FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW91LA026 · Cessna 205

25 Dec 1990 · Medford, OK, United States

Cessna 205 · Accident: loss of control on ground/water while standing

From 6B Airfield (OK68) to 6B Airfield (OK68)

Report a problem

Event

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

Cessna 205

Aircraft type
Cessna 205
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
N8219Z
Operator
Deterding, James L. · private individual
Onboard fatalities
Unknown
Route
From 6B Airfield (OK68)To 6B Airfield (OK68)
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
Standing · engine(s) start-up
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 › Starting procedure, improper

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

NTSB narrative

WHEN THE PILOT ATTEMPTED TO START THE AIRPLANE HE FOUND THAT IT HAD A DEAD BATTERY. HE THEN INSTRUCTED THE NON-RATED PASSENGER ON HOW TO MANIPULATE THE ENGINE CONTROLS AND PROCEEDED TO HAND PROP THE ENGINE. THE ENGINE STARTED AT FULL THROTTLE AND THE PILOT WAS UNABLE TO BOARD THE AIRPLANE AS THE PASSENGER WAS BLOCKING THE ENTRY IN HIS ATTEMPT TO GET OUT. THE AIRPLANE SUBSEQUENTLY ROLLED ACROSS A RUNWAY, THROUGH THE AIRPORT BOUNDARY FENCE, THROUGH A DITCH, AND ACROSS A ROAD INTO AN OPEN FIELD BEFORE THE NOSE GEAR COLLAPSED AND IT NOSED OVER. NO CHOCKS WERE USED DURING THE START.

Probable cause

THE PILOT'S USE OF IMPROPER STARTING PROCEDURES WHICH RESULTED IN THE LOSS OF CONTROL OF THE AIRPLANE. A FACTOR IN THE ACCIDENT WAS THE AIRPLANE'S ENCOUNTER WITH ROUGH TERRAIN DURING THE UNMANNED TAXI.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW91LA026
Event ID
20001212X24763
Case number
FTW91LA026
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: f1d576a2c7b2ac36eabfef186b4ad074817bf1de8e2b64636a424300109ad6b6; retrieved 2026-09-23T04:59:56.851Z.