_Incident · Regulatory action_

# FAA grants aircraft-agnostic BVLOS waiver for Vantis network across 5,000 square miles

Canonical ID: `f4083a68-ca80-48ba-b639-64ae5ed22f72`

- **Occurred:** 2026-06-02
- **Kind:** `regulatory_action`
- **Status (derived):** active
- **Company:** [Vantis](/companies/vantis.md) (id: `0448f277-f312-4a43-b02b-de7cd909fe18`)

FAA issued an aircraft-agnostic BVLOS waiver enabling Frontier Precision to fly any NDAA-compliant drone under 55 pounds across 5,000+ square miles of North Dakota via the Vantis network.

## Sources (1)

1. https://dronelife.com/2026/06/02/vantis-bvlos-system-adds-new-partner-faa-waiver-across-5000-square-miles/

## Status history

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

## Common questions

### What happened in FAA grants aircraft-agnostic BVLOS waiver for Vantis network across 5,000 square miles?

FAA issued an aircraft-agnostic BVLOS waiver enabling Frontier Precision to fly any NDAA-compliant drone under 55 pounds across 5,000+ square miles of North Dakota via the Vantis network.

### When did this incident occur?

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

### Who was involved in FAA grants aircraft-agnostic BVLOS waiver for Vantis network across 5,000 square miles?

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

### Has anyone responded to FAA grants aircraft-agnostic BVLOS waiver for Vantis network across 5,000 square miles?

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 FAA grants aircraft-agnostic BVLOS waiver for Vantis network across 5,000 square miles?

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


_API: GET /v1/incidents/f4083a68-ca80-48ba-b639-64ae5ed22f72 · sources: /v1/incidents/f4083a68-ca80-48ba-b639-64ae5ed22f72/sources · responses: /v1/incidents/f4083a68-ca80-48ba-b639-64ae5ed22f72/responses · status: /v1/incidents/f4083a68-ca80-48ba-b639-64ae5ed22f72/status · canonical URL: /incidents/regulatory-action-2026-06-02-vantis_