Probable cause
The pilot’s improper touchdown speed which resulted in a runway overrun. Contributing to the accident was the undetermined malfunction of the airspeed indicator.
NTSB analysis
The pilot was repositioning the airplane to an unfamiliar airport equipped with a 2,186-foot-long turf runway. After arrival, he circled the airport several times, and initiated an approach to the runway. On final approach, the pilot performed a go-around due to glare from the sun, and elected to land on the opposite runway. While on the base-to-final turn, he noticed the airspeed indicator was reading zero, but reported feeling comfortable and elected to continue the approach. After touchdown on the wet turf runway about 1/3 down its length, he noticed the airplane was faster than he expected. The pilot applied the brakes, but was unable to stop the airplane. The airplane overran the runway, crossed a road, and nosed over in a field, where it came to rest inverted. Testing of the pitot-static system revealed no evidence of preimpact failure or malfunction. No determination could be made as to the reason for the airspeed indicator malfunction, as reported by the pilot.
Text from the NTSB. Open the NTSB docket for ERA11LA105 for the full record.
Event
- Date
- Dec 31, 2010
- Type
- Accident
- Place
- Dublin, North Carolina
- Nearest airport
- Dublin Field (NC82)
- Highest injury
- None
- Weather
- Visual (VMC)
- Light
- Day
Cessna 172
- N-number
- N4383Q
- Category
- Airplane
- Damage
- Substantial
- Operating rule
- Part 91 (general aviation)
- Purpose of flight
- Personal
From the NTSB aviation accident database: N-registered aircraft, events since 2008, data through Oct 28, 2026. The file is published monthly, so the latest weeks are incomplete and recent records can change. The official source is the NTSB aviation investigation search. CheckAero is independent and not affiliated with the NTSB.