TRA INFO HUB

API Documentation

JSON exports for current TRA activations and Austria Widget airspace status, intended for external systems that need machine-readable airspace information.

What are TRAs?

TRAs are temporary reserved airspaces in Austria for VFR operations. They are located in airspace class G/W and are activated only for defined time windows; outside those times they are inactive.

Endpoints

export_activations.php

Returns exportable activation, extension and deactivation records whose start or deactivation time is within the last 26 hours and the next 12 hours. 

https://tra.airspace.at/export_activations.php?importer=abc123

export_activations_48h.php

Uses the same JSON structure, but extends the lookback window to the last 48 hours plus the next 12 hours. 

https://tra.airspace.at/export_activations_48h.php?importer=abc123

Only records from clubs and TRAs enabled for JSON export are included. Rejected requests and "no extension possible" notices are not part of this export.

Access

Importer hash

API consumers currently need an assigned importer hash. Pass it as the importer query parameter. The value shown in the examples is a placeholder and must be replaced with the assigned hash.

Firewall allowlisting

Please also provide the source IP address of the consuming system if possible. IP allowlisting for the firewall is currently optional, but may be required later or for selected integrations.

Free access

API access is provided free of charge. We are happy to present data users as partners on the homepage, including their logo where appropriate.

Support welcome

For commercial or profit-oriented projects, we appreciate voluntary financial support to help keep the service reliable, maintained and available to the community.

Missing access

If the export is not public and the hash is missing or invalid, the endpoint responds with HTTP 403 and a JSON error message.

JSON Structure

The response is a JSON array. Each array item represents one interaction and contains one or more affected airspaces. Every interaction is exported with its own activation_id for logging and protocol purposes.

Field Type Meaning
activation_id integer Unique interaction ID in the TRA Manager. Activations, extensions and deactivations each receive a separate activation_id.
addedTimestamp string UTC timestamp when the event was entered.
inverse boolean false for activations and extensions, true for deactivations.
activations array List of affected TRA intervals. One activation_id can contain multiple TRAs when they were activated or extended together.
airspace string Name of the TRA, for example TRA Almenland.
start string UTC start time. For deactivations this is the deactivation time.
end string UTC end time. For deactivations this is the previously planned end time.

Event Handling

Activation

An event with inverse=false opens the listed TRA for the exported time interval.

Extension

Extensions are exported with inverse=false as a separate interaction with its own activation_id. The start time remains the same as the original activation, while the end field contains the new end time.

Deactivation

A deactivation uses inverse=true. The start value marks the time from which the previous activation is shortened or cancelled; end contains the old planned end time.

Consumers should evaluate events by timestamp or activation_id and update their local state per airspace accordingly.

Examples

TRA Almenland activation and two extensions

The first event opens TRA Almenland until 11:00 UTC. The second event extends the same TRA until 13:00 UTC. The third event keeps the same start time and extends the TRA until ECET on that day, 18:49:34 UTC. 

[
    {
        "activation_id": 10421,
        "addedTimestamp": "2026-05-06 06:15:02",
        "inverse": false,
        "activations": [
            {
                "airspace": "TRA Almenland",
                "start": "2026-05-06 07:00:00",
                "end": "2026-05-06 11:00:00"
            }
        ]
    },
    {
        "activation_id": 10436,
        "addedTimestamp": "2026-05-06 10:32:18",
        "inverse": false,
        "activations": [
            {
                "airspace": "TRA Almenland",
                "start": "2026-05-06 07:00:00",
                "end": "2026-05-06 13:00:00"
            }
        ]
    },
    {
        "activation_id": 10458,
        "addedTimestamp": "2026-05-06 12:44:07",
        "inverse": false,
        "activations": [
            {
                "airspace": "TRA Almenland",
                "start": "2026-05-06 07:00:00",
                "end": "2026-05-06 18:49:34"
            }
        ]
    }
]

Multiple TRAs in one activation_id

This example shows three TRAs handled together. The activation_id 1188 opens all three until 12:00 UTC, 1189 extends all three until 16:00 UTC, and 1190 extends all three again until ECET, 18:49 UTC. Each interaction has one activation_id, while the activations array contains the affected airspaces. 

[
    {
        "activation_id": 1190,
        "addedTimestamp": "2026-05-06 15:35:32",
        "inverse": false,
        "activations": [
            {
                "airspace": "TRA SCHOECKL",
                "start": "2026-05-06 07:00:00",
                "end": "2026-05-06 18:49:00"
            },
            {
                "airspace": "TRA ALMENLAND",
                "start": "2026-05-06 07:00:00",
                "end": "2026-05-06 18:49:00"
            },
            {
                "airspace": "TRA BRUCK",
                "start": "2026-05-06 07:00:00",
                "end": "2026-05-06 18:49:00"
            }
        ]
    },
    {
        "activation_id": 1189,
        "addedTimestamp": "2026-05-06 10:15:21",
        "inverse": false,
        "activations": [
            {
                "airspace": "TRA SCHOECKL",
                "start": "2026-05-06 07:00:00",
                "end": "2026-05-06 16:00:00"
            },
            {
                "airspace": "TRA ALMENLAND",
                "start": "2026-05-06 07:00:00",
                "end": "2026-05-06 16:00:00"
            },
            {
                "airspace": "TRA BRUCK",
                "start": "2026-05-06 07:00:00",
                "end": "2026-05-06 16:00:00"
            }
        ]
    },
    {
        "activation_id": 1188,
        "addedTimestamp": "2026-05-06 06:45:06",
        "inverse": false,
        "activations": [
            {
                "airspace": "TRA SCHOECKL",
                "start": "2026-05-06 07:00:00",
                "end": "2026-05-06 12:00:00"
            },
            {
                "airspace": "TRA ALMENLAND",
                "start": "2026-05-06 07:00:00",
                "end": "2026-05-06 12:00:00"
            },
            {
                "airspace": "TRA BRUCK",
                "start": "2026-05-06 07:00:00",
                "end": "2026-05-06 12:00:00"
            }
        ]
    }
]

TRA Feldkirchen activation and deactivation

The first event opens TRA Feldkirchen until 14:00 UTC. The inverse event shortens the activation from 12:30 UTC onward. 

[
    {
        "activation_id": 20510,
        "addedTimestamp": "2026-05-06 06:45:11",
        "inverse": false,
        "activations": [
            {
                "airspace": "TRA Feldkirchen",
                "start": "2026-05-06 08:00:00",
                "end": "2026-05-06 14:00:00"
            }
        ]
    },
    {
        "activation_id": 20528,
        "addedTimestamp": "2026-05-06 11:58:44",
        "inverse": true,
        "activations": [
            {
                "airspace": "TRA Feldkirchen",
                "start": "2026-05-06 12:30:00",
                "end": "2026-05-06 14:00:00"
            }
        ]
    }
]