20201003016859A

Accident · Substantial damage

FAA accident report · Beech A23 · Spruce Pines, NC · October 3, 2020

Date
October 3, 2020 · 13:50 local
Place
Spruce Pines, NC
Airport
Avery County
Phase of flight
Landing: Touchdown
Operating rules
General operating rules (Part 91)
Damage
Substantial damage
Aircraft
N8783M
NTSB investigation
NTSBERA21LA012
Reported as
Beech A23
Reported engine
Continental IO-346 series
People aboard
1
Fatal injuries
0
Other injuries
1
Pilot’s certificate
Private pilot
Pilot’s flight hours
500 total10 in this make and model10 in the last 90 days

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry 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.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

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.

As the FAA filed it

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.

NTSB investigation

The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.

Other reports on N8783M · 2

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