Planefinder Flight Scraper

What does Planefinder Flight Scraper do?

Planefinder Flight Scraper retrieves the historical flight timeline for aircraft identified by flight number, ATC callsign, or ADS-B hex code using Planefinder's mobile API. Each run returns all recent legs flown by the queried aircraft — useful for tracking flight history, building route databases, or investigating specific tail numbers.

Results are pushed directly to an Apify dataset. Use Apify's scheduling and integrations to automate data collection at any cadence.

Why use Planefinder Flight Scraper?

• Flight history tracking — retrieve every leg flown recently by a specific flight number or tail number.
• Route analysis — understand which routes an airline or aircraft has been operating.
• Delay research — compare scheduled vs. actual departure and arrival timestamps across multiple legs.
• Aviation data pipelines — combine with airport scrapers to build comprehensive flight event feeds.

How to use Planefinder Flight Scraper

1. Open the Actor and click Try for free.
2. In the Input tab, enter one or more flight numbers, callsigns, or ADS-B hex codes.
3. Click Start and wait for the run to finish.
4. Download results from the Output tab in JSON, CSV, or Excel format.

Input

At least one of flight_numbers, callsigns, or adshex_codes must be provided.

Field	Type	Description
flight_numbers	array	IATA flight numbers (e.g. ["GA401", "JT123"])
callsigns	array	ATC callsigns (e.g. ["GIA401", "JSA123"])
adshex_codes	array	ADS-B transponder hex codes (e.g. ["8A02E4"])

{
    "flight_numbers": ["GA401"],
    "callsigns": [],
    "adshex_codes": []
}

Output

Each item represents one historical flight leg. You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

{
    "query_type": "flight_number",
    "query_value": "GA401",
    "flight_number": "GA401",
    "callsign": "GIA401",
    "reg": "PK-GFA",
    "type": "B77W",
    "dep_apt": "CGK",
    "arr_apt": "DPS",
    "airline_code": "GIA",
    "dep_status": 0,
    "arr_status": 0,
    "dep_ts": 1748000000,
    "arr_ts": 1748003600,
    "dep_schd_ts": 1748000000,
    "arr_schd_ts": 1748003600
}

Data table

Field	Description
query_type	How the aircraft was looked up: flight_number, callsign, or adshex
query_value	The specific value used for the query
flight_number	IATA flight number
callsign	ATC callsign
reg	Aircraft registration
type	ICAO aircraft type code
dep_apt	Departure airport IATA
arr_apt	Arrival airport IATA
airline_code	ICAO airline code
dep_ts	Actual departure Unix timestamp
arr_ts	Actual arrival Unix timestamp
dep_schd_ts	Scheduled departure Unix timestamp
arr_schd_ts	Scheduled arrival Unix timestamp

Tips

• Mix all three identifier types in a single run — each result includes a query_type field so you can trace which input produced it.
• Use ADS-B hex codes (adshex_codes) to track a specific physical aircraft regardless of which flight number it's operating.
• Combine with the Planefinder Airport Scraper to correlate live departures with historical timelines.

FAQ and support

This Actor uses Planefinder's public mobile API for informational purposes only. Do not use the data for commercial redistribution without verifying Planefinder's terms of service.

For bugs or feature requests, open an issue on the Actor's Issues tab. Custom scraping solutions are available on request.