FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Papillon Helicopters Sikorsky/Orlando S-55 accident

18 Sept 2000 · HOOVER DAM, AZ, United States

Sikorsky/Orlando S-55 · Accident: loss of engine power en route

From Harry Reid International Airport (LAS) to Grand Canyon National Park Airport (GCN)

Report a problem

Event

NTSB case
LAX00FA342
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
0
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/Orlando S-55

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
N17754
Onboard fatalities
Unknown
Route
From Harry Reid International Airport (LAS), Las Vegas, NVTo Grand Canyon National Park Airport (GCN), Grand Canyon, AZ
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 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
En route · cruise
First occurrenceThe 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
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

  • Other maintenance personnel › Maintenance, design change, not performed
  • Turboshaft engine, power output shaft › Failure, partial

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

NTSB narrative

**This report was modified on 2/23/2016. Please refer to the public docket for this accident for more information.**

The helicopter was being operated as a sightseeing flight to the Grand Canyon. The pilot reported that during cruise flight the rotor and engine noise suddenly decreased and the helicopter began a descent. During the ensuing forced landing, the helicopter landed hard. The helicopter was fabricated from an ex-military remanufactured and modified Sikorsky S-55 (UH-19D). The original radial reciprocating engine had been replaced with a Garrett Gas Turbine TPE 331 modified to a TSE 331 IOUA 511 SW. It had a 6,000-hour time between overhaul. According to maintenance records dating back to July 3, 1985, the accident engine P-54083 operated in more than one Fairchild SA226 airplane in Australia and several rotary wing S-55 aircraft during their certification in the United States. Following the accident, the engine was shipped to the modifier for functional testing in a cell. The engine started and idled normally. Increasing the rpm to the certified operating specification of 101.5 percent revealed no abnormal conditions. The test propeller was moved from the start locks and increasing torque load was applied. As the torque was increased, the engine responded normally until approximately 60 percent torque when the indicated engine rpm rapidly decreased and an emergency shutdown was initiated. The process was repeated through 12 cycles, during which the indicated rpm began a sudden rapid decrease when torque was increased. Test cell troubleshooting failed to identify or correct this condition. During manual rotation of the propeller following the final cycle, some "slipping" was noted between the output shaft and the main rotating group. Subsequent examination of the gearbox revealed disengagement of the sun and bull gear assembly. Examination revealed fretting damage to the retaining nut and mating surfaces related to loss of specified torque. Visual examination of the sun and bull gears revealed severe damage to the mating splines of both gears. When the next-to-last and last engine oil samples taken prior to the accident were compared, iron increased 412.5 percent, and magnesium increased 571.6 percent. Just before the accident flight, the engine chip detector warning light illuminated and maintenance personnel removed, cleaned, and reinstalled the chip light sensor.

Probable cause

**This report was modified on 2/23/2016. Please refer to the public docket for this accident for more information.**

The failure of Papillon maintenance personnel to recognize the significance of the increasing metal in the oil analysis test results and the illumination of the chip detector warning, the combination of which indicated internal engine wear that subsequently resulted in loss of engine drive to the rotor systems during flight. Contributing to the accident was National Flight Services' failure to properly torque the bull and sun gear retaining nut, which resulted in wear and the ultimate disengagement of the bull and sun gear.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX00FA342
Event ID
20001212X21998
Case number
LAX00FA342
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 5e9e6b2a9b5682550a114f18992d6f4d853024b027dd9cc3a8268c85f59bbb2f; retrieved 2026-09-18T16:24:56.831Z.