# Flightradar24 Airport Disruptions Scraper (`romy/flightradar24-airport-disruptions-scraper`) Actor

Get global airport delay/disruption rankings — a global, no-login angle competitors lack from Flightradar24. Talks directly to Flightradar24's own gRPC/REST APIs, no login needed. Split from the mature, published flightradar24-all-in-one-api for a focused, single-purpose workflow.

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

## Pricing

from $4.70 / 1,000 airport status chargeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

### What does Flightradar24 Airport Disruptions Scraper do?

**Flightradar24 Airport Disruptions Scraper** returns the airports currently experiencing the most delays or disruptions worldwide, ranked, in a single call — one dataset row per airport, no pagination needed.

It talks directly to the same internal REST API the official [Flightradar24](https://www.flightradar24.com/) Android app uses (`mobile.flightradar24.com`), reverse-engineered by static decompilation and validated against real live traffic. No API key, no login, no scraping setup — call the Actor, get JSON back.

This is the `/airport/disruptions` slice of [Flightradar24 All-in-One API](https://apify.com/romy/flightradar24-all-in-one-api), split out as its own focused Actor.

### Why use Flightradar24 Airport Disruptions Scraper?

- **One call, ranked results** — no pagination, no cursors, just the current disruption ranking
- **Real delay stats per airport** — arrivals/departures/combined, each broken down by yesterday/today/tomorrow/live, with delay counts, percentages, and a live "disruption index"
- **No account needed** — works fully anonymously, same as the free tier of the app itself
- **Use cases:** aviation monitoring dashboards, airport operations research, flight-delay news/data journalism, travel-disruption alerting

### Input

| Field       | Type    | Default  | Description              |
| ----------- | ------- | -------- | ------------------------ |
| `continent` | integer | `0`      | `0` = all continents     |
| `period`    | string  | `"live"` | Reporting period         |
| `type`      | string  | `"both"` | Arrivals/departures/both |

Example:

```json
{
    "continent": 0,
    "period": "live",
    "type": "both"
}
```

### Output

One dataset row per disrupted airport, Flightradar24's own ranked entry shape (trimmed real example):

```json
{
    "airport": {
        "id": 683,
        "name": "Colombo Bandaranaike International Airport",
        "code": { "iata": "CMB", "icao": "VCBI" },
        "country": { "name": "SRI LANKA", "alpha2": "LK", "alpha3": "LKA" },
        "continent": 3,
        "latitude": 7.181139,
        "longitude": 79.883789,
        "city": "Colombo"
    },
    "arrivals": {
        "live": { "index": 5, "averageDelayMin": 70, "delayed": 4, "delayedPercentage": 0.67, "trend": "static" }
    },
    "departures": {
        "live": { "index": 5, "averageDelayMin": 80, "delayed": 3, "delayedPercentage": 0.6, "trend": "up" }
    },
    "combined": {
        "live": { "index": 5, "averageDelayMin": 75, "delayed": 7, "delayedPercentage": 0.64, "trend": "up" }
    }
}
```

Each of `arrivals`/`departures`/`combined` also carries `yesterday`/`today`/`tomorrow` breakdowns (`total`, `delayed`, `delayedPercentage`, `cancelled`, `cancelledPercentage`) alongside `live`.

### Known limitations

- **Not paginated by Flightradar24** — this endpoint returns whatever the server currently ranks as disrupted (10 airports as observed live); there is no `page`/`limit` parameter to request more.
- It's normal for this to occasionally return few or zero entries — the ranking reflects real-time global disruption levels, which fluctuate.

### Pricing

This Actor uses **Pay Per Event** billing: charged $0.01 per disrupted-airport row returned (event `airport-status`, FREE tier price — lower on paid plans). See the Actor's Pricing tab for current rates.

### FAQ

**Does this require a Flightradar24 account?**
No. The Actor uses the same anonymous data feed the Flightradar24 mobile app uses — no login, no API key.

**Is this official?**
No. This is an independent tool using Flightradar24's internal API, reverse-engineered from the public Android app. Use responsibly and in accordance with Flightradar24's Terms of Service.

**Need a custom integration?**
Contact me at romysaputrasihanandaa@gmail.com or [hire me on Fiverr](https://www.fiverr.com/romyssss).

# Actor input Schema

## `continent` (type: `integer`):

0 = all continents

## `period` (type: `string`):

Time period to filter results by.

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

Type filter for results.

## Actor input object example

```json
{
  "continent": 0,
  "period": "live",
  "type": "both"
}
```

# Actor output Schema

## `dataset` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("romy/flightradar24-airport-disruptions-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("romy/flightradar24-airport-disruptions-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 '{}' |
apify call romy/flightradar24-airport-disruptions-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,romy/flightradar24-airport-disruptions-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/lVsr6t5nw4oZxFmd5/builds/xbCaNMYsYNXTdOeVx/openapi.json
