N260ND accident

NTSB ERA10CA496 · 2010-09-22 · Marlboro, MA · near 9B1

Docket — crew, injuries and powerplant

Summary

According to the pilot, he verified the wind direction and speed by observing the windsock before attempting to land. During the first attempt, he executed a go-around due to excessive altitude. During a second attempt, the pilot initiated a forward slip and landed the airplane two-thirds down the runway. After touchdown, he applied brake pressure, but the airplane continued off the end of the runway and impacted a fence, substantially damaging the fuselage and wings. A postaccident examination of the airframe and engine revealed no mechanical malfunctions or failures that would have precluded normal operation. The pilot reported that it was the first time he had landed at the airport and that it was the shortest runway he had ever attempted to land on. The pilot stated that the accident could have been prevented if he had performed a go-around.

Full narrative

According to the pilot, he was returning to the rented airplane’s home base when he overflew the accident airport and decided to land. The pilot checked the winds by observing the wind sock before attempting to land on runway 32, a 1,659-foot runway. During the first attempt, the pilot executed a go around due to excessive altitude. During a second attempt, the pilot initiated a forward slip and landed the airplane two-thirds down the runway. The pilot applied brake pressure, but the airplane continued off the end of the runway and impacted a fence, which substantially damaged the fuselage and wings. During a subsequent examination of the wreckage, a Federal Aviation Administration inspector identified no preexisting anomalies with the airplane. The pilot reported that it was the first time he had landed at the airport, and it was the shortest runway he had ever attempted to land on. He also noted that his total flight experience was approximately 90 hours, of which, about 6 hours were in the same make and model as the accident airplane. When asked how he could have prevented the accident, the pilot stated that he should have performed a go-around if he was unsure that he could land and stop on the remaining runway. The operator who rented the airplane to the pilot restricted landings to runways which were at least 3,000 feet long. Winds, recorded at an airport 12 miles to the northeast at the time of the accident, were calm.

Probable cause

The pilot’s improper touchdown point and failure to perform a go-around in a timely manner, which resulted in a runway excursion. The National Transportation Safety Board determined the probable cause of this accident.

Circumstances

Event type
Accident
Highest injury
None
Weather conditions
Visual Meteorological Cond
Light condition
Day
Sky condition
NONE
Ceiling (ft)
0
Visibility (sm)
10
Wind direction
0
Temperature (F)
73
Nearest airport
Marlboro Airport
Distance from field
0.0
Airport elevation
285

Aircraft

RegistrationMakeModelDamageFAR part
N260ND — — SUBS 091

Sequence of events

#OccurrencePhase
1 Landing-landing roll Collision with terr/obj (non-CFIT) Cruise
2 Landing Landing area overshoot defining Cruise
3 Landing Runway excursion Cruise

Findings

Finding
Personnel issues-Action/decision-Info processing/decision-Decision making/judgment-Pilot cause
Personnel issues-Action/decision-Action-Incorrect action selection-Pilot cause