The U.S. aircraft register, updated daily
Accidents · NTSB ERA20LA160 · Final report

Hughes 369 accident near Pylesville, Maryland, April 25, 2020

On April 25, 2020 at about 4:40 pm local time, a 1979 Hughes 369 (helicopter), registered N9159F, was substantially damaged in an accident during maneuvering (hover) near Pylesville, Maryland. It was an external-load flight under external-load helicopter rules (Part 133). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The loss of engine power due to fuel starvation as a result of unporting of the fuel tank supply pickup while the helicopter was maneuvered to move a conductor wire. Contributing to the accident was the helicopter’s inappropriate configuration for the type of operation being conducted, which impeded the pilot’s ability to release the long line and perform a successful emergency landing.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
April 25, 2020 · about 4:40 pm local time
Place
Pylesville, Maryland · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Hughes 369 D, built 1979 · all 369s on the register
Registration
N9159F · registry record · serial 1090605D
Damage
Substantial damage
Flight
External-load flight · external-load helicopter rules (Part 133)

The NTSB's narrative final · quoted from the NTSB record

The commercial helicopter pilot was attempting, via a long line, to move a conductor wire while it remained in contact with the ground, which is classified as a Class C rotorcraft-load combination (RLC) operation. According to the pilot, while he maneuvered the helicopter about 150 ft above ground level, he pitched the helicopter nose up about 5° to 10°, with no lateral banking, for about 10 to 15 seconds. The engine then experienced a total loss of engine power. In the autorotation, which the pilot estimated to be about 4 to 5 seconds, the pilot was only able to release one of two mechanisms that secured the long line to the helicopter. As a result, just before touchdown, the long line became taut and caused the helicopter to roll over onto its left side. The tailboom, main rotor, and tail rotor sustained substantial damage, and the pilot was uninjured. Postaccident examination of the helicopter found 146 lbs of fuel onboard. The pilot later reported that the helicopter had about 200 lbs of fuel (slightly less than half of a full load) when he began the flight about 1.5 hours before the accident. An engine test run found no evidence of mechanical malfunctions that would have precluded normal operation of the engine. The investigation identified four previous accident investigation reports that extensively documented loss of engine power due to fuel starvation on MD369 series helicopters while they were maneuvered in Class C RLC long line operations. In these past accidents, the remaining fuel on board ranged between 93 to 151 lbs. The investigations of these accidents found varying levels of pitch up and/or lateral banking (common maneuvers during Class C RLC operations) could interrupt normal fuel flow to the engine (that is, unport) at fuel levels well above the standard fuel minimums required for visual flight rules operation. Based on information provided by the helicopter manufacturer, with 146 lbs of fuel onboard, a 28.5° positive pitch attitude, with no lateral banking, could unport the fuel supply to the engine in static conditions. Therefore, in dynamic conditions, such as maneuvering, unporting could occur at lower pitch attitudes. The operator’s operating limitations at the time of the accident stated that for any Class C RLC operation, the flight must begin with a full fuel load and last no more than 1 hour and explains the policy by citing the risk of uncovering the fuel port due to lateral banking during these operations. The accident pilot believed that, similar to the operation he had completed earlier in the flight, moving the conductor wire was a Class B operation because it would not require any lateral banking of the helicopter. Because the pilot misconstrued the RLC class of operation he was performing, he erroneously believed that he only needed a minimum of 100 lbs of fuel at landing, which is the fuel minimum he selected on the operator’s job hazard analysis form before beginning the accident flight; the form contained no references to RLC classes. As a result of the accident, the operator updated its minimum fuel policies on its job hazard analysis form and in its RLC flight manual. The policies now provide specific references to Class B and C long line operations and detailed examples to help pilots’ understanding of which fuel minimums apply for specific operations. Thus, without evidence of malfunctions that would preclude the engine from producing or maintaining power and given the occurrence of fuel starvation during other Class C RLC long line operations with similar levels of fuel onboard, it is likely that the accident helicopter's maneuvering and nose-up attitude during the pilot’s attempt to move the conductor wire led to unporting of the remaining fuel, which resulted in fuel starvation and the loss of engine power. Additionally, it is possible that the pilot could have successfully landed the helicopter following the loss of engine power had the long line been released. The pilot had to pull two separate release mechanisms to detach the long line because the helicopter was previously configured for human external cargo (HEC) long line operations, although the specific operation being performed when the accident occurred did not involve HEC and redundancy to secure the long line was not needed (HEC operations were being performed earlier in the flight). As a result, the pilot did not have sufficient time to activate both release mechanisms, and the helicopter was substantially damaged during the attempted landing.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Autorotation Collision with terrain or object (not controlled flight into terrain)
  2. Autorotation External load event (Rotorcraft)
  3. Fuel starvation during maneuvering (hover) defining event

