Piper PA-24-400 accident near Minden, Nevada, March 12, 2013
On March 12, 2013 at about 7:27 pm local time, a Piper PA-24-400, registered N8533P, was substantially damaged in an accident during landing (flare/touchdown) near Minden, Nevada (Minden-Tahoe Airport). It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's improper flare, which resulted in a bounced landing and a loss of directional control.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- March 12, 2013 · about 7:27 pm local time · cases in 2013
- Place
- Minden, Nevada · Minden-Tahoe Airport · cases near this airport · map
- Type
- Accident
- Injuries
- 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-24-400 · all PA-24-400s on the register
- Registration
- N8533P · registry record · serial 26-114
- 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 the landing, he crossed the threshold at 85 to 90 knots with 15 degrees of flaps. The pilot used the electric trim as the airplane “floated” about 3 to 4 feet above the runway. The airplane subsequently touched down hard, and it bounced three times, striking the propeller on the runway each time. The pilot was unable to maintain directional control by applying brakes and making rudder control inputs, and the airplane departed the side of the runway, collapsing the landing gear. Postaccident examinations revealed substantial damage to the airplane’s lower belly main structure from the forward bulkhead firewall to just aft of the wing. The pilot reported no preimpact mechanical failures or malfunctions 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
- Hard landing during landing (flare/touchdown) defining event
- Loss of control on ground during landing (landing roll)
- Runway excursion during landing (landing roll)
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Not attained/maintained
- 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
- cause Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
Pilot
- Certificate: private
- Ratings: multi-engine land; single-engine land
- Flight time: 4,000 hours in all; 60 in this make and model; 10 in the last 90 days
- Last flight review: April 30, 2011
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 4,540 hours
- Last inspection: annual inspection, August 15, 2012
- Maximum gross weight: 3,600 lb
- Seats: 4
- Landing gear: retractable
- Engine: Lycoming IO-720 (piston); 0 hours total
The flight
- Departed from: 41U Manti UT at 4:15 pm
- Destination: MEV Minden NV
- Flight plan: none
- Runway 34, 7,400 ft by 100 ft
Weather at the time
- Light: daylight
- Wind: from 070° at 7 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 63°F (17°C), dew point 18°F (-8°C)
- Altimeter: 30.25 inHg
- Observation at 7:35 pm from CXP, 11 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
5 documents, released by the NTSB on April 24, 2013. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 9 pages | View Download |
| 2 | Pilot Statement | PDF, 1 page | View Download |
| 3 | Map of Parts Location | PDF, 1 page | View Download |
| 4 | FAA Interview of Pilot | PDF, 2 pages | View Download |
| 5 | Email Regarding Where Parts Were Found | PDF, 3 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N8533P on the register today · the tail number may have moved to another aircraft since
- Piper PA-24 Comanche 2,428 registered today · the model family and its accident history
- Piper 44,842 aircraft on the register
- Engine: Lycoming IO-720 120 aircraft carry this series today · as the NTSB recorded it
- Minden-Tahoe Airport · nearest airport
- Sanpete County Regional · departed from
- Accidents and incidents in Nevada 1,294 since 1982 · 223 in the last ten years
- Nevada 4,591 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/WPR13CA148.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.