Route line
Places and sequence. It does not prove ticketing, protection, baggage, or current feasibility.
Routes desk / the handoffs behind the line
Build the whole itinerary.
A line through six cities can still hide seven tickets, two local dates, an airport change, a baggage stop, a surface sector, and no owner for the broken handoff. Keep the route, contract, and journey on separate layers.
One itinerary / six records
The route line is only the first layer.
Write what is actually known beside every record. A blank stays blank. Nothing here supplies a route, time, carrier, transfer, allowance, or recovery result.
- TK Record 01 Ticket
Seller, issuer, ticket relationship, and operating carrier
- CL Record 02 Clock
Local dates, offsets, scheduled times, and fixed deadlines
- AP Record 03 Airport
Exact facility, terminal, reporting point, and movement
- BG Record 04 Baggage
Allowance, tag destination, collection, recheck, and special items
- GR Record 05 Ground
Surface sector, duration evidence, provider, and next cutoff
- RC Record 06 Recovery
Change owner, evidence, spare time, and the broken-handoff plan
Six inspected destinations
Open the handoff that is still unresolved.
Every destination is an existing reviewed guide or local tool. None connects to a schedule, fare, route, alliance, airline, border, booking, account, or payment system.
01 Ticket identity
Name the product behind the route.
Separate a named alliance fare, another multi-carrier ticket, and a chain of separate bookings before comparing the shape.
Inspect the ticket structure
02 Itinerary method
Build around commitments, not dots.
Keep local dates, surface sectors, current border checks, recovery gaps, and change exposure beside every leg.
Build the itinerary method
03 Responsibility
Find where one ticket stops.
Record the issued ticket, operating carrier, baggage arrangement, and written recovery promise instead of trusting one booking display.
Map the ticket handoff
04 Whole journey
Put every phase on one ledger.
Add origin ground travel, airport work, flights, connections, arrival tasks, and the final journey without hiding missing evidence.
Plan door to door
05 Local calendar
Make the arrival date explicit.
Apply the offsets and elapsed duration you verified without letting the browser guess the origin or destination time zone.
Calculate the arrival clock
06 Recovery margin
Expose the work inside a connection.
Add the tasks and contingency that apply to this handoff without turning an estimate into a minimum, guarantee, or safe-time verdict.
Build a connection bufferThree different records
Do not ask one layer to prove the next.
A visually continuous route can sit on one ticket, several tickets, or a mix of flight and surface commitments. Industry systems can support shared processes without deciding the outcome for one passenger.
Ticket evidence
Seller, issuer, operating carrier, fare or product rules, and written responsibility for each handoff.
Journey evidence
Local dates, airports, bags, borders, surface sectors, deadlines, fixed commitments, and recovery space.
Current commercial examples
Similar shapes can carry different rules.
These first-party pages describe their own products. They are examples of product-specific evidence, not Iliamna endorsements, neutral comparisons, or rules to copy into another itinerary.
Three product families, more than one pricing basis.
The current page distinguishes oneworld Explorer, Global Explorer, and Circle Pacific, then links complete fare rules. The product name and current rules must be recorded before the route is judged.
Open the current product page →One ticket with its own itinerary conditions.
The current page publishes its own direction, stop, duration, transfer, and flight-count framework. It also says exceptions apply and that price and availability can change.
Open the current product page →Shared process is not a passenger promise.
IATA describes interline standards across ticketing, baggage, and irregular operations. Confirm the actual ticket and carrier terms instead of inferring a result from the infrastructure.
Read the framework →The line between the flights
A surface sector is still a handoff.
Record the ground or sea provider, exact start and finish points, local calendar, duration evidence, baggage plan, accessibility needs, change terms, and the acceptance deadline for the next flight.
A blank line on a flight ticket does not make the movement free, instant, available, or protected. The responsible current provider controls the real instruction.
Hard boundary
A planning record is not a trip result.
Iliamna cannot establish that a route is available, affordable, lawful, suitable, safe, protected, through-ticketed, through-checked, or recoverable. Entry, transit, health, and travel-document rules depend on the exact traveler, places, dates, and authorities.
Verify current airline, airport, border, health, land-transport, and ticket sources for the actual journey. Preserve the confirmations and rules used for the decision, then record later changes.
Evidence custody
Four sources. Six paths. No live answer.
Four fresh authoritative responses support the limited claims on this collection. The six internal destinations retain their own source packets, claims, research dates, and review triggers.
Research checked 26 July 2026
Commercial products and operational processes can change quickly. Recheck the current complete terms before relying on a proposed itinerary.