Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

September 1, 2022 · Sikorsky S-61N · N617CK

Shady Cove, OR

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
September 1, 2022
Injury Outcomes
2 injuries (2 minor injuries)
Location
Shady Cove, OR
Aircraft
Sikorsky S-61N (1962)
Tail Number
N617CK
Operator
Croman
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
WPR22LA330

Two days before the accident flight, the helicopter flight crew conducted a timber logging flight. The No.1 engine started without issue, but the No. 2 engine start was aborted after it sustained a hot start, as confirmed by the No. 2 engine T5 temperature digital gauge indication of 999° C, a subsequent indication of --- ° C, and finally 001° C. The engine was allowed to cool, and about five minutes later the PIC started the No. 2 engine without issue, followed by the No. 1 engine; the flight crew then completed an eight-hour flight day. The helicopter remained in service until the day of the accident. On the day of the accident, while performing their normal logging operation flight, the flight crew heard a loud “bang” twice and decided to make a precautionary landing. With the engines turning, no anomalies were confirmed by maintenance personnel, and they continued flight operations. The flight crew did not perform an out-of-ground-effect hover power check to determine whether they had single-engine capability. After picking up about a 4,000 pound load during climb out of the confined area, another loud “bang” occurred, followed by a series of successive “bangs” that resulted in a vertical descent and hard impact with terrain, which resulted in a subsequent rollover onto the helicopter’s right fuselage. Postaccident examination of the helicopter’s No. 2 engine revealed overtemperature distress of the gas generator turbine (GGT) section. All stage 1 turbine blades revealed overtemperature distress. Most of the stage 2 turbine blades exhibited deformation about the leading edges and blade tips. During examination, the turbine coupling shaft was unusually difficult to remove, indicative of overtemperature effects, and the turbine forward shaft exhibited a dark blue discoloration indicative of thermal deformation. The metallurgical examination of 11 stage 1 turbine blades revealed evidence of bulk deformation, coating cracking/melting, and creep voiding/surface cracking consistent with overtemperature exposure. The PIC stated that he did not report the hot start event to the operator’s director of maintenance because he understood a hot start to entail a T5 temperature of 950° C sustained over 2 seconds. However, guidance from the engine manufacturer indicated that hot start criteria are based on a combination of temperature over time, and that hot starts may occur at temperatures of approximately 750° C within about 15 seconds. Given the circumstances of the event and physical evidence from the postaccident engine examination, it is likely that the No. 2 engine hot start that occurred 2 days before the accident contributed to the failure of the stage 1 turbine blades due to overtemperature, which resulted in the No. 2 engine loss of power and subsequent impact with terrain. According to the FAA, serious engine damage occurs if a hot start is allowed to continue.

NTSB Probable Cause

A total loss of engine power due to the failure of the No. 2 engine’s stage 1 turbine blades as a result of an unreported hot start two days earlier.

Full Narrative

