37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 944253 |
Time | |
Date | 201104 |
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 170/175 ER&LR |
Operating Under FAR Part | Part 121 |
Flight Phase | Taxi |
Component | |
Aircraft Component | Fan |
Person 1 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | Pilot Flying First Officer |
Events | |
Anomaly | Aircraft Equipment Problem Critical Ground Event / Encounter FOD Ground Event / Encounter Object |
Narrative:
On the taxi out; an aircraft taxiing behind us informed ground control that it appeared we might have ingested some plastic into one of our engines. They said it looked like there was a bunch of plastic pieces laying on the taxiway. The message was relayed to us. This report came shortly after we had started the number two engine. We didn't notice any glitches as far as how the engines were running; but as a safety precaution we decided to return to the gate to look at the engines to make sure they were clear and that there was no damage. Upon returning to the gate; an airport operations vehicle met us and said that they had found numerous pieces of a baggage scanner on the taxiway. Upon review of the engines; it did appear that the number two engine had indeed ingested something; as there was considerable damage to numerous fan blades that were not present during preflight. One would have to assume that one of the ground crew must have set the baggage scanner inside the number two cowling after scanning bags and forgot about it. It was not noticed by the ground crew on the push back and was then ingested by number two when the engine was started.ground crews need to be more aware of their actions and do a complete and thorough walk-around on the aircraft before it is pushed back.
Original NASA ASRS Text
Title: An ERJ170 suffered considerable engine damage after ingesting FOD during start. Remains of a baggage scanner were found on the taxiway.
Narrative: On the taxi out; an aircraft taxiing behind us informed Ground Control that it appeared we might have ingested some plastic into one of our engines. They said it looked like there was a bunch of plastic pieces laying on the taxiway. The message was relayed to us. This report came shortly after we had started the number two engine. We didn't notice any glitches as far as how the engines were running; but as a safety precaution we decided to return to the gate to look at the engines to make sure they were clear and that there was no damage. Upon returning to the gate; an Airport Operations vehicle met us and said that they had found numerous pieces of a baggage scanner on the taxiway. Upon review of the engines; it did appear that the number two engine had indeed ingested something; as there was considerable damage to numerous fan blades that were not present during preflight. One would have to assume that one of the ground crew must have set the baggage scanner inside the number two cowling after scanning bags and forgot about it. It was not noticed by the ground crew on the push back and was then ingested by number two when the engine was started.Ground crews need to be more aware of their actions and do a complete and thorough walk-around on the aircraft before it is pushed back.
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.