37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 761824 |
Time | |
Date | 200711 |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : lch.airport |
State Reference | LA |
Altitude | msl single value : 10000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : lch.tracon |
Operator | other |
Make Model Name | Talon |
Operating Under FAR Part | Part 91 |
Flight Phase | cruise : level |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : approach |
Qualification | controller : radar |
Experience | controller radar : 10 controller time certified in position1 : 10 |
ASRS Report | 761824 |
Events | |
Anomaly | airspace violation : entry non adherence : required legal separation |
Independent Detector | other controllera |
Resolutory Action | none taken : detected after the fact |
Consequence | faa : investigated |
Supplementary | |
Problem Areas | Aircraft ATC Human Performance |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Deviation |
Narrative:
Aircraft X departed cwf and called departure. I observed the aircraft off the end of the runway and radar idented him. The aircraft never tagged up; I was busy with other traffic and missed the fact he was on the wrong code. The aircraft left my airspace wbound. The pilot called back approximately 20-30 mins later and asked if I wanted him to call another controller. He idented his position as near houston intercontinental airport. We called houston center beaumont lo sector who called houston approach and I switched the aircraft to 126.67. Houston approach reported aircraft X was on code XXXX and not on his assigned YYYY code. Therefore; aircraft X had not automatic acquired and flight plan was never activated. The controllers working the sectors aircraft X flew through spotted the target at 10000 ft and kept all other traffic away from the target so separation was never lost.
Original NASA ASRS Text
Title: LCH APCH CTLR IDENTIFIED CWF DEP; NO DATA BLOCK AND ON THE WRONG CODE; SUBSEQUENTLY RESULTING IN OPDEVS WITH SEVERAL ADJACENT SECTORS/FACILITIES.
Narrative: ACFT X DEPARTED CWF AND CALLED DEP. I OBSERVED THE ACFT OFF THE END OF THE RWY AND RADAR IDENTED HIM. THE ACFT NEVER TAGGED UP; I WAS BUSY WITH OTHER TFC AND MISSED THE FACT HE WAS ON THE WRONG CODE. THE ACFT LEFT MY AIRSPACE WBOUND. THE PLT CALLED BACK APPROX 20-30 MINS LATER AND ASKED IF I WANTED HIM TO CALL ANOTHER CTLR. HE IDENTED HIS POS AS NEAR HOUSTON INTERCONTINENTAL ARPT. WE CALLED HOUSTON CTR BEAUMONT LO SECTOR WHO CALLED HOUSTON APCH AND I SWITCHED THE ACFT TO 126.67. HOUSTON APCH RPTED ACFT X WAS ON CODE XXXX AND NOT ON HIS ASSIGNED YYYY CODE. THEREFORE; ACFT X HAD NOT AUTO ACQUIRED AND FLT PLAN WAS NEVER ACTIVATED. THE CTLRS WORKING THE SECTORS ACFT X FLEW THROUGH SPOTTED THE TARGET AT 10000 FT AND KEPT ALL OTHER TFC AWAY FROM THE TARGET SO SEPARATION WAS NEVER LOST.
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.