Live Aircraft Scraper: ADS-B Positions by Radius
Pricing
Pay per usage
Go to Apify Store
Live Aircraft Scraper: ADS-B Positions by Radius
Pull live aircraft positions around any coordinate via the public adsb.lol API: callsign, registration, type, altitude and speed. No login, no proxy, no browser.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Naimur Hasan
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
6 days ago
Last modified
Categories
Share
Live Aircraft Scraper
Pulls live ADS-B aircraft positions around any coordinate through the public adsb.lol API. No login, no proxy, no browser.
Input
| Field | Type | Notes |
|---|---|---|
latitude | string | Required. Centre point latitude. Default 51.47 (Heathrow). |
longitude | string | Required. Centre point longitude. Default -0.4543. |
radiusNm | integer | Radius in nautical miles, capped at 250 upstream. Default 25. |
maxItems | integer | Cap on aircraft returned. Default 100. |
Output
One row per aircraft: hex, callsign, registration, aircraftType,
altitudeFt, onGround, groundSpeedKt, trackDeg, verticalRateFpm,
latitude, longitude, squawk, emergency, capturedAt.
Notes
alt_barois not always a number — a parked aircraft reports the literal string"ground". Coercing that blindly yieldsNaN, so it is split into a numericaltitudeFtand a separateonGroundboolean.- Callsigns are space-padded (
"GBRDF "), which breaks joins and grouping if passed through untrimmed. - Results are a live snapshot of what receivers can currently hear, so
coverage is best near populated areas and poor over oceans.
capturedAtis stamped by this Actor because the payload describes "now" with no timestamp per aircraft. - Aircraft that block their registration, and military traffic, may appear with a hex code but no callsign or type.
- The API 403s any request without a
User-Agent, which Node'sfetchomits by default while curl supplies one — so a curl spot-check passes while the Actor fails. One is set explicitly here. - It also rate limits, answering 429 under rapid repeat calls, so retryable statuses are retried with a backoff. A single scheduled run per day will not come close to the limit.
