# Accident 19890811028779A: Beech A36, Chapel Hill, NC, August 11, 1989

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: August 11, 1989, 21:18 local time
- Place: Chapel Hill, NC
- Airport: Private
- Damage: Destroyed
- Phase of flight: Final Approach
- Operating rules: General operating rules (Part 91)
- Location: 35.9283° N, 79.0401° W: Placed by OpenAirDocs: center of Chapel Hill, NC, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=35.9283&lon=-79.0401&mi=10
- Aircraft: N25805, a cancelled registration (https://openairdocs.org/deregistered/N25805-2014-10-27) (OpenAirDocs)
- Registry model: Beech A36 (registry code 1151604, https://openairdocs.org/model/beech-a36) (OpenAirDocs)
- Registry engine: Amateur-built UNKNOWN ENG (registry code 99999, https://openairdocs.org/engine/amateur-built-unknown-eng) (OpenAirDocs)
- Reported make and model: BEECH A36
- Reported engine: CONT IO520BB
- People aboard: 1
- Fatal injuries: 1
- Pilot flight hours: 1,200 total
- NTSB investigation: [NTSB ATL89FA196](https://openairdocs.org/ntsb/ATL89FA196) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19890811028779A

## Narrative

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

STRUCK TREE NEAR AIRPORT. UNABLE TURN OFF AUTO PILOT. TRIM FULL DOWN AT IMPACT.

## 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 ATL89FA196](https://openairdocs.org/ntsb/ATL89FA196), Aug 12, 1989: Beech A-36 (N25805), Chapel Hill, NC, destroyed, 1 fatal. Probable cause: THE PILOT'S FAILURE TO MAINTAIN CONTROL OF THE AIRPLANE WHILE MANEUVERING FOR A LANDING. CONTRIBUTING FACTORS WERE: THE PILOT'S FAILURE TO FOLLOW THE EMERGENCY PROCEDURES FOR AN AUTOPILOT…

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.