# FAA Aircraft Registry, Owners & N-Number Scraper (`logiover/faa-aircraft-registry-scraper`) Actor

Export the official daily FAA aircraft registry at scale. Get N-numbers, owners, addresses, manufacturer, model, year, aircraft and engine types, airworthiness dates, certificate status and expiration. Built for aviation leads and market research.

- **URL**: https://apify.com/logiover/faa-aircraft-registry-scraper.md
- **Developed by:** [Logiover](https://apify.com/logiover) (community)
- **Categories:** Lead generation, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 results

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 Aircraft Registry, Owners & N-Number Scraper

Export the United States civil aircraft registry from the official daily FAA releasable database. The Actor joins the FAA master registration file with aircraft make/model and engine reference files, producing useful records instead of raw numeric lookup codes.

Get hundreds of thousands of N-number registrations with aircraft manufacturer, model, manufacture year, aircraft and engine type, owner or registrant, address, certification, certificate dates, expiration, Mode S identifiers, and direct registry links. The implementation streams the official ZIP archive and does not automate the FAA search website.

### What you can use it for

- Build aircraft owner and operator lead lists for maintenance, avionics, insurance, financing, hangars, training, brokerage, parts, and fuel services.
- Research fleet composition by manufacturer, model, age, aircraft type, state, country, or owner class.
- Find valid registrations for corporations, LLCs, individuals, partnerships, or government entities.
- Monitor registration expiration and certificate activity.
- Enrich aviation datasets with N-number, serial number, Mode S hex code, engine, seat, and airworthiness fields.
- Create regional general-aviation market reports and prospecting datasets.

### Data included

The normalized dataset includes:

- N-number and aircraft serial number
- manufacturer, model, manufacture year, aircraft category and type
- engine manufacturer, model, type, horsepower, and thrust where available
- number of engines, number of seats, weight class, and cruising speed
- registrant type, primary owner name, and other owner names
- released owner mailing address, state, postal code, county, region, and country
- FAA certification and registration status
- certificate issue, airworthiness, last action, and expiration dates
- Mode S octal and hexadecimal codes
- fractional-ownership indicator, kit manufacturer/model, and unique record ID
- direct FAA registry inquiry URL and official data-source URL

FAA fixed-width-looking values are parsed as CSV according to the released file headers. Blank numeric fields remain `null`. N-numbers, ZIP codes, serial numbers, and Mode S codes remain strings.

### Input

The default run returns 1,000 records with valid FAA registrations. `maxResults` supports up to 500,000 records.

Filters include:

- `activeOnly`: status code V only by default
- `states` and `countries`: registrant address filters
- `manufacturerContains`, `modelContains`, and `ownerContains`
- `minYear` and `maxYear`
- `aircraftTypes`: glider, balloon, fixed-wing single/multi-engine, rotorcraft, and other FAA type codes
- `registrantTypes`: individual, partnership, corporation, co-owned, government, LLC, and non-citizen classes

Example: valid Florida and Texas Cessna or Beechcraft records should be run separately per manufacturer fragment. A Cessna request:

```json
{
  "maxResults": 10000,
  "activeOnly": true,
  "states": ["FL", "TX"],
  "manufacturerContains": "CESSNA",
  "minYear": 1990
}
```

Example: corporate and LLC rotorcraft:

```json
{
  "maxResults": 5000,
  "activeOnly": true,
  "aircraftTypes": ["6"],
  "registrantTypes": ["3", "7"]
}
```

### Output example

```json
{
  "nNumber": "N12345",
  "serialNumber": "ABC-100",
  "manufacturer": "CESSNA",
  "model": "172S",
  "yearManufactured": 2018,
  "aircraftType": "Fixed wing single-engine",
  "engineManufacturer": "LYCOMING",
  "ownerName": "EXAMPLE AVIATION LLC",
  "registrantType": "Limited liability company",
  "address": { "city": "MIAMI", "state": "FL", "country": "US" },
  "status": "Valid",
  "expirationDate": "2031-08-31",
  "modeSCodeHex": "A1B2C3"
}
```

The default Apify dataset supports JSON, CSV, Excel, XML, RSS, API access, webhooks, and integrations.

### Performance and reliability

The current FAA archive is tens of megabytes compressed and several hundred megabytes expanded. The Actor never expands it to disk or memory as one object. It streams ZIP entries, builds only the comparatively small aircraft and engine reference maps, then streams the master registrations. It stops the download/decompression pipeline as soon as `maxResults` is satisfied.

The archive download retries transient errors with backoff. Dataset records are pushed in batches. A 512 MB Actor configuration is sufficient for high-volume operation because the master file is not accumulated.

### Data source, privacy, and responsible use

The source is the FAA Releasable Aircraft Database. FAA documentation and field definitions govern interpretation. Registry information can lag transactions, include reserved formatting, or contain non-current addresses. Verify critical ownership, airworthiness, and certificate facts through official FAA channels.

Registrant data is public government data, but public does not mean unrestricted use. Follow privacy, direct-marketing, telemarketing, and data-protection requirements that apply to you. Do not use the dataset for harassment, stalking, discrimination, or unsafe targeting. This Actor is not affiliated with or endorsed by the FAA.

### Pricing

Pay-per-event pricing consists of a small Actor-start event and one event per saved aircraft. Use `maxResults` to cap result charges. Source rows that do not match filters are not charged as results.

### Changelog

#### 2026-08-03 — 1.0.0

- Initial release.
- Verified the live daily FAA ZIP contents and current MASTER, ACFTREF, and ENGINE headers.
- Added streaming joins, valid-status default, ownership/aircraft/year filters, normalized type labels, numeric integrity, retries, batch writes, and dataset overview.

# Actor input Schema

## `maxResults` (type: `integer`):

Maximum matching aircraft registrations to save. Raise up to 500,000 for bulk exports.

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

Keep FAA master records with status code V. Disable to include other released statuses.

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

Optional two-letter owner address state codes such as FL, TX or CA.

## `countries` (type: `array`):

Optional FAA country values, commonly US for domestic registrations.

## `manufacturerContains` (type: `string`):

Case-insensitive aircraft manufacturer fragment, for example CESSNA or BOEING.

## `modelContains` (type: `string`):

Case-insensitive aircraft model fragment.

## `ownerContains` (type: `string`):

Case-insensitive owner or registrant name fragment.

## `minYear` (type: `integer`):

Optional earliest aircraft manufacture year.

## `maxYear` (type: `integer`):

Optional latest aircraft manufacture year.

## `aircraftTypes` (type: `array`):

FAA codes: 4 fixed-wing single-engine, 5 multi-engine, 6 rotorcraft, and others shown below.

## `registrantTypes` (type: `array`):

Filter individuals, companies, LLCs, government owners and other FAA registrant classes.

## Actor input object example

```json
{
  "maxResults": 1000,
  "activeOnly": true,
  "states": [],
  "countries": [],
  "manufacturerContains": "",
  "modelContains": "",
  "ownerContains": "",
  "aircraftTypes": [],
  "registrantTypes": []
}
```

# Actor output Schema

## `results` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("logiover/faa-aircraft-registry-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("logiover/faa-aircraft-registry-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 '{}' |
apify call logiover/faa-aircraft-registry-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,logiover/faa-aircraft-registry-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/psniKUGH9JGNgruCc/builds/3kr7WP8QLvQdNquST/openapi.json