LAX91LA123 · Beech B95
Beech B95 · Accident: airframe, component or system failure en route
From Hemet Ryan Airport (HMT) to John Wayne Orange County International Airport (SNA)
Event
- NTSB case
- LAX91LA123
- 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
Beech B95
- Aircraft type
- Beechcraft 95
- 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
- N2712Y
- Operator
- Joseph Sheble III
- Onboard fatalities
- Unknown
- Route
- From Hemet Ryan Airport (HMT), Hemet, CATo John Wayne Orange County International Airport (SNA), ORANGE COUNTY, 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 · 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
- Airframe, component or system failure
- 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 › Emergency procedure, not followed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE CERTIFICATED COMMERCIAL PILOT AND TWO PASSENGERS WERE ENROUTE TO THEIR DESTINATION AIRPORT ON AN INSTRUMENT FLIGHT PLAN, WHEN A COMPLETE ELECTRICAL FAILURE OCCURRED. THE PILOT FAILED TO NOTICE THAT BOTH AMMETERS WERE READING ZERO DUE TO THE FAILURE OF BOTH CURRENT LIMITERS IN THE CHARGING SYSTEM. THE BATTERY WAS DEPLETED AND ALL ELECTRICAL POWER LOST. THE PILOT ELECTED TO LAND BEFORE DARK AND FAILED TO FOLLOW THE EMERGENCY GEAR EXTENSION PROCEDURE TO FULLY EXTEND THE LANDING GEAR. THE GEAR COLLAPSED UPON LANDING ON A TAXIWAY AT A MILITARY AIR FORCE BASE.
Probable cause
FAILURE OF THE PILOT TO FOLLOW THE EMERGENCY GEAR EXTENSION PROCEDURE TO FULLY EXTEND THE LANDING GEAR. CONTRIBUTING TO THE ACCIDENT WAS THE FAILURE OF THE PILOT TO MONITOR THE CONDITION OF THE ELECTRICAL POWER SYSTEM, LEADING TO THE COMPLETE LOSS OF ELECTRICAL POWER.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX91LA123
- Event ID
- 20001212X16483
- Case number
- LAX91LA123
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1991-02-10.
- API snapshot SHA-256: 6abca21b48c2a46378ecec0c2453828ec3c8d908b8261851c2c5530a68fb7b96; retrieved 2026-09-23T04:47:28.913Z.