Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

July 31, 2012 · Boeing 737-924ER · N37420

Denver, CO

Overview

Report Status
Final with probable cause
Event Type
Incident
Date
July 31, 2012
Injury Outcomes
No injuries (157 uninjured)
Location
Denver, CO
Aircraft
Boeing 737-924ER
Tail Number
N37420
Operator
United Airlines
Injuries
None
Aircraft Damage
Minor
NTSB Number
CEN12IA502

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.

NTSB 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.

Full Narrative

On July 31, 2012, about 0909 mountain daylight time, a Boeing 737-924ER, N37420, struck a large bird while approaching to land at the Denver International Airport (DEN), Denver, Colorado. There were no injuries reported. The airplane sustained damage to the radome, pilot side pitot tube, and the vertical stabilizer. The flight crew declared an emergency and continued to DEN making an uneventful landing. The aircraft was registered to Continental Airlines, Inc., and operated by United Airlines as flight 1475 under the provisions of 14 Code of Federal Regulations Part 121 as a domestic passenger flight. Visual meteorological conditions prevailed for the flight, which operated on an instrument flight rules flight plan. The flight originated from the Dallas/Fort Worth International Airport (DFW), at 0818, and was bound for DEN. The flight crew reported that during descent for landing, they heard a loud bang from the front of the airplane that was believed at the time to be the result of a bird strike. They reported that following the bird strike, the Captain's airspeed and altimeter were inoperative and the First Officer's airspeed and altitude were erratic. The crew referenced the standby instruments but the readings did not make sense to the crew given the aircraft altitude and power settings. The captain stated that he initially lost airspeed and altitude indication and eventually lost all instrument indications. As a result the flight crew used power settings and aircraft configurations along with air traffic control (ATC) call outs of their ground speed to continue the flight to DEN where an uneventful landing was made. It was later reported by the operator that the Captain reported that the standby airspeed indicator readings during the descent seemed to match the ground speed call outs provided by ATC. Examination of the airplane after the incident revealed a large hole in the radome located on the nose of the airplane. The hole measured about 12 inches by 24 inches. A portion of the broken radome became lodged on the left pitot tube and the left pitot tube was bent. Bird remains were found within the left engine, and on the tail of the airplane. Subsequent examination of bird remains confirmed the species of bird as a White Faced Ibis. The airplane was equipped with three separate and independent air data systems: Left, right, and a standby system. Each air data system used independent sensors and displays except that various comparative display messages relied on data from both the left and right systems. The airspeed and altitude recorded by the Flight Data Recorder (FDR) was computed by the left ADIRU based on sensed data from the left pitot probe and static ports. The airspeed and altitude computed by the right ADIRU was based on sensed data from the right pitot probe and static ports. The airspeed and altitude from the right ADIRU and the standby system were not recorded by the FDR. The FDR data showed a rapid loss of airspeed while descending through approximately 11,500 feet pressure altitude travelling at a computed airspeed of approximately 290 knots. Many of the air data parameters exhibited erroneous behavior consistent with a loss of airspeed, including a decrease of airspeed to 45 knots, a decrease of wind data to a value of zero, and an increase of pressure altitude. Additionally, the left angle of attack measurement split from that of the right by about 0.5 degrees. The FDR continued to record altitude and attitude information throughout the remainder of the flight and the loss of attitude reference described by the captain could not be verified through system testing following the incident. The rapid drop in computed airspeed to the "no computed data" (NCD) value of 45 knots was consistent with a complete loss of airspeed reference (pitot pressure) on the left air data system. According to the airplane manufacturer, the rapid drop in computed airspeed would have been consistent with the display of an amber "SPD" flag on the left primary flight display. Testing of the airplane's air data systems after replacement of the left pitot tube and system cleaning did not reveal any anomalies that would explain the loss of all instrument indications described by the captain or the reported unreliability of the First Officer's airspeed and altitude indications.

Flight

Event TypeIncident
Event Time09:09 MDT
Nearest AirportDenver International Airport (45nm)
Runway26
Runway Length12000 ft
Runway Width150 ft
Flight Plan FiledIFR
Flight Plan ActivatedYes
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftBoeing 737-924ER
Tail NumberN37420
Aircraft CategoryAir
DamageMinor
OperatorUnited Airlines
Operating RulePart 121
Engines2
Engine TypeTurbofan
Engine DetailsCfm Intl · CFM56-7B26 · Turbofan · 26300 | Cfm Intl · CFM56-7B26 · Turbofan · 26300
Seats191

People & Injuries

Injury SummaryNo injuries (157 uninjured)
Fatal0
Serious0
Minor0
Uninjured157
Total157
Crew 1Age 51 · First Class · None
Crew 2Age 47 · First Class · None

Conditions

ConditionsVMC
LightDaylight
Wind220° @ 19 kt, gusting 26 kt
Visibility10 sm
CeilingBroken clouds 20000 ft
Temperature / Dew Point52
Altimeter30.17 inHg
Observation Time08:53
Weather SourceWFAC

Appendix: Source Data