MTR X penetrated ZDV airspace without proper coordination.

Attributes
ACN	141469
Time
Date	199004
Day	Sat
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : lbl
State Reference	KS
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	artcc : zdv artcc : zkc
Operator	other
Make Model Name	Military Trainer
Flight Phase	cruise other
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : flight data
Qualification	controller : developmental
Experience	controller non radar : 1
ASRS Report	141469
Person 2
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Events
Anomaly	non adherence : published procedure other anomaly other other anomaly other
Independent Detector	other controllera other other : unspecified atc
Resolutory Action	none taken : detected after the fact
Consequence	faa : investigated
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Intra Facility Coordination Failure Inter Facility Coordination Failure Operational Deviation

Narrative:

I accepted a manual flight plan from K.C. I entered the flight plan in the computer; it said, 'accept fp.' we then received a printed strip saying, 'manual coordination required.' I was unfamiliar with this message and delivered it to my supervisor and then returned to my position. Kansas city had tied off our computer accidentally and therefore we were receiving numerous manual flight plans. The flight plan in question was rejected from the computer and therefore not passed to appropriate sectors. MTR X flew around in other sectors before being picked up on radar, therefore causing the deviation. I believe several things could have happened to avoid this error: 1) 'accept fp' doesn't really mean the computer has accepted it, only that it accepts the format. I was unaware of this, as were all others around me. 2) kansas city passed the flight plan to the wrong area. If it had been passed to the right area, they would have had at least a manual flight plan. 3) the message, 'manual coordination required,' was unclear--never seen or explained before. 4) kansas city inadvertently tying us off of computer was the main problem. I know I did everything properly and had no idea of this result coming about!

Original NASA ASRS Text

Title: MTR X PENETRATED ZDV AIRSPACE WITHOUT PROPER COORD.

Narrative: I ACCEPTED A MANUAL FLT PLAN FROM K.C. I ENTERED THE FLT PLAN IN THE COMPUTER; IT SAID, 'ACCEPT FP.' WE THEN RECEIVED A PRINTED STRIP SAYING, 'MANUAL COORD REQUIRED.' I WAS UNFAMILIAR WITH THIS MESSAGE AND DELIVERED IT TO MY SUPVR AND THEN RETURNED TO MY POS. KANSAS CITY HAD TIED OFF OUR COMPUTER ACCIDENTALLY AND THEREFORE WE WERE RECEIVING NUMEROUS MANUAL FLT PLANS. THE FLT PLAN IN QUESTION WAS REJECTED FROM THE COMPUTER AND THEREFORE NOT PASSED TO APPROPRIATE SECTORS. MTR X FLEW AROUND IN OTHER SECTORS BEFORE BEING PICKED UP ON RADAR, THEREFORE CAUSING THE DEVIATION. I BELIEVE SEVERAL THINGS COULD HAVE HAPPENED TO AVOID THIS ERROR: 1) 'ACCEPT FP' DOESN'T REALLY MEAN THE COMPUTER HAS ACCEPTED IT, ONLY THAT IT ACCEPTS THE FORMAT. I WAS UNAWARE OF THIS, AS WERE ALL OTHERS AROUND ME. 2) KANSAS CITY PASSED THE FLT PLAN TO THE WRONG AREA. IF IT HAD BEEN PASSED TO THE RIGHT AREA, THEY WOULD HAVE HAD AT LEAST A MANUAL FLT PLAN. 3) THE MESSAGE, 'MANUAL COORD REQUIRED,' WAS UNCLEAR--NEVER SEEN OR EXPLAINED BEFORE. 4) KANSAS CITY INADVERTENTLY TYING US OFF OF COMPUTER WAS THE MAIN PROB. I KNOW I DID EVERYTHING PROPERLY AND HAD NO IDEA OF THIS RESULT COMING ABOUT!

Data retrieved from NASA's ASRS site as of July 2007 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.