ATL91FA073 · Piper PA-24-250
Piper PA-24-250 · Accident: in flight encounter with weather en route
From Gwinnett County Briscoe Field (LZU) to Spirit of St Louis Airport (SUS)
Event
- NTSB case
- ATL91FA073
- 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
- 1 · 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
- Instrument 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
- N7457P
- Operator
- Hannasch, Thomas P. · private individual
- Onboard fatalities
- Unknown
- Route
- From Gwinnett County Briscoe Field (LZU), Lawrenceville, GATo Spirit of St Louis Airport (SUS), St. Louis, MO
- 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
- In flight encounter with weather
- 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; Stall
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Fluid, fuel › Starvation
- Pilot in command › Fuel tank selector position, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PRIVATE PILOT WAS ON AN IFR FLIGHT TO ST. LOUIS. WHILE APPROACHING THE NASHVILLE, TN. AREA, HE ENCOUNTERED ICING CONDITIONS, AND REQUESTED A DESCENT. THE ICING PERSISTED, SO HE REQUESTED AN ILS APPROACH TO NASHVILLE. THE AIRCRAFT CRASHED ABOUT 12 MILES SSW OF THE NASHVILLE AIRPORT, AFTER THE PILOT REPORTED THAT HE HAD LOST POWER, AND WAS STALLING. AN INSPECTION OF THE WRECKAGE REVEALED THAT THE LEFT, AUXILIARY FUEL TANK WAS EMPTY OF FUEL, AND THE FUEL SELECTOR VALVE WAS STILL IN THE 'LEFT AUX' TANK POSITION. NO EVIDENCE OF PRE-EXISTING MECHANICAL MALFUNCTION OR FAILURE WAS FOUND.
Probable cause
THE PILOT'S FAILURE TO SELECT A PROPER FUEL TANK FOR FLIGHT, RESULTING IN FUEL STARVATION TO THE ENGINE, AND SUBSEQUENT ENGINE STOPPAGE. FACTORS WERE THE PILOT'S INADEQUATE EVALUATION OF THE WEATHER CONDITIONS ALONG HIS ROUTE OF FLIGHT, AND HIS FLIGHT INTO KNOWN ADVERSE WEATHER CONDITIONS (ICING).
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL91FA073
- Event ID
- 20001212X16541
- Case number
- ATL91FA073
- 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 1991-03-30.
- API snapshot SHA-256: 5122dfd4c0214cd3d7472c15ac3505695ec8ee953edc7c8b6ccd6f56034beaf1; retrieved 2026-09-21T01:53:36.212Z.