ATL06LA003 · Grumman F6F
Grumman F6F · Accident: in flight collision with object en route
From Gatlinburg-Pigeon Forge Airport (GKT) to Bill & Hillary Clinton National Airport/Adams Field (LIT)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ATL06LA003
- 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
- Instrument Meteorological Cond
Grumman F6F
- Aircraft type
- Grumman F6
- 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
- N4994V
- Operator
- Arthur St Clair Vance
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From Gatlinburg-Pigeon Forge Airport (GKT), Sevierville, TNTo Bill & Hillary Clinton National Airport/Adams Field (LIT), Little Rock, AR
- 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
- Substantial
Cause areas
- Pilot in command › Clearance, not maintained
- Pilot in command › Visual lookout, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot told people at the departure Airport prior to takeoff that he was going to follow I-40 to his destination. The weather at the accident site was 500 foot overcast, 5 miles visibility and mist. Several motorists observed the airplane flying at an altitude of about 100 feet west bound along I-40 prior to colliding with power lines. There were no mechanical problems reported by the pilot or discovered during the post-accident examination of the airplane.
Probable cause
The pilot's inadequate preflight planning and inadequate evaluation of the weather, inadequate visual lookout, and his failure to maintain clearance, resulted in the in-flight collision with power lines.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL06LA003
- Event ID
- 20051012X01621
- Case number
- ATL06LA003
- 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, coordinates. 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: 5fd968729505cfdfc79a49e4d733e1c40c5ccf2df41ee89d7296ba71539106d0; retrieved 2026-09-20T17:50:08.075Z.