# Accident 20140910016829A: Piper J3C-65, Hillsville, VA, September 10, 2014

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: September 10, 2014, 13:12 local time
- Place: Hillsville, VA
- Damage: Substantial damage
- Phase of flight: Cruise/Level Flight
- Operating rules: General operating rules (Part 91)
- Location: 36.6361° N, 80.7200° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=36.6361&lon=-80.7200&mi=10
- Aircraft: N26105, a cancelled registration (https://openairdocs.org/deregistered/N26105-2025-01-25) (OpenAirDocs)
- Registry model: Piper J3C-65 (registry code 7100510, https://openairdocs.org/model/piper-j3c-65) (OpenAirDocs)
- Reported make and model: PIPER J3C-65
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 1
- Pilot certificates: Private pilot
- NTSB investigation: [NTSB ERA14LA433](https://openairdocs.org/ntsb/ERA14LA433) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20140910016829A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

PILOT DEPARTED BECKLEY, WV (BKW)ENROUTE TO NORTH CAROLINA. FLIGHT WAS VFR AND PILOT WAS NAVIGATING BY FOLLOWING SOUTHBOUND INTERSTATE 77. PILOT ENCOUNTERED IMC CONDITIONS (FOG). AIRCRAFT IMPACTED TREES IN BETWEEN NORTHBOUND  AND SOUTHBOUND LANES AT MILE MARKER 5.8.

A/C RECORDS REVIEW DID NOT INDICATE ANY ISSUES TO CAUSE THE AIRCRAFT TO BE UNAIRWORTHY.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB ERA14LA433](https://openairdocs.org/ntsb/ERA14LA433), Sep 10, 2014: Piper J3C 65 (N26105), Carrol County, VA, substantial damage. Probable cause: The pilot’s failure to maintain clearance from trees during an emergency landing after encountering deteriorating weather conditions. Contributing to the accident was the pilot’s poor preflight…

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.