FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Global Sky Air Charter Sikorsky S76 A accident

15 Dec 2017 · Islamorada, FL, United States

Sikorsky S76 A · Accident: fire/smoke (non-impact) while standing

From Florida Keys Marathon International Airport (MTH) to Islamorada, FL

Report a problem

Event

NTSB case
ERA18LA053
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

Sikorsky S76 A

Aircraft type
Sikorsky S76
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
N911FK
Onboard fatalities
Unknown
Route
From Florida Keys Marathon International Airport (MTH), Marathon, FLTo Islamorada, FL
Aircraft age
About 36 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 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
Standing · engine(s) operating
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
Fire/smoke (non-impact)
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

  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot landed the helicopter in an open field to pick up a patient. He reported that he positioned the engine controls to idle, and the main rotor speed (Nr) was less than 60% before he applied the rotor brake to stop the rotors. The rotors stopped, and the paramedic and flight nurse exited the helicopter. After they departed, the pilot noted that the No. 1 engine temperature was fluctuating with an increase in the inlet turbine temperature, so he shut down the No. 1 engine. The flight nurse then noticed dark smoke, sparks, and then flames emanating from the main rotor gearbox cowling area of the helicopter. The pilot was notified of the fire, shut down the No. 2 engine, and discharged both fire bottles, but the fire continued to burn until fire department personnel extinguished it. The thermal damage observed in the main rotor gearbox compartment appeared centered around the rotor brake. The rotor brake control components did not exhibit evidence of anomalies that would have either led to its uncommanded engagement with rotors turning or sustained engagement after disengagement of the rotor brake. Raised material found on the rotor brake disk surface was consistent with fused material from the rotor brake pads. Both forward and aft brake pucks extended when hydraulic pressure was applied to the brake calipers. The forward pucks of the left and right brake calipers did not automatically retract when hydraulic pressure was removed, but they were manually retracted without difficulty. The rotorcraft flight manual supplement (RFMS) for the accident helicopter mentioned the possibility of a rotor brake fire if pressure has been applied to the rotor brake system that resulted in a rotor brake puck dragging against a brake disk. However, with hydraulic pressure removed, it is unlikely the forward pucks of the left and right brake calipers would have asserted enough force on the rotor brake disk to increase friction between the puck and brake disk to cause these components to heat up enough to result in a fire. The No. 1 engine did not exhibit evidence of anomalous damage, and its FCU functioned normally on the test bench. There was no evidence of thermal damage to both engines’ exteriors. However, the gas generator turbines and thermocouples from the No. 2 engine exhibited thermal damage. Because thermal damage was not observed on the compressor stages, it is unlikely the thermal damage internal to the No. 2 engine was caused by the fire from the main gearbox compartment. Thus, it is likely the internal thermal damage to the No. 2 engine was caused by excess fuel flow into the combustion chamber of the engine. The No. 2 engine fuel control unit (FCU) functioned normally on the test bench; the FCU governed power turbine speed (Np) when its throttle was set to flight and stopped governing Np when its throttle was set to idle. A check of the rigging between the cockpit engine control levers (ECL) and the FCU throttles revealed no anomalies. Given that the engine FCU bench test was normal, it is likely that, after landing the helicopter, the pilot activated the rotor brake while the No. 2 engine FCU throttle position remained in the flight position and the No. 2 ECL was set to a condition to govern Np. As Nr, and consequently Np, dropped with the application of the rotor brake, the No. 2 engine FCU increased fuel flow to compensate, likely to its maximum rate, which resulted in thermal damage to the engine. The application of the rotor brake increased friction and heat as the additional fuel continued to provide power to the engine; thus, with the rotor brake force applied and with the No. 2 engine attempting to overcome it, the friction increased until a fire ignited near the rotor. The specific origin of the fire could not be determined; however, given the pilot's report that the area around the rotor brake assembly generally can accumulate slung grease and oil, it is possible that these materials, when exposed to the hot rotor brake disk, could have ignited and exacerbated the risk and spread of fire. A decal on the rotor brake lever cautioned that both engines must be shut down or one engine can be at idle for rotor brake application. The RFMS applicable to helicopters equipped with Arriel 1S1 engines installed indicated that rotor brake application was limited to one or two engines operating at idle or both engines shut down. Although a discrepancy existed between the decal and the RFMS, the Arriel 1S1 engine installation allows both engines to be at idle when applying the rotor brake; thus, the discrepancy was not a factor in this accident.

Probable cause

The pilot's activation of the rotor brake while the No. 2 engine was still set to govern the power turbine speed, which resulted in continuous power being applied to the rotor while the rotor brake was engaged and led to excessive friction, heat, and a subsequent fire in the area of the rotor brake.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA18LA053
Event ID
20171215X01947
Case number
ERA18LA053
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: f56d66f664eb6c9046f36694181a50670b0e7f4d3ad99b169cd7944137e09491; retrieved 2026-09-16T06:09:18.014Z.