CHI01FA146 · Piper PA-24-250
Piper PA-24-250 · Accident: partial loss of engine power (non-mechanical) while maneuvering
From Lee C Fine Memorial Airport (AIZ) to Schaumburg Regional Airport (06C)
Event
- NTSB case
- CHI01FA146
- 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
- 3 · 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-24-250
- Aircraft type
- Piper PA-24
- 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
- N7331P
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lee C Fine Memorial Airport (AIZ), Kaiser, MOTo Schaumburg Regional Airport (06C), Schaumburg, IL
- 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
- Maneuvering
- 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
- Partial loss of engine power (non-mechanical)
- 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
- Stall
- 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
- Pilot in command › Aircraft control, not maintained
- Pilot in command › Aircraft preflight, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During a forced landing the airplane stalled and impacted trees and terrain. Witnesses to the accident reported that the engine was running rough and intermittently prior to the accident. A global positioning system (GPS) receiver was recovered at the accident site and its track data was downloaded. The recovered GPS data showed the airplane's ground speed was between 73.7 - 79.8 mph during the last 10 seconds of data. The stall speed for the accident airplane with flaps retracted is 70 mph. Post-accident fuel samples taken from the fuel strainer and both electric fuel pumps were contaminated with water and particulate. Both electric fuel pumps contained rust, water, and particulate. The carburetor float bowl and accelerator pump-well were contaminated with fine particulate resembling silicon sand. The same fine particulate was observed in the carburetor idle tube passage and nozzle well. Fuel samples taken from the right main fuel cell and fuel selector were clear of debris and water. A fuel sample obtained from the departure airport was clear of debris and water. The accident airplane had been operated approximately 164 hours in the last 35 years, 47 hours in the last 15 years, 35 hours in the last 5 years, and 35 hours in the last year. According to Federal Aviation Regulations (FAR), the pilot-in-command is required to complete an aircraft preflight inspection in order to determine if the aircraft is in an airworthy condition. According to FAA AC 20-43C, "Fuel having a 'cloudy' appearance or definitely 'offcolor' should be suspected of contamination or deterioration and should not be used." According to Airplane Flying Handbook, "Significant and/or consistent water or sediment contamination are grounds for further investigation by qualified maintenance personnel. Each fuel tank sump should be drained during preflight and after refueling."
Probable cause
Aircraft control not being maintained by the pilot during the forced landing and inadequate preflight inspection performed by the pilot. Contributing factors to the accident were the fuel system contamination that resulted in the loss of engine power, the encountered stall, and trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI01FA146
- Event ID
- 20010608X01134
- Case number
- CHI01FA146
- 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: 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: 6c33b5498f872ba8e02b27c19911fc549d0651105169d407a897593c8986350d; retrieved 2026-09-20T20:31:53.873Z.