- Date
- June 24, 1995, 08:45 local (13:45 UTC)
- Place
- Shelbyville, IN
- Injuries
- 1 minor
- Damage
- Substantial damage
- Phase of flight
- Takeoff
- Aircraft
- N30878Griner Bushby Mustang I
- Weather
- Visual (VMC) · Day
- Status
- Completed · report February 27, 1996
- Report
- Approved by Office Director
- FAA report
- 19950624017989A
- Case key
- 9924
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
Probable cause
the pilot's allowing the airplane to inadvertently liftoff. A factor was a malfunction of the flight control system.
Sequence of events
NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.
Analysis
An inadvertent lift-off occurred during a high speed taxi. The pilot encountered difficulty in controlling the airplane which required full right aileron and full right rudder. He found that high power setting aggravated the situation so he reduced power. He elected to attempt to return to the runway, but with the reduced power was not able to do so. He then conducted a forced landing in a crop field and the airplane went through a fence. Post accident examination failed to reveal the nature of the control problem. Continuity was established, but full travel of controls was not possible due to the extent of damage from the accident.
Factual narrative
On June 24, 1995, at 0845 central daylight time, a homebuilt Bushby Mustang I, N30878, piloted by a private pilot, impacted the terrain one-quarter mile east of runway 27 (2,670' x 190' dry/turf) at Shelbyville, Indiana following the initial flight of the airplane. The airplane sustained substantial damage and the pilot received minor injuries. The 14 CFR Part 91 flight was operating in visual meteorological conditions. No flight plan was on file. The local flight departed at 0840.
The pilot stated that he did not intend to fly the airplane, but rather conduct high speed taxi tests on runway 36. He reported that the airplane became airborne and seemed controllable so he elected to continue the flight. During the climb he realized that the airplane required full right aileron and full right rudder to maintain level flight. He said he found that increasing the airspeed made the condition worse so he reduced power. He initially elected to land on runway 36; however, traffic on that runway prevented his doing so. He then continued, planning a landing on runway 27; however at the reduced power necessary to keep the airplane controllable, he realized that he would not make it to runway 27. He then elected to conduct a forced landing in a crop field one-quarter mile east of runway 27. On touchdown the airplane went through a fence.
A post accident examination failed to reveal the nature of the control difficulties. Continuity was established; however, travel could not be verified due to the damage to the airframe. No other anomalies were noted in the control system of the airplane.
Aircraft
- Registration
- N30878
- Reported as
- Griner Bushby Mustang I (BUSHBY MUS)
- Category
- Airplane, amateur-built
- Serial number
- 001
- Engine
- Continental C-85-J, 85 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Personal · Part 91
- Registered owner
- John R. Griner
- Airworthiness certificate
- Special, Experimental (Special)
- Departed
- 3SM
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 47
- Certificate
- Private
- Airplane ratings
- Single-engine land
- Medical
- Class 3, Valid Medical--w/ waivers/lim
- Seat
- Center
- Flight hours
- 126 total · 9 in the last 90 days · 3 in the last 30 days
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 140° at 7 knots
- Visibility
- 5 statute miles
- Lowest ceiling
- None
- Temperature
- 77 °F, dew point 68 °F
- Altimeter
- 29.00 inHg
- Observed at
- IND, 25 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.