American Eagle Airlines Flight 3773
Bombardier Inc CL-600-2C10 · Accident: system/component malfunction/failure (non-power) on approach
From Denver International Airport (DEN) to Chicago O'Hare International Airport (ORD)
Event
- NTSB case
- CEN12LA457
- 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
- Accident
- 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
Bombardier Inc CL-600-2C10
- Aircraft type
- Bombardier CL-600
- 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
- N502AE
- Operator
- American Eagle Airlines
- Onboard fatalities
- Unknown
- Route
- From Denver International Airport (DEN), Denver, COTo Chicago O'Hare International Airport (ORD), Chicago, IL
- 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
- Approach
- 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
- System/component malfunction/failure (non-power)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
While on approach to the airport, the flight crew smelled smoke in the airplane. The airplane landed without incident and the crew directed an emergency ground egress. During the ground egress, one passenger broke her ankle. A postflight review of the airplane found that the airplane was operating on a single environmental pack that failed during the final approach, resulting in ambient air entering the airplane via the ram air inlet. An assessment of the airplane did not find any on-board sources of smoke. However, smoke from a large house fire was present along the airplane's approach path and likely was the source of smoke detected by the crew.
Probable cause
The emergency ground egress during which a passenger broke her ankle. Contributing to the accident was the failure of the environmental system, which allowed smoke from a nearby house fire to enter the airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN12LA457
- Event ID
- 20120719X94744
- Case number
- CEN12LA457
- 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: local date, investigation status, damage. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2012-07-19.
- API snapshot SHA-256: 20105a7274f6131f5bf95b219d9d63a311116c8864e4c911ce1b2c68c0d17df0; retrieved 2026-09-15T18:59:16.432Z.