ERA10CA505

NTSB accident investigation · Cessna 172S · Franconia, NH · September 25, 2010

Accident · No injuriesData collectionFinal report
Date
September 25, 2010, 10:00 local (14:00 UTC)
Place
Franconia, NH
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N5295YCessna 172S
Defining event
Approach-VFR go-around: Collision with terr/obj (non-CFIT)
Weather
Visual (VMC) · Day
Status
Completed · report March 16, 2011
Report
Approved by Office Director
NTSB office
Eastern Region Aviation
Parties
FAA/FSDO
FAA report
20100925046009A
Case key
77437

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

The pilot’s delay in initiating a go-around, which resulted in an in-flight collision with a fence.

Findings · 2

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Action: delayed actionPersonnel issues › Action/decision · PilotCessna 172S: 30 casesAll aircraft: 894 casesProbable cause
Performance/control parameters: descent/approach/glide pathAircraft › Aircraft oper/perf/capability · Not attained/maintainedCessna 172S: 18 casesAll aircraft: 809 casesProbable cause

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

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
Reported as
Cessna 172S
Category
Airplane
Serial number
172S9236
Airframe hours
3,932
Engine
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

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
64
Injuries
None
Certificates
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

Docket · 2

The files NTSB released with the investigation on November 7, 2010, on NTSB’s docket system: statements, records, photos and specialists’ reports. 778 KB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.

Other investigations on N5295Y · 1

Matched to the same aircraft by N-number and date.