Permian Aviation Bell 206B accident
Bell 206B · Accident: total loss of engine power (mechanical failure) during landing
From San Pedro, CA to Long Beach International Airport (LGB)
Event
- NTSB case
- LAX84FA483
- 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
- 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
Bell 206B
- Aircraft type
- Bell 206
- Category
- Helicopter
- 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
- N7111J
- Operator
- Permian Aviation
- Onboard fatalities
- Unknown
- Route
- From San Pedro, CATo Long Beach International Airport (LGB)
- 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
- Landing · flare/touchdown
- 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
- Total loss of engine power (mechanical 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
- Company maintenance personnel › Maintenance, compliance with ad, not performed
- Turbine assembly, turbine wheel › Failure, total
- Turbine assembly, turbine wheel › Fatigue
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT EXPERIENCED A POWER LOSS DURING FLARE FOR LANDING. THE PLT PULLED COLLECTIVE TO SOFTEN THE TOUCHDOWN FROM 30 FTAGL BUT THE LANDING WAS HARD. POST ACCIDENT EXAMINATION OF THE ENGINE SHOWED A FAILURE OF THE #1 TURBINE DISC. LAB EXAM OF THE DISC SHOWED FAILURE FROM OVERHEATING AND FATIGUE. AN AD WAS IN EXISTANCE WITH THE PURPOSE OF PREVENTIG AFTER FIRES FROM INCOMPLETE FUEL CUT OFF DURING ENGINE SHUTDOWN BY ADJUSTING THE FUEL CONTROL QUADRANT TO READ MINUS 2 DEGREESWITH THE THROTTLE AGAINST THE MINIMUM STOP. INVESTIGATION SHOWED THE FUEL CONTROL QUADRANT ON THE ACCIDENT ACFT READ '0'DEGREES WITH THE THROTTLE LEVER AGAINST THE MINIMUM STOP.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX84FA483
- Event ID
- 20001214X41103
- Case number
- LAX84FA483
- 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: c2acf32baf8c725dfed3761c43b82a99fd1f86c119ef6c41e30185f455de34f1; retrieved 2026-09-18T20:37:07.654Z.