CEN26LA127 · Raytheon Aircraft Company B36TC
Raytheon Aircraft Company B36TC · Accident: loss of control on ground during landing
From River Falls Airport (H81) to Durango La Plata County Airport (DRO)
Event
- NTSB case
- CEN26LA127
- 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
- General aviation
- 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
Raytheon Aircraft Company B36TC
- Aircraft type
- Beechcraft 36
- 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
- N2251Q
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From River Falls Airport (H81), Amarillo, TXTo Durango La Plata County Airport (DRO), Durango, CO
- Aircraft age
- About 29 years (built 1997)
- 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 91: General Aviation
- 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
- 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
- Loss of control on ground
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that a crosswind of 28 knots, gusting to 44 knots, prevailed at the destination airport during the approach. As the airplane crossed the runway 21 threshold, it encountered windshear which resulted in a hard landing. The pilot subsequently lost directional control, and the airplane departed the runway pavement which resulted in substantial damage to the fuselage, left wing, and left aileron. The pilot stated there were no mechanical malfunctions or failures before the accident. He added that he should not have attempted to land with the reported wind conditions. About 10 minutes before the accident, the destination airport Automated Surface Observing System recorded a peak wind from 300° at 39 knots.
Probable cause
The pilot’s improper landing flare and subsequent loss of directional control while attempting to land during high crosswind conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN26LA127
- Event ID
- 20260227202560
- Case number
- CEN26LA127
- 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: investigation status, cause areas. 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: 5750826f16daa91000d6a47ef59df045c00cc655901c827eb5839fa9f5579921; retrieved 2026-09-16T20:51:59.517Z.