Piper PA-28-236 accident near Fullerton, California, July 15, 2010
On July 15, 2010 at about 8:09 pm local time, a Piper PA-28-236, registered N8337A, was substantially damaged in an accident during landing (flare/touchdown) near Fullerton, California (Fullerton Municipal Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot’s improper flare and inadequate bounced landing recovery, which resulted in a hard landing and porpoise down the runway.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 15, 2010 · about 8:09 pm local time
- Place
- Fullerton, California · Fullerton Municipal Airport · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-28-236 · all PA-28-236s on the register
- Registration
- N8337A · registry record · serial 28-8111051
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Abnormal runway contact during landing (flare/touchdown) defining event
- Landing area overshoot during landing (landing roll)
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Incorrect use/operation
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 1,510 hours in all; 485 in this make and model; 32 in the last 90 days; 15 in the last 30 days; 1,380 as pilot in command
- Last flight review: April 26, 2009
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 2,782 hours
- Last inspection: annual inspection, October 2, 2009; 15 hours since
- Maximum gross weight: 3,000 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming O-540 SERIES (piston); 0 hours total
The flight
- Departed from: SNA Santa Ana CA at 7:45 pm
- Destination: FUL Fullerton CA
- Flight plan: IFR
- Runway 24, 3,121 ft by 75 ft
Weather at the time
- Light: daylight
- Wind: from 200° at 6 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 88°F (31°C), dew point 57°F (14°C)
- Altimeter: 29.86 inHg
- Observation at 7:53 pm from FUL
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.