37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 935964 |
Time | |
Date | 201103 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.ARTCC |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | B767-300 and 300 ER |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Flight Plan | IFR |
Component | |
Aircraft Component | Powerplant Fuel Control Unit |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 150 Flight Crew Total 15000 Flight Crew Type 2000 |
Person 2 | |
Function | Pilot Not Flying Check Pilot |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 220 Flight Crew Total 11000 Flight Crew Type 5000 |
Events | |
Anomaly | Aircraft Equipment Problem Critical |
Narrative:
I was the captain on the flight. During the preflight review of the maintenance history; we noticed this airplane had been refused the previous day because of an electronic engine control (eec) status message. It appeared maintenance had replaced the left eec and the airplane was returned to service. There was some discussion among the crew about the implications of a loss of the eec and our ETOPS operation. Upon inspection of the maintenance release document (mrd); there was an entry indicating a deferral of a status message that seemed to be appearing intermittently. We had no status messages at that time and assumed it had been repaired. There was some discussion about why there was a deferral and no message. Again; after review of the release we noticed the left engine eec had been replaced and everything appeared normal. We continued our preflight preparations. We pushed back and started both engines. Before taxi we noticed the status message 'left engine eec C1' had appeared. We contacted maintenance and discussed the message and were convinced the message was erroneous and thus the reason for the deferral. We decided as a crew that the flight could continue safely. Taxi and takeoff were uneventful. As we continued our climb; I noticed a status message alert indication and noticed a 'left engine control' message now included with the 'left engine eec C1' message. We contacted dispatch and maintenance. We began discussing the new message with the maintenance controller. As we leveled off at 33;000 ft; the left engine spooled down to minimum fuel flow. We quickly reviewed our situation; declared an emergency; and decided to return to the departure airport. We needed about 10 minutes to dump enough fuel to prevent an overweight landing. We used that time to run all the appropriate checklists and set up a single engine approach to the runway. I advised the purser to prepare the cabin for evacuation. The plan was to touchdown as early as possible; use aerodynamic braking and reverse thrust to 80 KTS and apply brakes as required. We landed without incident. After we cleared the runway; the airport rescue and fire fighters inspected the landing gear and engines. We continued to the gate. After we completed the parking checklist; we noticed the 'left engine speed card' status message now also displayed. This entire incident was an excellent exercise in crew communication and coordination. We had an FAA inspector conducting an ETOPS line check. He joined in the discussions and we welcomed his input. He maintained a listening watch on all our cockpit and radio communications.
Original NASA ASRS Text
Title: A B767-300's EICAS alerted L ENG EEC C1 during climb followed later by alert L ENG CONTROL and the engine spooling down to minimum fuel flow. An emergency was declared and the aircraft returned to the departure airport.
Narrative: I was the Captain on the flight. During the preflight review of the maintenance history; we noticed this airplane had been refused the previous day because of an Electronic Engine Control (EEC) status message. It appeared Maintenance had replaced the left EEC and the airplane was returned to service. There was some discussion among the crew about the implications of a loss of the EEC and our ETOPS operation. Upon inspection of the Maintenance Release Document (MRD); there was an entry indicating a deferral of a status message that seemed to be appearing intermittently. We had no status messages at that time and assumed it had been repaired. There was some discussion about why there was a deferral and no message. Again; after review of the Release we noticed the left engine EEC had been replaced and everything appeared normal. We continued our preflight preparations. We pushed back and started both engines. Before taxi we noticed the status message 'L ENG EEC C1' had appeared. We contacted Maintenance and discussed the message and were convinced the message was erroneous and thus the reason for the deferral. We decided as a crew that the flight could continue safely. Taxi and takeoff were uneventful. As we continued our climb; I noticed a status message alert indication and noticed a 'L ENG CONTROL' message now included with the 'L ENG EEC C1' message. We contacted Dispatch and Maintenance. We began discussing the new message with the Maintenance Controller. As we leveled off at 33;000 FT; the left engine spooled down to minimum fuel flow. We quickly reviewed our situation; declared an emergency; and decided to return to the departure airport. We needed about 10 minutes to dump enough fuel to prevent an overweight landing. We used that time to run all the appropriate checklists and set up a single engine approach to the runway. I advised the Purser to prepare the cabin for evacuation. The plan was to touchdown as early as possible; use aerodynamic braking and reverse thrust to 80 KTS and apply brakes as required. We landed without incident. After we cleared the runway; the Airport Rescue and Fire Fighters inspected the landing gear and engines. We continued to the gate. After we completed the parking checklist; we noticed the 'L ENG SPEED CARD' status message now also displayed. This entire incident was an excellent exercise in crew communication and coordination. We had an FAA Inspector conducting an ETOPS line check. He joined in the discussions and we welcomed his input. He maintained a listening watch on all our cockpit and radio communications.
Data retrieved from NASA's ASRS site as of April 2012 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.