On September 01, 2022, about 0735 Pacific daylight time, a Sikorsky S-61N helicopter, N617CK, sustained substantial damage when it was involved in an accident near White City, Oregon. The two pilots and a ground support team member sustained minor injuries. The helicopter was operated as a Title 14 Code of Federal Regulations Part 133 rotorcraft external load flight. Two days before the accident, according to the maintenance personnel and the second in command (SIC), the morning of August 30, 2022, the SIC and PIC entered the cockpit with the intent of conducting timber logging operations. The No.1 engine start was completed by the SIC. During the No. 2 engine start sequence, the SIC reported that the Ng took longer to rise, but increased before he moved the speed select lever to the idle detent. The SIC reported that the fuel pressure increased, and ignition occurred. The No. 2 engine Ng reached 45 percent, and the T5 temperature fluctuated between 630° C to 670° C, before he released the starter. The temperature subsequently increased to 720° C and the SIC alerted the PIC. The PIC told the SIC to “Hold” and the SIC watched the temperature gauge increase, and the digital T5 gauge indicated 001° C. The PIC stated that he did not report the hot start event to the operator’s director of maintenance because he understood a hot start to entail a T5 temperature of 950° C sustained over 2 seconds. Guidance from the engine manufacturer indicated that hot start criteria are based on a combination of temperature over time, and that hot starts may occur at temperatures of approximately 750° C within about 15 seconds (see figure 1). Figure 1: Engine manufacturer Hot Start guidance Additionally, the SIC reported that when the digital gauge indicated 001° C, the maintenance technician located outside the helicopter transmitted over the intercom, “It’s hot” and the No. 2 engine start was aborted. The maintenance technician located inside the helicopter reported that the No. 1 engine start occurred without issue, but during the No. 2 engine start, the engine “temped out” and “it maxed the T5 to 999, then the gauge had 3 dashes (---) across [the] gauge and then the number 001.” According to the T5 gauge manufacturer, 001° C is the maximum value the gauge will report, even if the T5 temperature continues to increase above 999°C. The No.1 engine was secured, the No. 2 engine was allowed to cool and the No. 2 engine digital T5 gauge indicated that the engine temperature was decreasing, but the analog gauge needle did not show the temperature dropping back to normal operating temperature range. About five minutes after aborting the start sequence, the No. 2 engine was started by the PIC without anomaly, along with the No. 1 engine. That day the flight crew flew multiple sorties and shut down both engines during a crew break. Both engines were restarted after the break without anomaly; the crew finished their eight-hour flight day, and the helicopter remained in service. No entries were annotated on the maintenance log regarding the hot start. On September 01, 2022, the PIC who experienced the hot start two days before was assigned to N617CK with a different SIC for a day of timber logging flights. During climb out, a pedal turn to the right was accomplished while departing the log landing site. Shortly after the right turn, the crew heard a loud “bang” sound. They assessed the instrument panel and confirmed that all systems were within normal operating limits. The flight and engine instruments did not indicate that an anomaly existed; the PIC elected to continue the logging operation. Two additional sorties were accomplished, and the “bang” sound occurred again. A precautionary landing was made to troubleshoot the abnormal sound with the assistance of maintenance personnel while the engines continued to run. A definitive source of the “bang” sound was not identified by the maintenance personnel, and a decision was made by the PIC to continue the operation. While departing the log landing site, a right pedal turn was accomplished, and a subsequent “bang” ensued. However, this iteration presented several immediate and successive “bangs” followed by a grinding noise and a degradation of the No. 2 engine torque value to zero. The Master Caution warning light illuminated, and the helicopter descended to the ground, landing hard on the main landing gear. The helicopter rolled to the right and came to rest on the right-side fuselage. The helicopter came to rest on a flat surface used for timber storage, and the accident site was surrounded by trees over 50 ft tall. Each of the five main rotor blades had separated from the fully articulated main rotor hub, which remained attached to the upper fuselage. Examination of the airframe revealed substantial damage to the right overhead and chin bubble as well as the wind screen. The lower fuselage revealed substantial damage to the tailwheel landing gear attachment points. The tail rotor remained attached to the driveshaft, but the horizontal stabilizer sustained substantial damage. After making the precautionary landing, the flight crew did not complete an out-of-ground-effect hover power check to ensure that the helicopter had single-engine capability within the current environmental parameters, while operating in a confined area. According to Chapter 11 of the Federal Aviation Administration Helicopter Flying Handbook, “When one engine has failed, the helicopter can often maintain altitude and airspeed until a suitable landing site can be selected. Whether or not this is possible becomes a function of such combined variables as aircraft weight, density altitude, height above ground, airspeed, phase of flight, and single-engine capability.” A review of the engine logbooks indicated that the No. 2 engine, serial number 285036RC was installed in the accident helicopter on July 14, 2022. At the time of the accident, the No. 2 engine had about 18,646 hours time since new, about 311 hours since installation and about 479 hours since light overhaul. Additionally, the No. 2 engine was operated about 17 hours between the aborted hot start and the accident. Postaccident examination of the engine T5 temperature gauges on both engines indicated that they were operational. The fuel flow divider was removed from the helicopter for testing and revealed that the component did not meet operational standards. The testing facility identified the abnormalities as common occurrences amongst flow dividers that come in for overhaul or repair; however, no observable discrepancies had been noted by the customer. Postaccident examination of the spindle bearings to determine the source of the “bang” sound experienced by the flight crew was inconclusive. The spindles were disassembled by the operator before their arrival at Sikorsky, so the intended test for bearing stick could not be performed. Postaccident examination of the No. 2 engine revealed overtemperature distress on most of the gas generator turbine parts. All the stage 1 turbine blades sustained severe overtemperature distress, most notably visible at the leading edge tips and trailing edge tips. Four of the stage 1 turbine blades had separated at their mid-span. Additionally, multiple stage 1 turbine blades had cracks initiated at their trailing edge and mid-span. All stage 1 turbine blades also exhibited profile “cupping” to varying degrees compared to an exemplar stage 1 turbine wheel. Most of the stage 2 turbine blades had minor overtemperature distress at the leading edge tips. The metallurgical examination of 11 stage 1 turbine blades (2 destructively) revealed evidence of bulk deformation, coating cracking/melting, and creep voiding/surface cracking consistent with overtemperature exposure. The turbine coupling shaft was unusually difficult to remove. The turbine forward shaft exhibited a dark blue color. All gas generator turbine (GGT) seals were confirmed to be in place. General material debris was found throughout the GGT assembly. According to Chapter 15 of the Federal Aviation Administration Airplane Flying Handbook, “An engine tendency to exceed maximum starting temperature limits is termed a hot start. The temperature rise may be preceded by unusually high initial fuel flow, which may be the first indication the pilot has that the engine start is not proceeding normally. Serious engine damage occurs if the hot start is allowed to continue.”

Flight

Event TypeAccident
Event Time07:35 PDT
Nearest Airport0nm
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftSikorsky S-61N
Tail NumberN617CK
Aircraft CategoryHeli
DamageSubstantial
OperatorCroman
Operating RulePart 133
Engines2
Engine TypeTurboshaft
Engine DetailsGe · CT58-140-2 · Turboshaft · 1500 | Ge · CT58-140-2 · Turboshaft · 1500
Seats28

People & Injuries

Injury Summary2 injuries (2 minor injuries)
Fatal0
Serious0
Minor2
Uninjured0
Total2
Crew 1Age 65 · Second Class · Minor
Crew 2Age 55 · Second Class · Minor

Conditions

ConditionsVMC
LightDaylight
WindCalm
Visibility3 sm
CeilingBroken clouds 3800 ft
Temperature / Dew Point63 F / 48 F
Altimeter30.02 inHg
Observation Time07:29
Weather SourceWFAC

Appendix: Source Data