Skip to main content
GET
Searches events: notable things that happened on frequency, such as a go-around, a laser strike, a diversion, or a gate return, each summarized and linked to the transmissions it was found in. Describe what you are looking for in plain words; results are ranked by how closely they match its meaning, not by exact words. An event is reported once and then updated as more transmissions about it arrive. Each event is returned as it was first reported, with all its updates nested under it in updates. Every update has its own event_update_id.

Query parameters

Takes since, until, callsign, facility_id, atc_channel_ids, and airline_id as described in Selecting data. The window selects by happened_at, not received_at: an event matches when its happened_at as first reported, or the happened_at of any of its updates, is in it. See Time windows by endpoint.
string
required
What you are looking for, e.g. laser strike on approach or aircraft returning to the gate.
string
required
Start of the window, inclusive. RFC 3339.
string
required
End of the window, inclusive. Must be after since and at most 48 hours later.
string
ICAO callsign, e.g. UAL406. Case-insensitive.
string
A facility_id from GET /api/v0/facilities.
string
Comma-separated atc_channel_id values, e.g. 4,7,8. Every channel must be available.
integer
An airline_id from GET /api/v0/airlines.
integer
default:"10"
Maximum events to return, 1 to 25.
Results are the best matches in one page; there is no cursor. With facility_id or atc_channel_ids, a page can hold fewer than limit events.

Response

array
The events, best match first.

Billing

Each search is charged as one event_query_page, at $1.00, even when nothing matches. Each event returned is charged as one event_pull, at $1.00. An event’s updates are included in its event_pull. See Pricing and Billing.

Errors