# NTSB LAX02LA158: Piper PA-22-135, N3772A, Reno, NV, May 11, 2002 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: May 11, 2002, 14:50 local (21:50 UTC) - Place: Reno, NV - Coordinates: 39.667221, -119.875556 - Nearby events: https://openairdocs.org/map.md?lat=39.6672&lon=-119.8756&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report September 30, 2003 - Report: Approved by Office Director - Parties: FAA - NTSB case key (mKey): 54699 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX02LA158 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/54699/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=54699 - Page: https://openairdocs.org/ntsb/LAX02LA158 ## Probable cause Failure of the pilot to maintain directional control. A factor was the hump in the runway. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of control - on ground/water, landing - roll - weather condition - crosswind - directional control - not maintained, pilot in command (cause) - airport facilities,runway/landing area condition - other (contributing factor) - ground loop/swerve - encountered - On ground/water encounter with terrain/water, landing - roll - terrain condition - ground ## Analysis 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. ## Factual narrative On May 11, 2002, at 1450 Pacific daylight time, a Piper PA-22-135, N3772A, veered off runway 8 and ground looped while landing at the Reno Stead Airport, Reno, Nevada. The airplane was owned and operated by the pilot under the provisions of 14 CFR Part 91. The airplane sustained substantial damage. The private pilot, the sole occupant, was not injured. Visual meteorological conditions prevailed and no flight plan was filed. The local area personal flight departed from the Reno Stead Airport about 1445, to practice takeoffs and landings at the airport. In a telephone interview, the pilot stated that he intended to do a few pattern circuits to practice takeoffs and landings and was using runway 8. 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. A Federal Aviation Administration inspector from the Reno Flight Standards District Office, reported that there is a small hump in the pavement near the approach end of runway 8. ## Aircraft - Registration: [N3772A](https://openairdocs.org/aircraft/N3772A), registered now, S/N 22-2014, built 1954 (OpenAirDocs) - Reported make and model: Piper PA-22-135 - Registry model: [Piper PA-22-135](https://openairdocs.org/model/piper-pa-22-135) (registry code 7102206) (OpenAirDocs) - Registry engine: [Lycoming 0-290 series](https://openairdocs.org/engine/lycoming-0-290-series) (registry code 41506, 4 cycle) (OpenAirDocs) - Category: Airplane - Serial number: 22-2014 - Airframe hours: 2298 - Engines: Lycoming O-290-D2 135 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: Raymond A. Craft - Airworthiness certificate: Standard, Normal - Last inspection: Annual, September 26, 2001, 10 hours before - Departed: 4SD, Reno, NV - Airport: 4SD, Reno Stead, runway 8, 7,600 × 150 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 78; injuries: none; private; airplane ratings: single-engine land; medical: class 3, valid medical--w/ waivers/lim; last flight review November 1, 2000; seat: left; flight hours: 876 total, 72 in this make and model, 876 as pilot in command, 5 in the last 90 days, 2 in the last 30 days, 0 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 30° at 7 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 61 °F - Altimeter: 30.17 inHg - Observed at: 4SD ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20020511009779A](https://openairdocs.org/incident/20020511009779A), May 11, 2002: Piper PA22135, Reno, NV, No damage. (.19) On may 11, 2002, at 1450 pacific daylight time, a Piper PA-22-135, N3772A, veered off runway 8 and ground looped while landing at the Reno Stead airport,… ## Docket (2 files) The files NTSB released with the investigation on July 29, 2003, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=54699. 544 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 516 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40436601&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Phone Interview (item 2, .PDF, 27 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40169245&FileExtension=.PDF&FileName=Phone%20Interview-Master.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.