 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
When their FMS automatic performance update for takeoff from MMMX failed to appear in a timely fashion; the flight crew of a B737 manually programmed the FMS based on an acars hard copy and took off. After successfully departing they received the automatic update and discovered they had taken off on 5L although their manually loaded performance data was for 5R and had utilized flap and power settings inappropriate for their actual takeoff.
| Attributes | |
| ACN | 1069985 |
| Time | |
| Date | 201302 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | MMMX.Airport |
| State Reference | FO |
| Environment | |
| Flight Conditions | VMC |
| Aircraft 1 | |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Takeoff |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | PMC Performance/Thrust Management Computer |
| Person 1 | |
| Function | Pilot Not Flying Captain |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 163 Flight Crew Total 14000 Flight Crew Type 10000 |
| Person 2 | |
| Function | First Officer Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 220 Flight Crew Total 10800 Flight Crew Type 1600 |
| Events | |
| Anomaly | Aircraft Equipment Problem Critical Deviation - Procedural Published Material / Policy Deviation - Procedural Weight And Balance |
Narrative:
In the preflight setup; everything was uploading properly: route; winds; ATIS; etc. The first officer entered the expected runway (05L) and departure in the FMC. We called for our clearance and were cleared via the runway and departure we anticipated. With all doors closed; ready for pushback; we awaited our 'numbers' [takeoff performance data.]the hard copy of the data appeared on the printer and we waited for the uplink to the FMC; but it did not appear. The first officer pressed the 'request' prompt for the performance data for runway 05L (which was the runway already entered in the FMC). We reviewed the hard copy of the [performance data] and the first officer asked if it was okay to manually enter the data off the paper while we awaited the uplink. I said it was; and he entered the data manually. Flaps 1; no reduction. We pushed back; taxied to and took off runway 05L. A few minutes after takeoff; an FMS perf init load prompt appeared; and we received a hard copy of [performance data] for runway 05L. It was; however; for flaps 5 and 'improved climb.' huh? We reviewed our original [hard copy printed data] and realized it was for runway 05R. We took off with the wrong data in the wrong configuration. We later discussed the potential 'worse case' scenarios - particularly at such a critical; high altitude/mountainous airport.
Original NASA ASRS Text
Title: When their FMS automatic performance update for takeoff from MMMX failed to appear in a timely fashion; the flight crew of a B737 manually programmed the FMS based on an ACARs hard copy and took off. After successfully departing they received the automatic update and discovered they had taken off on 5L although their manually loaded performance data was for 5R and had utilized flap and power settings inappropriate for their actual takeoff.
Narrative: In the preflight setup; everything was uploading properly: route; winds; ATIS; etc. The First Officer entered the expected Runway (05L) and departure in the FMC. We called for our clearance and were cleared via the runway and departure we anticipated. With all doors closed; ready for pushback; we awaited our 'numbers' [Takeoff Performance DATA.]The hard copy of the data appeared on the printer and we waited for the uplink to the FMC; but it did not appear. The First Officer pressed the 'request' prompt for the performance data for Runway 05L (which was the runway already entered in the FMC). We reviewed the hard copy of the [performance data] and the First Officer asked if it was okay to manually enter the data off the paper while we awaited the uplink. I said it was; and he entered the data manually. Flaps 1; no reduction. We pushed back; taxied to and took off Runway 05L. A few minutes after takeoff; an FMS PERF INIT load prompt appeared; and we received a hard copy of [performance data] for RWY 05L. It was; however; for FLAPS 5 and 'Improved Climb.' Huh? We reviewed our original [hard copy printed data] and realized it was for Runway 05R. We took off with the wrong data in the wrong configuration. We later discussed the potential 'worse case' scenarios - particularly at such a critical; high altitude/mountainous airport.
Data retrieved from NASA's ASRS site as of July 2013 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.