CHI01LA009 · Piper PA-28-140
Piper PA-28-140 · Accident: partial loss of engine power (non-mechanical) en route
From Wilkes-Barre/Scranton International Airport (AVP) to Capital Region International Airport (LAN)
Event
- NTSB case
- CHI01LA009
- 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-28-140
- 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
- N732FL
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Wilkes-Barre/Scranton International Airport (AVP), Avoca, PATo Capital Region International Airport (LAN)
- 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 · descent
- 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
- Fuel exhaustion; Tree(s)
- 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 › Preflight planning/preparation, inaccurate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane sustained substantial damage on impact with trees and terrain during a forced landing after the pilot declared he was out of fuel. The pilot was seriously injured and the passenger sustained minor injuries. The pilot stated, "Departed Wilkes-Barre/Scranton Airport at 5:01P after refueling. Visually checked fuel level prior to departure for Lansing. ... Fuel starvation occurred east of LAN after 4 hrs and 35 min of flight (approx) and impact 4 1/2 mi east of destination. ... I slowed the aircraft and applied flaps. I headed for a dark area on the ground and impacted trees." Federal Aviation Administration inspectors performed an on-scene examination of the wreckage. An inspector stated, "An on scene investigation of the aircraft was conducted as well as an inspection of the engine after recovery of the aircraft. No abnormalities were noted other than there was no fuel in either tank or any evidence of fuel at the scene." The pilot stated that he "figured 9 gal/hr for cruise, leaned 75% at roughly 2500rpm. ... Pilot stated that he probably miscalculated winds."
Probable cause
the pilot's inaccurate preflight planning. Factors were the fuel exhaustion, the trees, and the bright night condition.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI01LA009
- Event ID
- 20001212X22121
- Case number
- CHI01LA009
- 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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2000-10-12.
- API snapshot SHA-256: 97528e3701c36bb2c6175ebbc82854501348f31e11acc4a1736e3dac0615ba50; retrieved 2026-09-21T10:22:47.556Z.