# NTSB ERA10CA505: Cessna 172S, N5295Y, Franconia, NH, September 25, 2010 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: September 25, 2010, 10:00 local (14:00 UTC) - Place: Franconia, NH - Coordinates: 44.194721, -71.750556 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=44.1947&lon=-71.7506&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-VFR go-around: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report March 16, 2011 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 77437 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA10CA505 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/77437/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=77437 - Page: https://openairdocs.org/ntsb/ERA10CA505 ## Probable cause The pilot’s delay in initiating a go-around, which resulted in an in-flight collision with a fence. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Action: delayed action](https://openairdocs.org/ntsb-findings/02041025): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cessna 172S, 30 cases](https://openairdocs.org/ntsb-findings/02041025/cases.md?model=2072439), [All aircraft, 894 cases](https://openairdocs.org/ntsb-findings/02041025/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: [Cessna 172S, 18 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=2072439), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach-VFR go-around: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470) (defining event); cases with it: [Cessna 172S, 118 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2072439), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot stated that the purpose of the flight was to fly his relative in the traffic pattern. Shortly after takeoff from runway 36, he remained in the traffic pattern and noticed personnel associated with gliders setting up for launches using runway 18. He was informed that the wind had shifted and opted to land on runway 18. The pilot reported that he made a higher approach than normal due to a glider being positioned at the threshold of runway 18. During landing, the wind shifted and he recognized that the airplane was not slowing. He initiated a go-around and just as the airplane was clearing a fence at the departure end of the runway, it encountered a downdraft and a gust. Despite the pilot applying aft elevator control, the airplane collided with the fence. The pilot continued the go-around procedure and looked outside the airplane noticing damage to a wheel pant; he thought the airplane appeared to be flying normally. Following an uneventful landing on runway 36, the pilot secured the airplane and inspected it for damage. The leading edges of both horizontal stabilizers, the bottom side of the left horizontal stabilizer, and the leading edge of the left elevator exhibited damage. ## Factual narrative The pilot stated that the purpose of the flight was to fly his sister around the traffic pattern. After engine start he taxied to runway 36, and departed. Shortly after takeoff, he remained in the traffic pattern and noticed personnel associated with gliders setting up for launches using runway 18. He was informed that the wind had shifted and was picking up from the south. He returned for landing on runway 18, and reported the approach was a bit high due to a glider that was being positioned at the threshold of runway 18. About that time, the wind shifted from the north as he was landing to the south. He recognized that the airplane was not slowing and initiated a go-around. While about clear of a fence at the departure end of the runway, the flight airplane encountered a downdraft and a gust. He The pilot applied aft elevator control but a portion of the airplane collided with the fence. He continued the go-around and looked outside the airplane noticing damage to a wheel pant; the airplane was flying normally at that time. At that moment, the glider business operator said that the wind was now blowing from the north again and that they were switching back to runway 36. Following an uneventful landing the pilot secured the airplane and inspected it for damage. The leading edges of both horizontal stabilizers, the bottom side of the left horizontal stabilizer, and also the leading edge of the left elevator exhibited damage. ## Aircraft - Registration: [N5295Y](https://openairdocs.org/deregistered/N5295Y-2018-05-30), registration cancelled 2018-05-30, S/N 172S9236, built 2002 (OpenAirDocs) - Reported make and model: CESSNA 172S - Registry model: [Cessna 172S](https://openairdocs.org/model/cessna-172s) (registry code 2072439) (OpenAirDocs) - Registry engine: [Lycoming IO-360-L2A](https://openairdocs.org/engine/lycoming-io-360-l2a) (registry code 41597, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 172S9236 - Airframe hours: 3932 - Engines: LYCOMING IO-360-L2A 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Air America LLC - Registered owner: Mike Bravo LLC - Airworthiness certificate: Standard, Utility; Standard, Normal - Last inspection: 100 hour, August 10, 2010 - Departed: 1B5, Franconia, NH - Destination: 1B5, Franconia, NH - Airport: 1B5, Franconia Airport, runway 18, 2,305 × 150 ft, grass/turf ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 64; injuries: none; flight instructor, airline transport, commercial; airplane ratings: multi-engine land, single-engine sea, single-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review April 22, 2010; seat: right; flight hours: 30,610 total, 10,000 in this make and model, 30,500 as pilot in command, 150 in the last 90 days, 25 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 300° at 6 knots - Visibility: 9 statute miles - Lowest ceiling: none - Temperature: 72 °F, dew point 61 °F - Altimeter: 29.72 inHg - Observed at: HIE, 14 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 20100925046009A](https://openairdocs.org/incident/20100925046009A), Sep 25, 2010: Cessna 172S, Franconia, NH, Substantial damage. Aircraft struck wood fence at end of grass strip while attempting to land. Aircraft continued go around and landed safely. Substantial damage to underside of… ## Other investigations on N5295Y (1) 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. - [NTSB ERA16LA008](https://openairdocs.org/ntsb/ERA16LA008), Oct 10, 2015: Cessna 172S (N5295Y), Seville, FL, substantial damage, 1 fatal. Probable cause: The airplane’s encounter with a downdraft, and the pilot's decision to maneuver the airplane at a low altitude and airspeed, which provided insufficient time and altitude to recover before impacting… ## Docket (2 files) The files NTSB released with the investigation on November 7, 2010, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=77437. 778 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 714 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40337943&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Weather Reports and Records (item 2, .PDF, 64 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40337944&FileExtension=.PDF&FileName=Weather%20Reports%20and%20Records-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.