# Airworthiness Directive Monitor: FAA AD Alerts by Aircraft (`centorprat/airworthiness-directive-monitor`) Actor

Watch FAA Airworthiness Directives (ADs) for your fleet. Give aircraft, manufacturers or models (Boeing 737, Airbus A320, Rolls-Royce); each run pulls recent ADs - final and proposed - from the keyless Federal Register, keeps your matches, and flags only what is NEW. Schedule + webhook for alerts.

- **URL**: https://apify.com/centorprat/airworthiness-directive-monitor.md
- **Developed by:** [Centor Prat](https://apify.com/centorprat) (community)
- **Categories:** Developer tools
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $8.50 / 1,000 watch runs

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/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

## Airworthiness Directive Monitor: FAA AD Alerts by Aircraft

**Watch FAA Airworthiness Directives for your fleet — and get alerted only when a NEW one lands.** An
Airworthiness Directive (AD) is a legally **mandatory** FAA order to correct an unsafe condition on an
aircraft, engine or part — the aviation equivalent of a recall, and missing one that applies to your
fleet means grounded aircraft and liability. This monitor pulls recent FAA ADs (final + proposed) from
the keyless Federal Register, matches them to your aircraft/manufacturer watch terms, and — because it
remembers the previous run — surfaces just the new ones. Schedule it and point `webhookUrl` at
Slack/email (via Make/Zapier) to turn it into a standing AD alarm. Works as a one-shot lookup too.

> 📋 **Factual public records.** Every row is an official Federal Register FAA document, reported
> verbatim (title, AD number, stage, effective date, docket, link). No scoring, no editorializing.

### ⚡ What makes it a *monitor*, not just a lookup

Most sources re-list every AD each time. This one **diffs against the previous run**: the first run
quietly sets a baseline (no spam from history), and every run after surfaces — and webhooks — **only ADs
that are new since last time**. Set a schedule once; hear about it only when it matters.

### 📋 What each directive contains

| Field | Meaning |
|---|---|
| `adNumber` | The AD number (e.g. `AD 2026-20-10`); blank for proposed rules not yet numbered |
| `stage` | `Final rule (mandatory)` or `Proposed rule (comment period)` |
| `subject` | Manufacturer / model the AD applies to (e.g. "The Boeing Company Airplanes") |
| `effectiveOn` | Date the AD takes effect |
| `publicationDate` / `docketNumber` / `htmlUrl` | When published, the FAA docket, and the full text |
| `matchedTerms` / `isNew` | Which of your watch terms matched, and whether it's new since last run |

### 📥 Input

```json
{
  "watchTerms": ["Boeing 737", "Airbus A320", "Rolls-Royce"],
  "ruleStages": ["final", "proposed"],
  "onlyNew": true,
  "webhookUrl": "https://hook.make.com/..."
}
```

Leave `watchTerms` empty to track **all** FAA ADs. `ruleStages` picks final (mandatory, in force) and/or
proposed (heads-up). `sinceDays` sets the look-back (default 120).

### 📤 Example output (real run, trimmed — a watch on "Boeing")

```json
{
  "isNew": true,
  "stage": "Final rule (mandatory)",
  "adNumber": "AD 2026-20-10",
  "subject": "The Boeing Company Airplanes",
  "effectiveOn": "2026-11-12",
  "publicationDate": "2026-10-07",
  "matchedTerms": ["Boeing"],
  "htmlUrl": "https://www.federalregister.gov/documents/..."
}
```

The first run instead writes a baseline marker (`"baseline": true`), so no false "new" alerts fire for
pre-existing ADs.

### 💰 Pricing (pay-per-event)

- **Watch run — $0.01** per run (the fetch + diff).
- **New directive alert — $0.02** per newly-detected AD. Quiet runs cost only the base.

### 💡 Use cases

- **Airlines / operators / flight departments:** a standing alarm for ADs on the types you fly.
- **MRO / maintenance / CAMO:** catch new mandatory fixes for your customers' fleets the day they publish.
- **Lessors / parts suppliers / insurers / aviation lawyers:** track ADs by manufacturer or model.
- **Agents:** callable as an MCP tool — give it aircraft terms, get back only what's new.

### 🔑 Keyless & agent-callable

No API keys, no accounts, no paid child Actors — just the public Federal Register (FAA) data.

### 🚀 Ready-made tasks (one click)

- [Boeing 737 Airworthiness Directives (FAA AD Alerts)](https://apify.com/centorprat/airworthiness-directive-monitor/examples/boeing-737-airworthiness-directives)
- [Airbus A320 Family Airworthiness Directives Monitor](https://apify.com/centorprat/airworthiness-directive-monitor/examples/airbus-a320-airworthiness-directives)
- [Aircraft Engine ADs - CFM, Pratt & Whitney, GE](https://apify.com/centorprat/airworthiness-directive-monitor/examples/aircraft-engine-airworthiness-directives)

### 🤖 For AI agents (MCP)

```
https://mcp.apify.com/?tools=actors,docs,centorprat/airworthiness-directive-monitor
```

Loads as `centorprat--airworthiness-directive-monitor`. Claude Code:

```
claude mcp add apify -- npx -y @apify/actors-mcp-server --actors centorprat/airworthiness-directive-monitor
```

# Actor input Schema

## `watchTerms` (type: `array`):

Alert when an AD mentions any of these, e.g. \["Boeing 737"], \["Airbus A320", "Rolls-Royce", "CFM56"]. Matched against the AD title, abstract and docket. Leave empty to track ALL FAA ADs in the window.

## `ruleStages` (type: `array`):

Final rules are mandatory and in force; proposed rules are a heads-up in the comment period.

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

On: each run returns only ADs not seen on the previous run (ideal for scheduled alerting). Off: returns every matching AD each run.

## `sinceDays` (type: `integer`):

How far back to pull ADs each run.

## `persistState` (type: `boolean`):

Stores the ADs seen this run in a named key-value store so the next run can tell what is new. Keep on for monitoring; off for a stateless one-shot query.

## `maxDirectives` (type: `integer`):

Cap how many ADs to pull per run.

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

If set, NEW ADs are POSTed here as JSON when a run finds any - wire it to Slack/Discord/email via Make or Zapier.

## Actor input object example

```json
{
  "watchTerms": [
    "Boeing 737"
  ],
  "ruleStages": [
    "final",
    "proposed"
  ],
  "onlyNew": true,
  "sinceDays": 120,
  "persistState": true,
  "maxDirectives": 1000
}
```

# Actor output Schema

## `directives` (type: `string`):

Matching FAA ADs, newest first, each flagged isNew. Fields: AD number, stage (final=mandatory / proposed), subject (manufacturer/model), effective date, publication date, docket, regulation IDs, abstract, link, and which watch terms matched. First run writes a baseline; later runs emit only new ADs when onlyNew is on.

# 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 = {
    "watchTerms": [
        "Boeing 737"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("centorprat/airworthiness-directive-monitor").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 = { "watchTerms": ["Boeing 737"] }

# Run the Actor and wait for it to finish
run = client.actor("centorprat/airworthiness-directive-monitor").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 '{
  "watchTerms": [
    "Boeing 737"
  ]
}' |
apify call centorprat/airworthiness-directive-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,centorprat/airworthiness-directive-monitor"
        }
    }
}
```

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/7KWjA1lirB9frUzoa/builds/Vm3NUm2Dgc7bg3Rza/openapi.json