A11 controller described event when IFR aircraft; with missing flight plan information; was initiall...

Attributes
ACN	741633
Time
Date	200706
Local Time Of Day	1801 To 2400
Place
Locale Reference	atc facility : a11.tracon
State Reference	AK
Altitude	msl bound upper : 14000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : a11.tracon tower : anc.tower
Operator	common carrier : air carrier
Make Model Name	C-46 Commando
Operating Under FAR Part	Part 121
Flight Phase	climbout : takeoff climbout : initial
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar controller : approach
Experience	controller limited radar : 4 controller military : 5 controller non radar : 2 controller radar : 7 controller time certified in position1 : 7 flight time total : 600
ASRS Report	741633
Events
Anomaly	non adherence : published procedure
Independent Detector	other controllera
Resolutory Action	none taken : anomaly accepted
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Inter Facility Coordination Failure

Narrative:

Aircraft departed runway 25R on about a 270 degree heading without any coordination or a strip generated by the tower. I called up for information and was told by the local assist that the aircraft was on a VFR flight plan. I told the aircraft to remain VFR and resume own navigation. I asked and was told what his destination was and final altitude. (Fairbanks and 14000 ft.) I asked if he wanted flight following with center and the aircraft informed me he was in fact on an IFR flight plan. By pure luck no IFR separation was lost although the aircraft did turn opposite direction to the arrival runway. The tower explained that the aircraft's flight plan was not in the system when he called for taxi so they gave him VFR flight instructions. Prior to departure the IFR flight plan came up and was given to the aircraft but the flight strip still looked like a VFR to the local controller. Both the tower and approach recently changed system for flight plan notification and the new procedures may have contributed to this error.

Original NASA ASRS Text

Title: A11 CTLR DESCRIBED EVENT WHEN IFR ACFT; WITH MISSING FLT PLAN INFO; WAS INITIALLY HANDLED AS VFR; NO SEPARATION LOST.

Narrative: ACFT DEPARTED RWY 25R ON ABOUT A 270 DEG HDG WITHOUT ANY COORD OR A STRIP GENERATED BY THE TWR. I CALLED UP FOR INFO AND WAS TOLD BY THE LCL ASSIST THAT THE ACFT WAS ON A VFR FLT PLAN. I TOLD THE ACFT TO REMAIN VFR AND RESUME OWN NAV. I ASKED AND WAS TOLD WHAT HIS DEST WAS AND FINAL ALT. (FAIRBANKS AND 14000 FT.) I ASKED IF HE WANTED FLT FOLLOWING WITH CTR AND THE ACFT INFORMED ME HE WAS IN FACT ON AN IFR FLT PLAN. BY PURE LUCK NO IFR SEPARATION WAS LOST ALTHOUGH THE ACFT DID TURN OPPOSITE DIRECTION TO THE ARR RWY. THE TWR EXPLAINED THAT THE ACFT'S FLT PLAN WAS NOT IN THE SYS WHEN HE CALLED FOR TAXI SO THEY GAVE HIM VFR FLT INSTRUCTIONS. PRIOR TO DEP THE IFR FLT PLAN CAME UP AND WAS GIVEN TO THE ACFT BUT THE FLT STRIP STILL LOOKED LIKE A VFR TO THE LCL CTLR. BOTH THE TWR AND APCH RECENTLY CHANGED SYS FOR FLT PLAN NOTIFICATION AND THE NEW PROCS MAY HAVE CONTRIBUTED TO THIS ERROR.

Data retrieved from NASA's ASRS site as of January 2009 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.

A11 controller described event when IFR aircraft; with missing flight plan information; was initially handled as VFR; no separation lost.