FAA Vertical Project Radar

Turn the FAA's weekly construction-notice file into a focused project-signal feed for crane and rigging firms, tower contractors, obstruction-lighting providers, wind contractors, and utility-structure crews.

This independent Actor is not affiliated with or endorsed by the Federal Aviation Administration. It reads only the FAA's public weekly construction-notice page and never contacts a project owner.

Why this is different

The official notice is a fixed-width multi-page file containing more than a thousand mixed structure records in a typical week. This Actor validates the entire notice, converts coordinates and identifiers into structured fields, and emits only records matching the chosen state and operational buyer route.

The latest verified California crane-and-rigging run parsed 1,179 official records and returned seven route-qualified records. A four-week backtest found 82 qualified records with zero parser ambiguities.

Input

• state: two-letter US state or territory code; default CA.
• route: crane_rigging, tower_erection, obstruction_lighting, wind, or utility_structure.
• cityQuery: optional case-insensitive FAA-reported city filter, such as Sacramento or San Jose.
• minHeightAgl: optional minimum FAA-reported height above ground, from 0 to 2,000 feet.
• includeRemoved: include official REMOVED and DISMANTLED actions; off by default.
• sourceUrl: optional exact official weekly notice URL for reproducible historical runs.

Use it as a weekly monitor

Save the input as an Apify Task and attach a weekly schedule. Each run resolves the newest complete official FAA notice and writes only the state, buyer route, city, and height matches you requested. For example, a Sacramento-focused crane firm can use CA, crane_rigging, Sacramento, and 100 feet. Apify retains each run's dataset, so results remain exportable as CSV, JSON, Excel, or through the API.

The Actor does not contact project owners, enrich identities, or promise that a record is commercially actionable. A scheduled run with zero matching records returns an empty dataset rather than manufacturing a lead.

Live example monitors

• Lockney, Texas wind-project monitor uses TX, wind, Lockney, and a 400-foot minimum. Its August 23, 2026 source run returned 68 official records.
• Alta, Iowa obstruction-lighting monitor uses IA, obstruction_lighting, Alta, and a 650-foot minimum. Its August 23, 2026 source run returned 70 official records.
• Sacramento crane-and-tower monitor uses a bounded city and height filter for a smaller local feed.

These counts describe one dated official notice, not guaranteed future volume. Each public task reruns the same transparent filters against the newest complete weekly source.

Output

Each dataset row contains the official action and verification code, city, coordinates, structure type, AGL/AMSL height, FAA study number when reported, OAS number, buyer routes, observation date, and exact official source URL.

Pricing

The launch configuration uses two synthetic events: $0.10 per GB at Actor start and $0.01 per qualified project signal. Runtime memory is fixed at 256 MB, so the start event is $0.025 per run before any result events. Empty or nonmatching runs return no dataset items and incur only that bounded start charge. Final pricing and whether platform usage is included must match the live Apify Console.

Verification boundary

FAA construction-notice records are early-work indicators, not confirmation of project stage, contract award, scope fit, procurement availability, owner identity, or eligibility. Always verify the official source record before acting. The Actor fails closed when pagination, dates, headers, row grammar, source host, or identifiers are inconsistent.

Official source

https://aeronav.faa.gov/Obst_Data/CONSTR_NOTICE_MMDDYY.htm