Corporate Flight Management Bombardier Inc CL-600-2B19 accident
Bombardier Inc CL-600-2B19 · Accident: birdstrike en route
From Dallas Fort Worth International Airport (DFW) to Mid Delta Regional Airport (GLH)
Event
- NTSB case
- CEN25LA070
- 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
- Event fatalities
- Unknown
- 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
Bombardier Inc CL-600-2B19
- 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
- N438SW
- Operator
- Corporate Flight Management
- Onboard fatalities
- Unknown
- Route
- From Dallas Fort Worth International Airport (DFW), Dallas / Ft. Worth, TXTo Mid Delta Regional Airport (GLH), Greenville, MS
- Aircraft age
- About 24 years (built 2001)
- 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
- 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
- Substantial
Cause areas
- Environmental issues › Physical environment
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The captain reported that about 5 miles north of the destination airport, at 3,000 ft mean sea level, the flight encountered a flock of birds. Due to the night lighting condition, the flight crew did not see the birds until they struck the airplane. The impact caused the captain’s primary flight display (PFD) to become unusable. The first officer’s PFD and the standby instruments continued to operate normally. The engines were not affected, and the flight landed without further incident. There were no injuries to the passengers or crew. A postaccident examination revealed substantial damage to the forward fuselage including a bulkhead, a frame, and the skin. Additional damage to the radome, right winglet, and vertical stabilizer was minor. Seven samples examined by the Smithsonian Feather Identification Lab were identified as being from Greater White-Fronted Geese.
Probable cause
Bird strike.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN25LA070
- Event ID
- 20250106199509
- Case number
- CEN25LA070
- 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, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2025-01-03.
- API snapshot SHA-256: 9ddd4cd8e8f31d3231094019a8cf64aa10e597f8ee4114a5ef183d3adb205f92; retrieved 2026-09-16T19:34:58.790Z.