# Incident 20160516017859I: Cessna 172P, Mesquite, NV, May 16, 2016

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: May 16, 2016, 12:00 local time
- Place: Mesquite, NV
- Airport: Mesquite
- Damage: Minor damage
- Phase of flight: Cruise/Level Flight
- Operating rules: General operating rules (Part 91)
- Location: 36.8331° N, 114.0559° W: Placed by OpenAirDocs at MESQUITE (67L), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=36.8331&lon=-114.0559&mi=10
- Aircraft: N5268K, registered now (https://openairdocs.org/aircraft/N5268K) (OpenAirDocs)
- Registry model: Cessna 172P (registry code 2072436, https://openairdocs.org/model/cessna-172p) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172P
- Reported engine: LYCOMING 0-320 SERIES
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20160516017859I

## Narrative

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

AIRCRAFT MADE EMERGENCY LANDING IN FIELD DUE TO SMOKE IN COCKPIT. MINOR AIRCRAFT DAMAGE AND NO INJURIES.

## Other reports on N5268K (2)

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

- [Accident 20250202000639A](https://openairdocs.org/incident/20250202000639A), Feb 2, 2025: Cessna 172P (N5268K), Ramona, CA, Substantial damage. Flight took off from kmyf for recreational flight to L08 at approximately 1115PST. After a few touch and go's at L08, the flight proceeded to krnm for a few…
- [Accident 20020725017359A](https://openairdocs.org/incident/20020725017359A), Jul 25, 2002: Cessna 172P (N5268K), Creston, CA, Substantial damage. (.19) On July 25, 2002, at 2130 pacific daylight time, a Cessna 172P, N5268K, lost engine power and forced landed on a road near Creston, California. The…

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.