37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 295890 |
Time | |
Date | 199502 |
Day | Mon |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : san |
State Reference | CA |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Aircraft 1 | |
Controlling Facilities | tower : msp |
Operator | common carrier : air carrier |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | climbout : takeoff ground : preflight |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
ASRS Report | 295890 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 240 flight time total : 12000 flight time type : 4000 |
ASRS Report | 296270 |
Events | |
Anomaly | aircraft equipment problem : less severe non adherence : far non adherence : published procedure 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:
This report involves a dispatch paper work error. Flight san- phx was dispatched with an authority/authorized allowable takeoff gross weight of 112200 pounds. The aircraft took off at a gross weight of 113900 pounds, well below the runway or climb limited takeoff gross weight performance limit of 118000 pounds. Safety was not a factor in this takeoff as our takeoff weight was more than 4000 pounds below the performance limit. The dispatch release was prepared for runway 9 with an allowable takeoff gross weight of 112200 pounds. We used runway 27 which could be used with an allowable takeoff gross weight of 118600 pounds. The error on the dispatch release was not caught until the aircraft was en route. Must pay closer attention to the data on the release to ensure accuracy and amend the release as necessary. Callback conversation with reporter revealed the following information: the reporter flies the B-737 for a low cost air carrier that is on the ascendancy. He chose not to cooperate in a special study and contributed no additional information other than aircraft type. Callback conversation with reporter from acn #296270 revealed the following information: the reporter is flying as first officer on the B-737-300 for an air carrier that is expanding rapidly. He has flown as captain on this aircraft for another air carrier and as captain for other acrs on other aircraft. He considered this to be a 'non event,' but sent in an ASRS report because the captain did. The captain did not report this to the air carrier, the only place that might have done some good. His air carrier is just now becoming aware of cockpit resource management problems and is beginning to do something about this. The first officer is concerned about his having to do several tasks that prevent him from helping when the captain is taxiing. The first officer is not expected to look at and confirm the takeoff weight computation. The air carrier puts a lot of schedule pressure on its crews.
Original NASA ASRS Text
Title: FLC TOOK OFF WITH THE WRONG ACFT WT ON THE MANIFEST.
Narrative: THIS RPT INVOLVES A DISPATCH PAPER WORK ERROR. FLT SAN- PHX WAS DISPATCHED WITH AN AUTH ALLOWABLE TKOF GROSS WT OF 112200 LBS. THE ACFT TOOK OFF AT A GROSS WT OF 113900 LBS, WELL BELOW THE RWY OR CLB LIMITED TKOF GROSS WT PERFORMANCE LIMIT OF 118000 LBS. SAFETY WAS NOT A FACTOR IN THIS TKOF AS OUR TKOF WT WAS MORE THAN 4000 LBS BELOW THE PERFORMANCE LIMIT. THE DISPATCH RELEASE WAS PREPARED FOR RWY 9 WITH AN ALLOWABLE TKOF GROSS WT OF 112200 LBS. WE USED RWY 27 WHICH COULD BE USED WITH AN ALLOWABLE TKOF GROSS WT OF 118600 LBS. THE ERROR ON THE DISPATCH RELEASE WAS NOT CAUGHT UNTIL THE ACFT WAS ENRTE. MUST PAY CLOSER ATTN TO THE DATA ON THE RELEASE TO ENSURE ACCURACY AND AMEND THE RELEASE AS NECESSARY. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR FLIES THE B-737 FOR A LOW COST ACR THAT IS ON THE ASCENDANCY. HE CHOSE NOT TO COOPERATE IN A SPECIAL STUDY AND CONTRIBUTED NO ADDITIONAL INFO OTHER THAN ACFT TYPE. CALLBACK CONVERSATION WITH RPTR FROM ACN #296270 REVEALED THE FOLLOWING INFO: THE RPTR IS FLYING AS FO ON THE B-737-300 FOR AN ACR THAT IS EXPANDING RAPIDLY. HE HAS FLOWN AS CAPT ON THIS ACFT FOR ANOTHER ACR AND AS CAPT FOR OTHER ACRS ON OTHER ACFT. HE CONSIDERED THIS TO BE A 'NON EVENT,' BUT SENT IN AN ASRS RPT BECAUSE THE CAPT DID. THE CAPT DID NOT RPT THIS TO THE ACR, THE ONLY PLACE THAT MIGHT HAVE DONE SOME GOOD. HIS ACR IS JUST NOW BECOMING AWARE OF COCKPIT RESOURCE MGMNT PROBS AND IS BEGINNING TO DO SOMETHING ABOUT THIS. THE FO IS CONCERNED ABOUT HIS HAVING TO DO SEVERAL TASKS THAT PREVENT HIM FROM HELPING WHEN THE CAPT IS TAXIING. THE FO IS NOT EXPECTED TO LOOK AT AND CONFIRM THE TKOF WT COMPUTATION. THE ACR PUTS A LOT OF SCHEDULE PRESSURE ON ITS CREWS.
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.