Important: Read Me First
BetaProduct-specific notes for the oneworld Circle Pacific beta module.
Beta warning
This tool is for planning, checking, and discussion only. It is not an authoritative fare construction, ticketing, route availability, or Qantas Frequent Flyer earning decision. Always check the current oneworld Circle Pacific fare rules, Qantas earning tables, and the booking airline before making a booking.
Accepted input formats
Routing format uses - for flight sectors, // or /- for surface sectors, and X/AAA for a transit or layover. Example: HND-SYD-X/HKG-X/DOH-LHR//EDI-X/HEL-ORD-HND.
Fare calculation-style input with marketing carriers is also supported. Example: HND QF SYD AY X/HKG AY X/HEL BA LHR AA HND.
Do not mix routing format and fare-calculation format in the same input. If you only know some marketing carriers, use routing format first, then select carriers manually in the segment table.
What this tool does currently
- Parses normal flight sectors using "-".
- Parses surface sectors using "//" or "/-".
- Parses X/AAA transit markers, for example X/SIN.
- Parses fare calculation-style input with marketing carrier codes where supplied.
- Counts surface sectors as itinerary segments.
- Includes surface-sector mileage in the total calculated mileage.
- Uses the IATA CCD Multi-Airport Cities list to treat co-terminal surface sectors as a single stopover point where applicable.
- Checks the 16-segment Circle Pacific cap, including surface sectors.
- Calculates the likely ACIR, DCIR, or LCIR product from selected class and total mileage.
- Supports the 22,000-mile, 26,000-mile, and 29,000-mile South America Circle Pacific tiers.
- Checks for one North/Central Pacific crossing and one South Pacific crossing.
- Checks the broad Area 1 to Area 3 circle pattern used by Circle Pacific.
- Flags South America as not permitted on CIR22 and CIR26 itineraries.
- Checks that CIR29SA itineraries originate in or include South America.
- Checks the broad South Pacific via Chile requirement for CIR29SA where the current data supports it.
- Checks the origin and destination rule, including the same-point return requirement and known origin-destination surface exceptions.
- Checks prohibited travel via the Caribbean, Bermuda, Central America, and the South Asian subcontinent.
- Reports stopovers and transfers, treating X/AAA airports as transfers rather than stopovers.
- Checks the minimum 2 stopover requirement.
- Flags when the free stopover allowance is exceeded for the calculated Circle Pacific tier.
- Checks the maximum one stopover in the country of origin rule.
- Checks the maximum two free stopovers per region rule.
- Checks the maximum three transfers at any one city rule.
- Checks the maximum four international transfers from any one country rule.
- Lets the user select Economy, Business, or First, then derives the likely LCIR, DCIR, or ACIR product.
- Lets the user select current Qantas Frequent Flyer status.
- Lets the user select a marketing airline for each flown segment from the Circle Pacific permitted carrier set.
- Resolves a default Circle Pacific booking class by carrier and selected cabin.
- Maps the resolved booking class to a Qantas Frequent Flyer earn category.
- Uses QFF route-specific earning tables where a matching route rule is available.
- Uses QFF all-other mileage bands where no route-specific table matches.
- Calculates base Qantas Points and Status Credits for selected flown segments.
- Shows Qantas Points status bonus separately where eligible.
- Gives surface sectors zero Qantas Points and zero Status Credits.
What this tool does not do currently
- It does not confirm that a route is actually operated.
- It does not confirm that the selected airline operates the selected sector.
- It does not confirm that the selected airline is valid for that exact sector under current ticketing rules.
- It does not fully model every codeshare and affiliate-operated service exception.
- It does not confirm flight availability.
- It does not confirm award availability.
- It does not confirm paid fare availability.
- It does not price an itinerary.
- It does not validate taxes, carrier charges, premium economy surcharges, or stopover charges.
- It does not check minimum stay, maximum stay, reservation timing, ticketing deadlines, endorsements, or ticket stock restrictions.
- It does not yet support manual booking-class override for cabin downgrades or unusual booking situations.
- It does not yet model every practical ticketing interpretation of additional paid stopovers.
- It does not treat every broad metropolitan airport grouping as co-terminal. Co-terminal handling is based on the IATA CCD Multi-Airport Cities list used by this beta.
- It does not guarantee that every QFF route-specific override row is complete or classified perfectly.
- It does not guarantee that every fallback to an all-other mileage band is correct.
- It does not use Qantas internal mileage basis where that differs from the calculated great-circle distance shown by this tool.
- It does not yet include a full audit log explaining every rule decision.
- It does not replace the current oneworld Circle Pacific fare rules, Qantas earning tables, or airline ticketing advice.
How to interpret the result
- PASS means no implemented rule breach was detected.
- WARNING means the itinerary may be valid, but a rule exception, stopover interpretation, or ticketing practice issue needs review.
- FAIL means an implemented rule has been breached.
- Assumptions are known limitations of the current beta. They do not automatically make an itinerary invalid.
- All-other mileage band means no named QFF route-specific rule matched, so the fallback mileage table was used.
Co-terminal surface handling
Surface sectors still count as itinerary segments. Where a surface sector is between airports in the same IATA CCD Multi-Airport City, this beta treats that surface as a single stopover point for stopover-counting purposes.
For example, TSA//TPE is treated as a co-terminal surface within Taipei, and LGA//JFKis treated as a co-terminal surface within New York. The surface sector remains visible in the segment table.
This beta does not treat JFK//EWR or LGA//EWR as co-terminal surfaces under the IATA CCD list used by the tool. Some airlines or booking channels may still apply their own broader commercial interpretation, so check the current fare rules and the booking airline before relying on a surface-sector interpretation.
Circle Pacific-specific notes
Circle Pacific is mileage-tiered, so the calculated product is based on the selected class and the total calculated mileage, including surface sectors.
The 22,000-mile and 26,000-mile products do not permit an itinerary that originates in or includes South America. The 29,000-mile South America product requires the itinerary to originate in or include South America.
The South America product also has a specific South Pacific via Chile requirement. This beta checks the broad structure, but any real itinerary should still be reviewed against current fare rules and available QF-marketed services.
Recommended use
Use this beta to test route structure, identify obvious Circle Pacific rule issues, compare possible routings, and estimate QFF earning. Before booking, cross-check the itinerary against the current fare rules, the current Qantas earning tables, and the airline or travel agent issuing the ticket.