ASN Wikibase Occurrence # 297309
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can
submit corrected information.
Date: | Saturday 11 May 2002 |
Time: | 13:50 LT |
Type: | Piper PA-22-135 |
Owner/operator: | Private |
Registration: | N3772A |
MSN: | 22-2014 |
Year of manufacture: | 1954 |
Total airframe hrs: | 2298 hours |
Engine model: | Lycoming O-290-D2 |
Fatalities: | Fatalities: 0 / Occupants: 1 |
Aircraft damage: | Substantial |
Category: | Accident |
Location: | Reno, Nevada -
United States of America
|
Phase: | Unknown |
Nature: | Private |
Departure airport: | Reno, NV (4SD) |
Destination airport: | |
Investigating agency: | NTSB |
Confidence Rating: | Accident investigation report completed and information captured |
Narrative: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.
Probable Cause: Failure of the pilot to maintain directional control. A factor was the hump in the runway.
Accident investigation:
|
| |
Investigating agency: | NTSB |
Report number: | LAX02LA158 |
Status: | Investigation completed |
Duration: | 1 year and 4 months |
Download report: | Final report |
|
Sources:
NTSB LAX02LA158
Revision history:
Date/time | Contributor | Updates |
14-Oct-2022 17:02 |
ASN Update Bot |
Added |
The Aviation Safety Network is an exclusive service provided by:
CONNECT WITH US:
©2024 Flight Safety Foundation