ERA25LA369 · Gregory A Spicola AR-1
Seven Alpha Romeo Gregory A Spicola AR-1 · Accident: loss of engine power (partial) during initial climb
Event
- NTSB case
- ERA25LA369
- 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
- Event fatalities
- Unknown
- Ground fatalities
- Unknown
- 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
Gregory A Spicola AR-1
- Aircraft type
- Gregory A Spicola AR-1
- Category
- Gyroplane
- 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
- N107AR
- Operator
- Seven Alpha Romeo
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 9 years (built 2016)
- 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
- Initial climb
- 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
- Loss of engine power (partial)
- 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 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.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record ERA25LA369
- Event ID
- 20250929201742
- Case number
- ERA25LA369
- 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: 326c8f0367c7be37a5bad98cc7ba238a5faef7f5480305eefbc472c12c5786ac; retrieved 2026-09-16T20:23:47.063Z.