WPR10FA085 · Eurocopter AS350BA (FX2)
Sunshine Helicopters Eurocopter AS350BA (FX2) · Accident: loss of engine power (total) during autorotation
From Kahului International Airport (OGG) to Kahului International Airport (OGG)
Event
- NTSB case
- WPR10FA085
- 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
Eurocopter AS350BA (FX2)
- Aircraft type
- Eurocopter AS350
- 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
- N87EW
- Operator
- Sunshine Helicopters
- Onboard fatalities
- Unknown
- Route
- From Kahului International Airport (OGG), Kahului, HITo Kahului International Airport (OGG), Kahului, 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 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
- Autorotation
- 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
- Loss of engine power (total)
- 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 › Aircraft handling/service
- Aircraft › Aircraft power plant
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
As part of the required normal 6-month competency check for the commercial pilot, a Federal Aviation Administration (FAA) inspector was performing an examination of the pilot's competency in responding to a total loss of engine power event while in cruise flight. To perform this examination, the FAA inspector announced the beginning of the simulated power loss procedure and moved the fuel flow control lever out of the flight detent (the full forward, full open position) and back just enough to keep the lever from springing back into the detent; this was done to ensure that the engine was not supplying power to the rotor system during the autorotation. However, when the fuel flow control lever was moved, the helicopter yawed right and the generator out warning light illuminated, indicating that the engine had flamed out. The pilot briefly attempted a restart, but the engine exceeded the temperature limit and he discontinued the start attempt. Because of their close proximity to the ground, there was inadequate time to attempt another restart of the engine. The pilot-in-command (PIC) identified and proceeded toward a forced landing site. Due to obstructing trees in the touchdown zone below the area where the simulated engine out was conducted, the PIC overflew the trees with up collective input, leading to a decay of the main rotor rpm. Thereafter, insufficient rotor rpm remained to cushion the touchdown. Also, because of down-sloping terrain, the distance between the helicopter and ground level increased seconds before landing, thereby increasing the helicopter's absolute altitude and contributing to a hard impact with the ground.
The fuel control unit and the power turbine governor were removed from the engine and taken to a test facility where they were installed on calibrated test benches and tested in accordance with the manufacturer’s test procedures. The results of the fuel control unit test showed that the internal parts all worked properly; however, the fuel flow at every test point was below the specified minimum limit. The results of the power turbine governor test revealed that the unit was out of specified limits at each test point. The discrepancies noted would affect the fuel flow at the high end of the schedule and is indicative of an improper rigging procedure. Examination of the unit showed that the maximum stop setting had been adjusted in the field and that the travel was set at 80 degrees instead of the required 86 degrees.
While some of the discrepancies found during the tests of the fuel control unit and the power turbine governor are not serious, those at the low end of the fuel schedule are of particular concern. The minimum fuel flow, idle, and the cut-off settings were found to be below the manufacturer’s specified minimum limits; when combined with hysteresis, or the lagging of a physical effect on a body behind its cause, the chances of insufficient fuel flow being delivered to the engine during any engine deceleration maneuver (i.e., moving the throttle out of the flight detent) increases dramatically. When the FAA inspector moved the fuel flow control lever as the pilot was manipulating the collective during the beginning of the autorotation, it is likely that the unloading of the engine sent a signal to the fuel control unit to rapidly decrease the fuel flow at the same time the fuel control lever was being brought out of the flight detent and moved aft, which helped induce the flameout.
Review of the operator’s flight and maintenance records found a pilot write-up that noted that about 9 months prior to the accident the engine had flamed out when the throttle was manipulated during the start sequence. The operator’s maintenance department was unable to find a reason for the event and released the helicopter back to service. The company pilots were aware that this particular helicopter had a “touchy throttle.” The pilot noted that, when operating the throttle lever in this particular helicopter, “you have to be gentle and slow with it as you retard the lever…if you pull it back to far or fast, it will shut off the fuel.” At least four prior instances of flameouts as a result of minor throttle movements were uncovered in deposition testimony of company pilots. All occurred on the ground and three of the flameouts happened as pilots were bringing the fuel flow control lever back toward ground idle during the post-flight engine cool down period. These instances were not documented in the maintenance records, and no records of attempted remediation were found.
Probable cause
An uncommanded engine shutdown due to an improperly calibrated fuel control unit (FCU) and power turbine governor (PTG). Also causal was the operator’s inadequate maintenance practices and procedures that failed to properly assess and correct the FCU and PTG irregularities/deficiencies. Contributing to the accident was the Federal Aviation Administration inspector’s selection of an area for the simulated engine failure that offered limited choices for a full-touchdown autorotation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR10FA085
- Event ID
- 20091217X62032
- Case number
- WPR10FA085
- 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: a58a0f4beb25692f094d4f428520ed6bf2601c98ec899268ed87c1b963f416ce; retrieved 2026-09-15T13:34:46.634Z.