Online Hub Connectivity & Routing Analysis
1. Business Objective & Use Cases
When evaluating competitive schedules or building corporate flight options between secondary markets and long-haul destinations, airlines and travel managers need to find viable online (single-carrier, own-metal) connecting itineraries.
The Online Hub Connectivity Search evaluates whether a carrier offers a legal, commercially viable two-leg connection between a specific origin and destination via a nominated hub on a given travel date. It automatically verifies:
- Operating Metal: Both segments are operated by the same carrier on its own physical aircraft (excluding marketing codeshares).
- MCT & Layover Windows: Layover duration satisfies the airport's official Minimum Connection Time (MCT) and falls within a maximum allowable connection window (for example, up to 3 hours).
- Circuity Control: The detour distance via the hub does not exceed a maximum circuity threshold (for example, up to 1.50).
Target Audience
- Network & Schedule Planners: Audit connecting flow and competitive schedule parity on key city pairs.
- Corporate Travel & Revenue Managers: Identify single-ticket, single-airline itineraries for premium passengers.
- Alliance Managers: Benchmark own-metal connection quality against competitor alliance offerings.
2. Executable Natural Language Prompt
Copy and paste the prompt below into the analytics chat bar. Replace the bracketed variables with your desired route, hub, and travel date:
PROMPT3. How the Platform Works Under the Hood
The analytics engine joins the inbound leg (Origin -> Hub) and outbound leg (Hub -> Destination) across calendar date arrays and computes spatial circuity.
flowchart LR
A[Inbound Leg: Origin -> Hub] --> C{MCT & Layover Evaluation}
B[Outbound Leg: Hub -> Dest] --> C
C --> D{Circuity Filter <= 1.50}
D --> E{Match Found?}
E -- Yes --> F[Display Valid Connections]
E -- No --> G[Display Nearest Available Fallbacks]
Technical Invariants & SQL Logic
| Dimension | Source Field / Expression | Logic Description |
|---|---|---|
| Origin & Hub Segments | departure_station & arrival_station | Inbound: departure_station = [Origin] AND arrival_station = [Hub]. Outbound: departure_station = [Hub] AND arrival_station = [Dest]. |
| Strictly Online (Own-Metal) | flight_airline_designator & operating_airline_disclosure | Inbound carrier must equal outbound carrier (Inbound.Carrier = Outbound.Carrier). Excludes codeshares (operating_airline_disclosure IS NULL). |
| Date Expansion & Multi-Day Crossings | GENERATE_DATE_ARRAY + date_variation | Normalizes flight date with date_variation (+1 / +2 days) to accurately calculate the local arrival date at the hub. |
| Connection Time Calculation | DATETIME_DIFF | Layover minutes = Outbound.Dep_Local_DT - Inbound.Arr_Local_DT. Must be greater than or equal to MCT and less than or equal to the max window. |
| Circuity Factor (GCD) | Haversine Formula | Circuity = (Distance(Origin, Hub) + Distance(Hub, Destination)) / Distance(Origin, Destination), capped at 1.50. |
| Fallback Protocol | Sorting by connection time | If 0 rows satisfy the strict window, the engine automatically surfaces the closest available options sorted by connection duration. |
4. Step-by-Step Customization Recipes
Recipe A: Lock to a Specific Airline To check connection feasibility for a specific carrier (e.g., American Airlines):
Find all online own-metal connections for carrier AA from LHR to SYD via LAX on August 17, 2027. Max connection time: 4 hours.
Recipe B: Multi-Hub Comparison To evaluate which hub offers the best connection between two cities:
Find all online connections from LHR to MIA connecting through either JFK, BOS, or ORD on October 15, 2026. Show connection times and circuity factors.
Recipe C: Relaxed Stopover Window (4 to 8 Hours) To find long day-layover itineraries:
Find all online own-metal connections from CDG to HND via DOH on November 10, 2026, with a connection window between 4 and 8 hours.
5. Expected Output & Interpretation
1. Results Table (Strict Window vs. Closest Alternatives) If no flight meets a strict 180-minute threshold, the engine clearly states 0 matches were found and presents the nearest alternatives:
| Carrier | Inbound Flight | Aircraft | Outbound Flight | Aircraft | Origin Dep | Hub Arr | Hub Dep | Dest Arr | Connection Time | Circuity Factor |
|---|---|---|---|---|---|---|---|---|---|---|
| AA | AA 135 | Boeing 777-300ER | AA 73 | Boeing 777-300ER | 16:25 (Aug 17) | 19:35 (Aug 17) | 22:55 (Aug 17) | 07:05 (+2d) | 200 mins (3h 20m) | 1.22 |
| UA | UA 935 | Boeing 787-9 | UA 839 | Boeing 787-9 | 13:05 (Aug 17) | 16:10 (Aug 17) | 22:45 (Aug 17) | 07:00 (+2d) | 395 mins (6h 35m) | 1.22 |
2. Distance & Circuity Summary:
- Great Circle Distance (LHR to LAX): 8,781 km (5,456 mi);
- Great Circle Distance (LAX to SYD): 12,061 km (7,494 mi);
- Total Routed Distance: 20,842 km (12,950 mi);
- Direct Distance (LHR to SYD): 17,016 km (10,573 mi); * Circuity Factor: 20,842 / 17,016 = 1.22 (valid routing under the 1.50 ceiling).
6. Common Questions & Troubleshooting
Why was a partner flight excluded? If British Airways flies LHR -> LAX and American Airlines flies LAX -> SYD, this is an Interline / Codeshare Connection, not an Online Own-Metal Connection. To include partner airlines, specify "include oneworld alliance partners" in the prompt.
What does a Circuity Factor of 1.0 mean? A Circuity Factor of 1.00 means the hub lies directly on the Great Circle path between the origin and destination (zero detour distance). A factor of 1.22 represents a modest 22% detour, well within commercial viability.