- Date
- July 15, 2010, 13:09 local (20:09 UTC)
- Place
- Fullerton, CA
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N8337APiper PA-28-236
- Defining event
- Landing-flare/touchdown: Abnormal runway contact
- Weather
- Visual (VMC) · Day
- Status
- Completed · report December 20, 2010
- Report
- Approved by Office Director
- NTSB office
- Western Pacific Region
- Parties
- Federal Aviation Administration
- FAA report
- 20100715037919A
- Case key
- 76645
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 improper flare and inadequate bounced landing recovery, which resulted in a hard landing and porpoise down the runway.
Findings · 2
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.
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.
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
- Reported as
- Piper PA-28-236
- Category
- Airplane
- Serial number
- 28-8111051
- Airframe hours
- 2,782
- Engine
- 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
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
- 48
- Injuries
- None
- Certificate
- 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
Docket · 1
The files NTSB released with the investigation on August 16, 2010, on NTSB’s docket system: statements, records, photos and specialists’ reports. 250 KB in all.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.