37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1095478 |
Time | |
Date | 201306 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | B737-300 |
Operating Under FAR Part | Part 121 |
Flight Phase | Takeoff |
Flight Plan | IFR |
Component | |
Aircraft Component | Air Conditioning and Pressurization Pack |
Person 1 | |
Function | Captain |
Experience | Flight Crew Last 90 Days 175 |
Person 2 | |
Function | First Officer |
Experience | Flight Crew Last 90 Days 175 Flight Crew Type 7500 |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy |
Narrative:
[The] captain asked for a bleeds off takeoff. We had an operating APU and the left pack had just been MEL'ed so we configured based on an operating APU. Since the left pack was not operable; we actually departed unpressurized and should have used that configuration for the bleeds and packs. That procedure would have included additional action items for our analog system. Upon reconfiguring after takeoff; we received an auto fail light and standby light on the pressurization panel. We leveled off at 8;000 ft; ran the appropriate checklists; notified dispatch; and continued to our destination. The controller was MEL'ed on arrival. Prior to departing; we were briefed by the arriving crew about an incident that occurred on takeoff. The incident involved a loud noise and vibration at approximately 10;000 ft that resolved when they reduced their power setting. They noticed no unusual engine indications and thought it might be a gear door seal. We thoroughly checked the aircraft and then decided to try operating the left pack. It made a very loud noise and we called maintenance control to get their thoughts on how to proceed. They thought we had a bad air cycle machine and suggested we call local maintenance to have it checked out. It was confirmed inoperable and MEL'ed. Because of the delay for maintenance and knowing we had a short (11-hour scheduled) overnight; I was rushed and not as vigilant as I should have been with regard to our release. I knew an increase in gross weight would be required for the additional fuel burn and quickly assumed a bleeds off takeoff would be necessary (it was 29C OAT) and I found myself headed down that road without checking the release for that change. I should have paid closer attention to our release and the performance data before jumping to the conclusion that a bleeds off takeoff was required. I should have taken the time to analyze our configuration and pressurization status before departure and configured to use the right pack and APU. [To prevent this] a note in the performance material; MEL; or aom that alerts a crew to use the unpressurized takeoff procedure for a bleeds off takeoff with the left pack inoperable or to configure using the APU and the right pack.
Original NASA ASRS Text
Title: A rushed B737-300 crew made a BLEEDS OFF takeoff with an MEL'ed Left pack but should have used APU air and the right pack for a pressurized BLEEDS OFF takeoff.
Narrative: [The] Captain asked for a bleeds off takeoff. We had an operating APU and the left pack had just been MEL'ed so we configured based on an operating APU. Since the left pack was not operable; we actually departed unpressurized and should have used that configuration for the bleeds and packs. That procedure would have included additional action items for our analog system. Upon reconfiguring after takeoff; we received an Auto Fail light and Standby light on the pressurization panel. We leveled off at 8;000 FT; ran the appropriate checklists; notified Dispatch; and continued to our destination. The controller was MEL'ed on arrival. Prior to departing; we were briefed by the arriving crew about an incident that occurred on takeoff. The incident involved a loud noise and vibration at approximately 10;000 FT that resolved when they reduced their power setting. They noticed no unusual engine indications and thought it might be a gear door seal. We thoroughly checked the aircraft and then decided to try operating the left pack. It made a very loud noise and we called Maintenance Control to get their thoughts on how to proceed. They thought we had a bad air cycle machine and suggested we call local Maintenance to have it checked out. It was confirmed inoperable and MEL'ed. Because of the delay for Maintenance and knowing we had a short (11-hour scheduled) overnight; I was rushed and not as vigilant as I should have been with regard to our Release. I knew an increase in gross weight would be required for the additional fuel burn and quickly assumed a bleeds off takeoff would be necessary (it was 29C OAT) and I found myself headed down that road without checking the Release for that change. I should have paid closer attention to our Release and the performance data before jumping to the conclusion that a bleeds off takeoff was required. I should have taken the time to analyze our configuration and pressurization status before departure and configured to use the right pack and APU. [To prevent this] a note in the performance material; MEL; or AOM that alerts a crew to use the unpressurized takeoff procedure for a bleeds off takeoff with the left pack inoperable or to configure using the APU and the right pack.
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.