Piper PA-22 accident near Napa, California, August 12, 2012
On August 12, 2012 at about 10:08 pm local time, a Piper PA-22, registered N3580A, was substantially damaged in an accident during landing (landing roll) near Napa, California (Napa County 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 inadequate landing flare, which resulted in a bounced landing and subsequent loss of directional control during the landing roll.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 12, 2012 · about 10:08 pm local time
- Place
- Napa, California · Napa County Airport · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-22 · all PA-22s on the register
- Registration
- N3580A · registry record · serial 22-1855
- 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 while landing the tailwheel-equipped airplane in a slight crab, it bounced upon touchdown. She was unable to maintain directional control and the airplane veered off of the runway, which resulted in substantial damage to the left wing. 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
- Loss of control on ground during landing (landing roll) defining event
- Runway excursion during landing (landing roll)
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Incorrect use/operation
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 97 hours in all; 15 in this make and model; 6 in the last 90 days; 6 in the last 30 days; 32 as pilot in command
- Last flight review: July 24, 2011
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 1,895 hours
- Last inspection: annual inspection, August 2, 2011; 30 hours since
- Maximum gross weight: 1,950 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming O-320 (piston); 0 hours total
The flight
- Departed from: APC Napa CA at 9:45 pm
- Destination: APC Napa CA
- Flight plan: none
- Runway 18R, 5,931 ft by 150 ft
Weather at the time
- Light: daylight
- Wind: from 170° at 10 knots, gusting 10
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 81°F (27°C), dew point 45°F (7°C)
- Altimeter: 30.00 inHg
- Observation at 9:45 pm from APC
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.