# Flightradar24 Flight Scraper (`moving_beacon-owner1/flightradar24-flight-scraper`) Actor

Fetches live aircraft and flight data including position, altitude, speed, callsign, aircraft, registration, airports, and flight details. Supports live-zone, registration, and flight-number searches with optional enrichment.

- **URL**: https://apify.com/moving\_beacon-owner1/flightradar24-flight-scraper.md
- **Developed by:** [Jamshaid Arif](https://apify.com/moving_beacon-owner1) (community)
- **Categories:** Travel, Developer tools, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.99 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Flightradar24 Flight Scraper

Pulls live flight and aircraft data from Flightradar24's open JSON endpoints — no API key,
no subscription, no browser. Three modes:

- **`live_zone`** —: every aircraft
  currently inside a lat/lon box, with position, altitude, speed, heading, squawk,
  registration, aircraft type, callsign and origin/destination IATA codes.
- **`registration`** / **`flight_number`** — :
  recent and scheduled flights for one tail number or flight number, with scheduled vs
  actual departure/arrival times, airline, aircraft model and airports.
- Optional per-flight enrichment in `live_zone` mode via
  \`\` (airline, full aircraft model, airport
  names, trail length).

Every record keeps the untouched API payload in `raw` (and `raw_detail` when details are on).

### Input

| Field | Default | Description |
|---|---|---|
| `mode` | `live_zone` | `live_zone`, `registration`, or `flight_number`. |
| `bounds` | `58.00,42.00,-11.00,20.00` | `north,south,west,east` box for `live_zone`. |
| `query` | `""` | Registration (`B-HPJ`) or flight number (`CX255`) for the other two modes. |
| `include_details` | `false` | Add clickhandler detail to each live aircraft (slow, rate limited). |
| `limit` | `100` | Max records (1–1500). |

### Output

```json
{
    "flight_id": "41332733",
    "icao_24bit": "40823F",
    "latitude": 51.862,
    "longitude": -0.303,
    "heading": 318,
    "altitude": 38025,
    "ground_speed": 396,
    "squawk": "",
    "radar": "F-BDWY1",
    "aircraft_code": "A21N",
    "registration": "G-HLYM",
    "time": 1786887903,
    "origin_airport_iata": "DBV",
    "destination_airport_iata": "MAN",
    "number": "LS962",
    "on_ground": false,
    "vertical_speed": 0,
    "callsign": "EXS92SG",
    "airline_icao": "EXS",
    "raw": ["...original feed.js array..."]
}
```

### Data source

Unofficial Flightradar24 JSON endpoints, reachable without credentials when called with a
desktop browser User-Agent and `Referer: https://www.flightradar24.com/`. Requests go
through `curl_cffi` with Chrome/Safari TLS impersonation and a 30 s timeout; paged calls
sleep 0.8 s between pages. `feed.js` sits behind a load balancer whose nodes intermittently
answer with statistics only and no aircraft, so the scraper retries up to 8 times.

FR24 states on every API response that the contents and derived data are the property of
Flightradar24 AB; using, modifying or redistributing them without written permission may be
prohibited. Keep request volume low, and use the official API at
https://fr24api.flightradar24.com/ for commercial use.

# Actor input Schema

## `mode` (type: `string`):

live\_zone returns every aircraft currently inside 'bounds'. registration and flight\_number return the recent and scheduled flights matching 'query'.

## `bounds` (type: `string`):

Latitude/longitude box for live\_zone mode, e.g. 58.00,42.00,-11.00,20.00 (Western Europe) or 49.5,24.5,-125.0,-66.5 (continental USA). Ignored in the other modes.

## `query` (type: `string`):

Aircraft registration (e.g. B-HPJ, G-HLYM) for registration mode, or flight number (e.g. CX255, BA117) for flight\_number mode. Ignored in live\_zone mode.

## `include_details` (type: `boolean`):

In live\_zone mode, additionally call the clickhandler endpoint for each aircraft to add airline, aircraft model, full airport names and trail size. Much slower and more heavily rate limited — keep the limit small.

## `limit` (type: `integer`):

Maximum number of flight records to return.

## Actor input object example

```json
{
  "mode": "live_zone",
  "bounds": "58.00,42.00,-11.00,20.00",
  "query": "B-HPJ",
  "include_details": false,
  "limit": 100
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# 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 = {
    "mode": "live_zone",
    "bounds": "58.00,42.00,-11.00,20.00",
    "query": "B-HPJ",
    "include_details": false,
    "limit": 100
};

// Run the Actor and wait for it to finish
const run = await client.actor("moving_beacon-owner1/flightradar24-flight-scraper").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 = {
    "mode": "live_zone",
    "bounds": "58.00,42.00,-11.00,20.00",
    "query": "B-HPJ",
    "include_details": False,
    "limit": 100,
}

# Run the Actor and wait for it to finish
run = client.actor("moving_beacon-owner1/flightradar24-flight-scraper").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 '{
  "mode": "live_zone",
  "bounds": "58.00,42.00,-11.00,20.00",
  "query": "B-HPJ",
  "include_details": false,
  "limit": 100
}' |
apify call moving_beacon-owner1/flightradar24-flight-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,moving_beacon-owner1/flightradar24-flight-scraper"
        }
    }
}

```

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/FFdvtspeaIIgBbf2J/builds/0sIsDVaJzg5VTeqa7/openapi.json