United Air Lines Flight 1475
Boeing 737-924ER · Incident: birdstrike en route
From Dallas Fort Worth International Airport (DFW) to Denver, CO
Event
- NTSB case
- CEN12IA502
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Incident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- Airline
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Boeing 737-924ER
- Aircraft type
- Boeing 737
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N37420
- Operator
- United Air Lines
- Onboard fatalities
- Unknown
- Route
- From Dallas Fort Worth International Airport (DFW), Dallas, TXTo Denver, CO
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 121: Air Carrier
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route · descent
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Birdstrike
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Environmental issues › Physical environment
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB 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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN12IA502
- Event ID
- 20120802X03552
- Case number
- CEN12IA502
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 9d17c26a0d62ffefb9bc2ada08d19af7448c603734dbf8308938730b51434ca1; retrieved 2026-09-15T19:09:50.093Z.