# Flightradar24 Airport Schedules Scraper (`kibaale/flightradar24-schedules-scraper`) Actor

Scrapes departure and arrival boards for any airport from Flightradar24: flight number, callsign, codeshare, airline, status, scheduled times and aircraft model. Accepts IATA codes or airport names. No API key, no login, no browser.

- **URL**: https://apify.com/kibaale/flightradar24-schedules-scraper.md
- **Developed by:** [kibalee](https://apify.com/kibaale) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 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 Airport Schedules Scraper

Scrapes **airport departure and arrival boards** from Flightradar24. No API key, no login, no browser.

### What you get

One record per scheduled flight:

```json
{
  "airportCode": "CGK",
  "direction": "departure",
  "flightNumber": "ID6564",
  "callsign": "",
  "codeshare": [],
  "airlineCode": "ID",
  "statusText": "Estimated dep 12:58",
  "statusType": "estimated",
  "statusColor": "green",
  "diverted": false,
  "eventTimeUtc": "2026-09-13T04:38:00+00:00",
  "eventTimeLocal": "2026-09-13T11:38:00+00:00",
  "scheduledDeparture": "2026-09-13T03:10:00+00:00",
  "aircraftModel": "32A"
}
```

Plus the full raw fields of the record.

### Input

| Field | Description |
|---|---|
| `airportCodes` | IATA codes (`CGK`, `SIN`) or airport names — names resolve automatically (default `["CGK"]`) |
| `mode` | `departures`, `arrivals`, or `both` (default `departures`) |
| `limitPerAirport` | Flights per board, 1-300 (default `100`) |

### What it does not do

- It does **not** track live in-air aircraft positions.
- It does **not** provide historical flight playback or flight detail pages.
- Each run is a **snapshot of the board** at run time; statuses change as flights operate, so re-run to refresh.

This actor focuses on schedule boards only — it makes no promises about live tracking.

### Output

One record per flight in the dataset, flattened fields as shown above.

# Actor input Schema

## `airportCodes` (type: `array`):

IATA codes (CGK, SIN) or airport names ("Singapore Changi") — names are resolved automatically.

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

Which board to scrape for each airport.

## `limitPerAirport` (type: `integer`):

How many flights to return per board (1-300).

## Actor input object example

```json
{
  "airportCodes": [
    "CGK"
  ],
  "mode": "departures",
  "limitPerAirport": 100
}
```

# Actor output Schema

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

Flight records stored in the run's default dataset

# 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 = {
    "airportCodes": [
        "CGK"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("kibaale/flightradar24-schedules-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 = { "airportCodes": ["CGK"] }

# Run the Actor and wait for it to finish
run = client.actor("kibaale/flightradar24-schedules-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 '{
  "airportCodes": [
    "CGK"
  ]
}' |
apify call kibaale/flightradar24-schedules-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,kibaale/flightradar24-schedules-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/E4HTxvGB5hr3Iz665/builds/ClCJtTAAXXF9oRa5E/openapi.json