LAX91LA328 · Beech 76
Altair Aviation Beech 76 · Accident: airframe, component or system failure during landing
From 2Q3 · Davis, CA to an unrecorded destination
Event
- NTSB case
- LAX91LA328
- 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 76
- Aircraft type
- Beechcraft 76
- 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
- N6045M
- Operator
- Altair Aviation
- Onboard fatalities
- Unknown
- Route
- From 2Q3 · Davis, CATo not recorded
- 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
- Landing · landing roll
- 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
- Landing gear, main gear spring › Fatigue
- Manufacturer › Acft/equip, inadequate aircraft component
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE CERTIFICATED AIRLINE PILOT/FLIGHT INSTRUCTOR, THE PILOT-IN-COMMAND, WAS DEMONSTRATING A SINGLE ENGINE LANDING TO A CERTIFICATED PRIVATE PILOT/DUAL INSTRUCTIONAL STUDENT. DURING THE LANDING ROLL, THE AIRPLANE BEGAN TO DRIFT TO THE RIGHT. THE PIC ATTEMPTED TO CORRECT THE DRIFT BY INCREASING THE RIGHT ENGINE POWER AND APPLYING LEFT RUDDER. THE AIRPLANE RIGHT WING BEGAN TO SETTLE TO THE GROUND AND THE PILOT SHUT DOWN BOTH ENGINES. THE AIRPLANE RECEIVED DAMAGE TO THE RIGHT GEAR FLAPS AND PROPELLER. AN INSPECTION REVEALED THAT THE RIGHT GEAR STRUT WAS BROKEN AT AN INSPECTION HOLE PROVIDED BY THE MANUFACTURER. THE GEAR STRUT WAS THE SUBJECT OF A MANUFACTURER'S SERVICE BULLETIN AND SUBSEQUENT FAA AIRWORTHINESS DIRECTIVE THAT REQUIRED AN INSPECTION FOR CRACKS. MAINTENANCE PERSONNEL HAD RECEIVED THE SERVICE BULLETIN BUT HAD NOT SCHEDULED AN INSPECTION.
Probable cause
A FATIGUE FAILURE OF THE LANDING GEAR STRUT DUE TO AN INADEQUATE DESIGN BY THE MANUFACTURER. CONTRIBUTING TO THE ACCIDENT WAS MAINTENANCE PERSONNEL NOT HAVING COMPLETED AN INSPECTION OF THE GEAR STRUT, IN ACCORDANCE WITH THE MANUFACTURER'S SERVICE BULLETIN.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX91LA328
- Event ID
- 20001212X17615
- Case number
- LAX91LA328
- 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: 9c5233f304b8ddcfd4d75af909e9ca2468220fde3f6b65d75a6e2efd259f478a; retrieved 2026-09-23T03:54:06.972Z.