# Accident 20020216002329A: Piper PA18A150, Beatty, NV, February 16, 2002

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: February 16, 2002, 10:30 local time
- Place: Beatty, NV
- Airport: Beatty Airport
- Damage: No damage
- Operating rules: General operating rules (Part 91)
- Location: 37.0903° N, 116.7904° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=37.0903&lon=-116.7904&mi=10
- Aircraft: N9299D, a cancelled registration (https://openairdocs.org/deregistered/N9299D-2019-01-25) (OpenAirDocs)
- Registry model: Piper PA-18A 150 (registry code 7101837, https://openairdocs.org/model/piper-pa-18a-150) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: PIPER PA18A150
- Fatal injuries: 0
- NTSB investigation: [NTSB LAX02LA087](https://openairdocs.org/ntsb/LAX02LA087) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20020216002329A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) AIRCRAFT WAS LANDING ON RUNWAY 34 BEATTY AIRPORT, WITH THE WINDS COMING STRAIGHT DOWN THE RUNWAY AT APPROXIMATELY 5 KNOTS. THE AIRCRAFT HIT SOMEWHAT HARD ACCORDING TO THE PILOT. THE PILOT STATED THAT HIS TAIL WHEEL WAS ON THE GROUND AND HIS RUDDER CONTROL WAS USELESS AT THIS POINT. THE AIRCRAFT THEN STARTED DRIFTING TO THE RIGHT OF CENTERLINE, WHEREIN THE PILOT MADE AN IMMEDIATE CORRECTION BY APPLYING A BRAKING ACTION IN THE OPPOSITE DIRECTION. UPON DOING SO, THE AIRCRAFT'S NOSE DIPPED ABRUPTLY AND SUBSEQUENTLY CONTINUED TO FLIP UPON IT'S BACK. THE AIRCRAFT CAME TO REST COMPLETELY UPSIDE DOWN AND REMAINED UPON THE RUNWAY UNTIL THE PILOT WAS ABLE TO OBTAIN ASSISTANCE.

## The NTSB's investigation of this event (1)

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.

- [NTSB LAX02LA087](https://openairdocs.org/ntsb/LAX02LA087), Feb 16, 2002: Piper PA-18-150 (N9299D), Beatty, NV, substantial damage. Probable cause: The pilot failed to maintain control of the airplane.

## Other reports on N9299D (3)

Matched to the same aircraft by N-number and date.

- [Accident 20140420005829A](https://openairdocs.org/incident/20140420005829A), Apr 20, 2014: Piper PA-18A 150 (N9299D), Ninilchik, AK, Substantial damage. Aircraft was taking off from a beach at fossil point in lake clark national park. Airman says he hit a bump and lost control during takeoff roll, and…
- [Accident 20010329005579A](https://openairdocs.org/incident/20010329005579A), Mar 29, 2001: Piper PA18150 (N9299D), Holbrook, AZ, Substantial damage. (.19)On March 29, 2001, about 1030 hours MST, a Piper PA18-150, N9299D, op erated by the pilot was substantially daamged during landing rollout at Holbrook,…
- [Accident 19950604017929A](https://openairdocs.org/incident/19950604017929A), Jun 4, 1995: Piper STCPA18 (N9299D), Manley Hs, AK, Substantial damage. Hard landing in gusty wind. Impact jammed rudder and damaged fuselage. Veered off runway.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
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.