# Incident 20251021017719I: Cessna 172M, Naples, FL, October 21, 2025

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: October 21, 2025, 02:42 local time
- Place: Naples, FL
- Airport: Naples Airport
- Damage: Minor damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 26.1524° N, 81.7756° W: Placed by OpenAirDocs at NAPLES MUNI (APF), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=26.1524&lon=-81.7756&mi=10
- Aircraft: N20392, registered now (https://openairdocs.org/aircraft/N20392) (OpenAirDocs)
- Registry model: Cessna 172M (registry code 2072418, https://openairdocs.org/model/cessna-172m) (OpenAirDocs)
- Registry engine: Lycoming O-320-E2D (registry code 42123, https://openairdocs.org/engine/lycoming-o-320-e2d) (OpenAirDocs)
- Reported make and model: CESSNA 172M
- Reported engine: LYCOMING O-320-E2D
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 112 total
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20251021017719I

## Narrative

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

THE AIRCRAFT DEPARTED FORT LAUDERDALE EXECUTIVE AIRPORT (FXE) AT APPROXIMATELY 0051 EDT EN ROUTE TO SOUTHWEST FLORIDA INTERNATIONAL AIRPORT (RSW). DUE TO A RUNWAY CLOSURE ADVISORY AT RSW, THE PILOT DIVERTED TO PAGE FIELD (FMY). UPON APPROACHING FMY, THE PILOT WAS UNABLE TO SEE THE RUNWAY, PROMPTING ANOTHER DIVERSION TO NAPLES MUNICIPAL AIRPORT (APF). WHILE APPROACHING APF, THE PILOT WAS UNABLE TO ACTIVATE THE PILOT-CONTROLLED LIGHTING AND EXECUTED SEVERAL NON-STANDARD PATTERNS AND LOW APPROACHES PARALLEL TO RUNWAY 5. THE PILOT LANDED APPROXIMATELY 125 FEET TO THE RIGHT OF RUNWAY 5 ON THE GRASS, STRIKING A DITCH, WHICH RESULTED IN THE NOSE LANDING GEAR BREAKING AND THE PROPELLER HITTING THE GROUND. BOTH THE PILOT AND PASSENGER THEN WALKED TO THE FIXED-BASE OPERATOR (FBO), WHERE A SECURITY GUARD RECORDED THE AIRCRAFT NUMBER. HOWEVER, THEY DID NOT REPORT THE INCIDENT OR THE AIRCRAFT'S LOCATION BEFORE LEAVING THE AIRPORT.

## Other reports on N20392 (1)

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

- [Incident 19840122009829I](https://openairdocs.org/incident/19840122009829I), Jan 22, 1984: Cessna 172M (N20392), Yuma, CO, Minor damage. Student lost control landing in a quartering crosswind. Ran off runway into plowed snow.

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.