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

Sikorsky S61 accident near Palm Bay, Florida, September 6, 2016

On September 6, 2016 at about 5:40 pm local time, a 1974 Sikorsky S61 (helicopter), registered N805AR, was destroyed in an accident during maneuvering (low-alt flying) near Palm Bay, Florida. It was a flight test under general aviation rules (Part 91). 3 people were killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

A dual loss of engine power for undetermined reasons after the pilot's improper decision to attempt another maneuver after recovering from a perceived compressor stall, rather than returning to the airport.

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

What the record shows

Date
September 6, 2016 · about 5:40 pm local time
Place
Palm Bay, Florida · map
Type
Accident
Injuries
3 people were killed.
Weather
visual conditions (good weather)
Aircraft
Sikorsky S61 N, built 1974 · all S61s on the register
Registration
N805AR · no longer on the register · serial 61717
Damage
Destroyed
Flight
Flight test · general aviation rules (Part 91)

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

The helicopter flight crew, consisting of a pilot, copilot, and maintenance crewmember, was performing 20-knot rearward flight about 200 ft above ground level as part of a post-maintenance functional check flight (FCF). While the pilot was flying and recovering from the first rearward flight maneuver, unusual sounds were heard, which the flight crew identified as a compressor stall. The pilot then told the maintenance crewmember that they were returning to their home airport; however, after discussing compressor stalls and engine exhaust gas temperatures with the copilot, the pilot changed his mind and told the maintenance crewmember that they were going to try the maneuver again in a different direction relative to the wind (with the wind off the nose). While the pilot was recovering from the second rearward flight maneuver, there was a change in background noise, which the maintenance crewmember identified as a compressor stall. About 2 seconds later, there was another change in background noise, consistent with a decay in drivetrain rpm, which was followed by the helicopter descending and impacting the ground. Although the crew identified the sounds and loss of power as compressor stalls, a sound spectrum study could not characterize the gas generator speed (Ng) behavior, due to overdriven audio on the CVR, to determine the engine anomaly the crew identified as a compressor stall. It is likely that the cause of the overdriven audio is related to an engine anomaly. At the same time the engine anomaly occurred, the sound spectrum revealed Nr quickly decayed due to a dual loss of engine power coupled with a high collective setting. Because main rotor speed (Nr) decayed at the same time the overdriven audio occurred, it is likely both engines lost power nearly simultaneously. No anomalous damage to the engines was found that would have explained the dual loss of engine power and the main rotor drive system did not exhibit evidence of preimpact mechanical malfunction. Fuel exhaustion was unlikely given the estimated fuel load at the time of the accident. After the overdriven audio, the rate of Ng decay for each engine appeared similar to engine Ng decay when at a lower power setting. Due to a lack of a flight data recorder or a cockpit image recorder, the behavior of the engines as well as the position of the cockpit engine control levers at the time of the anomaly could not be determined. During postaccident examination, the left (No. 1) freewheeling unit (FWU) was found to rotate freely in both directions of rotation instead of rotating freely in only one direction as it was designed to do. Had the left FWU failed in flight resulting in a loss of drive between the No. 1 engine and the main gearbox, the No. 1 engine power turbine would have experienced an overspeed due to the sudden loss of load. A No. 1 engine power turbine overspeed would also have resulted in an overspeed of the AC generators due to a through shaft connecting the left FWU and the AC generators. However, during the accident loss of power event, the frequencies of the main gearbox planetary mesh and the AC generators did not diverge but remained synced, which is not consistent with a left FWU overspeed. Therefore, the anomalous finding of rotation in both directions for the left FWU is likely a postaccident artifact. Review of the rotorcraft flight manual (RFM) emergency procedures revealed, "2. If an abnormal engine conditions occurs such as engine stall, flame-out, or overtemperature, transition to single engine flight or 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. Loss of engine power (total) during maneuvering (low-alt flying) defining event
  2. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent

The NTSB's findings

  • cause Aircraft › Aircraft power plant › (general) › (general) › Not specified
  • cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot

Pilot

  • Certificate: airline transport pilot, flight instructor, commercial pilot
  • Ratings: multi-engine land; single-engine land; instructor: helicopter; instructor: instrument helicopter; instrument: airplane; instrument: helicopter; rotorcraft: helicopter
  • Flight time: 6,347 hours in all; 1,780 in this make and model; 114 in the last 90 days; 25 in the last 30 days; 4,754 as pilot in command; 2,240 on instruments
  • Last flight review: May 18, 2016
  • Medical certificate: Class 1
  • Seat: left
  • Injury: fatal

Co-pilot

  • Certificate: commercial pilot
  • Ratings: instrument: helicopter; rotorcraft: helicopter
  • Flight time: 4,090 hours in all; 1 in this make and model; 1 in the last 90 days; 1 in the last 30 days; 3,419 as pilot in command; 1,400 on instruments
  • Medical certificate: Class 2 (with waivers/limitations)
  • Seat: rgt
  • Injury: fatal

The aircraft

  • Airframe total time: 40,296 hours
  • Last inspection: continuous airworthiness programme, August 25, 2016; 1 hours since
  • Maximum gross weight: 22,000 lb
  • Seats: 41
  • Landing gear: fixed
  • Engine 1: Ge CT58-140-2 (turboshaft); 23,235 hours total
  • Engine 2: Ge CT58-140-2 (turboshaft); 25,259 hours total
  • Fire on the ground
  • Operator: Aar Airlift Group

The flight

  • Departed from: MLB Melbourne FL at 5:24 pm
  • Destination: MLB Melbourne FL
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 070° at 11 knots
  • Visibility: 10 statute miles
  • Sky: a few clouds at 5,000 ft
  • Temperature: 86°F (30°C), dew point 70°F (21°C)
  • Altimeter: 30.14 inHg
  • Observation at 5:53 pm from MLB, 10 miles away

Injuries

FatalSeriousMinorNone
Flight crew3

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

The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.

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.