CHI96LA030 · Cessna 172N
Cessna 172N · Accident: total loss of engine power (non-mechanical) en route
From Buffalo Niagara International Airport (BUF) to South Bend International Airport (SBN)
Event
- NTSB case
- CHI96LA030
- 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
Cessna 172N
- Aircraft type
- Cessna 172
- 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
- N738LM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Buffalo Niagara International Airport (BUF), Buffalo, NYTo South Bend International Airport (SBN), South Bend, IN
- 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
- Total loss of engine power (non-mechanical)
- 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 › Exhaustion
- Pilot in command › Fuel consumption calculations, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT HAD FILED AN IFR FLIGHT PLAN FROM BUFFALO, NEW YORK, TO SOUTH BEND, INDIANA, AND SPENT 20 MINUTES GROUND RUNNING TIME WAITING FOR AN IFR CLEARANCE. DURING THE FLIGHT THE LEFT FUEL TANK GAUGE WAS ERRATIC, SO THE PILOT IGNORED IT. THE IN-FLIGHT TIME WAS 4 HOURS AND 25 MINUTES BEFORE A TOTAL LOSS OF POWER OCCURRED. THE PILOT STATED THE FUEL CONSUMPTION FOR THE AIRPLANE WAS BETWEEN 8.5 TO 8.9 GPH. AT 8.5 GPH, THE FUEL BURNED DURING THE 4 HOUR AND 25 MINUTE FLIGHT WOULD HAVE BEEN 37.5 GALLONS, PLUS AN ADDITIONAL 2 GALLONS USED FOR THE 20 MINUTE GROUND TIME, FOR A TOTAL OF 39.5 GALLONS USED. AT 8.9 GPH, THE TOTAL WOULD HAVE BEEN 41.3 GALLONS. THE PILOT'S OPERATING HANDBOOK SHOWS THE USABLE FUEL OF 40 GALLONS, WITH 3 GALLONS UNUSABLE. THE POSTCRASH INVESTIGATION REVEALED 1-1/2 GALLONS OF FUEL IN THE RIGHT TANK; NO FUEL IN THE LEFT TANK.
Probable cause
fuel exhaustion as a result of the pilot's improper fuel consumption calculations. Factors related to the accident were: the pilot's lack of familiarity with the aircraft and operating with a known malfunctioning fuel gauge.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI96LA030
- Event ID
- 20001207X04826
- Case number
- CHI96LA030
- 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: 0286d12cd06c200091985c42756e6fdef60ecc66c2f03f1031e6d8801deebacd; retrieved 2026-09-22T23:03:08.402Z.