37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1598728 |
Time | |
Date | 201811 |
Local Time Of Day | 0601-1200 |
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 | Parked |
Flight Plan | IFR |
Component | |
Aircraft Component | Fuel Drain |
Person 1 | |
Function | First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural FAR Deviation - Procedural Published Material / Policy Ground Event / Encounter Ground Strike - Aircraft |
Narrative:
I was informed that the aircraft had been operating in an unairworthy condition for a week; when the damage was first observed. The damage was to a wi-fi antenna and fuel drain mast in the rear of the aircraft. The crew that initially [experienced] the tailstrike did not recognize the strike.the original cause of the event was a tailstrike that went unnoticed by the crew. The aircraft went 7 days in operation before the damage was noticed. Contributing factors might include cold weather operations leading to rushed pre and post flights; subtle damage which was difficult to notice; and post flight inspection complacency.emphasis of pre and post flight diligence and duties during training. Tailstrike training and training focused on how to recognize the potential subtle cues and specific ways to identify antenna damage which could be a symptom of a tailstrike. Possible required inspections if the aircraft was flared during landing past a specific angle; where tailstrike possibility increases significantly.
Original NASA ASRS Text
Title: EMB-175 First Officer reported the aircraft had been flown for a week with damage caused by a tailstrike event. Reportedly; the original flight crew involved in the tailstrike was not aware of the event.
Narrative: I was informed that the aircraft had been operating in an unairworthy condition for a week; when the damage was first observed. The damage was to a wi-fi antenna and fuel drain mast in the rear of the aircraft. The crew that initially [experienced] the tailstrike did not recognize the strike.The original cause of the event was a tailstrike that went unnoticed by the crew. The aircraft went 7 days in operation before the damage was noticed. Contributing factors might include cold weather operations leading to rushed pre and post flights; subtle damage which was difficult to notice; and post flight inspection complacency.Emphasis of pre and post flight diligence and duties during training. Tailstrike training and training focused on how to recognize the potential subtle cues and specific ways to identify antenna damage which could be a symptom of a tailstrike. Possible required inspections if the aircraft was flared during landing past a specific angle; where tailstrike possibility increases significantly.
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.