WPR10LA427

NTSB accident investigation · Piper PA-28-180 · Sequim, WA · August 24, 2010

Accident · Minor injuriesLimited investigationFinal report
Date
August 24, 2010, 16:10 local (23:10 UTC)
Place
Sequim, WA
Injuries
1 minor, 2 uninjured
Phase of flight
Landing
Aircraft
N5101LPiper PA-28-180N50464Cessna 150J
Defining events
Landing-flare/touchdown: Landing area undershootStanding-engine(s) operating: Ground collision
Weather
Visual (VMC) · Day
Status
Completed · report December 27, 2011
Report
Approved by Office Director
NTSB office
Western Pacific Region
Parties
Federal Aviation Administration
Case key
77072

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 failure to maintain the proper approach path and his delayed corrective actions, which resulted in an undershoot. Contributing to the accident was the pilot's distraction from other aircraft in the area.

Findings · 5

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.

N5101L · Piper PA-28-180

Performance/control parameters: descent/approach/glide pathAircraft › Aircraft oper/perf/capability · Incorrect use/operationPiper PA-28-180: 7 casesAll aircraft: 809 casesProbable cause
Performance/control parameters: altitudeAircraft › Aircraft oper/perf/capability · Not attained/maintainedPiper PA-28-180: 12 casesAll aircraft: 1,310 casesProbable cause
Action: delayed actionPersonnel issues › Action/decision · PilotPiper PA-28-180: 10 casesAll aircraft: 894 casesProbable cause
Attention/monitoring: attentionPersonnel issues › Psychological · PilotPiper PA-28-180: 1 caseAll aircraft: 226 casesProbable cause

N50464 · Cessna 150J

Personnel issuesPersonnel issues › Action/decision · Pilot of other aircraftCessna 150J: 1 caseAll aircraft: 56 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.

N50464 · Cessna 150J

Ground collisionStanding-engine(s) operatingCessna 150J: 2 casesAll aircraft: 618 casesDefining event

Analysis

As the airplane approached the uncontrolled airport for landing, the pilot became distracted by two other airplanes in the traffic pattern and by a third airplane that entered the pattern in front of him. This resulted in the pilot extending the downwind leg of his traffic pattern and maintaining traffic pattern altitude until the final approach. A fourth airplane was in the run-up area preparing to depart, which the landing pilot also noted. As the pilot turned onto the final approach, he descended with full flaps. Just before the airplane touched down, the pilot observed that the airplane was low and slow, and he increased engine power. The airplane subsequently collided with upsloping terrain short of the runway, and then veered into the airplane that was standing in the run-up area.

Factual narrative

