Cessna 172S accident near Compton, California, October 6, 2008
On October 6, 2008 at about 3:30 am local time, a Cessna 172S, registered N6048Z, was substantially damaged in an accident during landing (flare/touchdown) near Compton, California (Compton airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were 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 recovery from a bounced landing.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- October 6, 2008 · about 3:30 am local time
- Place
- Compton, California · Compton · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 172S · all 172Ss on the register
- Registration
- N6048Z · registry record · serial 172S10217
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The private pilot reported that the airplane bounced during landing. The airplane then began to porpoise and after the third bounce the pilot pushed the control yoke forward. The propeller then struck the runway surface. The pilot stated that he initially believed the airplane damage was limited to the propeller. Subsequent inspection revealed that the airplane sustained substantial damage to the firewall and forward fuselage structure. The extent of the damage was not reported to the NTSB until June 1, 2009. The pilot reported no mechanical failures or malfunctions with the airframe or engine prior to the accident.
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
- Hard landing during landing (flare/touchdown) defining event
- Abnormal runway contact during landing (flare/touchdown)
The NTSB's findings
- cause Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
- 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
- Flight time: 60 hours in all; 60 in this make and model
- Medical certificate: Class 1 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 1,078 hours
- Last inspection: inspection type not recorded
- Maximum gross weight: 2,550 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming IO-360-L2A (piston); 0 hours total
The flight
- Departed from: CPM Compton CA at 3:20 am
- Destination: CPM Compton CA
- Flight plan: VFR
- Runway 25L, 3,322 ft by 60 ft
Weather at the time
- Light: night, dark
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 66°F (19°C), dew point 59°F (15°C)
- Altimeter: 29.93 inHg
- Observation at 4:53 am from HHR, 5 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 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.