ERA16CA308 · Beech C23
Beech C23 · Accident: runway excursion during landing
From Meriden Markham Municipal Airport (MMK) to Simsbury Airport (4B9)
Event
- NTSB case
- ERA16CA308
- 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
Beech C23
- Aircraft type
- Beechcraft 23
- 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
- N9352S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Meriden Markham Municipal Airport (MMK), Meriden, CTTo Simsbury Airport (4B9), SIMSBURY, CT
- Aircraft age
- About 41 years (built 1975)
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The student pilot reported that he was preparing for his private pilot check ride, and after about 90 minutes of flying, he approached the airport and entered the traffic pattern for runway 21, a 2,205-ft-long runway. The student pilot added that, while established on "short final," he chose to perform a go-around because he was not "comfortable" with the approach. On the second landing attempt, the airplane floated past the intended touchdown point before landing on the runway, and the student pilot was unable to stop the airplane before it went off the departure end. Subsequently, the airplane struck a perimeter fence and an embankment, which resulted in the nose landing gear collapsing and substantial damage to the fuselage and left wing. The student pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. The winds reported at an airport 4 miles east of the accident location were from 320° at 7 knots.
Probable cause
The student pilot’s failure to attain the proper touchdown point, which resulted in a runway overrun.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA16CA308
- Event ID
- 20160901X83843
- Case number
- ERA16CA308
- 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: 83da496a0896e6f66808b649fb9018ae2bb5953de0093ed9807fafe68c8bb30d; retrieved 2026-09-16T04:13:10.424Z.