This is taking longer than expected.
This is taking longer than expected.
Trust & transparency
Aviation data changes constantly and different feeds answer different questions. This page states what FlightQ counts, what it estimates, how pages qualify for search, and where our confidence stops.
The /from tool is a focused current-schedule explorer: one row per nonstop destination, with grouped operating airlines and frequency. /airports is the broader airport profile, combining the same route layer with terminals, operator rankings, aircraft, geography and tracked-route summaries. Counts can differ only when a page clearly applies a stricter passenger-service, completeness or indexing filter.
Games with protected grading are generated deterministically or stored once per date, then graded by the server. Their browser-carried progress uses authenticated encrypted state, and each state token is consumed once in a shared database ledger so stale tokens cannot be forked into independent guesses. Missing or invalid source data fails closed instead of recycling a prior answer during a read request. Client-graded games are not described as cheat-resistant.
RailQ validates station IDs, unique and non-reversed route pairs, drawn geometry against the endpoint stations, a scheduled average speed envelope per service type, and a single named operator per route. A route carries verified status only when it has inspectable sources and a check date inside the freshness window below; that status is derived from the record, never asserted. Its legacy bank predates per-record citations and is still being reviewed. Ridership states what it counts: a line total, a route total, or an estimate marked with a tilde. TransitQ removes answer labels from initial geometry and keeps public preview/reveal controls behind administrator authentication. Neither game presents an unreviewed schedule clue as a live service guarantee.
Live forecast clues use Open-Meteo's daily maximum for the city's local calendar date and return the provider, fetch time, local date, timezone offset and definition. Legacy stored PassportQ values are labelled as legacy stored forecasts when their older schema lacks full timezone provenance and may have come from OpenWeatherMap. A current forecast is never substituted for an archived day's weather.
Population values are only comparable when the boundary and reference year are known; pages should show those fields when the source supplies them. Older records without both fields are not represented here as boundary-verified. Country, territory and nearby-airport labels follow their declared source conventions and can be corrected through the process below.
Getaway uses a frozen deterministic game-price model, not bookable fares. Trip Builder can combine provider results with planning estimates; estimated flights, rail fares and hotel costs must be labelled as estimates, and only a provider-returned quote may be called live. Prices are informational and can differ at booking.
Fleet pages currently publish corrected in-service counts only. Order counts are withheld while the upstream parser and field-level provenance are revalidated. Known not-yet-in-service variants are forced to zero in service, and hand-maintained corrections carry a review-by date that fails CI when it expires. Schedule-derived aircraft are labelled separately from curated fleet inventory.
Validated layouts must reproduce stored cabin totals exactly, but internal agreement does not prove airline accuracy. A public link is labelled source-linked. Source-confirmed is reserved for field-level evidence, bidirectional seat and cabin comparisons, immutable source fingerprints, and two recorded approvals. Neither status claims engineering-exact geometry unless engineering hardpoints exist.
Programmatic comparison pages are indexable only when both aircraft belong to a meaningful role class and at least three numeric specifications differ. Cross-class and near-duplicate comparisons can render for users but remain noindex and are omitted from the sitemap.
Pages show a source date or sample window when the underlying dataset supplies one. A page can remain available to people while being excluded from search when it is thin, stale, contradictory, retired or under review. Sitemap membership and page robots rules share eligibility functions on the data tools where those gates apply, so a noindexed URL is not intentionally submitted.
Use the same contextual report action available on FlightQ data pages. It includes the current page and prompts for the incorrect field and supporting evidence.
These are publication thresholds where the corresponding validator is implemented and review targets elsewhere. A target is not a claim that every legacy record has already completed that review.