FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL05LA084 · de Havilland DH-82-C

21 May 2005 · Franklin, GA, United States

de Havilland DH-82-C · Accident: partial loss of engine power (mechanical failure) during initial climb

From Gum Creek Airport (8GA1) to Saluda County Airport (6J4)

Report a problem

Event

NTSB case
ATL05LA084
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

de Havilland DH-82-C

Aircraft type
de Havilland DH-82
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
N82CQ
Operator
Ronald Dick
Onboard fatalities
Unknown
Route
From Gum Creek Airport (8GA1), Franklin, GATo Saluda County Airport (6J4), Saluda, SC
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
Initial climb
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
Partial loss of engine power (mechanical failure)
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

  • Ignition system, magneto › Failure, total

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 he conducted an engine run up and the airplane experienced a magneto drop. A subsequent check of the magnetos revealed no anomalies. The pilot departed from runway 24 and the airplane was about 50- feet above the ground when the engine experienced a partial loss of engine power and a reduction in engine rpm. The pilot initiated a forced landing and the airplane collided with power lines and the ground. Examination of the engine assembly and fuel system revealed no anomalies. The left and right magnetos were removed. The right magneto was turned by hand and spark was present on all ignition towers. The left magneto would not produce an ignition spark when turned by hand. The left magneto was disassembled. The coil was removed and internal oil from the coil was present on the rotor and housing.

Probable cause

The total failure of the left magneto resulting in a partial loss of engine power on initial takeoff climb, forced landing, and in-flight collision with wires and the ground.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL05LA084
Event ID
20050601X00692
Case number
ATL05LA084
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: 5983805b69b5ebeeb1d6b518beca7960d076c5ed5ba37b21efe5ab91343f2b2f; retrieved 2026-09-21T19:01:15.230Z.