The NTSB's findings

  • Aircraft › Fluids/misc hardware › Fluids › Fuel › Fluid level
  • Personnel issues › Experience/knowledge › Knowledge › Knowledge of procedures › Pilot
  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Configuration › Incorrect use/operation
  • Aircraft › Aircraft systems › Fuel system › (general) › Capability exceeded
  • Organizational issues › Management › Policy/procedure › (general) › Not specified

Pilot

  • Certificate: commercial pilot
  • Ratings: rotorcraft: helicopter
  • Flight time: 12,549 hours in all; 8,736 in this make and model; 141 in the last 90 days; 101 in the last 30 days; 12,500 as pilot in command
  • Last flight review: March 8, 2020
  • Medical certificate: Class 2 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 17,015 hours
  • Last inspection: 100-hour inspection, April 6, 2020
  • Maximum gross weight: 3,000 lb
  • Seats: 5
  • Landing gear: fixed
  • Engine: Allison Gas Turbine (Rolls-Roy 250-C20B (turboshaft); 217,893 hours total
  • Operator: Haverfield International Incorporated

The flight

  • Departed from: NONE Pylesville MD at 4:30 pm
  • Destination: Pylesville MD
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 120° at 6 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 3,600 ft
  • Temperature: 61°F (16°C), dew point 46°F (8°C)
  • Altimeter: 30.04 inHg
  • Observation at 4:53 pm from THV, 26 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

20 documents, released by the NTSB on June 15, 2021. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 PDF, 11 pages View Download
2 Memorandum for Record (Pilot in Command) PDF, 3 pages View Download
3 Record of Conversation (Pilot in Command) PDF, 2 pages View Download
4 Memorandum for Record (Haverfield_faa_conference Call) PDF, 8 pages View Download
5 Memorandum for Record (Helicopter Exam Report) PDF, 13 pages View Download
6 Memorandum for Record - Engine Test Run Summary PDF, 1 page View Download
7 Memorandum for Record (Haverfield Dir. of Safety) PDF, 3 pages View Download
8 Memorandum for Record (Md Helicopter Unporting Chart) PDF, 2 pages View Download
9 Witness Statement Reports PDF, 6 pages View Download
10 Excerpts from the Rotorcraft Flight Manual PDF, 2 pages View Download
11 Haverfield Policy and Operational Document Excerpts PDF, 15 pages View Download
12 Md Helicopters_operational Safety Notice - OSN2015-002 PDF, 1 page View Download
13 MD369D Illustrated Parts Catalog - Fuel System PDF, 8 pages View Download
14 Haverfield Job Hazard Worksheet PDF, 7 pages View Download
15 ATSB Investigation AO-2008-025 PDF, 5 pages View Download
16 Revised Job Hazard Analysis Worksheet PDF, 9 pages View Download
17 Corporate Policy Change - Non-hec Ops and Belly Bands - June 2020 PDF, 1 page View Download
18 Statement of Party Representatives to NTSB Investigation PDF, 3 pages View Download
19 Release of Aircraft Wreckage, NTSB Form 6120.15 PDF, 5 pages View Download
20 Photo Array PDF, 6 pages View Download

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Other NTSB records under N9159F the same tail number, which may have belonged to a different aircraft at the time

2022-02-09ERA22LA117 · accident near Bel Air, MD · substantial damage · no injuries

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.