FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX84FA116 · Beech P35

27 Dec 1983 · MCKITTRICK, CA, United States

Flying Particles Beech P35 · Accident: loss of control in flight en route

From Livermore Municipal Airport (LVK) to Imperial County Airport (IPL)

Report a problem

Event

NTSB case
LAX84FA116
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
4 · 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

Beech P35

Aircraft type
Beechcraft 35
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
N258C
Onboard fatalities
Unknown
Route
From Livermore Municipal Airport (LVK), Livermore, CATo Imperial County Airport (IPL), Imperial, 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
En route · climb to cruise
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
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall/spin
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 › Airspeed, not maintained
  • Pilot in command › Remedial action, inadequate
  • Pilot in command › Stall/spin, inadvertent

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

NTSB narrative

AFTER DEPARTING ON AN IFR X-COUNTRY FLT, THE ACFT WAS CLIMBING FROM 7000 TO 11,000 FT, WHEN THE PLT WAS ASKED (AT 1126) TO INCREASING HER RATE OF CLIMB BECAUSE OF OTHER TRAFFIC. AT 1926:13, SHE WAS ASKED TO SAY HER ALT & SHE SAID SHE WAS AT 9500 FT. AT 1926:32, THE PLT WAS ASKED IF SHE WAS CLIMBING TO 11,000 FT & SHE REPLIED 'AS FAST AS POSSIBLE.' AT 1926:21, ATC AGAIN ASKED THE PLT TO REPORT HER ALT. THE ONLY REPLY WAS THE SOUND OF AN INTERMITTENT OPEN MICROPHONE. SUBSEQUENT ATTEMPTS TO ESTABLISH RADIO CONTACT WERE UNSUCCESSFUL. THE LAST MODE C REPLY WAS AT 1129:27 AT 10,200 FT. RADAR CONTACT WAS LOST 1 MIN LATER. GROUND WITNESSES BRIEFLY OBSERVED THE ACFT AT AN ESTIMATED 800 TO 1500 FT AGL. THE ACFT THEN ROLLED TO THE RIGHT TO AN EXTREME NOSE LOW ATTITUDE & CRASHED.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record LAX84FA116
Event ID
20001214X45319
Case number
LAX84FA116
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: a7de699cdec874192b90059bbe42b24ebbfe2ae0e8496224e3765c7d17726a77; retrieved 2026-09-21T05:42:57.239Z.