WPR11FA426 · Enstrom 280FX
Sky Park Helicopters Enstrom 280FX · Accident: hard landing
From 36U · Heber, UT to 36U · Heber, UT
Event
- NTSB case
- WPR11FA426
- 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
Enstrom 280FX
- Aircraft type
- Enstrom 280
- 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
- N280AD
- Operator
- Sky Park Helicopters
- Onboard fatalities
- Unknown
- Route
- From 36U · Heber, UTTo 36U · Heber, UT
- 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 · flare/touchdown
- 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
- Hard landing
- 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 operator was selling helicopter rides at a fly-in. After one such ride, a pilot, who was acting as a ground crewmember, measured the fuel level in the tanks with a calibrated wooden stick while the engine was running and the rotor blades were turning. He determined that about 8 gallons of fuel remained, which was sufficient for the next ride. About 9 minutes after takeoff, the engine lost power. Witnesses reported seeing the helicopter flying low when they heard the engine “sputter” or “pop.” The pilot reported that he performed an autorotation to a field; the helicopter landed hard on sloping terrain and rolled over onto its right side. Examination of the wreckage revealed that the engine lost power as a result of fuel exhaustion. Postaccident examination of the airframe and engine revealed no evidence of mechanical malfunctions or failures that would have prevented normal operation.
The helicopter manufacturer provided a wooden stick for pilots to dip a fuel tank during preflight to determine the total quantity of fuel available for flight. A representative of the helicopter manufacturer stated that caution must be exercised when measuring fuel quantity with a stick, because the irregular shape of each fuel tank can make it difficult to interpret the actual fuel quantity at lower levels. It is likely that the pilot who checked the fuel level before the accident flight did not accurately determine the amount of fuel in the tanks. The helicopter was equipped with a fuel gauge mounted on the instrument panel in the cockpit that would have provided the accident pilot with a direct reading of the helicopter’s fuel quantity.
The helicopter was being flown with the two cabin doors removed, an approved operation according to the rotorcraft flight manual. The helicopter left the factory with individual seat belts and shoulder restraints for three occupants. The passenger reported that someone buckled her and her son into the same lap belt; no shoulder strap was used. During postaccident examination, it was noted that the buckle half of the lap belt for the center seat had been removed. The center seat single-strap shoulder harness was found attached to the buckle half of the right seat lap belt. The right seat Y-type shoulder harness was found stowed behind the right seat back cushion. The first responders found the right seat occupant under the helicopter with his legs still in the cabin. Both passengers sustained serious injuries. It is likely that the lack of separate lap belt/shoulder harness assemblies for the two passengers increased the severity of their injuries.
Probable cause
The pilot’s failure to ensure that there was sufficient fuel onboard to conduct the flight, which resulted in a loss of engine power due to fuel exhaustion. Contributing to the severity of the passengers’ injuries was the operator’s failure to provide adequate restraints for the passengers.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR11FA426
- Event ID
- 20110903X53441
- Case number
- WPR11FA426
- 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: 83e404a039777bb5c0de4e0dac0f0905b04c032902c1cd09983035d5610341f5; retrieved 2026-09-15T16:41:39.740Z.