SEA96LA035

NTSB accident investigation · Cessna 172N · Pacific City, OR · December 24, 1995

Accident · No injuriesLimited investigationFinal report
Date
December 24, 1995, 10:15 local (18:15 UTC)
Place
Pacific City, OR
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N738MECessna 172N
Weather
Visual (VMC) · Day
Status
Completed · report September 19, 1996
Report
Approved by Office Director
FAA report
19951224042469A
Case key
42319

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 aborting the landing, which resulted in his failure to clear the perimeter fence. Factors relating to the accident were: the tailwind, and the pilot's failure to land at the proper touchdown point.

Sequence of events

NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.

In flight collision with objectLanding - aborted
Weather condition - tailwindFactor
Proper touchdown point - not attainedPilot in commandFactor
Aborted landing - delayedPilot in commandCause
Flaps - improper use ofPilot in commandFactor
Object - fence
Object - building(nonresidential)
Object - tree(s)

Analysis

The pilot of a Cessna 172N said that he made a normal approach to the 1,875 foot long runway during calm wind. Before landing, the airplane floated. The pilot said that after the airplane touched down and he lowered the nose wheel, the end of the runway was closer than he had expected. He initiated a go-around; however, the airplane's left main landing gear struck a cable, supported by 3 foot high wooden fence posts, which served as a barrier between the end of the runway and a paved road. The airplane then collided with a commercial building and a tree. The left flap was damaged, but the (undamaged) right flap was found in the retracted position. Witnesses around the airport reported the wind direction as southerly immediately following the accident. The Cessna 172N information manual indicated that in the event of a balked landing, 'climb, (and) reduce the flap setting to 20 degrees immediately after full power is applied.'

Factual narrative

History of flight

On December 24, 1995, approximately 1015 Pacific standard time, a Cessna 172N, N738ME, being flown by a private pilot, was substantially damaged during a collision with a barricade cable, commercial building and terrain while executing a go around at the Pacific City State airport, Pacific City, Oregon. The pilot and three passengers were uninjured. Visual meteorological conditions existed at the time of the accident and no flight plan had been filed. The flight, which was personal in nature, was to have been operated under 14CFR91, and originated at Mulino, Oregon, approximately 0930.

The pilot reported making a normal approach to land on runway 32 during which the plane floated. He reported that the winds were calm and that "when (the) mains touched and I lowered the nose wheel I saw the end of (the) runway fence was closer than I had expected" and "I executed a go around" (refer to DIAGRAM I which the pilot provided showing the initiation point of the go around). The runway at the Pacific City airport is 1,875 feet in length and is composed of a 30 foot wide asphalt strip.

On site examination by an FAA inspector revealed that the aircraft's left main landing gear had contacted a metal cable which was routed through vertically mounted wooden fence posts. The posts were situated across the upwind end of the runway, between the runway threshold and a roadway which passed perpendicular to the runway centerline. The posts were approximately three feet above ground level with the metal cable slightly lower. The point of contact between the right main landing gear and the cable was at a location slightly east of the centerline. Wheel marks diverging from the runway centerline were observed in the gravel on the north side of the roadway (refer to photographs 1 and 2).

The aircraft was observed to have come to rest adjacent to a commercial real estate building and a conifer tree. Examination of the aircraft revealed that the left wing had sustained leading edge impact damage and had been deformed aftward. The left flap was compressively buckled and partially extended. The right flap, however, was found to be in the fully retracted position (refer to photographs 3 and 4).

The winds at the Newport airport, 37 nautical miles south (also on the coast), were reported as 14 knots gusting to 20 knots from 070 degrees magnetic at 0952. Several witnesses located at or near the Pacific City airport reported southerly winds immediately after the accident (refer to extraction from the Tillamook County Sheriff's Report number 95-002734 attached),

The Cessna 172N Information Manual states in Section 4 "Normal Procedures" that the procedure in the event of a balked landing is to "climb, (and) reduce the flap setting to 20 degrees immediately after full power is applied" (refer to ATTACHMENTS I & II).

Aircraft

Registration
N738ME
Reported as
Cessna 172N
Category
Airplane
Serial number
17270078
Engine
Lycoming O-320-H2AD, 160 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Operator
Mulino Air
Registered owner
Henkel, Herbert
Airworthiness certificate
Standard, Normal
Departed
4S9 · Mulino, OR
Destination
PFC
Airport
PFC · Pacific City, runway 32, 1,875 × 30 ft, asphalt

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
52
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, Valid Medical--w/ waivers/lim
Seat
Left
Flight hours
169 total · 18 in this make and model · 2 in the last 90 days

Weather

Conditions
Visual (VMC) · Day
Wind
70° at 14 knots, gusting 20
Visibility
15 statute miles
Lowest ceiling
None
Observed at
ONP, 37 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.