ERA12CA427 · Cessna 182A
Cessna 182A · Accident: runway excursion during landing
From Sussex Airport (FWN) to Sussex Airport (FWN)
Event
- NTSB case
- ERA12CA427
- 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 182A
- Aircraft type
- Cessna 182
- 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
- N5143D
- Operator
- Anselm Winston Dewar
- Onboard fatalities
- Unknown
- Route
- From Sussex Airport (FWN), Sussex, NJTo Sussex Airport (FWN), Sussex, NJ
- 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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that, during the final leg of the approach, the airplane was above the intended approach path and speed. Over the threshold of the runway, the airplane encountered a gust of wind. The pilot announced on the common traffic advisory frequency his intention to perform a go-around maneuver. He was unable to perform the maneuver prior to the hard landing; he then proceeded to overrun the runway and the airplane nosed over, which resulted in substantial damage to the left wing. The pilot reported that there were no mechanical malfunctions or failures with the airplane that would have precluded normal operation. The recorded wind at the airport about the time of the accident was variable at 4 knots and for the hour before and an hour after the accident the wind was recorded as calm.
Probable cause
The pilot’s delayed decision to abort the landing and perform a go-around, which resulted in a runway overrun.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA12CA427
- Event ID
- 20120703X82414
- Case number
- ERA12CA427
- 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, coordinates. 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: d87c37059484210aeed3426cf50f540a8131fbaebb234ca038aadf79f9786734; retrieved 2026-09-15T18:43:48.674Z.