Planefinder Flightpath Scraper
Under maintenancePricing
from $30.00 / 1,000 results
Planefinder Flightpath Scraper
Under maintenancePlanefinder Flight Path Scraper fetches the full geographic track (latitude, longitude, altitude, speed, heading over time) flown by a completed flight from Planefinder's mobile API
Pricing
from $30.00 / 1,000 results
Rating
0.0
(0)
Developer
Romy
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
What does Planefinder Flight Path Scraper do?
Planefinder Flight Path Scraper fetches the full geographic track (latitude, longitude, altitude, speed, heading over time) flown by a completed flight from Planefinder's mobile API. Look up by Planefinder's internal flightId — get one with the Planefinder Search Scraper or Planefinder Flight Scraper first.
Results are pushed directly to an Apify dataset, one item per track point, in chronological order.
Why use Planefinder Flight Path Scraper?
- Route visualization — plot the actual flown path on a map (not just great-circle departure→arrival).
- Deviation analysis — compare actual routing against the scheduled/direct route.
- Flight replay — reconstruct a flight's climb, cruise, and descent profile over time.
How to use Planefinder Flight Path Scraper
- Get a
flightIdfrom the Planefinder Search Scraper (fieldflightId) or Planefinder Flight Scraper. - Open this Actor and click Try for free.
- In the Input tab, enter one or more flight IDs.
- Click Start and wait for the run to finish.
- Download results from the Output tab in JSON, CSV, or Excel format.
Input
| Field | Type | Description |
|---|---|---|
flight_ids | array | Planefinder internal flight IDs, e.g. ["5-54350130"] |
{"flight_ids": ["5-54350130"]}
Output
Each item represents one track point along the flight's path, in chronological order (seq starting at 0).
{"query_flight_id": "5-54350130","seq": 0,"lat": -6.27268,"lon": 106.879,"altitude": 975,"speed": 136,"heading": 238,"timestamp": 1772077196,"session_id": 1705}
Data table
| Field | Description |
|---|---|
query_flight_id | The flight ID you queried |
seq | Point index within this flight's path, 0 = earliest point |
lat / lon | Position in decimal degrees |
altitude | Altitude in feet |
speed | Ground speed in knots |
heading | Compass heading in degrees |
timestamp | Unix timestamp (seconds) for this point |
session_id | An internal Planefinder ID, constant across all points of the same flight (exact meaning unconfirmed — useful for grouping/dedup) |
Tips
- Flight IDs not found (or with no recorded path) return no output items, aren't charged, and log a warning, rather than failing the run.
- Combine with the Planefinder Search Scraper or Flight Scraper: resolve a callsign/registration to a
flightIdfirst, then feed it into this Actor.
Pricing
This Actor uses the Pay Per Event model: a flat $0.25 per flight path fetched, plus a negligible one-time actor-start fee — not per track point. You're asking for "this flight's path" as one thing, so you're billed as one thing, whether Planefinder returns 20 points or 400. A flight ID that isn't found isn't charged.
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.