ATL82FA144 · Bell 206B
Bell 206B · Accident: in flight collision with object en route
From VANSANT, VA to VANSANT, VA
Event
- NTSB case
- ATL82FA144
- 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
- 3 · 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
Bell 206B
- Aircraft type
- Bell 206
- Category
- Helicopter
- 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
- N9986K
- Operator
- Robert A. Wood · private individual
- Onboard fatalities
- Unknown
- Route
- From VANSANT, VATo VANSANT, VA
- 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, static
- 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 › Diverted attention
- Pilot in command › Visual lookout, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT WAS FLYING RAILROAD OFFICIALS TO INSPECT RAIL LINES THAT HAD BEEN COVERED BY MUD SLIDES CAUSED BY RECENT HEAVY RAINS. A WITNESS HEARD THE HELICOPTER COMING UP THE VALLEY & THEN HEARD TWO POPPING SOUNDS. HE SAW THE HELICOPTER FALLING TO THE GROUND NEAR SOME POWER LINES STRUNG ACROSS THE VALLEY OVER THE RAILROAD TRACKS. THE POWER LINE ASSEMBLY CONSISTED OF TWO STATIC LINES AT THE TOP & THREE POWER LINES AT THE BOTTOM. THE UPPERMOST STATIC LINE WAS SEPARATED & LYING ON THE LOWER STATIC LINE. THE LINES ARE APPROXIMATELY 300 FT AGL & WERE UNMARKED. THE PLT WAS FAMILIAR WITH THE OPERATING AREA & PURPORTEDLY AWARE OF THE LOCATION OF THE POWER LINES.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL82FA144
- Event ID
- 20020917X02834
- Case number
- ATL82FA144
- 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: ffdf3b028ae8ff0e0c6fdbd683148dfc9e686d8e78980b9b32b6cd9d146f2ced; retrieved 2026-09-21T08:19:20.179Z.