ATL94LA067 · Cessna 140
Cessna 140 · Accident: in flight collision with object en route
From Jackson County Airport (1A7) to an unrecorded destination
Event
- NTSB case
- ATL94LA067
- 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
Cessna 140
- Aircraft type
- Cessna 140
- 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
- N76342
- Operator
- Vassilev, James H. · private individual
- Onboard fatalities
- Unknown
- Route
- From Jackson County Airport (1A7), Gainesboro, TNTo 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
- 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, transmission
- 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
- Pilot in command › Clearance, not maintained
- Pilot in command › Proper altitude, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE STUDENT PILOT REPORTED THAT HE WAS FLYING LOW, OVER THE CUMBERLAND RIVER, WHEN THE AIRCRAFT COLLIDED WITH A POWER LINE. HE LOST CONTROL OF THE AIRPLANE, AND IT CRASHED INTO THE RIVER. HIS PASSENGER, WHO WAS NOT A PILOT, WAS FATALLY INJURED. THE PILOT WAS ISSUED HIS STUDENT CERTIFICATE 12 DAYS PRIOR TO THE ACCIDENT, AND AT THAT TIME REPORTED A TOTAL FLIGHT TIME OF 385 HOURS. AN INSPECTION OF THE WRECKAGE REVEALED NO EVIDENCE OF MECHANICAL FAILURE OR MALFUNCTION. THE WIRE WHICH WAS SEVERED BY THE AIRPLANE WAS ERECTED ABOUT 90 FEET ABOVE THE SURFACE OF THE RIVER.
Probable cause
THE PILOT'S FAILURE TO MAINTAIN A PROPER ALTITUDE, AND HIS FAILURE TO MAINTAIN CLEARANCE FROM THE TRANSMISSION WIRE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL94LA067
- Event ID
- 20001206X00846
- Case number
- ATL94LA067
- 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: 4821a1d19e5a10b1e9b37b4358aec9f61a46b5bad54cd0e9a49a6c5146bcf566; retrieved 2026-09-21T00:12:34.623Z.