FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI06LA031 · Piper PA-28-181

12 Nov 2005 · Milwaukee, WI, United States

Piper PA-28-181 · Accident: loss of engine power en route

From 5K6 · Westosha, WI to an unrecorded destination

Report a problem

Event

NTSB case
CHI06LA031
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
0 · 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

Piper PA-28-181

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
N2241P
Operator
Unknown
Onboard fatalities
Unknown
Route
From 5K6 · Westosha, WITo 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
En route · cruise
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
Loss of engine power
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Fuel starvation; Wire, transmission
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

  • Fluid, fuel › Starvation
  • Pilot in command › Fuel management, not performed

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

NTSB narrative

The airplane sustained substantial damage when it impacted power lines at night during an emergency descent after a loss of engine power. The pilot reported that he departed on the flight in order to keep current at night flying and to practice night takeoffs and landings. He reported that rain was forecast for later that night, but that the sky was clear and "bumpy" after departure. He ran into light rain and decided to return to the departure airport before the weather got any worse. He reported that the engine quit and he executed a forced landing to a "desolate street," but impacted wires. The airplane remained tangled in the power line wires, and emergency personnel removed the pilot from the suspended airplane about 2 hours later. The inspection of the airplane revealed that the left fuel tank contained no fuel, and that fuel "poured" out of the right fuel tank when it was drained of fuel. The fuel tanks were not compromised, and there were no fuel leaks from either tank. The fuel selector was selected to the left fuel tank. The flight duration was about 2.3 hours. The pilot's blood was tested for the presence of alcohols. The blood ethanol concentration was 0.286 grams per 100 milliliters. The FAA FAR Part 91.17 legal limit is 0.04. The pilot's FAA medical records revealed that the pilot had a history of alcohol-related traffic offenses since at least 20 years of age (17 years prior to the accident). The manager of the FAA Aerospace Medical Certification Division sent a letter to the pilot on June 26, 2002, which noted, "Our review of your medical records has established that you are eligible for a second-class medical certificate. ... Continued airman medical certification remains contingent upon your total abstinence from use of alcohol. ..." There is no indication of any additional requirement for evaluation or follow up. The pilot's most recent Application for 2nd Class Medical Certificate, dated April 21, 2005 indicated "no" in response to "HAVE YOU EVER IN YOUR LIFE BEEN DIAGNOSED WITH, HAD, OR DO YOU PRESENTLY HAVE ANY OF THE FOLLOWING ... Alcohol dependence or abuse." The pilot held a current second class medical certificate dated April 21, 2005.

Probable cause

The loss of engine power due to fuel starvation as a result of the pilot's fuel mismanagement. Factors to the accident included the pilot's impairment due to alcohol, the FAA's inadequate oversight when it issued the pilot a second class medical certificate, the power lines, and night.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI06LA031
Event ID
20051116X01849
Case number
CHI06LA031
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2005-11-13.
  • API snapshot SHA-256: ddf840f6cea2f1378550056a4e8979490db716eae56ff619602721a923ce1da5; retrieved 2026-09-21T18:51:48.556Z.