# NTSB WPR18LA203: Piper PA32, N4747H, Avalon, CA, July 25, 2018

- Type: NTSB accident investigation
- Classification: Accident · Serious injuries · Class 3 · Limited · Final report
- Date: July 25, 2018, 09:30 local (16:30 UTC)
- Place: Avalon, CA
- Coordinates: 33.401668, -118.421112 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=33.4017&lon=-118.4211&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing-aborted after touchdown: Runway excursion](https://openairdocs.org/ntsb-events/300)
- Highest injury: Serious injuries
- Injuries: 1 serious, 2 minor
- Status: Completed
- Report: Approved by Office Director
- Investigation class: Class 3
- NTSB office: Western Pacific Region
- Parties: FAA
- NTSB case key (mKey): 97891
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR18LA203
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/97891/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=97891
- Page: https://openairdocs.org/ntsb/WPR18LA203

## Probable cause

The pilot's delayed decision to conduct a go-around following an unstable landing approach and long landing.

## 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 · Not attained/maintained (probable cause); cases with it: [Piper PA-32-300, 5 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=7103212), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md)
- [Action: delayed action](https://openairdocs.org/ntsb-findings/02041025): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Piper PA-32-300, 4 cases](https://openairdocs.org/ntsb-findings/02041025/cases.md?model=7103212), [All aircraft, 894 cases](https://openairdocs.org/ntsb-findings/02041025/cases.md)
- [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Piper PA-32-300, 14 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=7103212), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md)
- [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot; cases with it: [Piper PA-32-300, 25 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=7103212), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md)

## Sequence of events

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

- [Landing: Landing area overshoot](https://openairdocs.org/ntsb-events/380); cases with it: [Piper PA-32-300, 4 cases](https://openairdocs.org/ntsb-events/380/sequence.md?model=7103212), [All aircraft, 400 cases](https://openairdocs.org/ntsb-events/380/sequence.md)
- [Landing-aborted after touchdown: Runway excursion](https://openairdocs.org/ntsb-events/300) (defining event); cases with it: [Piper PA-32-300, 11 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=7103212), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md)
- [Landing-aborted after touchdown: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper PA-32-300, 43 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7103212), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md)

## Analysis

A witness reported that the pilot's first landing attempt was too high, and the airplane went around. During the second landing attempt, the airplane was "still too high and came in too fast." The airplane touched down past the runway midpoint, and as the airplane neared the end of the runway, the witness heard the engine "rev up" and saw the airplane depart the runway in a "very nose high" pitch attitude. The airplane subsequently collided with terrain about 1,000 ft beyond the departure end of the runway and about 75 to 100 ft below the runway surface elevation. The pilot reported that he did not recall the events of the accident, but stated that there were no mechanical anomalies with the airplane. The accident is consistent with the pilot's delayed decision to conduct a go-around following an unstable approach and long landing, which resulted in the airplane having insufficient airspeed to climb after the attempted go-around and impact with terrain.

## Factual narrative

On July 25, 2018, about 0930 Pacific daylight time, a Piper PA-32-300, N4747H, was substantially damaged when it was involved in an accident in Avalon, California. The private pilot sustained serious injuries and the two passengers sustained minor injuries. The airplane was operated by the pilot as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot reported that he did not remember the accident but did state there were no mechanical failures or malfunctions with the airplane prior to the accident. The airport manager reported that when the airplane was on downwind, he advised the pilot of the wind which was 330° at 4 knots. He stated that the pilot's first landing attempt was too high, and the airplane went around. On the second landing attempt the airplane was "still too high and came in too fast" but touched down past about midfield. As the airplane neared the end of the runway, he heard the engine "rev up" and observed the airplane depart the runway in a "very nose high" pitch attitude. The airplane subsequently collided with terrain about 1,000 ft beyond the departure end of the runway and about 75 to 100 ft below the runway surface elevation in a nose low attitude.

## Aircraft

- Registration: [N4747H](https://openairdocs.org/deregistered/N4747H-2020-01-06), registration cancelled 2020-01-06, S/N 32-7940158 (OpenAirDocs)
- Reported make and model: Piper PA32 (300)
- Registry model: [Piper PA-32-300](https://openairdocs.org/model/piper-pa-32-300) (registry code 7103212) (OpenAirDocs)
- Registry engine: [Lycoming IO-540 series](https://openairdocs.org/engine/lycoming-io-540-series) (registry code 41530, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 32-7940158
- Engines: Lycoming IO-540 SER reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Airworthiness certificate: Standard, Normal
- Departed: FUL, Fullerton, CA
- Destination: AVX, Avalon, CA
- Airport: AVX, Catalina, runway 22, 3,000 × 75 ft, asphalt
- Equipment: Unknown

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 71; injuries: serious; private; airplane ratings: single-engine land, single-engine sea; instrument ratings: airplane; medical: class 3, with waivers/limitations; seat: left

## Weather

- Conditions: Visual (VMC), Day
- Wind: calm
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 84 °F, dew point 57 °F
- Altimeter: 30.03 inHg
- Observed at: KAVX

## 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 20180725017979A](https://openairdocs.org/incident/20180725017979A), Jul 25, 2018: Piper PA-32-300, Avalon, CA, Destroyed. July 25, 2018 N4747H departed kful enroute to kavx at approx 0905 hrs with 3 souls on board, one pilot and 2 los angeles county sheriff deputies. At…

## Docket (3 files)

The files NTSB released with the investigation on October 9, 2020, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=97891. 323 KB in all.

- Record of conversation-pilot (item 1, PDF, 1 page, 121 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=8543134&FileExtension=pdf&FileName=Record%20of%20Conversation_Pilot-Rel.pdf
- Airport manager statement (item 2, PDF, 1 page, 75 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=7371938&FileExtension=pdf&FileName=Airport%20Manager%20Statement-Rel.pdf
- Accident photo (item 3, PDF, 1 page, 1 photo, 127 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=7371339&FileExtension=pdf&FileName=Accident%20Photo-Rel.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.
