Important: Read Me First

• 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.
• Counts a permitted origin-destination surface as an additional segment and includes its mileage.
• Counts each intermediate surface as one total stopover, including co-terminal and ordinary surfaces.
• 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.
• Reserves CIR29SA for itineraries that include South America and uses CIR22 or CIR26 otherwise.
• 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.
• Warns when free stopover allowances are exceeded but paid additional stopovers remain possible.
• Checks the maximum one stopover in the country of origin rule.
• Checks free and maximum total stopovers per region separately.
• 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 separate marketing and operating carriers for each flown segment.
• Checks selected carrier combinations, including route-specific codeshare exceptions.
• Resolves a default Circle Pacific booking class by carrier and selected class.
• 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.
• Uses the current 50%, 75%, and 100% QFF status bonus rates for eligible QF, Jetstar Group, and AA-marketed flights.
• Gives surface sectors zero Qantas Points and zero Status Credits.

• 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 a permitted carrier combination operates the selected route.
• 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 expose the internal source mapping and interpretation record in the user interface.
• It does not replace the current oneworld Circle Pacific fare rules, Qantas earning tables, or airline ticketing advice.

• Routing looks OK means no implemented routing rule breach or itinerary-specific warning was detected. It does not guarantee that the itinerary can be booked or ticketed.
• Review needed means the routing may be valid, but an itinerary-specific condition, such as a rule exception or stopover interpretation, needs review.
• Rule breach detected means an implemented routing rule was 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.

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.