Cirrus Design CORP SR22 accident near Torrance, California, January 15, 2013
On January 15, 2013 at about 3:00 am local time, a Cirrus Design CORP SR22, registered N5384W, was substantially damaged in an accident during landing (flare/touchdown) near Torrance, California (Zamperini Field). 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 landing flare, which resulted in a bounced landing.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- January 15, 2013 · about 3:00 am local time
- Place
- Torrance, California · Zamperini Field · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cirrus Design CORP SR22
- Registration
- N5384W · registry record · serial 0854
- 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 he intended to land on an asphalt runway in night visual conditions. As the airplane approached the runway, he added engine power because the flight controls felt “mushy.” The airspeed was about 85 knots with full flaps, and the airplane remained in ground effect longer than usual. When the airplane touched down, it bounced and the propeller struck the runway surface. The airplane porpoised but eventually came to a stop. The airplane sustained substantial damage to the engine mount structure and support assembly. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.
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
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Not attained/maintained
- cause Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 608 hours in all; 585 in this make and model; 12 in the last 90 days; 6 in the last 30 days; 397 as pilot in command
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 958 hours
- Last inspection: annual inspection, September 13, 2012
- Maximum gross weight: 3,400 lb
- Seats: 4
- Landing gear: fixed
- Engine: Cont Motor IO-550 SERIES (piston); 0 hours total
The flight
- Departed from: KBUR Burbank CA
- Destination: KTOA Torrance CA
- Flight plan: not recorded
- Runway 29R, 5,000 ft by 80 ft
Weather at the time
- Light: night, dark
- Visibility: 20 statute miles
- Sky: clear
- Temperature: 41°F (5°C), dew point 0°F (-18°C)
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.
Other NTSB records under N5384W the same tail number, which may have belonged to a different aircraft at the time
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.