# NTSB ERA25LA237: Gyro Technic GT-VX2, N62XF, Swanzey, NH, June 23, 2025

- Type: NTSB accident investigation
- Classification: Accident · Minor injuries · Class 3 · Limited · Final report
- Date: June 23, 2025, 09:55 local (13:55 UTC)
- Place: Swanzey, NH
- Coordinates: 42.9065, -72.2726
- Nearby events: https://openairdocs.org/map.md?lat=42.9065&lon=-72.2726&mi=10
- Phase of flight: [Maneuvering](https://openairdocs.org/ntsb-phases/450) (OpenAirDocs' grouping)
- Defining event: [Maneuvering-low-alt flying: Miscellaneous/other](https://openairdocs.org/ntsb-events/900)
- Highest injury: Minor injuries
- Injuries: 1 minor
- Status: Completed, report October 21, 2026
- Report: Approved by Office Director
- Investigation class: Class 3
- NTSB office: Eastern Region Aviation
- Parties: Rotec Flight Safety Inc., FAA/FSDO
- NTSB case key (mKey): 200382
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA25LA237
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/200382/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=200382
- Page: https://openairdocs.org/ntsb/ERA25LA237

## Probable cause

The pilot’s failure to maintain rotor rpm of the gyroplane during a low approach, while distracted by other aircraft in the airport traffic pattern, which resulted in the pilot’s decision to perform an off-runway landing.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Attention/monitoring: attention](https://openairdocs.org/ntsb-findings/02021510): Personnel issues › Psychological · Pilot (probable cause); cases with it: [Mark C Timney GT-VX2, 1 case](https://openairdocs.org/ntsb-findings/02021510/cases.md?model=0564268), [All aircraft, 226 cases](https://openairdocs.org/ntsb-findings/02021510/cases.md)
- [Performance/control parameters: prop/rotor parameters](https://openairdocs.org/ntsb-findings/01062052): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Mark C Timney GT-VX2, 1 case](https://openairdocs.org/ntsb-findings/01062052/cases.md?model=0564268), [All aircraft, 182 cases](https://openairdocs.org/ntsb-findings/01062052/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Maneuvering-low-alt flying: Miscellaneous/other](https://openairdocs.org/ntsb-events/900) (defining event); cases with it: [Mark C Timney GT-VX2, 1 case](https://openairdocs.org/ntsb-events/900/sequence.md?model=0564268), [All aircraft, 1,556 cases](https://openairdocs.org/ntsb-events/900/sequence.md)
- [Emergency descent: Off-field or emergency landing](https://openairdocs.org/ntsb-events/440); cases with it: [Mark C Timney GT-VX2, 1 case](https://openairdocs.org/ntsb-events/440/sequence.md?model=0564268), [All aircraft, 3,365 cases](https://openairdocs.org/ntsb-events/440/sequence.md)
- [Landing: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Mark C Timney GT-VX2, 1 case](https://openairdocs.org/ntsb-events/470/sequence.md?model=0564268), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md)

## Analysis

The sport pilot of the gyroplane reported that he intended to complete two airport traffic pattern circuits over a runway. He planned to conclude the first circuit with a low approach over the runway and the second circuit with a full stop landing. The majority of the first circuit was uneventful; however, about halfway down the 4,001-ft-long runway during the low approach, when the pilot applied full throttle to climb, the gyroplane did not respond as he had expected. He then pitched forward to increase airspeed and rotor speed, but the gyroplane still would not climb. As his altitude became lower, the pilot decided to perform a forced landing to a grass area beyond the runway, during which the gyroplane’s empennage and main rotor were substantially damaged. Following the accident, the pilot stated that he was not sure if the engine was unable to produce full power, or if he allowed the gyroplane to “fall behind the power curve” as he was distracted looking for traffic utilizing a crossing runway. Data download from the gyroplane’s primary flight display, engine management system, and engine control unit were reviewed following the accident. The data did not reveal evidence of any preimpact mechanical malfunctions or failures and showed that just prior to the pilot terminating the climb attempt, the engine rpm was increasing while the rotor rpm was decreasing, consistent with the pilot’s statement that he may have let gyroplane get “behind the power curve”. During the impact sequence, there was a sudden increased in throttle position along with a rapid spike in engine rpm, beyond its maximum rated speed, likely due to the propeller blades shearing off and unloading resistance on the engine.

## Factual narrative

On June 23, 2025, about 0955 eastern daylight time, an experimental amateur-built Gyro Technic GT-VX2 gyroplane, N62XF, was substantially damaged when it was involved in an accident near Swansea, New Hampshire. The sport pilot sustained minor injuries. The gyroplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The sport pilot reported that he intended to complete two airport traffic pattern circuits on runway 32 at Dillan/Hopkins Airport (EEN), Keene, New Hampshire. He planned to conclude the first circuit with a low approach over the runway and the second circuit with a full stop landing. The first circuit was uneventful. During the low approach, while the gyroplane was near the mid-point of the 4,001-ft-long runway, about 50 ft above the runway, and at an airspeed about 50 mph, the pilot applied full throttle, but the gyroplane would not climb. He then pitched forward to increase airspeed and rotor speed, but the gyroplane would still not climb. As his altitude became lower, the pilot decided to perform a forced landing to a grass area beyond the runway, rather than the harder asphalt runway. During the landing, the gyroplane landed hard, bounced, and rolled over, coming to rest on its left side. The pilot further stated that he was not sure if the engine was unable to produce full power, or if he allowed the gyroplane to “fall behind the power curve” as he was also visually scanning for two airplanes in the airport traffic pattern that were utilizing runway 2. Postaccident examination of the gyroplane by a Federal Aviation Administration inspector revealed substantial damage to the empennage and main rotor blades. The gyroplane’s primary flight display (PFD), engine management system (EMS), and engine control unit (ECU) were retained for data download. Review of data downloaded from the ECU revealed that 18 minutes, 34 seconds elapsed from the time of engine start until impact. During that time, no errors, warnings, or abnormal parameters were logged that would have precluded normal operation of the engine. During climb on the accident flight, the throttle was advanced to 96.29% and the engine responded normally, reaching an rpm of 5,048.48. Just prior to the accident, the gyroplane’s descent lasted 2 minutes, 38 seconds. The pilot then reduced throttle position to 49% and the engine rpm decreased to 3,278. About 3 seconds later, the throttle position suddenly increased along with a rapid spike in engine rpm, beyond limits of 5,500, to 6,806. Review of data downloaded from the gyroplane’s PFD and EMS revealed that just prior to reduction in engine power for the forced landing, the engine power rpm was increasing while the rotor rpm was decreasing.

## Aircraft

- Registration: [N62XF](https://openairdocs.org/aircraft/N62XF), registered now, S/N VX2-008 (OpenAirDocs)
- Reported make and model: Gyro Technic GT-VX2 (NO SERIES)
- Registry model: [Mark C Timney GT-VX2](https://openairdocs.org/model/mark-c-timney-gt-vx2) (registry code 0564268) (OpenAirDocs)
- Category: Helicopter, amateur-built
- Serial number: VX2-008
- Year built: 2025
- Airframe hours: 3
- Engines: Rotax 912iS 100 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Airworthiness certificate: Special, Experimental light sport (Special)
- Airport: EEN, Dillant/Hopkins Airport, runway 32, 4,001 × 75 ft, asphalt
- Equipment: Electronic multifunction display

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 64; injuries: minor; sport pilot; airplane ratings: single-engine land; medical: sport pilot; last flight review March 8, 2024; seat: single; restraint: 4-point; flight hours: 455 total, 3 in this make and model, 384 as pilot in command, 16 in the last 90 days, 11 in the last 30 days, 1 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Day
- Wind: calm
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 81 °F, dew point 73 °F
- Altimeter: 30.08 inHg
- Observed at: EEN
- METAR: KEEN 231356Z AUTO 00000KT 10SM CLR 27/23 A3008

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20250623007139A](https://openairdocs.org/incident/20250623007139A), Jun 23, 2025: Mark C Timney GT-VX2, North Swanzey, NH, Destroyed. On 06-23-2025 at approximately 10:00 am, the operator of a homebuilt kit gyrocopter was flying into Dillant-Hopkins Airport near keene new hampshire on a low…

## Docket (6 files)

The files NTSB released with the investigation on October 21, 2026, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=200382. 7.6 MB in all.

- Pilot/operator aircraft accident report, NTSB form 6120.1 (item 1, PDF, 10 pages, 1.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19174853&FileExtension=pdf&FileName=6120_Redacted-Rel.pdf
- Investigation photographs (item 2, PDF, 4 pages, 3 photos, 945 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19175037&FileExtension=pdf&FileName=Investigation%20Photographs-Rel.pdf
- Rotax engine control unit investigation report (item 3, PDF, 11 pages, 3.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19622834&FileExtension=pdf&FileName=ERA25LA237%20ECU%20Investigation%20Report_Redacted-Rel.pdf
- Cockpit display - specialist's factual report (item 4, PDF, 11 pages, 7 photos, 1.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19770868&FileExtension=pdf&FileName=Cockpit%20Display%20-%20Specialist%27s%20Factual%20Report-Rel.pdf
- Cockpit display - specialist's factual report - attachment 1 (item 5, CSV, 95 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19771366&FileExtension=csv&FileName=Cockpit%20Display%20-%20Specialist%27s%20Factual%20Report%20Attachment%201-Rel.csv
- Cockpit display - specialist's factual report - attachment 2 (item 6, CSV, 89 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19771233&FileExtension=csv&FileName=Cockpit%20Display%20-%20Specialist%27s%20Factual%20Report%20Attachment%202-Rel.csv

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
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.