DEPLOYDatabase

Incident · Malfunction

Skyfly Axe VCA prototype G-SFAX suffers hard landing at Turweston Aerodrome during test flight, substantial damage

On April 22, 2025, the Skyfly Technologies Axe VCA prototype G-SFAX (MSN 001) suffered substantial damage in a hard landing at Turweston Aerodrome, Buckinghamshire, during a test flight. The aircraft suddenly rolled left and pitched down due to loss of power to two motors on the same side, creating thrust asymmetry.

The pilot selected all motors to idle to recover controlled flight, then was forced into a glide approach. The aircraft landed hard, short of the runway threshold and close to another aircraft. No injuries reported.

AAIB conducted a Record Only investigation. The aircraft was deregistered from the UK (27 June 2025) and transferred to the USA, reportedly repaired/rebuilt as N250EV, and resumed flight testing in the USA from mid-October 2025.

Occurred 2025-04-22 · Axe · Skyfly · Drones

How to read this record

Incident records on DEPLOY are compiled from public sources (regulatory filings, news reports, and operator disclosures) and reflect what has been reported and tracked to date. They are not legal findings, determinations of fault, or safety ratings, and may be updated as new information is verified. See the sources below for the underlying references.
Track Skyfly Axe VCA prototype G-SFAX suffers hard landing at Turweston Aerodrome during test flight, substantial damage

Machine-readable surfaces

Sources (1)

  1. Aviation Safety Network · https://aviation-safety.net/wikibase/566810 · 2025-04-22

Status history

  • Active · 2026-08-18 · agent:recon

Common questions

What happened in Skyfly Axe VCA prototype G-SFAX suffers hard landing at Turweston Aerodrome during test flight, substantial damage?
On April 22, 2025, the Skyfly Technologies Axe VCA prototype G-SFAX (MSN 001) suffered substantial damage in a hard landing at Turweston Aerodrome, Buckinghamshire, during a test flight. The aircraft suddenly rolled left and pitched down due to loss of power to two motors on the same side, creating thrust asymmetry. The pilot selected all motors to idle to recover controlled flight, then was forced into a glide approach. The aircraft landed hard, short of the runway threshold and close to another aircraft. No injuries reported. AAIB conducted a Record Only investigation. The aircraft was deregistered from the UK (27 June 2025) and transferred to the USA, reportedly repaired/rebuilt as N250EV, and resumed flight testing in the USA from mid-October 2025.
When did this incident occur?
The incident is recorded as occurring on April 22, 2025 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
What robot was involved in Skyfly Axe VCA prototype G-SFAX suffers hard landing at Turweston Aerodrome during test flight, substantial damage?
Axe is the recorded robot involved in this incident.
Has anyone responded to Skyfly Axe VCA prototype G-SFAX suffers hard landing at Turweston Aerodrome during test flight, substantial damage?
No responses to this incident are recorded on the DEPLOY registry. Operators, manufacturers, or affected parties can submit responses to the editorial team; absence is not a guarantee no response was issued.
What is the current status of Skyfly Axe VCA prototype G-SFAX suffers hard landing at Turweston Aerodrome during test flight, substantial damage?
This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Unreviewed · 1 source (no primary) · last reviewed 2026-08-18

Verification posture

Unreviewed

Low confidence

Review state

Stable

Last reviewed 2026-08-18

Sources by quality tier

1
unclassified
Unclassified source

The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.

Methodology surface for Skyfly Axe VCA prototype G-SFAX suffers hard landing at Turweston Aerodrome during test flight, substantial damage.

Deploy Watch

Track this incident.

We notify you when the regulator updates the record, the remedy status changes, or a related incident surfaces.

Canonical ID c13322cb-75f9-42db-ba81-60da573362b2