 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
The flight crew of a commuter aircraft failed to note the left engine had shut down until cleared for takeoff. All pre takeoff checks had been completed prior to the engine failing.
| Attributes | |
| ACN | 880421 |
| Time | |
| Date | 201003 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | IAD.Airport |
| State Reference | DC |
| Aircraft 1 | |
| Make Model Name | Medium Transport Low Wing 2 Turbojet Eng |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Taxi |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | Turbine Engine |
| Person 1 | |
| Function | Captain Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Person 2 | |
| Function | Pilot Not Flying Captain |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Aircraft Equipment Problem Critical |
Narrative:
Sometime during the taxi for takeoff the number 1 engine 'spooled-down' with no associated EICAS messages other than crossbleed open and we were cleared for takeoff on runway 30. As we were taking the active runway the first officer alerted me the number 1 engine had no oil pressure and not to takeoff; I looked at the engine; verified the low oil pressure and noticed we had no N2 showing as well. I taxied off the runway while the first officer told the tower controller we needed to go back to the gate. Once clear of the runway; the first officer contacted ground control for taxi instructions and operations to arrange for a gate. After receiving clearance to taxi to gate; we taxied single engine to the gate where we wrote-up the engine spool-down and notified maintenance control. I believe all applicable sops and policies were followed and we were in full compliance with all applicable regulations. However; I later learned an event may have occurred and that there was possible noncompliance with the fars when I received a letter of investigation earlier today via certified mail. I'm not sure why the engine 'spooled-down' but the reason the 'spool-down' wasn't caught is because we had already completed the required checklists and there were no EICAS messages other than 'crossbleed open'.
Original NASA ASRS Text
Title: The flight crew of a commuter aircraft failed to note the left engine had shut down until cleared for takeoff. All pre takeoff checks had been completed prior to the engine failing.
Narrative: Sometime during the taxi for takeoff the number 1 engine 'spooled-down' with no associated EICAS messages other than CROSSBLEED OPEN and we were cleared for takeoff on Runway 30. As we were taking the active runway the First Officer alerted me the number 1 engine had no oil pressure and not to takeoff; I looked at the engine; verified the low oil pressure and noticed we had no N2 showing as well. I taxied off the runway while the First Officer told the tower controller we needed to go back to the gate. Once clear of the runway; the First Officer contacted ground control for taxi instructions and operations to arrange for a gate. After receiving clearance to taxi to gate; we taxied single engine to the gate where we wrote-up the engine spool-down and notified Maintenance Control. I believe all applicable SOPs and policies were followed and we were in full compliance with all applicable regulations. However; I later learned an event may have occurred and that there was possible noncompliance with the FARs when I received a letter of investigation earlier today via certified mail. I'm not sure why the engine 'spooled-down' but the reason the 'spool-down' wasn't caught is because we had already completed the required checklists and there were no EICAS Messages other than 'CROSSBLEED OPEN'.
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.