eFlight
Accidents · NTSB ERA26LA244 · Preliminary: the investigation is not finished

Cessna 182S accident near Naples, Florida, June 20, 2026

On June 20, 2026 at about 2:30 pm local time, a 1999 Cessna 182S, registered N7270H, was substantially damaged in an accident during takeoff (rejected takeoff) near Naples, Florida (Wing South Airpark airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 4 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
June 20, 2026 · about 2:30 pm local time · cases in 2026
Place
Naples, Florida · Wing South Airpark · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 4 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 182S, built 1999 · all 182Ss on the register
Registration
N7270H · registry record · serial 18280481
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative preliminary · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Runway excursion during takeoff (rejected takeoff) defining event

The aircraft

  • Airframe total time: 4,944.6 hours
  • Last inspection: 100-hour inspection, June 11, 2026; 7 hours since
  • Maximum gross weight: 3,100 lb
  • Seats: 4
  • Landing gear: fixed
  • Operator: Sundowners Inc.

The flight

  • Departed from: FA37 Naples FL at 6:30 pm
  • Destination: MTH Marathon FL
  • Flight plan: none
  • Runway 18, 4,400 ft by 100 ft

Weather at the time

  • Light: daylight
  • Wind: from 240° at 6 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 2,800 ft
  • Temperature: 90°F (32°C), dew point 75°F (24°C)
  • Altimeter: 30.04 inHg
  • Observation at 10:30 am from MKY, 7 miles away

Weather report (METAR): SPECI KMKY 201430Z AUTO 24006KT 10SM BKN028 BKN037 BKN043 32/24 A3004 RMK AO2 PNO $

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers3

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/ERA26LA244.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.

Aircraft

By kindModelsMakersEnginesFleetsWhat changed

Fly

Plan a flightAirportsLive mapRoutes and flightsFuels

Training and work

TrainingFlight schoolsGround schoolsPilot examinersMedical examinersJobs

Companies

DirectoryCharter operatorsFBOsRepair stationsClaim your listing

Safety and data

AccidentsRecords checkAnalyticsSAFxCHANGEThe graphAbout

Colours follow your device's light or dark setting.