• In case of using more than one computer reservation system (CRS) , you must book and ticket within the same (CRS) .
  • Bookings should never be created for purposes other than confirmed travel ( e.g. to obtain fares ) . Applicable entries should be used to obtain fare quotes without using the END transaction if flights were booked for the purpose of obtaining a fare quote.
  • Travel agents who issue tickets on behalf of sub-agents must use the original live CRS booking.
  • Initials in lieu of first or last names are not permitted. A valid first and last name as published in the passenger’s travel document is required for all reservations, The full name and title of each passenger must be entered at the time of booking.
  • Name changes are only permitted for the purpose of correcting a misspelling of the passenger’s name. Any name changes are prohibited after ticket issuance.


  • Multiple bookings and cancellations for the purpose of extending the ticket time limit are not permitted as it results into unnecessary GDS cost due to booking and cancel actions.
  • Inserting fictitious ticket number/s by using the TKNM entry must never take place.
  • Inactive segments with status codes UC/UN/HX/NO must be deleted from bookings without delay (EgyptAir is going to charge for undeleted segments or segments that deleted less than 24 Hours before flight departure ) .


  • If a booking has a confirmed segment for a specific route, only one (1) Waitlist segment may be requested and held for the same confirmed routing.
    • Only two (2) waitlisted segments may be requested and held per route in a booking
  • Inactive segments with status codes HL must be deleted from bookings at least 24 hours before departure of the flight/s.
  • Waitlist segment not allowed within 24 Hours of flight departure .

Segment change

Segment status changes because of schedule changes, irregular operations, flight firming, flight cancellations or other circumstances will be queued to your CRS, and must be handled at least 24 hours prior to flight departure. This includes cancelling ticketed or UN ticketed segments with a status code of UN, NO, HX, WK, WL, or WN. You must also action or cancel segments with status codes UC, US, or DS.


  • Agents must refrain from creating individual bookings for a group of passengers exceeding nine (9). These passengers must be booked as a group using group booking procedures.
  • EgyptAir will not authorize passive segments on group bookings under any circumstances. In case of a change requiring a split from the original group PNR, you can reclaim the changed PNR and re-issue the ticket (s) to reflect the change.
  • Group bookings using (HN) 24 hours prior to flight departure is not permitted.


  • Duplicate bookings should never be created.
  • Action must be taken on any warning messages relating to duplicate bookings within 24 hours after receiving such message. Appropriate action is to cancel all duplicated items or the complete itinerary.

No Shows

The agent must advise their clients of the confirmed travel arrangements and the importance of notifying the airline or travel agent should the passenger not be able to make use of their confirmed travel commitments.

EgyptAir Action after a no-show accord:

The departure control status of a customer’s flight is incorporated in the Reservation system PNR where MS will analyse these statuses. All no-show bookings will be processed by cancelling the remaining MS flight segments in the PNR. No exceptions will be entertained

Passive Bookings

An acceptable passive segment is a segment entered into a GDS against an existing, identical booking in MS reservations system. Passive segments are also known as “information segments and have status codes of e.g. AK/BK/GK/MK/PK etc.

GDS subscribers must use the “Claim PNR” functionality where available instead of creating passive segments.

All GDS are required to inform airlines of passive segments i.e. to send a message to the relevant airline as soon as a passive segment is entered into a GDS and therefore give the airline a chance to process these bookings. If a passive segment has been created for no valid reason it can thus be rejected by the airline system. In this case the system will change the status code of the passive segment to “NO” and the segment will be returned to the GDS together with a SSR message stating the reason for the rejection, e.g.:

  • Retrieved segment in airline system shows waitlist and passive segment is confirmed.
  • No corresponding PNR found in airline system.
  • Invalid board or off point in passive segment.
  • Class shown with passive segment is different from the one held in airline PNR.

Where an agent uses more than one GDS in its business it must book and ticket each specific passenger itinerary within the same GDS.

Secure Flight Passenger Data (SFPD) :

Travel Agents must include Secure Flight Passenger Data (SFPD) including full name, date of birth, gender, and Redress Number if applicable, for each customer in every PNR that contained any segment to/from USA as required by the TSA (Transport and Security Administration).

Failure to provide the required SFPD at least 72 hours prior to departure may result in a debit memo.

PNRs created within 72 hours of departure must include SFPD when the PNR is initially booked.