Horizon Airlines Bombardier DHC-8-401 accident
Bombardier DHC-8-401 · Accident: in flight collision with object on approach
From Seattle–Tacoma International Airport (SEA) to Rogue Valley International-Medford Airport (MFR)
Event
- NTSB case
- SEA03FA024
- 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 DHC-8-401
- Aircraft type
- Bombardier DHC-8
- 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
- N409QX
- Operator
- Horizon Airlines
- Onboard fatalities
- Unknown
- Route
- From Seattle–Tacoma International Airport (SEA), Seattle, WATo Rogue Valley International-Medford Airport (MFR), Medford, OR
- 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 · VFR pattern downwind
- 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
- Window, flight compartment window/windshield › Fractured
- Window, flight compartment window/windshield › Overload
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The aircraft, which was on a downwind for a night visual approach, impacted a flock of Lesser Scaups (diving ducks). The nose structure of the aircraft and the windshield directly in front of the captain received multiple bird strikes. Some of the birds penetrated the aircraft's skin, but there was no direct penetration of the windshield. Although the windshield was not penetrated, hundreds of small pieces of glass were ejected from the most inner of the windshield's three panes, and approximately 70 of these pieces imbedded themselves in the face, forehead, and scalp of the captain. The first officer ultimately completed a successful landing, while using backup flight instruments. The investigation determined that the windshield certification process defined in Part 25 of the Federal Aviation Regulations and the Canadian Aviation Regulations does not take into account the effects of multiple bird strikes on the same windshield.
Probable cause
The fracture and spalling of the inner-most pane of the aircraft's port side windshield while on a downwind for a night visual approach due to an imposed load beyond that required for windshield certification (multiple bird strikes). Factors include a dark night, and a flock of ducks (Lesser Scaups) flying in the location of the visual traffic pattern.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA03FA024
- Event ID
- 20030205X00166
- Case number
- SEA03FA024
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2003-01-09.
- API snapshot SHA-256: 46f3b55ab47ed8513e991d52ab7650a82be4592ec7c0d55c24ab4b01714b2660; retrieved 2026-09-18T15:56:18.086Z.
- The NTSB's operator name is blank for N409QX; the operator shown is the name the NTSB records it doing business as.