ERA16LA051 · Piper PA28 180
Piper PA28 180 · Accident: fuel starvation during initial climb
From Gwinnett County Briscoe Field (LZU) to Gwinnett County Briscoe Field (LZU)
Event
- NTSB case
- ERA16LA051
- 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
- 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 PA28 180
- Aircraft type
- Piper PA28
- 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
- N3971R
- Operator
- Resnick Quinn A
- Onboard fatalities
- Unknown
- Route
- From Gwinnett County Briscoe Field (LZU), Lawrenceville, GATo Gwinnett County Briscoe Field (LZU), Lawrenceville, GA
- Aircraft age
- About 44 years (built 1971)
- 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
- Initial climb
- Defining eventThe 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
- Fuel starvation
- 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
- 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
- Aircraft › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight instructor and student pilot departed their home airport with about 34 gallons of fuel on board the airplane for the planned approximate 60-mile, round-trip, cross-country instructional flight. The student pilot reported that, after landing at the destination airport, they completed two more full-stop landings before returning to, and then landing uneventfully at, the departure airport. The flight instructor wanted the student pilot to complete one more landing before concluding the lesson. The student stated that, during the subsequent takeoff, everything seemed normal until he turned the airplane onto the crosswind leg of the airport traffic pattern, at which time the engine lost all power. The flight instructor then took control of the airplane. The flight instructor reported that he chose not to attempt to turn back and glide to the airport because the airplane was about 500 ft above ground level. He subsequently performed a forced landing straight ahead into trees.
Both fuel tanks were compromised during the impact, and the fuel quantity at impact could not be determined. Subsequently, an engine test run was performed with no anomalies noted. Both pilots reported that they did not switch the fuel tanks following the total loss of engine power. The student pilot further stated that the airplane "ran out of gas." Review of performance information for the make and model airplane revealed that, based on the reported fuel onboard the airplane at the beginning of the day, it should have had between 5 and 10 gallons of fuel remaining at the time of the accident. Although the amount of fuel in each fuel tank could not be determined, the loss of engine power likely resulted from a lack of available fuel in the selected tank. Because the flight instructor was the pilot-in-command and told the student to conduct another landing, he should have been more cognizant of the fuel level in the tanks.
Probable cause
The flight instructor's inadequate fuel management, which resulted in a total loss of engine power during initial climb due to fuel starvation and a subsequent forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA16LA051
- Event ID
- 20151124X61620
- Case number
- ERA16LA051
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 14d3c00a234211af1b6d6cc153cb2e7d4db394d947351d2bf10beb86f38bfb7e; retrieved 2026-09-16T02:59:19.391Z.