FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL94LA039 · Air & Space 18A

16 Jan 1994 · Atlanta, GA, United States

Air & Space 18A · Accident: loss of control in flight while maneuvering

From 9A7 · Jonesboro, GA to 9A7

Report a problem

Event

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

Air & Space 18A

Aircraft type
Air Space 18
Category
Gyroplane
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
N6118S
Operator
Unknown
Onboard fatalities
Unknown
Route
From 9A7 · Jonesboro, GATo 9A7
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
Maneuvering
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 control in flight
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

  • Reason for occurrence undetermined

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

NTSB narrative

THE PILOT WAS FLYING POWER LINE PATROL IN THE GYROPLANE WHEN HE EXPERIENCED AN UNCONTROLLED DESCENDING RIGHT TURN. EFFORTS BY THE PILOT TO CORRECT THE DESCENDING TURN FAILED. THE PILOT SELECTED A BASEBALL FIELD AND ATTEMPTED AN EMERGENCY LANDING. WHILE ON SHORT FINAL, THE PILOT REALIZED THAT A COLLISION WAS UNAVOIDABLE IF HE CONTINUED THE EXISTING HEADING, SO HE INITIATED A FLARE ABOUT 8 FT ABOVE THE GROUND. AS THE AIRCRAFT FELL, THE MAIN ROTOR BLADES STRUCK THE GROUND. EXAMINATION OF THE TRANSMISSION AND CLUTCH ENGAGEMENT SYSTEM FAILED TO DISCLOSE A MECHANICAL EXPLANATION FOR THE INADVERTENT ENGAGEMENT OF THE CLUTCH ASSEMBLY. THE MAIN ROTOR SYSTEM EXAMINATION ALSO FAILED TO DISCLOSE A MECHANICAL MALFUNCTION OR COMPONENT FAILURE OF ROTOR SYSTEM COMPONENTS,

Probable cause

A LOSS OF CONTROL FOR UNDETERMINED REASONS.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL94LA039
Event ID
20001206X00582
Case number
ATL94LA039
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: 04a9b3a17303c78052b4644fbf3fac55ac357b9dcc91cd7bb791d3828c8792ab; retrieved 2026-09-23T01:23:31.418Z.