CEN16LA375 · Piper PA 32R-300
Piper PA 32R-300 · Accident: fuel starvation during takeoff
From Grants-Milan Municipal Airport (GNT) to Cedar City Regional Airport (CDC)
Event
- NTSB case
- CEN16LA375
- 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 PA 32R-300
- 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
- N4477F
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Grants-Milan Municipal Airport (GNT), Grants, NMTo Cedar City Regional Airport (CDC), Cedar City, UT
- Aircraft age
- About 40 years (built 1976)
- 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
- Takeoff
- 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
- Destroyed
Cause areas
- Aircraft › Fluids/miscellaneous hardware
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
After a preflight inspection and engine run up that revealed no anomalies, the private pilot and two passengers were departing on a cross-country flight. The pilot stated that the airplane became airborne approximately 5,000 ft down the 7,172-ft-long runway at 80 knots. Approximately 100 feet above ground level, he heard a "gurgle" and the engine experienced a loss of power. The pilot verified that the fuel pump was on and the throttle was in its full-forward position. The pilot then located a forced landing site and during the landing, the airplane impacted a tree. The occupants egressed, and the airplane was subsequently consumed by postcrash fire. The accident airport was located at an elevation about 6,500 ft mean sea level (msl). Given the atmospheric conditions at the time of the accident, the density altitude exceeded 9,000 ft msl, which would have significantly increased the airplane's takeoff distance and reduced its climb capability. The pilot's experience operating in high density altitude environments could not be determined. Review of photos from the accident site revealed that the fuel selector handle appeared to be located between the left fuel tank and off positions; however, the fuel selector was not examined and its position could not be verified, therefore, the reason for the reported loss of engine power could not be determined.
Probable cause
A loss of engine power for reasons that could not be determined based on the available information.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN16LA375
- Event ID
- 20160920X85700
- Case number
- CEN16LA375
- 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: e4a6c182ed544e512f22e19e3b1f9b1f0980b220dc66f27a38c1d7dc9bb86383; retrieved 2026-09-16T04:17:21.187Z.