# Accident 20160513009819A: Cessna 172RG, Las Vegas, NV, May 13, 2016

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: May 13, 2016, 14:15 local time
- Place: Las Vegas, NV
- Airport: N Las Vegas
- Damage: Substantial damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 36.2106° N, 115.1936° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=36.2106&lon=-115.1936&mi=10
- Aircraft: N6281V, a cancelled registration (https://openairdocs.org/deregistered/N6281V-2019-05-01) (OpenAirDocs)
- Registry model: Cessna 172RG (registry code 2072438, https://openairdocs.org/model/cessna-172rg) (OpenAirDocs)
- Registry engine: Lycoming O&VO-360 series (registry code 41514, https://openairdocs.org/engine/lycoming-o-vo-360-series) (OpenAirDocs)
- Reported make and model: CESSNA 172RG
- Reported engine: LYCOMING O&VO-360 SER
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot, flight instructor
- NTSB investigation: [NTSB WPR16LA109](https://openairdocs.org/ntsb/WPR16LA109) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20160513009819A

## Narrative

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

PILOT TOUCHED DOWN ON RUNWAY 12R, AIRCRAFT VEERED LEFT AND STRUCK 3000 FOOT RUNWAY MARKER CAUSING SUBSTANTIAL DAMAGE TO AIRCRAFT.

TO BE AMENDED.

## 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 WPR16LA109](https://openairdocs.org/ntsb/WPR16LA109), May 13, 2016: Cessna 172RG (N6281V), Las Vegas, NV, substantial damage. Probable cause: The pilot's loss of directional control during the landing roll, which resulted in a runway excursion.

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.