IAD05LA129 · Dassault/Sud Falcon 20D
Dassault/Sud Falcon 20D · Accident: in flight collision with object during takeoff
From Lorain County Regional Airport (LPR) to St. Louis Lambert International Airport (STL)
Event
- NTSB case
- IAD05LA129
- 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
- Charter & commuter
- 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
Dassault/Sud Falcon 20D
- Aircraft type
- Dassault/sud FALCON 20
- 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
- N821AA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lorain County Regional Airport (LPR), Lorain, OHTo St. Louis Lambert International Airport (STL), ST LOUIS, MO
- 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 135: Air Taxi & Commuter
- 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
- Takeoff
- First occurrenceThe 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
- In flight collision with object
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Object › Bird(s)
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The small, twin-engine business jet was about 15 feet above the runway on takeoff, when a flock of birds from both sides of the runway flew up in front of the airplane. The number two engine "surged," and "loud reports" were heard before the copilot noted a complete loss of power on the number two engine instruments. The airplane climbed for about 10 seconds, before the copilot observed the gas producer (N1) gauge on the number one engine decay through 50 percent. The stall warning horn sounded, and the pilot adjusted the flight controls for landing. The airplane contacted the runway with the landing gear retracted, overran the runway, struck a fence, crossed a road, and came to rest in a cornfield about 1,000 feet beyond the initial point of ground contact. Post accident examination of both engines revealed evidence and damage consistent with multiple bird ingestion.
Probable cause
The ingestion of multiple birds in each engine at takeoff, which resulted in a complete loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD05LA129
- Event ID
- 20050927X01535
- Case number
- IAD05LA129
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 5ccbb5702f523152c9ded8d67acaa3d8bcde183a0b22ca7dd393132bf0011513; retrieved 2026-09-18T14:59:05.079Z.