FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA10FA148 · Piper PA-28-180

23 Feb 2010 · Springfield, KY, United States

KMT Consultants Piper PA-28-180 · Accident: loss of engine power (total) on approach

From St Clair County Airport (PLR) to Lebanon Springfield Airport - George Hoerter Field (6I2)

Report a problem

Event

NTSB case
ERA10FA148
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
Instrument Meteorological Cond

Piper PA-28-180

Aircraft type
Piper PA-28
Category
Airplane
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
N7778W
Onboard fatalities
Unknown
Route
From St Clair County Airport (PLR), Pell City, ALTo Lebanon Springfield Airport - George Hoerter Field (6I2), Springfield, KY
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
Approach · IFR final approach
Defining eventThe 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
Loss of engine power (total)
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

  • Aircraft › Fluids/miscellaneous hardware
  • Personnel issues › Physical
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot departed on the final 2-hour leg of a multi-leg flight into night instrument meteorological conditions after purchasing enough fuel to fly approximately 2 hours. He conducted the flight to his destination without the navigational publications for the route of flight, the instrument approaches at the destination airport, and with a Global Positioning System (GPS) navigational software data card that expired 4 years prior to the accident. Nearing his destination, the pilot contacted an air traffic controller and requested a non-directional beacon approach that was out of service, as posted in a notice to airman. The pilot then asked for a "GPS overlay" of the approach, and was advised that there was none. The pilot was issued a clearance for a GPS approach, subsequently reported crossing waypoints on the approach, then announced that his destination was in sight before cancelling his instrument clearance. There were no further transmissions received from the pilot.

Examination of the airplane at the accident site, approximately one-half mile from the destination airport, revealed no evidence of fuel and no evidence of mechanical anomalies with the engine or airframe. A 375-ml bourbon bottle, which contained approximately 100 ml of bourbon, was removed from the pilot's pocket during the medical examiner's recovery at the site.

Toxicological testing revealed that the pilot's blood alcohol content was 0.11 percent. A review of law enforcement and Federal Aviation Administration (FAA) records revealed that the pilot had been arrested for driving while intoxicated or driving under the influence (DUI) on at least two occasions, only one of which he reported. Further research of the pilot's records by the FAA revealed that they had improperly coded the pilot's medical application, which precluded the FAA from crosschecking information from his medical applications with the National Driver Register for potential alcohol-related motor vehicle actions. FAA processes did not independently identify at least two prior convictions of the pilot for DUI, though he had informed them of one of the events, and the FAA had not requested details of the offense reported. The NTSB obtained the arrest report for the event reported to the FAA by the pilot, and the arrest report noted that the pilot had been driving with a blood alcohol level of 0.20 percent. Given the pilot's history of multiple episodes of driving while intoxicated, and particularly given the level of tolerance exhibited by driving with a blood alcohol level of 0.20 percent, it is almost certain that he was substance dependent, a condition that is disqualifying for medical certification. Had the appropriate information been requested, the FAA would have known that the pilot was likely substance dependent and could have taken appropriate action, particularly given that the pilot had applied for and received 1st class medical certification.

Probable cause

The pilot's inadequate preflight planning, which resulted in a total loss of engine power due to fuel exhaustion, and the pilot's impairment due to alcohol. Contributing to the accident was the Federal Aviation Administration's failure to adequately oversee the pilot's medical certification.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA10FA148
Event ID
20100223X72903
Case number
ERA10FA148
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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. 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: 6ef1ece46951c86b05fb9a4e81d9eafd396db901bfdcb389f1a7a84fbc89b22b; retrieved 2026-09-13T20:39:58.208Z.