Our sources
Flight information is provided by AeroDataBox. Airgeek organizes that information into a shared Airport Board; it is not an official airline or airport service.
Special-livery descriptions are sourced from the AirportWebcams.net Special Liveries catalog. A description is matched to the aircraft registration supplied with the flight information.
Local fixture development and ordinary feature previews use sample data. The public Event view compares stored provider observations. It can show only changes captured between those observations; local review environments may show labelled synthetic demonstrations.
Airport coverage
Airgeek currently supports NRT, HND, SEA, and SFO. A refresh retrieves a rolling window from two hours before the refresh through ten hours after it.
Coverage focuses on scheduled commercial operations returned by the provider. General aviation, private, and military movements are outside the initial scope. The public board excludes flights identified as cargo; missing provider classification can affect that filtering.
This is not a complete record of every movement. Filters can narrow the view further, and changing a time filter cannot retrieve information outside the available snapshot.
Updates and freshness
Opening a board reads the most recent saved shared snapshot. The board periodically checks saved data; opening the app, switching views, changing filters, and checking saved data do not request a new flight-provider fetch. The selected Starter source profile polls NRT, SEA, and SFO every 15 minutes when enabled. The retained legacy profile polls NRT and SEA every eight hours until cutover. Other supported airports can show older saved data. Scheduling, provider limits, and outages can delay updates. The Starter profile retains up to 24 hours of flight history and pauses new source requests if the database reaches its storage safety ceiling. The latest successful snapshot can remain longer for stale fallback.
Timeline arranges reported flight movement times; it is not an aircraft-position track. Events is an observation history, not a complete airline or airport audit log. Alerts use available observations independently of the visible Event list.
“Updated” describes when Airgeek generated the snapshot, not when each detail changed at the airport. The provider’s information may already be delayed.
Source fetches share a 60-second per-airport cooldown. During provider errors or outages, Airgeek may keep the last available snapshot and mark it as stale. A fresh snapshot still does not guarantee that every field is accurate.
Times, aircraft, and runways
Scheduled, estimated or revised, and actual times describe different stages of a movement. Where a view shows one latest movement time, actual time takes precedence, followed by revised time and then scheduled time. Use Local or UTC to choose the time display.
Aircraft registrations, models, terminals, gates, and statuses may be missing or may change. Codeshare numbers can refer to the same operating flight.
A runway observation may be assigned, predicted, detected, provider-reported actual, airport-reported actual, or unknown. A runway designator by itself does not establish that it was used.
A special-livery match is a source-attributed catalog description, not confirmation of an aircraft’s current paint. Aircraft can be repainted, registrations can change, and catalog entries can become outdated.
Use the board responsibly
Use Airgeek to explore aviation activity. For check-in, boarding, connection planning, or other travel decisions, confirm details with the airline or airport. Do not use it for navigation, dispatch, or safety-critical operations.
Airgeek does not provide a public data-export license or a supported public API. Attribution identifies the sources; it does not grant permission to redistribute their data.