WPR16LA125 · Bell 206 L1
Bell 206 L1 · Accident: fuel related en route
From Corona Municipal Airport (AJO) to Mammoth Yosemite Airport (MMH)
Event
- NTSB case
- WPR16LA125
- 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
- Unknown
- 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
Bell 206 L1
- 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
- N1076Y
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Corona Municipal Airport (AJO), Corona, CATo Mammoth Yosemite Airport (MMH), Mammoth Lakes, CA
- Aircraft age
- About 36 years (built 1980)
- 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
- Defining eventThe 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
- Fuel related
- 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
- Aircraft › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The private pilot departed on a cross-country flight with two passengers onboard the helicopter, which had been filled with 110 gallons of fuel (88 gallons of which were in the aft tank) before departure. The pilot reported that, after encountering headwinds that were about 15 knots greater than anticipated and turbulence for more than 2 hours, he saw that the helicopter was low on fuel and decided to land at a nearby airport. He began a descent from 12,000 ft mean sea level (msl), but as he passed through 10,000 ft msl, he heard a "violent explosion in the engine compartment," followed by the illumination of the engine-out indication light. The pilot immediately initiated an autorotation and made two unsuccessful attempts to restart the engine during the descent. He flared the helicopter at 2,000 ft to avoid settling into a crater, and it subsequently impacted terrain hard. Paint transfer signatures on one of the main rotor blades indicated that they likely contacted and severed the tailboom during landing.
The pilot stated that he did not pull the fuel pump circuit breakers before or during the accident flight; however, the unbreeched aft fuel tank was void of fuel when first responders examined it shortly after the accident, and the fuel pump circuit breakers were found in the "off" position. Further, operational tests of the fuel system and engine did not reveal any blockages or mechanical malfunctions. Fuel computations showed that the engine consumed 88 gallons of fuel, the quantity that would have been in the aft tank at the time of departure, and the pilot reported that he customarily disengages the fuel pumps after each flight. It is likely that the pilot's improper fuel management, possibly from departing with the fuel pumps in the "off" position, prevented fuel trapped in the forward tanks from reaching the engine and resulted in fuel starvation.
The pilot had planned the flight around 15-knot winds despite multiple weather forecasts issued before his departure that indicated the presence of about 30-knot headwinds along his flight route. It is likely that the pilot's poor preflight weather and fuel planning resulted in greater-than-anticipated fuel consumption, which led to the low fuel state and the pilot's decision to divert to a closer airport.
The pilot did not experience any control issues throughout the long autorotation from 10,000 ft, and weather reports indicated that he would not have encountered any visibility restrictions during the descent, so he should have had sufficient time to properly flare the helicopter and land. However, he chose to initiate a flare at 2,000 ft, which likely reduced the rotor rpm and led to hard impact with terrain.
Probable cause
The pilot’s improper preflight weather planning, fuel planning, and fuel management, which resulted in fuel starvation and a loss of engine power. Contributing to the severity of the accident was the pilot's initiation of the landing flare at a high altitude, which led to a subsequent hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR16LA125
- Event ID
- 20160615X64926
- Case number
- WPR16LA125
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: e511843f2a182f5df9e1e998414fb9f2b4a04cbde6a6d301edae38167446f780; retrieved 2026-09-16T03:31:05.523Z.