- Date
- November 15, 1999, 22:08 local (Nov 16, 1999, 03:08 UTC)
- Place
- Shelbyville, IN
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Enroute
- Aircraft
- N5388BCessna 182
- Weather
- Visual (VMC) · Night/dark
- Status
- Completed · report November 30, 2000
- Report
- Approved by Office Director
- FAA report
- 19991115045799A
- Case key
- 47782
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 inadequate preflight planning by the pilot and the exhaustion of usable fuel. A factor was the drainage ditch encountered on landing.
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
The pilot made a forced landing following a loss of engine power. The pilot reported no mechanical malfunction. He also stated that the landing was normal until he encountered a drainage ditch that caused the plane to nose over. A postaccident examination of the aircraft by a Federal Aviation Administration Inspector revealed no evidence of fuel within the fuel tanks. The fuel tanks were found to be intact. No preexisting anomalies were found with respect to the airframe, engine or systems.
Factual narrative
On November 15, 1999, at 2208 eastern standard time, a Cessna 182, N5388B, piloted by a private pilot, sustained substantial damage during a forced landing near Shelbyville, Indiana. The personal flight was conducted under the provisions of 14 CFR Part 91 and was operating on an instrument flight plan. Visual meteorological conditions prevailed at the time of the accident. The pilot, who was the sole occupant, reported no injuries. The flight departed from the Winder-Barrow Airport, Winder, Georgia, and was en route to the Indianapolis Metropolitan Airport (UMP), Indianapolis, Indiana.
While inbound to UMP, the pilot reported that the aircraft engine was running rough and advised controllers that he would divert to the Shelbyville Municipal Airport (GEZ), Shelbyville, Indiana. The pilot then reported to controllers that he was not going to make it to the airport. Radar contact was lost as the pilot was leaving 1300 feet mean sea level altitude.
A postaccident examination of the aircraft by a Federal Aviation Administration Inspector revealed no evidence of fuel within the fuel tanks. The fuel tanks were found to be intact. No preexisting anomalies were found with respect to the airframe, engine or systems.
In a written report, the pilot reported no mechanical malfunction. He also stated that the landing was "... normal until I [the pilot] encountered a drainage ditch that caused the plane to nose over".
Aircraft
- Registration
- N5388B
- Reported as
- Cessna 182
- Category
- Airplane
- Serial number
- 33388
- Airframe hours
- 1,220
- Engine
- Continental O-470, 230 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Personal · Part 91
- Registered owner
- Joseph C. Traynor
- Airworthiness certificate
- Standard, Normal
- Last inspection
- Annual · June 12, 1999 · 75 hours before
- Departed
- WDR · Winder, GA
- Destination
- UMP · Indianapolis, IN
- Flight plan
- IFR
- Airport
- GEZ · Shelbyville Municipal
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
- 43
- Certificate
- Private
- Airplane ratings
- Single-engine land
- Instrument ratings
- Airplane
- Medical
- Class 3, Valid Medical--w/ waivers/lim
- Seat
- Left
- Flight hours
- 300 total · 99 in this make and model · 207 as pilot in command · 71 in the last 90 days · 23 in the last 30 days · 8 in the last 24 hours
Weather
- Conditions
- Visual (VMC) · Night/dark
- Wind
- 360° at 7 knots
- Visibility
- 10 statute miles
- Lowest ceiling
- 10,000 ft broken
- Temperature
- 46 °F, dew point 25 °F
- Altimeter
- 30.00 inHg
- Observed at
- IND, 24 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.