FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX03LA002 · Kline KSE5A

7 Oct 2002 · Sedona, AZ, United States

Kline KSE5A · Accident: loss of control on ground/water during takeoff

From Sedona Airport (KSEZ) to KE76 · Rimrock, AZ

Report a problem

Event

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

Kline KSE5A

Aircraft type
Kline KSE5
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
N589D
Operator
Unknown
Onboard fatalities
Unknown
Route
From Sedona Airport (KSEZ), Sedona, AZTo KE76 · Rimrock, AZ
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
Loss of control on ground/water
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 › Directional 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

During takeoff, the pilot applied full power about 150 feet down the runway. The amateur-built airplane veered left and proceeded off the runway. The pilot stated that as the airplane veered off the runway, he applied brakes and felt the left wheel lock. The pilot reduced the power, but the airplane continued for about 100 feet until it encountered a ditch. The airplane nosed over and came to rest inverted. Winds at the time of the accident were from 250 degrees at 8 knots, gusting to 17 knots. The pilot/builder attributed the accident to his improper installation of a motorcycle wheel, which resulted in the airplane's left wheel locking after he applied the brakes.

Probable cause

the pilot's failure to compensate for the wind conditions resulting in a loss of directional control during the takeoff roll. A contributing factor was the pilot's incorrect installation of the left wheel, which resulted in a locked left wheel when the brakes were applied.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX03LA002
Event ID
20021007X05287
Case number
LAX03LA002
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: 9ff2bfebe1c5604800440aa3364db25c67ea8f611ff7109b687618f41cc89cba; retrieved 2026-09-22T10:07:33.694Z.