# FAA Drone Data: Part 107 Waivers (BVLOS) & FRIA Sites (`johto.data/faa-drone-data`) Actor

Official FAA drone data: Part 107 waivers (company, waived rules like BVLOS 107.31, over people 107.39, night, altitude, PDF link, effective-from/until dates, status upcoming or in effect) plus FRIA Remote ID sites. Filter by rule, keyword, state, date. $0.002/record.

- **URL**: https://apify.com/johto.data/faa-drone-data.md
- **Developed by:** [Jo](https://apify.com/johto.data) (community)
- **Categories:** Lead generation, Agents, MCP servers
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## FAA Drone Data – Part 107 Waivers & FRIA Remote ID Sites

**Every Part 107 drone waiver on FAA's list in one dataset, in effect or upcoming, with a `status` field.** Company, waived rules (BVLOS, over people, altitude) and the signed PDF, plus all FRIA Remote ID sites.

Docs and samples: https://johtodata.com/docs/faa-drone-data/

**Quick start:** click **Start**. The prefilled input returns real results in about a minute for a few cents. New Apify accounts include free monthly credits, so your first runs are effectively free.

The definitive **official FAA drone dataset** in clean JSON:

- **Part 107 waivers:** every waiver on FAA's list (in effect or upcoming) with **company name, waiver number, waived rules, effective-from and expiration dates, a status (upcoming / in effect / expired), and a link to the signed waiver PDF**. Companies holding BVLOS (107.31), over-people (107.39), multiple-drone (107.35), altitude (107.51) or moving-vehicle (107.145) waivers are the most advanced commercial drone operators in the U.S.
- **FRIA sites:** all FAA-Recognized Identification Areas (where drones may fly without Remote ID), with organization, address, dates and coordinates.

### For AI agents

**Questions this answers:**

- Which companies hold FAA BVLOS waivers that take effect this year?
- List FRIA drone flying sites in Texas
- Who holds Part 107 over-people waivers?

**Call it when:**

- The user wants companies holding a specific Part 107 waiver (107.31 BVLOS, 107.39 over people, 107.29 night, 107.51(b) altitude).
- The user wants waivers that take effect on or after a date (`issuedAfter` filters on `effectiveFrom`), waivers by status (upcoming / in_effect / expired), or FRIA sites by state.

**Don't call it when:**

- Airspace / LAANC / no-fly checks for a location (different data; see malonestar/faa-drone-airspace-checker).
- NOTAM/TFR data.
- Individual pilot certificate lookups.

No like-for-like Store Actor was found on 2026-10-22 (Store search 'faa drone' returned an airspace checker and a NOTAM feed). Use those instead for airspace or NOTAM questions; use this one for waiver holders and FRIA sites.

**Input - Non-expired BVLOS waivers taking effect in 2026 or later:**

```json
{"datasets": ["waivers"], "regulations": ["107.31"], "issuedAfter": "2026-01-01", "activeOnly": true, "maxItems": 25}
```

**Input - FRIA sites:**

```json
{"datasets": ["fria"], "maxItems": 50}
```

**Output:** one dataset row per record. Real row from run `ETlLTWKUnRk9eKe6i` (long lists trimmed, named people redacted):

```json
{
 "dataset": "part107_waiver",
 "waiverNumber": "107W-2026-02718",
 "companyName": "Airloom Inc",
 "responsiblePerson": "<redacted in README: named person/contact from public filing>",
 "waivedRegulations": ["107.51(b)"],
 "effectiveFrom": "2026-12-10",
 "effectiveUntil": "2027-01-31",
 "status": "upcoming",
 "effectiveNow": false,
 "issueDate": "2026-12-10",
 "expirationDate": "2027-01-31",
 "active": true,
 "documentUrl": "https://www.faa.gov/sites/faa.gov/files/107W-2026-02718-Jason-R-Johnson-CoW.pdf",
 "sourceUrl": "https://www.faa.gov/uas/commercial_operators/part_107_waivers/waivers_issued?page=0"
}
```

**Price:** $0.002 per record (event `record`) + $0.00005 per run start.

**Limits:**

- FAA's 'Date of Issuance' column is the date a waiver **takes effect**, not the signing date (PDF for 107W-2026-02718: "effective from December 10, 2026, to January 31, 2027", signed 2026-10-14). So `effectiveFrom` is often in the future. Use `status` / `effectiveNow` for "in effect today". `issueDate` / `expirationDate` are deprecated aliases with the same values.
- `active: true` means not expired, so it includes upcoming waivers. `activeOnly: true` keeps upcoming waivers too.
- Waiver holders are companies or individuals; responsiblePerson is a named person.
- Default maxItems 10 (an empty-input call is a cheap sample); raise it for the full list.

**Call it:** MCP `https://mcp.apify.com/?tools=johto.data/faa-drone-data` (tool `johto-dot-data--faa-drone-data`), or `POST https://api.apify.com/v2/acts/johto.data~faa-drone-data/run-sync-get-dataset-items` with `Authorization: Bearer <APIFY_TOKEN>` and the JSON input.
**Agent pays with USDC (x402), no Apify account:** `https://mcp.apify.com/?tools=johto.data/faa-drone-data&payment=x402`

**Quick, cheap first call:** An empty-input call returns 10 Part 107 waiver records: about $0.02 ($0.00005 start + 10 x $0.002).

### Who uses it

Drone-insurance and drone-hardware sales teams, **drone-show / inspection / delivery market research**, counter-UAS and airspace startups, investors, journalists, and **AI agents** answering "who is authorized to fly BVLOS in the U.S.?"

### Pricing

**$0.002 per record.** The full waiver list (~2,200 records) costs about $4.50.

### Input example

```json
{ "datasets": ["waivers"], "regulations": ["107.31", "107.39"], "issuedAfter": "2026-01-01", "maxItems": 500 }
```

### Output example

```json
{ "dataset": "part107_waiver", "waiverNumber": "107W-2026-02528", "companyName": "Sky Elements LLC", "responsiblePerson": "<redacted>",
  "waivedRegulations": ["107.51(b)"], "effectiveFrom": "2026-12-05", "effectiveUntil": "2026-12-31", "status": "upcoming", "effectiveNow": false,
  "issueDate": "2026-12-05", "expirationDate": "2026-12-31", "active": true,
  "documentUrl": "https://www.faa.gov/sites/faa.gov/files/107W-2026-02528-<redacted>-CoW.pdf" }
```

### Sources

- FAA "Part 107 Waivers Issued" (faa.gov), a public U.S. government page.
- FAA UAS Data Delivery System (ArcGIS FeatureServer, FAA_Recognized_Identification_Areas).

Dates are exactly as FAA publishes them. FAA's "Date of Issuance" column is the date a waiver **takes effect** (each signed PDF says "effective from ... to ..."; it was signed earlier), so it is often in the future. This Actor returns it as `effectiveFrom` (with `effectiveUntil` for the expiration date) and adds `status`: `upcoming`, `in_effect` or `expired`. `issueDate` and `expirationDate` are kept as aliases with the same values. `active` means not expired, so it includes upcoming waivers.

### Scheduled alerts and only-new mode

- **`onlyNew: true`** remembers what earlier runs returned (stored in your own Apify account) and returns **only new records**, so a daily or hourly schedule charges you only for fresh data.
- **`webhookUrl`** POSTs every new batch as JSON with a ready-to-post `text` and `content` summary. It works with Slack and Discord incoming webhooks, Zapier, Make and n8n.

### Use from AI agents and code

- **Apify MCP server:** add `johto.data/faa-drone-data` as a tool. Every input field is documented in the input schema.
- **REST, one call, returns JSON:**

```bash
curl -X POST "https://api.apify.com/v2/acts/johto.data~faa-drone-data/run-sync-get-dataset-items?token=YOUR_TOKEN" \
  -H 'Content-Type: application/json' -d '{"maxItems": 50, "onlyNew": true}'
```

- **Python:** `ApifyClient(token).actor("johto.data/faa-drone-data").call(run_input={...})`

# Actor input Schema

## `datasets` (type: `array`):

Which official FAA datasets to return.

## `issuedAfter` (type: `string`):

YYYY-MM-DD. Waivers: effectiveFrom date (FAA's 'Date of Issuance' column, which is when the waiver takes effect). FRIA: start date. Empty = all.

## `regulations` (type: `array`):

Waived Part 107 sections to keep, e.g. \["107.31"] (BVLOS), \["107.39"] (over people), \["107.29"] (night), \["107.51(b)"] (altitude). Empty = all.

## `keywords` (type: `array`):

Match company/person (waivers) or site/organization/city (FRIA).

## `states` (type: `array`):

Two-letter states for FRIA sites. Empty = all.

## `activeOnly` (type: `boolean`):

Skip expired waivers/sites. Waivers that are not yet in effect (status 'upcoming') are kept.

## `maxItems` (type: `integer`):

Maximum records; each is one charged result ($0.002). Default 10 keeps an empty-input call a cheap sample; raise it for the full list.

## `onlyNew` (type: `boolean`):

Remember results across runs (per account) and return only items not seen before. Ideal for scheduled runs: you pay only for new records.

## `webhookUrl` (type: `string`):

Optional. POSTs the new items as JSON with a 'text'/'content' summary (Slack, Discord, Zapier, Make, n8n compatible).

## Actor input object example

```json
{
  "datasets": [
    "waivers"
  ],
  "issuedAfter": "",
  "regulations": [
    "107.31"
  ],
  "keywords": [],
  "states": [],
  "activeOnly": true,
  "maxItems": 25,
  "onlyNew": false
}
```

# Actor output Schema

## `results` (type: `string`):

One item per record.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "datasets": [
        "waivers"
    ],
    "regulations": [
        "107.31"
    ],
    "maxItems": 25
};

// Run the Actor and wait for it to finish
const run = await client.actor("johto.data/faa-drone-data").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "datasets": ["waivers"],
    "regulations": ["107.31"],
    "maxItems": 25,
}

# Run the Actor and wait for it to finish
run = client.actor("johto.data/faa-drone-data").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "datasets": [
    "waivers"
  ],
  "regulations": [
    "107.31"
  ],
  "maxItems": 25
}' |
apify call johto.data/faa-drone-data --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,johto.data/faa-drone-data"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/055TZGQGLRrRpeNo1/builds/QTT4ID2g5H9I3WcWi/openapi.json