# Accident 20201003016859A: Beech A23, Spruce Pines, NC, October 3, 2020

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: October 3, 2020, 13:50 local time
- Place: Spruce Pines, NC
- Airport: Avery County
- Damage: Substantial damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 35.9502° N, 81.9982° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=35.9502&lon=-81.9982&mi=10
- Aircraft: N8783M, a cancelled registration (https://openairdocs.org/deregistered/N8783M-2021-11-13) (OpenAirDocs)
- Registry model: Beech A23 (registry code 1151204, https://openairdocs.org/model/beech-a23) (OpenAirDocs)
- Registry engine: Continental IO-346 series (registry code 17033, https://openairdocs.org/engine/continental-io-346-series) (OpenAirDocs)
- Reported make and model: BEECH A23
- Reported engine: CONT MOTOR IO-346 SERIES
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 1
- Pilot certificates: Private pilot
- Pilot flight hours: 500 total, 10 in this make and model, 10 in the last 90 days
- NTSB investigation: [NTSB ERA21LA012](https://openairdocs.org/ntsb/ERA21LA012) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20201003016859A

## Narrative

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

THE PILOT STATED THE FLIGHT WAS NORMAL FROM K62 TO 7A8.  UPON ARRIVING AT 7A8 AT AN ALTITUDE OF 7500 FT., HE PERFORMED A CIRCLING DESCENT TO ENTER THE TRAFFIC PATTERN FOR A LANDING ON RUNWAY 35.

ON HIS APPROACH TO THE RUNWAY, HE SELECTED ONE NOTCH OF FLAPS. AS THE AIRCRAFT CONTINUED OVER THE RUNWAY, IT WAS NOT SLOWING DOWN OR DESCENDING SO HE ADDED MORE FLAPS. THE AIRCRAFT CONTINUED TO "FLOAT" AND HE CONTINUED ADDING FLAPS UNTIL HE HAD FULL FLAPS. THE AIRCRAFT TOUCHED DOWN ON THE RUNWAY WITH APPROXIMATELY 200 FEET REMAINING.  ON ROLLOUT, THE AIRCRAFT EXITED THE END OF THE RUNWAY, PROCEEDED THROUGH THE AIRPORT PERIMETER FENCE AND CAME TO REST ON A ROAD AFTER TRAVELING DOWN A SMALL EMBANKMENT.

THE PILOT STATED HE BELIEVES HE HAD A TAILWIND FORCING HIM DOWN THE RUNWAY AS HE HAD TO USE FULL FLAPS WHEN HE NORMALLY LANDS WITH ?ONE NOTCH? OF FLAPS SELECTED.

THE PILOT ADMITTED HE SHOULD HAVE ABORTED THE LANDING AND EXECUTED A GO-AROUND.

THE PILOT DID NOT CHECK THE WEATHER OR THE WINDSOCK PRIOR TO LANDING TO DETERMINE THE WINDS AND THE FAVORABLE RUNWAY. PRIOR TO HIS FLIGHT THE PILOT CALLED THE AIRPORT TO GATHER INFORMATION ON WHICH RUNWAY WAS BEST TO LAND SINCE HE HAD NOT FLOWN INTO THE AIRPORT BEFORE.  HE WAS TOLD TO LAND ON RUNWAY 35 BECAUSE IT WAS SLOPED UPHILL.

## 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 ERA21LA012](https://openairdocs.org/ntsb/ERA21LA012), Oct 3, 2020: Beech 23 (N8783M), Spruce Pines, NC, substantial damage. Probable cause: The pilot's failure to familiarize himself with the wind conditions at the destination airport and his failure to attain the proper touchdown point during landing, which resulted in a long, tailwind…

## Other reports on N8783M (2)

Matched to the same aircraft by N-number and date.

- [Incident 19980419011279I](https://openairdocs.org/incident/19980419011279I), Apr 19, 1998: Beech A23 (N8783M), Bay St Louis, MS, Minor damage. Narrative: during cruise the pilot stated engine began to run rough and while over the airport a cylinder failed knocking hole in side of cowling. Pilot…
- [Incident 19951013036909I](https://openairdocs.org/incident/19951013036909I), Oct 13, 1995: Beech 35A33 (N8783M), Dayton, TN. Narrative: pilot filed a VFR flight plan and received a weather briefing from lansing Michigan flight service on 10-13-95. The flight was uneventful until…

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.