ERA11LA105 · Cessna 172 L
Bladen Aviation Cessna 172 L · Accident: runway excursion during landing
From Curtis L Brown Jr Field (EYF) to Dublin Field (NC82)
Event
- NTSB case
- ERA11LA105
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna 172 L
- Aircraft type
- Cessna 172
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N4383Q
- Operator
- Bladen Aviation
- Onboard fatalities
- Unknown
- Route
- From Curtis L Brown Jr Field (EYF), Elizabethtown, NCTo Dublin Field (NC82), Dublin, NC
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · landing roll
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Runway excursion
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
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.
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA11LA105
- Event ID
- 20110104X01724
- Case number
- ERA11LA105
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 1cdcb18a00855831ef956844ffe1824a5d46f1dd373e11a1a180a5aaf8e8aea7; retrieved 2026-09-15T15:39:37.136Z.