# Incident 20220514007049I: Let L 33 SOLO, Reno, NV, May 14, 2022

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: May 14, 2022, 12:05 local time
- Place: Reno, NV
- Airport: Air Sailing
- Damage: Minor damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 39.8721° N, 119.7010° W: Placed by OpenAirDocs at AIR SAILING (NV23), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=39.8721&lon=-119.7010&mi=10
- Aircraft: N291BA, registered now (https://openairdocs.org/aircraft/N291BA) (OpenAirDocs)
- Registry model: Let L 33 SOLO (registry code 1360309, https://openairdocs.org/model/let-l-33-solo) (OpenAirDocs)
- Registry engine: Amateur-built UNKNOWN ENG (registry code 99999, https://openairdocs.org/engine/amateur-built-unknown-eng) (OpenAirDocs)
- Reported make and model: LET L 33 SOLO
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 39 total, 3 in this make and model, 16 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20220514007049I

## Narrative

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

ON 05/14/2022 AT APPROXIMATELY 12:05 PM, LET L-33 SOLO GLIDER N291BA, DEPARTED AND ARRIVED AT AIR SAILING GLIDERPORT (NV23).  GLIDER PILOT WAS CONDUCTING A PERSONAL PLEASURE FLIGHT.  ON FINAL APPROACH OF RUNWAY 17 THE PILOT FORCED THE AIRCRAFT DOWN AT A HIGHER THAN REQUIRED AIRSPEED RESULTING IN A HARD LANDING.  PILOT DID NOT USE AIR BRAKES. ON INITIAL TOUCHDOWN AIRCRAFT BOUNCED, BECAME AIRBORNE, CAME BACK DOWN, AND VEERED RIGHT AND CAME TO REST RIGHT OF THE RUNWAY 17.  THE AIRCRAFT SUSTAINED MINOR DAMAGE TO THE FUSELAGE BELOW THE COCKPIT, MINOR DAMAGE TO THE LH WING ATTACHMENT POINT WHERE SHEAR RIVETS WERE POPPED, AND THE MINOR SKIN DAMAGE TO THE UPPER FUSELAGE AREA JUST FORWARD OF THE EMPENNAGE.

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.