# Accident 19820910045139A: Gulstm 112, Fayetteville, WV, September 10, 1982

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: September 10, 1982, 20:56 local time
- Place: Fayetteville, WV
- Airport: Fayette
- Damage: Substantial damage
- Phase of flight: Final Approach
- Operating rules: General operating rules (Part 91)
- Location: 38.0268° N, 81.1198° W: Placed by OpenAirDocs at FAYETTE (WV59), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=38.0268&lon=-81.1198&mi=10
- Aircraft: N1072J, registered now (https://openairdocs.org/aircraft/N1072J) (OpenAirDocs)
- Registry model: Aero Commander 112 (registry code 0144701, https://openairdocs.org/model/aero-commander-112) (OpenAirDocs)
- Registry engine: Continental IO-360 series (registry code 17025, https://openairdocs.org/engine/continental-io-360-series) (OpenAirDocs)
- Reported make and model: GULSTM 112
- Reported engine: LYC IO360C1D6
- People aboard: 3
- Fatal injuries: 0
- Pilot flight hours: 286 total, 23 in this make and model, 14 in the last 90 days
- NTSB investigation: [NTSB ATL82DA266](https://openairdocs.org/ntsb/ATL82DA266) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19820910045139A

## Narrative

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

TOO LOW ON FINAL. AIRCRAFT STRUCK A TREE. AIRPORT OPERATOR FAILED TO ADVISE PILOT OF HAZARD AND DISPLACED THRESHOLD

## 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 ATL82DA266](https://openairdocs.org/ntsb/ATL82DA266), Sep 11, 1982: Aero Commander 112 (N1072J), Fayetteville, WV, substantial damage

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.