|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Local Time Of Day||0601 To 1200|
|Locale Reference||atc facility : fwa|
|Altitude||msl bound lower : 8000|
msl bound upper : 8000
|Operator||common carrier : air carrier|
|Make Model Name||Small Transport, Low Wing, 2 Recip Eng|
|Flight Phase||cruise other|
|Route In Use||enroute : direct|
enroute airway : gus
|Affiliation||government : faa|
|Function||controller : departure|
|Qualification||controller : radar|
|Affiliation||company : air carrier|
|Function||flight crew : captain|
oversight : pic
|Qualification||pilot : atp|
|Anomaly||non adherence : published procedure|
other anomaly other
|Independent Detector||other controllera|
|Resolutory Action||none taken : detected after the fact|
|Primary Problem||ATC Human Performance|
|Air Traffic Incident||Operational Deviation|
Small transport required a flight plan amendment prior to departure changing aircraft type, speed, altitude and route. A new flight plan was entered and the old one removed (this is easier than making all the changes). The wrong procedure was used and the flight plan was not sent to the fwa ARTS computer. This was a contributing factor. Small transport departed and I radar idented him. I told him to proceed on course and climb and maintain 8000' as there was no conflicting traffic. He was squawking the proper code,but I evidently didn't notice that he was not in my tab list (and not in my computer/fwa ARTS ii). Small transport called again requesting gus frequency. I gave him gus frequency, initially thinking I had handed him off earlier and he had missed or gotten the wrong frequency. I immediately called gus on the handoff line to see if they had him. They did not answer so the west coordinator called. Gus said they had no information (my computer did not depart his flight plan) and knew nothing about him. Gus then radar idented small transport outside my airspace. I was working 17 aircraft at the time, several of which required extra effort on my part in getting to their destinations. I was asked if I wanted to split up the radar position just prior to it getting busy. I said no because I was about to get rid of several aircraft to the tower and other facs, and there were only 2 strips in my proposal bay. My mistake was in not turning around and looking at the printer, as it was full.
Original NASA ASRS Text
Title: ACFT ENTERED ADJACENT AIRSPACE WITHOUT HANDOFF.
Narrative: SMT REQUIRED A FLT PLAN AMENDMENT PRIOR TO DEP CHANGING ACFT TYPE, SPD, ALT AND ROUTE. A NEW FLT PLAN WAS ENTERED AND THE OLD ONE REMOVED (THIS IS EASIER THAN MAKING ALL THE CHANGES). THE WRONG PROC WAS USED AND THE FLT PLAN WAS NOT SENT TO THE FWA ARTS COMPUTER. THIS WAS A CONTRIBUTING FACTOR. SMT DEPARTED AND I RADAR IDENTED HIM. I TOLD HIM TO PROCEED ON COURSE AND CLB AND MAINTAIN 8000' AS THERE WAS NO CONFLICTING TFC. HE WAS SQUAWKING THE PROPER CODE,BUT I EVIDENTLY DIDN'T NOTICE THAT HE WAS NOT IN MY TAB LIST (AND NOT IN MY COMPUTER/FWA ARTS II). SMT CALLED AGAIN REQUESTING GUS FREQ. I GAVE HIM GUS FREQ, INITIALLY THINKING I HAD HANDED HIM OFF EARLIER AND HE HAD MISSED OR GOTTEN THE WRONG FREQ. I IMMEDIATELY CALLED GUS ON THE HDOF LINE TO SEE IF THEY HAD HIM. THEY DID NOT ANSWER SO THE WEST COORDINATOR CALLED. GUS SAID THEY HAD NO INFO (MY COMPUTER DID NOT DEPART HIS FLT PLAN) AND KNEW NOTHING ABOUT HIM. GUS THEN RADAR IDENTED SMT OUTSIDE MY AIRSPACE. I WAS WORKING 17 ACFT AT THE TIME, SEVERAL OF WHICH REQUIRED EXTRA EFFORT ON MY PART IN GETTING TO THEIR DESTINATIONS. I WAS ASKED IF I WANTED TO SPLIT UP THE RADAR POS JUST PRIOR TO IT GETTING BUSY. I SAID NO BECAUSE I WAS ABOUT TO GET RID OF SEVERAL ACFT TO THE TWR AND OTHER FACS, AND THERE WERE ONLY 2 STRIPS IN MY PROPOSAL BAY. MY MISTAKE WAS IN NOT TURNING AROUND AND LOOKING AT THE PRINTER, AS IT WAS FULL.
Data retrieved from NASA's ASRS site as of August 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.