LAX83FA279 · Beech 95-B55
Beech 95-B55 · Accident: loss of control in flight en route
From Hollywood Burbank/Bob Hope Airport (BUR) to Paso Robles Municipal Airport (PRB)
Event
- NTSB case
- LAX83FA279
- 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
- 2 · 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
- Instrument Meteorological Cond
Beech 95-B55
- Aircraft type
- Beechcraft 55
- 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
- N6610K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Hollywood Burbank/Bob Hope Airport (BUR), Burbank, CATo Paso Robles Municipal Airport (PRB), Paso Robles, 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
- 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
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT CRASHED IN A RESIDENTIAL AREA AFTER A LOSS OF CONTROL BY THE PLT. THE ACFT WAS CLIMBING THROUGH AN OVERCAST IN IFR CONDITIONS AND LAST REPORTED 'FOUR' IN RESPONSE TO A REQUEST FOR ALTITUDE. THIS WAS THE LAST RADIO TRANSMISSION RECEIVED FROM THE FLT. THE ACFT WAS SEEN BY WITNESSES DIVING VERTICALLY FROM THE CLOUDS. IT LEVELED OFF FOR A SHORT WHILE AND THEN WENT INTO A NOSE-UP 90 DEGREE BANK AT LOW ALTITUDE. IT CONTACTED THE GROUND IN A 90 DEGREE LEFT BANK AND CARTWHEELED. A TOTAL OF FIVE SINGLE FAMILY RESIDENCES, THREE AUTOMOBILES AND SOME LANDSCAPING RECEIVED DAMAGE IN THE ACCIDENT. NO PERSONS ON THE GROUND WERE INJURED. THE WEATHER WAS REPORTED AS 1500 FT OVERCAST WITH TOPS 4000 TO 4300 FT.VISIBILITY 2 MILES IN HAZE. POST ACCIDENT EXAMINATION REVEALED BOTH ENGINES OPERATING AT IMPACT. ALL ACFT COMPONENTS WERE ACCOUNTED FOR AT THE ACCIDENT SITE. SOME SMALL ITEMS OF FAIRING AND ALUMINUM SKIN WERE FOUND ALONG THE FLT PATH FORA DISTANCE OF 2 BLOCKS.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX83FA279
- Event ID
- 20001214X43376
- Case number
- LAX83FA279
- 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: 5f0aab9353611f62e3ec5091e81c8af11ce84a430781228ed6750a871f129fa1; retrieved 2026-09-21T06:40:57.698Z.