FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Ameriflight Beech C-99 accident

16 Nov 1994 · Avenal, CA, United States

Beech C-99 · Accident: loss of control in flight en route

From Hollywood Burbank/Bob Hope Airport (BUR) to Oakland San Francisco Bay Airport (OAK)

Report a problem

Event

NTSB case
LAX95FA035
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
1 · 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
Charter & commuter
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 C-99

Aircraft type
Beechcraft C-99
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
N63995
Operator
Ameriflight
Onboard fatalities
Unknown
Route
From Hollywood Burbank/Bob Hope Airport (BUR), Burbank, CATo Oakland San Francisco Bay Airport (OAK), Oakland, 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 135: Air Taxi & Commuter
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 · 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
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 › Aircraft control, not maintained
  • Reason for occurrence undetermined

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

NTSB narrative

THE PILOT WAS ON AN IFR FLIGHT PLAN LEVEL AT 10,000 FEET MSL IN VFR CONDITIONS. THE ATP RATED PILOT WAS THE SOLE OCCUPANT, AND THERE WAS NO AUTOPILOT INSTALLED IN THE BEECH C-99 AIRLINER. ABOUT 10 MINUTES AFTER A HAND-OFF FROM LOS ANGELES CENTER TO OAKLAND CENTER WAS ACKNOWLEDGED, RADAR CONTACT WAS LOST AT 0239 HOURS. A REVIEW OF THE RADAR DATA REVEALED THAT OVER THE LAST 4 MINUTES THE AIRPLANE'S ALTITUDE INCREASED TO 10,500 FEET, THEN IT STARTED A LEFT DESCENDING TURN WITH A MAXIMUM DIAMETER OF ABOUT 2.1 NM. THE LAST RADAR RETURNS INDICATE THE AIRPLANE CONTINUING THE LEFT TURN AND DESCENDING THROUGH 5,600 FEET MSL, WITH A DESCENT RATE OF ABOUT 18,000 FEET PER MINUTE. THERE WAS NO EVIDENCE OF A MECHANICAL MALFUNCTION OF THE AIRCRAFT, ENGINES, OR PROPELLERS.

Probable cause

loss of aircraft control at night by the pilot for unknown reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX95FA035
Event ID
20001206X02611
Case number
LAX95FA035
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: fd559c24b35ce1ca0c57b6ace61ac3b813bcf11213e11c16fd6386bff8ed41e2; retrieved 2026-09-18T13:46:37.464Z.