FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA26LA244 · Cessna 182S

20 Jun 2026 · Naples, FL, United States

Sundowners Cessna 182S · Accident: runway excursion during takeoff

From Wing South Airpark (FA37) to Florida Keys Marathon International Airport (MTH)

Report a problem

Event

NTSB case
ERA26LA244
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Ongoing
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
0
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cessna 182S

Aircraft type
Cessna 182
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N7270H
Operator
Sundowners
Onboard fatalities
Unknown
Route
From Wing South Airpark (FA37), Naples, FLTo Florida Keys Marathon International Airport (MTH), Marathon, FL
Aircraft age
About 27 years (built 1999)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Takeoff · rejected takeoff
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Runway excursion
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

On June 20, 2026 at 1030 eastern daylight time, a Cessna 182S, N7270H, was substantially damaged when it was involved in an accident near Naples, Florida. The pilot and three passengers were uninjured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot reported that he planned to take three friends on a cross-country flight from Wing South Airport (FA37), Naples, Florida to Marathon International Airport (MTH), Marathon, Florida. He also reported it was his first flight of the day. Upon arrival at the departure airport, he conducted a preflight inspection of the airplane and did not find anything concerning. He reported that he received a weather briefing from flight service the night before the flight, then received an updated briefing the following morning. He remarked that it had been “hot that day” and that there were wet conditions at the airport. After the passengers boarded, he started the engine and taxied to runway 18 at FA37. Before departure, he conducted an engine runup and noted that all systems were operating normally. The pilot stated that he then conducted a normal takeoff, with the wing flaps retracted. The pilot reported that during the takeoff roll he observed normal engine indications on the tachometer, manifold pressure, and other engine gauges. He stated that he rotated the airplane at 70 to 75 knots, and that “upon liftoff, the aircraft felt sluggish, and the stall warning horn activated.” The pilot felt that the airplane was not producing sufficient power to climb, but stated “there were no abnormal sounds or instrument indications.” He then lowered the nose to accelerate. A review of airport security camera footage showed that the airplane about came into view when it was about 1,800 ft from the approach end of runway 18, airborne and aligned with runway. The airplane remained at a low altitude above the runway and eventually exited the frame of the security camera. The pilot then determined he did not have adequate airspeed to climb and decided to abort the takeoff. He landed on the remaining runway, and estimated there was 100 to 200 ft of runway remaining after he had touched down. The pilot stated the runway was damp and he did not apply heavy braking as he was concerned the wheels could lock up. The airplane then exited the runway onto grass on the departure end of runway 18. The pilot noticed an approaching concrete wall and decided to turn to the right. He then struck the concrete wall with airplane’s left wing. Post-accident examination of the airplane by an FAA inspector revealed substantial damage to the airplane’s left wing. Fuel was found in both wings and at the fuel strainer. The fuel was clear and blue, without any visible contaminants. The airplane’s engine was recovered and retained for further examination.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record ERA26LA244
Event ID
20260622203216
Case number
ERA26LA244
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: d87cfe3b5f4598a2543a3e45c2e9b04cb1306c1e43078841e4036d04f49384b9; retrieved 2026-09-17T05:11:33.128Z.