Paradise Helicopters McDonnell Douglas Helicopter 369E accident
McDonnell Douglas Helicopter 369E · Accident: fuel exhaustion on approach
From Hilo International Airport (PHTO) to Hilo International Airport (PHTO)
Event
- NTSB case
- WPR13CA342
- 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
- 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
McDonnell Douglas Helicopter 369E
- Aircraft type
- McDonnell Douglas 369
- 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
- N500PH
- Operator
- Paradise Helicopters
- Onboard fatalities
- Unknown
- Route
- From Hilo International Airport (PHTO), Hilo, HITo Hilo International Airport (PHTO), Hilo, HI
- 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
- Approach
- 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 exhaustion
- 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 from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
During a round trip tour flight, the pilot determined that the fuel state was low, and decided to return to the airport. The flight entered the airport environment and the pilot requested priority handling for a low fuel state. The engine subsequently lost power and the pilot initiated an autorotation to a field at the approach end of the runway. During the landing the helicopter's skid collapsed and the helicopter rolled over on to its right side which resulted in substantial damage. The operator indicated that there were no preimpact malfunctions or failures with the engine or airframe that would have precluded normal operation.
Probable cause
A loss of engine power due to the pilot's improper planning and mismanagement of the fuel supply, which resulted in fuel exhaustion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR13CA342
- Event ID
- 20130726X72243
- Case number
- WPR13CA342
- 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, coordinates. 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: 77a910d5194dd2ad87bac8eee47941dbb672f4bcd23bed7beb055917322899b7; retrieved 2026-09-15T22:20:13.431Z.