Your browser cannot create a WebGL context — this is usually caused by GPU acceleration being disabled, battery-saver mode, sandboxed environments (e.g. in-flight WiFi), or older hardware.
✓ Route input & CSV upload
✓ Results table & route calculations
✓ Export to CSV
✓ Save & load maps (logged in)
✗ Interactive map rendering
✗ Map snapshot / animation export
Try enabling hardware acceleration in your browser settings, or switch to a device with GPU support.
⚠️ Map disabled — GPU/WebGL unavailable
Format: ORIGIN-DEST[-DEST2-DEST3…] [value] — each waypoint can be IATA/ICAO or a coordinate pair as lat lon or lat, lon.
Network 1
Network 2
Paste two networks to compare. Format is the same as Route Input: ORIGIN-DEST [value], one per line.
Columns: origin,destination[,value][,color]. Origin/destination can be airport codes or coordinate pairs such as 46.236332388 6.105666244.
Enter IATA or ICAO codes separated by spaces, commas, or new lines.
These will plot as endpoints when “Endpoint Markers” is ON.
Show or hide route polylines
Fixed line color
Base width
Border
Match line colours
Dynamic endpoint
Scale
Plot byCount
Value
Box
100%
Custom airport labels are available to signed-in users.
Show the route code and value above the midpoint of each arc
Network 1
Network 2
Left = thinner · Mid = baseline · Right = thicker (×1.00)
Auto-detected from your data on Render/Animate.
Aircraft range
Performance
Range (nm)
Cruise Mach
TAS (kts)
Cruise FL
MTOW (kg)
Seats
Wind model
Condition
Month
Display
Show
Color
Plotted aircraft
Range circles
Use CODE@distanceunit ['label'], multiple lines; units: km, sm, nm.
Example: LHR@800km 'aircraft_A_range'.
Condition
Month
Applies wind at FL340 (250 hPa) using ERA5 climatology. "Calm" plots a standard geometric circle.
Map Options & Layers
12:00 UTC
Airport types
Jul
Source: NASA GIBS MODIS Terra LST (land only, monthly average). Winter months may have gaps at high latitudes.
Sea/Land colors are overridden after you change a color. “Reset colors” restores the underlying style and resets the pickers.
Enter one or more country names (comma-separated) (e.g. Canada, Norway, US:CA, CAN:ON), or use
Shade all countries with routes to seed the list from the current routes.
One rule per line: ORIGIN_CODE CSS_COLOR
e.g. LHR #000000 or EDI red.
Applies to all routes whose origin matches.
(Per-route overrides from the table still win.)
Live flights
Filter matches callsign prefix (first 2–3 letters). Example: BAW is British Airways.
Aircraft type depends on feed-provided fields; not all aircraft include type.
Results
Range circles
Center
Radius
Outline
Fill
Text
Fill on
Style
Aircraft range
Origin
Aircraft
Condition
Range N
Range E
Range S
Range W
Seats
Vis
Color
Endpoint colours
Code
Name / map label
Color
Country shading
Country
Color
Routes
Route Detail (inc multi-leg)
Custom Airport Labels
Edit the label for each airport, then click Plot to update the map.
Code / Coords
Label
km
mi
No origin set.
Uses OpenRouteService isochrone API to compute true drive-time catchments.
Population within —
—
Set an origin to calculate.
Filter destinations by their own catchment population (within the same catchment radius/drive-time). Leave blank for no limit.
Max range
Flight time
Using max range.
Filters destinations to a range band. Leave the max blank to derive from duration.
Assumes ISA speed of sound at cruise (a ≈ 573 kt).
Results
#
Code
Name
Country
Type
Runway
Dist (km)
Time
Top cities within max range
#
City
Country
Population
Distance (km)
Traffic flows
OD40 / DB1C Analytics · **BETA preview**
Pro
Updated: —
Latest OD40 release: —0 periods available
Paid traffic module scaffold
This UI is wired for the server-side OD40 / DB1C API. Set TRAFFIC_API_BASE to your API Gateway URL. If the API is unavailable, the panel falls back to preview data.
Enter only an origin for outbound flows, only a destination for inbound flows, origin + destination for point-to-point leg traffic, or a via airport to show traffic hubbing over that point.
Origin / from airport
Destination / to airport
Over / via airport
Carrier filter
Carrier basis
Default: origin only plots direct outbound flows from that airport.
Choose which itinerary depths to include. Non-stop is enabled by default; uncheck it to plot connecting-only traffic.
From
→
To
Ready. Query mode is inferred from Origin, Destination and Via inputs.
Traffic result
Demo result
Estimated pax
—
Grossed from sample
Sample pax
—
OD40 40% sample
Avg fare
—
Prorated where needed
Yield
—
U.S. cents / pax-mile
Estimate confidence:High (≥60 sampled)Medium (20–59)Low (6–19)Very low (<6)iConfidence reflects the raw sampled-passenger count behind each estimate. OD40 uses a 40% sample of DB1C tickets, so the relative standard error including the finite population correction is ≈ √(0.6 ÷ sample). Thin routes with few sampled passengers carry wider error bars — treat low-confidence rows as directional, not precise.
Component
Flow
Sample pax
Estimated pax
Avg fare
Yield ¢/mi
Share
#
Airport / market
Leg / path
Estimated pax
Avg fare
Yield ¢/mi
Share
#
Airport / market
Leg / path
Estimated pax
Avg fare
Yield ¢/mi
Share
#
Itinerary
Use case
Estimated pax
Avg fare
Yield ¢/mi
True O&D: all final destinations for passengers originating at the queried airport, ranked by total passengers. Includes both direct and connecting traffic.
#
Final destination
City
Type
Estimated pax
Avg fare
Yield ¢/mi
Share
Top destinations where no direct service exists from the origin — passengers connect via intermediate airports. Shows the via point(s) used.
#
Destination
City
Via (top routing)
Estimated pax
Avg fare
Yield ¢/mi
Share
Passenger flow visualization. Hover over any flow band to see volume, average fare, and yield. Width = estimated passengers.
