FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA86FA033 · North American T-28A

23 Nov 1985 · Lantana, FL, United States

North American T-28A · Accident: partial loss of engine power (mechanical failure) during initial climb

From Palm Beach County Park Airport (LNA) to an unrecorded destination

Report a problem

Event

NTSB case
MIA86FA033
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
1 · all aircraft and ground
Ground fatalities
0
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

North American T-28A

Aircraft type
North American T-28
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
N9867C
Operator
Unknown
Onboard fatalities
Unknown
Route
From Palm Beach County Park Airport (LNA), Lantana, FLTo not recorded
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
Destroyed

Cause areas

  • Ignition system, ignition harness › Incorrect
  • Ignition system, spark plug › Arcing
  • Pilot in command › Aircraft preflight, inadequate
  • Pilot in command › Judgment, improper
  • Pilot in command › Maintenance, installation, improper
  • Pilot in command › Maintenance, service of aircraft/equipment, improper

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE PILOT/MECHANIC HAD RECENTLY RE-INSTALLED A REBUILT ENGINE IN THE AIRCRAFT AND PERFORMED A VERY SHORT RUN-UP PRIOR TO TAKEOFF. WITNESSES STATED THE AIRCRAFT ENGINE MADE POPPING NOISES AND WAS BELCHING BLACK SMOKE DURING THE TAKEOFF ROLL. THE AIRCRAFT BECAME AIRBORNE AND MUSHED AROUND A LEFT 180 DEGREE TURN BEFORE CRASHING IN A SWAMPY AREA AT THE AIRPORT EDGE. EXAMINATION OF THE IGNITION HARNESS AND SPARK PLUGS REVEALED THAT A 7 MM HARNESS WAS INSTALLED UTILIZING 5 MM SPARKPLUG CONNECTORS. SIX SPARKPLUGS EXHIBITED EVIDENCE OF FLASHOVER IN THE SPARKPLUG CONNECTOR WELLS. THIS CAUSED A PARTIAL POWER LOSS OF THE TOTAL REQUIRED POWER AVAILABLE AND NECESSARY FOR FLIGHT.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record MIA86FA033
Event ID
20001214X38277
Case number
MIA86FA033
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. 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: ff0ca026f2e7552cfb2042831ecb508a1440b5065eab55ea1eb49c5d342e88a2; retrieved 2026-09-21T04:45:33.468Z.