37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 347765 |
Time | |
Date | 199609 |
Day | Sat |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : fyv |
State Reference | AR |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | ATR 42 |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other Other |
Flight Phase | ground : preflight other |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
ASRS Report | 347765 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp pilot : instrument pilot : commercial pilot : cfi |
Experience | flight time last 90 days : 140 flight time total : 2000 flight time type : 200 |
ASRS Report | 348570 |
Events | |
Anomaly | non adherence : far non adherence : published procedure other anomaly other |
Independent Detector | other other : unspecified |
Resolutory Action | none taken : detected after the fact |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Aircraft X was flown on a scheduled passenger flight from stl to fyv. We were scheduled for an overnight. When we called in range to fyv, we were told that we would have to take our flight bags off of the aircraft because it was scheduled for a training flight that night. We understood this to mean that if there had not been any training taking place, we would not have to take our bags off of the aircraft because we were taking the same aircraft out in the morning. The training crew met us at the airplane and said that they would try to get the airplane back without breaking anything. This also reinforced the thought that we were taking the same aircraft out in the morning. When we arrived at the airport in the morning, we proceeded to prepare for our flight to stl. The only aircraft on the ramp was aircraft X. Upon our arrival in stl, we were told by the crew taking over the aircraft that we had departed fyv in the wrong aircraft. A review of the dispatch for our flight confirmed that this was true. The error was discovered by stl ramp and operations, before we departed fyv, when the aircraft that we were scheduled to fly arrived in stl. When the error was discovered, no one called and informed fyv operations. Contributing factors: the crew training in fyv parked the aircraft in a position different from where we had parked it, and where it was expected to be parked. This confused the ground crew in fyv who loaded the wrong aircraft in the morning. This led the first crew into thinking that that was their aircraft. When stl operations discovered the error, they failed to pass along the information. We assumed that the aircraft on the ramp was the aircraft that we were to fly since we had flown the aircraft in the previous night. Aircraft X was also the only aircraft on the ramp. I failed to xchk the aircraft number against the dispatch release. I did look to see if an MEL was listed and there was. When we brought aircraft X in the previous night, it also had an MEL. I did not verify the MEL number. All concerned should have been able to catch this mistake. I will definitely make an effort to be more conscious and thorough in reviewing my dispatch and will also now require the first officer to review the dispatch instead of just asking if they want to look it over.
Original NASA ASRS Text
Title: AN ACR ATR42 CREW FLEW AN ACFT THAT WAS DIFFERENT FROM THE ONE LISTED ON THE DISPATCH RELEASE. ERROR ADMITTED. THE ACR'S OPS SPECS REQUIRE THAT THE RELEASE SHOW THE CORRECT ACFT NUMBER LEADING TO AN FAR VIOLATION IF THE ACFT NUMBER IS WRONG.
Narrative: ACFT X WAS FLOWN ON A SCHEDULED PAX FLT FROM STL TO FYV. WE WERE SCHEDULED FOR AN OVERNIGHT. WHEN WE CALLED IN RANGE TO FYV, WE WERE TOLD THAT WE WOULD HAVE TO TAKE OUR FLT BAGS OFF OF THE ACFT BECAUSE IT WAS SCHEDULED FOR A TRAINING FLT THAT NIGHT. WE UNDERSTOOD THIS TO MEAN THAT IF THERE HAD NOT BEEN ANY TRAINING TAKING PLACE, WE WOULD NOT HAVE TO TAKE OUR BAGS OFF OF THE ACFT BECAUSE WE WERE TAKING THE SAME ACFT OUT IN THE MORNING. THE TRAINING CREW MET US AT THE AIRPLANE AND SAID THAT THEY WOULD TRY TO GET THE AIRPLANE BACK WITHOUT BREAKING ANYTHING. THIS ALSO REINFORCED THE THOUGHT THAT WE WERE TAKING THE SAME ACFT OUT IN THE MORNING. WHEN WE ARRIVED AT THE ARPT IN THE MORNING, WE PROCEEDED TO PREPARE FOR OUR FLT TO STL. THE ONLY ACFT ON THE RAMP WAS ACFT X. UPON OUR ARR IN STL, WE WERE TOLD BY THE CREW TAKING OVER THE ACFT THAT WE HAD DEPARTED FYV IN THE WRONG ACFT. A REVIEW OF THE DISPATCH FOR OUR FLT CONFIRMED THAT THIS WAS TRUE. THE ERROR WAS DISCOVERED BY STL RAMP AND OPS, BEFORE WE DEPARTED FYV, WHEN THE ACFT THAT WE WERE SCHEDULED TO FLY ARRIVED IN STL. WHEN THE ERROR WAS DISCOVERED, NO ONE CALLED AND INFORMED FYV OPS. CONTRIBUTING FACTORS: THE CREW TRAINING IN FYV PARKED THE ACFT IN A POS DIFFERENT FROM WHERE WE HAD PARKED IT, AND WHERE IT WAS EXPECTED TO BE PARKED. THIS CONFUSED THE GND CREW IN FYV WHO LOADED THE WRONG ACFT IN THE MORNING. THIS LED THE FIRST CREW INTO THINKING THAT THAT WAS THEIR ACFT. WHEN STL OPS DISCOVERED THE ERROR, THEY FAILED TO PASS ALONG THE INFO. WE ASSUMED THAT THE ACFT ON THE RAMP WAS THE ACFT THAT WE WERE TO FLY SINCE WE HAD FLOWN THE ACFT IN THE PREVIOUS NIGHT. ACFT X WAS ALSO THE ONLY ACFT ON THE RAMP. I FAILED TO XCHK THE ACFT NUMBER AGAINST THE DISPATCH RELEASE. I DID LOOK TO SEE IF AN MEL WAS LISTED AND THERE WAS. WHEN WE BROUGHT ACFT X IN THE PREVIOUS NIGHT, IT ALSO HAD AN MEL. I DID NOT VERIFY THE MEL NUMBER. ALL CONCERNED SHOULD HAVE BEEN ABLE TO CATCH THIS MISTAKE. I WILL DEFINITELY MAKE AN EFFORT TO BE MORE CONSCIOUS AND THOROUGH IN REVIEWING MY DISPATCH AND WILL ALSO NOW REQUIRE THE FO TO REVIEW THE DISPATCH INSTEAD OF JUST ASKING IF THEY WANT TO LOOK IT OVER.
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.