FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN14CA037 · Raytheon Aircraft Company A36

3 Nov 2013 · Hayden, CO, United States

Raytheon Aircraft Company A36 · Accident: loss of control on ground during landing

From Aspen-Pitkin County Airport (Sardy Field) (KASE) to Yampa Valley Airport (KHDN)

Report a problem

Event

NTSB case
CEN14CA037
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
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 A36

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
N981PA
Onboard fatalities
Unknown
Route
From Aspen-Pitkin County Airport (Sardy Field) (KASE), Aspen, COTo Yampa Valley Airport (KHDN), Hayden, CO
Aircraft age
About 8 years (built 2005)
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 · flare/touchdown
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

  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

During a straight in approach to land to runway 28, the pilot flew the airplane with a side slip while maintaining runway centerline. At about ten feet above the runway a gust of wind blew the airplane right of centerline and the pilot corrected the airplane back to the runway's centerline. Upon touchdown, the pilot reported that a crosswind blew the airplane's nose to the right, the airplane touched down 10 to 20 degrees right of runway heading, and exited the right side of the runway, making contact with objects off the runway. Both wings sustained substantial damage. Winds reported on the field about the time of the accident were 250 degrees at 23 knots with gusts to 29 knots. The pilot reported no mechanical malfunctions or failures with the airplane prior to the accident that would have resulted in abnormal operation of the airplane.

Probable cause

The pilot's inadequate compensation for the crosswind, which resulted in a loss of directional control and runway excursion.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN14CA037
Event ID
20131104X02628
Case number
CEN14CA037
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. 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: c3973fbb32e72b78100604396f42279c7ef5761ca84e20f0f2f8f4871e66a1a5; retrieved 2026-09-15T23:04:35.385Z.