ATL03LA080 · Rans S-12
Rans S-12 · Accident: in flight collision with object while maneuvering
From West Point, TN (private airstrip) to West Point, TN (private airstrip)
Event
- NTSB case
- ATL03LA080
- 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
- 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
Rans S-12
- Aircraft type
- Rans S-12
- 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
- UNREG
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From West Point, TN (private airstrip)To West Point, TN (private airstrip)
- 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, transmission
- 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 › Clearance, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to a witness, the pilot was departing to the north under some high voltage power lines which ran northeast to southwest about 50 feet above the ground. After takeoff both wings on airplane had folded upward. The airplane turned northwest and executed a 180-degree turn. As the airplane approached the strip heading southeasterly, it began to bank to the left to align with the strip's southerly heading. As it banked the left wing contacted the wires and the airplane collided with the ground inverted at about a 45-degree nose down attitude. The airplane was found 100 feet from the point of wire contact, on the northeast side of the departure end of the airstrip. Examination of the unregistered airplane revealed crush damage to the cockpit area, and the left wing was separated about 18 inches outboard of the wing tip.
Probable cause
The pilot's failure to maintain adequate obstacle clearance which resulted in the inflight collision with a utility line. A factor was utility lines.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL03LA080
- Event ID
- 20030425X00570
- Case number
- ATL03LA080
- 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: 4938c8a837d6857829b08eabab38665c0168fc9680cf9bba8ecd3f6f6bcc0621; retrieved 2026-09-20T19:17:50.598Z.