 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
MD80 super 80 crew flew wrong aircraft. The wrong aircraft was positioned at the gate but the logbook for the right aircraft was boarded. Flight crew did not notice the discrepancy until after landing dfw. This created the problem of ACARS messages being delivered to the wrong flight.
| Attributes | |
| ACN | 362427 |
| Time | |
| Date | 199703 |
| Day | Tue |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | airport : sat |
| State Reference | TX |
| Altitude | agl bound lower : 0 agl bound upper : 0 |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tower : teb |
| Operator | common carrier : air carrier |
| Make Model Name | MD-80 Super 80 |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | Other |
| Flight Phase | ground : preflight |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| ASRS Report | 362427 |
| Person 2 | |
| Function | flight crew : first officer |
| Qualification | pilot : commercial pilot : instrument |
| Events | |
| Anomaly | non adherence other other anomaly other |
| Independent Detector | other flight crewa |
| Resolutory Action | none taken : detected after the fact |
| Consequence | Other |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
We were scheduled to fly flight sat-dfw. Everything was completed on the ground in sat except we were never told by sat operations that they had swapped aircraft for our flight. We also missed this on the paperwork. The ACARS was acting up from the beginning so we did everything manually. We suspected it was an ACARS problem. We never thought that it could be the wrong aircraft. We even free-texted dispatch to ask for the correct flight plan. When we arrived at the gate in dfw, we finally figured out that we had the paperwork for aircraft X, not aircraft Y -- obviously too late to correct our oversight. Luckily, both aircraft had clean logbooks and it was a VFR day. We both learned a valuable lesson in xchking paperwork and logbooks and tail numbers today.
Original NASA ASRS Text
Title: MD80 SUPER 80 CREW FLEW WRONG ACFT. THE WRONG ACFT WAS POSITIONED AT THE GATE BUT THE LOGBOOK FOR THE RIGHT ACFT WAS BOARDED. FLC DID NOT NOTICE THE DISCREPANCY UNTIL AFTER LNDG DFW. THIS CREATED THE PROB OF ACARS MESSAGES BEING DELIVERED TO THE WRONG FLT.
Narrative: WE WERE SCHEDULED TO FLY FLT SAT-DFW. EVERYTHING WAS COMPLETED ON THE GND IN SAT EXCEPT WE WERE NEVER TOLD BY SAT OPS THAT THEY HAD SWAPPED ACFT FOR OUR FLT. WE ALSO MISSED THIS ON THE PAPERWORK. THE ACARS WAS ACTING UP FROM THE BEGINNING SO WE DID EVERYTHING MANUALLY. WE SUSPECTED IT WAS AN ACARS PROB. WE NEVER THOUGHT THAT IT COULD BE THE WRONG ACFT. WE EVEN FREE-TEXTED DISPATCH TO ASK FOR THE CORRECT FLT PLAN. WHEN WE ARRIVED AT THE GATE IN DFW, WE FINALLY FIGURED OUT THAT WE HAD THE PAPERWORK FOR ACFT X, NOT ACFT Y -- OBVIOUSLY TOO LATE TO CORRECT OUR OVERSIGHT. LUCKILY, BOTH ACFT HAD CLEAN LOGBOOKS AND IT WAS A VFR DAY. WE BOTH LEARNED A VALUABLE LESSON IN XCHKING PAPERWORK AND LOGBOOKS AND TAIL NUMBERS TODAY.
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.