_Incident · Regulatory action_

# US Air Force awards AEVEX 0M contract for GPS-resistant autonomous strike drones

Canonical ID: `3cf4a58b-36dc-4610-8bac-2afb3886d9b5`

- **Occurred:** 2026-06-30
- **Kind:** `regulatory_action`
- **Status (derived):** active
- **Company:** [AEVEX Aerospace](/companies/aevex.md) (id: `ba358703-a726-4efe-9020-cdf6fa2a2b27`)

AEVEX Corp secured 0M US Air Force contract with 7M initial funding for GPS-resistant autonomous strike drones. One-way attack missions.

## Sources (1)

1. https://defence-blog.com/aevex-wins-50m-deal-for-gps-resistant-strike-drones/

## Status history

- **active** · 2026-07-03 · agent:depth

## Common questions

### What happened in US Air Force awards AEVEX 0M contract for GPS-resistant autonomous strike drones?

AEVEX Corp secured 0M US Air Force contract with 7M initial funding for GPS-resistant autonomous strike drones. One-way attack missions.

### When did this incident occur?

The incident is recorded as occurring on June 30, 2026 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.

### Who was involved in US Air Force awards AEVEX 0M contract for GPS-resistant autonomous strike drones?

The incident is recorded as involving AEVEX Aerospace on the DEPLOY registry. No specific robot model is linked to this incident in the registry.

### Has anyone responded to US Air Force awards AEVEX 0M contract for GPS-resistant autonomous strike drones?

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 US Air Force awards AEVEX 0M contract for GPS-resistant autonomous strike drones?

This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.


_API: GET /v1/incidents/3cf4a58b-36dc-4610-8bac-2afb3886d9b5 · sources: /v1/incidents/3cf4a58b-36dc-4610-8bac-2afb3886d9b5/sources · responses: /v1/incidents/3cf4a58b-36dc-4610-8bac-2afb3886d9b5/responses · status: /v1/incidents/3cf4a58b-36dc-4610-8bac-2afb3886d9b5/status · canonical URL: /incidents/regulatory-action-2026-06-30-aevex_