The U.S. aircraft register, updated daily
Accidents · NTSB ERA25LA369 · Preliminary: the investigation is not finished

Amateur-built AR-1 accident near Fort Myers, Florida, September 28, 2025

On September 28, 2025 at about 2:00 pm local time, a 2016 amateur-built AR-1 (gyroplane), registered N107AR, was substantially damaged in an accident during initial climb near Fort Myers, Florida (Buckingham Fld airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 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 October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
September 28, 2025 · about 2:00 pm local time
Place
Fort Myers, Florida · Buckingham Fld · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Amateur-built AR-1 NO SERIES, built 2016
Registration
N107AR · registry record · serial 0009
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

On September 28, 2025, about 1000 EST, a Spicola AR-1 gyroplane, N107AR, was substantially damaged when it was involved in an accident at Buckingham Field Airport (FL59), Lehigh Acres, Florida. The commercial pilot and pilot-rated passenger were not injured. The gyroplane was operated as a Title 14?Code of Federal Regulations Part 91 personal flight.?  The pilot stated that prior to departure he added 7 gallons of 100 low lead fuel bringing the total fuel capacity to 14 gallons. After fueling he checked the fuel tank for contaminants and there were none. He also performed a preflight inspection with no discrepancies noted. As part of his briefing to the pilot-rated passenger he informed him how to enter and exit, to keep his hands free of all controls, and do not exit the gyroplane until the main rotor blades had stopped turning. He also informed him how to put and take off the passenger restraint system including the chest strap which most aircraft do not have and therefore most pilots are not accustomed to a chest strap. Weight and balance calculations showed the gyroplane was 37 pounds below design gross weight. After engine start he taxied to the approach end of the runway where he performed an engine run-up with no discrepancies reported. He then lined up at the end of runway 32, and with about 4,400 feet of runway available, pre rotated the main rotor to 200RPM, the higher end of the pre rotation speed due to my higher weight than solo, and released the brakes. He reported acceleration was fine and the engine RPM was 5700 and climbing, rotor speed was 250RPM and climbing. After rotation he pushed over to stay in ground effect and accelerate to the takeoff safety speed of 55 knots and started to climb at 60 knots indicated. The climb rate was good until approximately 100-150 feet above ground level, when a noticeable reduction in climb performance was observed. He ensured he had full throttle applied and visually checked that his left hand was full forward. He then checked that both electric fuel pumps were on, and there was no illumination of turbocharger caution or warning lights, the alternator lights were out, and that both magneto switches were on. He glanced at the engine RPM gauge and noticed it was reading around 5,100 RPM. It was at this time that he knew a forced landing was imminent and his primary concern was of my passenger and that he needed to maintain a proper airspeed above all else. He pushed the nose down to maintain 55 knots and realized that the flight was no longer high enough to clear the trees at the end of the runway and was still losing altitude. He surmised that there was not enough runway and overrun available to land straight ahead. The west side of the airport had a large field but with two retention ponds running 32/14. He kept the nose down maintaining 50-55 knots and made a left turn trying to get more available landing area and to avoid the trees. At approximately 20 ft he rolled level, flared, and landed between the ponds on the upslope of the bank of the first pond, which sheared the nose landing gear. The gyroplane entered the second pond and rolled over to the right coming to rest in about 2 to 3 ft of water. He extracted himself and then moved back to help extract the passenger who had already self-extracted. The gyroplane was recovered for further detailed examination of the engine.

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. Loss of engine power (partial) during initial climb defining event
  2. Off-field or emergency landing during emergency descent
  3. Dragged wing/rotor/float/other during landing (landing roll)

The aircraft

  • Seats: 2
  • Landing gear: fixed
  • Operator: Seven Alpha Romeo LLC

The flight

  • Flight plan: none
  • Runway 32, 4,416 ft by 75 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: a few clouds at 2,000 ft
  • Temperature: 88°F (31°C), dew point 75°F (24°C)
  • Altimeter: 29.89 inHg
  • Observation at 9:53 am from RSW, 8 miles away

Weather report (METAR): METAR KRSW 281453Z VRB05KT 10SM FEW020 31/24 A2989 RMK AO2 SLP118 T03110244 50004 $=

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

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.

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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.