FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA03LA134 · John L. Klein Marquart ChargerMA-5

25 Jun 2003 · Pierson, FL, United States

John L. Klein Marquart ChargerMA-5 · Accident: airframe, component or system failure en route

From Ormond Beach Municipal Airport (OMN) to Pierson Municipal Airport (2J8)

Report a problem

Event

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

John L. Klein Marquart ChargerMA-5

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
N707JK
Operator
Unknown
Onboard fatalities
Unknown
Route
From Ormond Beach Municipal Airport (OMN), Ormond Beach, FLTo Pierson Municipal Airport (2J8), Pierson, FL
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
Airframe, component or system failure
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tree(s)
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

  • Flt control syst, elevator control cable/rod › Separation

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

NTSB narrative

A witness stated that he was about 900 to 1,000 feet, and N707JK was about 400 to 500 feet below, in a position forward of his airplane's wing, such that N707JK was in constant view while flying in a loose formation. The witness said he saw left rudder movement on N707JK, and N707JK yawed to the left, yawed to the right, and then the nose dipped slightly and N707JK disappeared immediately in the canopy of trees. Within several seconds the witness said he was over the area where N707JK had disappeared, but he could not see anything due to the trees. He then increased his altitude, and made a radio communications call, declaring an emergency. Postaccident examination of the airplane revealed that that the rod end bearing on the elevator push/pull tube had disconnected from the rear cockpit's control stick, resulting in a loss of elevator control, and the connecting clevis bolt, castle nut, and cotter key were never recovered.

Probable cause

Separation of the elevator push/pull tube from the rear cockpit's control stick for undetermined reasons, which resulted in a loss of elevator control, an uncontrolled descent, and an impact with trees.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA03LA134
Event ID
20030702X01006
Case number
MIA03LA134
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: 3605f29f27cb2e8c62c2e8773baaf0ace9c4a04f3952e98fe2e5bef06604d917; retrieved 2026-09-21T09:26:40.113Z.