ASN Wikibase Occurrence # 147274
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can
submit corrected information.
Date: | Tuesday 31 July 2012 |
Time: | 09:09 |
Type: | Boeing 737-924ER (WL) |
Owner/operator: | United Air Lines |
Registration: | N37420 |
MSN: | 33457/2565 |
Year of manufacture: | 2008 |
Engine model: | CFM INTL CFM56-7B26 |
Fatalities: | Fatalities: 0 / Occupants: 157 |
Aircraft damage: | Minor |
Category: | Incident |
Location: | near Denver, CO -
United States of America
|
Phase: | Approach |
Nature: | Passenger - Scheduled |
Departure airport: | Dallas/Fort Worth International Airport, TX (DFW/KDFW) |
Destination airport: | Denver International Airport, CO (DEN/KDEN) |
Investigating agency: | NTSB |
Confidence Rating: | Accident investigation report completed and information captured |
Narrative:The flight crew reported that the airplane struck a bird while descending to land. Examination of the airplane after the event revealed a large hole in the radome and a portion of the broken radome lodged on the left pitot tube, which was also bent. The flight crew reported that following the bird strike, the captain’s airspeed and altimeter were inoperative and the first officer’s airspeed and altimeter indications were erratic. The captain eventually lost all instrument indications on his primary flight display (PFD). The crew referenced the standby instruments, but the readings did not make sense given the airplane altitude and power settings. As a result, the flight crew used power settings and aircraft configurations along with air traffic control (ATC) callouts of their ground speed to continue the flight to the intended destination, where they executed an uneventful landing.
The operator later reported that the standby airspeed indicator readings during the descent appeared to match the ground speed callouts provided by ATC. Data retrieved from the flight data recorder (FDR) for the left air data inertial reference unit (ADIRU), which references sensed data from the left pitot probe and static ports, confirmed a loss of airspeed information that would have resulted in an amber flag indicating “IAS DISAGREE” on the left and right primary PFD, as well as an amber flag indicating “SPD” on the left PFD. Data from the right ADIRU and the standby system were not recorded. Other air data parameters exhibited erroneous behavior that was consistent with the loss of airspeed information. The FDR continued to record altitude and attitude information throughout the remainder of the flight. Testing of the air data systems following replacement of the damaged pitot tube and cleaning of the system did not reveal any malfunctions or failures that would explain the total loss of indications on the left PFD.
Probable Cause: An in-flight collision with a bird during descent to land, which resulted in damage to the left pitot tube and loss of airspeed information to the left and right primary flight displays (PFD). The reason for the total loss of indications on the left PFD could not be determined based on available evidence.
Accident investigation:
|
| |
Investigating agency: | NTSB |
Report number: | CEN12IA502 |
Status: | Investigation completed |
Duration: | 1 year and 7 months |
Download report: | Final report |
|
Sources:
NTSB
https://flightaware.com/live/flight/N37420/history/20120731/1319Z/KDFW/KDEN Location
Revision history:
Date/time | Contributor | Updates |
01-Aug-2012 13:02 |
ryan |
Added |
01-Aug-2012 13:06 |
harro |
Updated [Aircraft type, Cn, Source, Narrative] |
21-Dec-2016 19:28 |
ASN Update Bot |
Updated [Time, Damage, Category, Investigating agency] |
28-Nov-2017 20:17 |
ASN Update Bot |
Updated [Cn, Operator, Total occupants, Other fatalities, Departure airport, Destination airport, Source, Narrative] |
28-Nov-2017 20:18 |
harro |
Updated [Operator, Other fatalities, Source] |
The Aviation Safety Network is an exclusive service provided by:
CONNECT WITH US:
©2024 Flight Safety Foundation