Horizon Air Flight 2692
Dornier DO 328-100 · Accident: loss of control on ground/water during landing
From Redding Municipal Airport (RDD) to an unrecorded destination
Event
- NTSB case
- SEA95FA170
- 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
- 0
- 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
Dornier DO 328-100
- Aircraft type
- Dornier DO-328
- 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
- N335PH
- Operator
- Horizon Air
- Onboard fatalities
- Unknown
- Route
- From Redding Municipal Airport (RDD), Redding, CATo not recorded
- 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
- Landing · landing roll
- 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
- Loss of control on ground/water
- 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
- Company/operator management › Condition(s)/step(s) insufficiently defined
- Manufacturer › Procedures/directives, information insufficient
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Shortly after landing, aircraft (acft) began veering slightly left, & 1st officer (F/O, flying pilot) applied rudder for control, then captain (capt) assumed control of acft (above 60 kts). Capt realigned acft to runway centerline & called for condition levers (CL) to minimum (min) at about 60 to 70 kts. At this time, acft began to veer left again. Capt was unable to maintain directional control as acft veered sharply left. Right wing tip & right propeller contacted runway. Acft then collided with a runway sign before stopping partially off runway. Horizon Air procedures indicated CL were to be positioned to maximum (max) when main landing gear touched down. After landing, CL were to be positioned to min at the capt's discretion. With CL in max position, the flightcrew had up to 10 deg of nose-wheel steering through the rudder pedals. With CL in min range, 60 deg of nose-wheel steering authority was available through the tiller. Dornier 328-100 Airplane Operating Manual stated under Standard Landing Procedures that at a 'safe speed,' the CL should be retarded to the min position. Shortly after the accident, Horizon Air changed its landing procedures to state acft must be at taxi speed (below 30 kts) before capt commands CL to min. No mechanical failure/malfunction found.
Probable cause
insufficiently defined information from the manufacturer and operator concerning the landing/taxi procedures.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA95FA170
- Event ID
- 20001207X04369
- Case number
- SEA95FA170
- 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. 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: 8d6f4a2a86c9142b1da2fe57626034b4231c9eea8b312bca18e10e5f77218044; retrieved 2026-09-18T17:58:34.830Z.