 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Flight crew of medium large transport departing mexico city correctly read back clearance and route. Not the same as stored in their computer. Flight crew flew computer route and entering ZMA control had conflict with opposite direction traffic same altitude.
| Attributes | |
| ACN | 201444 |
| Time | |
| Date | 199202 |
| Day | Sat |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | atc facility : pie |
| State Reference | FL |
| Altitude | msl bound lower : 35000 msl bound upper : 35000 |
| Aircraft 1 | |
| Controlling Facilities | artcc : zma |
| Operator | common carrier : air carrier |
| Make Model Name | Medium Large Transport, Low Wing, 2 Turbojet Eng |
| Navigation In Use | Other Other |
| Flight Phase | cruise other |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : commercial pilot : flight engineer pilot : atp pilot : cfi pilot : instrument |
| Experience | flight time last 90 days : 200 flight time total : 11000 flight time type : 900 |
| ASRS Report | 201444 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : commercial pilot : atp pilot : instrument |
| Events | |
| Anomaly | conflict : airborne less severe non adherence : clearance non adherence : far non adherence : published procedure other spatial deviation |
| Independent Detector | other controllera other flight crewa |
| Resolutory Action | other |
| Consequence | Other |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
| Situations | |
| ATC Facility | procedure or policy : unspecified |
Narrative:
Copied correct routing from mexico clearance in mexico city. Routing was different from route stored in FMC computer. We flew the route stored in computer, not as filed by ATC. Merida center informed us of the error, but made no effort to change our routing. We continued up the airway when we entered miami airspace control we were informed that there was another aircraft opposite bound along the same airway. To arrival over the same fix (ciger) at the same time and altitude. ATC vectored us off the airway with no further incident.
Original NASA ASRS Text
Title: FLC OF MLG DEPARTING MEXICO CITY CORRECTLY READ BACK CLRNC AND RTE. NOT THE SAME AS STORED IN THEIR COMPUTER. FLC FLEW COMPUTER RTE AND ENTERING ZMA CTL HAD CONFLICT WITH OPPOSITE DIRECTION TFC SAME ALT.
Narrative: COPIED CORRECT ROUTING FROM MEXICO CLRNC IN MEXICO CITY. ROUTING WAS DIFFERENT FROM RTE STORED IN FMC COMPUTER. WE FLEW THE RTE STORED IN COMPUTER, NOT AS FILED BY ATC. MERIDA CTR INFORMED US OF THE ERROR, BUT MADE NO EFFORT TO CHANGE OUR ROUTING. WE CONTINUED UP THE AIRWAY WHEN WE ENTERED MIAMI AIRSPACE CTL WE WERE INFORMED THAT THERE WAS ANOTHER ACFT OPPOSITE BOUND ALONG THE SAME AIRWAY. TO ARR OVER THE SAME FIX (CIGER) AT THE SAME TIME AND ALT. ATC VECTORED US OFF THE AIRWAY WITH NO FURTHER INCIDENT.
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.