FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN14CA018 · Beech A36 UNDESIGNAT

13 Oct 2013 · Telluride, CO, United States

Beech A36 UNDESIGNAT · Accident: loss of control in flight during takeoff

From Telluride, CO to Gunnison Crested Butte Regional Airport (GUC)

Report a problem

Event

NTSB case
CEN14CA018
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

Beech A36 UNDESIGNAT

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
N26RG
Operator
Unknown
Onboard fatalities
Unknown
Route
From Telluride, COTo Gunnison Crested Butte Regional Airport (GUC), Gunnison, CO
Aircraft age
About 26 years (built 1987)
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
Takeoff
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 in flight
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

  • Aircraft › Aircraft oper/perf/capability

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

NTSB narrative

The pilot stated the reported winds near his departure time were 140 degrees at 24 knots, and he elected to depart from runway 27. During climb out, shortly after he rotated, the airplane weathervaned hard to the left and the stall warning horn sounded. The pilot felt a strong gust of wind as he attempted to clear rising terrain, and thought he encountered a strong down draft or rotor, followed by the airplane impacting terrain. Wind recorded five minutes before the accident was from 130 degrees at 15 knots, gusting to 29 knots.

Probable cause

The pilot's decision to take off in gusting tailwinds resulting in exceeding the performance capabilities of the airplane and subsequent loss of control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN14CA018
Event ID
20131024X45243
Case number
CEN14CA018
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: f8b375339d7946ca823cda1c300cad9e45dee60cd26ac0a6b4a8ffafa579553e; retrieved 2026-09-15T23:01:22.480Z.