# NOTAM & TFR Feed - Airports, Drone Areas, Changes Only (`prixodik/notam-tfr-feed`) Actor

Current NOTAMs for US and international airports from the FAA NOTAM system plus FAA Temporary Flight Restrictions (TFR) with areas and altitudes: parsed Q-codes, closures, obstacles, validity in UTC, TFRs near your drone sites and a changes-only mode.

- **URL**: https://apify.com/prixodik/notam-tfr-feed.md
- **Developed by:** [Milchenko Oleksii](https://apify.com/prixodik) (community)
- **Categories:** Travel, Developer tools
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 notam or tfrs

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

## NOTAM & TFR Feed: airport NOTAMs, drone-site TFRs and changes only

Get **current NOTAMs for the airports you care about and FAA Temporary Flight Restrictions (TFRs) near your sites** as clean, machine-readable records, ready for a spreadsheet, a dispatch dashboard, a drone-ops checklist or an AI agent:

- **Airport NOTAMs** from the FAA NOTAM system for US airports (KJFK, KLAX, 2W5 ...) and the **international NOTAMs** it distributes (EGLL, CYYZ, LFPG ...).
- **FAA TFRs** (security, VIP movements, wildfires and other hazards, UAS public gatherings, space operations) with their **areas, altitudes and times**, filtered by state, type or **distance from your drone job sites**.

Built for drone operators (Part 107 asks you to check local airspace and any flight restrictions before every flight), flight schools, charter and business-aviation dispatch, flight-ops teams and developers of EFB, ops and drone software.

### What you get for each NOTAM

- `qCode` and a plain `category`: `runway`, `taxiway`, `apron`, `aerodrome`, `obstacle`, `navaid`, `airspace`, `uas`, `procedure`, `lighting`, `services`, `other`
- `closed` = true for closures (Q-code condition LC or "CLSD" in the text)
- `validFrom` / `validTo` in ISO 8601 UTC, `permanent`, `estimatedEnd` (EST), `schedule` (item D)
- `lowerFt` / `upperFt`, `lat` / `lon`, `radiusNm` from the ICAO Q-line
- `text` (clean plain text) and `icaoText` (full ICAO format when published)

Example (real record from our tests):

```json
{
  "recordKey": "NOTAM:KJFK:12/171",
  "location": "KJFK",
  "category": "taxiway",
  "closed": true,
  "qCode": "QMXLC",
  "validFrom": "2025-12-10T19:44:00Z",
  "validTo": null,
  "permanent": true,
  "text": "TWY PB BTN HANGAR 12 RAMP AND TWY Q CLSD",
  "change": "new"
}
```

### What you get for each TFR

- `tfrType`, `regulation` (for example `91.137(a)(2)` for firefighting), `tfrReason`, `state`, `facility`
- `areas`: every area with lower and upper limits (value, unit, reference MSL/AGL/FL and feet), times, circle (centre and radius) and polygon coordinates
- `distanceNm` from your nearest `tfrNear` site (0 = the site is inside the TFR) and `matchedWatch` with the site labels

### Changes-only mode

With `mode: changes` and a `stateStoreId`, each run returns only:

- `new` NOTAMs and TFRs,
- `updated` ones (with `changedFields`, for example `validTo` when an end time is extended),
- `removed` ones that are no longer published (cancelled, replaced or expired).

Records already delivered are not delivered or charged again. Schedule the Actor every hour or before each shift and send the output to e-mail, Slack or your own system.

### Input

| Field | Description |
|---|---|
| `locations` | Up to 50 ICAO or FAA identifiers. Empty = TFRs only |
| `categories` | Optional NOTAM category filter |
| `activeWithinHours` | Keep only records in force now or starting within N hours |
| `includeTfr` | Add FAA TFRs (default `true`) |
| `tfrNear` | Up to 50 sites: `lat`, `lon`, `radiusNm` (default 5), optional `label` |
| `tfrStates`, `tfrTypes` | Optional TFR filters |
| `mode`, `stateStoreId` | `snapshot`, or `changes` with a named store |
| `maxRecords`, `maxPagesPerLocation`, `maxTfrDetails` | Limits (defaults 2000, 20 pages of 30 NOTAMs, 200 TFRs) |
| `proxyConfiguration` | Apify Proxy (datacenter) by default |

Drone operator example:

```json
{
  "locations": ["KORL", "KMCO"],
  "activeWithinHours": 24,
  "tfrNear": [{ "label": "Lake Buena Vista job", "lat": 28.39, "lon": -81.54, "radiusNm": 10 }],
  "mode": "changes",
  "stateStoreId": "orlando-drone-ops"
}
```

### Pricing

- **$0.003 per delivered NOTAM or TFR**, plus $0.005 per run start.
- In `changes` mode you pay only for new, updated and removed records.
- A run fails without delivering anything if a source cannot be read or a location is unknown, so you never receive a partial feed that looks complete.

### Data sources

- FAA NOTAM Search (notams.aim.faa.gov), including international NOTAMs distributed through the FAA system.
- FAA TFR list and TFR detail files (tfr.faa.gov).

Both are U.S. Government works. The FAA NOTAM Search does not answer cloud container addresses directly, so the Actor reads it through Apify Proxy (datacenter); no CAPTCHA or login is involved.

### Important

**This feed is for planning, monitoring and automation. It is not an official pre-flight briefing.** Before every flight obtain an official briefing (for example 1800wxbrief.com, the FAA NOTAM Search, B4UFLY or your national AIS) and follow your approved procedures. A NOTAM or TFR missing from the feed does not mean that no restriction applies. Times and limits are as published by the FAA; categories are derived from the Q-code or keyword and may not capture every detail of the text.

### Limits

- NOTAMs are read per location. FDC NOTAMs that are not tied to the locations you list, and NOTAMs of countries that do not distribute them to the FAA system, are not included.
- Locations with more NOTAMs than `maxPagesPerLocation` allows are read partially; the `SUMMARY` record lists them in `truncatedLocations`, and they never produce `removed` records.
- `tfrNear` distances use the published TFR polygon or circle; a TFR without geometry is not matched to sites.

# Actor input Schema

## `locations` (type: `array`):

Up to 50 ICAO or FAA location identifiers, for example KJFK, KLAX, 2W5, EGLL, CYYZ. Current NOTAMs are read from the FAA NOTAM system, which also carries international NOTAMs. Leave empty to receive TFRs only.

## `categories` (type: `array`):

Optional filter for airport NOTAMs. Empty means all categories. Categories come from the ICAO Q-code, or from the FAA keyword for domestic NOTAMs without a Q-line.

## `activeWithinHours` (type: `integer`):

Keep only NOTAMs and TFRs that are in force now or start within this many hours (1-8760). Empty keeps everything currently published, including future ones.

## `includeTfr` (type: `boolean`):

Add FAA Temporary Flight Restrictions (security, VIP, hazards and firefighting, UAS public gatherings, space operations) with their areas, altitudes and times.

## `tfrNear` (type: `array`):

Up to 50 points with lat, lon, radiusNm (default 5) and an optional label, for example drone job sites. Only TFRs whose area lies within the radius are returned, with the distance in nautical miles (0 = the point is inside). Empty = no distance filter.

## `tfrStates` (type: `array`):

Optional list of US state codes (for example CA, FL, DC). Empty = all states.

## `tfrTypes` (type: `array`):

Optional filter by FAA TFR type. Empty = all types.

## `mode` (type: `string`):

snapshot returns every current NOTAM and TFR. changes returns only records that are new, changed or removed (cancelled or expired) since the previous run with the same state store and filters.

## `stateStoreId` (type: `string`):

Named key-value store that remembers what was already delivered. Required for changes mode. Letters, digits and hyphens.

## `maxRecords` (type: `integer`):

Upper limit on delivered records in this run (1-10000).

## `maxPagesPerLocation` (type: `integer`):

The FAA system returns 30 NOTAMs per page. Busy airports such as KJFK publish 150-200 NOTAMs (5-7 pages). Default 20 pages = 600 NOTAMs.

## `maxTfrDetails` (type: `integer`):

Upper limit on TFR detail files read in one run (0-500). The run fails with an explanation if more TFRs match your state and type filters.

## `proxyConfiguration` (type: `object`):

The FAA NOTAM Search does not answer the cloud container address directly, so Apify Proxy (datacenter) is used by default.

## Actor input object example

```json
{
  "locations": [
    "KJFK",
    "EGLL",
    "CYYZ"
  ],
  "categories": [],
  "includeTfr": true,
  "tfrNear": [
    {
      "label": "Disney World job site",
      "lat": 28.4177,
      "lon": -81.5812,
      "radiusNm": 10
    }
  ],
  "tfrStates": [],
  "tfrTypes": [],
  "mode": "snapshot",
  "maxRecords": 2000,
  "maxPagesPerLocation": 20,
  "maxTfrDetails": 200,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

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

No description

## `summary` (type: `string`):

No description

# 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 = {
    "locations": [
        "KJFK",
        "EGLL",
        "CYYZ"
    ],
    "tfrNear": [
        {
            "label": "Disney World job site",
            "lat": 28.4177,
            "lon": -81.5812,
            "radiusNm": 10
        }
    ],
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("prixodik/notam-tfr-feed").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 = {
    "locations": [
        "KJFK",
        "EGLL",
        "CYYZ",
    ],
    "tfrNear": [{
            "label": "Disney World job site",
            "lat": 28.4177,
            "lon": -81.5812,
            "radiusNm": 10,
        }],
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("prixodik/notam-tfr-feed").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 '{
  "locations": [
    "KJFK",
    "EGLL",
    "CYYZ"
  ],
  "tfrNear": [
    {
      "label": "Disney World job site",
      "lat": 28.4177,
      "lon": -81.5812,
      "radiusNm": 10
    }
  ],
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call prixodik/notam-tfr-feed --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,prixodik/notam-tfr-feed"
        }
    }
}
```

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/SF8EzzryDIPXBHhQ7/builds/aHaUQ8jPipHzBdfCA/openapi.json