37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1186831 |
Time | |
Date | 201407 |
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 | EMB ERJ 145 ER/LR |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Component | |
Aircraft Component | Turbine Engine |
Person 1 | |
Function | First Officer Pilot Not Flying |
Events | |
Anomaly | Aircraft Equipment Problem Critical |
Narrative:
During cruise we noticed the aircraft yaw to the left twice for no [apparent] reason. As we looked for any clues on the third time it yawed the captain noticed that the N1 on engine 1 surged to about 70%; and the thrust levers were set in the detent in the cruise thrust setting; around 90%. We noticed this the third and fourth time it happened; and also noticed that the ignition kicked on momentarily; and then the N1 returned to the fadec calculated setting in the cruise setting. These events lasted for about 5 seconds each. On the fifth surging event; the N1 decreased significantly; the ignition did not kick on; and the fadec alternated from B to a. At this point; we were already contacting dispatch and maintenance. We briefed for a single engine approach and landing and discussed alternates. Dispatch advised us to proceed to a diversion airport that suited them; so we declared an emergency and deviated there. We did not end up shutting down the engine. We briefed the approach and landing and there were no further disruptions or engine 1 events during the rest of the flight. On the landing; EICAS message 'E1-2 no dispatched' and 'E1 short dispatch' appeared.the threats of this event included task saturation (executing an unplanned emergency landing and diversion) as well as trying to figure out the best course of action to respond to this engine abnormality. I believe the captain and I did a good job executing this diversion and emergency landing. When we landed; maintenance told us that this aircraft has had a history of fadec issues; and that there have been unavailable parts. If this is true; I would highly recommend to the company that we fix the underlying problems with fadecs the first time whenever possible rather than simply 'defer' them or 'clear' them. I also appreciate very much our dispatcher and his rapid response and coordination with this event.
Original NASA ASRS Text
Title: When their left engine initiated repeated surges of lowered N1 the flight crew of an EMB-145 conferred with Dispatch and Maintenance and opted to declare an emergency and divert for maintenance attention.
Narrative: During cruise we noticed the aircraft yaw to the left twice for no [apparent] reason. As we looked for any clues on the third time it yawed the Captain noticed that the N1 on Engine 1 surged to about 70%; and the thrust levers were set in the detent in the cruise thrust setting; around 90%. We noticed this the third and fourth time it happened; and also noticed that the ignition kicked on momentarily; and then the N1 returned to the FADEC calculated setting in the cruise setting. These events lasted for about 5 seconds each. On the fifth surging event; the N1 decreased significantly; the ignition did not kick on; and the FADEC alternated from B to A. At this point; we were already contacting Dispatch and Maintenance. We briefed for a single engine approach and landing and discussed alternates. Dispatch advised us to proceed to a diversion airport that suited them; so we declared an emergency and deviated there. We did not end up shutting down the engine. We briefed the approach and landing and there were no further disruptions or Engine 1 events during the rest of the flight. On the landing; EICAS message 'E1-2 No Dispatched' and 'E1 Short Dispatch' appeared.The threats of this event included task saturation (executing an unplanned emergency landing and diversion) as well as trying to figure out the best course of action to respond to this engine abnormality. I believe the Captain and I did a good job executing this diversion and emergency landing. When we landed; Maintenance told us that this aircraft has had a history of FADEC issues; and that there have been unavailable parts. If this is true; I would highly recommend to the company that we fix the underlying problems with FADECs the first time whenever possible rather than simply 'defer' them or 'clear' them. I also appreciate very much our Dispatcher and his rapid response and coordination with this event.
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.