CHI88LA170 · Piper PA-32R-301T PA-32R-301
Piper PA-32R-301T PA-32R-301 · Accident: airframe, component or system failure en route
From Bolingbrook's Clow International Airport (1C5) to UCA · Utica, NY
Event
- NTSB case
- CHI88LA170
- 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
- 0
- 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-32R-301T PA-32R-301
- Aircraft type
- Piper PA-32
- 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
- N8069S
- Operator
- Smith, Loren E. · private individual
- Onboard fatalities
- Unknown
- Route
- From Bolingbrook's Clow International Airport (1C5), Plainfield, ILTo UCA · Utica, NY
- 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 · climb to 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
- Airframe, component or system failure
- 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
- Fuel system, line fitting › Loose
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING CLIMBOUT AFTER TAKEOFF, THE PILOT EXPERIENCED AN ENGINE FIRE AND DIVERTED TO CHICAGO'S MIDWAY AIRPORT FOR AN EMERGENCY LANDING. THE PILOT EXECUTED EMERGENCY PROCEDURES, SHUT DOWN THE ENGINE, THE FUEL SUPPLY, AND ALL ELECTRICAL LOAD. WHEN THE PILOT KNEW HE HAD THE RUNWAY MADE, HE SELECTED THE GEAR DOWN POSITION WITH THE GEAR HANDLE, BUT ELECTED NOT TO VERIFY GEAR DOWN AND LOCKED FOR SAFETY REASONS. THE GEAR FAILED TO EXTEND; A GEAR UP LANDING ENSUED. IT WAS REPORTED THAT THE LANDING GEAR WOULD DROP WHEN THE GEAR HANDLE WAS ACTIVATED. POST-ACCIDENT EXAMINATION OF THE ENGINE COMPARTMENT REVEALED THAT THE FIRE WAS THE RESULT OF A LOOSE LINE FITTING ON A FUEL INJECTOR NOZZLE WHICH ALLOWED RAW FUEL TO SPRAY INTO THE COMPARTMENT; SPECIFICALLY, ONTO THE TURBO-CHARGER. THE AIRCRAFT WAS JACKED UP AND REMOVED FROM THE RUNWAY BEFORE AN INVESTIGATOR ARRIVED ON THE SCENE.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record CHI88LA170
- Event ID
- 20001213X26186
- Case number
- CHI88LA170
- 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: 75a14c4a82db385443bc39c0d292c151749311d707da06f82dc8b9d96f3bc44b; retrieved 2026-09-23T09:32:56.150Z.