DEN05CA107 · Taylorcraft BC12-65
Taylorcraft BC12-65 · Accident: loss of control in flight during landing
From 36U · Heber City, UT to Roosevelt Municipal Airport (74V)
Event
- NTSB case
- DEN05CA107
- 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
Taylorcraft BC12-65
- Aircraft type
- Taylorcraft BC12
- 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
- N36044
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 36U · Heber City, UTTo Roosevelt Municipal Airport (74V), Roosevelt, UT
- 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 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
- 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 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
- Pilot in command › Aircraft control, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot said he listened to the local weather observation and noted uncharacteristic northerly winds of 10 knots, gusting to 17 knots at his time of arrival. He said he then performed a crosswind landing on runway 25 (6,500 feet by 75 feet, dry asphalt). After approximately a 20 foot ground roll, a gust of wind lifted the aircraft off the runway and pivoted it left (counterclockwise). The airplane then touched down off the side of the runway, impacted a rock, and nosed down. The pilot exited the aircraft and pushed it back upright to stop fuel from leaking. An examination of the airplane showed no anomalies. At 1653, the wind conditions at Vernal, Utah (VEL), located 26 nautical miles east of the accident site, were 240 degrees at 8 knots. The wind conditions 33 minutes prior to the accident were 190 degrees at 13 knots, gusting 16 knots. The crosswind component at that time was calculated as 11 knots.
Probable cause
the pilot's failure to maintain control of the aircraft during landing. A factor contributing to the accident was the crosswind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN05CA107
- Event ID
- 20050809X01185
- Case number
- DEN05CA107
- 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, coordinates. 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: 1045b117381d901dec07318c29cc4be553ae5a2a5bd812c0c85d425994894fd6; retrieved 2026-09-22T05:40:00.385Z.