US Airport-Pair Fare Benchmarks — Quarterly Markets, Per Record

Official source. No API key. Pay per record.

Who this is for and the decision it supports

Airline network planners, travel-analytics and pricing teams benchmarking average fares and traffic on US city-pair markets (US DOT DB1B).

One record answers: for this origin-destination market and quarter, what were the average fare, traffic and the largest/lowest-fare carrier shares — a route-economics and competitive benchmark.

What one record is

Each record is one DB1B city-pair market x quarter: city and airport ids, distance, passengers, average fare, and largest/lowest-fare carrier and their market shares and fares.

Your first run

Paste this input and run it:

{
  "maxRecords": 10
}

Run it and get clean per-market fare rows immediately — no DB1B zip wrangling. Here is a real record from that exact input:

{
  "record_id": "199311013510986ABECHI",
  "tbl": "Table 1a",
  "year": 1993,
  "quarter": 1,
  "citymarketid_1": 30135,
  "citymarketid_2": 30977,
  "city1": "Allentown/Bethlehem/Easton, PA",
  "city2": "Chicago, IL",
  "airportid_1": 10135,
  "airportid_2": 10986,
  "airport_1": "ABE",
  "airport_2": "CHI"
}

What the sample costs: $0.05 per record. The sample above delivers 10 records, so it costs at most $0.50.

Pulling in bulk

Raise Maximum records to pull the full historical panel of US city-pair markets. A buyer pulls the full multi-decade panel to model fare trends, market concentration and route economics.

To expand from the sample: raise Maximum records, and widen any filters shown in the input. You are billed only for records actually delivered, so a sample stays cheap and a full pull is predictable.

When to run it again

US DOT publishes DB1B quarterly; the actor returns the full series (earliest quarters first).

Update schedule: Quarterly — US DOT releases DB1B each quarter with a lag. Verified live: records carry year and quarter; the source is the official DB1B market table.

How this is different

US airport-PAIR (route/market) fares and traffic — distinct from the country-level EU Air Passenger Flow actor. This is route-level economics.

Limitations (source coverage vs product coverage)

• ROUTE/MARKET level (city-pair), and fares are AVERAGE market fares over a quarter — not bookable, current, or itinerary-level prices.
• By default the newest available quarter is returned first (currently 2026 Q1). Use the year (and optional quarter) inputs for a historical window; the full multi-decade panel back to 1993 stays reachable. Each record is one market-quarter, unique on the source key (tbl1apk).
• Excludes some ticket types per DB1B methodology.

FAQ

Are these current bookable fares?

No. They are quarterly average market fares from US DOT DB1B, historical by design.

Can I pull only the latest quarter?

Yes. Leave year blank for the newest quarter first; set year (and optional quarter) for a historical window, e.g. year=1993, quarter=1. An unavailable period returns an honest empty result.

Route or country level?

Route/market (city-pair) level.

Related actors

• eu-air-passenger-flow-records — country-level EU air passenger volumes
• company-data-enrichment-api — resolve carriers to legal entities
• world-bank-project-records — transport-sector development projects

Source, licence and how it is built

Source and licence are carried on every record (source, licence, attribution, observed_at). The actor reads only the official public endpoint, honours the source's robots and licence terms, and emits values unmodified with full provenance. Records are keyed on a stable id so re-runs upsert cleanly into a table you keep. Row delivery and billing are exactly equal: you are charged once per record delivered (push-then-charge), so an empty run costs nothing.

Part of NexGen Signal — official-source data products.