FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL93LA092 · Jones LIGHTNING BUG 2 LIGHTNING

13 May 1993 · Walterboro, SC, United States

Jones LIGHTNING BUG 2 LIGHTNING · Accident: airframe, component or system failure en route

Report a problem

Event

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

Jones LIGHTNING BUG 2 LIGHTNING

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
N200NJ
Operator
Jones, Howell C. JR · private individual
Onboard fatalities
Unknown
Route
From not recordedTo 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
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
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

  • Flt control syst, elevator control attach points › Disconnected

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

NTSB narrative

THE COMMERCIAL PILOT WAS CONDUCTING A MAINTENANCE TEST FLIGHT TO EVALUATE A NEW PROPELLER INSTALLATION. THE AIRFRAME TOTAL TIME WAS ABOUT 7 HOURS. THE PILOT WAS THE DESIGNER AND BUILDER OF THE EXPERIMENTAL AIRCRAFT. DURING THE FLIGHT, HE REPORTED A LOSS OF ELEVATOR AUTHORITY. HE BAILED OUT OF THE AIRCRAFT, AND THE AIRCRAFT CRASHED INTO A WOODED, SWAMPY AREA. AN EXAMINATION OF THE FLIGHT CONTROL SYSTEM REVEALED THAT A ROD END FITTING HAD DISCONNECTED, RENDERING THE ELEVATOR INEFFECTIVE. THE PILOT REPORTED THAT HE WOULD CHANGE THE DESIGN OF THE FITTINGS TO INCORPORATE COTTER PINS FOR ADDED SECURITY ON FUTURE AIRCRAFT

Probable cause

THE DISCONNECTION OF AN ELEVATOR ROD END FITTING IN FLIGHT, WHICH DISABLED THE ELEVATOR

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL93LA092
Event ID
20001211X12284
Case number
ATL93LA092
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: 352864670e2af2657e84899083a71d06d6d59ebdd15b4a8f09e0eef1ca4bba28; retrieved 2026-09-21T22:57:21.290Z.