HISTORY OF FLIGHT On August 24, 2010, about 1610 Pacific daylight time, a Piper PA-28-180, N5101L, collided with a Cessna 150J, N50464, at the Diamond Point Airstrip, Sequim, Washington. The Piper was owned and operated by its certificated private pilot. The Cessna was owned by its student pilot, and it was operated by the certificated commercial pilot who was providing flight instruction to the student. The accident occurred when the pilot flying the Piper airplane, which was attempting to land, impacted terrain short of runway 29’s landing threshold. Thereafter, the Piper airplane veered into the Cessna that was holding short of the runway and was waiting for takeoff. Both airplanes were substantially damaged. The Piper pilot sustained minor injuries. His personal flight originated from Olympia, Washington, about 1530. Neither of the pilots in the Cessna were injured. Their flight was originating when the accident occurred. Visual meteorological conditions prevailed, and no flight plans were filed by any of the pilots. The National Transportation Safety Board investigator interviewed the Piper and Cessna pilots. The Piper pilot stated, in pertinent part, that he had not previously landed at the (uncontrolled) Diamond Point Airstrip. When he approached the airstrip, there were two other airplanes in the traffic pattern, and a Cessna reported on the radio that he was taxiing for takeoff. Then, when a third airplane entered the traffic pattern in front of his airplane, he altered his approach path and did not commence a descent. Rather, he maintained his altitude and extended his pattern until he had adequate clearance from the airplane ahead, which was landing. Thereafter, the Piper pilot reduced engine power and added full flaps to descend to the proper approach path. The Piper pilot verbally reported to the Safety Board investigator that he did not encounter any downdrafts during his approach. On final approach, he initially reduced the engine’s speed to 1,700 revolutions per minute (rpm), and the airplane descended. The pilot reported that on short final approach, he likely was low and slow, so he added full engine power to arrest the descent. The pilot opined that the engine rpm did not increase before the airplane collided with upsloping terrain, short of the runway’s pavement. According to the certified flight instructor (CFI) who was providing dual instruction to his student in the Cessna, the CFI observed the Piper airplane when it was on a long final approach to the airstrip. The Cessna was located in the taxiway’s run-up apron, adjacent to but clear of the runway. The CFI noted that the Piper was very low on short final approach, and it was heading 10 to 15 degrees left of the runway’s centerline extension. The CFI commented to his student that the Piper was going to crash, and within seconds it did. The Piper impacted the ground short of the runway and then veered into the Cessna. Subsequently, when the CFI spoke with the Piper pilot,the pilot stated that he had been distracted by the other airplanes in the area. He had increased engine power because he was low and slow, and he had pulled back on the yoke. However, according to the Piper pilot the airplane’s rate of descent was not adequately reduced. Airport Information Runway 29 has a marked landing threshold, which is displaced about 200 feet from the beginning of the runway’s pavement. The distance from the runway’s threshold to the end of runway 29 is about 2,135 feet. The runway is about 24 feet wide. Tests and Research A Federal Aviation Administration inspector examined the airplanes and accident site and documented the scene along with other personnel. Ground scar evidence was observed that indicated the Piper touched down on an upsloping dirt embankment, about 17 feet before reaching the runway’s asphalt pavement. This touchdown location was about 217 feet short of the runway's displaced threshold. A ground scar was noted in the terrain that was consistent with the Piper’s right main landing gear wheel. The scar was located about 9 feet left of the runway’s centerline. Tire rub marks on the tarmac were noted. The marks were consistent with the sideways skid-like movement of the Cessna's nose wheel. The marks were located in the run-up area, and indicated that the Cessna was clear of the active runway when its right wing was impacted.

Aircraft · 2

Registration
N5101L
Reported as
Piper PA-28-180
Category
Airplane
Serial number
28-4385
Airframe hours
2,825
Engine
Lycoming O&VO-360 SER, 180 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Airworthiness certificate
Standard, Utility; Standard, Normal
Last inspection
Annual · October 22, 2009 · 8 hours before
Departed
OLM · Olympia, WA
Destination
2WA1 · Sequim, WA
Airport
2WA1 · Diamond Point Airstrip, runway 29, 2,335 × 24 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.

Registration
N50464
Reported as
Cessna 150J
Category
Airplane
Serial number
15069321
Airframe hours
5,475
Engine
Cont Motor 0-200 SERIES, 100 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Airworthiness certificate
Standard, Utility; Standard, Normal
Last inspection
Annual · February 2, 2010 · 5 hours before
Departed
2WA1 · Sequim, WA
Destination
2WA1 · Sequim, WA
Airport
2WA1 · Diamond Point Airstrip, runway 29, 2,335 × 24 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 · 3

As NTSB recorded them. NTSB leaves out names.

Role
Pilot, aircraft N5101L
Age
61
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, With waivers/limitations
Last flight review
October 13, 2009
Seat
Left
Flight hours
549 total · 133 in this make and model · 549 as pilot in command · 4 in the last 90 days · 2 in the last 30 days · 1 in the last 24 hours
Role
Flight instructor, aircraft N50464
Age
60
Injuries
None
Certificates
Flight instructor, Commercial
Airplane ratings
Single-engine sea, Single-engine land
Instrument ratings
Airplane
Medical
Class 2, With waivers/limitations
Last flight review
March 17, 2009
Seat
Right
Flight hours
4,159 total · 43 in this make and model · 4,107 as pilot in command · 55 in the last 90 days · 17 in the last 30 days · 0 in the last 24 hours
Role
Student pilot, aircraft N50464
Age
64
Injuries
None
Certificate
Student
Medical
Class 3, With waivers/limitations
Seat
Left

Weather

Conditions
Visual (VMC) · Day
Wind
290° at 10 knots
Visibility
25 statute miles
Lowest ceiling
None
Temperature
75 °F
Altimeter
30.05 inHg

Docket · 18

The files NTSB released with the investigation on November 22, 2011, on NTSB’s docket system: statements, records, photos and specialists’ reports. 6.8 MB in all.

FAA reports on this event · 2

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