FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL84LA231 · Beech C23

21 Jul 1984 · Gainesboro, TN, United States

Stevens Aviation Beech C23 · Accident: in flight collision with object while maneuvering

From Jackson County Airport (1A7) to Nashville International Airport (BNA)

Show on map Search Wikipedia NTSB source dataset
Report a problem

Event

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

Beech C23

Aircraft type
Beechcraft 23
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
N18355
Onboard fatalities
Unknown
Route
From Jackson County Airport (1A7), Gainesboro, TNTo Nashville International Airport (BNA), Nashville, TN
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
In flight collision with object
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
Wire, static
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

  • Pilot in command › In-flight planning/decision, poor
  • Pilot in command › Proper altitude, not maintained
  • Pilot in command › Total

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

NTSB narrative

THE ACFT COLLIDED WITH A STATIC WIRE WHILE FLYING ALONG A RIVER. THE COLLISION OCCURRED AT 350 FT AGL ABOUT 5 MILES NE OF THE ARPT. THE LEFT WING HIT THE WIRE WHICH CUT INTO THE WING AND PENETRATED A FUEL CELL. FUEL ESCAPED FROM THIS CELL AND WHEN THE ACFT LANDED AT THE ARPT THE FUEL IGNITED. THE FIRE WAS PUT OUT BY FIRE FIGHTERS. THE PLT SAID HE DID NOT SEE THE WIRES UNTIL JUST BEFORE IMPACT.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record ATL84LA231
Event ID
20001214X40197
Case number
ATL84LA231
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: 1843b6c68d71d2c5b9c04ed6f70eaeacd0881ae9c25a7353dbc4e6402bdb1994; retrieved 2026-09-23T20:05:25.995Z.