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

August 8, 2004 · Giles Mustang II · N91061

Rainelle, WV

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
August 8, 2004
Injury Outcomes
1 injury (1 serious injury)
Location
Rainelle, WV
Aircraft
Giles Mustang II
Tail Number
N91061
Injuries
Serious
Aircraft Damage
Substantial
NTSB Number
IAD04LA035

The pilot of the homebuilt airplane reduced power on the downwind leg of the traffic pattern to initiate a low approach to the runway. The airplane was on final approach when the pilot attempted to add power to maintain his desired glide path. When he pushed the throttle lever forward, there was no response from the engine. Remedial actions by the pilot failed to restore control of the engine. During the subsequent forced landing to a field, the engine continued to run at the reduced power setting. On short final to the field, he noticed a dead tree with no foliage in his path, but determined that his altitude and airspeed were too low to maneuver around it. The airplane struck the tree, contacted the ground, spun around, and came to rest facing opposite the direction of travel. Examination of the throttle control after the accident revealed a separation of the throttle cable outer sheath and the inner throttle cable. When forward movement was applied to the throttle control, the inner cable bowed, and did not transfer forward motion to the throttle arm.

NTSB Probable Cause

The partial loss of engine power due to a broken throttle mechanism, which resulted in a forced landing over unsuitable terrain

Full Narrative

On August 8, 2004, at 1330 eastern daylight time, a homebuilt Mustang II, N91061, was substantially damaged during a forced landing in Rainelle, West Virginia. The certificated airline transport pilot was seriously injured. Visual meteorological conditions prevailed for local personal flight that originated at Rainelle Airport, Rainelle, West Virginia, at 1325. No flight plan was filed for the flight conducted under 14 CFR Part 91. During a telephone interview, the pilot reported that after takeoff he intended to fly a low pass down runway 35 prior to departing the traffic pattern. The takeoff and initial climb to the downwind leg of the traffic pattern were routine, and the pilot reduced power to arrest his climb and begin a descent through the base and final legs of the pattern. He estimated that his power setting was between 700 and 1,000 rpm after the power reduction. Once established on the final approach, the pilot perceived that his approach angle was too shallow, and pushed the throttle forward to re-intercept his desired glide path. There was no response from the engine, and actuation of the fuel boost pumps, carburetor heat, and the fuel selector valve failed to restore control of the engine. However, the engine continued to run at 700 to 1,000 RPM. The pilot determined that he couldn't reach the runway, which was on a hilltop, and turned down a valley adjacent to the airport in search of a forced landing area. He over flew several fields due to large bales of hay obstructing the landing surface, and selected an open field about 1 to 2 miles northeast of the airport. The pilot selected an approach path between two trees that bordered the field. On short final, he noticed a dead tree with no foliage in his path, but determined that his altitude and airspeed were too low to maneuver around it. The airplane struck the tree, contacted the ground, spun around, and came to rest facing opposite the direction of travel. A West Virginia Army National Guard MEDEVAC helicopter overheard the pilot's radio calls, landed at the crash site, and transported the pilot to a local hospital for treatment. Examination of the airplane at the scene by Federal Aviation Administration (FAA) aviation safety inspectors revealed that the engine and its associated controls were almost completely separated from the airplane during the crash sequence. Follow-up examination by the inspectors revealed a separation of the throttle cable outer sheath and the inner throttle cable. When forward movement was applied to the throttle control, the inner cable bowed, and did not transfer forward motion to the throttle arm. The pilot reported that other than the loss of engine control, there were no anomalies of note. According to FAA Advisory Circular AC-20-27D, Certification and Operation of Amateur-Built Aircraft: "...FAA inspections of amateur-built aircraft have been limited to ensuring the use of acceptable workmanship methods, techniques, practices, and issuing operating limitations necessary to protect persons and property not involved in this activity." The weather reported at Lewisburg, West Virginia, 16 miles northwest of Rainelle, at 1337, included winds from 190 degrees at 5 knots, 10 statute miles visibility, scattered clouds at 5,000 feet, temperature 68 degrees Fahrenheit, dew point 55 degrees Fahrenheit, and a barometric pressure of 30.22 inches of mercury.

Flight

Event TypeAccident
Event Time13:30 EDT
Nearest AirportRainelle Airport (1nm NNE)
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftGiles Mustang II
Tail NumberN91061
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320-BIA · Reciprocating · 160
Seats2

People & Injuries

Injury Summary1 injury (1 serious injury)
Fatal0
Serious1
Minor0
Uninjured0
Total1
Crew 1Age 65 · Second Class · Serious

Conditions

ConditionsVMC
LightDaylight
Wind190° @ 5 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point68 F / 55
Altimeter30.21 inHg
Observation Time17:37
Weather SourceWFAC

Appendix: Source Data