FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX83LA449 · Cessna 120

19 Sept 1983 · Lone Pine, CA, United States

Cessna 120 · Accident: loss of control on ground/water during takeoff

From SALINE VALLEY, CA to Eastern Sierra Regional Airport (BIH)

Report a problem

Event

NTSB case
LAX83LA449
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 120

Aircraft type
Cessna 120
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
N76744
Operator
Unknown
Onboard fatalities
Unknown
Route
From SALINE VALLEY, CATo Eastern Sierra Regional Airport (BIH), Bishop, CA
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
Destroyed

Cause areas

  • Pilot in command › Unsuitable terrain or takeoff/landing/taxi area, selected

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

NTSB narrative

THE ACFT COLLIDED WITH A SAND BANK DURING TAKEOFF ROLL, A FUEL LEAK DEVELOPED AND THE ACFT WAS CONSUMED BY FIRE. THE PILOT WAS ATTEMPTING A TAKEOFF ON A DRY LAKE BED WHEN THE ACFT HIT A FEW SAND BUMPS. THE NOSE WENT UP IN THE AIR ANDTHE ACFT CAME BACK DOWN HARD ON THE LEFT MAIN GEAR. THE LEFT WING WAS DAMAGED, FUEL LEAKED AND A FLASH FIRE STARTED. THEOCCUPANTS AND A DOG GOT OUT UNINJURED BEFORE THE ACFT WAS BURNED. THE PILOT AND HIS FRIENDS HAD TRIED TO SMOOTH THE LAKE BED BEFORE THE FLT BY FILLING RUTS AND MEASURING OFF THE SMOOTHEST PART FOR THE TAKEOFF. THE AREA ALLOCATED WAS 900FT LONG. THE PILOT HAD DETERMINED THE TAKEOFF DISTANCE TO BE 830 FT FOR THE ACFT AT GROSS WEIGHT. HE STATED THAT HE THOUGHT THE ACFT WAS AIRBORNE WHEN THE LEFT WHEEL HIT THE RISE IN THE TERRAIN JUST BEYOND THE DEPARTURE END OF THE STRIP.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record LAX83LA449
Event ID
20001214X44600
Case number
LAX83LA449
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: 0563f647e653535852026099818c4d2b72fff4dbd8944a48126e0b286ceb00ab; retrieved 2026-09-23T21:20:32.467Z.