# NTSB CEN09CA504: Vanderhoof Steve AIR Comman, N8099P, Mentone, IN, August 5, 2009

- Type: NTSB accident investigation
- Classification: Accident · Minor injuries · Data collection · Final report
- Date: August 5, 2009, 14:25 local (18:25 UTC)
- Place: Mentone, IN
- Coordinates: 41.150001, -86.062225 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=41.1500&lon=-86.0622&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing: Loss of control in flight](https://openairdocs.org/ntsb-events/240)
- Highest injury: Minor injuries
- Injuries: 1 minor
- Status: Completed, report October 19, 2009
- Report: Approved by Office Director
- NTSB office: Central Region
- Parties: Federal Aviation Administration
- NTSB case key (mKey): 74470
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN09CA504
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/74470/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=74470
- Page: https://openairdocs.org/ntsb/CEN09CA504

## Probable cause

The pilot's failure to maintain aircraft control during the landing and subsequent impact with a parked aircraft.

## Findings

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

- [Performance/control parameters](https://openairdocs.org/ntsb-findings/01062000): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Vanderhoof Steve AIR COMMAND (CLT), 1 case](https://openairdocs.org/ntsb-findings/01062000/cases.md?model=0590275), [All aircraft, 1,269 cases](https://openairdocs.org/ntsb-findings/01062000/cases.md)
- [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Vanderhoof Steve AIR COMMAND (CLT), 1 case](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=0590275), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md)
- [Object/animal/substance: aircraft](https://openairdocs.org/ntsb-findings/03022040): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Vanderhoof Steve AIR COMMAND (CLT), 1 case](https://openairdocs.org/ntsb-findings/03022040/cases.md?model=0590275), [All aircraft, 116 cases](https://openairdocs.org/ntsb-findings/03022040/cases.md)

## Sequence of events

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

- [Landing: Loss of control in flight](https://openairdocs.org/ntsb-events/240) (defining event); cases with it: [Vanderhoof Steve AIR COMMAND (CLT), 1 case](https://openairdocs.org/ntsb-events/240/sequence.md?model=0590275), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md)
- [Landing: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Vanderhoof Steve AIR COMMAND (CLT), 1 case](https://openairdocs.org/ntsb-events/300/sequence.md?model=0590275), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md)

## Analysis

The local airport was hosting an annual rotorcraft convention. Prior to the flight, the pilot had participated in the pilot's briefing and had been cleared to fly at the event. After flying to a nearby airport for lunch, the pilot was returning to the airport hosting the convention when the accident occurred. The pilot had entered a left hand traffic pattern for landing on runway 36. The air boss cleared the pilot to land and the pilot noticed "there was a lot of other aircraft activity." The pilot elected to extend his intended landing spot "past the majority of the aircraft... ." The pilot reported that "I hit the runway very hard and bounced on one wheel which veered me to the right in the direction of the east grass beside the runway. I was still going to be OK and continued to try and land. Then I was in the slow speed where the nose wheel is not on the ground yet and you are not able to steer and the rudder is becoming ineffective because of the slow airspeed and forward speed. I saw a [unoccupied] gyro parked close to the edge of the runway and it looked like I would clear it by a small margin. I powered up to put some airflow across the rudder in effort to steer clear of the gyro. I thought I had it made and then our rotors impacted and locked together. It flipped me over and dragged [the] gyro with mine." Examination of the accident gyrocraft revealed the main rotor blades were destroyed. No mechanical anomalies were noted with the accident gyrocraft.

## Factual narrative

The local airport was hosting an annual rotorcraft convention. Prior to the flight, the pilot had participated in the pilot's briefing and had been cleared to fly at the event. After flying to a nearby airport for lunch, the pilot was returning to the airport hosting the convention when the accident occurred. The pilot had entered a left hand traffic pattern for landing on runway 36. The air boss cleared the pilot to land and the pilot noticed "there was a lot of other aircraft activity." The pilot elected to extend his intended landing spot "past the majority of the aircraft... ." The pilot reported that "I hit the runway very hard and bounced on one wheel which veered me to the right in the direction of the east grass beside the runway. I was still going to be OK and continued to try and land. Then I was in the slow speed where the nose wheel is not on the ground yet and you are not able to steer and the rudder is becoming ineffective because of the slow airspeed and forward speed. I saw a [unoccupied] gyro parked close to the edge of the runway and it looked like I would clear it by a small margin. I powered up to put some airflow across the rudder in effort to steer clear of the gyro. I thought I had it made and then our rotors impacted and locked together. It flipped me over and dragged [the] gyro with mine." Examination of the accident gyrocraft revealed the main rotor blades were destroyed. No mechanical anomalies were noted with the accident gyrocraft.

## Aircraft

- Registration: [N8099P](https://openairdocs.org/deregistered/N8099P-2021-12-16), registration cancelled 2021-12-16, S/N 001, built 2007 (OpenAirDocs)
- Reported make and model: VANDERHOOF STEVE AIR COMMAN
- Registry model: [Vanderhoof Steve AIR COMMAND (CLT)](https://openairdocs.org/model/vanderhoof-steve-air-command-clt) (registry code 0590275) (OpenAirDocs)
- Registry engine: [Rotax 503 series](https://openairdocs.org/engine/rotax-503-series) (registry code 55564, 2 cycle) (OpenAirDocs)
- Category: Gyroplane, amateur-built
- Serial number: 001
- Airframe hours: 90
- Engines: ROTAX 503 52 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Operator: Steve Vanderhoof
- Registered owner: Vanderhoof Steve
- Airworthiness certificate: Special, Experimental light sport (Special)
- Last inspection: Condition, April 8, 2009
- Departed: RCR, Rochester, IN
- Destination: C92, Mentone, IN
- Airport: C92, Mentone Airport, runway 36, 2,521 × 40 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 60; injuries: minor; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review April 9, 2009; seat: single; flight hours: 1,282 total, 84 in this make and model, 1,090 as pilot in command, 13 in the last 90 days, 6 in the last 30 days, 1 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Day
- Wind: variable at 10 knots, gusting 18
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 82 °F

## 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 20090805048759A](https://openairdocs.org/incident/20090805048759A), Aug 5, 2009: Vanderhoof AIR COMMAND, Mentone, IN, Substantial damage. Aircraft lost directional control during landing rollout. After running off the right side of the runway the gyroplane collided with a parked gyroplane.…

## Docket (1 files)

The files NTSB released with the investigation on August 31, 2009, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=74470. 364 KB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 364 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40317603&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF

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.