Piper PA-22-135 accident near Reno, Nevada, May 11, 2002
On May 11, 2002 at about 9:50 pm local time, a Piper PA-22-135, registered N3772A, was substantially damaged in an accident near Reno, Nevada (Reno Stead 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
Failure of the pilot to maintain directional control. A factor was the hump in the runway.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- May 11, 2002 · about 9:50 pm local time
- Place
- Reno, Nevada · Reno Stead · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-22-135 · all PA-22-135s on the register
- Registration
- N3772A · registry record · serial 22-2014
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The tail-wheel equipped airplane veered off runway 8 and ground looped while landing with a 4-knot left crosswind component. The pilot stated that he intended to do a few pattern circuits to practice takeoffs and landings. The accident happened on the first landing. Just after touchdown, the airplane hit what the pilot described as some sort of hump in the pavement and bounced up in the air again. He added some power to cushion the touchdown and the airplane veered off the runway and into the infield area. It touched down in the dirt and he was unable to regain control before the airplane ground looped. The pilot said he is not certain, but he thinks he may have encountered a gust of wind that helped induce the loss of control. He stated that there were no mechanical malfunctions or failures that preceded the loss of control. An FAA inspector reported that there is a small hump in the pavement near the approach end of runway 8.
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
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 876 hours in all; 72 in this make and model; 5 in the last 90 days; 2 in the last 30 days; 876 as pilot in command
- Last flight review: November 1, 2000
- Medical certificate: Class 3 (valid medical--w/ waivers/lim.)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 2,298 hours
- Last inspection: annual inspection, September 26, 2001; 10 hours since
- Maximum gross weight: 1,950 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming O-290-D2 (piston); 0 hours total
The flight
- Departed from: 4SD Reno NV at 9:45 pm
- Flight plan: none
- Runway 8, 7,600 ft by 150 ft
Weather at the time
- Light: daylight
- Wind: from 030° at 7 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 61°F (16°C), dew point 0°F (-18°C)
- Altimeter: 30.17 inHg
- Observation at 9:46 pm from 4SD
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| 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.