FG FareGlide

Fare snapshots

Recently found fare context from route searches.

Cached fare samples help benchmark route pages before travelers open current partner search results.

Data stance

Use snapshots as context, not as live prices.

These samples were generated from Travelpayouts / Aviasales data on May 29, 2026. Prices, availability, baggage rules, and booking conditions can change before checkout.

Snapshot routes
114
Market
US / USD
Airline hubs
8
Fare calendars
18

Route timing

Fare calendar pages for routes with enough month coverage

FareGlide now groups 49 cached samples into 18 route fare calendar pages when the snapshot set covers at least two sampled months. These pages help choose dates to recheck, not live booking prices.

Cached calendar layer

Use the month rows to pick a flexible-date starting point, then open provider results and confirm current fare rules before booking.

Browse route fare calendars

Airline context

Airline snapshot hubs from the same cached data

FareGlide now groups 164 cached fare samples into airline hubs only when an airline appears across enough distinct route snapshots. These hubs are context pages, not live route maps.

Airline snapshots

Use airline hubs, 114 origin-level appearances, and 114 destination-level appearances to find where carrier codes appeared in cached fare data.

Browse airline hubs Browse airlines by airport Browse airlines by destination

Lowest cached samples

Fare snapshots to investigate first

Nashville (BNA) to New York (NYC)

from $66

3 cached fare samples. 3 nonstop seen.

Sample date: Jun 11, 2026

Airline hubs: JetBlue

Route guide

Departure coverage

Airports with cached fare context

Austin (AUS) 16 routes / 25 samples / from $52 Cleveland (CLE) 15 routes / 27 samples / from $58 Cincinnati (CVG) 12 routes / 19 samples / from $49 Pittsburgh (PIT) 12 routes / 14 samples / from $88 Raleigh-Durham (RDU) 11 routes / 17 samples / from $36 Nashville (BNA) 11 routes / 16 samples / from $43 Kansas City (MCI) 11 routes / 19 samples / from $114 Columbus (CMH) 8 routes / 17 samples / from $114 Indianapolis (IND) 7 routes / 11 samples / from $71 Omaha (OMA) 5 routes / 5 samples / from $48 Milwaukee (MKE) 3 routes / 3 samples / from $132 Tulsa (TUL) 3 routes / 3 samples / from $164

Snapshot questions

How to use cached fare observations

The snapshot table is a planning layer. The booking decision still belongs on current provider results.

Are FareGlide fare snapshots live flight prices?

No. Fare snapshots are cached price observations from prior Travelpayouts / Aviasales data pulls. Use them as route context, then open partner results to confirm current fare, availability, baggage, and checkout rules.

Why does FareGlide show cached snapshots at all?

Cached snapshots help travelers compare route ranges before running a live search. They also help FareGlide decide which route, airline, and timing pages have enough evidence to publish.

How should I use a low cached fare sample?

Treat the low sample as a shortlist signal. Open the route guide, test nearby dates, compare airports when available, and verify the final live fare with the provider before booking.

Can a fare snapshot disappear from live results?

Yes. Airline inventory, provider rules, taxes, baggage, seat fees, and connection options can change after a cached sample is collected.