FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN00LA100 · Culver LFA

2 Jun 2000 · Moab, UT, United States

A Pair of Jacks Culver LFA · Accident: airframe, component or system failure during takeoff

From Canyonlands Regional Airport (CNY) to Fremont County Airport (1V6)

Report a problem

Event

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

Culver LFA

Aircraft type
Culver LFA
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
N34783
Onboard fatalities
Unknown
Route
From Canyonlands Regional Airport (CNY)To Fremont County Airport (1V6), Canon City, CO
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
Takeoff · roll/run
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
Airframe, component or system failure
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

  • Landing gear, normal brake system › Overtemperature
  • Landing gear, wheel › Locked

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

NTSB narrative

The pilot was taking off on runway 21. As he raised the tail for lift off (about 50 mph), the airplane 'abruptly swerved to left (90 degrees), [departed] the runway, crossed a dirt border about 6 feet wide, flipped on its back, and slid down to the bottom of a drainage ditch between the runway and the adjacent taxiway.' The pilot said the airplane was equipped with Goodyear 'expanded tube' brakes, known to lock up if overheated (brakes were used for landing and for taxi to takeoff). An airport mechanic attempted to turn the left main wheel by hand shortly after the accident, and found the wheel to be binding. The right wheel turned freely. Later, he tried again and the wheel turned freely.

Probable cause

Overheating of the left brake, causing the wheel to lock. Factors were the pilot not being able to maintain directional control, a dirt berm, and a drainage ditch.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN00LA100
Event ID
20001212X21202
Case number
DEN00LA100
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: 76ed601ecb67caf9f1db6789ee59c890d7331ff60cf98967c17d912100ccb058; retrieved 2026-09-22T12:50:56.956Z.