CEN20LA384 · Piper PA32R 301T
4D Aviation Piper PA32R 301T · Accident: loss of engine power (total) en route
From Jones Field (F00) to Commerce Municipal Airport (2F7)
Event
- NTSB case
- CEN20LA384
- 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 PA32R 301T
- Aircraft type
- Piper PA32
- 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
- N3576X
- Operator
- 4D Aviation
- Onboard fatalities
- Unknown
- Route
- From Jones Field (F00), Bonham, TXTo Commerce Municipal Airport (2F7), Commerce, TX
- Aircraft age
- About 41 years (built 1979)
- 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 · climb to cruise
- 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
- Loss of engine power (total)
- 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 › Aircraft power plant
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, he and a passenger departed on a personal flight. The airplane was on its first flight after maintenance work, which included the replacement of the engine exhaust.
Shortly after departure, the pilot noted high turbine inlet and cylinder head temperatures. The pilot tried to return to the airport; however, about 2 miles short of the airport, the engine experienced a total loss of power. During the forced landing the landing gear collapsed in the soft terrain which resulted in substantial damage to the right wing.
An engine examination found that the No. 6 cylinder fuel injector line was not connected. It was also noted that initially the turbocharge was not free to rotate, but once freed it rotated without resistance.
The accident is consistent with a loss of engine power due to a fuel injector line not being connected. This is likely due to maintenance personnel not adequately tightening the No. 6 cylinder fuel injector line during the recent maintenance.
Probable cause
The loss of engine power due to a disconnected fuel injector line that was not properly tightened during recent maintenance.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN20LA384
- Event ID
- 20200907X23556
- Case number
- CEN20LA384
- 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, cause areas. 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: 4f06e11b5981fb4cc821424b63f12d7e3374e0b124af0b6bfc4e1242f00036da; retrieved 2026-09-16T12:59:57.360Z.