# FAA OE/AAA Crane, Tower & Pre-Construction Lead Feed (`zinky_atelier/faa-oeaaa-crane-tower-leads`) Actor

Extract US pre-construction FAA Form 7460-1 Obstruction Evaluation (OE/AAA) filings for tower cranes, 5G cell towers, high-rises, data centers, wind farms, and solar arrays via official FAA REST services—with optional sponsor contact & schedule enrichment.

- **URL**: https://apify.com/zinky_atelier/faa-oeaaa-crane-tower-leads.md
- **Developed by:** [Travis Burrows](https://apify.com/zinky_atelier) (community)
- **Categories:** Lead generation, Real estate, Business
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $17.50 / 1,000 faa oe/aaa filing extracteds

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

## FAA OE/AAA Crane, Tower & Pre-Construction Form 7460-1 Lead Feed

Capture high-value US commercial high-rises, tower cranes, data centers, hospitals, 5G telecom towers, utility-scale wind & solar farms, and transmission lines **months before municipal building permits are issued**—directly from official **FAA Form 7460-1 Obstruction Evaluation / Airport Airspace Analysis (OE/AAA)** filings.

Zero headless browsers. Zero proxy fees (`256 MB` RAM). Built natively for **daily scheduled delta feeds** (`onlyNew: true`), **Clay / Make / n8n outbound enrichment** (`enrichCaseDetails: true` for direct Sponsor & Engineering Representative emails, phones, and construction start/end dates), and **AI MCP agents**.

***

### Why FAA Form 7460-1 Is the Ultimate Early Pre-Construction Signal

Under **14 CFR Part 77**, any developer, general contractor, crane rental operator, telecom carrier, or energy EPC planning to erect or alter a vertical structure over **200 ft AGL**—or **any temporary construction crane, rig, building, or pole near thousands of US airports and heliports**—must file **FAA Form 7460-1** at least **45+ days prior to construction**.

| B2B Buyer Persona | Automated Workflow |
| :--- | :--- |
| **Tower & Mobile Crane Rental, Rigging & Hoisting** | Daily state delta alert (`structureCategories: ["CRANE", "BUILDING"]`) with exact `workBeginsDate`, `aglHeightProposedFt`, and contractor contact details. |
| **Builders-Risk, Inland Marine & Commercial P\&C Brokers** | Enrich upcoming commercial/industrial builds (`minAglHeightFt: 100`, `enrichCaseDetails: true`) in Clay 60–120 days before groundbreaking. |
| **Obstruction Lighting, Aviation Safety & Telecom Contractors** | Filter `TOWER`, `WIND`, and `UTILITY` filings requiring FAA `Red lights and flags` or medium/dual-intensity lighting (`recommendedMarkingLighting`). |
| **Concrete, Structural Steel, MEP & Data Center Suppliers** | Combine with our `epa-npdes-construction-permits` Actor to triangulate both **horizontal site grading** and **vertical crane/structure schedules**. |

***

### Transparent Pay-Per-Event (PPE) Pricing

| Event Name | When Charged | Suggested Store Price |
| :--- | :--- | :--- |
| `actor-start` | Once per Actor execution | `$0.02` / run |
| `filing-extracted` | Per normalized FAA OE/AAA filing emitted to Dataset (skipped duplicates are **never** charged) | `$0.025` / filing (`$25 / 1k`) |
| `case-detail-enriched` | Optional—only charged when `enrichCaseDetails: true` enriches per-case Form 7460-1 Sponsor/Representative email, phone, address & work schedule | `$0.015` / enriched lead |

***

### Input Guide & Modes

1. **`queryMode: "dateRange"` (Default — Best for Daily/Weekly Cron Schedules):**
   - Queries official FAA `/oeaaa/services/caseList/date/{OE|NRA}` endpoints in fast 3-day chunks (newest first), stopping as soon as `maxItems` is satisfied.
   - Set `daysBack` (default `5`) or explicit `startDate` / `endDate` (`YYYY-MM-DD`).
2. **`queryMode: "stateYear"` (State Archive Pulls):**
   - Queries `/oeaaa/services/caseList/{OE|NRA}/{year}?state=XX` for one or more 2-letter US state codes.
3. **`queryMode: "asnLookup"` (Clay / CRM Batch ASN Lookup):**
   - Pass `asns: ["2026-ASW-8882-OE", "2026-ASW-7839-OE"]` with `enrichCaseDetails: true` to enrich exact Form 7460-1 contacts and construction schedules on demand.

#### Copy-Paste Example Input (Daily Enriched Texas & Florida Crane/Tower Feed)

```json
{
  "queryMode": "dateRange",
  "states": ["TX", "FL"],
  "caseTypes": ["OE"],
  "structureCategories": ["CRANE", "TOWER", "BUILDING", "SOLAR", "WIND"],
  "minAglHeightFt": 100,
  "daysBack": 7,
  "enrichCaseDetails": true,
  "onlyNew": true,
  "maxItems": 50
}
```

***

### Realistic Enriched Output Sample

```json
{
  "asn": "2026-ASW-8882-OE",
  "caseId": "707995788",
  "caseType": "OE",
  "year": 2026,
  "faaRegion": "ASW",
  "statusCode": "DET-DNE-TMP",
  "statusSummary": "Determined - No Hazard",
  "sponsorName": "KEVIN SASSAMAN",
  "structureCategory": "CRANE",
  "structureTypeRaw": "CRANE$FIXED",
  "structureTypeLabel": "Stationary/Fixed Crane",
  "structureName": "Springtown Elementary School",
  "structureDescription": "Springtown Elementary School",
  "proposalDescription": "Location of crane to remove existing RTUs from school roof",
  "locationDescription": "Existing Elementary School",
  "state": "TX",
  "city": "Springtown",
  "county": "Parker",
  "latitude": 32.96791667,
  "longitude": -97.67825,
  "aglHeightProposedFt": 300,
  "aglHeightDeterminedFt": 300,
  "siteElevationProposedFt": 855,
  "amslHeightProposedFt": 1155,
  "amslHeightDeterminedFt": 1155,
  "nearestAirportName": "KENNETH COPELAND",
  "nearestAirportCode": "4T2",
  "distanceFromAirportFt": 57142,
  "directionFromAirportDeg": 267,
  "recommendedMarkingLighting": "Red lights and flags",
  "dateEntered": "2026-06-03",
  "receivedDate": "2026-06-03",
  "dateCompleted": "2026-06-25",
  "expirationDate": "2027-12-25",
  "noticeType": "New Construction",
  "durationType": "Temporary",
  "workBeginsDate": "2026-06-08",
  "workEndsDate": "2026-06-12",
  "fccAsrNumber": null,
  "detailEnriched": true,
  "sponsorContact": {
    "fullName": "KEVIN SASSAMAN",
    "organization": "KEVIN SASSAMAN",
    "attention": "KEVIN SASSAMAN",
    "email": "kevinsassaman@coreconstruction.com",
    "phone": "+1-817-733-4223",
    "streetAddress": "6320 Research Rd",
    "city": "Frisco",
    "state": "TX",
    "postalCode": "75033",
    "countryCode": "US"
  },
  "representativeContact": {
    "fullName": "Kevin Sassaman",
    "organization": "Kevin Sassaman",
    "attention": "Kevin Sassaman",
    "email": "kevinsassaman@coreconstruction.com",
    "phone": "+1-817-733-4223",
    "streetAddress": "6320 Research Rd",
    "city": "Frisco",
    "state": "TX",
    "postalCode": "75033",
    "countryCode": "US"
  },
  "faaCaseXmlUrl": "https://oeaaa.faa.gov/oeaaa/services/case/2026-ASW-8882-OE",
  "faaPublicPortalUrl": "https://oeaaa.faa.gov/oeaaa/asn-display/asn-case-display-page.html?asn=2026-ASW-8882-OE",
  "scrapedAt": "2026-11-14T04:30:00.000Z"
}
```

***

### Zero-Touch Daily Automation (Clay, Make, n8n, Slack & MCP)

1. Save an Apify Task with your target `states`, `structureCategories`, `minAglHeightFt`, `enrichCaseDetails: true`, and `onlyNew: true`.
2. Attach an **Apify Schedule** (`0 6 * * 1-5` — weekdays at 6:00 AM) and connect a Webhook to **Clay**, **Make**, **n8n**, **HubSpot**, or **Slack**.
3. The Actor automatically tracks delivered ASNs in `SEEN_CASES` so your outbound pipeline never receives or pays for duplicate pre-construction leads.

***

### How Much Does It Cost? (Tiered Pay-Per-Event Pricing)

No monthly rental—pay only per new Form 7460-1 filing extracted (`$0` on skipped duplicates with `onlyNew: true`), with automatic tier discounts:

| Event | One-Time? | Free Plan | Bronze | Silver | Gold / Enterprise |
| :--- | :---: | :---: | :---: | :---: | :---: |
| `actor-start` | Yes | `$0.02` | `$0.02` | `$0.02` | `$0.02` |
| `filing-extracted` *(Primary)* | No | `$0.025` | `$0.0225` | `$0.02` | `$0.0175` |
| `case-detail-enriched` | No | `$0.015` | `$0.0135` | `$0.012` | `$0.01` |

#### Clay, Make, n8n & AI Agent (`mcp.apify.com`) Chaining

- **Clay.com / CRM Pipeline:** Route crane, high-rise, data center, and 5G tower sponsor emails & phone numbers straight into Clay, HubSpot, or Apollo months before municipal permits are filed.
- **AI Agents & MCP (`mcp.apify.com`):** Query FAA OE/AAA pre-construction airspace filings by state and AGL height directly from MCP agents or JSON/CSV API endpoints.

# Actor input Schema

## `queryMode` (type: `string`):

Choose 'dateRange' for fast rolling pre-construction delta feeds (/services/caseList/date/{OE|NRA}), 'stateYear' for full-year state archives (/services/caseList/{OE|NRA}/{year}?state=XX), or 'asnLookup' to look up specific Aeronautical Study Numbers (/services/case/{asn}).

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

Filter to one or more 2-letter US state/territory codes (e.g. \['TX', 'FL', 'CA']). Leave empty (\[]) in 'dateRange' mode for nationwide US coverage; required in 'stateYear' mode.

## `caseTypes` (type: `array`):

'OE' = Off-Airport Obstruction Evaluation (Form 7460-1 cranes, towers, buildings, wind, solar, power lines); 'NRA' = On-Airport Non-Rulemaking Airport construction & safety plans.

## `structureCategories` (type: `array`):

Keep filings matching these structure types: 'CRANE', 'TOWER', 'BUILDING', 'WIND', 'SOLAR', 'UTILITY', or 'ALL' (unfiltered). You can also include raw FAA structureType prefixes such as 'CRANE$TOWER' or 'BRIDGE'.

## `minAglHeightFt` (type: `integer`):

Minimum proposed Above Ground Level (AGL) structure height in feet (e.g. 100 or 200 ft to isolate major tower cranes, high-rises, and cell towers).

## `daysBack` (type: `integer`):

Rolling number of days back from today (UTC) to query in 'dateRange' mode when explicit startDate/endDate are not set.

## `startDate` (type: `string`):

Optional explicit start date (YYYY-MM-DD) for 'dateRange' mode. Overrides daysBack when provided.

## `endDate` (type: `string`):

Optional explicit end date (YYYY-MM-DD) for 'dateRange' mode. Defaults to today (UTC) when startDate is set.

## `year` (type: `integer`):

4-digit year for 'stateYear' archive queries (defaults to current UTC year).

## `asns` (type: `array`):

List of FAA Aeronautical Study Numbers (e.g. \['2026-ASW-8882-OE', '2026-ASW-7839-OE']) to fetch directly.

## `enrichCaseDetails` (type: `boolean`):

Fetches per-case detail endpoints (/services/case/{asn} + public Form 7460-1 metadata) to enrich Sponsor & Representative direct email, phone, mailing address, county, proposal description, and exact construction start/end dates. Emits 'case-detail-enriched' PPE event per enriched lead.

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

Persists seen ASN identifiers in the 'SEEN_CASES' Key-Value Store record so scheduled daily/weekly cron runs only emit and bill for brand-new FAA filings.

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

Maximum number of matching FAA pre-construction filings to emit in this run.

## Actor input object example

```json
{
  "queryMode": "dateRange",
  "states": [
    "TX",
    "FL",
    "CA"
  ],
  "caseTypes": [
    "OE"
  ],
  "structureCategories": [
    "CRANE",
    "TOWER",
    "BUILDING",
    "WIND",
    "SOLAR",
    "UTILITY"
  ],
  "minAglHeightFt": 0,
  "daysBack": 5,
  "asns": [],
  "enrichCaseDetails": false,
  "onlyNew": false,
  "maxItems": 25
}
```

# Actor output Schema

## `filings` (type: `string`):

Normalized dataset of FAA OE/AAA aeronautical study pre-construction leads.

## `runSummary` (type: `string`):

JSON summary of query window, upstream XML cases scanned, filters applied, SEEN_CASES deduplication counts, and PPE events charged.

# 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 = {
    "states": [
        "TX",
        "FL",
        "CA"
    ],
    "caseTypes": [
        "OE"
    ],
    "structureCategories": [
        "CRANE",
        "TOWER",
        "BUILDING",
        "WIND",
        "SOLAR",
        "UTILITY"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("zinky_atelier/faa-oeaaa-crane-tower-leads").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 = {
    "states": [
        "TX",
        "FL",
        "CA",
    ],
    "caseTypes": ["OE"],
    "structureCategories": [
        "CRANE",
        "TOWER",
        "BUILDING",
        "WIND",
        "SOLAR",
        "UTILITY",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("zinky_atelier/faa-oeaaa-crane-tower-leads").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 '{
  "states": [
    "TX",
    "FL",
    "CA"
  ],
  "caseTypes": [
    "OE"
  ],
  "structureCategories": [
    "CRANE",
    "TOWER",
    "BUILDING",
    "WIND",
    "SOLAR",
    "UTILITY"
  ]
}' |
apify call zinky_atelier/faa-oeaaa-crane-tower-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,zinky_atelier/faa-oeaaa-crane-tower-leads"
        }
    }
}
```

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/wG8awZVkKgOUEH5KK/builds/dFyndLPJ0ngHIzx3u/openapi.json
