37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 866866 |
Time | |
Date | 201001 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZHU.ARTCC |
State Reference | TX |
Aircraft 1 | |
Make Model Name | Medium Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Route In Use | Direct |
Flight Plan | IFR |
Person 1 | |
Function | Oceanic |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy |
Narrative:
I was working D-79 when aircraft X reported over maeko intersection. Maeko intersection is on B753 and the flight plan showed kehli A766 kelpp. The R-79 controller asked the pilot to say again his position and aircraft X again stated maeko. The radar controller asked for aircraft X's route and was told kehli direct maeko B753. I then called merida to check what route they had which was the same as ours kehli A766 kelpp. When the supervisor was informed he ran a spurt and found that there had been a proposal that was the same as the pilots flight plan. Our flight plan was an automated one from merida. I do not know if their information is activated automatically like it is back and forth between merida and ZHU or if they must activate the north bound flight plans. Luckily; there were no other aircraft at that altitude.
Original NASA ASRS Text
Title: ZHU Controller reported an aircraft handed off from an adjacent facility was cleared and flying a different route than had been coordinated between the facilities.
Narrative: I was working D-79 when Aircraft X reported over MAEKO Intersection. MAEKO Intersection is on B753 and the flight plan showed KEHLI A766 KELPP. The R-79 Controller asked the pilot to say again his position and Aircraft X again stated MAEKO. The Radar Controller asked for Aircraft X's route and was told KEHLI direct MAEKO B753. I then called Merida to check what route they had which was the same as ours KEHLI A766 KELPP. When the Supervisor was informed he ran a spurt and found that there had been a proposal that was the same as the pilots flight plan. Our flight plan was an automated one from Merida. I do not know if their information is activated automatically like it is back and forth between Merida and ZHU or if they must activate the north bound flight plans. Luckily; there were no other aircraft at that altitude.
Data retrieved from NASA's ASRS site as of April 2012 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.