# NTSB CEN09CA026: Holland Rotorway 162F, N162NJ, Rutland, SD, October 10, 2008

- Type: NTSB accident investigation
- Classification: Accident · Minor injuries · Data collection · Final report
- Date: October 10, 2008, 18:50 local (23:50 UTC)
- Place: Rutland, SD
- Coordinates: 44.093887, -96.967224 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=44.0939&lon=-96.9672&mi=10
- Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping)
- Defining event: [Enroute-cruise: Sys/Comp malf/fail (non-power)](https://openairdocs.org/ntsb-events/330)
- Highest injury: Minor injuries
- Injuries: 1 minor, 1 uninjured
- Status: Completed, report January 22, 2009
- Report: Approved by Office Director
- NTSB office: Central Region
- Parties: Federal Aviation Administration - Rapid City FSDO
- NTSB case key (mKey): 69317
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN09CA026
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/69317/pdf
- Page: https://openairdocs.org/ntsb/CEN09CA026

## Probable cause

The loss of torque due to a failure of a transmission drivebelt and the pilot's delayed landing flare during the autorotation. Contributing to the accident was the dusk light condition and the corn crop.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Main rotor drive](https://openairdocs.org/ntsb-findings/01046300): Aircraft › Aircraft propeller/rotor · Failure (probable cause); cases with it: [Holland Randal ROTORWAY 162F, 1 case](https://openairdocs.org/ntsb-findings/01046300/cases.md?model=05611JX), [All aircraft, 15 cases](https://openairdocs.org/ntsb-findings/01046300/cases.md)
- [Performance/control parameters: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Incorrect use/operation (probable cause); cases with it: [Holland Randal ROTORWAY 162F, 1 case](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=05611JX), [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md)
- [Light condition: low light](https://openairdocs.org/ntsb-findings/03036015): Environmental issues › Conditions/weather/phenomena · Contributed to outcome (probable cause); cases with it: [Holland Randal ROTORWAY 162F, 1 case](https://openairdocs.org/ntsb-findings/03036015/cases.md?model=05611JX), [All aircraft, 36 cases](https://openairdocs.org/ntsb-findings/03036015/cases.md)
- [Terrain](https://openairdocs.org/ntsb-findings/03021000): Environmental issues › Physical environment · Contributed to outcome (probable cause); cases with it: [Holland Randal ROTORWAY 162F, 1 case](https://openairdocs.org/ntsb-findings/03021000/cases.md?model=05611JX), [All aircraft, 267 cases](https://openairdocs.org/ntsb-findings/03021000/cases.md)
- [Action: delayed action](https://openairdocs.org/ntsb-findings/02041025): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Holland Randal ROTORWAY 162F, 1 case](https://openairdocs.org/ntsb-findings/02041025/cases.md?model=05611JX), [All aircraft, 894 cases](https://openairdocs.org/ntsb-findings/02041025/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Enroute-cruise: Sys/Comp malf/fail (non-power)](https://openairdocs.org/ntsb-events/330) (defining event); cases with it: [Holland Randal ROTORWAY 162F, 1 case](https://openairdocs.org/ntsb-events/330/sequence.md?model=05611JX), [All aircraft, 994 cases](https://openairdocs.org/ntsb-events/330/sequence.md)
- [Autorotation: Off-field or emergency landing](https://openairdocs.org/ntsb-events/440); cases with it: [Holland Randal ROTORWAY 162F, 1 case](https://openairdocs.org/ntsb-events/440/sequence.md?model=05611JX), [All aircraft, 3,365 cases](https://openairdocs.org/ntsb-events/440/sequence.md)
- [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092); cases with it: [Holland Randal ROTORWAY 162F, 1 case](https://openairdocs.org/ntsb-events/092/sequence.md?model=05611JX), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md)
- [Landing-flare/touchdown: Roll over](https://openairdocs.org/ntsb-events/097); cases with it: [Holland Randal ROTORWAY 162F, 1 case](https://openairdocs.org/ntsb-events/097/sequence.md?model=05611JX), [All aircraft, 261 cases](https://openairdocs.org/ntsb-events/097/sequence.md)

## Analysis

The helicopter pilot reported that during the local area flight he heard "loud noises" behind the cockpit that were followed by a loss of torque to the rotor system. He immediately initiated an autorotation into a cornfield. The tailboom stinger contacted the ground during the landing flare, which pushed the tailboom up into the path of the main rotor system. The helicopter then landed hard and rolled over onto its right side. The pilot reported that the accident could have been prevented if he had initiated his flare about two feet higher, but at the time he was unsure of his altitude above the ground due to the corn crop and the dusk light condition. A postaccident inspection of the helicopter revealed that one of the transmission drive belts had failed and another belt had separated from its pulley assembly.

## Factual narrative

The helicopter pilot reported that during the local area flight he heard "loud noises" behind the cockpit which was followed by a loss of torque to the rotor system. He immediately initiated an autorotation into a cornfield. The tailboom stinger contacted the ground during the landing flare, which pushed the tailboom up into the path of the main rotor system. The helicopter then landed hard and rolled over onto its right side. The pilot reported that the accident could have been prevented if he had initiated his flare about two feet higher, but at the time he was unsure of his altitude above the ground due to the corn crop and the dusk light condition. A post-accident inspection of the helicopter revealed that one of the transmission drive belts had failed and another belt had separated from its pulley assembly.

## Aircraft

- Registration: [N162NJ](https://openairdocs.org/deregistered/N162NJ-2012-08-27), registration cancelled 2012-08-27, S/N 6064, built 2001 (OpenAirDocs)
- Reported make and model: Holland Rotorway 162F
- Registry model: [Holland Randal ROTORWAY 162F](https://openairdocs.org/model/holland-randal-rotorway-162f) (registry code 05611JX) (OpenAirDocs)
- Registry engine: [Amateur-built UNKNOWN ENG](https://openairdocs.org/engine/amateur-built-unknown-eng) (registry code 99999) (OpenAirDocs)
- Category: Helicopter, amateur-built
- Serial number: 6064
- Airframe hours: 261
- Engines: Rotorway 162F 150 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Airworthiness certificate: Special, Experimental (Special)
- Last inspection: Condition, November 17, 2007
- Departed: PVT, Wentworth, SD
- Destination: PVT, Wentworth, SD

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 43; injuries: minor; private; airplane ratings: single-engine land; medical: class 3, without waivers/limitations; last flight review May 21, 2008; seat: left; flight hours: 588 total, 67 in this make and model, 524 as pilot in command, 30 in the last 90 days, 8 in the last 30 days

## Weather

- Conditions: Visual (VMC), Dusk
- Wind: 30° at 12 knots, gusting 17
- Visibility: 10 statute miles
- Lowest ceiling: 7,500 ft broken
- Temperature: 48 °F, dew point 39 °F
- Altimeter: 29.90 inHg
- Observed at: KBKX, 14 nm away

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20081010850289A](https://openairdocs.org/incident/20081010850289A), Oct 10, 2008: Hollan ROTORWAY162F, Madison, SD, Substantial damage. (-23) On 10/10/2008 at approximately 1840 CDT, [privacy data omitted] departed with one pax from his private landing strip located approximately 10 miles NE of…

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.
