WPR16LA021 · MD Helicopter 369D
Olympic Air MD Helicopter 369D · Accident: fuel contamination while maneuvering
From Arlington Municipal Airport (AWO) to Arlington Municipal Airport (AWO)
Event
- NTSB case
- WPR16LA021
- 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
MD Helicopter 369D
- Aircraft type
- MD Helicopters 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
- N510PA
- Operator
- Olympic Air
- Onboard fatalities
- Unknown
- Route
- From Arlington Municipal Airport (AWO), Arlington, WATo Arlington Municipal Airport (AWO), Arlington, WA
- Aircraft age
- About 34 years (built 1981)
- 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 133: Rotorcraft Ext. Load
- 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
- Maneuvering · low-altitude flying
- 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 contamination
- 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 systems
- Aircraft › Fluids/miscellaneous hardware
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The commercial pilot reported that, while conducting longline operations, the helicopter lost engine power. The pilot entered the helicopter into an autorotation and attempted to land at the bottom of a hill on flat terrain, but the helicopter touched down on a slope; the tailboom, followed by the skids, impacted the side of a hill, and the helicopter then came to rest on its side.
During postaccident examination of the airframe and engine, debris was found throughout the fuel system. The start pump was removed, and the fuel bypass valve inlet port screen was found covered with a brown, spongelike debris. Normal operation is with the start pump off (except when using alternate fuel mixtures or emergency fuels). When the start pump is not in use, fuel passes through the fuel bypass valve inlet port screen. The debris located on the fuel pump bypass valve inlet port screen, throughout the inside of the pump, and embedded in the centrifugal pump prevented the pump from producing sufficient fuel flow, which starved the engine of fuel and resulted in the power loss. Although the operator reported that it monitored for fuel contamination in the accident helicopter and its other company helicopters in accordance with the helicopter manufacturer's maintenance procedures, these procedures did not require that the fuel bypass valve inlet port screen be checked unless a cockpit warning indication light was activated. The light had not activated in the accident helicopter; therefore, the operator had not checked the screen. Following the accident, the helicopter manufacturer revised its procedures to require that the screen be checked whenever fuel contamination was identified.
Testing of the debris was consistent with naphthenates, which are surfactants that reduce the surface tension between the fuel and free water and allow the two liquids to mix. Refinery processing should remove all traces of naphthenic acid and its corresponding metal salts; however, in some refining processes, small amounts of the naphthenates can get carried through with the jet fuel, which can lead to microbial growth in the fuel. About 1 month before the accident, the operator found microbial growth in company fuel and treated the fuel with a microbiocide to destroy biological growth. However, there is no evidence that the microbiocide used by the operator contributed to the dissolution of the naphthenates, and the reason for the separation of naphthenates from the fuel could not be determined.
Probable cause
The loss of engine power due to fuel starvation as a result of naphthenate fuel contamination, which blocked the fuel flow through the start pump.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR16LA021
- Event ID
- 20151103X52016
- Case number
- WPR16LA021
- 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: cb227de29b9964970362c3ec93fca3d07e8efe4c153e83f07054a93779953964; retrieved 2026-09-16T02:56:38.506Z.