LAX88LA048 · Beech 58
Beech 58 · Accident: overrun during landing
From Long Beach International Airport (LGB) to an unrecorded destination
Event
- NTSB case
- LAX88LA048
- 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 58
- Aircraft type
- Beechcraft 58
- 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
- N9106Q
- Operator
- Inzerella, John · private individual
- Onboard fatalities
- Unknown
- Route
- From Long Beach International Airport (LGB), Long Beach, 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
- Overrun
- 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 › Go-around, not performed
- Pilot in command › Planning/decision, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT RPRTD THAT PRIOR TO REACHING THE DESTN, HE RECEIVED AN ADZY ON THE UNICOM FREQ THAT RWY 19 WAS IN USE & THAT THERE WAS A DIRECT X-WIND. DRG ARRIVAL, HE TRIED TO CONTACT UNICOM AGAIN TO GET A WX UPDATE, BUT WAS UNABLE. HE ELECTED TO LND ON RWY 19. RPRTDLY, THE ACFT TOUCHED DOWN ABOUT 500' TO 600' DOWN THE 3400' RWY & THE PLT APPLIED BRAKES, BUT HE WAS UNABLE TO STOP ON THE REMAINING RWY. HE INTENTIONALLY GROUND LOOPED THE ACFT & THE LEFT MAIN GEAR COLLAPSED WHEN THE PLANE SKIDDED OFF THE RWY. AFTER THE PLT EXITED FROM THE ACFT, HE NOTED A SMALL WIND SOCK AT THE APCH END OF THE RWY THAT WAS INDICATING A DIRECT TAILWIND. BEFORE LANDING, HE HAD ESTD THE WIND WAS FROM 270 TO 280 DEG AT 15 TO 20 KTS.NO MECHANICAL PROBLEM WAS RPRTD.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX88LA048
- Event ID
- 20001213X32560
- Case number
- LAX88LA048
- 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: 42a8e9524ad9d1948282f229cf865444326792b31880b4bd47e6cf5ede9bb78a; retrieved 2026-09-23T11:34:04.050Z.