# FAA Airport Delays Scraper (`automation-lab/faa-nas-status-airport-delays-scraper`) Actor

Export current FAA NAS airport delays, closures, ground stops, advisories, runway configurations, and timing from official FAA feeds.

- **URL**: https://apify.com/automation-lab/faa-nas-status-airport-delays-scraper.md
- **Developed by:** [Stas Persiianenko](https://apify.com/automation-lab) (community)
- **Categories:** Travel
- **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.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## FAA Airport Delays Scraper

Export current **FAA airport delays**, closures, ground stops, air traffic advisories, and runway configurations from the official National Airspace System status feeds.

The Actor converts the FAA's live airport event payload into flat, typed dataset rows that are ready for spreadsheets, dashboards, scheduled monitoring, APIs, and automation workflows.

### What does FAA Airport Delays Scraper do?

The Actor requests the public FAA NAS airport events endpoint and returns one row for every active event exposed by the feed.

Supported event categories include:

- ground stops;
- ground delay programs;
- airport closures;
- free-form operational advisories;
- arrival delays;
- departure delays;
- runway configurations and arrival rates;
- deicing events.

Each result keeps the normalized fields needed for analysis and the original FAA event object for advanced use.

No FAA account, API key, browser, or proxy is required.

### Who is it for?

**Airline and airport operations teams** can monitor active restrictions and traffic-management programs.

**Travel intelligence teams** can enrich disruption dashboards with FAA reasons and timing.

**Data analysts** can collect repeatable snapshots for operational research.

**Developers** can consume a stable JSON contract instead of parsing changing source payloads themselves.

**Automation teams** can schedule the Actor and trigger downstream alerts when the current event set changes.

This Actor reports airport-level NAS advisories. It does not predict individual flight arrival times or provide airline itinerary status.

### Why use this Actor?

- Uses official anonymous FAA structured endpoints.
- Emits one normalized row per event rather than one deeply nested airport object.
- Includes stable event IDs where the FAA provides them.
- Preserves timing, reasons, delay minutes, runway data, and advisory links.
- Supports airport-code and event-type filters.
- Includes the official XML feed update time when available.
- Retries transient upstream failures and fails clearly on invalid authoritative data.
- Runs with a lightweight 256 MB HTTP configuration.

### What data can I extract?

| Field | Meaning |
| --- | --- |
| `eventId` | FAA event ID, or a deterministic fallback ID |
| `airportCode` | FAA/IATA/ICAO code exposed by the source |
| `airportName` | Airport long name when present |
| `eventType` | Normalized FAA event category |
| `reason` | Operational reason or impacting condition |
| `details` | Advisory text or status detail |
| `startTime` | Event start time when present |
| `endTime` | Event end time when present |
| `updatedAt` | Latest event/source timestamp |
| `issuedAt` | Advisory issue time when present |
| `averageDelayMinutes` | Average delay reported by FAA |
| `maximumDelayMinutes` | Maximum delay reported by FAA |
| `arrivalRate` | Published airport arrival rate |
| `arrivalRunways` | Current arrival runway configuration |
| `departureRunways` | Current departure runway configuration |
| `advisoryUrl` | Detailed FAA advisory link when available |
| `feedUpdatedAt` | Update time from the FAA status feed |
| `latitude`, `longitude` | Airport coordinates when present |
| `sourceUrl` | Official FAA source endpoint |
| `fetchedAt` | Time this Actor fetched the data |
| `rawEvent` | Original event object for advanced fields |

Fields that are not relevant to an event type are returned as `null`.

### How to run the Actor

1. Open the Actor in Apify Console.
2. Leave the airport list empty for all active airports, or add selected codes.
3. Select the event categories needed by your workflow.
4. Choose a maximum result count between 1 and 500.
5. Click **Start**.
6. Open the Dataset tab to view, download, or integrate the rows.

The default input collects up to 100 current events across all supported categories.

### Input parameters

#### `airports`

Optional list of 3- or 4-character airport codes.

Matching is case-insensitive.

Examples: `SFO`, `JFK`, `KJFK`.

Leave the list empty to include every airport returned by the current FAA feed.

#### `eventTypes`

Optional list of normalized categories.

Available values are `groundStop`, `groundDelay`, `airportClosure`, `freeForm`, `arrivalDelay`, `departureDelay`, `airportConfig`, and `deicing`.

All categories are used when the field is omitted.

#### `maxItems`

Maximum matching records to save.

The minimum is 1 and the maximum is 500.

The limit is applied after airport and event-type filters.

### Input examples

Collect all active delay and closure advisories:

```json
{
  "eventTypes": [
    "groundStop",
    "groundDelay",
    "airportClosure",
    "freeForm",
    "arrivalDelay",
    "departureDelay"
  ],
  "maxItems": 100
}
```

Collect current operational programs for selected airports:

```json
{
  "airports": ["SFO", "JFK", "EWR"],
  "eventTypes": ["groundStop", "groundDelay"],
  "maxItems": 50
}
```

Collect runway configuration records:

```json
{
  "eventTypes": ["airportConfig"],
  "maxItems": 100
}
```

### Output example

A current ground delay program is normalized like this:

```json
{
  "eventId": "0ebec647-5b3d-4d09-8325-5e1bef4382a9",
  "airportCode": "SFO",
  "airportName": "San Francisco International",
  "eventType": "groundDelay",
  "reason": "low ceilings",
  "details": "low ceilings",
  "startTime": "2026-08-18T15:30:00Z",
  "endTime": "2026-08-18T19:59:00Z",
  "updatedAt": "2026-08-18T12:29:08Z",
  "averageDelayMinutes": 42,
  "maximumDelayMinutes": 89,
  "feedUpdatedAt": "2026-08-18T14:04:30.000Z",
  "sourceUrl": "https://nasstatus.faa.gov/api/airport-events",
  "fetchedAt": "2026-08-18T14:05:00.000Z"
}
```

The live dataset may contain different airports and event types because FAA advisories change throughout the day.

### How much does it cost to export FAA airport delays?

This is a pay-per-event Actor.

Each run has a one-time **$0.001 start fee**.

Each saved advisory is charged through the `item` event. The current BRONZE rate is **$0.00144 per record**, with lower per-record prices on higher Apify plans.

At the BRONZE rate:

- 10 records cost approximately $0.0154 including the start fee;
- 25 records cost approximately $0.037 including the start fee;
- 100 records cost approximately $0.145 including the start fee.

You are charged only for normalized records saved to the dataset. An empty result has no item charge, although the start fee still applies.

### Monitoring and automation workflows

Schedule the Actor every 5, 15, or 30 minutes to capture current NAS conditions.

Use stable event IDs to compare snapshots and identify new, updated, or removed events.

Send selected event types into Slack, email, a webhook, or an incident-management system.

Export results to Google Sheets for an operations watchlist.

Load datasets into a warehouse for historical analysis.

Use `airportCode` and `eventType` as dashboard dimensions.

Apify schedules and integrations are configured outside this Actor; the Actor itself returns the current source snapshot.

### Download and integration options

Dataset results can be downloaded as JSON, CSV, Excel, XML, or RSS through Apify.

Typical destinations include:

- Google Sheets;
- Make;
- Zapier;
- webhooks;
- Python and JavaScript pipelines;
- BI tools and data warehouses.

Use the Dataset API to retrieve only the columns required by your application.

### Run with the Apify API

Replace `APIFY_TOKEN` with your token.

#### cURL

```bash
curl -X POST \
  "https://api.apify.com/v2/acts/automation-lab~faa-nas-status-airport-delays-scraper/runs?token=APIFY_TOKEN&waitForFinish=120" \
  -H "Content-Type: application/json" \
  -d '{"eventTypes":["groundStop","groundDelay"],"maxItems":100}'
```

#### JavaScript

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

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/faa-nas-status-airport-delays-scraper').call({
  eventTypes: ['groundStop', 'groundDelay'],
  maxItems: 100,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);
