FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA02LA017 · Piper PA-24-250

16 Nov 2001 · Peachtree City, GA, United States

Piper PA-24-250 · Accident: loss of engine power en route

From 4A7 · Hampton, GA to Cobb County International Airport-McCollum Field (RYY)

Report a problem

Event

NTSB case
MIA02LA017
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-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
N8183P
Operator
Unknown
Onboard fatalities
Unknown
Route
From 4A7 · Hampton, GATo Cobb County International Airport-McCollum Field (RYY), Marietta, GA
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
Loss of engine power
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

  • Pilot in command › Operation with known deficiencies in equipment, attempted

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

NTSB narrative

The pilot stated that on November 16, 2001, he prepared to depart from his home airport, McCollum Field. As he performed an engine runup, he found the left magneto was not operating. He returned to the ramp and his mechanic disconnected and then reconnected the magneto "P" leads. The left magneto began to work. He departed McCollum Field and went to Peachtree City. He then flew to Tara Field, at Hampton, Georgia. When leaving Tara Field, he found that the left magneto was again inoperative. He called his mechanic and was told to disconnect the "P" leads and fly home. With the "P" leads disconnected, he could not check the magnetos. During takeoff, the engine appeared to develop full power. The EGT was normal. About 5 minutes after departure, the EGT pegged out high and one of the magnetos appeared to have quit. About a minute later, the engine quit. Atlanta Approach gave him radar vectors to the closest airport, Peachtree City. He could not make it to the airport and landed in a field with the gear down and full wing flaps extended. During rollout in the field, the airplane collided with a drainage ditch. The landing gear collapsed and the airplane slid to a stop. The magnetos had been overhauled by a local mechanic about 100 flight hours before the accident. During examination prior to running the engine after the accident, the "P" lead was disconnected from the right magneto and the spark retard lead was disconnected from the left magneto. The leads were reconnected and the engine was started. Only the right magneto was operating. The engine was operated to 1,500 RPM with a club propeller in the feathered position. The was no evidence of mechanical failure or malfunction of the engine assembly.The magnetos were tested at the manufacturers facilities. The left magneto condenser was inoperative causing the magneto to not operate. The right magneto operated normally. Manufacturer personnel stated that with one magneto inoperative, the exhaust gas temperature will become elevated due inefficient burning in the cylinder which carries over into the exhaust area. When you remove the "P" lead on these magnetos, they actually ground internally and become inoperative. Sometimes contamination prevents them from grounding immediately when the "P" lead is removed, but they eventually ground and become inoperative. He believes that with the spark retard disconnected on the left magneto and the "P" lead disconnected on the right magneto, that the left and right magnetos operated for takeoff due to the condenser working at this time on the left magneto and that the "P" lead internal grounding had contamination that prevented it from grounding immediately after removal of the "P" lead. Takeoff was normal at full power due to both magnetos working. Then either the left magneto quit due the condenser failing or the right quit due to it becoming internally grounded. The exhaust gas temperature went high and a small loss of power could be noted. Then the second magneto quit resulting in failure of the engine.

Probable cause

The pilot’s attempted operation of the aircraft with known deficiencies in the engine ignition system resulting in failure of the engine due to ignition system failure and damage to the airplane during the subsequent forced landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA02LA017
Event ID
20011123X02286
Case number
MIA02LA017
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: investigation status, coordinates. 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: 8ecabe6360249768e02389dcd2caa9d0358bc1546cb3c810ab889ca348a52f07; retrieved 2026-09-21T19:49:04.111Z.