# NTSB ERA16CA308: Beech C23, N9352S, Simsbury, CT, August 29, 2016 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: August 29, 2016, 18:00 local (22:00 UTC) - Place: Simsbury, CT - Coordinates: 41.913055, -72.778053 - Nearby events: https://openairdocs.org/map.md?lat=41.9131&lon=-72.7781&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report August 22, 2017 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA FSDO - NTSB case key (mKey): 93932 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA16CA308 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/93932/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=93932 - Page: https://openairdocs.org/ntsb/ERA16CA308 ## Probable cause The student pilot’s failure to attain the proper touchdown point, which resulted in a runway overrun. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Student/instructed pilot (probable cause); cases with it: [Beech C23, 8 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=1151242), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Student/instructed pilot (probable cause); cases with it: [Beech C23, 23 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=1151242), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Performance/control parameters: descent/approach/glide path](https://openairdocs.org/ntsb-findings/01062040): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Beech C23, 2 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=1151242), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md) - [Aircraft capability: landing distance](https://openairdocs.org/ntsb-findings/01061030): Aircraft › Aircraft oper/perf/capability · Capability exceeded (probable cause); cases with it: [Beech C23, 3 cases](https://openairdocs.org/ntsb-findings/01061030/cases.md?model=1151242), [All aircraft, 68 cases](https://openairdocs.org/ntsb-findings/01061030/cases.md) - [Object/animal/substance: fence/fence post](https://openairdocs.org/ntsb-findings/03022047): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Beech C23, 4 cases](https://openairdocs.org/ntsb-findings/03022047/cases.md?model=1151242), [All aircraft, 313 cases](https://openairdocs.org/ntsb-findings/03022047/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing: Landing area overshoot](https://openairdocs.org/ntsb-events/380); cases with it: [Beech C23, 2 cases](https://openairdocs.org/ntsb-events/380/sequence.md?model=1151242), [All aircraft, 400 cases](https://openairdocs.org/ntsb-events/380/sequence.md) - [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300) (defining event); cases with it: [Beech C23, 9 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=1151242), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) - [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Beech C23, 25 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=1151242), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis 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. ## Factual 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. While established on "short final," he elected 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 degrees true at 7 knots. ## Aircraft - Registration: [N9352S](https://openairdocs.org/deregistered/N9352S-2024-06-12), registration cancelled 2024-06-12, S/N M-1653, built 1975 (OpenAirDocs) - Reported make and model: BEECH C23 (NO SERIES) - Registry model: [Beech C23](https://openairdocs.org/model/beech-c23) (registry code 1151242) (OpenAirDocs) - Registry engine: [Lycoming O&VO-360 series](https://openairdocs.org/engine/lycoming-o-vo-360-series) (registry code 41514, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: M-1653 - Year built: 1975 - Airframe hours: 2165 - Engines: LYCOMING O-360-A4J 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, March 10, 2016 - Departed: MMK, MERIDEN, CT - Destination: 4B9, SIMSBURY, CT - Airport: 4B9, Simsbury, runway 21, 2,205 × 50 ft, asphalt - Equipment: Handheld GPS ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 57; injuries: none; student; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; seat: left; restraint: 3-point; flight hours: 78 total ## Weather - Conditions: Visual (VMC), Day - Wind: 320° at 7 knots - Visibility: 10 statute miles - Lowest ceiling: 25,000 ft broken - Temperature: 84 °F, dew point 61 °F - Observed at: BDL, 4 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20160829015459A](https://openairdocs.org/incident/20160829015459A), Aug 29, 2016: Beech C23, Simsbury, CT, Substantial damage. On 8/29/2016 at approximately 1700 local time [privacy data omitted] student pilot number [privacy data omitted] departed 7B6 to practice maneuvers in [privacy… ## Docket (3 files) The files NTSB released with the investigation on August 7, 2017, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=93932. 3.1 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 995 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40454930&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Pilot Logbook Excerpt (item 2, .PDF, 623 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40454931&FileExtension=.PDF&FileName=Pilot%20Logbook%20Excerpt-Master.PDF - Accident Site and Damage Photographs (Courtesy of FAA) (item 3, .PDF, 4 photos, 1.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40454932&FileExtension=.PDF&FileName=Accident%20Site%20and%20Damage%20Photographs%20(Courtesy%20of%20FAA)-Master.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.