```

#### Python

```python
from apify_client import ApifyClient

client = ApifyClient(token="APIFY_TOKEN")
run = client.actor("automation-lab/faa-nas-status-airport-delays-scraper").call(
    run_input={"eventTypes": ["groundStop", "groundDelay"], "maxItems": 100}
)
items = client.dataset(run["defaultDatasetId"]).list_items().items
print(items)
```

### Use through Apify MCP

Add the Actor to Claude Code:

```bash
claude mcp add --transport http apify \
  "https://mcp.apify.com?tools=automation-lab/faa-nas-status-airport-delays-scraper"
```

#### Claude Desktop, Cursor, and VS Code setup

Desktop and editor clients can use this MCP configuration:

```json
{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=automation-lab/faa-nas-status-airport-delays-scraper"
    }
  }
}
```

Example prompts:

- “Export current FAA ground stops and summarize the affected airports.”
- “Check current FAA airport closures and return their start and end times.”
- “Get current runway configurations and arrival rates from the FAA feed.”

### Freshness, limits, and failure behavior

Results are a snapshot of what the official FAA source exposes when the run executes.

The Actor does not manufacture events for airports with no current advisory.

A filtered run can therefore succeed with zero records.

The authoritative JSON endpoint is retried for transient network, HTTP 429, and server errors.

If that endpoint remains unavailable or returns an invalid shape, the run fails rather than returning stale data.

The supplemental XML feed is used only for `feedUpdatedAt`; its temporary failure leaves that field null without discarding valid JSON events.

The Actor does not provide historical records unless you schedule runs and retain their datasets.

### Legality

FAA NAS status information is public operational data.

Review the FAA source terms and Apify's acceptable-use requirements before operating a production workflow.

Do not present this dataset as a safety guarantee, official dispatch instruction, or substitute for NOTAM, airline, airport, or air traffic control channels.

Operational decisions should be confirmed with authoritative aviation sources.

Avoid collecting or combining data in ways that violate applicable laws or contractual obligations.

### Troubleshooting

**Why is my dataset empty?**

The selected airport or event type may have no active FAA event. Remove filters and run again to confirm the current feed contains records.

**Why is `feedUpdatedAt` null?**

The supplemental XML status feed was temporarily unavailable. Event rows still came from the authoritative JSON endpoint.

**Why did the run fail after retries?**

Check the run log for an FAA HTTP or payload error. Wait for the public FAA service to recover, then rerun; a proxy is not required or supported.

**Why is an event field null?**

Different FAA event types expose different fields. For example, runway configuration events do not have delay minutes.

### Frequently asked questions

**Does this Actor track individual flights?**

No. It returns airport-level NAS events and advisories, not flight itineraries or tail-number movements.

**Can I filter by airport?**

Yes. Pass one or more 3- or 4-character codes in `airports`.

**Can I monitor changes?**

Yes. Schedule repeated runs and compare `eventId`, `updatedAt`, and event fields between datasets.

**Does it require an FAA API key?**

No. It uses public FAA NAS status endpoints.

**Are all US airports always returned?**

No. The feed primarily returns airports that currently have an event or published operational record.

### Related Automation Lab Actors

This Actor currently stands alone in the Automation Lab portfolio because its buyer job is specifically current FAA NAS delay, closure, and airport-status monitoring.

Use general flight-data products instead when you need individual itineraries, fares, or aircraft tracking rather than airport-level FAA advisories.

### Support

If a source payload changes or a field appears incorrect, open an issue from the Actor page.

Include the run URL, input, expected event type, and affected airport code.

Do not include credentials or private operational information in a public report.

# Actor input Schema

## `airports` (type: `array`):

Optional FAA, IATA, or ICAO airport codes to include, such as SFO or KJFK. Codes are matched case-insensitively.

## `eventTypes` (type: `array`):

Optional FAA event categories to include. By default, all delay, closure, advisory, configuration, and deicing records are returned.

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

Maximum number of matching current advisory records to save.

## Actor input object example

```json
{
  "airports": [],
  "eventTypes": [
    "groundStop",
    "groundDelay",
    "airportClosure",
    "freeForm",
    "arrivalDelay",
    "departureDelay"
  ],
  "maxItems": 20
}
```

# Actor output Schema

## `dataset` (type: `string`):

Default dataset containing all matching normalized airport event rows.

# 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 = {
    "airports": [],
    "eventTypes": [
        "groundStop",
        "groundDelay",
        "airportClosure",
        "freeForm",
        "arrivalDelay",
        "departureDelay"
    ],
    "maxItems": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("automation-lab/faa-nas-status-airport-delays-scraper").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 = {
    "airports": [],
    "eventTypes": [
        "groundStop",
        "groundDelay",
        "airportClosure",
        "freeForm",
        "arrivalDelay",
        "departureDelay",
    ],
    "maxItems": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("automation-lab/faa-nas-status-airport-delays-scraper").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 '{
  "airports": [],
  "eventTypes": [
    "groundStop",
    "groundDelay",
    "airportClosure",
    "freeForm",
    "arrivalDelay",
    "departureDelay"
  ],
  "maxItems": 20
}' |
apify call automation-lab/faa-nas-status-airport-delays-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,automation-lab/faa-nas-status-airport-delays-scraper"
        }
    }
}

```

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/E4FqJQF1OqSBmybwh/builds/hbUgF4D14sLy3xjUj/openapi.json