# NTSB WPR10LA427: Piper PA-28-180, N5101L, Sequim, WA, August 24, 2010

- Type: NTSB accident investigation
- Classification: Accident · Minor injuries · Limited investigation · Final report
- Date: August 24, 2010, 16:10 local (23:10 UTC)
- Place: Sequim, WA
- Coordinates: 48.090278, -122.924446 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=48.0903&lon=-122.9244&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining events: [Landing-flare/touchdown: Landing area undershoot](https://openairdocs.org/ntsb-events/370); [Standing-engine(s) operating: Ground collision](https://openairdocs.org/ntsb-events/200)
- Highest injury: Minor injuries
- Injuries: 1 minor, 2 uninjured
- Status: Completed, report December 27, 2011
- Report: Approved by Office Director
- NTSB office: Western Pacific Region
- Parties: Federal Aviation Administration
- NTSB case key (mKey): 77072
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR10LA427
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/77072/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=77072
- Page: https://openairdocs.org/ntsb/WPR10LA427

## Probable cause (aircraft 1)

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

NTSB's coded findings; those marked are part of the probable cause.

- [Performance/control parameters: descent/approach/glide path](https://openairdocs.org/ntsb-findings/01062040): Aircraft › Aircraft oper/perf/capability · Incorrect use/operation (probable cause), aircraft 1; cases with it: [Piper PA-28-180, 7 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=7102808), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md)
- [Performance/control parameters: altitude](https://openairdocs.org/ntsb-findings/01062012): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause), aircraft 1; cases with it: [Piper PA-28-180, 12 cases](https://openairdocs.org/ntsb-findings/01062012/cases.md?model=7102808), [All aircraft, 1,310 cases](https://openairdocs.org/ntsb-findings/01062012/cases.md)
- [Action: delayed action](https://openairdocs.org/ntsb-findings/02041025): Personnel issues › Action/decision · Pilot (probable cause), aircraft 1; cases with it: [Piper PA-28-180, 10 cases](https://openairdocs.org/ntsb-findings/02041025/cases.md?model=7102808), [All aircraft, 894 cases](https://openairdocs.org/ntsb-findings/02041025/cases.md)
- [Attention/monitoring: attention](https://openairdocs.org/ntsb-findings/02021510): Personnel issues › Psychological · Pilot (probable cause), aircraft 1; cases with it: [Piper PA-28-180, 1 case](https://openairdocs.org/ntsb-findings/02021510/cases.md?model=7102808), [All aircraft, 226 cases](https://openairdocs.org/ntsb-findings/02021510/cases.md)
- [Personnel issues](https://openairdocs.org/ntsb-findings/02040000): Personnel issues › Action/decision · Pilot of other aircraft (probable cause), aircraft 2; cases with it: [Cessna 150J, 1 case](https://openairdocs.org/ntsb-findings/02040000/cases.md?model=2071820), [All aircraft, 56 cases](https://openairdocs.org/ntsb-findings/02040000/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Approach-VFR pattern final: Altitude deviation](https://openairdocs.org/ntsb-events/282), aircraft 1; cases with it: [Piper PA-28-180, 2 cases](https://openairdocs.org/ntsb-events/282/sequence.md?model=7102808), [All aircraft, 104 cases](https://openairdocs.org/ntsb-events/282/sequence.md)
- [Approach-VFR pattern final: Attempted remediation/recovery](https://openairdocs.org/ntsb-events/060), aircraft 1; cases with it: [Piper PA-28-180, 12 cases](https://openairdocs.org/ntsb-events/060/sequence.md?model=7102808), [All aircraft, 1,422 cases](https://openairdocs.org/ntsb-events/060/sequence.md)
- [Landing-flare/touchdown: Landing area undershoot](https://openairdocs.org/ntsb-events/370) (defining event), aircraft 1; cases with it: [Piper PA-28-180, 3 cases](https://openairdocs.org/ntsb-events/370/sequence.md?model=7102808), [All aircraft, 201 cases](https://openairdocs.org/ntsb-events/370/sequence.md)
- [Standing-engine(s) operating: Ground collision](https://openairdocs.org/ntsb-events/200) (defining event), aircraft 2; cases with it: [Cessna 150J, 2 cases](https://openairdocs.org/ntsb-events/200/sequence.md?model=2071820), [All aircraft, 618 cases](https://openairdocs.org/ntsb-events/200/sequence.md)

## Analysis (aircraft 1)

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 (aircraft 1)

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 1

- Registration: [N5101L](https://openairdocs.org/deregistered/N5101L-2013-08-20), registration cancelled 2013-08-20, S/N 28-4385, built 1967 (OpenAirDocs)
- Reported make and model: PIPER PA-28-180
- Registry model: [Piper PA-28-180](https://openairdocs.org/model/piper-pa-28-180) (registry code 7102808) (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: 28-4385
- Airframe hours: 2825
- Engines: 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

## Aircraft 2

- Registration: [N50464](https://openairdocs.org/deregistered/N50464-2014-11-25), registration cancelled 2014-11-25, S/N 15069321, built 1968 (OpenAirDocs)
- Reported make and model: CESSNA 150J
- Registry model: [Cessna 150J](https://openairdocs.org/model/cessna-150j) (registry code 2071820) (OpenAirDocs)
- Registry engine: [Continental 0-200 series](https://openairdocs.org/engine/continental-0-200-series) (registry code 17020, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 15069321
- Airframe hours: 5475
- Engines: 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

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot, aircraft N5101L; age 61; injuries: none; 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
- Flight instructor, aircraft N50464; age 60; injuries: none; 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
- Student pilot, aircraft N50464; age 64; injuries: none; 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

## FAA reports on this event (2)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20100824042051A](https://openairdocs.org/incident/20100824042051A), Aug 24, 2010: Piper PA-28-180, Sequim, WA, Substantial damage. Aircraft was landing at Diamond Point Airstrip. The aircraft touched down prior to the runway and made contact with an embankment. The aircraft bounced and…
- [Accident 20100824042091A](https://openairdocs.org/incident/20100824042091A), Aug 24, 2010: Cessna 150J, Sequim, WA, Substantial damage. The aircraft was in the runup area next to the runway. An aircraft coming in to land touched prior to the runway and bounced, striking the aircraft in he runup…

## Docket (18 files)

The files NTSB released with the investigation on November 22, 2011, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=77072. 6.8 MB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1, N50464 (item 1, .PDF, 874 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40335898&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1,%20N50464-Redacted.PDF
- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1, N5101L (item 2, .PDF, 2.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40358283&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1,%20N5101L-Redacted.PDF
- Witness Statement & Photo, Conquest (item 3, .PDF, 568 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40358288&FileExtension=.PDF&FileName=Witness%20Statement%20%26%20Photo,%20Conquest-Redacted.PDF
- Statement & Photos of Student Pilot, N50464 (item 4, .PDF, 1.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40358289&FileExtension=.PDF&FileName=Statement%20%26%20Photos%20of%20Student%20Pilot,%20N50464-Redacted.PDF
- Photo 1. Cessna 150 Aileron part imbeded on Piper Strut (item 5, .PDF, 151 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40358297&FileExtension=.PDF&FileName=Photo%201.%20%20Cessna%20150%20Aileron%20part%20imbeded%20on%20Piper%20Strut-Master.PDF
- Photo 2. Cessna 150 front wheel skid marks (item 6, .PDF, 208 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40358299&FileExtension=.PDF&FileName=Photo%202.%20%20Cessna%20150%20front%20wheel%20skid%20marks-Master.PDF
- Photo 3. Crash site showing both airplanes (item 7, .PDF, 96 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40358301&FileExtension=.PDF&FileName=Photo%203.%20Crash%20site%20showing%20both%20airplanes-Master.PDF
- Photo 4. Damaged right wing of Cessna 150 (item 8, .PDF, 131 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40358302&FileExtension=.PDF&FileName=Photo%204.%20Damaged%20right%20wing%20of%20Cessna%20150-Master.PDF
- Photo 5. Front wheel skid marks of Cessna 150 (item 9, .PDF, 235 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40358303&FileExtension=.PDF&FileName=Photo%205.%20Front%20wheel%20skid%20marks%20of%20Cessna%20150-Master.PDF
- Photo 6. Fuel leak and asphault damage from Piper 180 (item 10, .PDF, 142 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40358304&FileExtension=.PDF&FileName=Photo%206.%20Fuel%20leak%20and%20asphault%20damage%20from%20Piper%20180-Master.PDF
- Photo 7. Fuel spill damage on runway (item 11, .PDF, 192 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40358305&FileExtension=.PDF&FileName=Photo%207.%20%20Fuel%20spill%20damage%20on%20runway-Master.PDF
- Photo 8. Landing gear marks on runway berm (item 12, .PDF, 182 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40358306&FileExtension=.PDF&FileName=Photo%208.%20Landing%20gear%20marks%20on%20runway%20berm-Master.PDF
- Photo 9. Piper 180 crash site (item 13, .PDF, 124 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40358307&FileExtension=.PDF&FileName=Photo%209.%20%20Piper%20180%20crash%20site-Master.PDF
- Photo 10. Piper crash site on runway 29 (item 14, .PDF, 106 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40358308&FileExtension=.PDF&FileName=Photo%2010.%20Piper%20crash%20site%20on%20runway%2029-Master.PDF
- Photo 11. Prop strikes (item 15, .PDF, 199 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40358309&FileExtension=.PDF&FileName=Photo%2011.%20%20Prop%20strikes-Master.PDF
- Photo 12. Runup pad on runway 29 (item 16, .PDF, 176 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40358310&FileExtension=.PDF&FileName=Photo%2012.%20%20Runup%20pad%20on%20runway%2029-Master.PDF
- Photo 13. Skid marks from Piper 180 crash (item 17, .PDF, 141 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40358311&FileExtension=.PDF&FileName=Photo%2013.%20%20Skid%20marks%20from%20Piper%20180%20crash-Master.PDF
- Photo 14. View from across Diamond Point Road (item 18, .PDF, 155 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40358312&FileExtension=.PDF&FileName=Photo%2014.%20%20View%20from%20across%20Diamond%20Point%20Road-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.