# NTSB WPR10CA351: Piper PA-28-236, N8337A, Fullerton, CA, July 15, 2010 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: July 15, 2010, 13:09 local (20:09 UTC) - Place: Fullerton, CA - Coordinates: 33.86972, -117.974441 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=33.8697&lon=-117.9744&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report December 20, 2010 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 76645 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR10CA351 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/76645/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=76645 - Page: https://openairdocs.org/ntsb/WPR10CA351 ## Probable cause The pilot’s improper flare and inadequate bounced landing recovery, which resulted in a hard landing and porpoise down the runway. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Incorrect use/operation (probable cause); cases with it: [Piper PA-28-236, 2 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=7102815), [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Piper PA-28-236, 8 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=7102815), [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-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) (defining event); cases with it: [Piper PA-28-236, 1 case](https://openairdocs.org/ntsb-events/090/sequence.md?model=7102815), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md) - [Landing-landing roll: Landing area overshoot](https://openairdocs.org/ntsb-events/380); cases with it: [Piper PA-28-236, 1 case](https://openairdocs.org/ntsb-events/380/sequence.md?model=7102815), [All aircraft, 400 cases](https://openairdocs.org/ntsb-events/380/sequence.md) ## Analysis The pilot reported that during landing the airplane porpoised twice down the runway. He decided to continue the landing as he believed there to be sufficient remaining runway to abort the landing. The pilot attempted to stop the airplane using the brakes when the airplane skidded off the end of the runway and struck a chain link fence. The airplane sustained substantial damage to the firewall during the accident sequence. The pilot reported that there were no preexisting mechanical problems with the airplane. ## Factual narrative The pilot reported that during landing the airplane porpoised twice down the runway. He decided to continue the landing as there was not enough remaining runway in his opinion to abort the landing. The pilot attempted to stop the airplane using the brakes. The airplane skidded off the end of the runway and struck a chain link fence. The airplane sustained substantial damage to the firewall during the accident sequence. The pilot reported that there were no mechanical problems with the airplane. ## Aircraft - Registration: [N8337A](https://openairdocs.org/aircraft/N8337A), registered now, S/N 28-8111051, built 1981 (OpenAirDocs) - Reported make and model: PIPER PA-28-236 - Registry model: [Piper PA-28-236](https://openairdocs.org/model/piper-pa-28-236) (registry code 7102815) (OpenAirDocs) - Registry engine: [Lycoming 0-540 series](https://openairdocs.org/engine/lycoming-0-540-series) (registry code 41532, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 28-8111051 - Airframe hours: 2782 - Engines: LYCOMING O-540 SERIES 250 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, October 2, 2009, 15 hours before - Departed: SNA, Santa Ana, CA - Destination: FUL, Fullerton, CA - Flight plan: IFR - Airport: FUL, Fullerton Municipal Airport, runway 24, 3,121 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 48; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, without waivers/limitations; last flight review April 26, 2009; seat: left; flight hours: 1,510 total, 485 in this make and model, 1,380 as pilot in command, 32 in the last 90 days, 15 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 200° at 6 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 88 °F, dew point 57 °F - Altimeter: 29.86 inHg - Observed at: FUL ## 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 20100715037919A](https://openairdocs.org/incident/20100715037919A), Jul 15, 2010: Piper PA-28-236, Fullerton, CA, Substantial damage. The pilot was attempting a landing at Fullerton airport on rwy 24. Weather at the time was VMC and does not appear to be a factor in the accident. The aircraft… ## Docket (1 files) The files NTSB released with the investigation on August 16, 2010, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=76645. 250 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 250 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40334860&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.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.