A practical guide for travel agents on fixing the pricing error on flown segments in Amadeus when using FXP, FXX, FXB, or FXR commands.
One of the most frustrating Amadeus pricing errors happens when an agent tries to price an itinerary using commands such as FXP, FXX, FXB, or FXR โ and the system refuses the request. The reason is that one of the segments in the PNR has already been flown or its travel date has passed. Amadeus does not treat a flown segment as a regular active segment, so the standard pricing request is blocked. This article explains exactly why the error happens and gives you three reliable methods to price the itinerary depending on what you actually need to accomplish.
Why the Pricing Error Happens
This error appears when using pricing commands such as FXP, FXX, FXB, or FXR.
The cause: the system detects that the segment you are trying to price has already been flown, or its travel date has passed.
Example scenario: a segment shows status FLWN (flown), meaning it has already been used. The system will not price it as a regular active segment and blocks the standard pricing request.
Method 1: Price Only the Remaining Segments
If you only need to price the future part of the itinerary, specify the segment number directly and skip the flown one.
Example:
FXX/S6This prices segment 6 only, ignoring the flown segment 5.
Method 2: Price the Entire Itinerary Including the Flown Segment
If you need to price the whole trip for record purposes, override the past date check by adding the ticket issuance date.
Example:
FXX/R,14APR26The /R, entry forces the system to price the full itinerary despite the flown segment.
Method 3: Manual Fallback Using FQP + TTC
If the above methods still fail, use a detailed manual pricing entry with FQP to force the fare calculation.
Example structure:
FQPSHJ/AYY/CU/D25MAY26CAI/CX/D1JUL26SHJ/R,14APR26Once the system returns the pricing details, save them into the PNR using the TTC command.
For more help on saving pricing, refer to: HE TTC
Quick Fix Checklist
- Check the segment status in the PNR โ look for
FLWNor a past travel date. - Decide whether you need to price only the remaining segments or the whole itinerary.
- If pricing future segments only, use
FXX/S6. - If pricing the full trip, use
FXX/R,[issue date]. - If both fail, fall back to
FQPfor manual pricing. - Save the pricing result with
TTC.
Frequently Asked Questions
Why wonโt Amadeus price my itinerary?
Because one or more segments have already been flown or their travel date has passed. The system will not price a flown segment as a regular active segment.
How do I price only the remaining segments?
Specify the segment number directly, for example FXX/S6.
How do I price the full itinerary including the flown segment?
Add the ticket issuance date to override the past date check, for example FXX/R,14APR26.
What if FXX still fails?
Use a manual FQP entry to force the fare calculation, then save the result with TTC.
Conclusion
The pricing error on flown segments is not a system fault โ it is a built-in check that prevents pricing past-dated segments. To bypass it correctly, choose the method that matches your goal: use FXX/S6 to price only the remaining segments, use FXX/R,[issue date] to price the entire itinerary, or fall back to a manual FQP entry and save it with TTC when all else fails. Knowing which method to use saves time, avoids repeated failures, and keeps your pricing workflow smooth.
FREQUENT FLYER/SSR INPUT RESTRICTED
EXCHANGE DOC IN FO DOES NOT MATCH ETKT RECORD
CT RJT: ETKT RJT โ NO INTERLINE BETWEEN CARRIERS
