37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1029283 |
Time | |
Date | 201208 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | Boeing Company Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Takeoff |
Component | |
Aircraft Component | Turbine Engine |
Person 1 | |
Function | First Officer Pilot Not Flying |
Experience | Flight Crew Last 90 Days 240 Flight Crew Total 9000 Flight Crew Type 900 |
Events | |
Anomaly | Aircraft Equipment Problem Critical |
Narrative:
This was a through-flight; and the APU was allowed to run throughout the turn due to the very high ambient temperatures (44 C/110 F). First officer observed what appeared to be a brief illumination of the engine fire detection fault light after engine start. Shortly after the start of our taxi we noticed the following: engine 2 overheat light illuminated intermittently. The associated overheat detection switch appeared to be in the normal position; but when the captain went to place his hand on it; the switch clicked into its' seated position (in the normal notch). The engine fire detection panel had been tested and checked earlier in the day. The abnormal switch position; in combination with the intermittent nature of the indication; and previous brief illumination of the fault light; lead us to believe that the overheat indication might have been related to the overheat detection switch not being fully seated in its normal position. All engine indications/condition appeared normal. We then referenced the QRH and the MEL; and after conferring with maintenance control performed a detector loop test per the MEL. The engine 2 overheat light was out while performing the test; but did not illuminate as a result of the test. Our conclusion was: no positive test in the normal position (no engine 2 overheat indication). The test was positive when selecting loop a only. This seemed to confirm that the problem had been the result of a loop malfunction; and was consistent with the MEL (O) instructions (air traffic area 26-02). The captain coordinated with maintenance control via phone; and both offices concurred with our assessment of the situation and cleared us to continue with the flight. We complied with the provisions of the MEL and we continued. During the takeoff roll; at approximately 120 KTS; the captain noticed that the #2 engine egt was higher than the #1 by about 50 degrees; but still well within limits. Not sure if this was related to the event or not. Shortly after lift-off the engine #2 overheat light illuminated. This time the light came on steady. We declared an emergency and proceeded with the QRH procedures. This led to a #2 engine shutdown. Shortly after pulling the start lever to cutoff; the engine #2 overheat light extinguished. Performed a single engine landing and coordinated with emergency personnel on the ground before taxiing to the gate. We briefed an overweight landing; but we believe that landing weight was below the limit upon touchdown. Touchdown was smooth. Note: I found the ipad to be very helpful for reference during/after this event.
Original NASA ASRS Text
Title: Air Carrier First Officer describes the circumstances leading up to an engine overheat warning shortly after takeoff on a very hot day. The engine is shut down and flight returns to departure airport.
Narrative: This was a through-flight; and the APU was allowed to run throughout the turn due to the very high ambient temperatures (44 C/110 F). First Officer observed what appeared to be a brief illumination of the engine fire detection fault light after engine start. Shortly after the start of our taxi we noticed the following: Engine 2 overheat light illuminated intermittently. The associated overheat detection switch appeared to be in the normal position; but when the Captain went to place his hand on it; the switch clicked into its' seated position (in the normal notch). The engine fire detection panel had been tested and checked earlier in the day. The abnormal switch position; in combination with the intermittent nature of the indication; and previous brief illumination of the fault light; lead us to believe that the overheat indication might have been related to the overheat detection switch not being fully seated in its normal position. All engine indications/condition appeared normal. We then referenced the QRH and the MEL; and after conferring with Maintenance Control performed a detector loop test per the MEL. The engine 2 overheat light was out while performing the test; but did not illuminate as a result of the test. Our conclusion was: no positive test in the normal position (no engine 2 overheat indication). The test was positive when selecting loop A only. This seemed to confirm that the problem had been the result of a loop malfunction; and was consistent with the MEL (O) instructions (ATA 26-02). The Captain coordinated with Maintenance Control via phone; and both offices concurred with our assessment of the situation and cleared us to continue with the flight. We complied with the provisions of the MEL and we continued. During the takeoff roll; at approximately 120 KTS; the Captain noticed that the #2 engine EGT was higher than the #1 by about 50 degrees; but still well within limits. Not sure if this was related to the event or not. Shortly after lift-off the engine #2 overheat light illuminated. This time the light came on steady. We declared an emergency and proceeded with the QRH procedures. This led to a #2 engine shutdown. Shortly after pulling the start lever to cutoff; the engine #2 overheat light extinguished. Performed a single engine landing and coordinated with emergency personnel on the ground before taxiing to the gate. We briefed an overweight landing; but we believe that landing weight was below the limit upon touchdown. Touchdown was smooth. Note: I found the iPad to be very helpful for reference during/after this event.
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.