FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN18LA377 · Piper PA32 300

7 Sept 2018 · Roanoke, TX, United States

Piper PA32 300 · Accident: loss of engine power (total) during initial climb

From Aero Valley Airport (52F) to Gulfport Biloxi International Airport (GPT)

Report a problem

Event

NTSB case
CEN18LA377
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 PA32 300

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
N33354
Operator
Unknown
Onboard fatalities
Unknown
Route
From Aero Valley Airport (52F), Roanoke, TXTo Gulfport Biloxi International Airport (GPT), Gulfport, MS
Aircraft age
About 43 years (built 1975)
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
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

  • Not determined › Not determined

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The commercial pilot and five passengers departed on a personal night cross-country flight. According to the pilot, the engine start and run-up were uneventful. Shortly after takeoff, the engine lost total power, and the pilot was unable to maintain altitude. He conducted a forced landing, which resulted in substantial damage to the fuselage and wings.

An engine examination revealed that the upper right spark plugs were in a worn-out normal condition and the lower spark plugs were in a worn-out severe condition. The lower spark plugs were replaced, and a test engine run was conducted; the engine started and ran without hesitation at various power settings. However, it was noted during the test that the engine would not run on the right magneto. Further examination of the right magneto found a failed magneto coil. Despite the failed coil on the right magneto and the spark plug condition, the engine ran at full power settings. No other anomalies were noted with the engine or fuel system that would have precluded normal operation. A failed magneto or the noted spark plug conditions would have resulted in a rough-running engine but not a complete loss of engine power as the pilot described. Thus, the reason for the total loss of power could not be determined.

Probable cause

The total loss of engine power for reasons that could not be determined based on the available evidence.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN18LA377
Event ID
20180910X12852
Case number
CEN18LA377
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (5)
  • 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, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2018-09-08.
  • API snapshot SHA-256: f93b8db9880d1ae41acfed3498ea018836017300e51de97118e1ba42808e1607; retrieved 2026-09-16T08:13:44.564Z.
  • Corrected after a review of the NTSB narrative, which states these values explicitly: destination. Misspelled city name; GPT is Gulfport-Biloxi International, Gulfport, MS.