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.
• Counts a permitted origin-destination surface as an additional itinerary segment.
• Counts each intermediate surface as one total stopover, including co-terminal and ordinary surfaces.
• Validates major oneworld Explorer structure rules.
• Calculates counted continents and the likely fare product, defaulting to DONE3 for three-continent Business unless select-market IONE3 availability has been independently confirmed.
• Checks total segment limits.
• Checks Atlantic and Pacific crossing counts.
• Checks TC direction and broad TC backtracking.
• Checks origin and destination surface rules, including known exceptions.
• Checks country-of-origin international departure and arrival limits.
• Reports stopovers and transfers, treating X/AAA airports as transfers rather than stopovers.
• Flags more than 2 apparent stopovers in the continent of origin as a failure under the rules.
• Allows repeated intermediate stopover ports unless another rule is breached.
• Checks continent entry and exit counts.
• Checks repeated same-direction flown city pairs or sectors.
• Checks intra-continent flight-sector caps without counting surfaces as flights.
• Checks selected North America, Hawaii, Alaska, and Australia transcontinental restrictions.
• Lets the user select Economy, Business, or First, then derives the likely LONE, DONE, or AONE 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 marketing and operating carrier combinations against the product manifest.
• Resolves a default oneworld Explorer 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 confirm flight availability.
• It does not confirm award availability.
• It does not confirm paid fare availability.
• It does not determine whether IONE3 is offered from the itinerary's point-of-sale market.
• It does not price an itinerary.
• It does not validate taxes, carrier charges, or surcharges.
• It does not check married-segment logic, booking engine limitations, or airline-specific ticketing behaviour.
• 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 yet support manual booking-class override for cabin downgrades or unusual booking situations.
• 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 Explorer 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.
• DONE3 and IONE3 means the validator uses DONE3 as the default three-continent Business product. Rule 3015 also defines IONE3 for unspecified select markets, so its availability must be confirmed through the issuing airline, travel agent, or GDS.

Use this beta to test route structure, spot obvious oneworld Explorer 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.