37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1282619 |
Time | |
Date | 201507 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Aircraft 1 | |
Make Model Name | B767-300 and 300 ER |
Operating Under FAR Part | Part 121 |
Flight Phase | Taxi |
Flight Plan | IFR |
Component | |
Aircraft Component | Air Conditioning and Pressurization Pack |
Person 1 | |
Function | Pilot Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | First Officer Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy |
Narrative:
After push and engine start; got a 'left pack temp' EICAS alert. Ran lt pack temperature QRH; reset pack temp control to stby north as directed. Light did not extinguish; so we waited for 5 minutes and reset the pack as directed. Alert extinguished and QRH checklist was complete. We looked at the MEL; but there didn't seem to be anything that applied. We contacted dispatch/maintenance control and got a 'roger.' we felt that we had a successful reset.only after takeoff did we realize that we did not comply with the post dispatch process as required by the fom. We contacted dispatch; they contacted maintenance control and told us via reply ACARS that no MEL would apply and to write it up and inform local maintenance upon arrival. The more we thought about it; the more that we felt that maintenance control was wrong; as we operated the left pack in the standby mode; not the normal mode.both crewmembers had turned from east coast cities into the flight. The sort was late; pushback crew had slow response to the plane after the beacon was turned on. The flight plan had a statement 'time critical flight//fly fast mach' which; unfortunately; had us armed to take off quickly after a lengthy delay. Failure of maintenance control to contact us after we alerted them to a maintenance issue.better verbiage in the QRH that matches the name of the switch as indicated in the cockpit companion or revision of the cockpit companion to better match verbiage used in the QRH. The two documents; in this case; do not provide assistance in attempting to resolve issued. Stay focused and keep after maintenance control for input. The only input received was after takeoff.
Original NASA ASRS Text
Title: B767-300 flight crew experiences a 'Left Pack Temp' EICAS alert; after push and engine start. The LT PACK TEMP QRH procedure is to reset and run the pack temp control in STBY N as directed. The pack is reset and run in STBY N but no MEL is applied.
Narrative: After push and engine start; got a 'Left Pack Temp' EICAS alert. Ran LT PACK TEMP QRH; reset pack temp control to STBY N as directed. Light did not extinguish; so we waited for 5 minutes and reset the pack as directed. Alert extinguished and QRH checklist was complete. We looked at the MEL; but there didn't seem to be anything that applied. We contacted Dispatch/Maintenance Control and got a 'roger.' We felt that we had a successful reset.Only after takeoff did we realize that we did not comply with the post dispatch process as required by the FOM. We contacted Dispatch; they contacted Maintenance Control and told us via reply ACARS that no MEL would apply and to write it up and inform local maintenance upon arrival. The more we thought about it; the more that we felt that Maintenance Control was wrong; as we operated the Left Pack in the Standby mode; not the Normal mode.Both crewmembers had turned from East Coast cities into the flight. The sort was late; pushback crew had slow response to the plane after the beacon was turned on. The flight plan had a statement 'TIME CRITICAL FLIGHT//FLY FAST MACH' which; unfortunately; had us armed to take off quickly after a lengthy delay. Failure of Maintenance Control to contact us after we alerted them to a maintenance issue.Better verbiage in the QRH that matches the name of the switch as indicated in the cockpit companion or revision of the cockpit companion to better match verbiage used in the QRH. The two documents; in this case; do not provide assistance in attempting to resolve issued. Stay focused and keep after Maintenance Control for input. The only input received was after takeoff.
Data retrieved from NASA's ASRS site 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.