FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC02FA064 · Denzer RAF 2000

29 Jun 2002 · Palmer, AK, United States

Denzer RAF 2000 · Accident: abrupt maneuver during takeoff

From Warren "Bud" Woods Palmer Municipal Airport (PAAQ) to an unrecorded destination

Report a problem

Event

NTSB case
ANC02FA064
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
1 · 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
General aviation
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

Denzer RAF 2000

Aircraft type
Denzer RAF-2000
Category
Gyroplane
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
N435PR
Operator
Unknown
Onboard fatalities
Unknown
Route
From Warren "Bud" Woods Palmer Municipal Airport (PAAQ), Palmer, AKTo not recorded
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 91: General Aviation
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
Takeoff
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
Abrupt maneuver
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

  • Pilot in command › Lift-off, abrupt
  • Pilot in command › Porpoise/pilot-induced oscillation, not corrected

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The private airplane pilot was conducting touch and go landings in a two-seat, wheel-equipped experimental/homebuilt gyroplane. During the takeoff roll, the gyroplane lifted off abruptly, and the main rotor blades struck the runway surface near the location where the gyroplane lifted off. The gyroplane then climbed steeply to an altitude of less than 100 feet above the ground, and went through one or more longitudinal axis pitch oscillations. The main rotor was observed to slow down and strike the tail-mounted rudder. The gyroplane then descended to the runway in a steep nose-down attitude. Examination of the wreckage revealed no evidence of any preexisting mechanical anomalies. The gyroplane kit was purchased by the pilot in April, 2000. It was assembled by the pilot/owner in Alaska, and transported to Alabama in January, 2002. The pilot began receiving flight training in the gyroplane on January 16, 2002, and concluded training on February 2, 2002. On February 3, 2002, the pilot completed an application for a private pilot, rotorcraft gyroplane rating, and the application was endorsed by the pilot's flight instructor. According to the pilot's flight instructor, the pilot planned to travel from Alabama to Alaska, and planned to complete the practical (flight) test portion of the gyroplane rating either enroute or in Alaska. Application for an additional gyroplane rating requires that the applicant accumulate at least 40 hours of flight time that includes at least 20 hours of flight training, and 10 hours of solo flight, and complete a practical test. No additional written test is required. On the application, the pilot listed 42.4 hours in a gyroplane, 32.2 hours of instruction, and 10.2 hours of solo flight. The pilot did not complete the practical test for a rotorcraft gyroplane rating. His last flight in the gyroplane was four months before the accident. A postmortem examination of the pilot attributed the cause of death for the pilot to blunt force injuries. Additionally, the examination found severe (60 to 70 percent) occlusive arteriosclerotic cardiovascular disease. The FAA's Rotorcraft Flying Handbook contains a discussion of pilot-induced oscillation (PIO), and power pushover situations. The handbook notes that gyroplanes experience a slight delay between control input and the reaction of the aircraft. This delay may cause an inexperienced pilot to apply more control input than required, resulting in a greater aircraft response than was desired. Once the error has been recognized, opposite control input is applied to correct the flight attitude. Because of the nature of the delay in aircraft response, it is possible for the corrections to be out of synchronization with the movements of the aircraft and aggravate the undesired changes in attitude. The result is pilot-induced oscillations that can grow rapidly in magnitude. A power pushover, as described in the FAA handbook, may result if rotor force is rapidly removed, producing a tendency to pitch forward abruptly. This is often referred to as a forward tumble, buntover, or power pushover. Removing the rotor force is often referred to as unloading the rotor, and can occur if pilot-induced oscillations become excessive. A power pushover can occur on some gyroplanes that have the propeller thrust line above the center of gravity and do not have an adequate horizontal stabilizer. In this case, when the rotor is unloaded, the propeller thrust magnifies the pitching moment around the center of gravity. This nose pitching action could become self-sustaining and irreversible.

Probable cause

The pilot's abrupt liftoff during takeoff, and his failure to correct a pilot-induced-oscillation during takeoff initial climb which resulted in the main rotor blades striking the tail mounted rudder, and an in-flight loss of control. A factor in the accident was the pilot's lack of recent experience in a gyroplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC02FA064
Event ID
20020712X01113
Case number
ANC02FA064
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, coordinates. 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: bf802d7606dbadc966592cf4fc84bc4326af90e268f4035da32568a432c19ee0; retrieved 2026-09-20T19:58:48.424Z.