Airport Check-in User

Guide
for New Skies 3.x and 4.x
Edition 38
January 2017

WWW.NAVITAIRE.COM | © 2017 NAVITAIRE LLC AN AMADEUS COMPANY ALL RIGHTS RESERVED.

Disclaimer
This documentation is the confidential and proprietary information of Navitaire LLC and may be used,
modified, altered, copied, reproduced, or transferred only in accordance with a written license
agreement executed by Navitaire.
© 2017 Navitaire LLC An Amadeus company. All rights reserved.
 Document History

The purpose of the document history is to list the changes made to each edition of the Airport
Check-in User Guide, including the section affected and a description of the change.

Edition 38 (January 23, 2017)

• In version 4.x of New Skies, the following product name changes have been made:

— SkySchedule has been renamed as Schedule Manager

— SkySpeed has been renamed as SkySpeed Call Center Manager
As a result of these changes, all references to the products in the documentation have been
updated.

Edition 37 (November 16, 2016)

• Added instructions for Changing the Gender of a Passenger on page 9-35.

• Added steps for Unverifying a Passenger Document on page 9-36.

Edition 36 (September 8, 2016)

• Rebranded the document with new corporate cover page and logo.
• Added notes stating that carriers that use government security should not enable same-day
processing as the two processes are mutually exclusive. Notes added to the following
sections:

— CheckinConfig.xml on page 1-3

— Checking In Passengers with Same-day Return on page 4-10
— Checking In Passengers on Flights Requiring Government Validation on page 4-11

Edition 35 (June 2016) - Release 3.4.14

• Added result code 8670 to Checking In Passengers with APPS Validation on page 4-20. This
code has been added in support of TH APPS functionality.

Edition 34 (March 2016) - Release 4.1

• The SENDGOV command was modified to accept new parameters to enable carriers to meet
Canadian security requirements. All three commands are now included in the Passenger
Display Commands on page A-17.

— SENDGOVALL/manual
— SENDGOVALL/<country code>manual
— SENDGOVALL/<country code>/<authorization code>

Airport Check-in User Guide iii

 DOCUMENT HISTORY

• Added support for operational suffixes to Chapter 1, Introduction to Airport Check-in; Chapter 2,
Loading Flights; Chapter 3, Displaying Passenger Lists;Chapter 7, Boarding Passengers and Chapter
10, Displaying Flight Information.

Edition 33 (October 9, 2015) - Release 3.4.11 UPD 6 and 3.4.13

• Added the EC command to Chapter 9, Modifying Passenger Information and Appendix A,

Summary of Check-in Commands.

• Added several new commands to resubmit security data for any passenger requiring security
verification. All four commands are now included in the Summary of Display Commands on
page A-9 with detailed instructions for their use in the Resubmitting Security Data on page 4-26
section.

— SENDGOV<pax>
— SENDGOV<pax>/<2-char country code>
— SENDGOVALL
— SENDGOVALL/<2-char country code>
• Moved Displaying Passengers with Missing APIS Information on page 3-30, Displaying Checked
Passengers Who Require Secure Flight Validation on page 3-30 and Displaying Passengers Who Are
Not Cleared for APPS on page 3-30 to Displaying Passengers with Missing Security Information on
page 3-30 in Displaying Passenger Lists on page 3-1.

• Added the new UNAPISPRE command to the APIS command in Sending the APIS Report to
Customs on page 4-17 and Appendix A, Summary of Check-in Commands.

Edition 32 (June 9, 2015) - Release 3.4.12

• Updated Checking and Unchecking Passengers on a Marketing Code Share, Outbound Interline,
or Third-Party-Controlled Flight on page 4-30 to reflect new inter-DCS IATCI support.

• Added several new commands to remove passengers from marketing code share, outbound
interline, and third-party-controlled flights to the Summary of Display Commands on page
A-9.

— RMC
— RMCALL
— RMCS
— RMCSALL

Edition 31 (November 26, 2014) - Release 4.0

• Moved the CultureForDisplayingSSRsInCheckIn setting to the SkyPort Settings dialog in

CheckinConfig.xml on page 1-3.

• Added the Report section, which includes the SeatMapDisplayRow setting, to

CheckinConfig.xml on page 1-3.

Edition 30 (September 12, 2014) - Release 3.4.10

• Added information about standby no-show passengers to the definition

DeleteStandByPassengers in CheckinConfig.xml on page 1-3.

iv Airport Check-in User Guide

 DOCUMENT HISTORY

• Added the new country code parameter to the APIS command in Sending the APIS Report to
Customs on page 4-17 and Appendix A, Summary of Check-in Commands.

• Added InternationalBoardingTimeOffset and UseEstimatedTimesOnBoardingPass to

CheckinConfig.xml on page 1-3.

Edition 29 (May 2, 2014) - Release 3.4.9

• Added a note to Verifying all Passengers on page 4-14 explaining that FLTVERIFY/F validates
no-show passengers unless they are removed before the command is executed.

Edition 28 (December 13, 2013) - Release 3.4.6 UPD 11 and 3.4.8

• Added information about the history record created when a bag weight is changed to
Changing Bag Weights on page 9-32.

• Added a description of and handling instructions for result codes 8503 and 8630 to Checking
In Passengers with APPS Validation on page 4-20. These codes have been added in support of
UAE APPS functionality.
• Added Checking In Passengers with iAPP Validation on page 4-28. Interactive Advance
Passenger Processing is now supported for Taiwan.

Edition 27 (June 21, 2013) - Release 3.4.7

• Added a Prompt for Missing Seat During Boarding setting to the SkyPort Settings Dialog on
page 1-10 and documented the new functionality in Boarding Passengers by Scanning
Boarding Passes on page 7-3. (The Prompt for Missing Seat During Boarding setting replaces
the BoardWithoutSeat2D setting in CheckinConfig.xml.)
• Added a Display Downline Segments in Checkin setting to the SkyPort Settings Dialog on
page 1-10 and documented the new functionality in Checking In Passengers on page 4-4.

Edition 26 (June 17, 2013) - Release 3.4.6 UPD 5

• Added an APIS send before flight close setting to the SkyPort Settings Dialog on page 1-10 and
documented the new functionality in Closing Flights on page 8-4.
• Added a description of and handling instructions for result codes 8530 and 8620 to Checking
In Passengers with APPS Validation on page 4-20. These codes have been added in support of
APPS functionality for Bahrain and Saudi Arabia.

Edition 25 (May 10, 2013) - Release 3.5

• Added unit of measure to baggage weight displays for the .B and .B<pax> commands:

— Displaying the Baggage Count on page 10-4.

— Displaying the Baggage Checked In for a Passenger on page 9-29.
• Added three new settings to the SkyPort Settings Dialog on page 1-10.

— Domestic Max Bag Weight Limit.

— International Max Bag Weight Limit.
— Max Bag Weight Type.
• Added SeatMapDisplayRow setting to CheckinConfig.xml on page 1-3.

Airport Check-in User Guide v

 DOCUMENT HISTORY

• Added information about a new warning that a passenger’s maximum allowable baggage
weight has been exceeded to the following sections:

— Checking In Baggage Manually on page 6-7.

— Checking In Baggage Using Bag Drop Functionality on page 6-12.
• Described new functionality that interactively updates coupon status when passengers
check-in or un-check.

— Checking In Confirmed Passengers Individually or by PNR on page 4-5.

— Removing Confirmed Passengers from Check-in Individually on page 4-35.
• Added a new role setting -- Allow Agent to Override E-Ticket Coupon Status -- that enables
agents to override coupon status during check-in or un-check to Role Settings in Management
Console on page 1-12.

• Added a ticket type indicator to the F and .S passenger display commands.

— Displaying All Passengers on a Flight on page 3-3.

— Displaying Standby Passengers on page 3-10.
• Added an advanced mode for bag drop, along with the following uses for the RB and BT
commands.

— RB<pax>.
— RB<pax>/<bag>.
— BT<pax>/<bag>.
Refer to Checking In Baggage Using Bag Drop Functionality on page 6-12 and Printing Bag Tags
on page 6-16.
• Added a new role setting -- Bag Drop Mode -- that determines whether an agent has access to
the basic or the advanced bag drop functionality to Role Settings in Management Console on
page 1-12.

Edition 24 (November 16, 2012) - Release 3.4.6

• Added information about the new .TKT command:

— Displaying Passengers With Ticket Numbers on page 3-22.

— Summary of Display Commands on page A-9.
• Updated examples in Displaying the Downline Passenger Count on page 10-5 to clarify that the
departure time displayed is that of the first leg of the journey.
• Added several new commands to display, add, and edit destination addresses for passengers.
All three commands are now included in the Summary of Display Commands on page A-9
with detailed instructions for their use in the following sections:
— DEST<pax> - See Entering Destination Addresses on page 9-14.
— .DEST<pax> - See Displaying Destination Addresses on page 9-13.
— .DEST*<address> - See Modifying Destination Addresses on page 9-16.
• Added two new settings to the SkyPort Settings Dialog on page 1-10 and described these
settings to Checking In Baggage Using Bag Drop Functionality on page 6-12.

vi Airport Check-in User Guide

 DOCUMENT HISTORY

— Restrict Bag Drop to Current Station.

— Restrict Bag Drop to Flights Departing Within 24 Hours from Current Time.

Edition 23 (August 3, 2012) - Release 3.4.5

• Added information about PNRGOV messaging:

— Closing Flights on page 8-4.

— Sending PNRGOV Messages on page 4-19.
— Appendix A, Summary of Check-in Commands.
• Added clarification about how to print gate passes when Secure Flight is enabled to Printing
Gate Passes on page 4-40.

• Added three new settings to the SkyPort Settings Dialog on page 1-10.

— Restricted SSRs for Boarding Passes.

— Culture for displaying SSR on Boarding Passes.
— Validate Record Locator in 2D Barcode.
• Removed the DoNotValidateRecLocIn2DBarCode setting from CheckinConfig.xml on page
1-3.

Edition 22 (April 25, 2012) - Release 3.4.2 EMR 11

• Added DoNotValidateRecLocIn2DBarCode to CheckinConfig.xml on page 1-3.

• Added the Codes - Waive Fees role setting to Role Settings in Management Console on page
1-12 and indicated that NameChangeFee must be set to “allow” for SkyPort users. Also
added information about the role setting to Modifying Passenger Name Information on page
9-2.

Edition 21 (January 20, 2012) - Release 3.4.4

• Updated .B<pax> command description on Displaying the Baggage Checked In for a Passenger
on page 9-29 to indicate that the baggage display includes operating carrier information for
interline and code share itineraries.
• Added station code to the transit prompts for APPS in Checking In Passengers with APPS
Validation on page 4-20.

• Added a two new settings to the SkyPort Settings Dialog on page 1-10:
— Use Remote Printing.
— Landscape Wide Reports.

Edition 20 (July 15, 2011) - Release 3.4.2

• Added BoardWithoutSeat2D to CheckinConfig.xml on page 1-3 and Chapter 7, Boarding
Passengers.

• Added Allow Bag Tag Reprint to Role Settings in Management Console on page 1-12 and Printing
Bag Tags on page 6-16.

• Added two commands to Appendix A, Summary of Check-in Commands along with sections
to describe them:

Airport Check-in User Guide vii

 DOCUMENT HISTORY

— .DN. See Displaying Downline Passengers on page 10-6.

— .IN. See Displaying Inbound, Connecting Passengers on page 10-10.
• Updated Entering Travel Documents on page 9-9 with the information that travel document
numbers can now be up to 35 characters long.

Edition 19 (February 25, 2011) - Release 3.2.3

• Added three commands to Appendix A, Summary of Check-in Commands along with sections
to describe them:

— .DOC<pax>. See Displaying Passengers with International Documents on page 3-25.

— DOCX<doc>. See Deleting Travel Documents on page 9-12.
— .DOC*<doc>. See Modifying Travel Documents on page 9-11.
• Added RequireCompleteSFPD to CheckinConfig.xml on page 1-3.

Edition 18 (November 22, 2010) - Release 3.4

• Updated Closing Flights on page 8-4 to include information about exit row seating requirements.
• Added a note to Chapter 7, Boarding Passengers and Chapter 8, Closing Flights regarding the
accrual of Loyalty points.
• Added a Booking - Check In role setting for manual Secure Flight processing to Role Settings in
Management Console on page 1-12: Allow Manual Clearance.

• Added a Booking - Check In role setting for gate pass printing to Role Settings in Management
Console on page 1-12: Allow Gate Pass Printing.

• Updated Checking In Passengers with Secure Flight Validation on page 4-24 to include
information about the various Secure Flight modes available: normal, batch only, and outage.
• Moved the information on gate pass printing to Printing Gate Passes on page 4-40 and changed it to
include printing gate passes when Secure Flight is not needed.
• Added DefaultLocation and UseStationDisplayNameOnBagTag to CheckinConfig.xml on page
1-3.
• Updated Seat Properties on Seat Maps on page 5-2 to include information about custom seat
properties.
• Added Booking History For Bag Tag Printing and Booking History for Boarding Pass Printing to the
SkyPort Settings Dialog on page 1-10 and added links in Re-printing Boarding Passes on page
4-39 and Printing Bag Tags on page 6-16.
• Added customer recognition data to F and .S displays in Chapter 3, Displaying Passenger
Lists.

Edition 17 (August 4, 2010) - Release 3.3.0

• Added Displaying Checked Passengers Who Require Secure Flight Validation on page 3-30 and
added the .SF/BAD command to Appendix A, Summary of Check-in Commands.
• Added customer loyalty level to several command displays, similar to the F command.
• Added passenger count screen showing the “Other” column that displays when passengers have been
moved to a flight where their original cabin does not exist. Refer to Displaying the Passenger Count
on page 10-2.

viii Airport Check-in User Guide

 DOCUMENT HISTORY

Edition 16 (May 14, 2010) - Release 3.3

• Added Displaying the Baggage Allowance for a Passenger on page 9-31 and added the .BA<pax>
command to Appendix A, Summary of Check-in Commands.

• Removed BagWeightType from CheckinConfig.xml on page 1-3.

Edition 15 (March 19, 2010) - Release 3.2.1

• Added two new settings to CheckinConfig.xml on page 1-3: RestrictedSSRSInCheckIn and

CultureForDisplayingSSRsInCheckIn. These settings are used to control the display of SSRs in
passenger display and seat map commands throughout Check-in.
• Updated a role setting in Role Settings in Management Console on page 1-12: Check-in on Previous
Flight Required is now Allow Mid-journey Check-in.
• Updated Displaying All Passengers on a Flight on page 3-3 to include new functionality for sorting
SSRs in passenger display commands.
• Updated Displaying Passengers with SSRs on page 3-21, Displaying Passengers Who Have Not
Checked In on page 3-14, and Understanding the Seat Map on page 5-2 with information about
excluding certain SSRs from the .SSR, .N, and seat map displays.
• Added two new settings to CheckinConfig.xml on page 1-3: PremiumFareSeatMapDisplayCheckedIn
and PremiumFareSeatMapDisplayNotCheckedIn. These settings define what is displayed on the seat
map for passengers with premium fares.
• Updated Understanding the Seat Map on page 5-2 to include new functionality for indicating seats
of passengers with premium fares on the seat map.
• Added Boarding Passengers by Scanning Boarding Passes on page 7-3 to document the process for
scanning boarding passes to board passengers.
• Added Changing Bag Weights on page 9-32 to document the new CW command and added CW to
Appendix A, Summary of Check-in Commands.
• Updated Understanding Bag Tags and Baggage Messages in Multi-Carrier Situations on page 6-3
to refer to the New Skies Type B Messaging User Guide for details about BSM messages.

Edition 14 (January 18, 2010) - Release 3.2 R2

• Added Checking In Passengers with Secure Flight Validation on page 4-24 to document new
Secure Flight functionality.
• Added Printing Gate Passes on page 4-40 and added the GP command to Appendix A, Summary
of Check-in Commands.

• Added Displaying Passengers With Premium Fares on page 3-20 and added the .PS command to
Appendix A, Summary of Check-in Commands.
• Updated Chapter 6, Checking In Baggage to include information about the following:
— Checking in bags for passengers who have not yet checked in.
— Prompts for informational segments during baggage check-in.
• Updated Setting Flights to Close Pending on page 8-3 to include information about exit row seating
requirements and changing flights from closed to close pending status.
• Updated Assigning SSRs on page 9-6 to include information about adding or removing SSRs for
passengers who have already checked in.
• Added several new role settings to Role Settings in Management Console on page 1-12:

Airport Check-in User Guide ix

 DOCUMENT HISTORY

— Check-in on Previous Flight Required.

— Allow Creation of Ad Hoc Connections in IROP.
— Override Over-Wing Exit Row Requirement.
— Allow Add/Remove Of SSR On Checked In Passenger.
• Added new configuration settings to CheckinConfig.xml on page 1-3:
— PremiumFares.
— AllowBagCheckinForNonCheckedInPax.
— ManualBagTagCodes.
— SkipPassiveSegmentPromptForManualBag.
— EnforceCheckInPending.
• Added a section on the SkyPort Settings Dialog on page 1-10, including the following new
settings:
— Default Move SSR Option.
— Enforce Over Wing Row Requirements.

Edition 13 (August 25, 2009) - Release 3.2

• Added a section on Custom Commands on page A-51.

• Added DOCVERIFY/F command to Verifying all Passengers on page 4-14 and Summary of Action
Commands on page A-2.

• Added Displaying Passengers Who Do Not Have Assigned Seats on page 3-15 and added the .NS
command to Appendix A, Summary of Check-in Commands.

• Added new role settings to Role Settings in Management Console on page 1-12 to enable agents to
add or remove SSRs with fees for passengers who are already checked in and to check in passengers
with payments due.
• Added a section on Displaying Passengers with a Balance Due on page 3-38 and added the .BD
command to Appendix A, Summary of Check-in Commands.
• Added information about balance due warnings during flight close and passenger boarding to Closing
Flights on page 8-4 and Boarding Passengers Individually on page 7-2.

Edition 12 (February 27, 2009) - Release 3.1

• Moved the section on passengers who are missing or have invalid APIS information to Chapter 3,
“Displaying Passenger Lists,” on page 1.

• Updated Checking In Passengers with APIS Validation on page 4-12 with a note about e-Borders
functionality.
• Added information about APIS Quick Query (AQQ) to Checking In Passengers on Flights Requiring
Government Validation on page 4-11.

• Minor updates and corrections.

Edition 11 (October 14, 2008)

• Updated the APPS boarding directives listed in Checking In Passengers with APPS Validation on
page 4-20.

x Airport Check-in User Guide

 DOCUMENT HISTORY

• Added the new manual bag tag formats to Checking in Baggage (Pre-printed Bag Tags) on page
6-9.
• Updated the information about the “in transit” prompts in Checking In Passengers with APPS
Validation on page 4-20.

Edition 10 (August 21, 2008)

• Added a note about dependencies in SkyLedger to Closing Flights on page 8-4.

• Updated CheckinConfig.xml on page 1-3 and Checking In Passengers on page 4-4 to reflect
changes to the functionality that enables passengers to check in for connecting flights.

Edition 9 (July 9, 2008)

• Added DCCOffer settings to CheckinConfig.xml on page 1-3.

• Updated the SkyPort > FLIFO role in Role Settings in Management Console on page 1-12 to reflect
that choosing “none” disables all Check-in functionality for the user.
• Changed all Task Guide references to Functional Knowledge Base.

Edition 8 (April 17, 2008)

• Added new roles for baggage weight requirements to Role Settings in Management Console on page
1-12.
• Added several new configuration options to CheckinConfig.xml on page 1-3:

— PassengerDocumentReport on page 1-4.

— IncludeIATCIFlightsForInboundAndDownlineDisplays on page 1-4.

— DisplayInboundAndDownlinePaxNames on page 1-4.

— PrintConjunctiveBagTags on page 1-6.

— TransferConjunctionIndicator on page 1-6.

• Updated Checking In Baggage Manually on page 6-7 with steps to add bag weights as required by
the airline.
• Added information about IATCI functionality to the following sections:
— Checking In Passengers on page 4-4.

— Removing Passengers from Check-in on page 4-35.

— Assigning Seats on page 5-6.

— Checking In Baggage Manually on page 6-7.

— Removing Baggage from Check-in on page 6-15.

— Assigning SSRs on page 9-6.

— Removing SSRs on page 9-8.

— Entering Travel Documents on page 9-9.

— Entering Birthdates on page 9-21.

— Maintaining Other Airline Frequent Flyer Information on page 9-22.

— Associating Passenger Names with Customer Accounts on page 9-25.

Airport Check-in User Guide xi

 DOCUMENT HISTORY

• Added a note to Displaying the Downline Passenger Count on page 10-5 and Displaying the
Inbound, Connecting Passenger Count on page 10-9 about configuring the .I and .D commands for
IATCI.
• Added Understanding Bag Tags and Baggage Messages in Multi-Carrier Situations on page 6-3.
• Added several commands to Appendix A, Summary of Check-in Commands:
— .APPSOVR
— .APC
— APC<pax #>
— APPSALL
• Changed all SkyManager references to Management Console.
• Removed the APIS information appendix. The information is now located in the New Skies
Functional Knowledge Base.

Edition 7 (July 25, 2007)

• Made minor updates and corrections throughout.

Edition 6 (April 27, 2007)

• Added .MC command to Displaying Code Share Passengers that are Associated with Another
Marketing Designator on page 3-16 and to Appendix A, Summary of Check-in Commands.

• Added MC and MCS commands to Checking and Unchecking Passengers on a Marketing Code
Share, Outbound Interline, or Third-Party-Controlled Flight on page 4-30 and to Appendix A,
Summary of Check-in Commands.

• Added .FC command to Displaying All Passengers on a Flight on page 3-3 and to Appendix A,
Summary of Check-in Commands.

• Updated Chapter 5, Assigning Seats and Appendix A, Summary of Check-in Commands to reflect
changes to SM and ST commands.
• Updated Role Settings in Management Console on page 1-12 to reflect new booking -- check-in
roles.
• Changed all references to SkyManager to Utilities.

Edition 5 (February 2007)

• Updated Printing Bag Tags on page 6-16 to indicate that the BT command can now be used to print
initial bag tags in addition to re-printing them.
• Added Chapter 11, Creating Vouchers and updated Appendix A, Summary of Check-in
Commands.

Edition 4 (December 2006)

• Made necessary formatting changes to facilitate the creation of HTML output in addition to previously
available PDF.

Edition 3 (October 2006)

• Added new role settings to Role Settings in Management Console on page 1-12.

xii Airport Check-in User Guide

 DOCUMENT HISTORY

• Added LL command to Loading Flights from the Command Prompt on page 2-8 and to Appendix
A, Summary of Check-in Commands.
• Added product class code to passenger list screen in Displaying All Passengers on a Flight on page
3-3.
• Added II command to Re-printing Itineraries on page 4-39 and to Appendix A, Summary of
Check-in Commands.

• Added Checking In Baggage Using Bag Drop Functionality on page 6-12.

• Added Changing Standby Priority Codes on page 9-4.

• Added DOCS command to Entering Travel Documents on page 9-9 and to Appendix A, Summary
of Check-in Commands.

Edition 2

• Added Associating Reservations with Customer Loyalty Accounts on page 9-27.

• Added Maintaining Other Airline Frequent Flyer Information on page 9-22.

• Updated Entering Travel Documents on page 9-9.

• Added Displaying Passengers Associated with Customer Loyalty Programs on page 3-34.

• Added information about paper tickets to Checking In Passengers on page 4-4.

• Added information about bag tag destination mismatches to Checking In Baggage Manually on page
6-7.
• Updated the layout information for CheckinConfig.xml on page 1-3.

• Updated the Check-In commands in Appendix A, Summary of Check-in Commands.

• Updated the description of the Passenger Count screen.

First Edition

• No history recorded for first edition.

Airport Check-in User Guide xiii

 DOCUMENT HISTORY

xiv Airport Check-in User Guide

Contents
Contents

Document History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DH–iii

Document History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DH–iii

1 Introduction to Airport Check-in . . . . . . . . . . . . . . . . . . . . . . .1–1

Customizing Airport Check-in. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
CheckinConfig.xml. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3
SkyPort Settings Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10
Role Settings in Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–12
Logging On and Accessing Airport Check-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–18
Logging Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–21
Understanding the Command Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–21
Using Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–23

2 Loading Flights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–1

Loading Flights Directly after Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2
Loading Flights from the Command Prompt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8
Loading Flights from the Flight List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9

3 Displaying Passenger Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–1

Displaying All Passengers on a Flight. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–3
Displaying All Passengers on the Same Reservation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–8
Displaying All Passengers on the Indicated Reservation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–8
Displaying Passengers by Surname. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–9
Displaying Checked-in Passengers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–9
Displaying Standby Passengers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–10
Displaying Boarded Passengers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–13
Displaying “Un-boarded” Passengers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–13
Displaying Passengers Who Have Not Checked In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–14
Displaying Passengers Who Do Not Have Assigned Seats . . . . . . . . . . . . . . . . . . . . . . . . . . 3–15
Displaying Code Share Passengers that are Associated with Another Marketing Designator
3–16
Displaying Thru Passengers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–17
Displaying Connecting Passengers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18
Displaying Upgraded Passengers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18
Displaying Passengers With Premium Fares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–20
Displaying Passengers with Manifest Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–20
Displaying Passengers with SSRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–21
Displaying Passengers With Ticket Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–22
Displaying Passengers with International Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–25
Displaying Passengers without International Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . 3–26
Displaying Passengers with APIS Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–27

Airport Check-in User Guide xv

 CONTENTS

Displaying Passengers with Missing Security Information . . . . . . . . . . . . . . . . . . . . . . . . . . 3–30

Displaying APPS Overrides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–33
Displaying Passengers with Customer Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–33
Displaying Passengers Associated with Customer Loyalty Programs. . . . . . . . . . . . . . . . . 3–34
Displaying Passengers by Sequence Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–35
Displaying the Passenger Assigned a Specific Seat. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–35
Displaying Passengers on Locked Reservations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–35
Displaying Passengers with a Balance Due . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–38

4 Checking In Passengers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–1

Understanding Sequence Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3
Checking In Passengers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4
Clearing Locked Passengers from a Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4
Checking In Confirmed Passengers Individually or by PNR . . . . . . . . . . . . . . . . . . . . . . 4–5
Checking In All Confirmed Passengers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–7
Checking In Standby Passengers Individually or by PNR . . . . . . . . . . . . . . . . . . . . . . . . . 4–7
Checking In All Standby Passengers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–9
Checking In Passengers with Same-day Return. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–10
Checking In Passengers on Flights Requiring Government Validation . . . . . . . . . . . . . 4–11
Checking and Unchecking Passengers on a Marketing Code Share, Outbound Interline, or
Third-Party-Controlled Flight. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–30
Removing Passengers from Check-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–35
Removing Confirmed Passengers from Check-in Individually. . . . . . . . . . . . . . . . . . . . 4–35
Removing All Confirmed Passengers from Check-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–36
Removing Standby Passengers from Check-in Individually . . . . . . . . . . . . . . . . . . . . . . 4–37
Removing All Standby Passengers from Check-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–37
Re-printing Itineraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–39
Re-printing Boarding Passes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–39
Printing Gate Passes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–40

5 Assigning Seats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5–1

Understanding the Seat Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–2
SSRs on Seat Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–2
Seat Properties on Seat Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–2
Configuring Premium Fares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–4
Displaying the Seat Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–5
Assigning Seats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–6
Assigning Seats for Connecting Flights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–7
Assigning Seats on Thru (Direct) Flights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–8
Merging Seat Maps for Thru Flights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–8
Assigning Seats for a Specific Leg of a Thru Flight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–10
Changing Seat Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–12

xvi Airport Check-in User Guide

 CONTENTS

Holding or Blocking Seats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–13

Unblocking Seats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–16

6 Checking In Baggage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6–1

Understanding Bag Tag Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–2
Understanding Bag Tags and Baggage Messages in Multi-Carrier Situations . . . . . . . . . . . 6–3
Displaying Bag Tag Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–5
Selecting a Bag Tag Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–6
Checking In Baggage Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–7
Checking In Baggage (Automatic Bag Tag Printing). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–7
Checking in Baggage (Pre-printed Bag Tags) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–9
Checking In Baggage Using Bag Drop Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–12
Removing Baggage from Check-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–15
Printing Bag Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–16
Performing Positive Bag Tag Matching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–17

7 Boarding Passengers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7–1

Boarding Passengers Individually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–2
Boarding Passengers by Scanning Boarding Passes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–3
Boarding All Passengers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–5
Automated Boarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–5
Un-boarding Passengers Individually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–6
Un-boarding All Passengers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–7

8 Closing Flights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–1

Understanding Flight Status Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–2
Setting Flights to Close Pending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–3
Closing Flights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–4
Opening Closed Flights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–6

9 Modifying Passenger Information . . . . . . . . . . . . . . . . . . . . . . .9–1

Modifying Passenger Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–2
Changing Standby Priority Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–4
Changing a Passenger Title to “CHD” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–5
Assigning SSRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–6
Removing SSRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–8
Entering Travel Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–9
Modifying Travel Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–11
Deleting Travel Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–12
Displaying Destination Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–13
Entering Destination Addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–14

Airport Check-in User Guide xvii

 CONTENTS

Modifying Destination Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–16

Entering Passenger Emergency Contact Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–17
Displaying Passenger Emergency Contact Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–18
Modifying Passenger Emergency Contact Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–19
Deleting Passenger Emergency Contact Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–20
Entering Birthdates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–21
Maintaining Other Airline Frequent Flyer Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–22
To add frequent flyer information for a passenger:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–22
To modify frequent flyer information for a passenger:. . . . . . . . . . . . . . . . . . . . . . . . . . . 9–22
To remove a passenger’s frequent flyer information: . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–23
Associating Passenger Names with Customer Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–25
Removing Customer Account Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–26
Associating Reservations with Customer Loyalty Accounts . . . . . . . . . . . . . . . . . . . . . . . . . 9–27
Displaying the Baggage Checked In for a Passenger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–29
Displaying the Baggage Allowance for a Passenger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–31
Changing Bag Weights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–32
Displaying Manifest Comments for a Passenger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–33
Displaying the SSRs Assigned to a Passenger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–34
Changing the Gender of a Passenger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–35
Unverifying a Passenger Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–36

10 Displaying Flight Information . . . . . . . . . . . . . . . . . . . . . . . . .10–1

Displaying the Passenger Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–2
Displaying the Baggage Count. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–4
Displaying Downline Passenger Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–5
Displaying the Downline Passenger Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–5
Displaying Downline Passengers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–6
Displaying Inbound Passenger Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–9
Displaying the Inbound, Connecting Passenger Count . . . . . . . . . . . . . . . . . . . . . . . . . . 10–9
Displaying Inbound, Connecting Passengers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–10
Displaying Valid Standby Priority Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–13
Displaying Valid SSR Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–14
Viewing the Status History of a Flight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–15

11 Creating Vouchers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11–1

Creating Vouchers for Individual Passengers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–2
Creating Vouchers for All Passengers on a Flight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–4

A Summary of Check-in Commands . . . . . . . . . . . . . . . . . . . . . . A–1

Summary of Action Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–2
Summary of Display Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–9

xviii Airport Check-in User Guide

 CONTENTS

Summary of Commands by Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–14

Flight Listing and Loading Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–15
Flight Opening/Closing Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–15
Passenger Display Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–17
Passenger Check-in Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–19
Seat Map/Seat Assignment Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–22
Itinerary and Boarding Pass Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–22
Baggage Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–23
Standby Passenger Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–23
Passenger Boarding Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–24
Passenger Information Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–24
Special Service Requests (SSRs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–26
Infant and Child Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–26
Flight Information Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–26
Voucher Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–26
Shortcuts to Other Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–27
Miscellaneous Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–27
Command Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–28
AB Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–29
.B Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–29
B Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–29
BD Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–30
BP Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–30
BRD Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–31
BS Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–31
BTP Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–32
C Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–32
CS Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–34
CU Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–35
.DOC Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–35
F Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–36
.FI Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–36
H Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–37
IT Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–37
J Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–38
L Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–38
LF Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–39
.LP Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–39
LP Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–40
.M Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–40
MB Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–40
MC Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–41

Airport Check-in User Guide xix

CONTENTS

MCS Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–41

PNRGOV Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–42
.Q Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–43
R Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–43
RB Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–44
RMC Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–44
RMCS Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–44
RS Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–45
RZ Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–46
SA Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–46
SM Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–47
SSR Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–48
UNAPISPRE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–48
US Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–49
.X Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–49
Custom Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–51
Creating Custom Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–51
Configuring Custom Commands in Management Console. . . . . . . . . . . . . . . . . . . . . . . A–53

B Shortcut Commands to Other Management Console . . . . . . . . B–1

Shortcut to General Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–2
Shortcut to Irregular Operations (IROP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–3
Shortcut to Flight Following (FLIFO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–4
Shortcut to Flight Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–5
Shortcut to the Reservations Tool (RZ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–6
Shortcut to the Aircraft Zone Report (23) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–7

C Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C–1

xx Airport Check-in User Guide

1 Introduction to Airport Check-in

Airport Check-in enables you to check in passengers, board and un-board passengers, open and
close flights, change the status of flights, and perform other tasks related to passenger check-in.
Its functionality is dependent on the individual configurations requested by your airline.
If you have questions regarding your Airport Check-in configuration, please contact a Navitaire
representative.

In this chapter:

• Customizing Airport Check-in on page 1-2

• Logging On and Accessing Airport Check-in on page 1-18
• Logging Out on page 1-21
• Understanding the Command Prompt on page 1-21
• Using Online Help on page 1-23

Airport Check-in User Guide 1–1

 CHAPTER 1 INTRODUCTION TO AIRPORT CHECK-IN
Customizing Airport Check-in

Customizing Airport Check-in

You can customize Airport Check-in’s many settings to suit your airline. For example, you can
determine what information displays on boarding passes, the process for checking in baggage,
whether agents can create vouchers, and so on.
Most of the customization is done in CheckinConfig.xml. However, some customization must be
performed by Navitaire. This section describes the configurable settings, organized by category.
For any settings that require customization by Navitaire, please contact a Navitaire
representative.
Keep in mind that changing these settings affects the functionality in Airport Check-in. It is good
practice after configuring each setting to review the settings in Airport Check-in to ensure it
works according to the needs of your airline.
Refer to the following sections for more information on Check-in configuration settings.
• CheckinConfig.xml on page 1-3
• SkyPort Settings Dialog on page 1-10
• Role Settings in Management Console on page 1-12

1–2 Airport Check-in User Guide

 CHAPTER 1 INTRODUCTION TO AIRPORT CHECK-IN
Customizing Airport Check-in

CheckinConfig.xml
Many configuration settings for Airport Check-in are contained in CheckinConfig.xml. This file
can be accessed in Management Console (System Configuration > Resource Management). The
Resource Management directory has the following structure.

Note New Skies recognizes only the CheckinConfig.xml file located in the Default directory.
Location-specific CheckinConfig.xml files are ignored.
CheckinConfig.xml is split up into the following sections: CheckIn, Boarding, FlightInfo,
FlightClosure, RZ, and Report. The settings (tags) in each section of the file are specific to the
function denoted by the section header. For example, settings in the Boarding section affect the
process of boarding passengers in Airport Check-in, whereas settings in FlightClosure affect the
process of closing flights.
Before editing CheckinConfig.xml, it is recommended that you save the file to your computer
hard drive and make the edits using either a text editor, such as Notepad or WordPad, or an XML
editor. Once you modify the file, browse and open it from the Resource Management dialog in
Management Console. For more information on CheckinConfig.xml, refer to the help files for
Management Console.
Each section of CheckinConfig.xml is explained in the following tables.

CheckIn Settings

Setting Description

CheckIn Parent tag for check-in settings.

PremiumFares Comma-delimited list of premium fares. This list

defines which fares are included in the display when
an agent enters the .PS command. It also defines
which fares are indicated on the seat map.

PremiumFareSeatMapDisplayCheckedIn Character to display on the seat map if the passenger

has a premium fare and is checked in.

PremiumFareSeatMapDisplayNotChecke Character to display on the seat map if the passenger

dIn has a premium fare and is not checked in.

AllowForceFLTVERIFY If set to true, you must issue a FLTVERIFY/F or

DOCVERIFY/F command on all international flights.

Airport Check-in User Guide 1–3

 CHAPTER 1 INTRODUCTION TO AIRPORT CHECK-IN
Customizing Airport Check-in

Setting Description

FlightDepartureOffset The manifest prompt is highlighted when the flight is

within this number of minutes from departure. For
example, if the FlightDepartureOffset is 20, the
manifest prompt for a flight 15 minutes from
departure is highlighted.

EnforceCheckInLid If set to true, you can check in passengers until you

reach the check-in lid. Once you reach the lid you
cannot check in any more passengers.

IncludeIATCIFlightsForInboundAndDow If set to true, the .I, .IN, .D, and .DN commands
nlineDisplays include passengers on inbound and downline IATCI
flights as well as any passengers who have booked
connections or point-to-point flights within a 24-hour
period in the passenger counts.

DisplayInboundAndDownlinePaxNames If set to true, the .I and .D commands include

passenger names for inbound and downline IATCI
flights as well as passengers who have booked
connections or point-to-point flights within a 24-hour
period.

CheckInForConnectingFlights Defines how passengers are checked in. Enter one of

the following values.

• CheckinJourney (default) - Checks the

passengers in for the entire journey.

• CheckinJourneyPromptFinalDestination -
Prompts the agent to enter the final destination
for check-in. Passengers are not checked in
beyond that destination.

• CheckinSegment - Checks the passengers in only

for the current segment.

AutoSeatAssignmentForConnectingFlig If set to true, when assigning a seat for a passenger

hts on a segment with a “connection”, the passenger is
automatically assigned a seat on the connecting
segment.

ReplaceSpecificSeatRequestIfNotAvaila If set to true, when a specific seat requested is

ble available for the first segment but not for the second
segment, a different seat is assigned for the second
segment. If set to false, seat assignment succeeds for
the first segment but fails for the second. If this seat
assignment is done during check-in, the passenger is
not checked in for either segment.

PassengerDocumentReport If set to true, agent is prompted as to whether or not

APIS detail is required for the flight on the Flight
Manifest report.

PromptSecurityQuestions If set to true, agent is prompted to ask up to the

three standard security questions when checking in
passengers (U.S. carriers only). Each question is
defined under SecurityQuestions (described in the
following row).

SecurityQuestions Parent tag for security questions.

Question Repeat this tag for each security question you want
the agent to be prompted to ask.

1–4 Airport Check-in User Guide

 CHAPTER 1 INTRODUCTION TO AIRPORT CHECK-IN
Customizing Airport Check-in

Setting Description

CapitalizeNames If set to true, passenger names are displayed

capitalized in Check-in, regardless of how they were
entered into the system.

DefaultLocation Location to be used for APPS messaging when an

agent logs into SkyPort using a non-station location.

AircraftZoneReportByAdult If set to true, the zone report is grouped by “adult”

rather than by “male” and “female”.

RemoveSeatPrompt If set to false, the prompt to remove seat

assignments when unchecking passengers is
suppressed.

RequireCompleteSFPD If set to true, full Secure Flight passenger data

(SFPD) is required at check-in.

RestrictedSSRsInCheckIn Comma-delimited list of SSRs that are not to be

included in the .SSR, .N, and seat map command
displays.

CultureForDisplayingSSRsInCheckIn Indicates the culture to be used for sorting SSRs.

Configure SSR sorting preferences by culture in the
[Moved to SkyPort Settings dialog in
Localization and Sorting dialog in Management
4.0]
Console (System Configuration > Localization and
Sorting).

EnforceCheckInPending Set to true to prevent agents from adding baggage to

a flight that has close pending status. The default is
false and allows agents to add bags to close pending
flights.

SeatMapDisplayRow Indicates the number of rows to display in the seat

map. Default value is 4.
[New in 3.5]

BoardingPass Parent tag for boarding pass settings.

PrintInfantBoardingPass If set to true, a boarding pass is automatically printed

when an “infant” passenger is checked in.

BoardingMessage Configurable message to be printed on boarding

passes.

BoardingTimeOffset Number of minutes before a flight departs that

boarding is scheduled to begin.

InternationalBoardingTimeOffset Number of minutes before an international flight

departs that boarding is scheduled to begin. If this
[New in 3.4.6]
value is not set, the system uses the
BoardingTimeOffset value for international flights.

UseEstimatedTimesOnBoardingPass If set to true, boarding pass printing relies on any

existing estimated times of departure and arrival
[New in 3.4.6]
provided in flight following rather than the scheduled
times. If set to false, the estimated times in flight
following are ignored and scheduled times are used
instead.

PrintBoardingPass If set to true, a boarding pass is automatically printed

when the passenger is checked in.

SelecteeString XXXX.

Airport Check-in User Guide 1–5

 CHAPTER 1 INTRODUCTION TO AIRPORT CHECK-IN
Customizing Airport Check-in

Setting Description

BundleBoardingPasses Set to true to send connecting boarding passes to a

SITA printer as a group. This setting works with
non-common use printing.

Baggage Parent tag for baggage settings.

MaxPassengerBaggage Sets the number of bags that can be checked per

passenger. For example, entering 2 means a
passenger may check up to two bags per flight.

RemoveBagsPrompt If set to true, when removing a passenger from

check-in, agents are prompted to remove baggage.

If set to false, when removing a passenger from

check-in, there is no prompt to remove their baggage
information from the system and baggage is not
removed.

PromptAutoPrintBagTagsAtLogon If set to true, upon loading the initial flight after log
on, agents are prompted whether they want to print
bag tags for the flight automatically.

If set to false, upon loading the initial flight after log

on, agents are not prompted to print bag tags for the
flight automatically. In this case, bag tags are not
automatically printed.

IataIdentifier Three-digit airline number.

PrintBagTag Set to true to automatically print bag tags for each

checked bag.

SocketTimeOutInSeconds Number of seconds the system waits for the bag tag
printer to respond to a print request. If the printer
does not respond within the given time frame, the
system assumes the print job failed and returns
control to the user.

PrintConjunctiveBagTags Set to true to print a conjunctive bag tag when an

automatic bag is added to a destination that spans
four to six consecutive flight segments. An error
message is displayed for automatic bags that span
more than six consecutive flight segments, and the
agent is required to create a handwritten bag tag.

If set to false, an error message is displayed any time

an automatic bag is added to a destination that spans
more than three consecutive flight segments, and the
agent is required to create a handwritten bag tag.

TransferConjunctionIndicator Configurable transfer conjunction indicator. This value

is used to override the destination city on the first bag
tag of a conjunctive bag tag pair. For example, if you
enter TRANSFER CONJ, the first bag tag shows the
information for the first three segments and
“TRANSFER CONJ” in place of the destination city.

ManualBagTagCodes Comma-delimited list of codes that an agent can enter

instead of a final destination at the beginning of a
manual bag tag number.

1–6 Airport Check-in User Guide

 CHAPTER 1 INTRODUCTION TO AIRPORT CHECK-IN
Customizing Airport Check-in

Setting Description

SkipPassiveSegmentPromptForManua If set to true, the system does NOT prompt for passive
lBag segment information for manual bag tags. If the
manual bag tag code entered is not a valid destination
and is not one of the codes configured in
ManualBagTagCodes, the transaction fails.

AllowBagCheckinForNonCheckedInPax If set to true, agents can add bags for passengers

who have not yet checked in.

SendPecTab Set to true to send the pec tab to the bag tag printer
with each bag tag. Set to false to send only the bag
tag data.

UseStationDisplayNameOnBagTag Set to true to use the station display name as

configured in the Station in Management Console on
bag tags. When set to false, the station name is used
instead.

Boarding Settings

Setting Description

Boarding Parent tag for passenger boarding settings.

AutoBoardAllCheckedInPassengers If set to true, all checked-in passengers are boarded

automatically when a flight is closed. This enables
agents to close flights without first boarding all
passengers.

EnableSameDayOptions If set to true, agents are prompted to check in

passengers with same day returns into their return
flight as well. The boarding pass for the return flight
prints.

Do not enable same-day processing if you use

government security as the two processes are
mutually exclusive.

BoardWithoutSeat2D Set to true to enable passengers without seat

assignments to board flights using 2D barcodes
[Replaced in 3.4.7 by Prompt for without seats. Default value is false, meaning
Missing Seat During Boarding in passenger cannot board without seat assignments.
SkyPort Settings dialog]

Flight Information Settings

Setting Description

FlightInfo Parent tag for flight information settings.

Airport Check-in User Guide 1–7

 CHAPTER 1 INTRODUCTION TO AIRPORT CHECK-IN
Customizing Airport Check-in

Setting Description

IncludeStandbyOnFind If set to true, upon executing the F command,

standby (HL) passengers are included in the
passenger list.

Flight Closure Settings

Setting Description

FlightClosure Parent tag for flight closure settings.

ConvertHoldToConfirmed If set to true, converts Standby (HL) passengers to

Confirmed (HK) status when the flight is closed. If the
passenger has an HK segment booked for the same
market and date, it is removed when the HL segment
is confirmed. The newly confirmed segment has the
same fare as the original HK segment.

DeleteStandByPassengers If set to true, deletes standby no-show passengers

upon flight closure. However, standby no-show
passengers booked on connecting flights can be
deleted from the first segment only. Doing so deletes
the entire connecting flight from the booking.

ProcessStandbyPassengerPayment Not currently supported.

RZ Settings

Setting Description

RZ Parent tag for RZ settings.

DCCOffer Indicates the DCC offer status to be returned from

SkyPort. Possible values are as follows:

• 0 = DCC not offered

• 1 = DCC rejected (default)

• 2 = DCC accepted

Report Settings

Setting Description

Report Parent tag for report settings.

1–8 Airport Check-in User Guide

 CHAPTER 1 INTRODUCTION TO AIRPORT CHECK-IN
Customizing Airport Check-in

Setting Description

SeatMapDisplayRow Indicates the number of rows to display for seat maps

in the Pre/Post Flight Close Report.
[New in 4.0]

Airport Check-in User Guide 1–9

 CHAPTER 1 INTRODUCTION TO AIRPORT CHECK-IN
Customizing Airport Check-in

SkyPort Settings Dialog

Some configuration settings for Airport Check-in are accessible through the SkyPort Settings
dialog in Management Console. This dialog can be accessed through System Configuration >
System Settings > SkyPort Settings.

The table below lists the configuration options available in the SkyPort Settings dialog.

Setting Description

Default Move SSR Option Controls whether SSRs can be oversold during
passenger moves.

• Overbook SSR - SSRs are overbooked when

necessary.

• Move Available SSR - SSRs that are available on

the new flight are moved, while SSRs that are not
available are deleted.

• Move None - No SSRs are moved.

Enforce Over Wing Row Requirements If checked, agents cannot set a flight to closed or
close pending until at least two able-bodied
passengers are checked in with seats on each side of
the aircraft in each over-wing exit row. Assign role
“Override Over-Wing Exit Row Requirement” to agents
who need to override this configuration.

Write to Booking History For Bag Tag If checked, the system creates a booking history entry
Printing when bag tags are printed or re-printed.

Write to Booking History For Boarding If checked, the system creates a booking history entry
Pass Printing when boarding passes are printed or re-printed.

Use Remote Printing If checked, the system prints SkyPort reports using
the Remote Printing service.

1–10 Airport Check-in User Guide

 CHAPTER 1 INTRODUCTION TO AIRPORT CHECK-IN
Customizing Airport Check-in

Setting Description

Landscape Wide Reports If checked, the system prints reports over 132
characters wide in landscape format to preserve the
normal font size.

Restricted SSRs for Boarding Passes Indicates which SSRs are not to be printed on
boarding passes.
[New in 3.4.5]

Culture For Displaying SSR On Boarding Indicates the culture to be used to prioritize the SSRs
Passes to be printed on boarding passes. Refer to the
Management Console help file for more information
[New in 3.4.5]
about configuring cultures using the Localization and
Sorting dialog.

Culture For Displaying SSR In Check-in Indicates the culture to be used to prioritize the SSRs
in Airport Check-in displays. Refer to the Management
[New in 4.0]
Console help file for more information about
configuring cultures using the Localization and Sorting
dialog.

Validate Record Locator in 2D Barcode If checked, the system validates the record locator in
a 2D barcode.
[New in 3.4.5]

Restrict Bag Drop to Current Station If checked, the system prevents bag tag printing
through bag drop when the origin on the boarding
[New in 3.4.6]
pass does not match the current station.

Restrict Bag Drop to Flights Departing If checked, the system prevents bag tag printing
Within 24 Hours from Current Time through bag drop when the flight on the boarding
pass does not depart within the next 24 hours.
[New in 3.4.6]

Domestic Max Bag Weight Limit Indicates the maximum bag weight allowable for a
passenger on a domestic flight.
[New in 3.5]

International Max Bag Weight Limit Indicates the maximum bag weight allowable for a
passenger on an international flight.
[New in 3.5]

Max Bag Weight Type Indicates the unit of measure, pounds or kilograms, to
be used for baggage. If no value is set, the default is
[New in 3.5]
kilograms.

APIS send before flight close If checked, the system prompts the agent to send
APIS if it hasn’t already been sent when the flight is
[New in 3.4.6 UPD 5]
closed.

Prompt for Missing Seat During If checked, the agent is prompted upon scanning a 1D
Boarding type 5 or 2D barcode on a boarding pass for a
passenger with no seat assigment. If not checked, the
[New in 3.4.7] system boards the passenger without a prompt.

Display Downline Segments in Checkin If checked, the system displays details about downline
segments outside the New Skies journey during
[New in 3.4.7]
check-in.

Airport Check-in User Guide 1–11

 CHAPTER 1 INTRODUCTION TO AIRPORT CHECK-IN
Customizing Airport Check-in

Role Settings in Management Console

The following settings and permissions affecting Airport Check-in are set in Management
Console (System Users > Roles).

Role Setting or Description

Permission

Applications Logon Allow Login to Agent must be assigned this permission to log in
SkyPort to SkyPort.

Booking - Check In Time Before Flight Set the number of minutes before flight
Departure that departure, after which passengers may be
Check-in is checked in. For example, if set to 60, passengers
Allowed may be checked in once the current time is
within sixty minutes of the flight departure time.

Booking - Check In Time Before Sets the cut-off time when agents are unable to
Departure that check in a customer before the flight departs.
Check-in is For example, if set to 5, passengers may not be
Disallowed checked in once the current time is within five
minutes of the flight departure time.

Entering a negative value means check-in may

continue until after departure. For example,
entering -5 means passengers can be checked in
up to five minutes after departure time.

Booking - Check In Enable Name Select to enable the agent to perform name
Change for changes for passengers who have already
Checked-in checked in.
Passenger

Booking - Check In Time Before Sets the cut-off time when agents are unable to
Departure that change a passenger’s name before the flight
Name Change is departs. For example, if set to 5 minutes,
Disallowed for passenger names may not be changed once the
Checked-in current time is within five minutes of the flight
Passenger departure time.

Booking - Check In Enable Flight Select to enable the agent to perform flight
Change for changes for passengers who have already
Checked-in checked in.
Passenger

Booking - Check In Time Before Sets the cut-off time when agents are unable to
Departure that perform flight changes for passengers who have
Flight Change is checked it before the flight departs. For
Disallowed for example, if set to 5 minutes, the flight may not
Checked-in be changed once the current time is within five
Passenger minutes of the flight departure time.

Booking - Check In Allow check-in to In order to check in passengers at the gate,

be performed at agent must be assigned this permission.
gate

Booking - Check In Allow check-in to In order to check in passengers at the curb,

be performed at agent must be assigned this permission.
curb

Booking - Check In Allow check-in on In order to check in a passenger whose booking

invalid status has an invalid status, agent must be assigned
Bookings this permission.

1–12 Airport Check-in User Guide

 CHAPTER 1 INTRODUCTION TO AIRPORT CHECK-IN
Customizing Airport Check-in

Role Setting or Description

Permission

Booking - Check In Allow check-in In order to check in a passenger who has a

when ticket needs paper ticket, agent must be assigned this
to be collected permission.

Booking - Check In Allow Bag Tag In order to check in passengers whose bag tags
Destination do not match their final destinations, agent must
Mismatch be assigned this permission.

Note The bag destination must exist as a stop on

the journey.

Booking - Check In Allow TBA If selected, agent can check in TBA (to be
check-in announced) passengers.

Booking - Check In Ignore Market If selected, system ignores time restrictions for
Time Restrictions markets.

Booking - Check In Valid SSR Codes Lists all valid SSR types and indicates whether
each is allowed, restricted, or required for the
user. The settings selected here also apply to
IATCI.

Booking - Check In Allow APPS Indicates that the agent has permission to check
Check-in in passengers when APPS is required.

Booking - Check In Allow APPS Indicates that the agent has permission to
Override override APPS responses when checking
passengers in.

Booking - Check In International Bag Indicates what bag weights are required, if any,
Weight on international flights. Options are the
following:

• Weight not required.

• Total weight required.

• Individual weight required.

Booking - Check In Domestic Bag Indicates what bag weights are required, if any,
Weight on domestic flights. Options are the following:

• Weight not required.

• Total weight required.

• Individual weight required.

Booking - Check In Allow APIS Indicates that the agent has permission to check
Checkin in passengers when APIS is required. Options
are the following:

• Not allowed.

• Allowed with verified documents.

• Allowed without verified documents.

Booking - Check In Allow checkin of In order to check in passengers with a balance

passenger with due, agent must be assigned this permission and
pending payments there must be a pending payment on the
reservation.

Airport Check-in User Guide 1–13

 CHAPTER 1 INTRODUCTION TO AIRPORT CHECK-IN
Customizing Airport Check-in

Role Setting or Description

Permission

Booking - Check In Allow Mid-journey In order to check in a passenger at a station

Check-in without the passenger having been checked on
the previous flight in the journey, agent must be
assigned this permission.

Booking - Check In Allow Manual In order to manually screen a passenger through

Clearance Secure Flight, agent must be assigned this
permission.

Note This role only applies when using the

Outage mode of Secure Flight as configured in
Management Console’s External Message
System settings.

Booking - Check In Allow Gate Pass In order to print gate passes, agent must be
Printing assigned this permission.

Booking - Check In Allow Bag Tag In order to reprint bag tags, agent must be
Reprint assigned this permission.

Booking - Check In Allow Agent to In order to override e-ticket coupon status

Override E-Ticket during check-in, agent must be assigned this
[New in 3.5] Coupon Status permission.

Booking - General Allow In order to add or remove SSRs with fees for
Add/Remove Of passengers who are already checked in to a
SSR On Checked flight, agent must be assigned this permission.
In Passenger

Codes Waive Fees NameChangeFee must be allowed for SkyPort

users because an agent may have to change a
passenger name prior to boarding, and SkyPort
cannot collect a payment.

SkyPort Allow Opening of In order to open a flight with a “closed” status,

Closed Flights agent must be assigned this permission.

SkyPort Allow Flight Status In order to change the status of a flight, agent
Change must be assigned this permission.

SkyPort FLIFO Permissions There are four permission levels for FLIFO.

• None -- Disables all Check-in functionality

for the user.

• Read Only -- The user can retrieve flight

following information but cannot update it.

• Read and Update -- The user can retrieve

and update flight following information.

• All -- The user can retrieve, update, and

delete flight following information.
(Currently, users can only delete delay
codes.)

1–14 Airport Check-in User Guide

 CHAPTER 1 INTRODUCTION TO AIRPORT CHECK-IN
Customizing Airport Check-in

Role Setting or Description

Permission

SkyPort Flight Information There are three permission levels for flight
Permissions information.

• None -- The user cannot retrieve flight

information.

• Read Only -- The user can retrieve flight

information but cannot update it.

• Read and Update -- Flight information can

not be updated through Check-in. Therefore,
this option functions the same as Read Only.

SkyPort Allow agent to In order to update standby priority codes, agent

update Standby must be assigned this permission.
Priority Code

SkyPort Allow RZ Access In order to access RZ, agent must be assigned

this permission.

SkyPort Allow Check-in In order to access Check-in, agent must be

Access assigned this permission.

SkyPort Allow Aircraft In order to access the Aircraft Mishap Utility,

Mishap Utility agent must be assigned this permission.
Access

SkyPort Allow Equipment In order to access the Equipment Swap Utility,

Swap Utility agent must be assigned this permission.
Access

SkyPort Allow Tail Number In order to access the Tail Number Utility, agent
Utility Access must be assigned this permission.

SkyPort Allow Voucher In order to access the Voucher Utility, agent

Utility Access must be assigned this permission.

SkyPort Allow IROP Utility In order to access the IROP Utility from the
Access via console, agent must be assigned this
Console permission.

SkyPort Allow Diversion In order to access the diversion functionality in

Permissions in IROP, agent must be assigned this permission.
IROP

SkyPort Allow Creation of In order to create ad hoc connections for IROP,

Ad Hoc agent must be assigned this permission.
Connections in
IROP

SkyPort Allow Diversion In order to access the diversion functionality in

Permissions in Ad Ad Hoc, agent must be assigned this permission.
Hoc

SkyPort Allow In order to cancel or restore inventory, agent

Cancel/Restore of must be assigned this permission.
Inventory

Airport Check-in User Guide 1–15

 CHAPTER 1 INTRODUCTION TO AIRPORT CHECK-IN
Customizing Airport Check-in

Role Setting or Description

Permission

SkyPort Allow Inventory In order for an agent to update the inventory lid,
Record this field must be checked. If it is not, the agent
Maintenance is only allowed to view the lid.
Update Utility
Access

SkyPort Allow Inventory In order for an agent to update SSR inventory

SSR Maintenance information, this field must be checked. If it is
update not, the agent is only allowed to view the
information.

SkyPort Verify APIS If selected, APIS information must be collected

International for each passenger on international flights to
Flights APIS-enabled countries.

SkyPort Allow Check-in of If selected, agent can check in passengers on

Marketing Flights marketing code share flights.

SkyPort Send APIS Report To verify an international flight and send the
APIS report to customs, agent must be assigned
this permission.

SkyPort Allow Passenger To clear passengers in the event of an aircraft

Clear in Aircraft mishap, agent must be assigned this permission.
Mishap

SkyPort Allow Passenger To restore passengers in the event of an aircraft

Restore in Aircraft mishap, agent must be assigned this permission.
Mishap

SkyPort Allow agent to To oversell the TO flight in IROP, agent must be

oversell IROP TO assigned this permission.
flight

SkyPort Allow view for In order to work with watch list entries and
Watch List Entries matches, agent must be assigned these
(.L command) permissions.

Allow detail view Note These settings are nested. That means that
for Watch List in order for an agent to have permission to clear
matches (.L# and a passenger from a watch list, the agent must
.WL# commands) also be able to view the watch list details.
However, it is possible that some roles may have
Allow clear
permission to view the watch list but not to clear
passenger from a passengers.
Watch List (CL
command)

SkyPort Days Before and Set the number of days before and after flight
After Flight departure that IROP is allowed. For example, if
Departure that set to two, passengers may not be moved to a
IROP is Allowed different flight using IROP until the current time
is within two days of the flight departure time.

SkyPort Days Before and Set the number of days before and after the
After Current Date current date for which ad hoc flights can be
that Ad Hoc created. For example, if set to one, agents can
Flights can be create an ad hoc flight for tomorrow but not
Created further out.

1–16 Airport Check-in User Guide

 CHAPTER 1 INTRODUCTION TO AIRPORT CHECK-IN
Customizing Airport Check-in

Role Setting or Description

Permission

SkyPort Time After Set the amount of time after flight departure
Departure that that a flight can be opened. For example, if set
Open Flight is to 0/6/0, the flight can be opened until the
Allowed: current time is six hours after the flight
Days/Hours/ departure time. The maximum time allowed for
Minutes this setting is one year (525600 minutes).

SkyPort Time Before Set the amount of time before flight departure
Departure that that a flight can be closed. For example, if set to
Close Flight is 0/6/0, the flight cannot be closed until the
Allowed: current time is less than six hours before the
Days/Hours/ flight departure time.
Minutes

SkyPort Programs Select or clear to allow or restrict agent access

to the following programs:

• Allow SITA Message Send

• Allow Message Send (Non-SITA)

• Allow Ad Hoc Scheduling and Inventory

Connections

SkyPort Allow access to In order to access the CAPPS report, agent must
the CAPPS be assigned this permission.
detailed report

Allow check-in of In order to check in selectee passengers, agent

selectee must be assigned this permission.
passenger

Note These settings are nested. That means that

in order for an agent to have permission to
check in selectee passengers, the agent must
also be able to view the CAPPS detailed report.
However, it is possible that some roles may have
permission to view the CAPPS detailed report but
not to check in selectee passengers.

SkyPort Reports Select or clear to allow or restrict agent access

to the SkyPort reports. For more information,
refer to the SkyPort Reports User Guide.

SkyPort Allow Baggage In order to access baggage tracking utility, agent

Tracking Access must be assigned this permission.

SkyPort Override In order to set a flight to closed or close pending

Over-Wing Exit even if the over-wing exit row requirements are
Row Requirement not met, agent must be assigned this
permission.

SkyPort Bag Drop Mode Select normal to grant access to the basic bag
drop functionality. Select advanced to enable the
[New in 3.5] user to access advanced bag drop functionality,
which includes the ability to add or remove bags
directly from bag drop.

Airport Check-in User Guide 1–17

 CHAPTER 1 INTRODUCTION TO AIRPORT CHECK-IN
Logging On and Accessing Airport Check-in

Logging On and Accessing Airport Check-in

To use Airport Check-in, you must first log on to SkyPort. Once you log on and select the Airport
Check-in menu option, you are able to load flights, check in passengers, board passengers, and
so on. SkyPort can be accessed either from an airport terminal or from a PC using a terminal
emulator, such as SkyPort Term, Reflection, MiniSoft or HyperTerm.
Note: If your session times out due to inactivity, the screen clears when you begin typing and you
return to the login screen.

To log on to SkyPort and access Airport Check-in:

1 (Conditional) If your terminal screen is blank, press any key to activate the screen.

2 Once your screen is active, press Enter:

The LOGON: prompt displays.

3 Enter your logon information , then press Enter:

Use the following syntax: hello <agent name>,<domain code>

• For <agent name>, type your agent name assigned in Management Console (System
Users > Agents).
• For <domain>, type the domain code that identifies the domain to which you belong.
Domains are configured in Management Console (System Users > Domains).
The following is an example logon entry:
hello jjohnson,jfk

In this example, jjohnson is the agent name and jfk is the domain.
A prompt similar to the following displays, requiring you to select the terminal type you are
using to access SkyPort.

4 Select the terminal type , then press Enter.

Use VT320 if you are using Navitaire TE as your emulator. For Minisoft or Reflections, select
HP.

1–18 Airport Check-in User Guide

 CHAPTER 1 INTRODUCTION TO AIRPORT CHECK-IN
Logging On and Accessing Airport Check-in

A list of valid locations configured for your airline is displayed, including your current
location. This is the default location assigned to your domain in Management Console.
(System Users > Domains).

5 Do one of the following.

• To select the current location, press Enter.
OR

• To select a different location, enter the three-digit location code, then press Enter.
You are prompted for a password. This password is assigned to your agent account in
Management Console (System Users > Agents).

6 Type your password , then press Enter.

You are now logged on to the SkyPort system. Information regarding your account is
displayed, including your current role:

In the example above, the agent signing on to SkyPort is assigned more than one role. Your
role determines what items you can access and what tasks you are able to perform. Roles are
set up in Management Console (System Users > Roles). If you are assigned more than one
role, you may select a different role.

7 (Conditional) If you are assigned more than one role, do one of the following:
• To select your current role, press Enter.
OR

• To select a different role, enter the one to four-digit role code identifying the role, then
press Enter.
The FYI notes for the current date are displayed, if any.

8 Press Enter.

Airport Check-in User Guide 1–19

 CHAPTER 1 INTRODUCTION TO AIRPORT CHECK-IN
Logging On and Accessing Airport Check-in

The SkyPort Main menu displays, similar to the following:

The options on the SkyPort Main menu may differ from those shown above, as this menu is
customizable for individual airlines.
The options that display on the SkyPort Main menu depend on the following:

• MainMenu.xml file
Each menu item must be included in this file in order to be displayed on the SkyPort Main
menu. This file can be accessed in Management Console (System Configuration >
Resource Management).
Note: To add Airport Check-in to the Operations menu, edit OperationsMenu.xml in
Management Console (System Configuration > Resource Management).
For more information about these files, refer to the help files for Management Console.
• Assigned Role
Only menu items in which the agent's assigned role is permitted to access are displayed.
Any operation or task not permitted by the agent's role does not display on the menu.
Roles are configured in Management Console (System Users > Roles).
For more information about roles and agents, refer to the help files for Management
Console.

9 Select the number that corresponds to Airport Check-in, then press Enter.

1–20 Airport Check-in User Guide

 CHAPTER 1 INTRODUCTION TO AIRPORT CHECK-IN
Logging Out

The initial Check-in screen is displayed, allowing you to a load a flight, similar to the
following:

For information on the Airport Check-in screen, see Loading Flights Directly after Login on
page 2-2.

Logging Out
Once you complete your tasks within any program on the Airport menu, you should log out to
ensure that other users do not use your login data. The method for logging out is the same for all
modules within the Airport menu (except for RZ, where the logout command is BYE instead of
EX).

To log out of Airport Check-in:

1 At the command prompt, type EX , then press Enter.

You are returned to the SkyPort Main menu.

2 At the Enter Selection prompt, type EX , then press Enter.

You are now logged out of the server and disconnected from the airline database.
Note You can also type BYE to exit the system.

Understanding the Command Prompt

In Airport Check-in, the command prompt serves two purposes. First, it displays the status of the
check-in and boarding processes for a flight. Second, it serves as the location to enter commands.

Airport Check-in User Guide 1–21

 CHAPTER 1 INTRODUCTION TO AIRPORT CHECK-IN
Understanding the Command Prompt

The following table describes the information in the command prompt.

Element Example Description

Command prompt...

<time> 10:38 Current time, based on a 24-hour clock.

<flight date> 19Apr Flight date, displays in the format DDMMM.

<market> JFKBOS Market, displays in the format <origin airport of

flight leg><destination airport of flight leg>.

<flight departure time> 1815 Flight departure time, based on a 24-hour clock.

<flight arrival time> 2120 Flight arrival time, based on a 24-hour clock.

<airline code> L1 Airline code of the airline offering the flight.

<flight number> 160 Flight number.

<operational suffix> A One-character operational suffix appended to a

flight number for flights involved in an operational
procedure.

If the flight number is not entered, no operational

suffix is required.

<departure gate> A22 (Conditional) Departure gate number.

Gate numbers are entered in Flight Following.

Refer to the Airport Operations Guide for details.

<flight status> CLSD Flight status, which can be one of six types:

• <no status>. Flight is “open”. You can check in

and board passengers.

• CXLD. Flight is “cancelled”. You cannot check

in, board, or un-board passengers.

• CLSD. Flight is “closed”. You cannot check in,

board, or un-board passengers.

• CLPD. Flight is in “close pending” mode. You

can board and unboard passengers, but you
cannot check in passengers.

• IROP. Flight is under “irregular operations”.

However, you can still check in, board and
unboard passengers.

• VER. International flight has been verified.

For more detailed information on flight status

types, see Understanding Flight Status Types on
page 8-2.

1–22 Airport Check-in User Guide

 CHAPTER 1 INTRODUCTION TO AIRPORT CHECK-IN
Using Online Help

Using Online Help

If you need assistance at any time while working in Airport Check-in, you can access online Help
using the HELP command; simply type HELP at the command prompt , then press Enter.
The online Help screen displays, similar to the following:

This screen displays the commands used in Airport Check-in, organized into logical groups. In
the example above, all commands related to passenger check-in are listed under Check-in. Other
categories include baggage, standby passengers, seat maps/seat assignments, checking-in
passengers, boarding passengers, and so on.
Each page displays about 15 commands. At the bottom of the screen is the Continue? prompt,
which enables you to view the next page of commands (simply press Enter to view the next page
of commands).
To exit online Help and return to the command prompt, do one of the following:

• At the Continue? prompt, type N , then press Enter.

OR

• Press Enter to scroll through the entire list of Help topics until you reach the end of the Help
file.

Airport Check-in User Guide 1–23

 CHAPTER 1 INTRODUCTION TO AIRPORT CHECK-IN
Using Online Help

1–24 Airport Check-in User Guide

2 Loading Flights

Loading a flight enables you to check in/board passengers for the flight, open/close the flight,
view passenger counts, and so on. You can load flights any one of three ways: (1) after login, (2)
from the command prompt, and (3) from the flight list.
This section contains the following topics:

In this chapter:
• Loading Flights Directly after Login on page 2-2
• Loading Flights from the Command Prompt on page 2-8
• Loading Flights from the Flight List on page 2-9

Airport Check-in User Guide 2–1

 CHAPTER 2 LOADING FLIGHTS
Loading Flights Directly after Login

Loading Flights Directly after Login

You can load a flight directly after login. Each time you log in, you are prompted to enter
information for the purpose of “loading” a flight, such as city pair, date, and flight number. The
information required varies, depending on your individual airline settings. The following list
describes what you may be prompted to enter when loading a flight:

• Airline code
At the Airline Code: prompt, enter the airline code of the airline whose flight you want to
load. Airline codes are maintained in Management Console (System Settings > Carriers).
• Flight Date
For any flight that you load, you are required to enter the flight departure date. However, the
year is optional.
• City Pair or Airport
You are prompted to enter the city pair of the flight to load. If you do not know the city pair,
you can view (1) flights in all city pairs or (2) flights that originate at a specific airport.
Entering a city pair or airport in this field is optional.
• Flight number
If you entered a city pair or airport, you are prompted to enter the flight number of the flight
to load. If you do not know the flight number, you can view all flights for the specified city
pair or airport on the specified date.
• Whether to print bag tags
If your airline prints bag tags at the time of baggage check-in, the Automatic Print Bag Tags
prompt displays. You should indicate whether to print bag tags for this session. If you choose
to print bag tags (Y), you are prompted to select the bag tag printer.

To load a flight:

1 Select Airport Check-in from the SkyPort Main menu.

See Logging On and Accessing Airport Check-in on page 1-18. A screen similar to the following
is displayed:

2–2 Airport Check-in User Guide

 CHAPTER 2 LOADING FLIGHTS
Loading Flights Directly after Login

2 At the Airline Code prompt, enter the airline code of the carrier whose flight you want
to load, then press Enter.

Airline codes may be two to three characters and are configured in Management Console
(System Settings > Carriers).

3 At the Flight Date prompt, do one of the following:

• To load a flight for the current date, press Enter.

OR

• To load a flight for another date, enter the date , then press Enter. Use the format
DDMMMYY (for example, 04MAR05).

4 At the City Pair prompt, do one of the following:

• If you know the flight number of the flight to load:

Type the airport codes of the market , then press Enter. For example, to load a flight from
SLC to MSP, enter SLCMSP.
OR

Press Enter without entering the city pair. By entering the flight number in step 5, the
appropriate flight is loaded.
• If you do not know the flight number, do one of the following:

— To view all flights for a specific market, type the airport codes of the market , then
press Enter. For example, to view all flights from SLC to MSP, enter SLCMSP.
OR

— To view all flights from a specific airport, type the airport code , then press Enter.
For example, to view all flights that originate from SLC, enter SLC.
OR

Airport Check-in User Guide 2–3

 CHAPTER 2 LOADING FLIGHTS
Loading Flights Directly after Login

— To view all flights for all markets, press Enter. Once you complete steps 5 and 6, all
flights for all markets display, similar to the following:

The following table describes the elements on the flight information line:

Element Example Description

<date> 29Mar07 Date for which you are viewing flights. The date is
entered when you log in to Airport Check-in.

<line number> 1 Line number of the flight.

<code share or * Indicates that the flight is marketed by the current

wet-lease/dry-lease flight airline but is operated by another airline. The
indicator> operating carrier and flight number are listed in
the Operated By column.

When an “Also sold as” line displays, but no

asterisk (*) is present, the flight is operated by
the current airline but is marketed by at least one
other airline. In that case, the additional
information refers to the marketing airline.

<market> AKIABR Airport code of the origin airport, followed by

airport code of the destination airport.

<airline code> 1L Airline code. Airline codes are configured in

Management Console and added to schedules in
SkySchedule.

<flight number> 3434 Flight number. Flight numbers are configured in

SkySchedule.

<operational suffix> A One-character operational suffix appended to a

flight number for flights involved in an operational
procedure.

If the flight number is not entered, no operational

suffix is required.

2–4 Airport Check-in User Guide

 CHAPTER 2 LOADING FLIGHTS
Loading Flights Directly after Login

Element Example Description

<flight status> CLSD Flight status.

<scheduled departure 0800 Scheduled departure time, based on a 24-hour

time> clock. Scheduled departure times are configured in
SkySchedule.

<scheduled arrival time> 1400 Scheduled arrival time, based on a 24-hour clock.
Scheduled arrival times are configured in
SkySchedule.

<estimated departure 0810 (Conditional) Estimated departure time, based on

time> a 24-hour clock. Estimated departure times are
entered in Flight Following.

<estimated arrival time> 1440 (Conditional) Estimated arrival time, based on a

24-hour clock. Estimated arrival times are entered
in Flight Following.

<departure gate> A22 (Conditional) Departure gate. Gate numbers are

entered in Flight Following.

<arrival gate> G26 (Conditional) Arrival gate. Gate numbers are

entered in Flight Following.

<# seats sold per cabin> 3 Number of seats sold, organized by cabin.
Includes HK and HU bookings. If the plane has
more than one cabin defined other columns
display.

<operating airline> OA (Conditional) Two-character code for the airline

that operates the flight. This value only displays if
the flight is part of a code share agreement.

<operating airline flight 5243 (Conditional) Flight number used by the operating
number> airline for the flight. This value only displays if the
flight is part of a code share agreement.

5 At the Flight Number prompt, do one of the following:

• If you know the flight number, type the flight number , then press Enter.
OR

• If you do not know the flight number, press Enter. Once you complete step 6, all flights for
the specified market or airport display. In the example below, all flights that originate in
BOS display:

6 At the Automatic Print Bag Tags prompt, specify whether you want to print bag tag
numbers for this session.

Airport Check-in User Guide 2–5

 CHAPTER 2 LOADING FLIGHTS
Loading Flights Directly after Login

• To manually enter bag tag numbers based on pre-printed bag tags, type N , then press
Enter.

OR

• To automatically generate bag tag numbers and print bag tags at check-in, type Y , then
press Enter. The bag tag printers available to your department display, similar to the
following:

At the Select printer: prompt, type the line number of the desired printer, then press
Enter. For information on automatic bag tag printing, see Understanding Bag Tag Numbers
on page 6-2.
The flight is loaded and the passenger counts for the flight display, similar to the following:

The following table describes the passenger counts:

Element Description

Passenger Counts In this table, “HK” represents confirmed passengers, “HU”

represents unconfirmed passengers, and “HL” represents standby
passengers. The columns on the screen, in this example C, F, and
Y, represent the cabin classes available on the aircraft. These
columns are based on the aircraft’s configuration in SkySchedule.

2–6 Airport Check-in User Guide

 CHAPTER 2 LOADING FLIGHTS
Loading Flights Directly after Login

Element Description

Manifested: Number of “local” HU and HK passengers (this is their first

boarding point for this flight #). Basically, includes all manifested
non-stop and connecting passengers but not thru passengers.

Note Depending on your airline settings, may also include standby

passengers (HL).

Checked In: Number of “local” HK passengers that have checked in. Does not
include thru passengers.

Note Depending on your airline settings, may also include standby

passengers (HL).

No Show: Number of “local” HU and HK passengers that are manifested but

not checked in. All passengers are considered “no show” until they
have been checked in for the flight. Does not include thru
“no-show” passengers.

Note: Depending on your airline settings, may also include

standby passengers (HL).

Stand By: Number of “local” HL passengers (this is their first boarding point
for this flight #).

Cleared Stand By: Number of “local” HL passengers that have checked in.

Thru Manifested: Number of “thru” HK and HU passengers that are manifested for
this flight leg.

Note Depending on your airline settings, may also include “thru”

standby passengers (HL).

Thru Checked In: Number of “thru” HK passengers that are checked in to this flight
leg. Thru passengers are automatically checked in to all legs of a
flight when they check in to the first leg of the flight.

Note Depending on your airline settings, may also include standby

passengers (HL).

Thru No Show: Number of “thru” passengers that are no shows for a previously
booked point of the flight, including HK, HU, and HL passengers.
All passengers are considered to be “no show” until they have
checked in to the flight.

Thru Stand By: Number of HL passengers who are manifested on a previous leg of
the flight #.

Thru Cleared SBY: Number of HL passengers who are manifested on a previous leg of
the flight # that have checked in to this flight leg. (Even though
the previous flight leg was “closed,” their reservations were not
changed to HK and they are still listed as HL.)

Total Checked In: Number of “local” HK and HL passengers that have checked in, as
well as “thru” passengers that have checked in. Does not include
HU passengers.

On Board: Number of “local” HK and HL passengers that have boarded, as

well as “thru” passengers that have boarded. Does not include HU
passengers.

Check In Lid: Number of passengers that can be checked in for the flight.

Airport Check-in User Guide 2–7

 CHAPTER 2 LOADING FLIGHTS
Loading Flights from the Command Prompt

Loading Flights from the Command Prompt

You can load a new flight from the command prompt using the LF or LL command. This can be
useful if you have closed the current flight, and the next scheduled flight is ready for check-in.
The LL command can be used only for flights on the same calendar day as the currently loaded
flight. To use the LL command, simply type the command, followed by the flight number and the
airline code if you are switching to a different airline (for example: LL203/1L).
To use the LF command, you must know the date, city pair, flight number, and airline of the
flight to load. If you do not know any of these parameters, you can enter the L command to view
a list of all flights, and then load the desired flight. For more information on listing flights, see
Loading Flights from the Flight List on page 2-9.

To load a flight from the command prompt using the LF command:

1 At the command prompt, type LF<date><market><flight #>/<airline code> , then

press Enter.

For example, to load 1L flight 147 between LAX and SLC departing on 4 March 2003, enter
LF04MAR03LAXSLC147/1L. You can omit the date if the flight is scheduled for the current
day.
Note: If you do not know the parameters of the flight to load, enter L at the command prompt to
view a list of all flights, and then select the flight to load. For more information on listing
flights, see Loading Flights from the Flight List on page 2-9.
The passenger count displays, which displays passenger totals for the loaded flight, similar to
the following:

This screen is described in Loading Flights Directly after Login on page 2-2.

2–8 Airport Check-in User Guide

 CHAPTER 2 LOADING FLIGHTS
Loading Flights from the Flight List

If a seat map is loaded for the aircraft, the seat map displays as well. See Understanding the
Seat Map on page 5-2.

Loading Flights from the Flight List

With the L command, you can list (1) all flights for a specific carrier, (2) all flights between two
cities for a specific carrier, and (3) all flights that originate at a particular airport for a specific
carrier. This can be useful if you need to load a flight, but you do not know the city pair or flight
number; you can locate the desired flight in the flight list, and then load the flight.

To load a flight from the flight list:

1 At the command prompt, do one of the following:

• To view all flights for all markets, type L/<airline code> , then press Enter. To retrieve
flights for the most recently loaded flight’s airline, omit the /<airline code>.
OR

• To view all flights that originate at a specific airport, type L<airport code>/<airline
code> , then press Enter. For example, to view all 1L flights that originate at the London
Gatwick airport, enter LLGW/1L. To retrieve flights for the most recently loaded flight’s
airline, omit the /<airline code>.
OR

• To view all flights between a specific market, type L<market>/<airline code> , then
press Enter. For example, to view all 1L flights from LGW to JFK, enter LLGWJFK/1L. To
retrieve flights for the most recently loaded flight’s airline, omit the /<airline code>.
All flights that match your search criteria display, similar to the following:

2 Type LF<line #> , then press Enter.

For example, to load the flight on line 1, enter LF1. The flight is loaded, and the passenger
count for the flight displays.

Airport Check-in User Guide 2–9

 CHAPTER 2 LOADING FLIGHTS
Loading Flights from the Flight List

2–10 Airport Check-in User Guide

3 Displaying Passenger Lists

There are many ways you can list passengers on a flight. For example, you can view standby
passengers, checked-in passengers, passengers with manifest comments, and so on. There are
many commands you can use to display passengers, the most common of which is the F
command. Others are also explained in this chapter.

In this chapter:
• Displaying All Passengers on a Flight on page 3-3
• Displaying All Passengers on the Same Reservation on page 3-8
• Displaying All Passengers on the Indicated Reservation on page 3-8
• Displaying Passengers by Surname on page 3-9
• Displaying Checked-in Passengers on page 3-9
• Displaying Standby Passengers on page 3-10
• Displaying Boarded Passengers on page 3-13
• Displaying “Un-boarded” Passengers on page 3-13
• Displaying Passengers Who Have Not Checked In on page 3-14
• Displaying Passengers Who Do Not Have Assigned Seats on page 3-15
• Displaying Code Share Passengers that are Associated with Another Marketing Designator on
page 3-16
• Displaying Thru Passengers on page 3-17
• Displaying Connecting Passengers on page 3-18
• Displaying Upgraded Passengers on page 3-18
• Displaying Passengers With Premium Fares on page 3-20
• Displaying Passengers with Manifest Comments on page 3-20
• Displaying Passengers with SSRs on page 3-21
• Displaying Passengers With Ticket Numbers on page 3-22
• Displaying Passengers with International Documents on page 3-25
• Displaying Passengers without International Documents on page 3-26
• Displaying Passengers with APIS Information on page 3-27
• Displaying Passengers with Missing Security Information on page 3-30
• Displaying Passengers with Customer Accounts on page 3-30
• Displaying Passengers by Sequence Number on page 3-32
• Displaying the Passenger Assigned a Specific Seat on page 3-32

Airport Check-in User Guide 3–1

 CHAPTER 3 DISPLAYING PASSENGER LISTS

• Displaying Passengers on Locked Reservations on page 3-32

• Displaying Passengers on Locked Reservations on page 3-32
• Displaying Passengers with a Balance Due on page 3-35

3–2 Airport Check-in User Guide

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying All Passengers on a Flight

Displaying All Passengers on a Flight

To check in, board, or modify reservation information for any passenger, you must first display
the passenger on the screen.
You can display all passengers on a flight using the F command. This command displays
confirmed, unconfirmed, and standby passengers. However, depending on your airline settings,
the F command may not display standby passengers (see Customizing Airport Check-in on page
1-2).
The display includes the first SSR code associated with each passenger if SSRs are present.
There are several settings that affect the way SSRs display in Airport Check-in dialogs and on
boarding passes. First, the Add/Edit SSR dialog in Management Console enables you to
configure each SSR to either display or be suppressed in Check-in and on boarding passes. You
can also configure the SSR sort order for each culture within the Localization and Sorting dialog
in Management Console (System Configuration > Localization and Sorting). Then use the
Culture For Displaying SSRs In Check-in setting in the SkyPort Settings dialog to identify the
culture to be used to sort the SSRs. If SSR sorting is not configured for the specified culture or if
no culture is specified, Check-in displays infant SSRs first by default. Refer to CheckinConfig.xml
on page 1-3 and the help file for Management Console for details.
An asterisk (*) next to the SSR code indicates that the passenger has more than one SSR. To view
SSR details, use the .SSR<pax> command. Refer to Displaying the SSRs Assigned to a Passenger
on page 9-30 for details.

To display all passengers on a flight:

1 At the command prompt, type F, then press Enter.

All passengers on the flight display, similar to the following:

Note: To display the seat map along with the passenger list, enter “F,SM”.

Every “passenger display” command displays the same format of the passenger information line
except for the .S command, which displays the “standby passenger information line” and the
.TKT command, which displays ticket information.

Airport Check-in User Guide 3–3

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying All Passengers on a Flight

The following table provides a description of the passenger information line.

Element Example Description

<line #> 1) Line number associated with the passenger. For

example, “1)” represents the passenger on line 1.

<surname>/<given ANDERSON/ Surname and given name are required. For

name>/<middle LISA/CHRIS example, “ANDERSON/LISA/CHRIS” indicates Lisa
name>=<title> Chris Anderson.

If a middle name and/or title is specified for the

passenger at the time of the reservation’s creation
in SkySpeed, SkySales, or RZ, then it is listed
using the specified format. For example,
“DOE/JOHN/DAVID=MR” indicates Mr. John David
Doe.

<SSR code> MAAS* (Conditional) Special Service Request (SSR) for

the passenger. For example, “MAAS” represents
Meet and Assist.

If an asterisk (*) displays next to the SSR (for

example, MAAS*), then the passenger has more
than one SSR code for the flight and only the first
one is shown. To view additional SSR codes for a
passenger, use the .SSR<pax> command.

<sequence #> 1 (Conditional) Displays the sequence number

assigned to the passenger. See Understanding
Sequence Numbers on page 4-3.

<Customer ID indicator> C (Conditional) If a customer account is associated

with the passenger name, then a “C” displays in
this field.

If a customer loyalty program is associated with

the reservation, the customer recognition level
displays. For example, a ”G” displays for a
program member with Gold status.

Otherwise, no data displays.

For information on associating customer accounts

with passengers, see Associating Passenger
Names with Customer Accounts on page 9-21.

<IROP indicator> ! (Conditional) Indicates that the passenger was

moved to the flight via IROP.

<check-in/boarding status> + (Conditional) Check-in and boarding status of the

passenger:

• + (passenger is checked in)

• ++ (passenger is checked in and boarded)

• +% (passenger is checked in but has not yet

received a boarding directive)

• * (passenger is on an operating code share

flight and is not yet checked in)

<seat #> 1A (Conditional) Seat assignment.

3–4 Airport Check-in User Guide

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying All Passengers on a Flight

Element Example Description

<reservation number> KZZ4YJ Reservation number, also called record locator or

PNR number.

If an asterisk (*) displays after the reservation

number, then the passenger has manifest
comments.

<pax # on PNR><total # of 0102 Order of the passenger on their reservation in

pax on PNR> relation to the total number of passengers on the
reservation. For example, “0102” indicates that
the passenger is the first of two passengers on the
reservation.

<booking status> HK Booking status of the passenger.

• HK - Confirmed

• HL - Standby

• HU - Unconfirmed

<upgrade indicator> ^ (Conditional) If the customer has upgraded their

cabin, then a caret (^) displays.

<product class code> B (Conditional) Product class code if a product class

exists.

<class of service> Y Class of service booked on the itinerary. For

example, “Y” represents the Y class of service.

Note If the class of service is more than two

characters long, the first character is followed by
an asterisk (*). Use the .FC command to view the
full fare class for a passenger.

<Customer ID> CID: (Conditional) Customer ID of the customer

1234567890 account associated with the passenger. Displays
only when using the .CU command to display the
passenger list (see Displaying Passengers with
APIS Information on page 3-27).

<inbound flight #> 100 (Conditional) If the passenger has an inbound

connecting flight, this is the flight number of the
inbound flight.

For example, a passenger has the following double

connection: 100/200/300. If the passenger is
checking in to flight 200, “100” displays. If the
passenger is checking in to flight 300, “200”
displays.

<inbound city> SLC (Conditional) If the passenger has an inbound

connecting flight, this is the airport code of the
inbound flight.

For example, a passenger has the following double

connection: DEN/SLC/JFK/MCO. If the passenger
is checking in at SLC, “DEN” displays. If the
passenger is checking in at JFK, “SLC” displays.

Airport Check-in User Guide 3–5

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying All Passengers on a Flight

Element Example Description

<final destination> 0SLC Three-letter airport code of the final destination.

There are four ways to display the final
XSLC
destination, described below:
YSLC
• 0<airport code> - If the airport code is
#SLC preceded by a zero (0), the passenger is
non-stop to the final destination.

• X<airport code> - If the airport code is

preceded by an “X”, the passenger makes one
connection before arriving to the final
destination. The connecting flight number
displays after the final destination airport
code. For example, XMSP 300 indicates that
the passenger makes one connection on flight
300, with a final destination of SLC.

• Y<airport code> - If the airport code is

preceded by a “Y”, the passenger makes two
connections before arriving to the final
destination. The flight number of the second
connecting flight displays after the final
destination airport code. For example, YMSP
300 indicates that the passenger makes a
second connection on flight 300, with a final
destination of SLC.

• #<airport code> - If the airport code is

preceded by a number, the passenger makes
that number of stops before arriving to the
final destination. For example, 2SLC indicates
that the passenger is on a thru flight that has
two stops, with a final destination of SLC.
However, if the thru flight is either (1) the first
segment of a single connection or (2) the first
or second segment of a double connection,
then an X or Y displays before the final
destination airport code (rather than the
number of stops).

<connecting flight #> 300 (Conditional) If the passenger has to make one or
more connections after the current flight, this is
the flight number of the last connection that has to
be made. For example, a passenger has the
following double connection: 100/200/300. If the
passenger is checking in to flight 100 or 200,
“300” displays.

<operational suffix> F One-character operational suffix appended to a

flight number for flights involved in an operational
procedure.

If the flight number is not entered, no operational

suffix is required.

<# of bags> 2 Number of bags checked in for the passenger.

<recognition code> X Indicates the customer recognition level of the

passenger.

3–6 Airport Check-in User Guide

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying All Passengers on a Flight

Element Example Description

<ticket type indicator> P Indicates the type of ticket the passenger holds for
the flight segment. If the flight segment does not
[New in 3.5]
have an associated ticket type, the field is blank.

• E = Electronic ticket. Corresponds to New

Skies Ticket Type E and H.

• P = Paper ticket. Corresponds to New Skies

Ticket Type A, B, M, and N.

• X = Ticket number is missing.

Airport Check-in User Guide 3–7

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying All Passengers on the Same Reservation

Displaying All Passengers on the Same Reservation

You can display all passengers on the same reservation using the .P command. For example, to
display all passengers on the same reservation as the passenger on line 1, enter .P1.

To display all passengers on the same reservation:

1 Display a passenger on the reservation you want to view.

2 At the command prompt, type .P<pax>, then press Enter.

For example, to view all passengers on the same reservation as the passenger on line 1, enter
.P1. All passengers on the same reservation as the indicated passenger display, similar to the
following:

In this example, there are five passengers on the same reservation.

Note: If you make any changes to the specified reservation, like adding an SSR, type U to update the
reservation information. Then repeat the .P<pax> command to review the changes.

Displaying All Passengers on the Indicated

Reservation
You can also display all passengers on the same reservation by reservation number using the
.<reservation #> command. For example, to display all passengers on the reservation number
D1DFDF enter .D1DFDF.

To display all passengers on the indicated reservation:

1 At the command prompt, type .<reservation #>, then press Enter.

For example, to view all passengers on reservation CZZ1KW, enter .CZZ1KW. All passengers
on that reservation display, similar to the following:

In this example, there are two passengers on the same reservation.

3–8 Airport Check-in User Guide

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying Passengers by Surname

Displaying Passengers by Surname

You can display passengers on a flight according to passenger surname. This may be helpful
when you have flights with dozens of passengers; if you filter passengers by surname, you can
view fewer passengers in the passenger list. For example, to display all passengers whose
surname begins with “BEN,” enter FBEN.
The F command displays confirmed, unconfirmed, and standby passengers. However,
depending on your airline setting, the F command may not display standby passengers (see
Customizing Airport Check-in on page 1-2).

To display passengers by surname:

1 At the command prompt, type F<surname>, then press Enter.

For example, to display all passengers whose surname begins with “BEN”, enter FBEN. All
passengers on the flight whose surname begins with the specified letters display, similar to
the following:

Note: To display the seat map along with the passenger list, enter “F<surname>,SM”.

Displaying Checked-in Passengers

As a flight nears departure, it may be useful to review a list of passengers who have been
checked in to the flight. You can display checked-in passengers using the .C command.

To display checked-in passengers on a flight:

1 At the command prompt, type .C, then press Enter.

All checked-in passengers on the flight display, similar to the following:

Notice that each passenger has a sequence number, followed by a plus sign (+). In this
example, Bill Bennett is sequence #2 and Bob Smith is sequence #1. The plus sign (+) indicates
that the passenger has been checked in, and the sequence number indicates the order in
which the passenger was checked in.

Airport Check-in User Guide 3–9

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying Standby Passengers

Displaying Standby Passengers

You can display all standby passengers on a flight using the .S command. This command
displays standby passengers only; it does not display confirmed or unconfirmed passengers.
Standby passengers are sorted first by priority code, and then by the date/time the passenger was
listed as standby.
Depending on your airline settings, you may be able to display standby passengers using the F
command. For more information on this setting, see Customizing Airport Check-in on page 1-2.

To display standby passengers on a flight:

1 At the command prompt, type .S, then press Enter.

All standby passengers on the flight display, similar to the following:

Passengers are sorted first by priority code, and then by the date/time the passenger was
listed as standby. The following table provides a description of the standby passenger
information line.

Element Example Description

<line #> 1) Line number associated with the passenger. For

example, “1)” represents the passenger on line 1.

<surname>/<given JOHNSON/J Surname and given name are required. For

name>/<middle OHN/DAVID example, “JOHNSON/JOHN” indicates John
name>;<suffix>=<title> =MR Johnson.

If a middle name and/or title is specified for the

passenger at the time of the reservation’s creation
in SkySpeed, SkySales, or RZ, then it is listed
using the specified format. For example,
“JOHNSON/JOHN/DAVID=MR” indicates Mr. John
David Johnson.

<SSR code> MAAS (Conditional) Special Service Request (SSR)

reserved for the passenger, if any. For example,
“MAAS” represents Meet and Assist.

If an asterisk (*) displays next to the SSR (for

example, MAAS*), the passenger has more than
one SSR code for the flight. To view additional SSR
codes for a passenger, use the .SSR<pax>
command.

3–10 Airport Check-in User Guide

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying Standby Passengers

Element Example Description

<customer ID indicator> C (Conditional) If a customer account is associated

with the passenger name, then a “C” displays in
this field.

If a customer loyalty program is associated with

the reservation, the customer recognition level
displays. For example, a ”G” displays for a
program member with Gold status.

Otherwise, no data displays.

For information on associating customer accounts

with passengers, see Associating Passenger
Names with Customer Accounts on page 9-21.

<standby priority code> A Standby priority code. Every standby passenger is

assigned a priority code that determines the order
in which they are considered for the flight, should
a seat become available.

Standby priority codes are configured in

Management Console (System Settings > Codes >
Standby Priorities) and assigned to passengers in
SkySpeed, RZ, and Airport Check-in. See
Changing Standby Priority Codes on page 9-4 and
Displaying Valid Standby Priority Codes on page
10-12.

<date> 01APR Date the passenger was listed as standby.

<time> 10:36 Time the passenger was listed as standby, based

on a 24-hour clock.

<class of service> Y Class of service booked on the itinerary. For

example, “B” represents the B class of service.

<reservation number> UCVRTX* Reservation number, also called record locator and
PNR number. If an asterisk (*) displays after the
reservation number, then the passenger has
manifest comments.

<market> BOSSLC Origin and destination airports for the standby

reservation.

<check-in/boarding status> + Check-in and boarding status of the passenger:

++ • + (passenger is checked in)

• ++ (passenger is checked in and boarded)

<sequence #> 0 (Conditional) This field displays the sequence

number assigned to the passenger. See
Understanding Sequence Numbers on page 4-3.

<seat assignment> 9D (Conditional) Seat assignment.

<# of bags> 0 Number of bags checked in for the passenger.

<recognition code> X Indicates the customer recognition level of the

passenger.

Airport Check-in User Guide 3–11

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying Standby Passengers

Element Example Description

<ticket type indicator> E Indicates the type of ticket the passenger holds for
the flight segment. If the flight segment does not
[New in 3.5]
have an associated ticket type, the field is blank.

• E = Electronic ticket. Corresponds to New

Skies Ticket Type E and H.

• P = Paper ticket. Corresponds to New Skies

Ticket Type A, B, M, and N.

• X = Ticket number is missing.

3–12 Airport Check-in User Guide

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying Boarded Passengers

Displaying Boarded Passengers

As a flight nears departure, it may be useful to review a list of passengers who have boarded the
flight. You can display boarded passengers using the .QB command.

To display boarded passengers:

1 At the command prompt, type .QB, then press Enter.

All boarded passengers on the flight display, similar to the following.

Notice that each passenger has a sequence number along with two plus signs (++). The “first”
plus sign (+) indicates that the passenger has been checked in, and the “second” plus sign
indicates that the passenger has boarded the flight. The sequence number indicates the order
in which the passenger was checked in.

Displaying “Un-boarded” Passengers

You can display a list of passengers who have been checked in to a flight, but have not yet
boarded, using the .QN command.

To display un-boarded passengers:

1 At the command prompt, type .QN, then press Enter.

All passengers on the flight who have checked in but not yet boarded display, similar to the
following:

Notice that each passenger has only one plus sign (+), indicating that the passenger has
checked in to the flight, but not yet boarded (boarded passengers have two plus signs (++)).

Airport Check-in User Guide 3–13

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying Passengers Who Have Not Checked In

Displaying Passengers Who Have Not Checked In

As a flight nears departure, it may be useful to review a list of passengers who have not yet
checked in to the flight, or “no-shows”. You can display these passengers using the .N command.
The .N command displays both confirmed and unconfirmed passengers. If your airline is
configured to display standby passengers with the F command, then standby passengers display
with the .N command as well.
The display includes the first SSR code associated with each passenger if SSRs are present. SSRs
are sorted just as they are for all passenger display commands. However, you can specify SSRs to
be excluded from the .N display using the RestrictedSSRsInCheckIn setting in
CheckinConfig.xml. For more information on sorting SSRs refer to Displaying All Passengers on a
Flight on page 3-3.

To display “no-show” passengers:

1 At the command prompt, type .N, then press Enter.

All passengers on the flight who are not checked in display, similar to the following:

Notice that “no-show” passengers do not have a sequence number or a plus sign (+). (The plus
sign (+) indicates that the passenger has been checked in, and the sequence number indicates
the order in which the passenger was checked in.)

3–14 Airport Check-in User Guide

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying Passengers Who Do Not Have Assigned Seats

Displaying Passengers Who Do Not Have Assigned

Seats
As a flight nears departure, it may be useful to review a list of passengers who do not have an
assigned seat. You can display these passengers using the .NS command.
The .NS command displays both confirmed and unconfirmed passengers. If your airline is
configured to display standby passengers with the F command, standby passengers display with
the .NS command as well.

To display passengers without seat assignments:

1 At the command prompt, type .NS, and then press Enter.

All passengers on the flight who do not yet have a seat assignment display, similar to the
following:

Airport Check-in User Guide 3–15

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying Code Share Passengers that are Associated with Another Marketing Designator

Displaying Code Share Passengers that are

Associated with Another Marketing Designator
Marketing code share flight may be marketed by multiple carriers. To see the marketing carrier’s
flight number and any passengers who made reservations through a specific marketing carrier,
use the .MC command.

To display passengers by marketing designator:

1 At the command prompt, type .MC, then press Enter.

A list of all airlines that are marketing the current flight displays, along with the flight number
for each.

2 At the command prompt, type .MC<line #>, then press Enter.

For example, to see all passengers who made their reservations through the airline MA, type
.MC2, and press Enter. The passenger list displays, similar to the following:

3–16 Airport Check-in User Guide

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying Thru Passengers

Displaying Thru Passengers

You can display passengers whose “thru” flight stops at the currently loaded airport using the .T
command. For example, a passenger has a thru flight from LAX–ORD that stops in SLC. If you
load the flight segment from SLC–ORD, the passenger name displays when you enter .T. If you
load the flight segment from LAX–ORD and enter .T, the passenger name does not display,
because the “stopover” is not in LAX.

To display “thru” passengers on a flight:

1 At the command prompt, type .T, then press Enter.

All “thru” passengers display, similar to the following:

In this example, Thurl Putmee is arriving from LAX, stops once, and continues on with a final
destination of ORD.

Airport Check-in User Guide 3–17

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying Connecting Passengers

Displaying Connecting Passengers

You can display inbound, connecting passengers using the .X command. These are passengers
coming from inbound flights who are making connections at the current station.
Use the .DN and .IN command to display a list of downline or inbound, connecting passengers
for a particular flight. Refer to Displaying Downline Passengers on page 10-6 and Displaying
Inbound, Connecting Passengers on page 10-10 for more information.

To display connecting passengers for the current station:

• At the command prompt, do one of the following:

— To display all connecting passengers, type .X, then press Enter.

— To display connecting passengers coming from a particular flight, type .X<flight #>, then
press Enter. For example, to display the connecting passengers coming from flight 100,
enter .X100.
— To display connecting passengers coming from a particular airport, type .X<airport
code>, then press Enter. For example, to display the connecting passengers coming from
LAX, enter .XLAX.
The connecting passengers display, similar to the following:

In this example, there are four passengers making a connection at the currently loaded
airport. Bob Dean makes one more connection on flight 566, with a final destination of JFK.
Marty, Cary, and Mary Pack fly non-stop to ORD.

Displaying Upgraded Passengers

You can display all upgraded passengers using the .U command. These are passengers who have
upgraded their fare to a higher class of service.

To display all upgraded passengers:

• At the command prompt, type .U, then press Enter.

3–18 Airport Check-in User Guide

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying Upgraded Passengers

All upgraded passengers display, similar to the following:

The upgrade symbol (^) displays after the booking status (for example, HK^).

Airport Check-in User Guide 3–19

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying Passengers With Premium Fares

Displaying Passengers With Premium Fares

You can display all passengers why have purchased premium fares using the .PS command.
Note Premium Fares are configured in CheckinConfig.xml. For details, refer to Customizing Airport
Check-in on page 1-2.

To display a list of premium fare passengers:

• At the command prompt, type .PS, then press Enter.

All premium passengers display, similar to the following:

Note Standby passengers are also included in the premium service display list.

The header “Premium Fare” displays when you list passengers using the .PS command. The
passengers are listed by seat number, starting with passengers without seats listed
alphabetically.

Displaying Passengers with Manifest Comments

You can display all passengers on a flight that have manifest comments using the .M command.
Manifest comments alert airline personnel to any special conditions of passengers on the flight.
For example, a passenger in a wheelchair may have a manifest comment that reads: Passenger in
a wheelchair.
Manifest comments are added to reservations in SkySpeed and RZ.

To display passengers with have manifest comments:

1 At the command prompt, type .M, then press Enter.

All passengers that have manifest comments display, similar to the following:

3–20 Airport Check-in User Guide

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying Passengers with SSRs

Notice that an asterisk (*) displays next to the reservation number (AZZ2XP). This indicates
that the reservation has manifest comments.
To view the manifest comments for a passenger, use the .M<pax> command. For example, to
view the manifest comments for the passenger on line 1, enter .M1.

Displaying Passengers with SSRs

You can display passengers with Special Service Requests (SSRs) using the .SSR command. SSRs
are special services offered by your airline to passengers. For example, a passenger may request
language assistance at the check-in counter.
The display includes the first SSR code associated with each passenger. SSRs are sorted just as
they are for other passenger display commands. However, you can specify SSRs to be excluded
from the .SSR display using the RestrictedSSRsInCheckIn setting in CheckinConfig.xml. For
more information on sorting SSRs refer to Displaying All Passengers on a Flight on page 3-3.
An asterisk (*) next to the SSR code indicates that the passenger has more than one SSR. To view
SSR details, use the .SSR<pax> command. Refer to Displaying the SSRs Assigned to a Passenger
on page 9-30 for details.
For more information on SSRs, see Assigning SSRs on page 9-6.

To display passengers with SSRs:

1 At the command prompt, type .SSR, then press Enter.

All passengers that have SSRs display, similar to the following:

In the example above, three passengers have SSRs: Karie Johnson, John David Doe, and Jeff
G. Smith. Notice that an asterisk displays next to the SSR for Jeff Smith (WCHS*). This
indicates that he has more than one assigned SSR. Each additional SSR is listed below the
passenger name.
Note To view SSR details for a passenger, type .SSR<pax>.

With this information, you can notify other airline personnel of the special service requests.

Airport Check-in User Guide 3–21

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying Passengers With Ticket Numbers

Displaying Passengers With Ticket Numbers

You can display a list of confirmed and standby passengers who have ticket numbers for a flight
using the .TKT command. The display does not include passengers on passive segments.
Passengers are sorted first by ticket type and then alphabetically by name as with the F
command.

To display all passengers with ticket numbers on a flight:

1 At the command prompt, type .TKT, then press Enter.

All passengers who have ticket numbers for the flight display, similar to the following:

3–22 Airport Check-in User Guide

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying Passengers With Ticket Numbers

The following table provides a description of the information displayed.

Element Example Description

Passenger Information

<line #> 1) Line number associated with the passenger. For

example, “1)” represents the passenger on line 1.

<surname>/<given CHAVEZ/ Surname and given name are required. For

name>/<middle LINDA example, “CHAVEZ/LINDA” indicates Linda
name>=<title> Chavez.

If a middle name and/or title is specified for the

passenger at the time of the reservation’s creation
in SkySpeed, SkySales, or RZ, then it is listed
using the specified format. For example,
“DOE/JOHN/DAVID=MR” indicates Mr. John David
Doe.

If the passenger is associated with a lap infant, an

(I) indicator follows the passenger name.

<IROP indicator> ! (Conditional) Indicates that the passenger was

moved to the flight via IROP.

<check-in/boarding status> + (Conditional) Check-in and boarding status of the

passenger:

• + (passenger is checked in)

• ++ (passenger is checked in and boarded)

• +% (passenger is checked in but has not yet

received a boarding directive)

<reservation number> MNO234 Reservation number, also called record locator or

PNR number.

<booking status> HK Booking status of the passenger.

• HK - Confirmed

• HL - Standby

• HU - Unconfirmed

<ticket type> A Indicates the ticket type as follows:

• (E) Electronic-No Lift Required

• (H) Host issued Electronic-No Lift Required

• (A) Paper Tkt (Automated)-Lift Required

• (B) Paper Tkt (Automated)-No Lift Required

• (M) Paper Tkt (Manual)-Lift Required

• (N) Paper Tkt (Manual)-No Lift Required

• (X) Missing

<ticket number> 1234567890 Ticket number (13 digits).

001

Airport Check-in User Guide 3–23

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying Passengers With Ticket Numbers

Element Example Description

<coupon number> 1 (Conditional) Coupon number ranging from 1 to 4.

Mandatory for electronic tickets (type E and H)
and not applicable to automated or manual paper
tickets (A, B, M, and N).

<infant ticket number> 1234567890 (Conditional) Ticket number of the lap infant on
011 the reservation (13 digits).

<infant coupon number> 3 (Conditional) Coupon number ranging from 1 to 4

for the infant on the reservation. Mandatory for
electronic tickets (type E and H) and not applicable
to automated or manual paper tickets (A, B, M,
and N).

Ticket Subtotal/Total Information

<Ticket type> (A)Paper Tkt Indicates the type of tickets grouped in the
(Automated) preceding section.
-Lift
Required

<ticket subtotal> 4 Number of passengers with the given type of

ticket for the flight.

<infant subtotal> 0 Number of infants with the given type of ticket for
the flight.

Ticket Summary

<total> 20 Total number of tickets on the flight.

<infant total> 3 Total number of infant tickets on the flight.

Missing Tickets

<passenger information 22) List of missing tickets. Same as passenger

line> information listed above.

3–24 Airport Check-in User Guide

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying Passengers with International Documents

Displaying Passengers with International

Documents
You can display passengers that have passport, visa, and other international documents using
the .DOC command.
To view passengers that do not have international documents, see Displaying Passengers without
International Documents on page 3-26.

To display passengers with international documents:

1 (Conditional) If you need to update the passenger information, type U, then press
Enter.

After entering passport or other international document information for a passenger, you
must first enter the U command to update the passenger information. Otherwise, the
passenger information is not updated on the screen.

2 At the command prompt, type .DOC, then press Enter.

All passengers on the flight who have passports, visas, or other international documents
display, similar to the following:

3 (Optional) To view the documents for a passenger, type .DOC<pax>, then press Enter.

For example, to view the documents for the passenger on line 1, enter .DOC1. The document
information displays, similar to the following:

In this example, Abby Akol was born 8 February 1964. She has a passport and a
miscellaneous travel document, which in this case is a visa (“V”). Document types are
configured in Management Console (System Settings > Codes > Document Types).

Airport Check-in User Guide 3–25

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying Passengers without International Documents

Displaying Passengers without International

Documents
You can display passengers that do not have passports or other international documents using
the .XDOC command.
You can enter passports and other international documents for passengers at any time (see
Entering Travel Documents on page 9-9).

To display passengers without international documents:

1 At the command prompt, type .XDOC, then press Enter.

All passengers on the flight who do not have passports or other international documents
display, similar to the following:

3–26 Airport Check-in User Guide

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying Passengers with APIS Information

Displaying Passengers with APIS Information

The .APIS command provides a way for you to identify passengers whose APIS information has
been collected to send to customs. Under APIS, international air carriers are required to provide
customs with an electronic manifest detailing the name, date of birth, sex, travel document
number, and nationality of the document of each passenger and crew member before the aircraft
lands in the domestic country.
There are three variations of the .APIS command, described below:

• .APIS - Lists each passengers on the flight whose APIS information has been collected to
send to customs.
• .APIS<PAX#> - Displays APIS information for the indicated passenger only.
• .APIS*<DOC #> - Displays and verifies the selected document for the currently loaded
passenger.
For more information on APIS, refer to the New Skies Functional Knowledge Base.

To display passengers with APIS information:

1 At the command prompt, type .APIS and then press Enter.

A prompt similar to the following displays:

2 Do one of the following:

• If you want to include passengers without verified documents in the report of passengers
whose APIS information has been collected, type Y (yes), then press Enter.
• If you do not want to include passengers without verified documents in the report of
passengers whose APIS information has been collected, type N (no), or just press Enter.
A prompt similar to the following displays:

3 Do one of the following:

• If you want to include the passengers’ destination addresses in the report of passengers
whose APIS information has been collected, type Y (yes), or just press Enter.
• If you do not want to include the passengers’ destination addresses in the report of
passengers whose APIS information has been collected, type N (no), then press Enter.

Airport Check-in User Guide 3–27

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying Passengers with APIS Information

The resulting screen prompts you to select an output option for the report:

— Print to Screen
Outputs the report to your computer screen.
— Select Printer
Allows you to select a printer by entering the printer ID.
— List Printers
Allows you to select the printer from a list of pre-configured printers.

4 Select an output option for the report, then press Enter.

A report listing all passengers whose APIS information has been collected is displayed,
similar to the following:

The following table describes the information provided in the report.

Element Example Description

PNR PPZ1UV The reservation number.

Last Name JENSON Passenger last name.

First Name FREDDY Passenger first name.

3–28 Airport Check-in User Guide

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying Passengers with APIS Information

Element Example Description

Middle Name RAY Passenger middle name.

G M Passenger gender (M = male, F = female).

DOB 710106 Passenger date of birth using the following format

YYMMDD. For example, 710106 indicates the
passenger was born January 6, 1971.

Nationality US Two-character IATA code for the passenger’s

country of citizenship.

Res US Two-character IATA code for the passenger’s

country of residence.

WL Wa Indicates whether a passenger is in watch list.

Ver Y Indicates whether the documents have been

verified (Y = yes, N = no).

Sb N Indicates whether the passenger is flying standby

(Y = yes, N = no).

Doc Type V The type of document entered. Document types

are defined in Management Console (System
Settings > Codes > Document Types).

Number X125689745 Travel document number (unique identifier).

55

Exp 101231 Document expiration date using the following

format YYMMDD. For example, 101231 indicates
the document expires December 31, 2010.

Cy 2 Two-character IATA code for the country issuing

the travel document.

Address 123 Elm St. Passenger’s destination address.

Batavia, IL
60510

Airport Check-in User Guide 3–29

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying Passengers with Missing Security Information

Displaying Passengers with Missing Security

Information
• New Skies Versions Before 3.4.13
The following commands were replaced by the .GOVSTATUS command in New Skies 3.4.13.
If any of these commands are entered, a message displays prompting the agent to use the
.GOVSTATUS command instead. Refer to Using the .GOVSTATUS display command on page
3-31 for details.

— Displaying Passengers with Missing APIS Information

The .APIS/BAD command provides a way for you to identify passengers whose APIS
information is not complete and valid. Under APIS, international air carriers are required
to provide customs with an electronic manifest detailing the name, date of birth, sex,
travel document number, and nationality of the document of each passenger and crew
member before the aircraft lands in the domestic country.
To display passengers with incomplete or invalid APIS information, type .APIS/BAD and
then press Enter. The output displayed is similar to the output from the .APIS command
with one exception. The check-in status for each passenger is included in the list of
passengers without valid APIS information.
Note This command can also be used with E-Borders.

For more information on APIS, refer to the New Skies Functional Knowledge Base.
— Displaying Checked Passengers Who Require Secure Flight Validation
Under Secure Flight, all air carriers flying in the United States are required to compare
each passenger’s and crew member’s name, date of birth, and gender against the
Transportation Security Administration (TSA) watch list entries. The .SF/BAD command
enables you to identify passengers who require additional Secure Flight validation. A
passenger may be on the list for the following reasons:

— After the passenger checked in to the flight, Navitaire received an unsolicited message
denying the passenger flight clearance.
— The information used to validate the passenger (name, date of birth, or gender) has
been updated since the passenger was cleared.
To display passengers whose Secure Flight clearance must be verified, type .SF/BAD and
then press Enter. The output displayed is similar to the output from the .APIS command.
Refer to Displaying Passengers with APIS Information on page 3-27 for report field
descriptions.
In order to obtain Secure Flight clearance for these passengers, you must un-check and
re-check each passenger on the list. Refer to Removing Passengers from Check-in on page
4-35 and Checking In Passengers on page 4-1 for details.
For more information on Secure Flight, refer to the New Skies Functional Knowledge Base.
— Displaying Passengers Who Are Not Cleared for APPS
For carriers who have APPS enabled for a single country, the .APC command provides a
way for you to identify passengers who are checked in for a flight but do not yet have

3–30 Airport Check-in User Guide

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying Passengers with Missing Security Information

APPS clearance to board. The APC command enables you to request clearance for those
passengers. For more information, refer to Summary of Check-in Commands on page A-1.

To display passengers who do not have APPS clearance:

Note: The APC and APPSALL commands are intended for use by carriers who have APPS
enabled for a single country.

1 At the command prompt, type .APC and then press Enter.

All passengers who are currently checked in and do not have a positive boarding
directive are displayed similar to the following.

2 (Conditional) To send APPS data, do one of the following:

— To request clearance for one passenger type APC<pax#>, then press Enter.
For example, to submit APPS data for the passenger on line one, type APC1. The
data is collected as described in Checking In Passengers with APPS Validation on
page 4-20 and is transmitted to the appropriate government.
— To request clearance for all passengers who do not yet have permission to
board, type APPSALL, then press Enter.

For example, to submit APPS data for all passengers, type APPSALL. The system
gathers APPS info from each PNR for which clearance is needed and transmits it to
the appropriate government. If there is no travel document associated with a
reservation, no data is sent for that passenger. No overrides are allowed with this
command.

• New Skies Versions 3.4.13 and Above

The .GOVSTATUS command was introduced in New Skies 3.4.13 to simplify government
security processing during check-in.

Using the .GOVSTATUS display command

The .GOVSTATUS command displays all checked-in and boarded passengers with missing
security information as well as passengers with manually entered clearance. It also displays a
note if passenger is missing a verified document or missing a destination address when
required to.
To display this list, type .GOVSTATUS, and then press Enter. The output displays all
checked-in and boarded passengers without positive clearance and passengers with manual
clearance.

Airport Check-in User Guide 3–31

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying Passengers with Missing Security Information

3–32 Airport Check-in User Guide

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying APPS Overrides

Displaying APPS Overrides

Use the .APPSOVR command to generate a list of the passengers whose APPS boarding directive
was overridden, along with the agent responsible for the override.
For more information, refer to Appendix A, Summary of Check-in Commands.

To display a list of APPS overrides for the current flight:

• At the command prompt, type .APPSOVR and then press Enter.

All passengers with manually entered or overridden APPS status are displayed similar to the
following.

The “APPS Overrides” list shows passengers who failed to receive a positive boarding
directive for one of the reasons listed in APPS Failure Scenarios on page 4-24. The “Manual
APPS Overrides” list shows passengers whose APPS directives were entered manually by the
agent due to a connectivity failure within APPS.

Displaying Passengers with Customer Accounts

Any time a customer account is created for a passenger, the customer account is automatically
associated with the passenger name. You can display passengers that have customer accounts
associated with their name using the .CU command. Created in SkySpeed or SkySales, customer
accounts store passenger information, such as addresses, phone numbers, seating preferences,
and so on.
You can create or remove customer account associations at any time (see Associating Passenger
Names with Customer Accounts on page 9-21 and Removing Customer Account Associations on
page 9-22).

To display passengers associated with customer accounts:

1 At the command prompt, type .CU, then press Enter.

Airport Check-in User Guide 3–33

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying Passengers Associated with Customer Loyalty Programs

All passengers on the flight who have customer accounts associated with their passenger
name display, similar to the following:

If a customer account is associated with the passenger name, a C displays after the sequence
number and the customer ID is appended to the passenger line. If a customer loyalty program
is associated with the reservation, the customer recognition level displays instead. For
example, a G is displayed for a program member with Gold status.

Displaying Passengers Associated with Customer

Loyalty Programs
You can use the .LP command to list the passengers associated with customer loyalty programs.

To display passengers on the current flight who have customer loyalty

programs associated with their reservations:
• At the command prompt, type .LP, then press Enter.
Passengers who have customer loyalty information associated with their reservations are
displayed, similar to the following:

In this example, A. Traveler belongs to the B loyalty program and holds B program level. The
loyalty program account number is 444555666.

3–34 Airport Check-in User Guide

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying Passengers by Sequence Number

Displaying Passengers by Sequence Number

You can display passengers by sequence number using the .Q command. Passengers are assigned
a sequence number when they check in to a flight. This number indicates the order in which
passengers were checked in.
For more information on sequence numbers, see Understanding Sequence Numbers on page 4-3.

To find a passenger by sequence number:

• At the command prompt, type .Q<sequence #>, then press Enter.

For example, to find the passenger assigned sequence #1, enter .Q1.
The passenger assigned the specified sequence number displays, similar to the following:

Displaying the Passenger Assigned a Specific Seat

You can display the passenger assigned to a specific seat using the .<seat #> command. For
example, to display the passenger assigned seat 8A, enter .8A.

To display the passenger assigned to a specific seat:

• At the command prompt, type .<seat #>, then press Enter.

For example, to display the passenger assigned seat 4C, enter .4C. The passenger information
line displays, similar to the following:

In this example, Jonathon Smith is assigned seat 4C.

Displaying Passengers on Locked Reservations

When a passenger or reservation is assigned to a queue that is set up to lock reservations, the
passenger is unable to check in until the lock is cleared. You can display passengers whose
reservations are locked using the .L command.

To display all passengers on locked reservations:

• At the command prompt, type .L, then press Enter.

Airport Check-in User Guide 3–35

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying Passengers on Locked Reservations

A list of passengers whose reservations are locked and the queues they are assigned to
displays, similar to the following:

Sometimes, agents want to view more information and find out why a passenger or reservation
is on a lock queue. There are two ways to accomplish this in Check-in:

• The .L<pax#> command enables you to view a summary of the match information for a
particular passenger.
• The .WL<pax#> command takes this one step farther by also showing you the watch list
entry that caused the passenger or reservation to be locked.

To display brief match details for a passenger on a locked reservation:

• At the command prompt, type .L<pax#>, then press Enter.

For example, enter .L3 to see details about the third passenger in the list above.

In this example, the passenger SMITH/S matched two watch list entries for the SWL Security
Watch List queue.
Note Enter the .L<pax#> command following the F command to see watch list matches for all
lock queues for a particular passenger. For passengers who are on multiple lock queues,
enter .L<pax#> following the .L command to see details about a specific queue.

To display full match details for a passenger on a locked reservation:

• At the command prompt, type .WL<pax#>, then press Enter.

3–36 Airport Check-in User Guide

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying Passengers on Locked Reservations

For example, enter .WL3 to see details about the third passenger in the list above.

In this example, there are two pages of match details. Enter MD to continue to the next page.

The .WL command allows you to view not only the match information, but also the watch list
entry that resulted in the match.
Note Enter the .WL<pax#> command following the F command to see watch list matches for
all lock queues for a particular passenger. For passengers who are on multiple lock queues,
enter .WL<pax#> following the .L command to see details about a specific queue.

Airport Check-in User Guide 3–37

 CHAPTER 3 DISPLAYING PASSENGER LISTS
Displaying Passengers with a Balance Due

Displaying Passengers with a Balance Due

Before closing a flight, you may want to search for passengers who have a balance due on their
reservations. If there are passengers on the flight who are missing required EMDs and have a
balance due when you run the CF command to close the flight, the system displays a warning
and lists the passengers before closing the flight. The .BD command enables you to list these
passengers so you may resolve the remaining balances and complete EMD requirements before
you attempt to close the flight.

To display all passengers with a balance due:

• At the command prompt, type .BD, and then press Enter.
This displays a list of passengers whose reservations are not paid in full. Notice that the
status of each passenger is HU.

This list follows the same format as the results from the F command. Refer to Displaying All
Passengers on a Flight on page 3-3 for details.

3–38 Airport Check-in User Guide

4 Checking In Passengers

Before passengers may board an aircraft, they must first check in to the flight.
Because airlines have unique needs and procedures for checking in passengers, the check-in
procedure is configurable by each airline. See Customizing Airport Check-in on page 1-2.
During the check-in process, you may need to perform additional processes as well:
• Assign seats. If your airline has assigned seating, you need to ensure that every passenger
has a seat assignment. Seats are assigned in SkySpeed and Airport Check-in. See Chapter 5,
Assigning Seats.

• Check in baggage. After a passenger checks in, you are prompted to check in baggage for
the passenger. See Chapter 6, Checking In Baggage.
• Check in same-day return passengers. For passengers who have same-day return flights,
you may be prompted to check them in to the return flight after you check them in to the
outbound flight. See Checking In Passengers with Same-day Return on page 4-10.
• Clear locked passengers from a queue. A passenger whose reservation is locked cannot
check in until the reservation is removed from the queue. See Clearing Locked Passengers from
a Queue on page 4-4.

• Check in a passenger with an infant. If there is an SSR in the system indicating that a
passenger is traveling with an infant and the system is configured to print infant boarding
passes, an infant boarding pass is printed in addition to the adult boarding pass. The
boarding pass may be identical to the adult pass with the exception of the name, date of birth,
passport information and ticket number. However, through Management Console, you can
set up a separate boarding pass format to be used for all infants. Refer to the Management
Console help file for details.
There are two ways to track the check-in progress of a flight:

• Update the passenger totals for the flight (U command). The passenger totals include
several categories, such as the number of passengers who have checked in, boarded, have not
yet checked in, and so on. See Displaying the Passenger Count on page 10-2.
• Generate a manifest report. See the documentation for the Manifest with Connection
Information Report and Manifest with Trip Detail Report in the SkyPort Reports User Guide.
After a passenger is checked in to a flight, the system prints a boarding pass for the passenger. In
addition, the system assigns a sequence number to the passenger. The sequence number
indicates the order in which passengers checked in.

In this chapter:

• Understanding Sequence Numbers on page 4-3

• Checking In Passengers on page 4-4

— Clearing Locked Passengers from a Queue on page 4-4

Airport Check-in User Guide 4–1

 CHAPTER 4 CHECKING IN PASSENGERS

— Checking In Confirmed Passengers Individually or by PNR on page 4-5

— Checking In All Confirmed Passengers on page 4-7
— Checking In Standby Passengers Individually or by PNR on page 4-7
— Checking In All Standby Passengers on page 4-9
— Checking In Passengers with Same-day Return on page 4-10
— Checking In Passengers on Flights Requiring Government Validation on page 4-11
— Checking and Unchecking Passengers on a Marketing Code Share, Outbound Interline, or
Third-Party-Controlled Flight on page 4-30

• Removing Passengers from Check-in on page 4-35

— Removing Confirmed Passengers from Check-in Individually on page 4-35

— Removing All Confirmed Passengers from Check-in on page 4-36
— Removing Standby Passengers from Check-in Individually on page 4-37
— Removing All Standby Passengers from Check-in on page 4-37
• Re-printing Itineraries on page 4-39
• Re-printing Boarding Passes on page 4-39
• Printing Gate Passes on page 4-40

4–2 Airport Check-in User Guide

 CHAPTER 4 CHECKING IN PASSENGERS
Understanding Sequence Numbers

Understanding Sequence Numbers

Sequence numbers are issued to passengers at check-in. These numbers are generated
automatically by the system according to the order in which passengers check in. The first
passenger checked in is assigned sequence #1, the second passenger checked in is assigned
sequence #2, and so on.
The sequence number displays on the passenger information line and is located after the
passenger name and before the check-in/boarding status. In the example below, Jonathon Smith is
assigned sequence #3:

Airport Check-in User Guide 4–3

 CHAPTER 4 CHECKING IN PASSENGERS
Checking In Passengers

Checking In Passengers
This section covers the major scenarios for checking in passengers:
• Clearing Locked Passengers from a Queue on page 4-4
• Checking In Confirmed Passengers Individually or by PNR on page 4-5
• Checking In All Confirmed Passengers on page 4-7
• Checking In Standby Passengers Individually or by PNR on page 4-7
• Checking In All Standby Passengers on page 4-9
• Checking In Passengers with Same-day Return on page 4-10
• Checking In Passengers on Flights Requiring Government Validation on page 4-11
• Checking and Unchecking Passengers on a Marketing Code Share, Outbound Interline, or
Third-Party-Controlled Flight on page 4-30

Clearing Locked Passengers from a Queue

The most restrictive queues, called “no fly” queues, actually prevent passengers from checking
in for a flight. If you attempt to check in a passenger on a PNR that is on a no fly queue, a
message similar to the following is displayed:

With the correct permission (Allow clear passenger from a Watch List) in Management Console
(System Users > Roles) you can clear passengers on a locked PNR so that they may be checked in.
The CL command removes the PNR or passenger from the specified queue that locked the PNR
or passenger. See Role Settings in Management Console on page 1-12 for details.

To clear a locked passenger from a “no fly” queue:

1 Type CL<pax line #>/<queue code>.

2 At the Contact Person prompt, enter the name or Agent ID of the person who
approved clearing the passenger from the queue.

3 At the Reason prompt, enter a reason for clearing the passenger from the queue.

A message similar to the following is displayed:

Important: Before the cleared passenger can be checked in to the flight, you must first execute the U
(update) command.

4–4 Airport Check-in User Guide

 CHAPTER 4 CHECKING IN PASSENGERS
Checking In Passengers

Checking In Confirmed Passengers Individually or by PNR

You can check in one confirmed passenger at a time or all confirmed passengers on a reservation
using the C command.
There are many combinations of the C command. For example, you can assign a seat at the time
of check-in, bypass the seat assignment requirement, and so on. For more information, see C
Command on page A-32.

If a flight is international and APIS or APPS is required, the system uses additional validation
criteria when checking in passengers. See Checking In Passengers on Flights Requiring
Government Validation on page 4-11.

Inter Airline Through Check-in (IATCI) enables passengers to check in with the first
Navitaire-hosted carrier in their itinerary and be checked in for connecting flights operated by a
different carrier at the same time. When an IATCI passenger or group of passengers are checked
in for a connecting flight with the same board and off points, a message is sent to the other airline
asking that the passengers also be checked in for the downline flights.

To check in confirmed passengers individually or by PNR:

1 Display the confirmed passengers to check in.

See Chapter 3, Displaying Passenger Lists.

If you are checking in all passengers on the same reservation, you can use the .P<pax>
command to display the passengers. For example, to display all passengers on the same
reservation as the passenger on line 1, enter .P1. See Displaying All Passengers on the Same
Reservation on page 3-8.

2 (Conditional) If you are checking in ONE passenger, do one of the following:

• If the passenger already has a seat assignment, type C<pax> , then press Enter. For
example, to check in the passenger on line 1, enter C1.
• To assign a seat, type C<pax>/<seat> , then press Enter. For example, to check in the
passenger on line 1 and assign seat 8A, enter C1/8A.
• To bypass the seat assignment requirement, type C<pax>/* , then press Enter. For
example, to check in the passenger on line 1, enter C1/*.
The passenger is checked in and assigned a sequence number for boarding the aircraft.

3 (Conditional) If you are checking in consecutive passengers on the SAME

RESERVATION, do one of the following:

• If the passengers already have seat assignments, type C<pax>-<pax> , then press Enter.
For example, to check in the passengers on lines 1–3, enter C1-3.
• To assign seats, type C<pax>-<pax>/<seat> , then press Enter. For example, to check
in the passengers on lines 1–3 and assign seats sequentially (where possible), beginning
with seat 8A, enter C1-3/8A.
• To bypass the seat assignment requirement, type C<pax>-<pax>/* , then press Enter.
For example, to check in the passengers on lines 1–3, enter C1-3/*.
The passengers are checked in and assigned sequence numbers for boarding the aircraft.

Airport Check-in User Guide 4–5

 CHAPTER 4 CHECKING IN PASSENGERS
Checking In Passengers

4 (Conditional) If prompted to ask security questions, ask the questions, and then enter
the responses. Press Enter after each response.

Enter Y for “yes” or N for “no.” The system does not enforce whether the responses to these
questions are valid. Rather, it is up to the individual agent to determine whether a passenger
may continue with the check-in process.

5 (Conditional) Enter the final destination for check-in:

Depending on the settings in the CheckinConfig.xml file, you may be prompted for the
destination. The passenger is checked through to the destination you enter and remains
unchecked for any additional downline segments in the journey.

6 (Conditional) Pull paper tickets if prompted to by the system:

If there are paper tickets associated with the reservation, the system prompts you to collect
them at this time.
Note Paper tickets may not be required depending on your Booking Configuration settings. Refer
to the Management Console help file for more information about the Do Not Require
Ticket/Coupon Lifts for Paper Tickets configuration.

7 (Conditional) Check in any baggage as needed.

See Chapter 6, Checking In Baggage. If you are checking in multiple passengers, you are
prompted to check in baggage for each passenger individually.
If the Display Downline Segments in Checkin setting in the SkyPort Settings dialog is
checked, any existing onward connection information displays.
The passenger information line displays, which indicates the sequence number, check-in
status (+), and number of checked bags similar to the following:

In this example, Jonathon Smith has checked in (+) and been assigned sequence number 3. He
did not check any bags.
At this point, the boarding pass and any bag tags to be printed are sent to the printer.
For thru flights (the flight number does not change), the passenger is automatically checked
in to all remaining legs of the flight. For connecting flights (the flight number changes), the
passenger may or may not be checked in to the connecting flights, depending on your airline
settings (see Customizing Airport Check-in on page 1-2). For IATCI flights, a message is sent to
the other carrier asking that the passenger be checked in for the downline flights.
In release 3.5, functionality was added to interactively update the coupon status when a
passenger checks in. If the update fails and you are assigned the Allow Agent to Override
E-Ticket Coupon Status role, the system asks if you want to override the coupon status and
continue checking in. If you choose to override the coupon status, a booking history record is
created. Refer to Role Settings in Management Console on page 1-12 for details.

4–6 Airport Check-in User Guide

 CHAPTER 4 CHECKING IN PASSENGERS
Checking In Passengers

Checking In All Confirmed Passengers

You can check in all confirmed passengers on a flight using the CALL command. If you choose to
use the CALL command, the system does not prompt you to assign seats or check in baggage.
Rather, you must do so manually.
If a flight is international and APIS or APPS is required, the system uses additional validation
criteria when checking in passengers. See Checking In Passengers on Flights Requiring
Government Validation on page 4-11. Using the CALL command bypasses this validation.

Important Travel documents are not verified when you use CALL to check in all confirmed
passengers.

To check in all confirmed passengers on a flight:

1 At the command prompt, type CALL , then press Enter.

A confirmation prompt displays.

2 Type Y , then press Enter.

All confirmed passengers are checked in to the flight. If your airline has assigned seating,
each passenger is assigned a sequence number for boarding the aircraft. To view the sequence
numbers, display the passengers using the F command.
You can assign seats using the SA command (see Chapter 5, Assigning Seats).
You can check in baggage using the B, AB, and MB commands (see Chapter 6, Checking In
Baggage).

Checking In Standby Passengers Individually or by PNR

You can check in one standby passenger at a time or all standby passengers on a reservation
using the CS command.
There are many combinations of the CS command. For example, you can assign a seat at the time
of check-in, check in multiple passengers on a reservation at the same time, and so on. For more
information, see CS Command on page A-34.
The CheckinConfig.xml file contains a setting that enables you to specify whether the system
should convert HL bookings to HK upon flight close, or whether standby bookings should
remain HL after the flight is closed. Refer to CheckinConfig.xml on page 1-3 for details.
If a flight is international and government validation is required, the system uses additional
validation criteria when checking in passengers. See Checking In Passengers on Flights Requiring
Government Validation on page 4-11.

To check in standby passengers individually or by PNR:

1 Type .S to display the standby passengers to check in.

See Displaying Standby Passengers on page 3-10.

Airport Check-in User Guide 4–7

 CHAPTER 4 CHECKING IN PASSENGERS
Checking In Passengers

The passenger list displays similar to the following:

Notice that each passenger is assigned a standby priority code (in the example above, “A”).
Standby priority codes indicate the priority in which standby passengers should be checked
in to the flight if a seat becomes available. To view the standby priority codes for your airline,
enter the STBY command.
If you are checking in all passengers on the same reservation, you can use the .P<pax>
command display the passengers. For example, to display all passengers on the same
reservation as the passenger on line 1, enter .P1. See Displaying All Passengers on the Same
Reservation on page 3-8.

2 (Conditional) If you are checking in ONE passenger, do one of the following:

• If the passenger already has a seat assignment, type CS<pax> , then press Enter. For
example, to check in the passenger on line 1, enter CS1.
• To assign a seat, type CS<pax>/<seat> , then press Enter. For example, to check in the
passenger on line 1 and assign seat 8A, enter CS1/8A.
• To bypass the seat assignment requirement, type CS<pax>/* , then press Enter. For
example, to check in the passenger on line 1, enter CS1/*.
The passenger is checked in and assigned a sequence number for boarding the aircraft.

3 (Conditional) If you are checking in consecutive passengers on the SAME

RESERVATION, do one of the following:

• If the passengers already have seat assignments, type CS<pax>-<pax> , then press
Enter. For example, to check in the passengers on lines 1–3, enter CS1-3.

• To assign seats, type CS<pax>-<pax>/<seat> , then press Enter. For example, to check
in the passengers on lines 1–3 and assign seats sequentially (where possible), beginning
with seat 8A, enter CS1-3/8A.
• To bypass the seat assignment requirement, type CS<pax>-<pax>/* , then press Enter.
For example, to check in the passengers on lines 1–3, enter CS1-3/*.
The passengers are checked in and assigned sequence numbers for boarding the aircraft.

4 (Conditional) If prompted to ask security questions, ask the questions, and then enter
the responses. Press Enter after each response.

Enter Y for “yes” or N for “no.” The system does not enforce whether the responses to these
questions are valid. Rather, it is up to the individual agent to determine whether a passenger
may continue with the check-in process.

5 (Conditional) Enter the final destination for check-in:

Depending on the settings in the CheckinConfig.xml file, you may be prompted for the
destination. The passenger is checked through to the destination you enter and remains
unchecked for any additional downline segments in the journey.

4–8 Airport Check-in User Guide

 CHAPTER 4 CHECKING IN PASSENGERS
Checking In Passengers

6 (Conditional) Pull paper tickets if prompted to by the system:

If there are paper tickets associated with the reservation, the system prompts you to collect
them at this time.
Note Paper tickets may not be required depending on your Booking Configuration settings. Refer
to the Management Console help file for more information about the Do Not Require
Ticket/Coupon Lifts for Paper Tickets configuration.

7 (Conditional) Check in any baggage as needed.

See Chapter 6, Checking In Baggage. If you are checking in multiple passengers, you are
prompted to check in baggage for each passenger individually.
If the Display Downline Segments in Checkin setting in the SkyPort Settings dialog is
checked, any existing onward connection information displays.
The passenger information line displays, which indicates the sequence number, check-in
status (+), and number of checked bags similar to the following:

In this example, Jonathon Smith has checked in (+) and been assigned sequence number 3. He
did not check any bags.
At this point, the boarding pass and any bag tags to be printed are sent to the printer.
For thru flights (the flight number does not change), the passenger is automatically checked
in to all remaining legs of the flight. For connecting flights (the flight number changes), the
passenger may or may not be checked in to the connecting flights, depending on your airline
settings. See Customizing Airport Check-in on page 1-2.

Checking In All Standby Passengers

You can check in all standby passengers on a flight using the CSALL command. However, you
must first execute the .S command to display all standby passengers on the flight.
When you use the CSALL command, the system does not prompt you to assign seats or check in
baggage. Rather, you must do so manually.
For standby passengers, passenger check-in applies only to the specific flight leg; standby
passengers must check in at each downline city for which they are listed as standby, except for
thru flights (unless your airline handles thru flights as separate flight segments).
The CheckinConfig.xml file contains a setting that enables you to specify whether the system
should convert HL bookings to HK upon flight close, or whether standby bookings should
remain HL after the flight is closed. Refer to CheckinConfig.xml on page 1-3 for details.
If a flight is international and APIS or APPS is required, the system uses additional validation
criteria when checking in passengers. See Checking In Passengers on Flights Requiring
Government Validation on page 4-11.

To check in all standby passengers on a flight:

1 At the command prompt, type .S , then press Enter.

Airport Check-in User Guide 4–9

 CHAPTER 4 CHECKING IN PASSENGERS
Checking In Passengers

All standby passengers on the flight are returned.

2 At the command prompt, type CSALL , then press Enter.

A confirmation prompt displays.

3 Type Y , then press Enter.

All standby passengers are checked in to the flight. If your airline has assigned seating, each
passenger is assigned a sequence number for boarding the aircraft. To view the sequence
numbers, display the passengers using the .S command.
You can assign seats using the SA command (see Chapter 5, Assigning Seats). You can check in
baggage using the B, AB, and MB commands (see Chapter 6, Checking In Baggage).

Checking In Passengers with Same-day Return

If your airline is configured to do so, you can issue boarding passes for both outbound and return
travel when the outbound and return flights occur on the same date. Otherwise, the passenger
must check in and receive a boarding pass on the outbound flight, and then check in and receive
a new boarding pass for the return flight. Issuing boarding passes for both outbound and return
flights during the initial check in expedites the check-in process.
Carriers can use the EnableSameDayOptions setting in the CheckinConfig.xml file to control
same-day return functionality.
Important: Do not enable same-day processing if you use government security as the two processes
are mutually exclusive.

To check in passengers with same-day return:

1 Check in the passengers as usual.

See Checking In Confirmed Passengers Individually or by PNR on page 4-5.

After you check in the baggage, if the return flight occurs on the same day as the outbound
flight, a prompt similar to the following displays:

2 Type Y , then press Enter.

The following prompt displays, requesting you to enter a seat preference:

4–10 Airport Check-in User Guide

 CHAPTER 4 CHECKING IN PASSENGERS
Checking In Passengers

Although you can enter an exact seat assignment, the system does not load the seat map for
the return flight, so you cannot verify whether the seat is available. For this reason, it is
preferable to specify a seating preference of Window, Aisle, or No preference. The system
assigns an available seat and prints the seat number on the boarding pass.

3 Enter the seating preference , then press Enter.

A confirmation message displays, indicating that the passenger has been checked in to the
return flight. In addition, a boarding pass prints for the return flight.

Any baggage that needs to be checked in on the return flight must be checked in at the
check-in station for the return flight.
To verify check-in status of the passenger on the return flight, load the return flight (see
Chapter 2, Loading Flights).

Checking In Passengers on Flights Requiring Government

Validation
Some flights require additional passenger validation before passengers can check in. The
check-in system behaves differently for these flights than it does for non-validated flights.
The following sections describe how Airport Check-In responds to government validation
requirements during check-in. For more information about the specific types of government
validation, refer to the New Skies Functional Knowledge Base.
Note New Skies government security processing is not currently supported for thru flights that start
and end in one country with a stop in a different country. For example, security validation is not
supported for thru flights beginning and ending in the US with a stop in Canada. In addition,
carriers who use government security processing should not enable same-day return functionality,
which is controlled via the EnableSameDayOptions setting in the CheckinConfig.xml file.
• Checking In Passengers with APIS Validation on page 4-12
• Verifying all Passengers on page 4-14

• Sending an Unverified Preliminary APIS Report to Customs on page 4-15

• Sending a Preliminary APIS Report to Customs on page 4-16
• Sending the APIS Report to Customs on page 4-17
• Sending PNRGOV Messages on page 4-19
• Checking In Passengers with APPS Validation on page 4-20
• Checking In Passengers with Secure Flight Validation on page 4-24
• Checking In Passengers with iAPP Validation on page 4-28
• Resubmitting Security Data on page 4-26

Airport Check-in User Guide 4–11

 CHAPTER 4 CHECKING IN PASSENGERS
Checking In Passengers

Checking In Passengers with APIS Validation

If you are checking in passengers on a flight that requires APIS validation, the following
happens: After entering the C or CS command to check in a passenger, the system prompts you
to enter the passenger’s passport or other miscellaneous international travel document
information.
If the flight is configured to require AQQ, an interactive type of APIS processing, the passenger’s
information is sent to the government for validation and you must wait for a response before
continuing. If the passenger is cleared, you may proceed with check-in. If the passenger does not
clear validation, an error is displayed and you cannot check the passenger in.
If the flight does not require AQQ, but instead requires non-interactive APIS processing, no
validation is necessary and you may proceed with check-in.
Note E-Borders validation follows the process outlined here. The e-Borders message is triggered when
you close the flight. For more information about e-Borders, refer to the New Skies Functional
Knowledge Base.
Once you have entered the international travel documents for all passengers on the flight, you
must send the APIS report to the customs office for the departure and/or arrival country. Refer to
Sending the APIS Report to Customs on page 4-17 for details.

To check in passengers on a flight with APIS validation:

1 Enter the C or CS command.

The system checks to see if an international document exists for the passenger.
If yes, the following prompt displays.

If no, the following prompt displays:

2 Do one of the following:

• (Conditional) Select the appropriate document from the list provided in the
prompt.

In the example above, you would enter 1 to select the passport on file for Bob Smith.
• Scan the travel document. (This option only applies if you are set up to scan
documents.)

4–12 Airport Check-in User Guide

 CHAPTER 4 CHECKING IN PASSENGERS
Checking In Passengers

A screen similar to the following displays:

• Press Enter to manually enter data.

A screen similar to the following displays:

Respond to each prompt and then press Enter. If a prompt already displays the correct
information, press Enter to accept it and display the next prompt. The Name field is
pre-populated with the name of the passenger as entered on the reservation.
For more information about manually entering travel documents, refer to Entering Travel
Documents on page 9-9.

3 Enter Y to save the document information, and press enter.

Airport Check-in User Guide 4–13

 CHAPTER 4 CHECKING IN PASSENGERS
Checking In Passengers

If the passenger is entering a country that is configured to require a destination address, you
are prompted to enter it now. This prompt displays similar to the following:

4 Follow the prompts, and press enter.

If the flight requires AQQ processing, the data is immediately transmitted to the appropriate
governments. If the validation is successful, you may continue the check-in process. If
validation fails, the system does not allow you to check in the passenger. If this is the case,
verify that the document information has been entered correctly on the reservation.

Verifying all Passengers

You can verify all passengers who have not yet been verified using the DOCVERIFY/F or
FLTVERIFY/F command. Use DOCVERIFY/F to verify passengers prior to boarding. This is
useful when a traveler provides a document during Web check-in and the agent wants to update
the document status to show that it has been verified prior to boarding. Use FLTVERIFY/F to
verify any boarded passenger who has not already been verified and verify the flight in one step.
Note If you run FLTVERIFY/F before removing no-show passengers, the system verifies the
documents on file for those passengers. To prevent this, remove no-show passengers before
running FLTVERIFY/F.
In order to use these commands, your airline must have configured the AllowForceFLTVERIFY
setting in CheckinConfig.xml to be “true”. Also, you cannot use the FLTVERIFY command for
marketing code share flights. For more information, refer to CheckinConfig.xml on page 1-3.

To verify the first valid document for any passenger who has not yet
boarded the aircraft:

1 Type DOCVERIFY/F, and then press Enter.

Note This command updates the status of the documents. The agent is responsible for actually
verifying the documents.
If a passenger has missing or invalid document data, you may be prompted to enter
.APIS/BAD to find and handle the passenger individually (possibly by un-checking and
re-checking that passenger.) In that case, refer to Displaying Passengers with Missing Security
Information on page 3-30 for more information.

To verify the first valid document for any boarded passenger who has not

4–14 Airport Check-in User Guide

 CHAPTER 4 CHECKING IN PASSENGERS
Checking In Passengers

already been verified and verify the flight:

1 Type FLTVERIFY/F, and then press Enter.

The system prompts you to confirm that you want to verify the identified flight, similar to the
following:

2 Type Y, then press Enter.

The system verifies all remaining passengers and confirms the flight has been verified,
similar to the following:

Once verified, the flight status is changed to “VER” as shown in the example above.

Sending an Unverified Preliminary APIS Report to Customs

An unverified preliminary APIS report is a non-standard message containing information about
all passengers in a flight and is sent to customs 24 hours before the scheduled departure. This
type of message does not require passengers to be checked in and have verified travel
documents.
Currently, Russia is the only country that requires an unverified APIS report.
Note The UNAPISPRE command should be used only where the country requires one or more
non-interactive check-in messages. Use of this command when it is not required may result in
duplicate messages being sent.

To send the unverified preliminary APIS report to customs:

1 Type UNAPISPRE, then press Enter.

You are prompted for your phone and fax numbers.

2 Follow the on-screen prompts.

The system returns a summary of the report to be sent to customs, similar to the following:

Airport Check-in User Guide 4–15

 CHAPTER 4 CHECKING IN PASSENGERS
Checking In Passengers

You are prompted to send the report to customs.

3 Type Y, then press Enter.

The system confirms the unverified preliminary APIS report is sent to customs.

Sending a Preliminary APIS Report to Customs

The APISPRE command enables you to generate and send a preliminary APIS report prior to
verification of the flight. This report contains only the passengers who have already checked in
and have a verified travel document. You cannot send an APIS report for a marketing code share
flight.
Note This command should be used only where the country requires one or more non-interactive
check-in messages. Use of this command when it is not required may result in duplicate
messages being sent.

To send the preliminary APIS report to customs:

1 Type APISPRE , then press Enter.

You are prompted for your phone and fax numbers.

2 Follow the on-screen prompts.

The system returns a summary of the report to be sent to customs, similar to the following:

4–16 Airport Check-in User Guide

 CHAPTER 4 CHECKING IN PASSENGERS
Checking In Passengers

You are prompted to send the report to customs.

3 Type Y, then press Enter.

The system confirms the preliminary APIS report is sent to customs.

Sending the APIS Report to Customs

Once you have entered the international travel documents for each passenger on the flight,
follow the steps below to verify the flight and send the APIS report to the customs office for the
departure and/or arrival country. You cannot send an APIS report for a marketing code share
flight.
If you are using AQQ, the following procedure should be used to send the flight closeout
message. This message is required and must be generated within a certain time period following
departure as mandated by the government.

To send the APIS report to customs, do one of the following:

1 Type APISFINAL , then press Enter.

You are prompted for your phone and fax numbers.

2 Follow the on-screen prompts.

Airport Check-in User Guide 4–17

 CHAPTER 4 CHECKING IN PASSENGERS
Checking In Passengers

The system verifies all remaining passengers and verifies the flight. A summary of the report
to be sent to customs is displayed, similar to the following:

You are prompted to send the report to customs.

3 Type Y, then press Enter.

The system confirms the flight has been verified and the APIS report is sent to customs:

OR

1 Type fltverify, then press Enter.

The system prompts you to confirm that you want to verify the identified flight, similar to the
following:

2 Type Y, then press Enter.

The system confirms the flight has been verified, similar to the following:

Once verified, the flight status is changed to “VER” as shown in the example above.

3 Type APIS or APIS/<2-character country code>, then press Enter.

4–18 Airport Check-in User Guide

 CHAPTER 4 CHECKING IN PASSENGERS
Checking In Passengers

Including the country code ensures that the APIS report is sent only to the specified country.
The system returns a summary of the report to be sent to customs, similar to the following:

You are prompted to send the report to customs.

4 Type Y, then press Enter.

The system confirms the flight has been verified and the APIS report is sent to customs:

Sending PNRGOV Messages

When you close a flight in Airport Check-in and PNRGOV processing is required and has not
been sent, the system prompts you to send a PNRGOV message. You can use the PNRGOV
command to send the message. The command supports the following options:

• Send PNR information to a specific government (if the government requires it). For example,
a flight originates in Canada and ends in Australia and both countries require PNRGOV
messaging. You can send a complete PNRGOV message only to Canada by typing
PNRGOV/CA.

• Send information only for a particular PNR. For example, to send information only about
PNR YIG83R, enter PNRGOV/YIG83R.
• Force PNRGOV send. This option is currently ignored. When you submit a PNRGOV
command that includes the force option (/F), the system ignores the force and processes the
rest of the request.
The country and PNR options can be combined to send information about a particular PNR only
to a particular government. The supported combinations are described in the section titled
PNRGOV Command on page A-42.

Use the following procedure to send the message from Airport Check-in. For more information
about PNRGOV processing, refer to the New Skies Functional Knowledge Base.

To send the PNRGOV message from Airport Check-in:

1 Load the flight.

Airport Check-in User Guide 4–19

 CHAPTER 4 CHECKING IN PASSENGERS
Checking In Passengers

2 Type PNRGOV, then press Enter.

The system determines which governments, if any, require PNRGOV for the current flight. If
a PNRGOV message is needed, New Skies formats and sends the message. Refer to PNRGOV
Command on page A-42 for more information about specific command combinations.

Checking In Passengers with APPS Validation

If you are checking in passengers on a flight where APPS validation is required, the following
happens: After entering the C or CS command to check in a passenger, the system prompts you
to either scan the travel document if scanning is available or enter the appropriate information at
the prompts. After the required information is entered, the information is sent to the APP system
for validation and one of the following passenger status codes is returned.

Message Boarding Short Description Action Required by Airline

Code Directive

8501 B OK TO BOARD Allow passenger to board.

8502 D Australia - DO NOT Do not allow passenger to board. If the data

BOARD does not match what is stored in the
government database, the passenger may
New Zealand, United
NOT check into the flight. Ensure that the
Arab Emirates and
information on the passport matches exactly
Thailand - OVERRIDE
what is on the reservation.
REQUIRED
Note In New Zealand, Thailand and the
United Arab Emirates, this status may be
overridden with the appropriate permission.
Refer to Role Settings in Management
Console on page 1-12 for details.
8503 B BOARD IF DOCS OK Allow passenger to board.

8505 C CANCELLED No action required. This is confirmation of a

successful cancellation.

8506 N NO RECORD No action required. This is advice that a

cancellation was NOT successful.

8507 U DUPLICATE NAME Do not allow passenger to board. Retry APP

for this passenger using additional data. For
example, given name or date of birth.

8508 B REPEATED-OK TO Allow passenger to board.

BOARD

8509 X BORDER CLOSED Do not allow passenger to board.

8510 D CONTACT EOC Do not allow passenger to board. Contact

Entry Operations Centre (EOC), DIMIA.

Note If EOC grants permission for the

passenger to board, this status may be
overridden (override code ‘G’) with the
appropriate permission. Refer to Role Settings
in Management Console on page 1-12 for
details.

4–20 Airport Check-in User Guide

 CHAPTER 4 CHECKING IN PASSENGERS
Checking In Passengers

Message Boarding Short Description Action Required by Airline

Code Directive

8516 I INSUFFICIENT DATA Do not allow passenger to board. Retry APP

for this passenger using full personal and
passport data.

8517 B OVERRIDE Allow passenger to board. Initial negative

ACCEPTED boarding directive has been overridden.

8519 B BRD WITH OWT Allow passenger with an onward ticket to

board. If no onward ticket, do not allow
passenger to board.

8520 D CONTACT NZIS Do not allow passenger to board. Contact

Advance Passenger Screening (APS) Support
Office, New Zealand.

Note If NZIS grants permission for the

passenger to board, this status may be
overridden (override code ‘G’) with the
appropriate permission. Refer to Role Settings
in Management Console on page 1-12 for
details.

8530 D CONTACT GDNPR Do not allow passenger to board. Contact

General Directorate of Nationality, Passports,
and Residence (GDNPR) in Bahrain.

Note If GDNPR grants permission for the

passenger to board, this status may be
overridden (override code ‘G’) with the
appropriate permission. Refer to Role Settings
in Management Console on page 1-12 for
details.

8620 D CONTACT SAUDI Do not allow passenger to board. Contact the

GOVERNMENT Kingdom of Saudi Arabia (KSA) government.

Note If UAE grants permission for the

passenger to board, this status may be
overridden (override code ‘G’) with the
appropriate permission. Refer to Role Settings
in Management Console on page 1-12 for
details.

8630 D CONTACT UAE Do not allow passenger to board. Contact

GOVERNMENT United Arab Emirates (UAE) government.

Note If UAE grants permission for the

passenger to board, this status may be
overridden (override code ‘G’) with the
appropriate permission. Refer to Role Settings
in Management Console on page 1-12 for
details.

8670 D CONTACT THAI Do not allow passenger to board. Contact Thai

GOVERNMENT (TH) government.

Note If TH grants permission for the

passenger to board, this status may be
overridden (override code ‘G’) with the
appropriate permission. Refer to Role Settings
in Management Console on page 1-12 for
details.

Airport Check-in User Guide 4–21

 CHAPTER 4 CHECKING IN PASSENGERS
Checking In Passengers

Message Boarding Short Description Action Required by Airline

Code Directive

N/A T N/A The APP system for the country has not
responded within the time-out period
specified. No directive from the country was
provided.

N/A E N/A An error condition has been detected. All error

conditions must be corrected before
processing can be completed for the
passengers represented in the message.

In any case, a history record displays on the reservation showing the boarding directive received.
Note The CheckInForConnectingFlights setting in the CheckinConfig.xml file enables you to check a
passenger in for only part of the journey. If the part of the journey the passenger is checking in
for requires APPS, APPS processing is done for the entire journey including segments beyond
the check-in destination.

To check in passengers on a flight with APPS validation:

1 Enter the C or CS command.

See Checking In Passengers on page 4-4. The following prompt displays:

2 To enter a travel document, do one of the following:

• Scan the travel document.

A screen similar to the following displays:

The data is automatically sent for authorization.

• Press Enter to manually enter data.

4–22 Airport Check-in User Guide

 CHAPTER 4 CHECKING IN PASSENGERS
Checking In Passengers

A screen similar to the following displays:

Respond to each prompt and then press Enter. If a prompt already displays the correct
information, press Enter to accept it and display the next prompt. The Name field is
pre-populated with the name of the passenger as entered on the reservation.
For more information about manually entering travel documents, refer to Entering Travel
Documents on page 9-9.

3 Enter Y to save the document information, and press enter.

When the origin station requires APPS, for example, stations in Australia or New Zealand,
the transit prompt displays along with the station code to which the question applies:

Note These prompts do not apply to infants traveling with adults; the infant’s “in transit” status
is assumed to be the same as the adult’s.

4 Enter Y or N at the prompt, and press enter.

If the passenger did not begin traveling at the first airport in this journey, type Y. Otherwise
type N or press enter.
If the destination station requires APPS, a transit prompt displays along with the station code
to which the question applies:

5 Enter Y or N at the prompt, and press enter.

If the passenger is not ending travel at the journey’s final destination, type Y. Otherwise type
N or press enter.

The data is automatically transmitted to the appropriate governments. If the data is a match,
you may continue the check-in process. If there is insufficient data for the government to
authorize or deny check-in for the passenger, the agent must correct the data and check in the
passenger again. If the data is not a match, the system does not allow you to check in the

Airport Check-in User Guide 4–23

 CHAPTER 4 CHECKING IN PASSENGERS
Checking In Passengers

passenger. If this is the case, verify that the passport information has been entered correctly
on the reservation.

6 (Conditional) If the Check-in system fails to connect to APPS or an error message

displays, you can manually enter the APPS information.

A message similar to the following displays:

If you enter N, the check-in process terminates and the passenger is not checked in for the
flight. If you enter Y, the following prompts display:

Enter the appropriate information at each prompt, and press Enter.

APPS Failure Scenarios

APPS validation can fail for a variety of reasons. Each failure scenario is described below.

• No positive boarding directive received from CPS or entered manually.

The following prompt displays:

If you enter N, the check-in process terminates and the passenger is not checked in for the
flight. If you enter Y, then you can enter the override in the following format:
<outbound country>/<override code>/<inbound country>/<override code>
For example, AU/A/NZ/G means that the passenger is outbound from Australia, and the
override is based on the airline decision (A). The passenger is inbound to New Zealand, and
the override is based on a government agency directive (G).
If the passenger’s journey includes a single APPS country, enter XX/A or XX/G where XX is
the APPS country code.
• Not enough information response received.
The following prompt displays:

If you enter N, the check-in process terminates and the passenger is not checked in for the
flight. If you enter Y, the process continues from step 2 above and you may re-enter the travel
document information.

Checking In Passengers with Secure Flight Validation

When a flight requiring Secure Flight validation is 72 hours from its scheduled departure time,
New Skies uses the data available in the bookings for the flight to generate and send a message to

4–24 Airport Check-in User Guide

 CHAPTER 4 CHECKING IN PASSENGERS
Checking In Passengers

the appropriate agency for validation against government watch lists. The system awaits a
response containing the clearance status of each passenger and stores the information. A
Boarding Pass Printing Result (BPPR) and an Electronic System for Travel Authorization (ESTA)
status are received for each passenger.
The SecureFlight Mode setting (Management Console > External Message System Setting)
enables airlines to specify how Secure Flight behaves after the 72-hour pre-screening. The
following sections describe how to check passengers in when the system is in Normal and
Outage mode.
For more information about Secure Flight, refer to the New Skies Functional Knowledge Base.

To check in passengers on a flight with Secure Flight validation (Normal

Mode):

1 Enter the C or CS command, as usual.

The system looks for a BPPR for the passenger. If none is found, or if a status of Inhibited or
Error is present, the system prompts you to verify the passenger’s ID.

2 (Conditional) After checking the ID, type Y and press Enter.

The system sends a new request to the government and waits for clearance for the passenger.
If clearance is granted, you may continue the check-in process. If validation fails, the system
does not allow you to check in the passenger. In this case, you can contact the government
directly to resolve the issue. The government then sends an updated BPPR and the passenger
can check in.
Depending on the clearance code returned by the government, the passenger may be cleared
for travel but required to provide a secondary, U.S.-issued travel document. The system
prompts you to verify the additional ID at boarding but does not require that you enter the
data.

To check in passengers on a flight with Secure Flight validation (Outage

Mode with Allow Manual Clearance role):

1 Enter the C or CS command, as usual.

The system looks for a BPPR for the passenger. If the passenger’s status is clear, you may
continue the check-in process. If the BPPR or ESTA is not found or is inhibited or error, the
system prompts you to manually clear the passenger.

2 (Conditional) Enter Y to clear the passenger manually.

The system prompts you to specify whether the passenger is cleared (C) or a selectee (S).

3 (Conditional) Enter C or S, then press Enter.

The system searches for an ESTA status. If none is found, the system prompts you to enter a
status from a list.

4 (Conditional) Enter the ESTA status, then press Enter.

The system prompts you to enter an optional comment.

Airport Check-in User Guide 4–25

 CHAPTER 4 CHECKING IN PASSENGERS
Checking In Passengers

5 (Conditional) Enter a comment, then press Enter.

The check-in process continues with bag tag entry as usual. Refer to Chapter 6, Checking In
Baggage for details.

Resubmitting Security Data

Use the SENDGOV command to resubmit passenger information for government validation.

To resubmit security data to all countries for a specific passenger:

1 Load the flight and list the passengers.

2 Type SENDGOV<pax>, then press Enter.

The system determines the government security requirements for the passenger and all
affected countries and resubmits the data accordingly.

To resubmit security data for a specific passenger to a specific country:

1 Load the flight and list the passengers.

2 Type SENDGOV<pax>/<2-char country code>, then press Enter.

4–26 Airport Check-in User Guide

 CHAPTER 4 CHECKING IN PASSENGERS
Checking In Passengers

The system determines the government security requirements for the passenger in the
specified country and resubmits the data accordingly.

To resubmit security data for all passengers on a flight:

1 Load the flight.

2 Type SENDGOVALL, then press Enter.

The system resubmits the data accordingly.

In case of an outage, the output displays an error notification.

Airport Check-in User Guide 4–27

 CHAPTER 4 CHECKING IN PASSENGERS
Checking In Passengers

To resubmit security data to a specific country for all passengers on a flight:

1 Load the flight.

2 Type SENDGOVALL/<2-char country code>, then press Enter.

The system resubmits the data accordingly for the specified country.

In case of an outage, the output displays an error notification.

Checking In Passengers with iAPP Validation

If you are checking in passengers on a flight that requires iAPP validation, the system prompts
you to enter the passenger’s passport or other miscellaneous international travel document
information after you enter the C or CS command. This information is then sent to the
government of the country that requires it for validation. You must wait for a response before
continuing. If the passenger is cleared, you can proceed with check-in. If the passenger does not
clear validation, the reason displays and you cannot check the passenger in. Ensure that all
passenger information is complete and try again to check the passenger in.

To check in passengers on a flight with iAPP validation:

1 Enter the C or CS command.

The system displays any security questions as well as the security programs that apply to the
current flight similar to the following.

4–28 Airport Check-in User Guide

 CHAPTER 4 CHECKING IN PASSENGERS
Checking In Passengers

2 Do one of the following:

Note The travel document must be valid for all security programs that apply. In this example, the
document must be acceptable for both APIS and iAPP.
• Scan the travel document. (This option only applies if you are set up to scan
documents.)
A screen similar to the following displays:

• Press Enter to manually enter data.

A screen similar to the following displays:

Respond to each prompt and then press Enter. If a prompt already displays the correct
information, press Enter to accept it and display the next prompt. The Name field is
pre-populated with the name of the passenger as entered on the reservation.
For more information about manually entering travel documents, refer to Entering Travel
Documents on page 9-9.

3 Enter Y to save the document information, and press enter.

Airport Check-in User Guide 4–29

 CHAPTER 4 CHECKING IN PASSENGERS
Checking In Passengers

If the passenger is entering a country that is configured to require a destination address, you
are prompted to enter it now. This prompt displays similar to the following:

4 Follow the prompts, and press enter.

The data is immediately transmitted to the appropriate government. If the iAPP validation is
successful, you may continue the check-in process. If iAPP validation fails, the system does
not allow you to check in the passenger. If this is the case, verify that the document
information has been entered correctly on the reservation.

Checking and Unchecking Passengers on a Marketing Code

Share, Outbound Interline, or Third-Party-Controlled Flight
The MC and MCS commands and their many variations are used to check passengers in on code
share, outbound interline, or third-party-controlled flights that are marketed but not operated by
your airline. These commands are typically performed by select airport agents in order to close
other airline flights when a PFS flight close message was not received from the operating carrier.
The MC and MCS commands are very similar to the C and CS commands, but there are several
important differences.

• The MC and MSC commands apply to marketing code share, outbound interline, or
third-party-controlled flights only (sold by the host), which you cannot load in Check-in
unless your role enables you to do so. Refer to Role Settings in Management Console on page
1-12 or the Management Console help file for details.
• Seat assignments are not required to check in on a marketing flight.
• Passengers are checked in and boarded in a single step.
• Passengers are checked in and boarded for the current flight only. They are not automatically
checked in for connecting flights.
• You cannot add baggage when checking in passengers to a marketing code share or
outbound interline flight (sold by the host).
• You cannot verify or send APIS reports for international marketing code share flights. The
operating carrier is responsible for transmitting APIS information to the government in that
case.
The RMC and RMCS commands and their many variations are used to uncheck passengers on
code share, outbound interline, or third-party-controlled flights that are marketed but not
operated by your airline. The syntax and usage of these commands mirrors that of the MC and

4–30 Airport Check-in User Guide

 CHAPTER 4 CHECKING IN PASSENGERS
Checking In Passengers

MCS commands, but the result is that the passenger or passengers are unchecked instead of
checked in.
This section covers common scenarios for checking in and unchecking passengers on marketing
code share, outbound interline, and DCS-controlled flights:

• Checking and Unchecking Confirmed Passengers Individually on a Marketing Code Share,

Outbound Interline, or Third-Party-Controlled Flight on page 4-31

• Checking and Unchecking All Confirmed Passengers on a Marketing Code Share, Outbound
Interline, or Third-Party-Controlled Flight on page 4-32

• Checking and Unchecking Standby Passengers Individually on a Marketing Code Share,

Outbound Interline, or Third-Party-Controlled Flight on page 4-32

• Checking and Unchecking All Standby Passengers on a Marketing Code Share, Outbound
Interline, or Third-Party-Controlled Flight on page 4-33

Checking and Unchecking Confirmed Passengers Individually on a

Marketing Code Share, Outbound Interline, or Third-Party-Controlled
Flight
Depending on your role, you can check in either (1) one confirmed passenger at a time or (2) all
confirmed passengers on a reservation using the MC command. For more information about
roles, refer to the Management Console help file.
If a flight is international or is connecting to an international marketing code share flight and
APIS is required, the system collects additional validation data as described in Checking In
Passengers on Flights Requiring Government Validation on page 4-11. The only difference is that
the marketing code share flight cannot be verified so the APIS report cannot be sent.
To uncheck rather than check one or more confirmed passengers, use the RMC command in place
of the MC command in the following procedure.

To check in and board confirmed passengers individually:

1 Display the confirmed passengers to check in.

For more information, see Chapter 3, Displaying Passenger Lists.

If you are checking in all passengers on the same reservation, you can use the .P<pax>
command to display the passengers. For example, to display all passengers on the same
reservation as the passenger on line 1, enter .P1. See Displaying All Passengers on the Same
Reservation on page 3-8.

2 (Conditional) If you are checking in ONE passenger, type MC<pax> , then press Enter.

For example, to check in the passenger on line 1, type MC1 and press Enter. The passenger is
checked in and assigned a sequence number for boarding the aircraft.

3 (Conditional) If you are checking in consecutive passengers on the SAME

RESERVATION, type MC<pax>-<pax>.

For example, to check in the passengers on lines 1 through 4, type MC1-4 and press Enter.
The passengers are checked in and assigned sequence numbers for boarding the aircraft.

Airport Check-in User Guide 4–31

 CHAPTER 4 CHECKING IN PASSENGERS
Checking In Passengers

4 (Conditional) If prompted to ask security questions, ask the questions, and then enter
the responses. Press Enter after each response.

Enter Y for “yes” or N for “no.” The system does not enforce whether the responses to these
questions are valid. Rather, it is up to the individual agent to determine whether a passenger
may continue with the check-in process.
The boarding pass is sent to the printer.

Checking and Unchecking All Confirmed Passengers on a Marketing

Code Share, Outbound Interline, or Third-Party-Controlled Flight
Depending on your role, you can check in all confirmed passengers on a marketing code share
flight using the MCALL command.
To uncheck rather than check all confirmed passengers, use the RMCALL command in place of
the MCALL command in the following procedure.

To check in and board all confirmed passengers on a marketing code

share/outbound interline flight:

1 At the command prompt, type MCALL , then press Enter.

A confirmation prompt displays.

2 Type Y , then press Enter.

All confirmed passengers are checked in to the flight. Each passenger is assigned a sequence
number for boarding the aircraft. To view the sequence numbers, display the passengers
using the F command.

Checking and Unchecking Standby Passengers Individually on a

Marketing Code Share, Outbound Interline, or Third-Party-Controlled
Flight
Depending on your role, you can check in either (1) one standby passenger at a time or (2) all
standby passengers on a reservation using the MCS command.
For standby passengers, passenger check-in applies only to the specific flight leg; standby
passengers must check in at each downline city for which they are listed as standby, except for
thru flights (unless your airline handles thru flights as separate flight segments).
The CheckinConfig.xml file contains a setting that enables you to specify whether the system
should convert HL bookings to HK upon flight close, or whether standby bookings should
remain HL after the flight is closed. Refer to CheckinConfig.xml on page 1-3 for details.
If a flight is international or is connecting to an international marketing code share flight and
APIS is required, the system collects additional validation data as described in Checking In
Passengers on Flights Requiring Government Validation on page 4-11. The only difference is that
the marketing flight cannot be verified so the APIS report cannot be sent.
To uncheck rather than check one or more standby passengers, use the RMCS command in place
of the MCS command in the following procedure.

4–32 Airport Check-in User Guide

 CHAPTER 4 CHECKING IN PASSENGERS
Checking In Passengers

To check in and board standby passengers individually:

1 Type .S to display the standby passengers to check in.

See Displaying Standby Passengers on page 3-10.

Notice that each passenger is assigned a standby priority code (in the example above, “A”).
Standby priority codes indicate the priority in which standby passengers should be checked
in to the flight, should a seat become available. To view the standby priority codes for your
airline, enter the STBY command.
If you are checking in all passengers on the same reservation, you can use the .P<pax>
command to display the passengers. For example, to display all passengers on the same
reservation as the passenger on line 1, enter .P1. See Displaying All Passengers on the Same
Reservation on page 3-8.

2 (Conditional) If you are checking in ONE passenger, type MCS<pax>.

For example, to check in the passenger on line 1, type MCS1 and press Enter. The passenger is
checked in and assigned a sequence number for boarding the aircraft.

3 (Conditional) If you are checking in consecutive passengers on the SAME

RESERVATION, type MCS<pax>-<pax>.

For example, to check in the passengers on lines 1 through 4, type MCS1-4 and press Enter.
The passengers are checked in and assigned sequence numbers for boarding the aircraft.

4 (Conditional) If prompted to ask security questions, ask the questions, and then enter
the responses. Press Enter after each response.

Enter Y for “yes” and N for “no.” The system does not enforce whether the responses to these
questions are valid. Rather, it is up to the agent to determine whether a passenger may
continue with the check-in process.
The boarding pass is sent to the printer.

Checking and Unchecking All Standby Passengers on a Marketing

Code Share, Outbound Interline, or Third-Party-Controlled Flight
Depending on your role, you can check in all standby passengers on a flight using the MCSALL
command. Before using the MCSALL command, you must first use the .S command to display all
standby passengers on the flight.
For standby passengers, passenger check-in applies only to the specific flight leg; standby
passengers must check in at each downline city for which they are listed as standby, except for
thru flights (unless your airline handles thru flights as separate flight segments).
The CheckinConfig.xml file contains a setting that enables you to specify whether the system
should convert HL bookings to HK upon flight close, or whether standby bookings should
remain HL after the flight is closed. Refer to CheckinConfig.xml on page 1-3 for details.

Airport Check-in User Guide 4–33

 CHAPTER 4 CHECKING IN PASSENGERS
Checking In Passengers

To check in and board all standby passengers on a flight:

1 At the command prompt, type .S , then press Enter.

All standby passengers on the flight are returned.

2 At the command prompt, type MCSALL, then press Enter.

A confirmation prompt displays.

3 Type Y , then press Enter.

All standby passengers are checked in to the flight. Each passenger is assigned a sequence
number for boarding the aircraft. To view the sequence numbers, display the passengers
using the .S command.

4–34 Airport Check-in User Guide

 CHAPTER 4 CHECKING IN PASSENGERS
Removing Passengers from Check-in

Removing Passengers from Check-in

It may be necessary to remove passengers from check-in. For example, a passenger has checked
in to a flight but has not boarded the aircraft, and you need to close the flight. You must remove
the passenger from check-in so that you can close the flight. This section describes how to
remove passengers from check-in.
When you remove a passenger from check-in, any existing APPS boarding directive is deleted
automatically. Using the CheckinConfig.xml file, the system can be configured to prompt for
removal of seat assignments and bags. If there is checked baggage, ensure that any associated
baggage information is deleted from the system as well (see Removing Baggage from Check-in on
page 6-15) and that the actual bags are removed from the aircraft.
This section contains the following topics:

• Removing Confirmed Passengers from Check-in Individually on page 4-35

• Removing All Confirmed Passengers from Check-in on page 4-36
• Removing Standby Passengers from Check-in Individually on page 4-37
• Removing All Standby Passengers from Check-in on page 4-37

Removing Confirmed Passengers from Check-in

Individually
You can remove confirmed passengers from check-in individually using the R command. For
more information on the R command, see R Command on page A-43.
For more information on removing passengers from check-in, see Removing Passengers from
Check-in on page 4-35.

To remove confirmed passengers individually:

1 Display the confirmed passengers to remove from check-in.

For more information, see Chapter 3, Displaying Passenger Lists.

2 At the command prompt, do one of the following:

• To remove one passenger, type R<pax> , then press Enter. For example, to remove the
passenger on line 1, enter R1.
• To remove multiple passengers on the same reservation, type R<pax>-<pax> , then
press Enter. For example, to remove the passengers on lines 1–3, enter R1-3.

3 (Conditional) A prompt displays asking if you would like to remove seat assignments.

• To remove seat assignments, type Y , then press Enter.

• To preserve seat assignments, type N , then press Enter.

4 (Conditional) A prompt displays asking if you would like to remove bags.

Airport Check-in User Guide 4–35

 CHAPTER 4 CHECKING IN PASSENGERS
Removing Passengers from Check-in

• To remove bags, type Y , then press Enter.

• To preserve bags, type N , then press Enter.
Note: If the system does not prompt you to remove the passenger’s baggage from check-in, check
the baggage status to ensure that the baggage is removed from the system. If a passenger is
removed from check-in, the baggage should be removed as well.
A message displays indicating that the passenger has been removed from check-in, similar to
the following:

If the passenger is associated with an IATCI reservation and the passenger is checked in, a
message is sent to the other carrier asking that the passenger be removed from the downline
flights.
Note To remove a passenger from a downline OA IATCI flight, you must first remove the
passenger from the host flight.
In release 3.5, functionality was added to interactively update the coupon status when a
passenger is un-checked. If the update fails, a warning displays telling you that the coupon or
coupons were not updated. In that case, the passenger is un-checked despite the warning.

Removing All Confirmed Passengers from Check-in

You can remove all confirmed passengers from check-in using the RALL command. For more
information on removing passengers from check-in, see Removing Passengers from Check-in on
page 4-35.

To remove all confirmed passengers on a flight:

1 Display the passengers to remove.

For more information, see Displaying All Passengers on a Flight on page 3-3.

2 At the command prompt, type RALL , then press Enter.

3 (Conditional) A prompt displays asking if you would like to remove seat assignments.

• To remove seat assignments, type Y , then press Enter.

• To preserve seat assignments, type N , then press Enter.

4 (Conditional) A prompt displays asking if you would like to remove bags.

• To remove bags, type Y , then press Enter.

• To keep bags checked in, type N , then press Enter.

4–36 Airport Check-in User Guide

 CHAPTER 4 CHECKING IN PASSENGERS
Removing Passengers from Check-in

Note: If the system does not prompt you to remove the passenger’s baggage from check-in, check
the baggage status to ensure that the baggage is removed from the system. If a passenger is
removed from check-in, the baggage should be removed as well.
All confirmed passengers are removed from the flight. A confirmation prompt displays.

Removing Standby Passengers from Check-in Individually

You can remove standby passengers from check-in individually using the RS command. For
more information on the RS command, see RS Command on page A-45.
For a standby passenger who paid for a reservation with a credit card, payment information is
not sent to the bank until the flight is closed (it is not sent when the passenger is checked in).
For more information on removing passengers from check-in, see Removing Passengers from
Check-in on page 4-35.

To remove standby passengers individually:

1 Display the standby passengers to remove from check in (.S command).

See Displaying Standby Passengers on page 3-10. A list of standby passengers displays.

2 At the command prompt, do one the following:

• To remove one passenger, type RS<pax> , then press Enter. For example, to remove the
passenger on line 1, enter RS1.
• To remove multiple passengers on a reservation, type RS<pax>-<pax> , then press
Enter. For example, to remove the passengers on lines 1–3, enter RS1-3.

3 (Conditional) A prompt displays asking if you would like to remove seat assignments.

• To remove seat assignments, type Y , then press Enter.

• To preserve seat assignments, type N , then press Enter.

4 (Conditional) A prompt displays asking if you would like to remove bags.

• To remove bags, type Y , then press Enter.

• To keep bags checked in, type N , then press Enter.
Note: If the system does not prompt you to remove the passenger’s baggage from check-in,
manually check the baggage status to ensure that the baggage remains with the passenger. If
a passenger is removed from check-in, the baggage should be removed as well.
A confirmation message displays.

Removing All Standby Passengers from Check-in

You can remove all confirmed passengers from check-in using the RSALL command.
For a standby passenger who paid for a reservation with a credit card, payment information is
not sent to the bank until the flight is closed (it is not sent when the passenger is checked in).

Airport Check-in User Guide 4–37

 CHAPTER 4 CHECKING IN PASSENGERS
Removing Passengers from Check-in

For more information on removing passengers from check-in, see Removing Passengers from
Check-in on page 4-35

To remove all standby passengers from check-in:

1 Display the standby passengers to remove from check in (.S command).

See Displaying Standby Passengers on page 3-10. A list of standby passengers displays.

2 At the command prompt, type RSALL , then press Enter.

A message displays, confirming whether you want to remove all standby passengers from
check-in.

3 Type Y , then press Enter.

All standby passengers are removed from check-in.

Note: For all passengers who are removed from check-in, check the baggage status to ensure that
the baggage remains with them. If any passenger is removed from check-in, the baggage
should be removed as well.

4–38 Airport Check-in User Guide

 CHAPTER 4 CHECKING IN PASSENGERS
Re-printing Itineraries

Re-printing Itineraries
There may be times when you need to re-print an itinerary for a passenger. For example, a
passenger who has misplaced an itinerary may request that you print another.
You can re-print itineraries using the IT command. This command sends itineraries to the printer
that you indicate. If your airline is configured to use the II command, you send itineraries to the
boarding pass printer. For example, to send an itinerary to the boarding pass printer for the
passenger on line 1, enter II1.

To reprint an itinerary:

1 Display the passenger for whom you need to re-print an itinerary.

See Chapter 3, Displaying Passenger Lists.

2 At the command prompt, type IT<pax>/<printer code> , then press Enter.

For example, to re-print an itinerary for the passenger on line 1 and send it to printer
SLCPRN1, enter IT1/SLCPRN1. A message displays, indicating that the itinerary has been
sent to the printer.
The <printer code> for a printer is configured in Printer Maintenance. It is the same printer
code you use to print reports.

Re-printing Boarding Passes

There may be times when you need to re-print a boarding pass for a passenger. For example, a
passenger who has misplaced a boarding pass needs another printed in order to board the
aircraft.
Note Use the Booking History for Boarding Pass Printing configuration in the SkyPort Settings
dialog of Management Console to create a booking history record when boarding passes are
printed.

To re-print a boarding pass:

1 Display the passenger for whom you need to re-print a boarding pass.

See Chapter 3, Displaying Passenger Lists.

2 At the command prompt, type BP<pax> , then press Enter.

For example, to re-print a boarding pass for the passenger on line 1, enter BP1. A message
displays, indicating that a boarding pass is being printed.

Airport Check-in User Guide 4–39

 CHAPTER 4 CHECKING IN PASSENGERS
Printing Gate Passes

Printing Gate Passes

The “Allow Gate Pass Printing” role in Management Console enables you to use the GP
command to print a gate pass for any non-passengers who want to go to a gate. When the airport
code included in the request requires Secure Flight security processing, all non-passengers who
want to go to the gate must also receive proper clearance from the government. In that case, you
must use the GP<pax> option to associate the person requesting the gate pass with a passenger.

To print a gate pass:

1 Type GP, and press Enter.

To create a gate pass tied to a particular passenger, first list the passengers. Then enter
GP<pax> where <pax> is the number of the passenger in the list.

Note If the airport requires Secure Flight security processing you must use GP<pax>.

The system prompts you for the information to be printed on the gate pass as follows:

The information you enter relates to the person using the gate pass, not to a passenger on the
flight.

2 After entering the information for each line, press Enter.

4–40 Airport Check-in User Guide

 CHAPTER 4 CHECKING IN PASSENGERS
Printing Gate Passes

The system prompts you to verify the information similar to the following:

3 (Conditional) If necessary, enter the line number where you want to make changes.

Type the correct information and press Enter.

4 Enter Y to print the gate pass.

The document prints to the boarding pass printer.

Airport Check-in User Guide 4–41

 CHAPTER 4 CHECKING IN PASSENGERS
Printing Gate Passes

4–42 Airport Check-in User Guide

5 Assigning Seats

If your airline has configured seat maps for its aircraft, you can make passenger seat assignments
in Airport Check-in. This section contains several topics related to seat maps and seat
assignments.

In this chapter:

• Understanding the Seat Map on page 5-2

— SSRs on Seat Maps on page 5-2

— Seat Properties on Seat Maps on page 5-2
— Configuring Premium Fares on page 5-4
• Displaying the Seat Map on page 5-5
• Assigning Seats on page 5-6
• Assigning Seats for Connecting Flights on page 5-7
• Assigning Seats on Thru (Direct) Flights on page 5-8

— Merging Seat Maps for Thru Flights on page 5-8

— Assigning Seats for a Specific Leg of a Thru Flight on page 5-10
• Changing Seat Assignments on page 5-12
• Holding or Blocking Seats on page 5-13
• Unblocking Seats on page 5-16

Airport Check-in User Guide 5–1

 CHAPTER 5 ASSIGNING SEATS
Understanding the Seat Map

Understanding the Seat Map

The seat map displays the seating configuration for an aircraft, as well as the current seat
assignments for a flight, similar to the following:

In the seat map above, the aircraft has six columns of seats (A–F) and 29 rows, which makes a
total of 174 seats (there are no missing seats). The rows over the wing are identified by slashes (/
or \) and the exit rows are identified by the letter “E”. The horizontal numbering at the top and
bottom of the seat map, combined with the vertical lettering to the left of the seat map, indicate
the seat number. The seats on this particular aircraft are numbered 1A through 29F.
If the passenger assigned to a certain seat has at least one eligible SSR, the seat map displays the
first SSR. Refer to SSRs on Seat Maps on page 5-2 for details. If the passenger does not have any
SSRs, the status code displays instead. Refer to Seat Properties on Seat Maps on page 5-2.
For more information on configuring seat maps, please refer to the help files for SkySchedule.
You can display the seat map at any time using the SM command. For more information on
displaying the seat map for a flight, see Displaying the Seat Map on page 5-5.

SSRs on Seat Maps

When a passenger with one or more SSRs is assigned a particular seat, the seat map includes the
passenger’s first SSR code. SSRs are sorted just as they are for the passenger display commands.
However, you can specify SSRs to be excluded from the display using the
RestrictedSSRsInCheckIn setting in CheckinConfig.xml. For more information on sorting SSRs
refer to Displaying All Passengers on a Flight on page 3-3.

Seat Properties on Seat Maps

Each seat may be labeled with a code to indicate its properties or status, such as held, blocked,
bulkhead, and so on. Using SkySchedule, you may assign one or more property codes to a seat.

5–2 Airport Check-in User Guide

 CHAPTER 5 ASSIGNING SEATS
Understanding the Seat Map

If a seat has more than one property code, the display hierarchy dictates that the code listed
highest in the following table is displayed except when the agent role is not allowed to assign
seats with one of the lower-level seat property codes.
For example, say a seat is designated as both fleet blocked (r) and restricted (b). The seat map
shows “r” unless the agent is allowed to assign fleet-blocked seats but cannot assign restricted
seats. In that case, the seat map displays “b” to indicate that the agent cannot assign the seat.
The following table lists all of the standard status codes that may display on a seat map.
However, you can use the Add/Edit Seat Property dialog in Management Console to create
custom seat property codes, which are prioritized and displayed along with the standard codes
on the seat map. Refer to the help file for Management Console for more information on creating
custom seat priority codes.

Seat Status Codes for Seats that are Open

r Seat is fleet blocked.

b Seat is restricted.

i Seat is enabled for infants.

^ Seat provides extra leg room.

l Seat is at the bulkhead.

s Seat is designated for smokers.

- Seat is available.

Seat Status Codes for Seats that are Taken

<SSR code> Specifies seat SSR if one exists.

R Seat is reserved. The seat map displays ‘r’ for reserved seats regardless of any
other status codes associated with the seat.

If your airline has configured premium fares, the

PremiumFareSeatMapDisplayNotCheckedIn value is displayed in place of the ‘r’
when applicable. Refer to Configuring Premium Fares on page 5-4 for details.

C Seat is designated for “child” passenger types. The seat map displays ‘c’ for
seats that are either reserved for or occupied by children regardless of any
other status codes associated with the seat

* Seat is occupied (displays after a passenger has checked in). The seat map
displays ‘*’ for occupied seats regardless of any other status codes associated
with the seat.

If your airline has configured premium fares, the

PremiumFareSeatMapDisplayCheckedIn value is displayed in place of the ‘*’
when applicable. Refer to Configuring Premium Fares on page 5-4 for details.

x Seat is blocked. The seat map displays ‘x’ for blocked seats regardless of any
other status codes associated with the seat

k Seat is broken. The seat map displays ‘k’ for broken seats regardless of any
other status codes associated with the seat

Airport Check-in User Guide 5–3

 CHAPTER 5 ASSIGNING SEATS
Understanding the Seat Map

Seat Status Codes for Seats that are Taken

h Seat is on hold. The seat map displays ‘h’ for seats on hold regardless of any
other status codes associated with the seat.

Configuring Premium Fares

The seat map can be configured to indicate seats that are occupied by passengers with premium
fares. Use the PremiumFares setting in CheckinConfig.xml to list the fares that should be
considered premium fares and included on the seat map.
Then use the PremiumFareSeatMapDisplayCheckedIn and
PremiumFareSeatMapDisplayNotCheckedIn settings, also in CheckinConfig.xml to indicate the
characters to be shown on the seat map for checked and non-checked passengers respectively.
For example, PremiumFares is set to Q,Z, PremiumFareSeatMapDisplayCheckedIn to V, and
PremiumFareSeatMapDisplayCheckedIn to v. The system looks for any seats occupied by
passengers with Q or Z fares. Seats for Q- and Z-fare passengers who have already checked in
are indicated by the letter V. For seats where the passengers have not yet checked in, the system
displays the letter v.

5–4 Airport Check-in User Guide

 CHAPTER 5 ASSIGNING SEATS
Displaying the Seat Map

Displaying the Seat Map

Your airline can configure seat map for each aircraft configuration it uses. Once these
configurations are in the system, you can retrieve the seat map for the currently loaded flight at
any time using variations of the SM command (see SM Command on page A-47). Each time you
retrieve a seat map, it is updated with the most current seat assignments for the selected flight.
If your airline has not configured a seat map for a particular aircraft, when you attempt to display
the seat map for any flight that uses that aircraft, the system displays a message indicating that
no seat map has been created for that particular aircraft.
For more information on seat maps, see Understanding the Seat Map on page 5-2.

To display the seat map for the currently loaded flight:

1 At the command prompt, type SM , then press Enter.

The seat map displays, similar to the following:

The seat map is updated with the most current seat assignments for the flight. With this
information, you can determine which seats are available.
You can also display the seat map by appending the SM command after the F command. For
example, to find all passengers on a flight and display the seat map, enter F,SM. For more
information on displaying the seat map with the F command, see F Command on page A-36.
Note: If a seat is reserved or designated for a specific purpose, you should follow your airline
policies and procedures before assigning the seat.

Airport Check-in User Guide 5–5

 CHAPTER 5 ASSIGNING SEATS
Assigning Seats

Assigning Seats
You can make seat assignments at check-in using the C and CS commands and using the SA
command. When entering a seating preference, do one of the following:
• Enter an exact seat number (for example, 8A).
• Select “Window”, “Aisle”, or “Other”, in which case the system assigns the next available
window, aisle, or other (no preference) seat. The next available seat is determined by the
seating priorities configured in SkySchedule.
• Select “No preference”, in which case the system assigns the next available seat. The next
available seat is determined by the seating priorities configured in SkySchedule.
For more information on the SA command, see SA Command on page A-46.
To assign seats for passengers on thru flights, see Assigning Seats on Thru (Direct) Flights on page
5-8.
To assign seats for passengers who have connecting flights, see Assigning Seats for Connecting
Flights on page 5-7.

To assign a seat to a passenger:

1 Display the passengers for whom to assign a seat.

See Chapter 3, Displaying Passenger Lists.

2 At the command prompt, type SA<pax>/<seat> , then press Enter.

For example, to assign a window seat to the passenger on line 1, enter SA1/W, to assign an
aisle seat enter SA1/A, and for no preference enter SA1/O.
The system returns a confirmation of the seat assignment, similar to the following:

In the example above, Dan MacLellan is assigned seat 4A.

For IATCI reservations, a request is sent to the other airline asking that the seat be assigned
on the downline flights and a message displays on the screen that says “Sending update to
OA system.” Since Navitaire has no access to the other airline’s seat maps, there is no
guarantee that the seat will be assigned.
Multiple passengers on the same PNR can be checked in simultaneously if they display in
sequential order in the passenger list. Looking at the previous example, entering SA1-3/8a
assigns seats to the passengers on lines 1–3, beginning with seat 8A. The seats are assigned
sequentially, whenever possible. Keep in mind that in this example, passengers 1-3 are on the
same PNR (AZZ1YZ). You cannot check in multiple passengers on different PNRs.
For more information, see SA Command on page A-46.

5–6 Airport Check-in User Guide

 CHAPTER 5 ASSIGNING SEATS
Assigning Seats for Connecting Flights

Assigning Seats for Connecting Flights

When you make a seat assignment for the first segment of a connecting flight, the system does
one of two things:
• If your airline has enabled the “automatic seat assignment” feature for connecting flights,
when you make a seat assignment for the first leg of a connecting flight, the system checks the
remaining flight segments for the same seat assignment. If the seat is available, the system
checks in the passenger on all subsequent legs of the flight, and provides the same seat
assignment. For more information about this feature, see Customizing Airport Check-in on
page 1-2.
If the same seat is not available on subsequent flight segments, the system checks in the
passenger for the currently loaded flight, but does not check in the passenger for the
connecting flights. If this is the case, you must load each connecting flight, check in the
passenger for the flight, and then make the seat assignment.
If you enter C1/1A, the system attempts to find seat 1A on all connecting flight segments. If
you enter C1/W, the system attempts to find a window seat on all connecting flight
segments.
• If the “automatic seat assignment” feature is not enabled, you must load each connecting
flight, check the passenger in to the flights, and then make the seat assignments.

Airport Check-in User Guide 5–7

 CHAPTER 5 ASSIGNING SEATS
Assigning Seats on Thru (Direct) Flights

Assigning Seats on Thru (Direct) Flights

When checking in passengers for thru flights (multi-leg flights where the does not change), the
SA command automatically assigns the same seat for all legs of the flight whenever possible. If
you attempt to assign a seat that is not available for one or more legs of the thru flight, the system
assigns another seat in the same cabin and a message similar to the following displays:

To reserve the same seat on all legs of a thru flight, you must first locate a suitable seat. You can
find a seat by “merging” the seat maps for all legs of the thru flight using the SM command. The
merged seat map shows you which seats are available for all legs of the flight.
For more information on merging seat maps, see Merging Seat Maps for Thru Flights on page 5-8.
There may be times when you want to assign a specific seat on a flight leg other than the one that
is currently loaded. The ST command enables you to specify the destination airport code that
identifies the segment for which you want to assign a seat.

Merging Seat Maps for Thru Flights

For passengers on thru flights, it may be convenient to assign the same seat for all legs of their
flight. That way, they do not have to change seats on different flight legs.
In Airport Check-in, you can find which seats are available on all legs of a thru flight by
“merging” the seat maps for all legs of the thru flight. The merged seat map displays the status
code for each seat, and you can easily determine which seats are available on all legs of the flight.
Note If there is a change of gauge, (that is, a change in aircraft configuration or aircraft type) instead
of a merged seat map, all of the seat maps are displayed.
For example, flight 636 is a thru flight with two legs: ALB-BOS and BOS-JFK. The seat map for
the ALB-BOS leg is the following:

5–8 Airport Check-in User Guide

 CHAPTER 5 ASSIGNING SEATS
Assigning Seats on Thru (Direct) Flights

And the seat map for the BOS-JFK leg is the following:

When you merge the two seat maps, the merged seat map looks like the following:

Seat 01F is available on the first leg (ALB-BOS), but it is not available on the second leg
(BOS-JFK). On the merged seat map, seat 01F is shown as reserved.
Seat 01E is available on both legs of the flight, and thus shows as available on the merged seat
map.

To merge the seat maps of a thru flight:

1 At the command prompt, type SM<final destination airport code> , then press Enter.

Airport Check-in User Guide 5–9

 CHAPTER 5 ASSIGNING SEATS
Assigning Seats on Thru (Direct) Flights

For example, if the final destination of a thru flight is JFK, you would enter SMJFK. The
system merges all seat maps for each leg of the thru flight, and then displays the merged seat
map, similar to the following:

In the example above, seats 1A–1C are reserved on all legs of the thru flight.
Once you locate a seat that is available for the entire flight, you can assign the seat using the
SA command (see Assigning Seats on page 5-6).

Assigning Seats for a Specific Leg of a Thru Flight

The ST command enables you to make or change a passenger’s seat assignment on one leg of a
thru flight without affecting the seat assignment on other legs. When using the ST command,
first load one leg of the thru flight and then use the .T command to display the thru passengers
on the leg.
If necessary, you can change multiple seat assignments at once.

To make or change a seat assignment for a particular leg of a thru flight:

1 Load one leg of the thru flight.

You can choose to load any leg of the flight in this step. The syntax of the ST command that
you use in step 3 below depends on whether you load the first leg or a subsequent one. For
details on loading flights, refer to Chapter 2, Loading Flights.

2 Display the thru passengers for whom to change seat assignments.

Use the F command if the first leg of the flight is currently loaded. Otherwise, use the .T
command to display thru passengers only. See Displaying All Passengers on a Flight on page
3-3 or Displaying Thru Passengers on page 3-17.

3 At the command prompt, type ST<pax>/<seat>/<dest> , then press Enter.

For example, to assign seat 11B on the leg ending at JFK to the passenger on line 2, enter
ST2/11B/JFK. To assign seats on the JFK leg to the passengers on lines 1–3, beginning with
seat 8A, enter ST1-3/8A/JFK. The seats are assigned sequentially, whenever possible.

5–10 Airport Check-in User Guide

 CHAPTER 5 ASSIGNING SEATS
Assigning Seats on Thru (Direct) Flights

A confirmation of the new seat assignment displays, similar to the following:

In the example above, Jane Smith was assigned seat 11B for the DEN-JFK leg of flight 7777.
Because the ST command was used instead of the SA command, the seat assignment change
only applies to the second leg (DEN-JFK). Her seat assignment for the first leg, if there was
one, remains unchanged.
If you are making or changing a seat assignment on the currently loaded flight segment, you
do not need to include the destination in the ST command syntax. For example, if you wanted
to assign Jane Smith seat 11B on the SLC-DEN leg of flight 7777, you would simply enter
ST2/11B.

If the seat you request is not available, the system assigns the next available seat in the same
cabin and returns a message similar to the following:

Airport Check-in User Guide 5–11

 CHAPTER 5 ASSIGNING SEATS
Changing Seat Assignments

Changing Seat Assignments

You can change seat assignments at any time, even after passengers have checked in and boarded
the flight, using the SA command. However, if you change a seat assignment after the passenger
has checked in or boarded, you must re-print the boarding pass to reflect the current seat
assignment. See Re-printing Boarding Passes on page 4-39.
If necessary, you can change multiple seat assignments at once.

To change a seat assignment:

1 Display the passengers for whom to change seat assignments.

See Chapter 3, Displaying Passenger Lists.

2 At the command prompt, type SA<pax>/<seat> , then press Enter.

For example, to assign a window seat to the passenger on line 1, enter SA1/W.
A confirmation of the new seat assignment displays, similar to the following:

In the example above, Fred Smith changed from seat 2C to seat 4F.
For more information on what you can enter in the <seat> field, or for more information on
the SA command, see SA Command on page A-46.

5–12 Airport Check-in User Guide

 CHAPTER 5 ASSIGNING SEATS
Holding or Blocking Seats

Holding or Blocking Seats

In some cases, you may need to hold or block a seat on an aircraft. For example, you may need to
hold a seat for a passenger with special needs, or you may need to block a seat due to the seat
conditions, such as the necessity of a repair. This section describes how to hold and block seats
on an aircraft.
Once a seat is placed on hold it is initially only available for assignment by the agent who placed
the hold. However, once the agent’s current session expires (either by signing out of Check-in or
being inactive for a period of time exceeding the session time-out setting for their role), the seat
becomes available to all agents for assignment.
Blocked seats must first be “unblocked” before being assigned (see Unblocking Seats on page
5-16).
In Airport Check-in, seats on hold are denoted by an “h”, whereas blocked seats are denoted by
an “x”. However, both of these seat designations are denoted by an “R” in SkySpeed, indicating
the seat may not be assigned.
For thru flights, you can block a seat for the currently loaded leg or for all legs of the thru flight.

To hold or block a seat on a flight:

1 Display the seat map containing the seats to hold or block.

See Displaying the Seat Map on page 5-5.

2 At the command prompt, do one of the following:

• To hold a seat, type H<seat #> , then press Enter. For example, to hold seat 8A, enter
H8A. To hold seats 8A-8D, enter H8A-8D.

OR

• To block a seat, type BS<seat #> , then press Enter. For example, to block seat 8A, enter
BS8A. To block seats 8A-8D, enter BS8A-8D.

Note: For thru flights, to hold or block a seat for all legs of the thru flight, enter BS<seat #>/<final
destination> or H<seat #>/<final destination>. For example, to block seat 8A for all legs of a
thru flight to SLC, enter BS8A/SLC. To block seats 8A-8D for all legs of a thru flight to
SLC, enter BS8A-8D/SLC. To hold seat 8A for all legs of a thru flight to SLC, enter
H8A/SLC. To hold seats 8A-8D for all legs of a thru flight to SLC, enter H8A-8D/SLC.

Airport Check-in User Guide 5–13

 CHAPTER 5 ASSIGNING SEATS
Holding or Blocking Seats

A message displays, indicating that the seat has been held or blocked, similar to the
following:

5–14 Airport Check-in User Guide

 CHAPTER 5 ASSIGNING SEATS
Holding or Blocking Seats

3 (Optional) To view the updated seat map, type SM , then press Enter.

The updated seat map displays, similar to the following:

In this example, seat 16F has been blocked. Seats 14A-14C are on hold. Seats on hold are
denoted by an “h”, whereas blocked seats are denoted by an “x”.
Once a seat is placed on hold it is initially only available for assignment by the agent who
placed the hold. However, once the agent’s current session expires (either by signing out of
Check-in or being inactive for a period of time exceeding the “session time-out” setting for
their role), the seat becomes available to all agents for assignment. The session time-out
setting is configured in Management Console (System Users > Roles).
Blocked seats must first be “un-blocked” before being assigned (see Unblocking Seats on page
5-16).

Airport Check-in User Guide 5–15

 CHAPTER 5 ASSIGNING SEATS
Unblocking Seats

Unblocking Seats
You cannot assign blocked seats to passengers. If you need to assign a blocked seat, you must
first “unblock” the seat. This section describes how to remove the “blocked” status from a seat.
Seats on hold can be assigned to passengers; therefore, it is not necessary to remove the “hold”
status from a seat.

To unblock a seat:

1 Display the seat map containing the seats to unblock.

See Displaying the Seat Map on page 5-5.

2 At the command prompt, type US<blocked seat #> , then press Enter.

For example, to unblock seat 16F, enter US16F. To unblock multiple seats, for example 16D
through 16F, enter US16D-16F.
Note: For thru flights, to unblock a seat for all legs of the thru flight, enter US<seat #>/<final
destination>. For example, to unblock seat 8A for all legs of a thru flight to SLC, enter
US8A/SLC. To unblock seats 8A-8D for all legs of a thru flight to SLC, enter US8A-8D/SLC.
A message displays indicating that the seat has been unblocked, similar to the following:

3 (Optional) To view the updated seat map, type SM , then press Enter.

5–16 Airport Check-in User Guide

 CHAPTER 5 ASSIGNING SEATS
Unblocking Seats

The updated seat map displays, similar to the following:

In this example, the block was removed from seat 16F. However, seats 16D and 16E are still
blocked (denoted by an “x”).
Once the block is removed from a seat, you can assign the seat using the SA command (see
Assigning Seats on page 5-6).

Airport Check-in User Guide 5–17

 CHAPTER 5 ASSIGNING SEATS
Unblocking Seats

5–18 Airport Check-in User Guide

6 Checking In Baggage

In Airport Check-in, you can monitor and track the baggage checked in by passengers. As part of
the tracking process, you may be required to record the number of bags checked in for each
passenger, assign bag tag numbers, or record baggage weight. This section describes how to
perform tasks related to baggage check-in.
Airport Check-in has many baggage check-in features you can customize for your airline. For
information, see Customizing Airport Check-in on page 1-2.

In this chapter:

• Understanding Bag Tag Numbers on page 6-2

• Understanding Bag Tags and Baggage Messages in Multi-Carrier Situations on page 6-3
• Displaying Bag Tag Printers on page 6-5
• Selecting a Bag Tag Printer on page 6-6
• Checking In Baggage Manually on page 6-7
• Checking In Baggage Using Bag Drop Functionality on page 6-12
• Removing Baggage from Check-in on page 6-15
• Printing Bag Tags on page 6-16
• Performing Positive Bag Tag Matching on page 6-17

Airport Check-in User Guide 6–1

 CHAPTER 6 CHECKING IN BAGGAGE
Understanding Bag Tag Numbers

Understanding Bag Tag Numbers

Bag tag numbers are identification numbers assigned to each bag checked in to a flight. Bag tag
numbers may consist of letters, numbers, or a combination of both.
Bag tag numbers can be generated one of two ways:

• Manually. With this method, bag tag numbers are pre-printed on bag tags and entered by the
agent in Airport Check-in. Manual bag tags follow the format <final destination><6-digit
serial #>. For example, a bag whose final destination is the Salt Lake International airport
might be assigned the bag tag number SLC123456.
Note Airlines can set up a list of codes that agents may enter in place of the final destination at the
beginning of manual bag tag numbers. Refer to the “ManualBagTagCodes” setting in
CheckinConfig.xml on page 1-3 for details.
• Automatically. With this method, bag tag numbers are automatically generated by the
system and printed on bag tags at the time the baggage is checked in to the flight. Automatic
bag tags follow the format <1-digit bag type><3-digit airline IATA identifier><6-digit
serial #>. In the New Skies system, the bag type is always 0.

Whether you generate bag tag numbers manually or automatically depends on your airline
settings. For information on configuring bag tag number generation for your airline, please
contact a Navitaire representative.
The following table describes how bag tag numbers are generated under each scenario:

Automatic Manual

With this method, agents check in all bags for a With this method, agents check in each bag
passenger in one step (rather than checking individually. For each bag checked in, agents must
each bag individually). enter the destination airport code followed by the
six-digit bag tag number from the pre-printed bag
Bag tag numbers are generated automatically by
tag.
the system and printed on the bag tags at
check-in. • At check-in, check in each bag individually. For
each bag, enter the destination airport code
• When initially loading the flight, at the
followed by the pre-printed bag tag number
“Automatic Print Bag Tags” prompt, type Y.
(for example, JFK123456). Some airlines
(ARINC and SITA airports are not asked this
require that you enter the weight of the bag.
question; bag tags are always printed for For example, if a bag weighs 30 lbs., enter
these airports.) JFK123456/30.
• Select the bag tag printer.
• Complete the check-in process for the
• At check-in, check in all bags for a passenger passenger.
at once by entering the total number of bags Note: The New Skies system requires pre-printed
being checked in (for example, 2). Some
bag tag numbers to be six digits.
airlines require that you enter the total
baggage weight as well. For example, if a
passenger has two bags that weigh 30 lbs.
and 50 lbs., respectively, you would enter
2/80. Some airlines also require you to enter
the final destination of the bags.

• After you complete the check-in process for

the passenger, a bag tag is printed for each
bag. A system-generated bag tag number is
printed on each bag tag.

6–2 Airport Check-in User Guide

 CHAPTER 6 CHECKING IN BAGGAGE
Understanding Bag Tags and Baggage Messages in Multi-Carrier Situations

Understanding Bag Tags and Baggage Messages in

Multi-Carrier Situations
More and more, airlines are entering into partnerships with other carriers to offer more travel
options and better service to travelers. When baggage is added to a reservation, a bag tag and
message called the Baggage Sortation Message (BSM) are generated. In cases where the
reservation spans multiple carriers, the bag tag and BSM are used to communicate information
about the baggage to airport personnel.
A BSM is generated if the airline is using a bag tag printer to generate an automatic bag tag and
the airport or terminal that handles the bag has an automated baggage sortation system
requiring a BSM. These messages are sent, received, and processed by those systems in order to
achieve automated sortation and passenger and baggage reconciliation. For more information
about BSMs and system configuration for baggage messages, refer to the New Skies Type-B
Messaging Guide.
Note If the bag is removed from the reservation in Airport Check-in, a Baggage Unload Message
(BUM) or BSM DEL may be generated containing the same information as described for the
BSM below.
The table below outlines several scenarios in which a bag is added to a multi-leg reservation. It
outlines who prints the bag tag, who generates the BSM, and the specific flight information each
should contain.
The following airline codes are used in the examples:

• 1L - This is the Host carrier.

• OA - This is the other airline.
• CP - Code share partner (not configured for IATCI).
• IP - IATCI partner.

Scenario Flight Information Bag Tag BSM

Single airline. 1L 1111 SLC-DEN 1L 1111 SLC-DEN 1L 1111 SLC-DEN

1L 2222 DEN-JFK 1L 2222 DEN-JFK 1L 2222 DEN-JFK

Bag added at SLC by 1L. Printed by 1L. Sent by 1L/Navitaire to

Checked through to JFK. SLC, DEN, and JFK.*

Single airline. 1L 1111 SLC-DEN 1L 1111 SLC-DEN 1L 1111 SLC-DEN

1L 2222 DEN-JFK

Bag added at SLC by 1L. Printed by 1L. Sent by 1L/Navitaire to

Checked through to SLC and DEN.*
DEN.

OA/Passive 1L 1111 SLC-DEN 1L 1111 SLC-DEN 1L 1111 SLC-DEN

segment. OA 2222 DEN-JFK OA 2222 DEN-JFK OA 2222 DEN-JFK

Bag added at SLC by 1L. Printed by 1L. Sent by 1L/Navitaire to

Checked through to JFK. SLC.*

Airport Check-in User Guide 6–3

 CHAPTER 6 CHECKING IN BAGGAGE
Understanding Bag Tags and Baggage Messages in Multi-Carrier Situations

Scenario Flight Information Bag Tag BSM

Code share 1L 1111 SLC-DEN 1L 1111 SLC-DEN 1L 1111 SLC-DEN

initiating with CP 3333 DEN-JFK CP 3333 DEN-JFK CP 3333 DEN-JFK
Host.
Note This is the Printed by 1L. Sent by 1L/Navitaire to
operating carrier SLC.*
information. These
flights may be sold by
either airline.

Bag added at SLC by 1L.

Checked through to JFK.

Code share CP 4444 JFK-DEN CP 4444 JFK-DEN CP 4444 JFK-DEN

initiating with 1L 5555 DEN-SLC 1L 5555 DEN-SLC 1L 5555 DEN-SLC
code share
Note This is the Printed by CP. Sent by CP to JFK.*
partner.
operating carrier
Navitaire does not send
information. These
any BSM in this scenario
flights may be sold by
because the inbound
either airline.
BTM from the
Bag added at JFK by CP. non-hosted carrier
Checked through to SLC. (which tells Navitaire
there are bags) is not
supported.

IATCI initiating 1L 1111 SLC-DEN 1L 1111 SLC-DEN 1L 1111 SLC-DEN

with Host. IP 6666 DEN-JFK IP 6666 DEN-JFK IP 6666 DEN-JFK

Bag added at SLC by 1L. Printed by 1L. Sent by 1L/Navitaire to

Checked through to JFK. SLC.*

Note Navitaire sends IP

an outbound IATCI
message indicating that
the passenger has been
checked in with bags so
IP can print the
necessary BSMs for their
own flights.

IATCI initiating IP 7777 JFK-DEN IP 7777 JFK-DEN IP 7777 JFK-DEN

with IATCI 1L 5555 DEN-SLC 1L 5555 DEN-SLC 1L 5555 DEN-SLC
partner.
Bag added at JFK by IP. Printed by IP. Sent by IP to JFK.*
Checked through to SLC.
Note IP sends Navitaire
an inbound IATCI
message indicating that
the passenger has been
checked in with bags so
Navitaire can print the
necessary BSMs for the
host carrier. Navitaire
sends BSMs to DEN and
SLC.

*BSMs are only sent to terminals that are set up to require them. For more information about
terminal configuration or the types of BSMs sent to each recipient, refer to New Skies Type-B
Messaging Guide.

6–4 Airport Check-in User Guide

 CHAPTER 6 CHECKING IN BAGGAGE
Displaying Bag Tag Printers

Displaying Bag Tag Printers

You can display bag tag printers using the .BTP command. All bag tag printers configured for
the default location of the agent currently logged in display. For example, if the user currently
logged in is assigned to the “JFK” location, the bag tag printers configured for the “JFK” location
display. If no bag tag printers are configured for that location, the system displays all available
default bag tag printers.
The location to which an agent is assigned is determined by their assigned domain. Domains are
assigned a location in Management Console (System Users > Domains). Bag tag printers are
configured and assigned to locations in printer.xml. This file is located in Management Console
(System Configuration > Resource Management). For more information on locations, agents,
domains, and printer.xml, refer to the help files for Management Console.

To display the bag tag printers for your department:

• At the command prompt, type .BTP , then press Enter.

The bag tag printers configured for your department display, similar to the following:

In this example, all printers configured for the AIR location display. Notice that the currently
selected printer is denoted by the *SELECTED* message.
For each printer, you can view the printer name, description, and IP address. These
properties are configured in printer.xml. This file is located in Management Console (System
Configuration > Resource Management). For more information on printer.xml, refer to the
help files for Management Console.

Airport Check-in User Guide 6–5

 CHAPTER 6 CHECKING IN BAGGAGE
Selecting a Bag Tag Printer

Selecting a Bag Tag Printer

Each check-in station is configured to print bag tags to one particular printer. If your airline
prints bag tags at check-in, you are prompted to select the bag tag printer when you load the
initial flight in Airport Check-in. This becomes your default printer for the session. If you need to
change the bag tag printer, you can do so using the BTP command, as described in this section.

To select a bag tag printer:

1 At the prompt, type .BTP , then press Enter.

The bag tag printers configured for your department display.

For each printer, you can view the printer name, description, and IP address. These
properties are configured in printers.xml. This file resides in Management Console (System
Configuration > Resource Management).

2 At the prompt, type BTP/<printer #> , then press Enter.

For example, to select the printer on line 1, enter BTP/1. All bag tags are printed to the
selected printer.
Note: When you load the initial flight in Airport Check-in, if you select “Y” at the “Automatic
Print Bag Tags” prompt, the bag tag printers for your department display automatically.
Rather than following step 2 to select a bag tag printer, you can simply type the line number
of the desired printer , then press Enter.

6–6 Airport Check-in User Guide

 CHAPTER 6 CHECKING IN BAGGAGE
Checking In Baggage Manually

Checking In Baggage Manually

When you check in a passenger, you are automatically prompted to check in their baggage. After
a passenger has checked in, you can use either the B, AB, or MB command to add baggage.
Depending on your airline’s configuration, you may also be able to use these commands to add
baggage for passengers who have not yet checked in or you may be prohibited from adding bags
once a flight has been changed to close pending status. Refer to CheckinConfig.xml on page 1-3 for
details.
When you check in baggage, the system prompts you to enter either (1) the total number of bags
being checked in for the passenger or (2) the bag tag number for each bag. If your airline
generates bag tag numbers automatically, then you are required to enter the total number of bags
being checked in for the passenger—the bag tag numbers are printed on the bag tags
automatically. If your airline uses pre-printed bag tags, you are required to enter the bag tag
number from the pre-printed bag tag.
Bag weights may or may not be required, depending on the settings defined in Management
Console. Refer to Role Settings in Management Console on page 1-12 for details.
For standby passengers with thru flights, baggage check-in applies to all legs of the thru flight
unless your airline handles thru flights as separate flight segments, in which case passengers
need to check in their baggage at each downline city for which they are listed as standby. For
standby passengers with connecting flights, baggage check-in applies only to the specific
flight—standby passengers must check in their baggage at each downline city for which they are
listed as standby.
This section contains the following topics:

• Checking in Baggage (Automatic Bag Tag Printing)

If your airline is configured to print bag tags at check-in, you are prompted to enter the total
number of bags being checked in for the passenger. After the baggage is added, the bag tag
numbers are generated automatically and printed on the bag tags. See Checking In Baggage
(Automatic Bag Tag Printing) on page 6-7.

• Checking in Baggage (Pre-printed Bag Tags)

If your airline uses pre-printed bag tags, you are prompted to enter the bag tag number from
the pre-printed bag tag at check-in. See Checking in Baggage (Pre-printed Bag Tags) on page
6-9.

Checking In Baggage (Automatic Bag Tag Printing)

When generating bag tag numbers, airlines have the option to generate them automatically or
use pre-printed bag tags. This section describes how to check in baggage with automatic bag tag
number generation, assuming that you loaded the flight in automatic bag tag mode as described
in Loading Flights Directly after Login on page 2-2.
When you are checking in baggage with this method, you are prompted to enter the total
number of bags being checked in. After the baggage is added, the bag tag numbers are generated
automatically and printed on the bag tags. You may be prompted to ask passengers certain
questions regarding the baggage being checked in. These questions are unique for every airline.

Airport Check-in User Guide 6–7

 CHAPTER 6 CHECKING IN BAGGAGE
Checking In Baggage Manually

Note: If your airline is configured to generate bag tag numbers automatically, but your printer is
broken, you need to use the MB command to check in baggage as described in Checking in
Baggage (Pre-printed Bag Tags) on page 6-9. The MB command prompts you to enter a bag tag
number (rather than the total number of bags being checked in). If this is the case, when loading
the initial flight, make sure to select N at the “Automatic Print Bag Tags” prompt.
For more information on baggage check-in, see Checking In Baggage Manually on page 6-7.

To check in baggage with automatic bag tag printing:

1 Display the passenger whose baggage you want to check in.

For information on displaying passengers, see Chapter 3, Displaying Passenger Lists. If you are
checking in the passenger, proceed to step 3.

2 Type B<pax> or AB<pax>, then press Enter.

For example, to check in baggage for the passenger on line 1, enter B1 or AB1. These
commands perform the same function.
The “Enter number of bags” prompt displays, similar to the following:

3 Type the number of bags, then press Enter.

If your airline requires total baggage weight, you can enter it now. Type <# of
bags>/<weight> , then press Enter. For example, if the passenger is checking in two bags
with a total weight of 100 lbs, enter 2/100.

4 (Conditional) Enter bag weight.

If your airline requires individual or total baggage weight and you did not enter it in the
previous step, you are prompted to enter it now. Type the bag weight, then press Enter until
all weights have been entered.
Beginning with release 3.5, the system displays a warning if the bag weight exceeds the
maximum allowable weight as configured in the SkyPort Settings dialog of Management
Console. However, the warning only displays if your role requires you to collect bag weights
and your system is configured to track individual bag weights rather than total bag weight
for each passenger. This is a warning only and does not prevent the bag from being checked
in.

5 (Conditional) Verify the destination information.

If the bag’s final destination does not match the final destination of the journey, you may be
prompted to enter details about an informational segment similar to the following:

6–8 Airport Check-in User Guide

 CHAPTER 6 CHECKING IN BAGGAGE
Checking In Baggage Manually

If you type Y, the following displays:

Enter the other airline flight information as shown, and press Enter. Refer to the RZ User
Guide for more information on adding passive segments.
The bag is added. If the bag is associated with an IATCI reservation, an update is sent to the
other airline and a message displays on the screen that says “Sending update to OA system”.
Refer to Understanding Bag Tags and Baggage Messages in Multi-Carrier Situations on page 6-3
for more information.
To view the baggage checked in for a passenger, see Displaying the Baggage Checked In for a
Passenger on page 9-29.

To view the total baggage count for a flight, see Displaying the Baggage Count on page 10-4.

Checking in Baggage (Pre-printed Bag Tags)

When generating bag tag numbers, airlines have the option to generate them automatically or
use pre-printed bag tags. This section describes how to check in baggage with pre-printed bag
tags, assuming that you loaded the flight in pre-printed bag tag mode as described in Loading
Flights Directly after Login on page 2-2.

When you are checking in baggage using pre-printed bag tags, you are prompted to enter the
bag tag number from the pre-printed bag tag. You may be prompted to ask passengers certain
questions regarding the baggage being checked in. These questions are unique for every airline.

To check in baggage if you have pre-printed bag tags:

1 Display the passenger whose baggage you want to check in.

For information on displaying passengers, see Chapter 3, Displaying Passenger Lists. If you are
adding bags as part of the check-in flow, proceed to step 3.

2 Type B<pax>, AB<pax>, or if you normally use automatic bag tags but want to
override with manual, enter MB<pax> , then press Enter.

For example, to check in baggage for the passenger on line 1, enter B1, AB1, or MB1. MB1
always prompts you to enter a bag tag number, while B1 and AB1 only prompt for the bag
tag number if you pulled up the flight in pre-printed bag tag mode.
The “Enter bag tag #” prompt displays.

3 Enter the bag tag numbers.

Bag tag numbers may follow any of the these formats:

• <2-letter carrier code><6-digit serial number>

• <3-letter station code><6-digit serial number>

Airport Check-in User Guide 6–9

 CHAPTER 6 CHECKING IN BAGGAGE
Checking In Baggage Manually

• <3-letter station code><10-digit serial number> (A BSM is generated when this format is
used. Refer to Understanding Bag Tags and Baggage Messages in Multi-Carrier Situations on
page 6-3 for more information.)
• <3-letter manual bag tag code as defined in CheckinConfig.xml on page 1-3>
<6-digit serial number>
If your airline requires baggage weights, you can enter the weight of each bag now. Type
<bag tag #>/<weight> , then press Enter. For example, if the bag tag number is JFK000150
and the weight is 50 lbs, enter JFK000150/50.
The Enter bag tag # prompt displays again, prompting you to enter the next bag tag
number. Repeat this step until all bags have been entered for the passenger. Then press Enter
once more.

4 (Conditional) Enter bag weight.

If your airline requires baggage weight and you did not enter it in the previous step, you are
prompted to enter it now. Type the bag weight, then press Enter until all weights have been
entered.
Beginning with release 3.5, the system displays a warning if the bag weight exceeds the
maximum allowable weight as configured in the SkyPort Settings dialog of Management
Console. However, the warning only displays if your role requires you to collect bag weights
and your system is configured to track individual bag weights rather than total bag weight
for each passenger. This is a warning only and does not prevent the bag from being checked
in.

5 (Conditional) Verify the destination information.

If the bag’s final destination does not match the final destination of the journey or one of the
manual bag tag codes configured in CheckinConfig.xml, you may be prompted to enter
details about an informational segment similar to the following:

If you type Y, the following displays:

Enter the other airline flight information as shown, and press Enter. Refer to the RZ User
Guide for more information on adding passive segments.
Note The informational segment prompts do not display if your airline has set the
SkipPassiveSegmentPromptForManualBag configuration in CheckinConfig.xml to true.
The bag is added. If the bag is associated with an IATCI reservation, an update is sent to the
other airline and a message displays on the screen that says “Sending update to OA system”.
Refer to Understanding Bag Tags and Baggage Messages in Multi-Carrier Situations on page 6-3
for more information.

6–10 Airport Check-in User Guide

 CHAPTER 6 CHECKING IN BAGGAGE
Checking In Baggage Manually

6 To exit the bag tag mode, press Enter at the baggage prompt.

The command prompt displays.

To view the baggage checked in for a passenger, see Displaying the Baggage Checked In for a
Passenger on page 9-29.

To view the total baggage count for a flight, see Displaying the Baggage Count on page 10-4.

Airport Check-in User Guide 6–11

 CHAPTER 6 CHECKING IN BAGGAGE
Checking In Baggage Using Bag Drop Functionality

Checking In Baggage Using Bag Drop Functionality

You can use bag drop functionality to check bags simply by scanning a passenger’s boarding
pass.
In New Skies 3.4.6, two settings were added to the SkyPort Settings dialog in Management
Console. The Restrict Bag Drop to Current Station setting enables you to prevent bag tag printing
when the origin on the boarding pass does not match the current station. The Restrict Bag Drop
to Flights Departing Within 24 Hours from Current Time setting enables you to prevent bag tag
printing when the flight on the boarding pass does not depart within 24 hours. Refer to SkyPort
Settings Dialog on page 1-10 for more information about the SkyPort Settings dialog.

Note: In normal mode, bag drop can only be used to check in bags that have already been added via a
kiosk API or a Web API call. In release 3.5 an advanced mode was added that enables agents
with the proper role to add and remove bags directly from bag drop. Refer to Role Settings in
Management Console on page 1-12 for details about the SkyPort -> Bag Drop Mode role
setting.
Follow the steps below to access bag drop functionality

1 Select Baggage Check-in from the main menu OR from the command prompt, type
>bagtag, then press Enter.

The Baggage Check In screen displays.

2 (Conditional) Type the printer number, then press Enter.

Note If you have already selected a printer in auto mode, the same printer is used here by default.
To select a different printer you must go back to Check-in, change the printer using the BTP
command, and then re-enter Baggage Check-in.

3 At the prompt, enter your current station.

The command prompt displays as shown below.

6–12 Airport Check-in User Guide

 CHAPTER 6 CHECKING IN BAGGAGE
Checking In Baggage Using Bag Drop Functionality

The system uses the station code entered at login by default unless a different station is
specified here.

4 Scan the first boarding pass.

The passenger’s bags are retrieved and if you have access only to the basic bag drop mode,
the associated bag tags are printed. With advanced bag drop, you must manually print the
bag tags using the BT<pax> or BT<pax>/<bag> command.
Scanning should correctly find and board passengers on flights with operational suffix.
Note: You can also manually enter boarding pass information. To do so, enter Q<3-digit sequence
number><4-digit flight number><departure station (optional)>. Both the 3-digit sequence
number and the 4-digit flight number are padded with zeros if necessary.

5 (Conditional) Enter bag weight.

Depending on your airline’s requirements, you may be prompted to enter either the total
weight of all bags, or the weight of each individual bag. Type the appropriate information,
then press Enter.
The bag is checked in. If the bag is associated with an IATCI reservation and the passenger is
checked in, an update is sent to the other airline and a message displays on the screen that
says “Sending update to OA system”. Refer to Understanding Bag Tags and Baggage Messages
in Multi-Carrier Situations on page 6-3 for more information.

Beginning with release 3.5, the system displays a warning if the bag weight exceeds the
maximum allowable weight as configured in the SkyPort Settings dialog of Management
Console. However, the warning only displays if your role requires you to collect bag weights
and your system is configured to track individual bag weights rather than total bag weight
for each passenger. This is a warning only and does not prevent the bag from being checked
in.

6 (Conditional) Add or remove bags if you have permission to access bag drop’s
advanced mode.

This step is only possible if you are using New Skies 3.5 or later and your role permits you to
access the advanced mode of SkyPort’s bag drop functionality. Refer to Role Settings in
Management Console on page 1-12 for more information about the SkyPort -> Bag Drop Mode
role.
Use any of the following commands:

• AB to add a bag. The system prompts you to enter the number of bags and their weights.
• RB<pax> to remove all bags.
• RB<pax>/<bag> to remove a specific bag. For example, RB1/1 removes the first bag for
the first passenger.

7 (Conditional) Print bag tags if you have permission to access bag drop’s advanced
mode.

Advanced bag drop does not automatically print bag tags since you have the ability to add or
remove bags first.

Airport Check-in User Guide 6–13

 CHAPTER 6 CHECKING IN BAGGAGE
Checking In Baggage Using Bag Drop Functionality

Use either of the following commands:

• BT<pax> to print all bag tags.
• BT<pax>/<bag> to print a specific bag tag. For example, BT1/2 reprints the bag tag for
the first passenger’s second bag.

8 Type EX to return to Check-in.

6–14 Airport Check-in User Guide

 CHAPTER 6 CHECKING IN BAGGAGE
Removing Baggage from Check-in

Removing Baggage from Check-in

It may become necessary to remove baggage from check-in. For example, a passenger has
checked in baggage, but has not boarded the aircraft, and you need to close the flight. You should
un-check their baggage and ensure the baggage is removed from the aircraft. This section
describes how to un-check baggage.

To remove baggage from check-in:

1 Display the passenger whose baggage you want to un-check.

See Chapter 3, Displaying Passenger Lists.

2 Display the baggage currently checked in for the passenger.

For example, .B1 displays the baggage for the passenger on line 1 (see Displaying the Baggage
Checked In for a Passenger on page 9-29).

The baggage checked in for the passenger displays, similar to the following:

3 Type RB<bag line #>, then press Enter.

For example, RB1 removes the bag on line 1. A message displays, indicating that the bag has
been removed, similar to the following:

The bag is removed. If the bag was associated with an IATCI reservation and the passenger is
checked in, an update is sent to the other airline and a message displays on the screen that
says “Sending update to OA system”. Refer to Understanding Bag Tags and Baggage Messages
in Multi-Carrier Situations on page 6-3 for more information.

Important: Once the information for a bag is removed from check-in, the system no longer retains a
record of the bag; therefore, you should remove the bag from the aircraft.

Airport Check-in User Guide 6–15

 CHAPTER 6 CHECKING IN BAGGAGE
Printing Bag Tags

Printing Bag Tags

If your role permits, you can use the BT command either to print automatic bag tags for baggage
that has not yet been checked in or to re-print automatic bag tags for baggage added in Airport
Check-in. Refer to the Allow Bag Tag Reprint role setting in Role Settings in Management Console
on page 1-12 for more information.
Note Use the Booking History for Bag Tag Printing configuration in the SkyPort Settings Dialog of
Management Console to create a booking history record when bag tags are printed.

To print or re-print automatic tags for a passenger:

Note: When you load the initial flight in Airport Check-in, select “Y” at the “Automatic Print Bag
Tags” prompt.

1 Display the passenger whose bag tags you want to print.

See Chapter 3, Displaying Passenger Lists.

2 Type BT<pax> and then press Enter to print all bag tags for the passenger.

For example, to print bag tags for the passenger on line 1, enter BT1. The bag tags for this
passenger print on the selected printer. Any baggage that was added outside of Airport
Check-in is checked in automatically at this time.
OR

Type BT<pax>/<bag> and then press Enter to print a specific bag tag for the
passenger.

This use of the BT command was added in New Skies 3.5.

For example, to print the second bag tag for the passenger on line 1, enter BT1/2. The second
bag tag for this passenger prints on the selected printer. If the bag was added outside of
Airport Check-in, it is checked in automatically at this time.

6–16 Airport Check-in User Guide

 CHAPTER 6 CHECKING IN BAGGAGE
Performing Positive Bag Tag Matching

Performing Positive Bag Tag Matching

With positive bag tag matching, you can ensure that for each bag checked in to a flight, the
passenger who checked in the baggage has boarded the flight.
To perform positive bag tag matching, print the Checked Baggage report as it nears time to close
a flight. Then, display a list of passengers who have checked in to the flight but not yet boarded.
(These passengers are referred to as “un-boarded” throughout this section.) If you identify any
baggage that is checked in to the flight, but the passenger who checked in the baggage has not
yet boarded the aircraft, you may want to remove the baggage from the aircraft. If you remove
any baggage from the aircraft, you also need to remove the associated passenger from check-in
so that you can close the flight.
For positive bag tag matching to work, each bag checked in to the flight should have a bag tag
number entered into the system, either manually or automatically. For information on entering
bag tag numbers, see Checking In Baggage Manually on page 6-7.

To perform positive bag tag matching:

1 Load the flight to perform positive bag tag matching for.

See Chapter 2, Loading Flights.

2 Generate the Checked Baggage report.

This is a standard report that is generated through the reporting system, and may be an
option on the SkyPort Main menu. For information on generating this report, see the SkyPort
Reports User Guide.

3 Retrieve a list of passengers who have checked in to the flight but not yet boarded
(.QN command).

See Displaying “Un-boarded” Passengers on page 3-13. The list of passengers who have
checked in but not yet boarded displays.

From this list, you can determine whether an un-boarded passenger has bags checked in to
the flight. In the example above, Wilfredo Rodriguez has two bags checked in to the flight
and has not yet boarded the aircraft.

4 (Conditional) If any un-boarded passengers have checked in baggage, retrieve the

baggage information for the passenger (.B<pax> command).

The baggage information for the passenger displays, similar to the following:

Airport Check-in User Guide 6–17

 CHAPTER 6 CHECKING IN BAGGAGE
Performing Positive Bag Tag Matching

On this screen, you can view the bag tag numbers for each bag checked in by the un-boarded
passenger. After collecting the bag tag numbers for each un-boarded passenger, you can
request that the bags be removed from the aircraft. For information on removing bags from
check-in, see Removing Baggage from Check-in on page 6-15.
For information on displaying the bags checked in for a passenger, see Displaying the Baggage
Checked In for a Passenger on page 9-29.

If any bag has been removed from the aircraft, you should also remove the associated
passenger from check-in so that the flight can be closed. See Removing Passengers from
Check-in on page 4-35.

For information on closing flights, see Chapter 8, Closing Flights.

6–18 Airport Check-in User Guide

7 Boarding Passengers

A passenger who has checked in to a flight can be boarded on the flight. To board a flight, a
passenger must first be issued a boarding pass. Boarding passes authorize passengers to board
an aircraft. They are issued after a passenger has successfully checked in to their flight. Also,
passengers may not board flights where government validation is required until they have
obtained clearance.
Boarding passes can be configured to include information specific to the individual needs of
your airline. For information, see Customizing Airport Check-in on page 1-2.
Although passengers may be issued a boarding pass, they are not considered “boarded” until
their boarding pass number has been entered in Airport Check-in. Boarding passes are typically
entered automatically by scanners or manually by check-in agents. However, some airlines use
automated boarding whereby all passengers who have checked in for a flight are automatically
boarded when the flight is closed.
Note For carriers using Navitaire’s Loyalty product, Loyalty point accrual may be triggered during
boarding depending on your system configurations.

In this chapter:
• Boarding Passengers Individually on page 7-2
• Boarding Passengers by Scanning Boarding Passes on page 7-3
• Boarding All Passengers on page 7-5
• Un-boarding Passengers Individually on page 7-6
• Un-boarding All Passengers on page 7-7

Airport Check-in User Guide 7–1

 CHAPTER 7 BOARDING PASSENGERS
Boarding Passengers Individually

Boarding Passengers Individually

You can board passengers one at a time using the BRD command. For each passenger, you are
required to enter either a sequence number or a boarding pass number.
To board a passenger, the passenger must first be checked in to the flight. Passengers are
indicated as checked in with a single plus sign (+). To view a list of checked-in passengers, see
Displaying Checked-in Passengers on page 3-9.

To board all passengers on a flight at the same time, see Boarding All Passengers on page 7-5.

To board each passenger individually:

1 At the prompt, type BRD and press Enter.

The SEQUENCE-NUMBER prompt displays.

2 Type the sequence number of the passenger to board, then press Enter.

If your airline does not use sequence numbers for boarding, you are required to enter a
boarding pass number.
A message displays, indicating the passenger has been boarded, similar to the following:

Notice that two plus signs (++) display for the passenger, indicating that the passenger has
been checked in and boarded (the second plus sign indicates that the passenger has boarded).
If the passenger has pending payments, a warning also displays that says the passenger has a
balance due.

3 (Optional) To board any additional passengers, repeat step 2.

4 To exit the boarding mode, type EX, then press Enter.

The command prompt displays. To review a list of boarded passengers, enter the .QB
command (see Displaying Checked-in Passengers on page 3-9).

7–2 Airport Check-in User Guide

 CHAPTER 7 BOARDING PASSENGERS
Boarding Passengers by Scanning Boarding Passes

Boarding Passengers by Scanning Boarding Passes

Some airlines choose to board passengers by using a scanner to read boarding passes as
passengers board the aircraft. If you choose this type of system, you must configure your
boarding passes to contain one of the barcode types described in the Boarding Pass Configuration
User Guide.
Passengers may only be boarded after they are checked in to the flight. Passengers are indicated
as checked in with a single plus sign (+) in the passenger list display. To view a list of checked-in
passengers, see Displaying Checked-in Passengers on page 3-9.
You can board passengers by scanning boarding passes one at a time using the BRD command.
Simply enter BRD to access the board function. Then scan each passenger’s boarding pass. The
system displays any applicable prompts or warnings based on the information in the barcode.

To board each passenger by scanning the boarding pass:

1 At the prompt, type BRD and press Enter.

The SEQUENCE-NUMBER prompt displays.

2 Scan the barcode on the boarding pass.

Depending on your scanner configuration, you may have to press Enter.

Scanning should correctly find and board passengers on flights with operational suffix.
A seat assignment may or may not be required depending on the barcode format and the
value of the Prompt for Missing Seat During Boarding configurable setting in the SkyPort
Settings dialog.
If you are scanning a 1D type 5 barcode or a 2D barcode, the Prompt for Missing Seat During
Boarding configuration is checked, and no seat assignment exists, the system displays the
following warning:

Refer to CheckinConfig.xml on page 1-3 for more information about the BoardWithoutSeat2D
setting.

3 (Conditional) To board the passenger without a seat assignment type Y, then press
Enter.

If the information in the barcode does not match the information on the booking, the
passenger is not allowed to board. If the information matches, a message displays indicating
the passenger has been boarded, similar to the following:

Notice that two plus signs (++) display for the passenger, indicating that the passenger has
been checked in and boarded (the second plus sign indicates that the passenger has boarded).

Airport Check-in User Guide 7–3

 CHAPTER 7 BOARDING PASSENGERS
Boarding Passengers by Scanning Boarding Passes

If the passenger has pending payments, a warning also displays that says the passenger has a
balance due.

4 (Conditional) To board any additional passengers, repeat step 2.

5 To exit the boarding mode, type EX, then press Enter.

The command prompt displays. To review a list of boarded passengers, enter the .QB
command (see Displaying Boarded Passengers on page 3-13).

7–4 Airport Check-in User Guide

 CHAPTER 7 BOARDING PASSENGERS
Boarding All Passengers

Boarding All Passengers

You can board all passengers on a flight at the same time using the BRD command, and then
entering ALL for the sequence number.
Any passengers who check in after the ALL command has been entered must be boarded
individually (Boarding Passengers Individually on page 7-2).
To board a passenger, the passenger must first be checked in for the flight. Passengers are
indicated as checked in with a single plus sign (+). To view a list of checked-in passengers, see
Displaying Checked-in Passengers on page 3-9.

To board all passengers on a flight at the same time:

1 At the command prompt, type BRD, then press Enter.

The SEQUENCE-NUMBER prompt displays.

2 Type ALL, then press Enter.

A message displays, confirming whether you want to board all passengers on the flight.
Note: Any passengers who check in after the “ALL” command has been entered must be boarded
individually (see Boarding Passengers Individually on page 7-2).

3 Type Y, then press Enter.

A message displays, indicating the number of passengers that were boarded, similar to the
following:

4 To exit the boarding mode, type EX, then press Enter.

The command prompt displays. To review a list of boarded passengers, enter the .QB
command (see Displaying Boarded Passengers on page 3-13).

Automated Boarding
Some airlines prefer to automate the boarding process even further. If the
AutoBoardAllCheckedInPassengers setting in the CheckinConfig.xml file is set to true, all
passengers who have been checked into a flight are boarded automatically when the agent closes
the flight. Thus, there is no need to use the BRD command since passengers cannot check in after
a flight is closed. For information about closing flights, refer to Chapter 8, Closing Flights, on page
8-1.

Airport Check-in User Guide 7–5

 CHAPTER 7 BOARDING PASSENGERS
Un-boarding Passengers Individually

Un-boarding Passengers Individually

On occasion it may be necessary to “un-board” passengers from a flight. For example, a
passenger may become ill and want to cancel their flight. You can un-board passengers one at a
time using the BRD command.
When you un-board a passenger, the system does not prompt you to remove their baggage from
check-in. However, you should remove their baggage from check-in and also ensure that their
baggage has been physically removed from the aircraft. See Removing Baggage from Check-in on
page 6-15.
If you un-board a passenger and you need to close the flight, you must remove the passenger
from check-in as well; you cannot close a flight that has checked-in passengers who have not
boarded the aircraft. When you remove a passenger from check-in, the system may prompt you
to remove their baggage from check-in, depending on your airline settings. In either case, you
should always remove their baggage from check-in and ensure that their baggage has been
physically removed from the aircraft. See Removing Passengers from Check-in on page 4-35.

To un-board a passenger from a flight:

1 At the command prompt, type BRD, then press Enter.

The SEQUENCE-NUMBER prompt displays.

2 Type <sequence-number>X, then press Enter.

For example, to un-board the passenger whose sequence number is 40, enter 40X. If your
airline does not use sequence numbers, you are required to enter a seat number.
The un-boarded passenger displays, similar to the following:

Notice that only one plus sign (+) displays for the passenger, indicating that the passenger has
been checked in but is not boarded.

3 (Conditional) To un-board any additional passengers, repeat step 2.

4 To exit the boarding mode, type EX, then press Enter.

The command prompt displays. To review a list of un-boarded passengers, enter the .QN
command (see Displaying “Un-boarded” Passengers on page 3-13).

7–6 Airport Check-in User Guide

 CHAPTER 7 BOARDING PASSENGERS
Un-boarding All Passengers

Un-boarding All Passengers

It may be necessary to “un-board” a passenger from a flight. For example, a passenger may
become ill and want to cancel their flight. You can un-board all passengers from a flight at the
same time using the BRD command, and then entering ALLX for the sequence number.
When you un-board a passenger, the system does not prompt you to remove their baggage from
check-in. However, you should remove their baggage from check-in and also ensure that their
baggage has been physically removed from the aircraft. See Removing Baggage from Check-in on
page 6-15.
If you un-board a passenger and you need to close the flight, you must remove the passenger
from check-in as well; you cannot close a flight that has checked-in passengers who have not
boarded the aircraft. When you remove a passenger from check-in, the system may prompt you
to remove their baggage from check-in, depending on your airline settings. In either case, you
should always remove their baggage from check-in and ensure that their baggage has been
physically removed from the aircraft. See Removing Passengers from Check-in on page 4-35.

To un-board all passengers from a flight:

1 At the command prompt, type BRD, then press Enter.

The SEQUENCE-NUMBER prompt displays.

2 Type ALLX, then press Enter.

A prompt displays, confirming whether you want to un-board all passengers from the flight.

3 Type Y, then press Enter.

A message displays, indicating the number of passengers that were un-boarded from the
flight.

4 To exit the boarding mode, type EX, then press Enter.

The command prompt displays. To display a list of un-boarded passengers, enter the .QN
command (see Displaying “Un-boarded” Passengers on page 3-13).

Airport Check-in User Guide 7–7

 CHAPTER 7 BOARDING PASSENGERS
Un-boarding All Passengers

7–8 Airport Check-in User Guide

8 Closing Flights

After you have checked in and boarded all passengers on a flight, you can close the flight and
run the flight close reports.
Note There is a setting in Management Console > Roles that determines how many days, hours, or
minutes before flight departure a flight may be closed. Refer to Role Settings in Management
Console on page 1-12 for details.
As a flight nears closure, you can prepare the flight for closure by setting the flight to “close
pending” mode. In this mode, you can board passengers, but you cannot check in passengers. To
suspend booking on a flight, use Suspend Inventory, which is accessed through the Airports
menu.
This chapter describes how to (1) view the status of a flight, (2) change the status of a flight, and
(3) view the status history of a flight. Only agents with the appropriate role are allowed to
change the flight status.
Note For carriers using Navitaire’s Loyalty product, Loyalty point accrual may be triggered during
flight close depending on your system configurations.

In this chapter:
• Understanding Flight Status Types on page 8-2
• Setting Flights to Close Pending on page 8-3
• Closing Flights on page 8-4
• Opening Closed Flights on page 8-6

Airport Check-in User Guide 8–1

 CHAPTER 8 CLOSING FLIGHTS
Understanding Flight Status Types

Understanding Flight Status Types

The status of a flight determines whether you can check-in and board passengers on the flight.
You can always determine the current status of a flight from the command prompt; the status
displays at the end of the prompt. In the example below, the flight status is “close pending”
(CLPD):

All flight status changes, including opening, closing, close pending, and cancelling, can be
performed in Inventory Record Maintenance. In Airport Check-in, flights can be opened, closed,
and set to close pending, but not cancelled. However, in SkySchedule, flights may be cancelled.
The following table provides a description of flight status types:

Code Status Description

<no entry> Open Passengers can be checked in and boarded.

Flights can be opened in Airport Check-in and Inventory

Record Maintenance. If a flight has been cancelled, it can
only be “restored” in SkySchedule, Suspend/Cancel
Inventory, and Inventory Record Maintenance.

For more information on Inventory Record Maintenance,

refer to the Operations User Guide.

CLPD Close Pending Passengers can be boarded, but not checked in.

Flights can be set to “close pending” in Airport Check-in and

Inventory Record Maintenance.

CLSD Closed Passengers cannot be checked in or boarded.

Flights can be closed in Airport Check-in and Inventory

Record Maintenance.

CXLD Cancelled Passengers cannot be checked in or boarded. If the flight

departure occurs in the future, all passengers previously
booked on the flight are considered “no-shows” until they
are re-accommodated. In addition, the seats are returned
to inventory, although the seat cannot be sold because the
flight is cancelled.

Flights can be cancelled in SkySchedule, Suspend/Cancel

Inventory, and Inventory Record Maintenance. Flights
cannot be cancelled in Airport Check-in.

IROP Irregular Passengers can be checked in and boarded, but the flight is
Operations under irregular operations. You can set to “IROP” status in
Flight Following. For more information on Flight Following
and “IROP” status, refer the Operations User Guide.

VER Verified International flight has been verified.

8–2 Airport Check-in User Guide

 CHAPTER 8 CLOSING FLIGHTS
Setting Flights to Close Pending

Setting Flights to Close Pending

At any time, an agent with the AllowFlightStatusChange role can set the flight status to close
pending (CLPD). In this mode, you can board passengers on the flight, but you cannot check in
passengers to the flight. This can be useful if you are ready to close a flight, but not all passengers
have boarded. For example, a passenger at the baggage counter has checked in to the flight but
has not had time to get to the gate. You can set the flight to close pending and begin flight close
procedures.
Some airlines train agents to use the CP command on flights that have already been closed. This
changes the flight status from closed to close pending so no-show passengers can be removed
from the manifest.
Your airline may configure the system to enforce exit row seating requirements before flights are
set to close pending using the Enforce Over Wing Row Requirements setting in the SkyPort
Settings dialog of Management Console. In that case you cannot set a flight to close pending until
at least two passengers are checked in with seats on each side of the aircraft in each exit row.
Users with proper authorization (Override Over-Wing Exit Row Requirement role) can override
the exit row requirement. Refer to Chapter 1, Introduction to Airport Check-in for details on
system settings and roles.

To set a flight to close pending:

1 Select the flight you want to change to close pending status.

For more information on accessing flights, see Chapter 2, Loading Flights.

2 At the command prompt, type CP , then press Enter.

A close pending confirmation prompt displays.

3 At the prompt, type Y , then press Enter.

A message displays, indicating that the flight has been set to close pending.
The flight status is now close pending (CLPD), which means that you can board passengers or
remove no-show passengers, but you cannot check in passengers.
To re-open a flight that is in close pending mode, see Opening Closed Flights on page 8-6.

Airport Check-in User Guide 8–3

 CHAPTER 8 CLOSING FLIGHTS
Closing Flights

Closing Flights
After all passengers have checked in and boarded the flight, you can close the flight (CLSD) and
run the flight close reports. Typically, flights are closed after the aircraft has departed.
Note You must close flights in a timely manner to earn revenue if you use SkyLedger. There is also a
SkyLedger setting that “expires” revenue on flights that have not been closed within a certain
amount of time (usually two days).
When you close a flight, all no-show passengers become designated with an N.
You cannot close a flight that has passengers who have checked in but have not boarded unless
you are configured to use automated boarding. See Automated Boarding on page 7-5 for details. If
you are not using automated boarding and the number of passengers checked in does not match
the number of passengers boarded, you must remove the passengers who have checked in but
not boarded from check-in. See Removing Passengers from Check-in on page 4-35.
To display a list of these un-boarded passengers, use the .QN command. To view an updated
passenger count for the flight, use the U command.
If there are checked-in or boarded passengers on the flight who have a balance due when you
attempt to close the flight, the system displays a warning and a list of those passengers. The
flight closes successfully, and the airline is responsible for resolving the remaining balances.
Your airline may configure the system to enforce exit row seating requirements before flights are
closed using the Enforce Over Wing Row Requirements setting in the SkyPort Settings dialog of
Management Console. In that case you cannot set a flight to close pending until at least two
passengers are checked in with seats on each side of the aircraft in each exit row. Users with
proper authorization (Override Over-Wing Exit Row Requirement role) can override the exit row
requirement. Refer to Chapter 1, Introduction to Airport Check-in for details on system settings
and roles.
If the origin or departure country requires a PNRGOV message, a warning message displays to
alert you. Refer to Sending PNRGOV Messages on page 4-19 for details.
In versions 3.4.6 UPD 5 and higher, if the APIS send before flight close setting in the SkyPort
Settings dialog in Management Console is set to true and you have not yet sent an APIS report,
the system prompts you to send one. Refer to Sending the APIS Report to Customs on page 4-17.
Flights can be closed in Airport Check-in, Inventory Record Maintenance (see the Operations User
Guide), and Management Console (see the help file for Management Console). To suspend
booking on a flight, use Suspend Inventory, which can be accessed from the Operations menu.
This section describes how to close a flight in Airport Check-in.

To close a flight:

1 Select the flight you want to close.

For more information on accessing flights, see Chapter 2, Loading Flights.

Note There is a setting in Management Console > Roles that determines how many days, hours,
or minutes before flight departure a flight may be closed. Refer to Role Settings in
Management Console on page 1-12 for details.

2 At the command prompt, type CF , then press Enter.

8–4 Airport Check-in User Guide

 CHAPTER 8 CLOSING FLIGHTS
Closing Flights

A confirmation prompt displays.

3 At the prompt, type Y , then press Enter.

A message displays indicating that the flight has been closed.

Note If you do not see a confirmation and instead receive an error message and a list of
passengers with errors, you must correct all the errors before entering the CF command
again.
If you see a warning message and a list of passengers with warnings, the flight closes
successfully and the airline is responsible for handling the warnings if necessary.
The flight status is now “closed” (CLSD), which means that you cannot check in or board
passengers.
To re-open a closed flight, see Opening Closed Flights on page 8-6.

Airport Check-in User Guide 8–5

 CHAPTER 8 CLOSING FLIGHTS
Opening Closed Flights

Opening Closed Flights

After a flight has been closed, you may find it necessary to “re-open” the flight. For example, a
flight was closed, but then a “no-show” passenger shows up at the gate to check in; you must
open the flight to check the passenger in to the flight.
Flights can be opened in Airport Check-in and Inventory Record Maintenance (see the Operations
User Guide).
If a flight has been cancelled, it cannot be restored in Airport Check-in; it can only be restored in
SkySchedule, Suspend/Cancel Inventory, and Inventory Record Maintenance.
Note There is a setting in Management Console > Roles that determines how many days, hours, or
minutes before flight departure a flight may be closed. Refer to Role Settings in Management
Console on page 1-12 for details.

To open a “closed” or “close pending” flight:

1 Select the flight you want to open.

For more information on accessing flights, see Chapter 2, Loading Flights.

2 At the command prompt, type OF or OP to open the flight, then press Enter.

3 At the prompt, type Y , then press Enter.

A message displays indicating that the flight has been opened, which means that you can
check in and board passengers.

8–6 Airport Check-in User Guide

9 Modifying Passenger Information

As you perform the check-in and boarding procedures for a flight, it may be helpful to view or
modify passenger flight and reservation information.

In this chapter:

• Modifying Passenger Name Information on page 9-2

• Changing a Passenger Title to “CHD” on page 9-5
• Changing Standby Priority Codes on page 9-4
• Assigning SSRs on page 9-6
• Removing SSRs on page 9-8
• Entering Travel Documents on page 9-9
• Modifying Travel Documents on page 9-11
• Deleting Travel Documents on page 9-12
• Displaying Destination Addresses on page 9-13
• Entering Destination Addresses on page 9-14
• Modifying Destination Addresses on page 9-16
• Entering Passenger Emergency Contact Details on page 9-17
• Displaying Passenger Emergency Contact Details on page 9-18
• Modifying Passenger Emergency Contact Details on page 9-19
• Deleting Passenger Emergency Contact Details on page 9-20
• Entering Birthdates on page 9-21
• Maintaining Other Airline Frequent Flyer Information on page 9-22
• Associating Passenger Names with Customer Accounts on page 9-25
• Removing Customer Account Associations on page 9-26
• Associating Reservations with Customer Loyalty Accounts on page 9-27
• Displaying the Baggage Checked In for a Passenger on page 9-29
• Displaying the Baggage Allowance for a Passenger on page 9-31
• Changing Bag Weights on page 9-32
• Displaying Manifest Comments for a Passenger on page 9-33
• Displaying the SSRs Assigned to a Passenger on page 9-34
• Changing the Gender of a Passenger on page 9-35
• Unverifying a Passenger Document on page 9-36

Airport Check-in User Guide 9–1

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Modifying Passenger Name Information

Modifying Passenger Name Information

There may be times when passenger information, such as name, title, suffix, or assigned discount
code are entered incorrectly on a reservation. You can modify passenger names, titles, suffixes,
and discount codes using the N*<pax> command. SkyPort agents should have permission to
waive name change fees, since payment cannot be collected in SkyPort. Refer to the Codes >
Waive Fees role in Chapter 1, Introduction to Airport Check-in, on page 1-1 for details.
If a passenger name is associated with a customer account, you cannot use the N*<pax>
command; rather, you must modify the passenger name and title in SkySpeed.
Note: Names cannot contain special characters such as “~” or “/”. Also, if your airline accepts
bookings from external sources, always use UPPER CASE in the name field.

To modify a passenger name or title:

1 Display the passenger whose name or title to modify.

For more information, see Chapter 3, Displaying Passenger Lists.

2 Type N*<pax> , then press Enter.

For example, to modify passenger name information for the passenger on line 1, enter N*1.
A series of prompts display in succession, allowing you to change the following information
for the passenger:

• Last Name (required)

• First Name (required)
• Middle Name
• Suffix
• Title
• Pax Type
• Discount Code

3 At each prompt, enter the modified information and then press Enter.

To retain the original information or to leave the field empty, press Enter without typing.

9–2 Airport Check-in User Guide

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Modifying Passenger Name Information

The Pax name changed to prompt displays the updated passenger name information,
similar to the following:

In this example, Bob Smith was changed to Mr. Rob Smitt.

Airport Check-in User Guide 9–3

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Changing Standby Priority Codes

Changing Standby Priority Codes

Every standby passenger is assigned a “priority code” that determines the order in which they
are considered for the flight if a seat becomes available. These are called “standby priority
codes.”
Standby priority codes are configurable for every airline. Some airlines may choose to use “A, B,
C”, whereas other airlines may choose “A1, A2, A3, B1, B2, B3”. You can view the standby
priority codes for your airline using the STBY command.
This section describes how to change the standby priority code assigned to a passenger.

To change the standby priority code for a passenger:

1 Display the standby passenger whose priority code you want to change (.S
command).

The standby passenger displays, similar to the following:

In this example, Joe G. Smith is assigned the “A1” standby priority code.

2 At the prompt, type S<pax>/<priority code> , then press Enter.

For example, to change the priority code of the passenger on line 1 to “B1”, enter S1/B1.
To view the valid standby priority codes for your airline, use the STBY command. See
Displaying Valid Standby Priority Codes on page 10-13.

9–4 Airport Check-in User Guide

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Changing a Passenger Title to “CHD”

Changing a Passenger Title to “CHD”

You can change the passenger title of any passenger to “CHD” using the J<pax> command.
This does not change the passenger type to child; rather, it changes the passenger title to CHD
(just like adding MR or MRS to a passenger name).

To change a passenger title to “CHD”:

1 Display the passenger whose title you want to change to “CHD”.

See Chapter 3, Displaying Passenger Lists.

2 At the command prompt, type J<pax> , then press Enter.

For example, to change the passenger title on line 1 to “CHD,” enter J1. A message displays,
indicating the passenger is now designated as a “youth passenger”, similar to the following:

Important: Before the cleared passenger can be checked in to the flight, you must first execute the U
(update) command.

Airport Check-in User Guide 9–5

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Assigning SSRs

Assigning SSRs
Special Service Requests (SSRs) are special services offered by your airline to passengers. For
example, a passenger may request language assistance at the check-in counter. SSRs display on
the reservation and flight manifest. In addition, some airlines may include the SSR on boarding
passes.
When a passenger requests a special service from your airline, you can reserve the SSR for the
passenger in Check-in as long as there is no fee associated with the SSR. SSRs associated with a
fee must be assigned in either SkySpeed or RZ.
Only agents who are assigned the role “Allow Add/Remove Of SSR On Checked In Passenger” in
Management Console may add or remove SSRs once a passenger has checked in. However,
infant SSRs cannot be added after check-in regardless of the agent’s role due to security issues. In
order to add an infant, you must uncheck the passenger, add the infant, and re-check the
passenger.
Once a non-fee SSR is assigned in Check-in, the SSR displays on the itinerary and the manifest to
notify airline personnel of the request. For SSRs on IATCI reservations, the system sends a
message to the other airline alerting them of the request as well. Refer to Understanding SSR
Functionality for IATCI Reservations on page 9-6 for more information.

You can remove SSRs in SkySpeed and Airport Check-in, but not in RZ. Each time an agent adds
or removes an SSR, the agent’s user name displays along with the entry in the reservation history.
You can view the SSRs offered by your airline using the SSR command (see Displaying Valid SSR
Codes on page 10-14).

Understanding SSR Functionality for IATCI Reservations

Inter Airline Through Check-in (IATCI) enables passengers to check in with the first carrier in their
itinerary and be checked in for connecting flights operated by a different carrier at the same time. When an
SSR is added to an IATCI reservation, the request information is typically communicated to the other
airline. However, there are a few restrictions:

• Only SSR codes consisting of four alpha characters are supported for IATCI.
• Payment of SSR fees is not supported for IATCI.
• Removing a FQTV number from a booking does not trigger an IATCI update to be sent to the
other airline.
• With the exception of FQTV and TKNE, SSRs provided by the other airline in an IATCI reply
message are not added to the hosted airline booking.
• E-ticket numbers received from the other airline in an IATCI check-in message are not stored
in the hosted booking. This prevents conflicts with TA (ticket) form of payment functionality.

To reserve an SSR for a passenger:

1 Display the passenger for whom to reserve an SSR.

See Chapter 3, Displaying Passenger Lists.

2 Type SSR<pax>/<SSR code> , then press Enter.

9–6 Airport Check-in User Guide

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Assigning SSRs

For example, to assign the “PET” SSR to the passenger on line 1, enter SSR1/PET. To view a
list of valid SSR codes, use the SSR command (see Displaying Valid SSR Codes on page 10-14).
A message displays, indicating that the SSR has been assigned to the passenger, similar to the
following:

In this example, a “meet and assist” SSR (MAAS) has been booked for Bob Smith for the
YYZ-YHZ market.
If the SSR is associated with an IATCI reservation and the passenger is checked in, an update
is sent to the other airline and a message displays on the screen that says “Sending update to
OA system”. Refer to Understanding SSR Functionality for IATCI Reservations on page 9-6 for
more information.
If you attempt to reserve an SSR with a fee, a message similar to the following is displayed:

Airport Check-in User Guide 9–7

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Removing SSRs

Removing SSRs
Some passengers who have requested a Special Service Requests (SSR) of your airline may no
longer need the service. In these instances, remove the SSR from the passenger reservation.
Each time an agent adds or removes an SSR, the agent’s ID displays along with the entry in the
reservation history.

To “remove” an SSR:

1 Display the passenger for whom to remove an SSR.

See Chapter 3, Displaying Passenger Lists.

2 Type SSR<pax>/<SSR code>/R , then press Enter.

For example, to remove the “MAAS” SSR from the passenger on line 1, enter SSR1/MAAS/R.
To view the SSRs assigned to a passenger, use the .SSR<pax> command. For example, .SSR1
displays the SSRs reserved for the passenger on line 1.
A message displays, indicating that the SSR has been removed, similar to the following:

When you remove an SSR, the SSR no longer displays on the reservation or flight manifest. If
the SSR was associated with an IATCI reservation and the passenger is checked in, an update
is sent to the other airline and a message displays on the screen that says “Sending update to
OA system”.

9–8 Airport Check-in User Guide

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Entering Travel Documents

Entering Travel Documents

You can enter travel document information for passengers using the DOC command. For
example, you can enter passports, visas, or other information like U. S. Alien Registration
Numbers using this command.
To see a complete list of valid document types for a passenger, type DOCS<pax #> at the
prompt. A screen similar to the following displays, listing all document types that can be verified
for the passenger.

To enter travel document information for infants, use the DOCI command (rather than the DOC
command). First, there must be an infant SSR on the reservation, which can be added in
SkySpeed, SkySales, or RZ. To add an infant SSR using RZ, see the “Entering Infants”
information in the Airport Reservations Tool (RZ) User Guide.
If the passenger is associated with an IATCI reservation and has been checked in, the updated
travel document information is sent to the other airline and a message displays on the screen that
says “Sending update to OA system”.

To enter travel document information:

1 At the command prompt, type DOC<pax>.

For infants, use DOCI rather than DOC. A prompt similar to the following displays:

2 Enter the appropriate information on each line, and press Enter.

The following fields are required:

• Passenger Last Name - cannot contain certain special characters such as “~” or “/”.

Airport Check-in User Guide 9–9

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Entering Travel Documents

• Document Type Code - use one of the document types entered in Management Console
(System Settings > Codes > Document Types). Type ‘?’ on the Document type code line
and press Enter to see a list of valid types.
• Document Number - 1 to 35 alphanumeric characters.
• Passenger Nationality
All other fields are optional.

3 (Optional) To display all passengers that have international documents, type .DOC ,
then press Enter.

If you have just entered international document information for a passenger, enter the U
command to update the passenger information before entering the .DOC command.
For more information on viewing passengers with international documents, see Displaying
Passengers with International Documents on page 3-25.

9–10 Airport Check-in User Guide

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Modifying Travel Documents

Modifying Travel Documents

You can modify information for a passenger’s travel document using the .DOC*<doc>
command.
If the passenger is associated with an IATCI reservation and has been checked in, the updated
travel document information is sent to the other airline and a message displays on the screen that
says “Sending update to OA system”.

To modify travel document information:

1 Display all travel documents for the passenger.

Refer to Displaying Passengers with International Documents on page 3-25.

2 At the command prompt, type .DOC*<doc>.

For example, to modify the passenger’s second document, enter .DOC*<2>. The existing
document information displays.

3 Modify the appropriate information, and press Enter.

The document information is updated.

Airport Check-in User Guide 9–11

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Deleting Travel Documents

Deleting Travel Documents

You can modify information for a passenger’s travel document using the DOCX<doc>
command.
If the passenger is associated with an IATCI reservation and has been checked in, a message is
sent to the other airline stating that the travel document has been removed and a message
displays on the screen that says “Sending update to OA system”.

To delete travel document information:

1 Display all travel documents for the passenger.

Refer to Displaying Passengers with International Documents on page 3-25.

2 At the command prompt, type DOCX<doc>.

For example, to delete the passenger’s second document, enter DOCX<2>. The system
prompts you to verify that you want to delete the document.

3 Type Y or press Enter.

The document is removed from the system.

9–12 Airport Check-in User Guide

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Displaying Destination Addresses

Displaying Destination Addresses

Government security programs, such as APIS may require destination addresses for other airline
segments or active segments that were booked point to point are therefore not in the journey
being checked in. You can display all existing destination address information for a passenger
using the .DEST<pax> command.
When the required addresses are not in the system, you can add them using the DEST<pax>
command. Refer to Entering Destination Addresses on page 9-14 for details.

To display destination addresses:

1 Display the passenger.

You can display all passengers with the F command. For more information, refer to Displaying
All Passengers on a Flight on page 3-3.

2 At the command prompt, type .DEST<pax> and press Enter.

All destination addresses for the passenger display.

Airport Check-in User Guide 9–13

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Entering Destination Addresses

Entering Destination Addresses

Government security programs, such as APIS may require destination addresses for other airline
segments or active segments that were booked point to point are therefore not in the journey
being checked in. When these addresses are not in the system, you can add them using the
DEST<pax> command.

To enter a destination address:

1 Display the passenger.

You can display all passengers with the F command. For more information, refer to Displaying
All Passengers on a Flight on page 3-3.

2 At the command prompt, type DEST<pax> and press Enter.

A list of the passenger’s segments displays with a prompt similar to the following:

3 Type the line number of the segment for which to add a destination address and press
Enter.

If a destination exists for the specified segment, the system displays it and prompts you to
verify it. In that case proceed to step five. If no address exists, a prompt similar to the
following displays:

4 Enter the appropriate information on each line, and press Enter.

The following fields are required for APIS verification:

• Address-1
• City
• State/Province
• Country Code
All other fields are optional.

9–14 Airport Check-in User Guide

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Entering Destination Addresses

The address information displays similar to the following.

5 Enter ‘Y’ to save the address, or enter a line number to make a change.

If the passenger is associated with an IATCI reservation and has been checked in, a message is
sent to the other airline to update the address and a message displays on the screen that says
“Sending update to OA system”.

Airport Check-in User Guide 9–15

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Modifying Destination Addresses

Modifying Destination Addresses

You can modify a passenger’s destination addresses using the .DEST*<address> command.
If the passenger is associated with an IATCI reservation and has been checked in, the updated
travel document information is sent to the other airline and a message displays on the screen that
says “Sending update to OA system”.

To modify destination address information:

1 Display all destination addresses for the passenger.

Refer to Displaying Destination Addresses on page 9-13.

2 At the command prompt, type .DEST*<address>.

For example, to modify the destination address for the passenger’s second segment, enter
.DEST*<2>. The existing destination information displays.

3 Enter ‘Y’ to save the address, or enter a line number to make a change.

4 To update the address type the new information, and press Enter.

The document information is updated in New Skies.

If the passenger is associated with an IATCI reservation and has been checked in, New Skies
sends a message to the other airline to update the address and a message displays on the
screen that says “Sending update to OA system”.

9–16 Airport Check-in User Guide

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Entering Passenger Emergency Contact Details

Entering Passenger Emergency Contact Details

The New Skies reservation system has the ability to hold an emergency contact for a passenger.
This, however, is not transmitted to partner systems during IATCI processing.
You can enter an emergency address for a passenger using the EC command.

To add the emergency contact details for a passenger:

1 Display the passenger.

You can display all passengers with the F command. For more information, refer to Displaying
All Passengers on a Flight on page 3-3.

2 At the command prompt, type EC<pax#> and press Enter.

A prompt similar to the following displays:

3 Enter the appropriate information on each line, and press Enter.

4 Enter ‘Y’ to save the address.

The passenger emergency contact has been added.

Airport Check-in User Guide 9–17

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Displaying Passenger Emergency Contact Details

Displaying Passenger Emergency Contact Details

You can display the emergency address information for a passenger using the .EC<pax#>
command.

To display passenger emergency address:

1 Display the passenger.

You can display all passengers with the F command. For more information, refer to Displaying
All Passengers on a Flight on page 3-3.

2 At the command prompt, type .EC<pax#> and press Enter.

The emergency contact details for the passenger display.

9–18 Airport Check-in User Guide

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Modifying Passenger Emergency Contact Details

Modifying Passenger Emergency Contact Details

You can modify a passenger’s emergency contact details using the .EC*<adress line #>
command.

To modify the emergency contact information:

1 Display the passenger.

You can display all passengers with the F command. For more information, refer to Displaying
All Passengers on a Flight on page 3-3.

2 To display the emergency contact details for a passenger, type .EC<pax#> and press
Enter.

The emergency contact details for the passenger display.

3 Type .EC*<address line#> to modify the emergency address for the passenger.

The existing contact information displays.

4 Enter a line number to make a change then press Enter.

For example, type 4 to change the City.

5 Type the new information, and press Enter.

6 Enter ‘Y’ to save the address.

The passenger emergency contact has been updated.

Airport Check-in User Guide 9–19

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Deleting Passenger Emergency Contact Details

Deleting Passenger Emergency Contact Details

You can delete a passenger’s emergency contact details using the ECX<pax#> command.

To delete emergency contact information:

1 Display the passenger.

You can display all passengers with the F command. For more information, refer to Displaying
All Passengers on a Flight on page 3-3.

2 To display the emergency contact details for a passenger, type .EC<pax#> and press
Enter.

The emergency contact details for the passenger displays.

3 At the command prompt, type ECX<pax#>.

This will delete all emergency contact information for a specific passenger. The system
prompts you to verify that you want to delete the emergency address.

4 Enter ‘Y’ to delete the emergency contact details.

The passenger emergency contact has been removed.

9–20 Airport Check-in User Guide

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Entering Birthdates

Entering Birthdates
You can enter birthdates for passengers and associated infants using the BD and BDI commands.

To enter birthdate information for a passenger:

1 Display the passenger whose birthdate you are entering.

2 At the command prompt, type BD<pax>/<birthdate>.

For example, if the birthdate for the passenger on line 1 is 17 March 1981, enter
BD1/17MAR1981. Use the date format DDMMMYYYY.

If the passenger is associated with an IATCI reservation and has been checked in, the updated
birthdate is sent to the other airline and a message displays on the screen that says “Sending
update to OA system”.

To enter birthdate information for a lap infant:

1 Display the passenger associated with the lap infant to be updated.

2 At the command prompt, type BDI<pax>/<birthdate>.

For example, if the birthdate for the lap infant associated with the passenger on line 1 is 1
January 2013, enter BDI1/01JAN2013. Use the date format DDMMMYYYY.
If the passenger is associated with an IATCI reservation and has been checked in, the updated
birthdate is sent to the other airline and a message displays on the screen that says “Sending
update to OA system”.

Airport Check-in User Guide 9–21

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Maintaining Other Airline Frequent Flyer Information

Maintaining Other Airline Frequent Flyer

Information
Passengers may want to associate frequent flyer numbers with their bookings. Agents can add
this information when a passenger checks in.

To add frequent flyer information for a passenger:

1 Display the passenger.

You can display all passengers with the F command. For more information, refer to Displaying
All Passengers on a Flight on page 3-3.

2 Type FF<pax> , then press Enter.

For example, to add a frequent flyer number for the passenger on line 1, enter FF1.
The system prompts you to enter a frequent flyer number and the issuer’s code similar to the
following:

3 Follow the prompts , then press Enter.

A message displays indicating that the frequent flyer information has been added, similar to
the following:

If the affected traveler is associated with an IATCI reservation and has been checked in, an
update is sent to the other airline and a message displays on the screen that says “Sending
update to OA system”.

To modify frequent flyer information for a passenger:

1 Display the passenger.

You can display all passengers with the F command. For more information, refer to Displaying
All Passengers on a Flight on page 3-3.

2 Display the frequent flyer details for the passenger.

9–22 Airport Check-in User Guide

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Maintaining Other Airline Frequent Flyer Information

You can use the .FF<pax> command to display other airline frequent flyer information for a
passenger, similar to the following:

3 Type FF*<line #> , then press Enter.

For example, to modify the frequent flyer account on line two, enter FF*2.
The system displays the current information for that account and prompts you to enter the
new information similar to the following:

4 Follow the prompts , then press Enter.

A message displays indicating that the information has been updated.

If the affected traveler is associated with an IATCI reservation and has been checked in, an
update is sent to the other airline and a message displays on the screen that says “Sending
update to OA system”.

To remove a passenger’s frequent flyer information:

1 Display the passenger.

You can display all passengers with the F command. For more information, refer to Displaying
All Passengers on a Flight on page 3-3.

2 Display the frequent flyer details for the passenger.

You can use the .FF<pax> command to display frequent flyer information for a passenger,
similar to the following:

Airport Check-in User Guide 9–23

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Maintaining Other Airline Frequent Flyer Information

3 Type FF<line #>/R , then press Enter.

For example, to remove the frequent flyer number on line two, enter FF2/R.
The system asks whether you want to delete the information similar to the following:

4 Press Y , then press Enter.

A message displays indicating that the frequent flyer number has been removed.

If the affected traveler is associated with an IATCI reservation and has been checked in, an
update is sent to the other airline and a message displays on the screen that says “Sending
update to OA system”.

9–24 Airport Check-in User Guide

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Associating Passenger Names with Customer Accounts

Associating Passenger Names with Customer

Accounts
When a customer establishes a customer account with your airline, their customer account is
automatically “associated” with their name. For Airport Check-in, this means that their ten-digit
Customer ID displays on their boarding pass.
Sometimes, passengers request that their name not be associated with their customer account,
but then later decide to have it re-associated. This section describes how to associate passengers
names with customer accounts.
When associating a passenger name with a customer account, the passenger name on the
reservation must match exactly with the name entered on the customer account. Otherwise, the
system cannot make the association.
Note Use the .CU command to list all passengers on the current flight who are associated with a
customer account.

To associate a passenger name with a customer account:

1 Display the passenger to associate with a customer account.

See Chapter 3, Displaying Passenger Lists.

2 Type CU<pax>/<Customer ID> , then press Enter.

Customer IDs always contain ten digits. For example, to associate the passenger on line 1
with Customer ID #1234567890, enter CU1/1234567890.
A message displays, indicating that the customer account has been associated with the
passenger, similar to the following:

In the example above, Mike Johnson has been associated with customer account #X667859747.
This Customer ID is printed on the boarding pass.
If the customer is associated with an IATCI reservation and has been checked in, an update is
sent to the other airline and a message displays on the screen that says “Sending update to
OA system”.
If the customer name on a customer account is not the same as the passenger name on the
reservation you are trying to associate, the system cannot make the association. If necessary,
you can modify the name on a reservation using the N*<pax> command (see Modifying
Passenger Name Information on page 9-2).

To remove the association between a passenger and their customer account, see Removing
Customer Account Associations on page 9-26.

Airport Check-in User Guide 9–25

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Removing Customer Account Associations

Removing Customer Account Associations

There may be times when a passenger does not want to have their name associated with their
customer account, which means that they do not want to have their Customer ID printed on their
boarding pass. This section describes how to remove customer account associations.
For more information on customer account associations, see Associating Passenger Names with
Customer Accounts on page 9-25.

To disassociate a passenger from their customer account:

1 Display the passenger to remove the customer account association from.

You can use the F command to display all passengers on the flight or the .CU command to
display all passengers who have customer account associations. See Displaying Passengers
with Customer Accounts on page 3-33.

Any passenger associated with a customer account has a “C” after the sequence number,
similar to the following:

2 Type CU<pax>/R , then press Enter.

For example, to remove the association between the passenger on line 1 and their customer
account, enter CU1/R.
A message displays, identifying which passenger the customer account association is being
removed from and asking if you want to continue, similar to the following:

3 Type Y , then press Enter.

A message displays indicating that the customer ID is no longer associated with the
passenger.
To associate a customer account with a passenger name, see Associating Passenger Names with
Customer Accounts on page 9-25.

9–26 Airport Check-in User Guide

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Associating Reservations with Customer Loyalty Accounts

Associating Reservations with Customer Loyalty

Accounts
Passengers who want to use customer loyalty accounts, also known as frequent flier accounts,
when booking reservations may do so in SkySpeed. An agent can also associate a reservation
with a customer loyalty account before a traveler checks in. This section describes how to attach
frequent flier information to a reservation at check-in as well as how to change which frequent
flier account is associated with the reservation.
Note: Only customer loyalty accounts that are listed in a traveler’s customer account may be used in
Check-In. To add customer loyalty information to a customer account, please refer to
SkySpeed’s online help.

To associate a reservation with a customer loyalty account:

1 Display the passenger whose reservation you want to associate with a customer
loyalty account.

You can use the F command to display all passengers on the flight or the .CU command to
display all passengers who have customer account associations. See Displaying Passengers
with APIS Information on page 3-27.

Any passenger associated with a customer account has a “C” after the sequence number,
similar to the following:

2 Type CU<pax>/<Customer ID> , then press Enter.

For example, if the customer ID of the passenger on line one is 0930000011, enter
CU1/0930000011.

The system associates the customer’s default loyalty program with the reservation. A
message displays, identifying for which passenger the customer loyalty account association
was made and indicating the specific loyalty program that was used, similar to the following:

To change which customer loyalty account is associated with a reservation:

1 Display the passenger whose reservation you want to associate with a different
customer loyalty account.

You can use the F command to display all passengers on the flight or the .LP command to
display all passengers who have customer loyalty account associations. See Displaying
Passengers Associated with Customer Loyalty Programs on page 3-34.

Airport Check-in User Guide 9–27

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Associating Reservations with Customer Loyalty Accounts

Any passenger whose reservation is associated with a customer loyalty account has a letter
after the sequence number. This is the first letter of the program level. For example, a
passenger who is a gold member is identified by a “G”, similar to the following:

2 To associate the reservation with a different customer loyalty program on the

traveler’s customer account, type LP<pax>/<loyalty program>/<account number> ,
then press Enter.

For example, to associate the reservation with account 444555666 on the CPB program, enter
LP1/CPB/444555666.

The system associates the reservation with this customer loyalty account. A message
displays, identifying for which passenger the customer loyalty account association was made
and indicating the specific loyalty program that was used, similar to the following:

9–28 Airport Check-in User Guide

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Displaying the Baggage Checked In for a Passenger

Displaying the Baggage Checked In for a Passenger

You can display the baggage checked in for a passenger using the .B<pax> command. For each
bag, you can view the bag tag number, baggage weight, check-in status, final destination, and so
on.
If you need to remove bags, you must first display the baggage using .B<pax> command.

To display the baggage checked in for a passenger:

1 Display the passenger whose baggage you want to view.

See Chapter 3, Displaying Passenger Lists.

2 Type .B<pax> , then press Enter.

For example, to view the baggage checked in for the passenger on line 1, enter .B1. The
baggage displays, similar to the following:

Additionally, you can view the baggage count for the entire flight using the .B command.
This includes the total number of checked and thru baggage for the flight. See Displaying the
Baggage Count on page 10-4.

The following table explains the baggage information lines.

Element Example Description

<line #> 1) Line number associated with the baggage. For

example, “1)” represents the bag on line 1.

<bag tag #> 0999000643 Bag tag number (see Understanding Bag Tag
Numbers on page 6-2).

<weight> 0023 lb Baggage weight. In releases below 3.5, the

system does not include the unit of measurement,
such as pounds or kilograms; rather the system
only tracks the number of units, such as 0080.

In release 3.5 and higher, the system displays the

baggage weight along with the unit of measure,
which is configurable by station. However, if no
unit is configured for a given station the default is
kg.

<baggage check-in status> + Check-in status of the baggage; a single plus sign
(+) indicates the baggage has been checked in.

<baggage check-in date> 06Dec10 Date the baggage was checked in.

Airport Check-in User Guide 9–29

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Displaying the Baggage Checked In for a Passenger

Element Example Description

<baggage check-in time> 215858 Time the baggage was checked in, based on a
24-hour clock. The time format is HHMMSS
(hours, minutes, seconds).

<final destination airline 1L Airline code of the carrier operating the flight to
code> the final destination.

<final destination flight #> 9945 Flight number of the final destination flight on
which the baggage is checked. If the flight is
interline or code share, this is the operating flight
number.

<final destination airport JFK Airport code of the final destination on which the
code> baggage is checked.

<passenger status> Checked Status of the passenger on the flight.

9–30 Airport Check-in User Guide

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Displaying the Baggage Allowance for a Passenger

Displaying the Baggage Allowance for a Passenger

Some carriers allow travelers to purchase a baggage or extra baggage allowance during booking
and pay for excess baggage or airport baggage fees at the airport if necessary. Use the .BA<pax>
command to display a passenger’s total baggage allowance.

To display the current baggage allowance for a passenger:

1 Display the passenger whose baggage allowance you want to view.

See Chapter 3, Displaying Passenger Lists.

2 Type .BA<pax>, then press Enter.

For example, to view the baggage allowance for the passenger on line 1, enter .BA1. The total
baggage allowance displays, similar to the following:

The traveler in this example purchased a baggage allowance of 30 units -- whether pounds,
kilograms, or another unit of measure. The unit of measure depends on the weight type
configured for the station in Management Console.

Airport Check-in User Guide 9–31

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Changing Bag Weights

Changing Bag Weights

The CW command enables you to change the weight associated with a bag without having to
remove and re-add the bag. This is useful when an agent enters a bag weight incorrectly.
As of release 3.4.8, all changes to bag weight are now recorded in the booking history. This
enables carriers to closely monitor weight and balance data and track revenue. For optimal
results, ensure that the Write to Booking History For Bag Tag Printing setting (Management
Console > System Configuration > System Settings > SkyPort Settings) is enabled. With this
configuration turned on, the system stores a history entry on the booking whenever a bag tag is
printed or reprinted.

To change the weight of an individual bag:

1 Display the passenger whose baggage weight you want to change.

See Chapter 3, Displaying Passenger Lists.

2 Display the baggage currently checked in for the passenger.

For example, .B1 displays the baggage for the passenger on line one (see Displaying the
Baggage Checked In for a Passenger on page 9-29).

The baggage checked in for the passenger displays, similar to the following:

3 Type CW<bag line #>/<new weight>, then press Enter.

For example, CW1/25 changes the weight of the bag on line one to 25 pounds. A message
displays, indicating that the weight of the bag has been changed and asking whether you
want to reprint the bag tag, similar to the following:

4 Type Y and press Enter to reprint the bag tag, or press Enter to continue without
reprinting.

If you enter Y, the bag tag reprints to the bag tag printer. In New Skies 3.4.8 and higher a
record showing the new bag weight is added to the reservation history.

9–32 Airport Check-in User Guide

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Displaying Manifest Comments for a Passenger

Displaying Manifest Comments for a Passenger

You can display the manifest comments for a passenger using the .M<pax> command. Manifest
comments alert airline personnel to any special conditions of passengers on the flight. For
example, a passenger in a wheelchair may have a manifest comment that reads: Passenger in a
wheelchair. Manifest comments are added to reservations in SkySpeed and RZ.

To display the manifest comments for a passenger:

1 Display the passenger whose manifest comments you want to view.

See Displaying Passengers with Manifest Comments on page 3-20. You can also display
passengers using the F command; any passenger with manifest comments has an asterisk (*)
after their reservation number (for example, B1SIDF*).

2 Type .M<pax> , then press Enter.

For example, to view the manifest comments assigned to the passenger on line 1, enter .M1.
The manifest comments display, similar to the following:

In the example above, the comment verifies the passenger has been advised that
identification is required to board the flight.

Airport Check-in User Guide 9–33

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Displaying the SSRs Assigned to a Passenger

Displaying the SSRs Assigned to a Passenger

Some passengers have Special Service Requests (SSRs) for a flight. An SSR notifies airline
personnel, via the manifest, that a passenger has requested a special service from the airline. For
example, a passenger may request language assistance at the check-in counter. SSRs are assigned
to passengers in SkySpeed, SkySales, and RZ.
You can display the SSRs assigned to a passenger using the .SSR<pax> command.
There are several settings that affect the way SSRs display in Airport Check-in dialogs and on
boarding passes. First, the Add/Edit SSR dialog in Management Console enables you to
configure each SSR to either display or be suppressed in Check-in and on boarding passes. You
can also configure the SSR sort order for each culture within the Localization and Sorting dialog
in Management Console (System Configuration > Localization and Sorting). Then use the
Culture For Displaying SSRs In Check-in setting in the SkyPort Settings dialog to identify the
culture to be used to sort the SSRs. If SSR sorting is not configured for the specified culture or if
no culture is specified, Check-in displays infant SSRs first by default. Refer to CheckinConfig.xml
on page 1-3 and the help file for Management Console for details.

To display the SSRs for a passenger:

1 Display the passenger whose SSRs you want to view.

See Displaying Passengers with SSRs on page 3-21. You can also display passengers using the F
command; any SSRs are appended to the passenger name (for example, PACK/CARY
(MAAS).

2 Type .SSR<pax> , then press Enter.

For example, to view the SSRs assigned to the passenger on line 1, enter .SSR1. The SSRs
assigned to the passenger display, similar to the following:

In the example above, Fred Martin has two SSRs: MAAS (Meet and Assist), and YPTU (Youth
Passenger Traveling Unaccompanied).
If an asterisk displays next to the SSR (for example, MAAS*), the passenger has more than one
SSR.
With this information, you can notify other airline personnel of the special service requests.

9–34 Airport Check-in User Guide

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Changing the Gender of a Passenger

Changing the Gender of a Passenger

In the event that the gender of a passenger was incorrectly entered in a reservation, you can
modify the gender information using the CG<pax #>/m or CG<pax #>/f commands.

To change the gender of a passenger:

1 Display the passenger whose gender to modify.

For more information, see Chapter 3, Displaying Passenger Lists.

2 Type CG<pax #>/m or CG<pax #>/f, then press Enter.

For example, to change the passenger gender to male for passenger 1, enter CG1/M.
The Pax gender change prompt displays the update passenger gender information similar to
the following:

In this example, Bob Smith’s gender has been modified to male.

Airport Check-in User Guide 9–35

 CHAPTER 9 MODIFYING PASSENGER INFORMATION
Unverifying a Passenger Document

Unverifying a Passenger Document

In special cases, passenger documents can be mistakenly verified or in other cases the documents
provided by the passenger is found to be sufficient. This may require you to unverify the said
documents.

To unverify a passenger document:

1 Display the passenger whose gender to modify.

For more information, refer to Displaying Passengers with International Documents on page
3-25.

2 Check in the passenger and verify their travel documents.

Some flights require additional passenger validation before passengers can check in. See
Checking In Passengers on Flights Requiring Government Validation on page 4-11.

3 Type .apis*<line # of the document>/r to unverify the document then press

Enter.

9–36 Airport Check-in User Guide

10 Displaying Flight Information

Every flight you load in Airport Check-in has information regarding its schedule, the passengers
and baggage on the flight, and so on. This chapter describes how to view this type of information
for the currently loaded flight.

In this chapter:

• Displaying the Passenger Count on page 10-2

• Displaying the Baggage Count on page 10-4
• Displaying Downline Passenger Information on page 10-5

— Displaying the Downline Passenger Count on page 10-5

— Displaying Downline Passengers on page 10-6
• Displaying the Inbound, Connecting Passenger Count on page 10-9

— Displaying the Inbound, Connecting Passenger Count on page 10-9

— Displaying Inbound, Connecting Passengers on page 10-10
• Displaying Valid Standby Priority Codes on page 10-13
• Displaying Valid SSR Codes on page 10-14
• Viewing the Status History of a Flight on page 10-15

Airport Check-in User Guide 10–1

 CHAPTER 10 DISPLAYING FLIGHT INFORMATION
Displaying the Passenger Count

Displaying the Passenger Count

You can use the U command to update the passenger count for a flight. The passenger count
displays the number of passengers on the flight in various categories, such as the number of
passengers who are confirmed, standby, checked-in, boarded, no-show, and so on.
As you check in and board passengers, viewing the passenger count for the flight becomes
important. For example, if you want to close a flight, you can quickly determine how many
passengers have not checked in or boarded the flight.

To display an updated passenger count for the current flight:

1 At the command prompt, type U, then press Enter.

The Passenger Count screen displays an updated passenger count. If the aircraft has a single
cabin, the display appears similar to the following:

10–2 Airport Check-in User Guide

 CHAPTER 10 DISPLAYING FLIGHT INFORMATION
Displaying the Passenger Count

If the aircraft has multiple cabins, the display appears similar to the following. Note that the
totals for each cabin are displayed in separate columns in addition to a column at the right
that displays the totals for the entire flight.

If the passengers have been moved to the flight and their original cabin does not exist on the
current aircraft, the display appears similar to the following.

Airport Check-in User Guide 10–3

 CHAPTER 10 DISPLAYING FLIGHT INFORMATION
Displaying the Baggage Count

Displaying the Baggage Count

You can display the baggage totals for a flight using the .B command. The baggage totals include
the number of checked bags, thru bags, standby bags, and total number of bags on the flight.
For weights and balances, you can compare the baggage count information in Airport Check-in
against baggage reports to verify accurate baggage counts for the aircraft.

To display the baggage count for the current flight:

1 Load the flight whose downline passenger totals you want to view.

See Chapter 2, Loading Flights.

2 Type .B, then press Enter.

The Baggage Count screen displays the most current baggage count for the flight, similar to
the following:

For a description of the information that appears on this screen for each category, see the
following table.

Element Description

Counts -

Checked Bags: Number of bags checked in to the currently loaded flight.

Thru Bags: Number of thru bags coming from previous flight legs.

Standby Bags: Number of bags checked in to the currently loaded flight for
standby passengers.

Total Bags: Total number of bags checked in to the flight (bags checked on the
loaded flight segment and bags coming from previous flights
segments).

Weight Total bag weight for the category. In release 3.5 and higher, the
unit of measurement displays in parentheses, for example (lb),
[New in 3.5]
next to the weight heading. The unit is configurable by station.
However, if no unit is configured for a given station the default is
kg.

10–4 Airport Check-in User Guide

 CHAPTER 10 DISPLAYING FLIGHT INFORMATION
Displaying Downline Passenger Information

Displaying Downline Passenger Information

Any time a flight makes a stop or connection, the airport where the stop or connection occurs is
referred to as a downline airport. For example, suppose flight 147 originates in LAX, stops in SLC,
connects to flight 338 in ORD, and has a final destination at JFK. If you load the first leg of flight
147, its downline airports include SLC, ORD, and JFK.
You can either display only the downline passenger counts by airport or the counts along with
the name, fare class, customer program level, number of bags, and status of each downline
passenger with the .D and the .DN commands, respectively.

• Displaying the Downline Passenger Count on page 10-5

• Displaying Downline Passengers on page 10-6
The display screens do not include HL (standby) passengers. However, when the flight is closed,
HL passengers who are checked in and boarded for the flight may be changed to HK status
depending on the value of the ConvertHoldToConfirmed flight closure setting. Refer to
CheckinConfig.xml on page 1-3. At that point, these passengers are included in the passenger
totals since they have HK status.
Note To include IATCI and other OA flights and passenger names in the results, refer to the
configuration options available in the CheckinConfig.xml.

Displaying the Downline Passenger Count

You can display the passenger totals for each downline airport for a flight using the .D
command. This can be helpful if you need to give connection information to passengers,
determine how many passengers are manifested for each downline location, how many
passengers are no-shows, and so on.

To display downline passenger totals:

1 Load the flight whose downline passenger totals you want to view.

See Chapter 2, Loading Flights.

2 At the command prompt, type .D, then press Enter.

The passenger totals for each downline airport appear, similar to the following:

Note: To display the seat map along with the passenger counts, enter “.D,SM”.

In the example above, flight 637 is a thru flight that stops in LGA and ALB before landing in
BOS.

Airport Check-in User Guide 10–5

 CHAPTER 10 DISPLAYING FLIGHT INFORMATION
Displaying Downline Passenger Information

For a description of the information on this screen, see the following table:

Element Description

Downline Airports -

<airport code> Airport code of the downline airport. If a “y” appears before the
airport, that airport is the third flight of a double connection.

<airline code> Airline code of the airline supporting the flight.

<flight #> Number of the flight that stops at the specified airport. In the
example above, ORD L1 139 indicates that flight 139 (coming from
IAH) stops in ORD.

ETD Estimated time of departure of the first leg. For on-time flights,
this field displays the Scheduled Time of Departure. However, if a
time is entered for the Estimated Time of Departure in FLIFO
(there is a delay), this field displays the Estimated Time of
Departure entered in FLIFO.

Gt Departure gate number.

St If the flight is under IROP, an asterisk (*) displays in this field.

IROP status is entered in FLIFO.

Man Number of confirmed and unconfirmed passengers manifested for

the flight leg who are departing the aircraft at the station listed.

Ckd Number of confirmed and unconfirmed passengers checked in for

the flight leg who are departing the aircraft at the station listed.

N/S Number of no-show passengers on the flight leg who are departing
the aircraft at the station listed.

Bags Total number of bags checked in to the flight leg for passengers
who are departing the aircraft at the station listed, including bags
checked in to the flight locally and bags coming from previous legs
of the flight.

Includes only bags for HK (confirmed) and HU (unconfirmed)

passengers. Bags for any HL (standby) passengers on the flight
are displayed in the HL Bags column. However, when the flight is
closed, HL passengers who are checked in and boarded for the
flight may be changed to HK status depending on the value of the
ConvertHoldToConfirmed flight closure setting. Refer to
CheckinConfig.xml on page 1-3. At that point, bags for these
passengers are included in the Bags column since they have HK
status.

HL Bags Total number of bags for standby (HL) passengers who are
departing the aircraft at the station listed.

Displaying Downline Passengers

Use the .DN command to display downline passenger counts along with the name, fare class,
customer program level, number of bags, and status of each downline passenger. This can be
helpful during pre-flight planning or when there are flight disruptions.

10–6 Airport Check-in User Guide

 CHAPTER 10 DISPLAYING FLIGHT INFORMATION
Displaying Downline Passenger Information

To display a list of downline passengers:

1 Load the flight whose downline passengers you want to view.

See Chapter 2, Loading Flights.

2 At the command prompt, type .DN, then press Enter.

The passenger totals for each downline airport appear followed by a list of passengers,
similar to the following:

Note: To display the seat map along with the passenger list, enter “.DN,SM”.

In the example above, flight 9602 from SLC to DEN connects to flight 9603 from DEN to JFK.
The final destination of passenger 1 is DEN, and the final destination of the remaining four
passengers is JFK.
For a description of the information on this screen, see the following table:

Element Description

Downline Airports -

<airport code> Airport code of the downline airport. If a “y” appears before the
airport, that airport is the third flight of a double connection.

<airline code> Airline code of the airline supporting the flight.

<flight #> Number of the flight that stops at the specified airport. In the
example above, DEN 1L 9602 indicates that flight 9602 (coming
from SLC) stops in DEN.

ETD Estimated time of departure. For on-time flights, this field displays
the Scheduled Time of Departure. However, if a time is entered for
the Estimated Time of Departure in FLIFO (there is a delay), this
field displays the Estimated Time of Departure entered in FLIFO.

Gt Departure gate number.

St If the flight is under IROP, an asterisk (*) displays in this field.

IROP status is entered in FLIFO.

Man Number of confirmed and unconfirmed passengers manifested for

the flight leg who are departing the aircraft at the station listed.

Ckd Number of confirmed and unconfirmed passengers checked in for

the flight leg who are departing the aircraft at the station listed.

Airport Check-in User Guide 10–7

 CHAPTER 10 DISPLAYING FLIGHT INFORMATION
Displaying Downline Passenger Information

Element Description

N/S Number of no-show passengers on the flight leg who are departing
the aircraft at the station listed.

Bags Total number of bags checked in to the flight leg for passengers
who are departing the aircraft at the station listed, including bags
checked in to the flight locally and bags coming from previous legs
of the flight.

Includes only bags for HK (confirmed) and HU (unconfirmed)

passengers. Bags for any HL (standby) passengers on the flight
are displayed in the HL Bags column. However, when the flight is
closed, HL passengers who are checked in and boarded for the
flight may be changed to HK status depending on the value of the
ConvertHoldToConfirmed flight closure setting. Refer to
CheckinConfig.xml on page 1-3. At that point, bags for these
passengers are included in the Bags column since they have HK
status.

HL Bags Total number of bags for standby (HL) passengers who are
departing the aircraft at the station listed.

Downline Passengers Includes all manifested passengers: checked-in, boarded, and

no-show.

<passenger name> Full names of all manifested downline passengers listed in

alphabetical order.

<customer program Customer program level of the passenger.

level>

<class of service> Fare class booked by the passenger.

<number of bags> Total number of bags checked in for the specified downline
passenger.

<passenger status> Passenger status:

• <blank> = not checked in, not boarded.

• + = checked in, not boarded.

• ++ = checked in and boarded.

• NS = no-show.

10–8 Airport Check-in User Guide

 CHAPTER 10 DISPLAYING FLIGHT INFORMATION
Displaying Inbound Passenger Information

Displaying Inbound Passenger Information

Passengers arriving from other airports who are making connections at the current airport are
called inbound, connecting passengers. For example, a person who came from MSP and is
connecting at ORD for a flight to MCO is considered an inbound, connecting passenger at ORD.
You can either display only the inbound, connecting passenger counts or the counts along with
the name, fare class, customer program level, number of bags, and status of each inbound,
connecting passenger with the .I and the .IN commands, respectively.

• Displaying the Inbound, Connecting Passenger Count on page 10-9

• Displaying Inbound, Connecting Passengers on page 10-10
Note To include IATCI and other OA flights and passenger names in the results, refer to the
configuration options available in the CheckinConfig.xml.

Displaying the Inbound, Connecting Passenger Count

You can display the inbound, connecting passenger totals for a flight using the .I command.
These are passengers arriving from another airport who are making a connection at the currently
loaded airport.

To display the inbound, connecting passenger totals:

1 Load the flight whose connecting passenger totals you want to view.

See Chapter 2, Loading Flights.

2 Type .I, and then press Enter.

The connecting passenger totals appear, similar to the following:

In the example above, four passengers, inbound from YDF on flight 8845, are making a
connection at the currently loaded airport.
For a description of the information on this screen, see the following table:

Element Description

Inbound Airport -

<airport code> Airport code of the origin airport from the inbound flight leg. In the
example above, the flight leg is inbound from YDF.

Airport Check-in User Guide 10–9

 CHAPTER 10 DISPLAYING FLIGHT INFORMATION
Displaying Inbound Passenger Information

Element Description

<airline code> Airline code of the airline supporting the inbound flight leg. In the
example above, the airline code is L1.

<flight #> Number of the inbound flight leg. In the example above, flight
8845 is the inbound flight.

<operational suffix> One-character operational suffix appended to a flight number for

flights involved in an operational procedure.

If the flight number is not entered, no operational suffix is

required.

ETA Estimated time of arrival. For on-time flights, this field displays the
Scheduled Time of Arrival. However, if a time is entered for the
Estimated Time of Arrival in FLIFO (there was a delay), this field
displays the Estimated Time of Arrival entered in FLIFO.

Gt Arrival gate number.

St If the flight is under IROP, an asterisk (*) displays in this field.

IROP status is entered in FLIFO.

Man Number of passengers manifested on the inbound flight leg.

Ckd Number of passengers checked in on the inbound flight leg.

N/S Number of no-show passengers on the inbound flight leg.

Sby Number of standby passengers booked on the inbound flight leg.

Bags Total number of bags checked in for the inbound, connecting

passengers.

Displaying Inbound, Connecting Passengers

You can display the inbound, connecting passenger totals for a flight along with the name, fare
class, customer program level, number of bags, and status of each inbound, connecting
passenger using the .IN command.

To display a list of inbound, connecting passengers:

1 Load the flight whose connecting passenger totals you want to view.

See Chapter 2, Loading Flights.

2 Type .IN, and then press Enter.

10–10 Airport Check-in User Guide

 CHAPTER 10 DISPLAYING FLIGHT INFORMATION
Displaying Inbound Passenger Information

The connecting passenger totals appear, similar to the following:

In the example above, the first two passengers shown are inbound from SLC on flight 2398
and are making a connection at the currently loaded airport. The last two passengers are
inbound from SLC on flight 1000.

For a description of the information on this screen, see the following table:

Element Description

Inbound Airport -

<airport code> Airport code of the origin airport from the inbound flight leg. In the
example above, both flight legs are inbound from SLC.

<airline code> Airline code of the airline supporting the inbound flight leg. In the
example above, the airline code is 1L.

<flight #> Number of the inbound flight leg. In the example above, flights
2398 and 1000 are the inbound flights.

<operational suffix> One-character operational suffix appended to a flight number for

flights involved in an operational procedure.

If the flight number is not entered, no operational suffix is

required.

ETA Estimated time of arrival. For on-time flights, this field displays the
Scheduled Time of Arrival. However, if a time is entered for the
Estimated Time of Arrival in FLIFO (there was a delay), this field
displays the Estimated Time of Arrival entered in FLIFO.

Gt Arrival gate number.

St If the flight is under IROP, an asterisk (*) displays in this field.

IROP status is entered in FLIFO.

Man Number of passengers manifested on the inbound flight leg.

Ckd Number of passengers checked in on the inbound flight leg.

N/S Number of no-show passengers on the inbound flight leg.

Sby Number of standby passengers booked on the inbound flight leg.

Bags Total number of bags checked in for the inbound, connecting

passengers.

Inbound, Connecting -
Passengers

Airport Check-in User Guide 10–11

 CHAPTER 10 DISPLAYING FLIGHT INFORMATION
Displaying Inbound Passenger Information

Element Description

<passenger name> Full names of all inbound, connecting passengers listed in

alphabetical order.

<customer program Customer program level of the passenger.

level>

<class of service> Fare class booked by the passenger.

<number of bags> Total number of bags checked in for the specified passenger.

<passenger status> Passenger status:

• <blank> = not checked in, not boarded.

• + = checked in, not boarded.

• ++ = checked in and boarded.

• NS = no-show.

10–12 Airport Check-in User Guide

 CHAPTER 10 DISPLAYING FLIGHT INFORMATION
Displaying Valid Standby Priority Codes

Displaying Valid Standby Priority Codes

Priority codes are assigned in the system to determine the order in which passengers are
considered if a seat becomes available. Standby priority codes are configurable for individual
airlines. Some airlines may choose to use “A, B, C”, whereas other airlines may choose “A1, A2,
A3, B1, B2, B3”. This section describes how to view the standby priority codes for your airline
using the STBY command.
Standby priority codes are configured in Management Console (System Settings > Codes >
Standby Priorities) and assigned to passengers in SkySpeed, RZ, and Airport Check-in.

To display the standby priority codes for your airline:

• At the command prompt, type STBY, then press Enter.
The standby priority codes configured for your airline appear, similar to the following:

Airport Check-in User Guide 10–13

 CHAPTER 10 DISPLAYING FLIGHT INFORMATION
Displaying Valid SSR Codes

Displaying Valid SSR Codes

You can display the valid SSR codes configured for your airline using the SSR command. SSRs
are configured in Management Console (System Settings > SSR Code). For more information on
SSRs, see the online help for Management Console.

To view a list of SSR codes:

• At the prompt, type SSR, then press Enter.
The SSRs offered by your airline appear, similar to the following:

For each SSR, you can view the following:

— SSR code
— SSR name (for example, MAAS represents Meet and Assist)
— SSR group (if the SSR is inventoried)
— current availability for inventoried SSRs
SSR nests (groups) are configured in Management Console (System Settings > SSR Nest
Code).
To assign SSRs to passengers, see Assigning SSRs on page 9-6.

10–14 Airport Check-in User Guide

 CHAPTER 10 DISPLAYING FLIGHT INFORMATION
Viewing the Status History of a Flight

Viewing the Status History of a Flight

The status of a flight may change several times before the flight is flown. For example, a flight
may be set to close pending, closed, opened, and then closed again. All flight status changes are
tracked by the system. You can view the status history of a flight using the .FR command. This
command also displays any IROP comments entered in Flight Following.

To view the status history of the current flight:

1 Load the flight whose status history you want to view.

See Chapter 2, Loading Flights.

2 Type .FR, and then press Enter.

The status history of the flight appears, similar to the following:

On each line of the history you can view the flight status, date/time the action took place, and
user name of the person who performed the action. In the example above, flight 122 was
“opened” on January 20 at 11:22 by AGT1.

Airport Check-in User Guide 10–15

 CHAPTER 10 DISPLAYING FLIGHT INFORMATION
Viewing the Status History of a Flight

10–16 Airport Check-in User Guide

11 Creating Vouchers

There may be instances when you need to create vouchers for passengers. For example, some
airlines issue vouchers for lost luggage, cancelled or delayed flights, and so on. If your airline is
configured to do so, you can create vouchers for passengers in Airport Check-in. Vouchers can
also be used to pay for reservations.
To create vouchers in Airport Check-in, your airline must first configure voucher codes in
Management Console (Finance > Vouchers). For example, flight 711 is cancelled. You can create
voucher code X711 for the cancelled flight in Management Console, and then issue vouchers that
use the voucher code X711 to passengers on flight 711 in Airport Check-in.
All voucher codes are assigned a voucher type. The type is important in determining what
vouchers you can create in Airport Check-in. To create vouchers for individual passengers, the
voucher code must be the Individual voucher type. To create vouchers for an entire flight, the
voucher code must be the Flight voucher type. Vouchers are set up and managed in Management
Console (Finance > Account Management > Vouchers). For more information on voucher codes
and types, refer to the help files for Management Console.
Depending on your airline settings, you may not be able to create vouchers in Airport Check-in.
For information, see Customizing Airport Check-in on page 1-2.

In this chapter:

• Creating Vouchers for Individual Passengers on page 11-2

• Creating Vouchers for All Passengers on a Flight on page 11-4

Airport Check-in User Guide 11–1

 CHAPTER 11 CREATING VOUCHERS
Creating Vouchers for Individual Passengers

Creating Vouchers for Individual Passengers

This section describes how to create vouchers for individual passengers. You can create a
voucher for one passenger, and you can create vouchers for a sequential group of passengers. To
create vouchers for all passengers on a flight, see Creating Vouchers for All Passengers on a Flight
on page 11-4.
To create vouchers for individual passengers, your airline must first configure a voucher code
that has the Individual voucher type. For more information on voucher codes and types, refer to
the help files for Management Console.

To create vouchers for individual passengers:

1 Display the passenger for whom to create a voucher.

See Chapter 3, Displaying Passenger Lists.

2 At the prompt, do one of the following:

• To create a voucher for one passenger, type V<pax>/<voucher code> , then press Enter.
For example, to assign a voucher with the voucher code “DLY” to the passenger on line 1,
enter V1/DLY.
OR

• To create vouchers for a group of passengers, type V<pax>-<pax>/<voucher code> ,

then press Enter. For example, to assign vouchers with the voucher code “DLY” to the
passengers on lines 1–3, enter V1-3/DLY.
Note: When using the V command, you can only issue Individual voucher types. For more
information on voucher types, refer to the help files for Management Console

3 Enter the information requested at each prompt that follows , then press enter.

The system prompts you to enter the voucher’s expiration date, a reason code, and an
optional note. The available reason codes are listed on the screen for your reference.

11–2 Airport Check-in User Guide

 CHAPTER 11 CREATING VOUCHERS
Creating Vouchers for Individual Passengers

The system returns the voucher numbers, similar to the following:

In this example, voucher #57646166217600001 was created for Jane Doe. It is important to
inform the passenger of both the voucher code and the voucher number; the passenger needs
both as payment for a future reservation.
For more information on the V command, see Voucher Commands on page A-26.
Note: You can generate a report of the voucher numbers issued during a specific time period, as
well as the flights on which they were issued, in the Voucher Status report (a0063). For
more information on this report, see the Report s User Guide.

Airport Check-in User Guide 11–3

 CHAPTER 11 CREATING VOUCHERS
Creating Vouchers for All Passengers on a Flight

Creating Vouchers for All Passengers on a Flight

There may be instances when you need to issue vouchers for all passengers on a flight. For
example, if a flight is delayed or cancelled, you may wish to issue a voucher to every passenger
on the flight. Vouchers can be used to pay for reservations.
This section describes how to create vouchers for all passengers on a flight. To create vouchers
for individual passengers, see Creating Vouchers for Individual Passengers on page 11-2.
To create vouchers for all passengers on a flight, your airline must first configure a voucher code
that has the Flight voucher type. Voucher codes are managed in Management Console (Finance >
Vouchers). For more information on voucher codes and types, refer to the help files for
Management Console.

To create vouchers for all passengers on a flight:

1 Load the flight whose passengers you wish to create vouchers for.

See Chapter 2, Loading Flights.

2 At the command prompt, type VALL/<voucher code> , then press Enter.

For example, the voucher code X711 was created because flight 711 was cancelled. To issue
vouchers that use the voucher code X711 to all passengers on the cancelled flight, enter
VALL/X711.

3 Enter the information requested at each prompt that follows , then press enter.

The system prompts you to enter the vouchers’ expiration date, a reason code, and an
optional note. The available reason codes are listed on the screen for your reference.
The system returns a message, indicating that vouchers have been created for all passengers
on the flight, similar to the following:

When using the VALL command, the system does not return voucher numbers. Therefore, in
order to use the vouchers as payment on future reservations, the passenger must provide the
booking agent with the flight information so the booking agent can look up the voucher in the
system.
Note: When using the VALL command, you can only issue Flight voucher types. For more
information on voucher types, refer to the help files for Management Console.

11–4 Airport Check-in User Guide

A Summary of Check-in Commands

To perform any task in Airport Check-in, you must enter a command at the command prompt.
For example, to display all standby passengers on the currently loaded flight, you would enter
the .S command. To check in passengers for a flight, you would use the C command.
The commands in Airport Check-in can be divided into two categories:

• Action commands. These commands perform specific tasks, such as loading flights,
checking in passengers, and boarding passengers.
• Display commands. These commands display information. For example, you can display all
passengers on a flight, the SSR codes for your airline, the standby priority codes, and so on.
Some commands are both action commands and display commands. For example, when used
alone, the SSR command displays the valid SSR codes configured for your airline. However,
when used in combination with other commands, the SSR command can assign and remove
SSRs from reservations.

In this chapter:

• Summary of Action Commands on page A-2

• Summary of Display Commands on page A-9
• Summary of Commands by Task on page A-14
• Command Combinations on page A-28
• Custom Commands on page A-51

Airport Check-in User Guide A–1

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Summary of Action Commands

Summary of Action Commands

Action commands are used to perform tasks in Airport Check-in. For example, the C command
enables you to check in passengers. This section lists all of the action commands in Airport
Check-in, listed alphabetically.
In many cases, a single command is all you need to perform a task. For example, CLS clears the
screen. However, some tasks require command combinations. For example, to check in the
passenger on line 1 and assign seat 8A, you must enter C1/8A. For a description of command
“combinations”, see Command Combinations on page A-28.

Command Description Helpful References

AB Check in baggage. See Chapter 6, Checking In

Baggage.

APC<pax> Gather APPS documents and send to See Displaying Passengers Who
customs. Are Not Cleared for APPS on
page 3-30.
Note: The APC command is intended for use
by carriers who have APPS enabled for a
single country.

APIS Sends the APIS report for the currently See Sending the APIS Report to
loaded flight to the customs office of the Customs on page 4-17.
departure and/or arrival country. To use this
command, you must be assigned the “Verify
International Flight” permission and “Send
APIS Report” permissions in Management
Console (System Users > Roles). Before you
send the APIS Report, you must first verify it
using the FLTVERIFY command.

APIS/<2-char Sends the APIS report for the currently See Sending the APIS Report to
country loaded flight to the customs office of the Customs on page 4-17.
code> specified country only. To use this command,
you must be assigned the “Verify
[New in
International Flight” permission and “Send
3.4.10]
APIS Report” permissions in Management
Console (System Users > Roles). Before you
send the APIS Report, you must first verify it
using the FLTVERIFY command.

APISFINAL Verifies all remaining passengers as well as See Sending the APIS Report to
the currently loaded international flight Customs on page 4-17.
before sending the APIS report to the
customs office of the departure and/or arrival
country.

A–2 Airport Check-in User Guide

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Summary of Action Commands

Command Description Helpful References

APISPRE Sends a preliminary APIS report for the See Sending a Preliminary APIS
currently loaded flight to the customs office Report to Customs on page
of the departure and/or arrival country even 4-16.
if some passengers are not verified. The
report contains only passengers who are
checked in and have a verified travel
document.

Note This command should be used only

where the country requires one or more
non-interactive check-in messages. Use of
this command when it is not required may
result in duplicate messages being sent.

APPSALL Send APPS data for all passengers who have See Displaying Passengers Who
not yet cleared APPS. Are Not Cleared for APPS on
page 3-30.
Note: The APPSALL command is intended for
use by carriers who have APPS enabled for a
single country.

>BAGTAG Access the Baggage Check-in functionality. See Checking In Baggage Using
Bag Drop Functionality on page
6-12.

B Check in baggage. See Chapter 6, Checking In

Baggage.

BD Enter birthdates for passenger. See Entering Birthdates on page

9-21.

BDI Enter birthdates for lap infant. See Entering Birthdates on page
9-21.

BP Re-print boarding pass. See Re-printing Boarding Passes

on page 4-39.

BRD Board passengers on a flight. See Chapter 7, Boarding

Passengers.

BS Block a seat on an aircraft. See Holding or Blocking Seats

on page 5-13.

BSB Block a broken seat on an aircraft. See Holding or Blocking Seats

on page 5-13.

BT Print bag tags. See Printing Bag Tags on page

6-16.

BTP Select a bag tag printer. See Selecting a Bag Tag Printer
on page 6-6.

BUM Remove a passenger from boarded/checked -

in status and remove any passenger baggage
from the flight. This command generates an
external “BUM” message.

C Check in confirmed passengers individually See Checking In Confirmed

or in sequence. For example, typing C1 Passengers Individually or by
checks in passenger on line 1, whereas tying PNR on page 4-5.
C1-3 checks in passengers 1 through 3.

Airport Check-in User Guide A–3

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Summary of Action Commands

Command Description Helpful References

CALL Check in all confirmed passengers. See Checking In All Confirmed

Passengers on page 4-7.

CF Close a flight (CLSD). See Chapter 8, Closing Flights,

on page 8-1.

CG<pax Change the gender of the specified See Changing the Gender of a
#>/<gender passenger to female (f) or male (m). Passenger on page 9-35.
>

CL# Clear locked pax or PNR from queue. Clearing Locked Passengers
from a Queue on page 4-4.

CLS Clear any data that is currently on the -

screen, leaving only the command prompt.

CP Set flight status to “close pending” (CLPD). See Setting Flights to Close
Pending on page 8-3.

CS Check in standby passengers individually. See Checking In Standby

Passengers Individually or by
PNR on page 4-7.

CSALL Check in all standby passengers. See Checking In All Standby

Passengers on page 4-9.

CU Create/remove customer account See Associating Passenger

associations. Names with Customer Accounts
on page 9-25.

CW Change baggage weight. See Changing Bag Weights on

page 9-32.

DEST<pax> Add a destination address to the specified See Entering Destination

passenger. Addresses on page 9-14.
[New in 3.3.0
UPD 19]

.DEST* Edit the specified destination address for the See Modifying Destination
<address> current passenger. Addresses on page 9-16.

[New in 3.3.0
UPD 19]

DOC Add travel documents for a passenger. Entering Travel Documents on

page 9-9.

.DOC*<doc> Edit a travel document. Modifying Travel Documents on

page 9-11.

DOCVERIFY/F This command is used prior to boarding on See Verifying all Passengers on
flights requiring e-Borders verification. It page 4-14.
verifies the first valid document for any
passenger on the currently loaded
international flight who does not yet have a
verified document. The system must be
configured to AllowForceFLTVERIFY. Refer to
CheckinConfig.xml on page 1-3 for details.

DOCX<doc> Delete a travel document. Deleting Travel Documents on

page 9-12.

A–4 Airport Check-in User Guide

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Summary of Action Commands

Command Description Helpful References

FF Add other airline frequent flyer information See Maintaining Other Airline
for a passenger. Frequent Flyer Information on
page 9-22.

FF* Edit a passenger’s other airline frequent flyer See Maintaining Other Airline
information. Frequent Flyer Information on
page 9-22.

FF/R Remove a passenger’s other airline frequent See Maintaining Other Airline
flyer number. Frequent Flyer Information on
page 9-22.

FLTVERIFY Verify the currently loaded international flight See Sending the APIS Report to
(used in conjunction with the APIS Customs on page 4-17.
command). To use this command, you must
be assigned the “Verify International Flight”
permission and “Send APIS Report”
permissions in Management Console (System
Users > Roles).

FLTVERIFY/F This command is known as force FLTVERIFY. See Verifying all Passengers on
It verifies the first valid document for any page 4-14.
boarded passenger on the currently loaded
international flight who does not yet have a
verified document. It then verifies the flight.
See AllowForceFLTVERIFY in
CheckinConfig.xml on page 1-3 for details.

FLTVERIFYX Remove the verification for the currently See Sending the APIS Report to
loaded international flight. Customs on page 4-17.

GP Print a gate pass to the boarding pass See Printing Gate Passes on
printer. page 4-40.

GS Shortcut to General Reference. See Shortcut to General

Reference on page B-2.

H Place a seat on hold. See Holding or Blocking Seats

on page 5-13.

HELP Access online Help. See Using Online Help on page

1-23.

II Print itinerary receipt to boarding pass See Re-printing Itineraries on

printer. page 4-39.

IROP Shortcut to Irregular Operations. See Shortcut to Irregular

Operations (IROP) on page B-3.

IT Re-print an itinerary. See Re-printing Itineraries on

page 4-39.

J Change a passenger title to “CHD”. See Changing a Passenger Title

to “CHD” on page 9-5.

LF Load a flight scheduled on the current date See Loading Flights from the
by typing the command followed by the city Command Prompt on page 2-8.
pair and flight number and the airline code.
(For example: LFSLCLAX203/1L.)

Airport Check-in User Guide A–5

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Summary of Action Commands

Command Description Helpful References

LL Load a flight scheduled on the same date as See Loading Flights from the
the current flight by typing the command Command Prompt on page 2-8.
followed by the flight number and the airline
code. (For example: LL203/1L.)

LP Create/remove an association between a See Associating Passenger

passenger and a loyalty program (for Names with Customer Accounts
example: LP1/FRQ/123456789 associates on page 9-25.
passenger 1 with the loyalty program FRQ,
account number 123456789).

MB Check in baggage. See Chapter 6, Checking In

Baggage.

MC Check in passengers individually on a See Checking and Unchecking

marketing code share, outbound interline, or Confirmed Passengers
DCS-controlled flight. Individually on a Marketing Code
Share, Outbound Interline, or
Third-Party-Controlled Flight on
page 4-31.

MCALL Check in all passengers on a on a marketing See Checking and Unchecking

code share, outbound interline, or All Confirmed Passengers on a
DCS-controlled flight. Marketing Code Share,
Outbound Interline, or
Third-Party-Controlled Flight on
page 4-32.

MCS Check in standby passengers individually on See Checking and Unchecking

a marketing code share, outbound interline, Standby Passengers Individually
or DCS-controlled flight. on a Marketing Code Share,
Outbound Interline, or
Third-Party-Controlled Flight on
page 4-32.

MCSALL Check in all standby passengers on a See Checking and Unchecking

marketing code share, outbound interline, or All Standby Passengers on a
DCS-controlled flight. Marketing Code Share,
Outbound Interline, or
Third-Party-Controlled Flight on
page 4-33.

MD Move down to view the next page of data –

(scroll down).

MU Move up to view the previous page of data –

(scroll up).

N* Modify passenger name information. See Modifying Passenger Name

Information on page 9-2.

OF Re-open a flight. See Opening Closed Flights on

page 8-6.

OP Re-open a flight. See Opening Closed Flights on

page 8-6.

OPS Shortcut to Flight Following (FLIFO). See Shortcut to Flight Following

(FLIFO) on page B-4.

A–6 Airport Check-in User Guide

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Summary of Action Commands

Command Description Helpful References

PNRGOV Send a PNRGOV message for the current See Sending PNRGOV Messages
flight to one or more governments who on page 4-19 and PNRGOV
[New in 3.4.5]
require it. Command on page A-42.

Q Manually enter boarding pass information to See Checking In Baggage Using

print bag tags. Bag Drop Functionality on page
6-12.

R Remove confirmed passengers from See Removing Confirmed

check-in. Passengers from Check-in
Individually on page 4-35.

RALL Remove all confirmed passengers from See Removing All Confirmed
check-in. Passengers from Check-in on
page 4-36.

RB Remove baggage from check-in. See Removing Baggage from

Check-in on page 6-15 and
Checking In Baggage Using Bag
Drop Functionality on page 6-12.

RMC Uncheck passengers individually on a See Checking and Unchecking

marketing code share, outbound interline, or Confirmed Passengers
third-party-controlled flight. Individually on a Marketing Code
Share, Outbound Interline, or
Third-Party-Controlled Flight on
page 4-31.

RMCALL Uncheck all passengers on a on a marketing See Checking and Unchecking

code share, outbound interline, or All Confirmed Passengers on a
third-party-controlled flight. Marketing Code Share,
Outbound Interline, or
Third-Party-Controlled Flight on
page 4-32.

RMCS Uncheck standby passengers individually on See Checking and Unchecking

a marketing code share, outbound interline, Standby Passengers Individually
or third-party-controlled flight. on a Marketing Code Share,
Outbound Interline, or
Third-Party-Controlled Flight on
page 4-32.

RMCSALL Uncheck all standby passengers on a See Checking and Unchecking

marketing code share, outbound interline, or All Standby Passengers on a
third-party-controlled flight. Marketing Code Share,
Outbound Interline, or
Third-Party-Controlled Flight on
page 4-33.

RS Remove standby passengers from check-in. See Removing Standby

Passengers from Check-in
Individually on page 4-37.

RSALL Remove all standby passengers from See Removing All Standby
check-in. Passengers from Check-in on
page 4-37.

RZ Shortcut to the Reservations Tool (RZ). See Shortcut to the Reservations

Tool (RZ) on page B-6.

Airport Check-in User Guide A–7

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Summary of Action Commands

Command Description Helpful References

RZGO Shortcut to open the Reservations Tool (RZ) See Shortcut to the Reservations
with pre-populated fields. Tool (RZ) on page B-6.

S Change passenger standby priority code. See Changing Standby Priority

Codes on page 9-4.

SA Make seat assignment. See Chapter 5, Assigning Seats.

SENDGOV Resubmit security data for any passenger on See Resubmitting Security
current and past dated flights requiring Data on page 4-26.
security verification.

SSR Display the valid SSR codes configured for See Assigning SSRs on page
your airline, as well as assign/remove SSRs. 9-6, Removing SSRs on page
9-8, and Displaying Valid SSR
Codes on page 10-14.

ST Assign a seat on a particular leg of a thru See Assigning Seats for a

flight. Specific Leg of a Thru Flight on
page 5-10.

UNAPISPRE Sends an unverified preliminary APIS report See Sending an Unverified

for the currently loaded flight to the customs Preliminary APIS Report to
[New in 3.4.11
office of the departure and/or arrival country Customs on page 4-15.
UPD 6]
even if passengers are not yet checked in nor
verified. The report contains all passengers.

Note This command should be used only

where the country requires one or more
non-interactive check-in messages. Use of
this command when it is not required may
result in duplicate messages being sent.

UNAPISPRE/ Sends an unverified preliminary APIS report See Sending an Unverified

<country for the currently loaded flight to the customs Preliminary APIS Report to
code> office of the country specified in the Customs on page 4-15.
command.
[New in 3.4.11
UPD 6] Note This command should be used only
where the country requires one or more
non-interactive check-in messages. Use of
this command when it is not required may
result in duplicate messages being sent.

US Un-block a seat on the aircraft. See Unblocking Seats on page

5-16.

V Issue a voucher to a passenger. See Creating Vouchers for

Individual Passengers on page
11-2.

VALL Issue vouchers to each passenger on a flight. See Creating Vouchers for All
Passengers on a Flight on page
11-4.

.APIS*<line# Unverify the passenger document provided. See Unverifying a Passenger

of the Document on page 9-36.
document>/r

A–8 Airport Check-in User Guide

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Summary of Display Commands

Summary of Display Commands

Display commands are used to display information in Airport Check-in. For example, you can
display all passengers on a flight, the SSR codes for your airline, the standby priority codes, and
so on. This section lists all display commands in Airport Check-in, listed alphabetically.
Any command that begins with a dot (.) is a “display” command. For example, the .S command
displays all standby passengers on the currently loaded flight. Some display commands do not
begin with a dot (.). For example, the F command displays all passengers on the currently loaded
flight, but does not begin with a “.”.
In many cases, a single command is all you need to perform a task. For example, .B displays
baggage totals for the flight. However, some tasks require command combinations. For example,
to display the manifest comments for the passenger on line 1, you must enter .M1. For a
description of command “combinations”, see Command Combinations on page A-28.

Command Description Helpful References

.<seat #> Display the passenger assigned to the See Displaying the Passenger
specified seat. Assigned a Specific Seat on page
3-35.

.<PNR> Display all passengers on the indicated PNR. See Displaying All Passengers on
the Indicated Reservation on
page 3-8.

.APC Display all passengers who are checked in See Displaying Passengers Who
but do not have APPS clearance. Are Not Cleared for APPS on
page 3-30.

.APIS Display APIS information for passengers. See Displaying Passengers with
APIS Information on page 3-27.

.APIS<pax> Display APIS information for selected See Displaying Passengers with
passenger. APIS Information on page 3-27.

.APIS*<doc> Verify the selected document for the See Displaying Passengers with
passenger. APIS Information on page 3-27.

.APIS/BAD List all passengers who do not have See Displaying Passengers with
complete, valid APIS information. Missing APIS Information on
page 3-30.

.APPSOVR Display all APPS overrides on the current See Displaying APPS Overrides
flight. on page 3-33.

.B Display the baggage totals for a flight. See Displaying the Baggage
Count on page 10-4.

.B<pax> Display the baggage checked in for the See Displaying the Baggage
selected passenger. Checked In for a Passenger on
page 9-29.

.B/<bagtag Display the passenger information associated -

#> with the indicated bag.

.BA<pax> Display total baggage allowance for the See Displaying the Baggage
passenger. Allowance for a Passenger on
page 9-31.

Airport Check-in User Guide A–9

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Summary of Display Commands

Command Description Helpful References

.BD Display passengers with a balance due. See Displaying Passengers with
a Balance Due on page 3-38.

.BTP Display the bag tag printers. See Displaying Bag Tag Printers
on page 6-5.

.BZ<zone#> Display a list of passengers assigned to a -

boarding zone.

.C Display checked-in passengers on a flight. See Displaying Checked-in

Passengers on page 3-9.

.CU Display all passengers who have a customer See Displaying Passengers with
account associated with their reservation. Customer Accounts on page
3-33.

.D Display the downline passenger count for the See Displaying the Downline
currently loaded flight. Passenger Count on page 10-5.

.DEST<pax> Display all destination addresses for the See Displaying Destination
specified passenger. Addresses on page 9-13.
[New in 3.3.0
UPD 19]

.DN Display the downline passenger count for the See Displaying Downline
currently loaded flight along with individual Passengers on page 10-6.
passenger details.

.DOC Display passengers with passport or other See Displaying Passengers with
international document information. International Documents on
page 3-25.

.DOC<pax#> Display travel documents for a passenger. See Displaying Passengers with
International Documents on
page 3-25.

DOCS Display a list of valid international travel See Entering Travel Documents
documents for a passenger. on page 9-9.

.EC<pax#> Display emergency contact address for a See Displaying Passenger

passenger. Emergency Address.

.EXST Display all passengers with an extra seat -

assigned and EXST as the suffix.

F Display passengers on a flight, including See Displaying All Passengers on

confirmed and unconfirmed passengers. a Flight on page 3-3.
Depending on your airline settings, this
command may also display standby
passengers. See IncludeStandbyOnFind in
CheckinConfig.xml on page 1-3 for details.

Display all passengers on a flight, followed by See Displaying All Passengers on

the seat map by typing F,SM. a Flight on page 3-3.

Display all passengers on a flight whose See Displaying Passengers by

surname begins with what is typed after the Surname on page 3-9.
F command. For example, to display all
passengers whose surname begins with AN,
type FAN. Passengers with surnames such as
Anderson, Andreasen and so on are
returned.

A–10 Airport Check-in User Guide

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Summary of Display Commands

Command Description Helpful References

.FC<pax> Display full fare class for a passenger. When -

the class of service is more than two
characters, the passenger list shows the first
character followed by an asterisk (*).

.FF Display all other airline frequent flyer Maintaining Other Airline
accounts for a passenger. Frequent Flyer Information on
page 9-22.

.FI/<flight> Shortcut to Flight Information. See Appendix , Shortcut to

Flight Information, on page B-5.
.FI/<mkt>

.FR Display the status history of a flight, as well See Viewing the Status History
as any IROP comments entered for the flight of a Flight on page 10-15.
in Flight Following.

FYI Display the FYI notes if any exist. -

.GOVSTATUS Display passenger information and status See Using the .GOVSTATUS
according to the government security display command on page 3-31.
program applicable.

.I Display inbound, connecting passenger See Displaying the Inbound,

totals. Connecting Passenger Count on
page 10-9.

.IN Display inbound, connecting passenger totals See Displaying Inbound,

along with individual passenger details. Connecting Passengers on page
10-10.

L Display all outbound flights from a specific See Loading Flights from the
airport or all flights within a specific market. Flight List on page 2-9.

.L Display all passengers who are on a locked See Displaying Passengers on

PNR. Locked Reservations on page
3-35.

.L<pax> Display the match score detail for a See Displaying Passengers on
passenger on a locked PNR. Locked Reservations on page
3-35.

.LP Display all passengers who are associated See Displaying Passengers
with a loyalty program. Associated with Customer
Loyalty Programs on page 3-34.

.LP<pax> Display the loyalty program details for the See Displaying Passengers
selected passenger. Associated with Customer
Loyalty Programs on page 3-34.

.LP/<progra Display all passengers associated with the See Displaying Passengers
m code> selected loyalty program code. Associated with Customer
Loyalty Programs on page 3-34.

.M Display all passengers who have manifest See Displaying Passengers with
comments. Manifest Comments on page
3-20.

.M<pax> Display manifest comments for the selected See Displaying Manifest
passenger. Comments for a Passenger on
page 9-33.

Airport Check-in User Guide A–11

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Summary of Display Commands

Command Description Helpful References

.MC Display other marketing designators for a See Displaying Code Share
hosted flight. Passengers that are Associated
with Another Marketing
Designator on page 3-16.

.MC<line #> Display code share passengers associated See Displaying Code Share
with a particular marketing designator. Passengers that are Associated
with Another Marketing
Designator on page 3-16.

.N Display “no-show” passengers. See Displaying Passengers Who

Have Not Checked In on page
3-14.

.NS Display passengers without seat See Displaying Passengers Who

assignments. Do Not Have Assigned Seats on
page 3-15.

.P<pax> Display all passengers booked on the same See Displaying All Passengers on
reservation as the selected passenger by the Same Reservation on page
typing the command followed by the line 3-8.
number of the passenger.

For example, typing .P1 displays all

passengers on the same reservation as
passenger 1.

.PS Display all passengers with premium fares. See Displaying Passengers With
Premium Fares on page 3-20.

.Q Display passengers by sequence number or See Displaying Passengers by

boarding pass number. Sequence Number on page
3-35.

.QB Display all boarded passengers See Displaying Boarded

Passengers on page 3-13.

.QN Display all passengers who have checked in, See Displaying “Un-boarded”
but have not yet boarded. Passengers on page 3-13.

.S Display all standby passengers. See Displaying Standby

Passengers on page 3-10.

.SF/BAD List all passengers who require additional See Displaying Checked
Secure Flight validation. Passengers Who Require Secure
Flight Validation on page 3-30.

SM Display the seat map. See Displaying the Seat Map on

page 5-5.

SM<city> Displays the merged seat map for the See Merging Seat Maps for Thru
destination city. Flights on page 5-8.

.SSR Display all passengers who have SSRs. See Displaying Passengers with
SSRs on page 3-21.

.SSR<pax> Display the SSRs assigned to a passenger. See Displaying the SSRs
Assigned to a Passenger on page
9-34.

SSR Display all the valid SSR codes configured for See Displaying Valid SSR Codes
your airline. on page 10-14.

A–12 Airport Check-in User Guide

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Summary of Display Commands

Command Description Helpful References

STBY Display the standby priority codes configured See Displaying Valid Standby
for your airline. Priority Codes on page 10-13.

.T Displays all passengers who have thru flights See Displaying Thru Passengers
that stop in current airport. on page 3-17.

.TKT Displays all passengers who have tickets on See Displaying Passengers With
the current flight. Ticket Numbers on page 3-22.
[New in 3.4.5]

.U Display upgraded passengers. See Displaying Upgraded

Passengers on page 3-18.

U Display an updated passenger count. See Displaying the Passenger

Count on page 10-2.

.WL<pax> Display the match score detail and matching See Displaying Passengers on
watch list entry for a passenger on a locked Locked Reservations on page
PNR. 3-35.

.X Display inbound connecting passengers. See Displaying Connecting

Passengers on page 3-18.

.XDOC Display passengers without passport or other See Displaying Passengers

miscellaneous document information. without International
Documents on page 3-26.

.Z Shortcut to the Aircraft Zone report (23), See the SkyPort Reports User
which displays seating zone information and Guide.
passenger totals for a flight. To access this
report, agents must be assigned the “Aircraft
Zone Report (23)” permission in
Management Console (System Users >
Roles).

Airport Check-in User Guide A–13

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Summary of Commands by Task

Summary of Commands by Task

This section lists all of the commands used in Airport Check-in—including action and display
commands—organized by task. For example, you can view all commands related to baggage
check-in.
The commands are organized into the following categories:
• Flight Listing and Loading Commands on page A-15.
• Flight Opening/Closing Commands on page A-15.
• Passenger Display Commands on page A-17.
• Passenger Check-in Commands on page A-19.
• Seat Map/Seat Assignment Commands on page A-22.
• Itinerary and Boarding Pass Commands on page A-22.
• Baggage Commands on page A-23.
• Standby Passenger Commands on page A-23.
• Passenger Boarding Commands on page A-24.
• Passenger Information Commands on page A-24.
• Special Service Requests (SSRs) on page A-26.
• Infant and Child Commands on page A-26.
• Flight Information Commands on page A-26.
• Voucher Commands on page A-26.
• Shortcuts to Other Programs on page A-27.
• Miscellaneous Commands on page A-27.

A–14 Airport Check-in User Guide

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Summary of Commands by Task

Flight Listing and Loading Commands

Command/Combinations Example Description

L L L List all flights for the current airline on

the current date.

L/<airline code> L/1L List all flights for 1L on current date.

L<airport code> LSLC List all flights for the current airline that
originate at SLC.

L<airport code>/<airline LSLC/1L List all flights for 1L that originate at

code> SLC.

L<citypair> LSLCJFK List all flights between specified cities

for the current airline.

L<citypair>/<airline code> LSLCJFK/1L List all flights between specified cities

for 1L.

LF LF<citypair><flt#> LFSYDBNE203 Load flight with indicated parameters.

LF<citypair><flt#>/ LFSYDBNE203/1L Load flight with indicated parameters.

<airline code>

LF<date><citypair><flt#> LF04MAR03LAXSLC147 Load flight with indicated parameters.

LF<date><citypair><flt#> LF04MAR03LAXSLC147 Load flight with indicated parameters.

/<airline code> /1L

LL LL<flt#> LL203 Load indicated flight for the current

date.

LL<flt#>/<airline code> LL203/1L Load indicated flight for the current

date.

Flight Opening/Closing Commands

Command/Combinations Example Description

CF – – Close flight.

CP – – Set flight to “close pending”.

FLTVERIFY FLTVERIFY - Verify the currently loaded international

flight.

FLTVERIFY/F Verify the first valid document for any

boarded passenger on the currently
loaded international flight who does not
yet have a verified document. Then verify
the flight.
FLTVERIFYX
Remove the verification for the currently
loaded international flight.

.N – – Display no-show passengers.

OF – – Re-open a closed flight.

OP – – Open flight in “close pending” mode.

Airport Check-in User Guide A–15

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Summary of Commands by Task

Command/Combinations Example Description

PNRGOV PNRGOV/<country> PNRGOV/CA Send a complete PNRGOV message to CA

if required.
[New in PNRGOV/<PNR>
3.4.5] PNRGOV/GHT3M5 Send a PNRGOV message containing only
PNRGOV/<country>/
the PNR GHT3M5 to any government that
<PNR>
requires it.

PNRGOV/AU/ Send a PNRGOV message containing only

M8I78T PNR M8I787 to AU if required.

.QN – – Display checked-in, unboarded

passengers.

U – – Display passenger totals.

.XDOC – – Display pax without international docs.

A–16 Airport Check-in User Guide

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Summary of Commands by Task

Passenger Display Commands

Command/Combinations Example Description

.APC - - Display all passengers who are checked in

but do not have APPS clearance.

.APPSO - - Display all APPS overrides on the current

VR flight.

.APIS - - Display passengers with APIS information.

.APIS<pax#> .APIS3 Display APIS information for selected

passenger.

.APIS*<doc#> .APIS5245687 Verify information for selected document.

.APIS/BAD .APIS/BAD List all passengers who do not have APIS

information.

.BD – – Display passengers with a balance due.

.C – – Display checked-in passengers.

.CU – – Display passengers with customer account.

.D – – Display downline passenger counts.

.D,SM – Display downline passenger counts and

seat maps.

.DOC – – Display passengers with international docs.

F - – Display all passengers.

F<surname> FWOOD Display passengers by surname.

F,SM – Display all passengers and seat map.

F<surname>,SM FWOOD,SM Display passengers by surname, seat map.

.FC .FC<pax> .FC3 Display full fare class for the passenger on
line 3.

Note You must issue the F command to

display a passenger list before using this
command.

.GOVST - – Display passenger information and status

ATUS according to the government security
program applicable

.I – – Display inbound, cnx passenger totals.

.L - - List all passengers who are on locked PNRs.

.L<pax> .L1 Display match score details for a passenger

on a locked PNR.

.LP - - List all passengers who are associated with

customer loyalty programs.
.LP<pax> .LP1
List customer loyalty program details for
the selected passenger.
.LP/<program code> .LP/FRQ
List all passengers associated with the
selected customer loyalty program.

Airport Check-in User Guide A–17

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Summary of Commands by Task

Command/Combinations Example Description

.M – – Display pax with manifest comments.

.MC – – Display other marketing designators for the

current hosted flight.

.MC<line#> .MC1 Display all passengers associated with a

particular marketing designator.

Note These two variations of the .MC

command are intended to be run in
sequence. First list the designators, then
list the passengers for your chosen carrier.

.N – – Display no-show passengers.

.P - – Display passengers in special airline group.

.P<pax> .P1 Display all passengers on same PNR.

.PS - – Display passengers with premium seats.

.QB – – Display boarded passengers.

.QN – – Display checked-in, unboarded passengers.

.S – – Display standby passengers.

.SF .SF/BAD .SF/BAD Display passengers requiring Secure Flight

validation.

.SSR – – Display passengers with SSR codes.

.T – – Display “thru” passengers.

.TKT – – Display passengers with tickets.

[New in
3.4.6]

.U – – Display upgraded passengers.

.WL .WL<pax> .WL1 Display match score details and the

matching watch list entry for a passenger
on a locked PNR.

.X - – Display inbound, connecting passengers.

.X<flight #> .X100 Display inbound cnx pax from flight.

.X<airport code> .XLAX Display inbound cnx pax from airport.

.XDOC – Display pax without international docs.

.<seat #> .8A Display passenger in specified seat.

A–18 Airport Check-in User Guide

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Summary of Commands by Task

Passenger Check-in Commands

Command/Combinations Example Description

APC APC<pax> APC1 Gather APPS documents and send to

customs.

Note: The APC command is intended for

use by carriers who have APPS enabled for
a single country.

APIS APIS APIS Send the APIS report for the currently
loaded flight to the customs office of the
departure and/or arrival country.

APIS APISFINAL APISFINAL Verify all remaining passengers as well as

FINAL the currently loaded international flight
before sending the APIS report to the
customs office of the departure and/or
arrival country.

APIS APISPRE APISPRE Send a preliminary APIS report for the

PRE currently loaded flight to the customs office
of the departure and/or arrival country
even if some passengers are not verified.
The report contains only passengers who
are checked in and have a verified travel
document.

APPS - - Send APPS data for all passengers who

ALL have not yet cleared APPS.

Note: The APPSALL command is intended

for use by carriers who have APPS enabled
for a single country.

C C<pax> C1 Check in passenger.

C<pax>/<seat> C1/8A Check in passenger, assign seat.

CALL – Check in all confirmed passengers.

CL# CL#<pax> C1 Check in passenger.

C<pax>/<seat> C1/8A Check in passenger, assign seat.

CALL – Check in all confirmed passengers.

CS CS<pax> CS1 Check in standby passenger.

CS<pax>/<seat> CS1/8A Check in standby passenger, assign seat.

CSALL – Check in all standby passengers.

F - – Display all passengers.

F<surname> FWOOD Display passengers by surname.

F,SM – Display all passengers and seat map.

F<surname>,SM FWOOD,SM Display passengers by surname, seat map.

Airport Check-in User Guide A–19

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Summary of Commands by Task

Command/Combinations Example Description

MC MC<pax> MC1 Check in passenger 1 on a marketing code

share flight.

MC<pax>-<pax> MC1-3 Check in passengers 1-3 on a marketing

code share flight.

MCALL – Check in all confirmed passengers on a

marketing code share flight.

MCS MCS<pax> MCS1 Check in standby passenger on a

marketing code share flight.

MCS<pax>-<pax> MCS1-3 Check in standby passengers 1-3 on a

marketing code share flight.

MCSALL – Check in all standby passengers on a

marketing code share flight.

R R<pax> R1 Remove passenger from check-in.

RALL – Remove all passengers from check-in.

RMC RMC<pax> RMC1 Uncheck passenger 1 on a marketing code

share, outbound interline, or
third-party-controlled flight.

Uncheck passengers 1-3 on a marketing

RMC<pax>-<pax> RMC1-3
code share, outbound interline, or
third-party-controlled flight.
RMCALL –
Uncheck all confirmed passengers on a
marketing code share, outbound interline,
or third-party-controlled flight.

RMCS RMCS<pax> RMCS1 Uncheck standby passenger on a marketing

code share, outbound interline, or
third-party-controlled flight.
RMCS<pax>-<pax> RMCS1-3
Uncheck standby passengers 1-3 on a
marketing code share, outbound interline,
RMCSALL –
or third-party-controlled flight.

Uncheck all standby passengers on a

marketing code share, outbound interline,
or third-party-controlled flight.

RS RS<pax> RS1 Remove standby passenger from check-in.

RSALL – Remove all standby pax from check-in.

A–20 Airport Check-in User Guide

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Summary of Commands by Task

Command/Combinations Example Description

SEND SENDGOV<pax> SENDGOV1 Resubmit security data to all countries for a

GOV specific passenger.

Resubmit security data for a specific

SENDGOV<pax>/<2-char SENDGOV1/K
passenger to a specific country.
country code> R

Resubmit security data for all passengers

SENDGOVALL SENDGOVALL
on a flight.

SENDGOVALL/<2-char SENDGOVALL/
Resubmit security data to a specific country
country code> KR
for all passengers on a flight.

SENDGOVALL/<2-char SENDGOVALL/
Resubmit security data for all passengers in
country CA/OT
the manifest for the indicated country and
code>/<authorization
with the indicated status.
status>

- Resubmit security data for all passengers in

SENDGOVALL/manual
the manifest with a manual status during
outage mode.

SENDGOVALL/ Resubmit security data for all passengers in

SENDGOVALL/<2-char
CA/MANUAL the manifest for the indicated country who
country code>/MANUAL
have manual status.

SM – – Display seat map.

U – – Display passenger totals.

UN UNAPISPRE UNAPISPRE Send an unverified preliminary APIS report

APIS of the currently loaded flight to the
PRE UNAPSIPRE/<country code> UNAPSIPRE/R
customs office of the departure and/or
U
arrival country even if passengers are not
yet checked in nor verified. The report
[New contains all passengers.
in
3.4.1
1
UPD
6]

.C – – Display checked-in passengers.

.D – – Display downline passenger totals.

.N – – Display no-show passengers.

.P – – Display passengers in special airline group.

.P<pax> .P1 Display all passengers on same PNR.

.T – – Display “thru” passengers.

.X – – Display inbound, connecting passengers.

Airport Check-in User Guide A–21

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Summary of Commands by Task

Seat Map/Seat Assignment Commands

Command/Combinations Example Description

SA SA<pax>/<seat> SA1/8A Assign seat.

SM - – Display seat map.

SM<airport code> SMSLC Display seat map for destination airport.

Displays a merged seat map if airport is
final destination. If change of gauge, all
seat maps display.

ST ST<pax>/<seat> ST1/8A Assign seat for current leg of thru flight.

ST<pax>/<seat>/<dest> ST/8A/JFK Assign seat for the leg matching the flight
number and destination.

F F,SM – Display all passengers and seat map.

F<surname>,SM FWOO,SM Display passengers by surname, seat map.

H H<seat> H8A Hold seat.

BS BS<seat> BS8A Block seat.

US US<seat> US8A Un-block seat.

.PS – – Display passengers with premium seats.

.T – – Display “thru” passengers.

Itinerary and Boarding Pass Commands

Command/Combinations Example Description

GP GP GP Print gate pass to boarding pass printer.

GP<pax> GP1 Print gate pass for a person associated with

the passenger on line 1.

II II<pax> II1 Print itinerary receipt to boarding pass

printer.

IT IT<pax>/<printer code> IT1/SLCPRN1 Reprint itinerary.

BP BP<pax>/<printer> BP1/1400 Re-print boarding pass.

BRD BRD | <sequence #> BRD | 1 Board passenger.

BRD | <sequence #>X BRD | 1X Un-board passenger.

A–22 Airport Check-in User Guide

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Summary of Commands by Task

Baggage Commands

Command/Combinations Example Description

.B – – Display baggage totals.

.B<pax> .B1 Display checked-in baggage for passenger.

.B/<bagtag #> .B/ Display information about the passenger

0999000014 associated with bag 0999000014 on the
current flight.

.BA .BA<pax> .BA1 Display total baggage allowance for the

passenger.

Q Q<3-digit sequence Q1231234JFK Manually enter boarding pass information

number><4-digit flight to print bag tags. Both the 3-digit sequence
number><departure station number and the 4-digit flight number are
(optional)> padded with zeros if necessary.

.BTP – – Display available bag tag printers.

CW CW<bag line #>/<new CW1/25 Change the weight of the bag on line one to
weight> 25.

BTP BTP/<printer #> BTP/1 Select bag tag printer.

B B<pax> B1 Check in baggage.

BT BT<pax> BT1 Print bag tags for the selected passenger.

Standby Passenger Commands

Command/Combinations Example Description

CS CS<pax> CS1 Check in standby passenger.

CS<pax>/<seat> CS1/8A Check in standby passenger, assign seat.

CSALL – Check in all standby passengers.

RS RS<pax> RS1 Remove standby passenger from check-in.

RSALL – Remove all standby passengers from

check-in.

.S – – Display standby passengers.

S S<pax>/<priority code> S1/B1 Change the standby priority code of

passenger 1 to “B1”.

STBY – – Display valid standby priority codes.

U – – Display passenger totals.

Airport Check-in User Guide A–23

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Summary of Commands by Task

Passenger Boarding Commands

Command/Combinations Example Description

BRD BRD | <sequence #> BRD | 1 Board passenger.

BRD | <sequence #>X BRD | 1X Un-board passenger.

BRD | ALL – Board all passengers.

BRD | ALLX – Un-board all passengers.

BP BP/<pax> BP/1 Re-print boarding pass for selected pax.

.BZ .BZ<zone#> .BZ1 Display a list of passengers assigned to a

boarding zone.

.QB – – Display boarded passengers.

.QN – – Display checked-in, unboarded passengers.

U – – Display passenger totals.

Passenger Information Commands

Command/Combinations Example Description

BD BD<pax>/<birthdate> BD1/17MAR20 Enter birthdate for passenger.

00

CU CU<pax>/<Customer ID> CU1/1234567 Create association between passenger and

8910 customer account.

CU<pax>/R CU1/R Remove association between passenger

and customer account.

DEST DEST<pax> DEST1 Add a destination address for the

passenger on line 1.
[New in
3.3.0
UPD 19]

.DEST .DEST<pax> .DEST1 Display all destination addresses for the

passenger on line 1.
[New in
3.3.0
UPD 19]

.DEST* .DEST*<address> .DEST*1 Modify the address on line 1 for the current
passenger.
[New in
3.3.0
UPD 19]

DOC DOC<pax> DOC1 Enter travel document info for passenger.

.DOC .DOC<pax> .DOC1 View travel document info for passenger.

.DOC* .DOC*<doc> .DOC*1 Modify info for first travel document.

DOCS DOCS<pax> DOCS1 Display a list of all valid travel document

types for passenger.

A–24 Airport Check-in User Guide

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Summary of Commands by Task

Command/Combinations Example Description

DOCX DOCX<doc> DOCX1 Delete the first document for a passenger.

.EC<pax - .EC1 Display the emergency contact address for

#> a passenger.

EC<pax - EC1 Add an emergency contact address for a

#> passenger.

.EC*<p - .EC*1 Modify the existing emergency contact

ax#> address for a passenger.

.ECX<p - .ECX1 Delete an existing emergency contact

ax#> address for a passenger.

.FF .FF<pax> .FF1 Display other airline frequent flyer

information for a passenger.

FF FF<pax> FF1 Add other airline frequent flyer information

for a passenger.

FF/R FF<line#>/R FF1/R Remove a customer’s other airline frequent

flyer number.

FF* FF*<line#> FF*1 Modify a specific other airline frequent flyer

account for a passenger.

LP LP<pax>/<program LP1/FRQ/1234 Associate a passenger with a customer

code>/<account #> 56789 loyalty program.

LP<pax>/R LP1/R Remove the association between the

selected passenger and the customer
loyalty program.

J J<pax> J1 Change passenger title to “CHD.”

N N*<pax> N*1 Modify passenger name and title.

.M .M – Display pax with manifest comments.

.M<pax> .M1 Display manifest comments for passenger.

PNRGOV PNRGOV/<country> PNRGOV/CA Send a complete PNRGOV message to CA if

required.
[New in PNRGOV/<PNR>
3.4.5] PNRGOV/ Send a PNRGOV message containing only
PNRGOV/<country>/
GHT3M5 the PNR GHT3M5 to any government that
<PNR>
requires it.

Send a PNRGOV message containing only

PNRGOV/AU/ PNR M8I787 to AU if required.
M8I78T

SSR SSR – Display passengers with SSRs.

SSR<pax>/<SSR code> SSR1/PET Assign SSR to passenger.

SSR<pax>/<SSR SSR1/PET/R Remove SSR from passenger.

code>/R

.SSR – – Display valid SSR codes.

.<seat #> .8A Display passenger with specified seat.

Airport Check-in User Guide A–25

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Summary of Commands by Task

Special Service Requests (SSRs)

Command/Combinations Example Description

SSR SSR – Display passengers with SSRs.

SSR<pax>/<SSR code> SSR1/PET Assign SSR to passenger.

SSR<pax>/<SSR code>/R SSR1/PET/R Remove SSR from passenger.

.SSR – – Display valid SSR codes.

.SSR<pax> .SSR1 Display SSRs assigned to pax.

Infant and Child Commands

Command/Combinations Example Description

J J<pax> J1 Change passenger title to “CHD.”

Flight Information Commands

Command/Combinations Example Description

.FI .FI/<flight #> .FI/100 Display status information for flight 100 for
the current airline.

.FI/<city pair> .FI/SLCATL Display status info for this market for the
current airline.

.FR – – Display status history and IROP remarks.

.Z – – Shortcut to Aircraft Zone report (23).

Voucher Commands

Command/Combinations Example Description

V V<pax>/<voucher code> V1/VCHR Issue a voucher of type VCHR for

passenger 1.

VALL VALL/<voucher code> VALL/VCHR Issue vouchers of type VCHR for each
passenger on a flight.

A–26 Airport Check-in User Guide

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Summary of Commands by Task

Shortcuts to Other Programs

Command/Combinations Example Description

>BAG – – Shortcut to Baggage Check-in.

TAG

GS – – Shortcut to General Reference.

IROP – – Shortcut to Irregular Operations.

OPS – – Shortcut to Flight Following.

RZ – – Shortcut to Reservations tool (RZ).

.Z – – Shortcut to Aircraft Zone report (23).

Miscellaneous Commands

Command/Combinations Example Description

CLS – – Clear data on screen.

HELP – – Access online Help.

MD – – Move down.

MU – – Move up.

U – – Display passenger totals.

Airport Check-in User Guide A–27

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Command Combinations

Command Combinations
In many cases, a single command is all you need to perform a task. For example, CLS clears the
screen. However, some tasks require command combinations. For example, to check in the
passenger on line 1 and assign seat 8A, you must enter C1/8A. This section describes any
combinations that may be required for specific commands.
The commands that require combinations include the following:

Command Combinations

• AB Command on page A-29 • LF Command on page A-39

• .B Command on page A-29 • .LP Command on page A-39

• B Command on page A-29 • LP Command on page A-40

• BD Command on page A-30 • .M Command on page A-40

• BP Command on page A-30 • MB Command on page A-40

• BRD Command on page A-31 • MC Command on page A-41

• BS Command on page A-31 • MCS Command on page A-41

• BTP Command on page A-32 • PNRGOV Command on page A-42

• C Command on page A-32 • .Q Command on page A-43

• CS Command on page A-34 • R Command on page A-43

• CU Command on page A-35 • RB Command on page A-44

• .DOC Command on page A-35 • RS Command on page A-45

• F Command on page A-36 • RZ Command on page A-46

• .FI Command on page A-36 • SA Command on page A-46

• H Command on page A-37 • SM Command on page A-47

• IT Command on page A-37 • SSR Command on page A-48

• J Command on page A-38 • US Command on page A-49

• L Command on page A-38 • .X Command on page A-49

A–28 Airport Check-in User Guide

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Command Combinations

AB Command
The AB command enables you to check in baggage. See Chapter 6, Checking In Baggage.

Element Description

Combinations... AB<pax>

AB<pax> Check in baggage for the indicated passenger. For example, to

check in baggage for the passenger on line 1, enter AB1.

This command works for both automated bag tag printing and
pre-printed bag tags.

.B Command
The .B command displays the baggage totals for a flight. When combined with a passenger
number, this command displays the baggage checked in for a passenger. See Displaying the
Baggage Count on page 10-4 and Displaying the Baggage Checked In for a Passenger on page 9-29.

Element Description

Combinations... • .B

• .B<pax>

.B Display the baggage totals for a flight, including the number of

checked bags, thru bags, standby bags, and total number of bags.

For more information on displays the baggage totals for a flight,

see Displaying the Baggage Count on page 10-4.

.B<pax> Display the baggage checked in for a passenger. For example, to

display the baggage checked in for the passenger on line 1, enter
.B1.

For each bag, you can view the bag tag number, baggage weight,
check-in status, final destination, and so on.

For more information on displaying the baggage checked in for a

passenger, see Displaying the Baggage Checked In for a Passenger
on page 9-29.

.B/<bagtag #> Search the current flight for the indicated bag. For example, to
determine which passenger is associated with bag 0999000014,
first load the correct flight. Then type .B/0999000014. The
passenger information displays.

B Command
The B command enables you to check in baggage. See Chapter 6, Checking In Baggage.

Element Description

Combinations... B<pax>

Airport Check-in User Guide A–29

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Command Combinations

Element Description

B<pax> Check in baggage for the indicated passenger. For example, to

check in baggage for the passenger on line 1, enter B1.

This command works for both automated bag tag printing and
pre-printed bag tags.

BD Command
The BD command enables you to enter birthdates for passengers. See Entering Birthdates on page
9-21.

Element Description

Combinations... BD<pax>/<birthdate>

BD<pax>/<birthdate> For example, if the birthdate is 17 March 2000 for the passenger
on line 1, you would enter BD1/17MAR2000. Use the date format
DDMMMYYYY.

BP Command
The BP command enables you to re-print boarding passes. See Re-printing Boarding Passes on
page 4-39.

Element Description

Combinations... BP<pax>

BP<pax> Re-print boarding passes for the passengers on the indicated lines.
For the <pax> entry, use any of the following combinations:

• <pax>

For example, enter BP1 to select the passenger on line 1.

• <pax>-<pax>

For example, enter BP1-3 to select the passengers on lines 1,

2, and 3.

A–30 Airport Check-in User Guide

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Command Combinations

BRD Command
The BRD command enables you to board and un-board passengers. See Chapter 7, Boarding
Passengers.

Element Description

Combinations... • BRD | <sequence #>

• BRD | ALL

• BRD | <sequence #>X

• BRD | ALLX

BRD | <sequence #> Board the passenger with the indicated sequence number. For
example, to board the passenger whose sequence number is 40,
enter BRD, and then enter 40.

BRD | ALL Board all passengers on the flight (enter BRD, and then enter
ALL).

BRD | <sequence #>X Unboard the passenger with the indicated sequence number. For
example, to unboard the passenger whose sequence number is 40,
enter BRD, and then enter 40X.

BRD | ALLX Unboard all passengers on the flight (enter BRD, and then enter
ALLX).

BS Command
The BS command enables you to block seats on an aircraft. For thru flights, you can block a seat
for the currently loaded leg or for all legs of the flight. See Holding or Blocking Seats on page 5-13.

Element Description

Combinations... • BS<seat #>

• BS<seat #>/<final destination>

BS<seat #> Block the indicated seats on the aircraft. You must enter an exact
seat number, such as 8A (you cannot enter Window or Aisle). For
thru flights, this command blocks the seat for the currently loaded
leg only.

For the <seat #> entry, you can use any of the following
combinations:

• <seat #>

For example, enter BS8A to block seat 8A.

• <seat #>-<seat #>

For example, enter BS8A-8D to block seats 8A, 8B, 8C and 8D.

Airport Check-in User Guide A–31

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Command Combinations

Element Description

BS<seat #>/<final Block the indicated seats for all legs of a thru flight to the final
destination> destination. You must enter an exact seat number, such as 8A (you
cannot enter Window or Aisle).

For example, to block seat 8A on all legs of the currently loaded

flight to SLC, enter BS8A/SLC. To block seats 8A through 8D on all
legs to SLC, enter BS8A-8D/SLC.

BTP Command
The BTP command enables you to select a bag tag printer. See Selecting a Bag Tag Printer on page
6-6.

Element Description

Combinations... • BTP/<printer>

BTP/<printer> Select the bag tag printer on the indicated line. For example, to
select the bag tag printer on line 1, enter BTP/1.

For this command to work, you must first display the available bag
tag printers (.BTP command).

C Command
The C command enables you to check in confirmed (HK) passengers on a flight. You can check in
(1) one passenger at a time, (2) all passengers booked on the same reservation, and (3) all
passengers on a flight.
See Checking In Confirmed Passengers Individually or by PNR on page 4-5 and Checking In All
Confirmed Passengers on page 4-7.

Element Description

Combinations... • C<pax>

• C<pax>/<seat>

• CALL

C<pax> For confirmed passengers who already have a seat assignment,

use this command to check in the indicated passengers. For
example, to check in the passenger on line 1, enter C1.

You can check in passengers booked on the same reservation at

the same time using the C<pax>-<pax> command. For example,
to check in the passengers on lines 1–4, enter C1-4.

A–32 Airport Check-in User Guide

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Command Combinations

Element Description

C<pax>/<seat> For confirmed passengers who do not have a seat assignment, use
this command to check in the indicated passengers and assign
seats. For example, to check in the passenger on line 1 and assign
seat 8A, enter C1/8A.

You can check in passengers booked on the same reservation at

the same time using the C<pax>-<pax>/<seat #> command.
For example, to check in the passengers on lines 1–4 and assign
seats sequentially where possible, beginning with seat 8A, enter
C1-4/8A. To check in the passengers on lines 1–4 and assign
window seats where possible, enter C1-4/W.

For the <seat> entry, you can enter any of the following:

• W(indow). Assigns the next available window seat. For

example, SA1/W.

• A(isle). Assigns the next available aisle seat. For example,

SA1/A.

• N(o preference). Assigns the next available seat. For example,

SA1/N.

• <seat #> – Assigns the specified seat number. For example,

SA1/8A.

• * – Bypasses the seat assignment requirement. For example,

SA1/*.

CALL For airlines who do not use the Airport Check-in system from
Navitaire, use this command to check in all confirmed passengers
on the flight. This command does not assign seats; however, every
passenger is issued a sequence number for boarding.

Airport Check-in User Guide A–33

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Command Combinations

CS Command
The CS command enables you to check in standby (HL) passengers on a flight. You can check in
(1) one standby passenger at a time, (2) all standby passengers booked on the same reservation,
and (3) all standby passengers on a flight.
See Checking In Standby Passengers Individually or by PNR on page 4-7 and Checking In All
Standby Passengers on page 4-9.

Element Description

Combinations... • CS<pax>

• CS<pax>/<seat>

• CSALL

CS<pax> For standby passengers who already have a seat assignment, use
this command to check in the indicated passengers. For example,
to check in the standby passenger on line 1, enter CS1.

You can check in passengers booked on the same reservation at

the same time using the C<pax>-<pax> command. For example,
to check in the standby passengers on lines 1–4, enter CS1-4.

CS<pax>/<seat> For standby passengers who do not have a seat assignment, use
this command to check in the indicated passengers and assign
seats. For example, to check in the standby passenger on line 1
and assign seat 8A, enter CS1/8A.

You can check in passengers booked on the same reservation at

the same time using the C<pax>-<pax>/<seat #> command.
For example, to check in the standby passengers on lines 1–4 and
assign seats sequentially where possible, beginning with seat 8A,
enter CS1-4/8A. To check in the standby passengers on lines 1–4
and assign window seats where possible, enter CS1-4/W.

For the <seat> entry, you can enter any of the following:

• W(indow). Assigns the next available window seat. For

example, SA1/W.

• A(isle). Assigns the next available aisle seat. For example,

SA1/A.

• N(o preference). Assigns the next available seat. For example,

SA1/N.

• <seat #> – Assigns the specified seat number. For example,

SA1/8A.

• * – Bypasses the seat assignment requirement. For example,

SA1/*.

CSALL For airlines who do not use the Airport Check-in system from
Navitaire, use this command to check in all standby passengers on
the flight. This command does not assign seats; however, every
passenger is issued a sequence number for boarding.

A–34 Airport Check-in User Guide

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Command Combinations

CU Command
The CU command enables you to create and remove customer account associations. See
Associating Passenger Names with Customer Accounts on page 9-25 and Removing Customer
Account Associations on page 9-26.

Element Description

Combinations... • CU<pax>/<Customer ID>

• CU<pax>/R

CU<pax>/<Customer ID> Associate the passenger with the indicated customer account. For
example, to associate the passenger on line 1 with Customer ID
#12134567890, enter CU1/1234567890.

Customer IDs always contain ten digits.

CU<pax>/R Remove the association between the passenger and their customer
account. For example, to remove the association between the
passenger on line 1 and their customer account, enter CU1/R.

.DOC Command
The .DOC command enables you to display passengers with international documents such as
passports, visas, and so on as well as view and modify document information.

Element Description

Combinations... • .DOC

• .DOC<pax>

• .DOC*<doc>

.DOC Display passengers who have passports, visas, or other

international documents. See Displaying Passengers with
International Documents on page 3-25.

.DOC<pax> Display the international document details for the passenger on

the indicated line. For example, to display the document details for
the passenger on line 1, enter .DOC1. See Displaying Passengers
with International Documents on page 3-25.

.DOC*<doc> Modify the international document details for the document on the
indicated line. For example, to modify the details for the document
on line 1, enter .DOC*1. See Modifying Travel Documents on page
9-11.

Airport Check-in User Guide A–35

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Command Combinations

F Command
The F command displays all passengers on a flight, including confirmed and unconfirmed
passengers. Depending on your airline settings, this command may also display standby
passengers. See Chapter 3, Displaying Passenger Lists.

Element Description

Combinations... • F

• F<surname>

• F,SM

• F<surname>,SM

F Display all passengers on a flight, including confirmed and

unconfirmed passengers. Depending on your airline settings, this
command may also display standby passengers.

For more information on displaying all passengers on a flight, see

Displaying All Passengers on a Flight on page 3-3.

F<surname> Display passengers on the flight, filtered by surname. You may

enter one to all of the characters of the surname to view. For
example, to display all passengers whose surname begins with
“WOOD,” enter FWOOD.

This may be helpful when you have a flight with dozens of

passengers; if you filter passengers by surname, the system
displays fewer passengers in the passenger list.

For more information on filtering passengers by surname, see

Displaying Passengers by Surname on page 3-9.

F,SM Display all passengers on the flight and the seat map.

F<surname>,SM Display passengers on the flight filtered by surname and the seat
map. For example, to display all passengers whose surname
begins with “WOOD” and the seat map, enter FWOOD,SM.

.FI Command
The .FI command displays a consolidated version of the flight status information entered in
SkySchedule and Flight Following. Basically, this command is a shortcut to Flight Information.
See Shortcut to Flight Information on page B-5.

Element Description

Combinations... • .FI/<flight #>

• .FI/<city pair>

.FI/<flight #> Display status information for all legs of the indicated flight on the
most recently loaded flight’s carrier. For example, to view status
information for all legs of flight 123, enter .FI/123.

A–36 Airport Check-in User Guide

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Command Combinations

Element Description

.FI/<city pair> Display status information for all non-stop flights on the most
recently loaded flight’s carrier between the indicated city pair. For
example, to view status information for all non-stop flights
between SLC and JFK, enter .FI/SLCJFK.

H Command
The H command enables you to hold seats. See Holding or Blocking Seats on page 5-13.

Element Description

Combinations... • H<seat #>

• H<seat #>/<final destination>

H<seat #> Hold the indicated seats on the aircraft. You must enter an exact
seat number, such as 8A (you cannot enter Window or Aisle).

For the <seat #> entry, you can use any of the following
combinations:

• <seat #>

For example, enter H8A to hold seat 8A.

• <seat #>-<seat #>

For example, enter H8A-8D to hold seats 8A, 8B, 8C, and so
on, through seat 8D.

H<seat #>/<final Hold the indicated seats for all legs of a thru flight to the final
destination> destination. You must enter an exact seat number, such as 8A (you
cannot enter Window or Aisle).

For example, to hold seat 8A on all legs of the currently loaded

flight to SLC, enter H8A/SLC. To hold seats 8A through 8D on all
legs to SLC, enter H8A-8D/SLC.

IT Command
The IT command enables you to reprint itineraries. See Re-printing Itineraries on page 4-39.

Element Description

Combinations... IT<pax>/<printer code>

Airport Check-in User Guide A–37

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Command Combinations

Element Description

IT<pax>/<printer code> Re-print an itinerary for the passengers on the indicated lines and
send to the selected printer. For the <pax> entry, you can use any
of the following combinations:

• <pax>

For example, enter IT1 to select the passenger on line 1.

• <pax>-<pax>

For example, enter IT1-3 to select the passengers on lines 1,

2, and 3.

The <printer code> is configured for printers in Printer

Maintenance. It is the same printer code you use to print reports.

J Command
The J command changes the passenger title of a selected passenger to “CHD.” This does not
change the passenger type to “child”; rather, it simply changes the passenger title to CHD (just
like adding MR or MRS to a passenger name). See Changing a Passenger Title to “CHD” on page
9-5.

Element Description

Combinations... J<pax>

J<pax> Change the passenger title of the selected passenger to “CHD.” For
example, to change the passenger title of the passenger on line 1
to “CHD,” enter J1.

L Command
The L command enables you to list all flights from a specific airport or between a specific market.
See Loading Flights from the Flight List on page 2-9.

Element Description

Combinations... • L

• L/<airline code>

• L<airport code>

• L<airport code>/<airline code>

• L<market>

• L<market>/<airline code>

L List all flights for all markets on the current carrier.

L/<airline code> List all flights for all markets on the specified carrier.

A–38 Airport Check-in User Guide

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Command Combinations

Element Description

L<airport code> List all flights that originate from the specified airport for the
current carrier.

L<airport code>/<airline List all flights that originate from the specified airport for the
code> specified carrier.

L<market> List all flights between the specified cities for the current carrier.

L<market>/<airline List all flights between the specified cities for the specified carrier.
code>

LF Command
The LF command enables you to load flights. See Chapter 2, Loading Flights.

Element Description

Combinations... LF<departure date><market><flight #>/<airline code>

LF<departure date> Load the specified flight for the current carrier on the Passenger
<market><flight Count screen. For example, to load flight 147 from LAX to SLC on 4
#>/<airline code> March 2003, enter LF24MAR04LAXSLC147/1L.

If the flight is on the current calendar day, you do not need to

enter the date, as in LFLAXSLC147/1L.

If the flight is on the same carrier as the most recently loaded

flight, you do not need to enter the carrier code, as in
LF24MAR04LAXSLC147.

For more information on the Passenger Count screen, see

Displaying the Passenger Count on page 10-2.

.LP Command
The .LP command enables you to display customer loyalty program information for one or more
passengers. See Chapter 3, Displaying Passenger Lists.

Element Description

Combinations... • .LP<pax>

• .LP/<program code>

.LP<pax> Display the loyalty program details for the selected passenger.

.LP/<program code> Display all passengers associated with the selected loyalty
program. For example, .LP/FRQ displays a list of passengers who
are associated with the FRQ customer recognition program.

Airport Check-in User Guide A–39

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Command Combinations

LP Command
The LP command enables you to create or remove an association between a passenger and a
customer loyalty program. See Chapter 3, Displaying Passenger Lists.

Element Description

Combinations... • LP<pax>/<program code>/<account #>

• LP<pax>/R

LP<pax>/<program Associates the passenger with the given customer loyalty program
code>/<account #> using the account number entered. For example, to associate
passenger 1 with the FRQ loyalty program, account 123456789,
enter LP1/FRQ/123456789.

LP<pax>/R Removes the association between the selected passenger and the
customer loyalty account.

.M Command
The .M command enables you to display manifest comments. See Displaying Passengers with
Manifest Comments on page 3-20.

Element Description

Combinations... • .M

• .M<pax>

.M Display all passengers who have manifest comments.

.M<pax> Display the manifest comments for the passenger on the indicated
line. For example, to display the manifest comments for the
passenger on line 1, enter .M1.

MB Command
The MB command enables you to check in baggage. See Chapter 6, Checking In Baggage.

Element Description

Combinations... MB<pax>

MB<pax> Check in baggage for the indicated passenger. For example, to

check in baggage for the passenger on line 1, enter MB1.

This command does not work for automatic bag tag printing; it
only works for pre-printed bag tags.

A–40 Airport Check-in User Guide

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Command Combinations

MC Command
The MC command enables you to check in confirmed (HK) passengers on a marketing code
share, outbound interline, or DCS-controlled flight. You can check in (1) one passenger at a time, (2)
all passengers booked on the same reservation, and (3) all passengers on the flight.
See Checking and Unchecking Confirmed Passengers Individually on a Marketing Code Share,
Outbound Interline, or Third-Party-Controlled Flight on page 4-31 and Checking and Unchecking All
Confirmed Passengers on a Marketing Code Share, Outbound Interline, or Third-Party-Controlled
Flight on page 4-32.

Element Description

Combinations... • MC<pax>

• MC<pax>-<pax>

• MCALL

MC<pax> Use this command to check in one confirmed passenger. For

example, to check in the passenger on line 1, enter MC1.

MC<pax>-<pax> You can check in passengers booked on the same reservation at

the same time using the MC<pax>-<pax> command. For
example, to check in the passengers on lines 1–4, enter MC1-4.

MCALL Use this command to check in all confirmed passengers on the

flight. Every passenger is issued a sequence number for boarding.

MCS Command
The MCS command enables you to check in standby (HL) passengers on a marketing code share,
outbound interline, or DCS-controlled
flight. You can check in (1) one standby passenger at a time,
(2) all standby passengers booked on the same reservation, and (3) all standby passengers on a
flight.
See Checking and Unchecking Standby Passengers Individually on a Marketing Code Share,
Outbound Interline, or Third-Party-Controlled Flight on page 4-32 and Checking and Unchecking All
Standby Passengers on a Marketing Code Share, Outbound Interline, or Third-Party-Controlled
Flight on page 4-33.

Element Description

Combinations... • MCS<pax>

• MCS<pax>-<pax>

• MCSALL

MCS<pax> Use this command to check in one standby passenger. For

example, to check in the standby passenger on line 1, enter MCS1.

MCS<pax>-<pax> You can check in passengers booked on the same reservation at

the same time using the MC<pax>-<pax> command. For
example, to check in the standby passengers on lines 1–4, enter
MCS1-4.

Airport Check-in User Guide A–41

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Command Combinations

Element Description

MCSALL Use this command to check in all standby passengers on the flight.
Every passenger is issued a sequence number for boarding.

PNRGOV Command
The PNRGOV command enables you to send PNR information to governments that requires it for
security. You can send PNRGOV messages to the origin or destination country of the currently
loaded flight.
Note New Skies sends PNRGOV messages only to governments that use PNRGOV.

See Sending PNRGOV Messages on page 4-19.

Element Description

Combinations... • PNRGOV

• PNRGOV/<country code>

• PNRGOV/<PNR>

• PNRGOV/F

• PNRGOV/F/<country code>

• PNRGOV/F/<PNR>

• PNRGOV/<country code>/<PNR>

• PNRGOV/F/<country code>/<PNR>

PNRGOV Use this command to send PNR data to all countries that are part
of the currently loaded flight’s path and require PNRGOV
messaging. For example, to send all PNR data to all countries that
require it, enter PNRGOV.

PNRGOV/<country code> Use this command to send PNR data for the currently loaded flight
to either the origin or the destination of the current flight. For
example, if the current flight originates in Australia and ends in
Canada and you want to send a PNRGOV message only to Canada,
enter PNRGOV/CA.

PNRGOV/<PNR> This command sends only data for a particular PNR. For example,
to send data for the PNR JFQ7Y8 to the countries that require it,
enter PNRGOV/JFQ7Y8.

PNRGOV/F Use this command to send PNR data to all countries that are part
of the currently loaded flight’s path and require PNRGOV
messaging. For example, to send all PNR data to all countries that
require it, enter PNRGOV/F.

Note The F option is not currently supported and is ignored.

PNRGOV/F/<country Use this command to send PNR data for the currently loaded flight
code> to either the origin or the destination of the current flight. For
example, if the current flight originates in Australia and ends in
Canada and you want to send a PNRGOV message only to Canada,
enter PNRGOV/F/CA.

Note The F option is not currently supported and is ignored.

A–42 Airport Check-in User Guide

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Command Combinations

Element Description

PNRGOV/F/<PNR> This command sends only data for a particular PNR. For example,
to send data for the PNR JFQ7Y8 to the countries that require it,
enter PNRGOV/F/JFQ7Y8.

Note The F option is not currently supported and is ignored.

PNRGOV/<country This command sends only data for a particular PNR and only to the
code>/<PNR> specified country. For example, to send data for the PNR JFQ7Y8 to
Canada only, enter PNRGOV/CA/JFQ7Y8.

PNRGOV/F/<country This command sends only data for a particular PNR and only to the
code>/<PNR> specified country. For example, to send data for the PNR JFQ7Y8 to
Canada only, enter PNRGOV/F/CA/JFQ7Y8.

Note The F option is not currently supported and is ignored.

.Q Command
The .Q command enables you to display passengers by sequence number. See Displaying
Passengers by Sequence Number on page 3-35.

Element Description

Combinations... • .Q<sequence #>

.Q<sequence #> Display the passenger assigned the indicated sequence number.
For example, to display the passenger assigned sequence #1,
enter .Q1.

R Command
The R command enables you to remove passengers from check-in. See Removing Passengers from
Check-in on page 4-35.

Element Description

Combinations... • R<pax>

• RALL

R<pax> Remove the specified confirmed passenger from check-in. For the
<pax> entry, you can use any of the following combinations:

• <pax>

For example, to remove the confirmed passenger on line 1

from check-in, enter R1.

• <pax>-<pax>

For example, to remove the confirmed passengers on lines 1-3

from check-in, enter R1-3.

RALL Remove all passengers on a flight from check-in.

Airport Check-in User Guide A–43

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Command Combinations

RB Command
The RB command enables you to remove baggage from check-in. See Removing Baggage from
Check-in on page 6-15.

Element Description

Combinations... RB<pax>/<bag>

RB<pax>/<bag> Remove baggage from check-in for the indicated passenger. For
example, to remove the bag on line 3 for the passenger on line 1,
enter RB1/3.

For this command to work, you must first display the passenger
and then display the baggage for the passenger using the .B
command.

RMC Command
The RMC command enables you to uncheck confirmed (HK) passengers on a marketing code
share, outbound interline, or DCS-controlled flight. You can uncheck (1) one passenger at a time, (2)
all passengers booked on the same reservation, and (3) all passengers on the flight.
See Checking and Unchecking Confirmed Passengers Individually on a Marketing Code Share,
Outbound Interline, or Third-Party-Controlled Flight on page 4-31 and Checking and Unchecking All
Confirmed Passengers on a Marketing Code Share, Outbound Interline, or Third-Party-Controlled
Flight on page 4-32.

Element Description

Combinations... • RMC<pax>

• RMC<pax>-<pax>

• RMCALL

RMC<pax> Use this command to uncheck one confirmed passenger. For

example, to check in the passenger on line 1, enter MC1.

RMC<pax>-<pax> You can uncheck passengers booked on the same reservation at

the same time using the MC<pax>-<pax> command. For
example, to uncheck the passengers on lines 1–4, enter MC1-4.

RMCALL Use this command to uncheck all confirmed passengers on the

flight.

RMCS Command
The RMCS command enables you to uncheck standby (HL) passengers on a marketing code
share, outbound interline, or DCS-controlled flight. You can uncheck (1) one standby passenger at a
time, (2) all standby passengers booked on the same reservation, and (3) all standby passengers
on a flight.
See Checking and Unchecking Standby Passengers Individually on a Marketing Code Share,
Outbound Interline, or Third-Party-Controlled Flight on page 4-32 and Checking and Unchecking All

A–44 Airport Check-in User Guide

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Command Combinations

Standby Passengers on a Marketing Code Share, Outbound Interline, or Third-Party-Controlled

Flight on page 4-33.

Element Description

Combinations... • RMCS<pax>

• RMCS<pax>-<pax>

• RMCSALL

MCS<pax> Use this command to uncheck one standby passenger. For

example, to uncheck the standby passenger on line 1, enter
RMCS1.

MCS<pax>-<pax> You can uncheck passengers booked on the same reservation at

the same time using the RMC<pax>-<pax> command. For
example, to uncheck the standby passengers on lines 1–4, enter
RMCS1-4.

MCSALL Use this command to uncheck all standby passengers on the flight.

RS Command
The RS command enables you to remove standby passengers from check-in. See Removing
Passengers from Check-in on page 4-35.

Element Description

Combinations... • RS<pax>

• RSALL

RS<pax> Remove the specified standby passenger from check-in. For the
<pax> entry, you can use any of the following combinations:

• <pax>

For example, to remove the standby passenger on line 1 from

check-in, enter RS1.

• <pax>-<pax>

For example, to remove the standby passengers on lines 1-3

from check-in, enter RS1-3.

RSALL Remove all standby passengers on a flight from check-in.

Airport Check-in User Guide A–45

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Command Combinations

RZ Command
The RZ command is a “shortcut” to the Reservations tool (RZ). See Shortcut to the Reservations
Tool (RZ) on page B-6.

Element Description

Combinations... • RZ

• RZGO

• RZ<pax>

RZ Access the “full reservation” mode of RZ. In this mode, you must
enter all information required in a standard reservation, such as
passenger name/contact information, flights, payments,
comments, and so on.

RZGO Access the “go-show” mode of RZ. In this mode, the following
fields are pre-filled with the words “walk-up”: phone, address,
comments, caller, and ticketing. You must enter the passenger
name, flights, and payments.

RZ<pax> Display the reservation for the specified passenger in RZ. For
example, to access the reservation for the passenger on line 1,
enter RZ1. To use this command, you must first display the
passenger whose reservation you want to view in a passenger list
(see Chapter 3, Displaying Passenger Lists).

SA Command
The SA command enables you to assign seats. See Chapter 5, Assigning Seats.

Element Description

Combinations... SA<pax>/<seat>

A–46 Airport Check-in User Guide

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Command Combinations

Element Description

SA<pax>/<seat> Assign a seat to the specified passengers. For thru passengers, the
system assigns the same seat for all legs of the thru flight.

For the <pax> entry, you can use any of the following
combinations:

• <pax>

For example, to assign seat 8A to the passenger on line 1,

enter SA1/8A.

• <pax>-<pax>

For example, to assign seats to the passengers on lines 1–3,

beginning with seat 8A, enter SA1-3/8A. The seats are
assigned sequentially, whenever possible, beginning with the
seat you specify.

For the <seat> entry, you must enter W, A, O, or <seat #> based
on the following criteria:

• W(indow). Assign the next available window seat. The next

available seat is determined by the seating priorities
configured in SkySchedule. For example, SA1/W assigns the
next available window seat.

• A(isle). Assign the next available aisle seat. The next available
seat is determined by the seating priorities configured in
SkySchedule. For example, SA1/A assigns the next available
aisle seat.

• O(ther). Assign the next available seat without a preference for

window or aisle. The next available seat is determined by the
seating priorities configured in SkySchedule. For example,
SA1/O assigns the next available seat.

• <seat #> – Assign the exact seat number. For example,

SA1/8A.

For more information on assigning seats, see Chapter 5, Assigning

Seats.

SM Command
The SM command displays the seat map for a flight. See Chapter 5, Assigning Seats.

Element Description

Combinations... • SM

• SM<destination station code>

• F,SM

• F<surname>,SM

SM Display the seat map for a flight. For more information on

displaying the seat map for a flight, see Displaying the Seat Map
on page 5-5.

Airport Check-in User Guide A–47

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Command Combinations

Element Description

SM<destination> Display the seat map for the leg that matches the destination
station. For thru flights with multiple aircraft configurations, all
seat maps are displayed.

F,SM Display all passengers on the flight and the seat map. For more
information on displaying the seat map for a flight, see Displaying
the Seat Map on page 5-5.

F<surname>,SM Display passengers on the flight filtered by surname and the seat
map. For example, to display all passengers whose surname
begins with “WOO” and the seat map, enter FWOO,SM.

SSR Command
The SSR command enables you to assign SSRs, remove SSRs, and view valid SSR codes. See
Assigning SSRs on page 9-6, Removing SSRs on page 9-8, and Displaying Valid SSR Codes on page
10-14.

Element Description

Combinations... • SSR

• SSR<pax>/<SSR code>

• SSR<pax>/<SSR code>/R

SSR Display the valid SSR codes configured for your airline.

SSR<pax>/<SSR code> Assign the specified SSR to the specified passenger. For example,
to assign the “PET” SSR to the passenger on line 1, enter
SSR1/PET. You can only assign one SSR at a time.

SSR<pax>/<SSR code>/R Remove the specified SSR from the reservation of the specified
passenger. For example, to remove the “PET” SSR from the
passenger on line 1, enter SSR1/PET/R. You can only remove one
SSR at a time.

UNAPISPRE Command
The UNAPISPRE command enables you to send an unverified preliminary APIS report for the
currently loaded flight to the customs office of the departure and/or arrival country even if
passengers are not yet checked in nor verified. See Sending an Unverified Preliminary APIS Report
to Customs on page 4-15.

Element Description

Combinations... • UNAPISPRE

• UNAPISPRE/<2-char country code>

UNASPISPRE Sends the unverified APIS report of the currently loaded flight to
the customs office of the departure or arrival country.

A–48 Airport Check-in User Guide

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Command Combinations

Element Description

UNAPISPRE/<2-char Sends the unverified APIS report of the currently loaded flight to
country code> the customs office of the country specified in the command.

US Command
The US command enables you to un-block seats. See Unblocking Seats on page 5-16.

Element Description

Combinations... • US<blocked seat #>

• US<blocked seat #>/<final destination>

US<seat #> Un-block the indicated seats. You must enter an exact seat
number, such as 8A (you cannot enter Window or Aisle).

For the <blocked seat #> entry, you can use any of the following
combinations:

• <blocked seat #>

For example, enter BS8A to un-block seat 8A.

• <blocked seat #>-<blocked seat #>

For example, enter BS8A-8D to un-block seats 8A through 8D.

US<seat #>/<final Un-block the indicated seats for all legs of a thru flight to the final
destination> destination. You must enter an exact seat number, such as 8A (you
cannot enter Window or Aisle).

For example, to un-block seat 8A on all legs of the currently loaded

flight to SLC, enter US8A/SLC. To un-block seats 8A through 8D
on all legs to SLC, enter US8A-8D/SLC.

.X Command
The .X command displays inbound passengers who are making a connection at the currently
loaded airport. See Displaying Connecting Passengers on page 3-18.

Element Description

Combinations... • .X

• .X<flight #>

• .X<airport code>

.X Display all inbound, connecting passengers for a flight.

.X<flight #> Display inbound, connecting passengers coming from a particular

flight. For example, to display the inbound, connecting passengers
coming from flight 100, enter .X100.

Airport Check-in User Guide A–49

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Command Combinations

Element Description

.X<airport code> Display inbound, connecting passengers coming from a particular

airport. For example, to display the inbound, connecting
passengers coming from LAX, enter .XLAX.

A–50 Airport Check-in User Guide

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Custom Commands

Custom Commands
SkyPort enables you to create your own commands to perform tasks that are not supported by
New Skies. In order to use custom commands, you first need to write code to accomplish the
desired task and ensure that your code can communicate with SkyPort. Then the command must
be added to the ExternalCommandConfig.xml file in Management Console. The following
sections give you the information required to perform those tasks.
• Creating Custom Commands on page A-51

• Configuring Custom Commands in Management Console on page A-53

Creating Custom Commands

The external code you create for your custom commands must have the ability to “talk” to
SkyPort. The schemas for the request and response are outlined below.

ExternalCommandRequest
<?xml version="1.0" encoding="utf-8"?>
<xs:schema elementFormDefault="qualified"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:import namespace="http://schemas.navitaire.com/Messages/Common" />
<xs:element name="ExternalCommandRequest" nillable="true"
type="ExternalCommandRequest" />
<xs:complexType name="ExternalCommandRequest">
<xs:complexContent mixed="false">
<xs:extension xmlns:q1="http://schemas.navitaire.com/Messages/Common"
base="q1:RequestBase">
<xs:sequence>
<xs:element minOccurs="0" maxOccurs="1" name="AgentId" type="xs:string" />
<xs:element minOccurs="0" maxOccurs="1" name="BagTagPrinterOff" type="xs:string"
/>
<xs:element minOccurs="0" maxOccurs="1" name="BagTagPrinterOn" type="xs:string"
/>
<xs:element minOccurs="0" maxOccurs="1" name="InputString" type="xs:string" />
<xs:element minOccurs="0" maxOccurs="1" name="CommandName" type="xs:string" />
<xs:element minOccurs="0" maxOccurs="1" name="PrinterOff" type="xs:string" />
<xs:element minOccurs="0" maxOccurs="1" name="PrinterOn" type="xs:string" />
<xs:element minOccurs="0" maxOccurs="1" name="ReportPrinterOff" type="xs:string" />
<xs:element minOccurs="0" maxOccurs="1" name="ReportPrinterOn" type="xs:string" />
<xs:element minOccurs="0" maxOccurs="1" name="SerializedObject" type="xs:string" />
<xs:element minOccurs="0" maxOccurs="1" name="TransactionIdentifier"
type="xs:string" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>

Airport Check-in User Guide A–51

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Custom Commands

Field Definitions
The following table provides an explanation of the elements included within the
ExternalCommandRequest.
Unless otherwise indicated, all fields are optional.

Field Name Example Description

AgentId - Identifies the agent currently logged into

SkyPort.

BagTagPrinterOff - Turns the bag tag printer off.

BagTagPrinterOn - Turns the bag tag printer on.

InputString - Input to the custom command.

CommandName manifest Name of the command as configured in

ExternalCommandConfig.xml. See
Configuring Custom Commands in
Management Console on page A-53 for
details.

PrinterOff - Turns the printer off.

PrinterOn - Turns the printer on.

ReportPrinterOff - Turns the report printer off.

ReportPrinterOn - Turns the report printer on.

SerializedObject - Serialized object to send.

TransactionIdentifier - Identifies the request and response.

ExternalCommandResponse
<?xml version="1.0" encoding="utf-8"?>
<xs:schema elementFormDefault="qualified"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:import namespace="http://schemas.navitaire.com/Messages/Common" />
<xs:element name="ExternalCommandResponse" nillable="true"
type="ExternalCommandResponse" />
<xs:complexType name="ExternalCommandResponse">
<xs:complexContent mixed="false">
<xs:extension xmlns:q1="http://schemas.navitaire.com/Messages/Common"
base="q1:MessageBase">
<xs:sequence>
<xs:element minOccurs="0" maxOccurs="1" name="ResponseString" type="xs:string" />
<xs:element minOccurs="0" maxOccurs="1" name="TransactionIdentifier"
type="xs:string" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>

A–52 Airport Check-in User Guide

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Custom Commands

Field Definitions
The following table provides an explanation of the elements included within the
ExternalCommandResponse.
Unless otherwise indicated, all fields are optional.

Field Name Example Description

ResponseString - Output from the custom command. Because

the output is displayed to the user in
SkyPort, the data should be formatted to be
no more than 80 characters wide and 22
lines long. Any data that does not fit on the
screen is ignored.

TransactionIdentifier - Identifies the request and response.

Configuring Custom Commands in Management Console

Custom commands must be configured in ExternalCommandConfig.xml, which is accessible
through Management Console (System Configuration > Resource Management). The Resource
Management directory structure looks like this.

ExternalCommandConfig.xml contains information about each of the custom commands you

have created. Before editing the file, it is recommended that you save a copy to your hard drive
and make the edits using either a text editor, such as Notepad or WordPad, or an XML editor.
Once you modify the file, browse and open it from the Resource Management dialog in
Management Console.
Your ExternalCommandConfig.xml file should look something like the example below, with one
section for each external command.
<ExternalCommandConfig xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd = "http://www.w3.org/2001/XMLSchema">
<ExternalCommands>
<ExternalCommand alias = "mo" name = "manifest">
<Description>Manifest Description</Description>
<IsInteractive>true</IsInteractive>
<SerializedObjectToSend>manifest</SerializedObjectToSend>
<TimeOutInSeconds>60</TimeOutInSeconds>
<WebServiceUrl>http://localhost:30094/SkyPortService.asmx</WebServiceUrl>
<Refresh>true</Refresh>
</ExternalCommand>
<ExternalCommand alias = "fi" name = "flight">
<Description>Flight Information Description</Description>
<IsInteractive>false</IsInteractive>

Airport Check-in User Guide A–53

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Custom Commands

<SerializedObjectToSend>flight information</SerializedObjectToSend>
<TimeOutInSeconds>60</TimeOutInSeconds>
<WebServiceUrl>http://localhost:30094/SkyPortService.asmx</WebServiceUrl>
<Refresh>false</Refresh>
</ExternalCommand>
</ExternalCommands>
</ExternalCommandConfig>

Field Definitions
The following table provides an explanation of the elements included within the
ExternalCommandConfig.xml file.
Unless otherwise indicated, all fields are required.

Field Name Example Description

ExternalCommand - Contains data specific to a specific custom

command. Create one ExternalCommand
section for each custom command.

alias mo Command to be run in SkyPort. For example,

>mo.

Note These values are case- and

space-sensitive.

name manifest Name of the command as it is sent to the

Web service.

Description Manifest Description Description of the command as displayed

when the user enters >?.

IsInteractive true Indicates whether the user can interact with

the Web service or not. If true, the user can
continue to enter text and press Enter until
typing EX to exit the command and return to
SkyPort. Each new input is appended to the
command’s InputString and is separated
from existing input by a ~. If false, the
command is not interactive and instead only
accepts one input when the user invokes it.
The user returns to SkyPort immediately
after the custom command executes.

SerializedObjectToSend manifest Serialized object to be sent in the Web

service request. Possible objects include
(Optional) manifest, booking, and flight information.

Note SkyPort sends the instance of the given

object that is loaded when the custom
command is executed. Since Airport
Check-in does not always load a passenger’s
booking, it is recommended that for
commands requiring a booking, you load the
booking in RZ and run the command there.
For commands requiring manifest of flight
information, load the desired information in
Airport Check-in before running the
command.

A–54 Airport Check-in User Guide

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Custom Commands

Field Name Example Description

TimeOutInSeconds 60 Number of seconds to wait for a response

from the Web service before timing out.

WebServiceUrl http://localhost:300 Web service URL.

94/SkyPortService.a
smx

Refresh true Indicates whether SkyPort updates the

booking or manifest object after the Web
service terminates. If true, the object is
updated in New Skies. If false, the object
remains as it was before the Web service
call.

Airport Check-in User Guide A–55

 APPENDIX A SUMMARY OF CHECK-IN COMMANDS
Custom Commands

A–56 Airport Check-in User Guide

B Shortcut Commands to Other
Management Console

In addition to the commands related specifically to Airport Check-in, there are several
commands you can use to access other utilities, including General Reference, Irregular
Operations (IROP), Flight Following (FLIFO), Seat Hold Maintenance, Flight Information, the
Reservations tool (RZ), and the Aircraft Zone report (a0023ros). This section describes the
commands you can use to access these utilities from Airport Check-in.
When you exit any of the Management Console accessed through Airport Check-in, the system
returns to the command prompt from which the utility was originally accessed.

In this chapter:

• Shortcut to General Reference on page B-2

• Shortcut to Irregular Operations (IROP) on page B-3
• Shortcut to Flight Information on page B-5
• Shortcut to the Reservations Tool (RZ) on page B-6
• Shortcut to the Aircraft Zone Report (23) on page B-7

Airport Check-in User Guide B–1

 APPENDIX B SHORTCUT COMMANDS TO OTHER MANAGEMENT CONSOLE
Shortcut to General Reference

Shortcut to General Reference

You can access General Reference from Airport Check-in using the GS command. General
Reference contains important information for your airline, including policies and procedures.
For example, a customer wants to know the policy of your airline regarding the carry on and use
of oxygen during flights. You can find your airline policy regarding oxygen use on flights in
General Reference.
This section describes how to use the shortcut command to access General Reference topics from
Airport Check-in.
General reference information is configured in Management Console (System Settings > General
Reference Management). For more information on General Reference, refer to the help files for
Management Console.

To access General Reference:

1 At the command prompt, type GS , then press Enter.

The main screen of General Reference displays:

2 To access a General Reference topic, at the Enter Selection prompt, type the number
that corresponds to the topic , then press Enter.

There may be additional topics within the selected topic. The organization of the General
Reference topics are configured in Management Console (System Settings > General
Reference Management). For more information on General Reference, refer to the help files
for Management Console.

3 To return to Airport Check-in, type EX , then press Enter.

The system returns you to the command prompt from which General Reference was
originally accessed.

B–2 Airport Check-in User Guide

 APPENDIX B SHORTCUT COMMANDS TO OTHER MANAGEMENT CONSOLE
Shortcut to Irregular Operations (IROP)

Shortcut to Irregular Operations (IROP)

You can access Irregular Operations (IROP) from Airport Check-in using the IROP command.
IROP is where you can process irregular operations for delayed or cancelled flights, including
passenger re-accommodation.
This section describes how to use the shortcut command to access Irregular Operations (IROP)
from Airport Check-in. It is important to note that in order to access IROP, you must be assigned
the Allow Console IROP role in Management Console (System Users > Roles). For more
information on agents and roles, refer to the online help for Management Console.
For more information on Irregular Operations, see the Operations User Guide.

To access IROP:

1 At the command prompt, type IROP , then press Enter.

The following screen displays:

You are now logged in to Irregular Operations.

Note: To access irregular operations, you must be assigned the Allow Console IROP permission in
Management Console (System Users > Roles).

2 To return to Airport Check-in, type EX , then press Enter.

The system returns you to the command prompt from which IROP was originally accessed.

Airport Check-in User Guide B–3

 APPENDIX B SHORTCUT COMMANDS TO OTHER MANAGEMENT CONSOLE
Shortcut to Flight Following (FLIFO)

Shortcut to Flight Following (FLIFO)

You can access Flight Following (FLIFO) from Airport Check-in using the OPS command. Flight
Following is where you enter status information about a flight, such as departure time/gate,
arrival time/gate, pit loads, passenger counts, and so on. The information can be viewed by
airport agents, reservation agents, customers using SkySales, and so on.
This section describes how to use the shortcut command to access Flight Following (FLIFO) from
Airport Check-in. It is important to note that in order to access FLIFO, you must be assigned the
Manage FLIFO role in Management Console (System Users > Roles). For more information on
agents and roles, refer to the help files for Management Console.
For more information on Flight Following, see the Operations User Guide.

To access Flight Following:

1 At the command prompt, type OPS , then press Enter.

The Flight Following screen displays:

Note: To access flight following, you must be assigned the Manage FLIFO role in Management
Console.

2 To return to Airport Check-in, type EX , then press Enter.

The system returns you to the command prompt from which Flight Following was originally
accessed.

B–4 Airport Check-in User Guide

 APPENDIX B SHORTCUT COMMANDS TO OTHER MANAGEMENT CONSOLE
Shortcut to Flight Information

Shortcut to Flight Information

You can access Flight Information from Airport Check-in using the .FI command. Flight
Information displays a consolidated version of the flight status information entered in
SkySchedule and Flight Following.
This section describes how to use the shortcut command to access Flight Information from
Airport Check-in. However, you can also access this utility from the Airport menu.

To access Flight Information:

1 At the command prompt, do one of the following:

• To view the status information for one flight (including all legs of the flight), type
.FI/<flight #> , then press Enter. For example, to view all legs of flight 123, enter
.FI/123.

OR

• To view the status information for all non-stop flights between a city pair, type .FI/<city
pair> , then press Enter. For example, to view all non-stop flights from SLC to JFK, enter
.FI/SLCJFK.

The status information displays, similar to the following:

If any comments were entered for the flight in Flight Following (including IROP comments
and RES comments), these comments display on this screen.

2 (Conditional) If necessary, to view additional flights, press Enter.

After all flights have displayed, the Press <ret> to continue prompt displays.

Airport Check-in User Guide B–5

 APPENDIX B SHORTCUT COMMANDS TO OTHER MANAGEMENT CONSOLE
Shortcut to the Reservations Tool (RZ)

Shortcut to the Reservations Tool (RZ)

You can access the Reservations tool from Airport Check-in using the RZ command. Also called
RZ, this tool enables you to create basic reservations and modify reservations. You can also book
flights, make payments, enter passenger information, and distribute itineraries.
RZ is designed for basic walk-up reservations and modifications; it does not have all of the
functionality of SkySpeed. If you need a more robust tool for creating or modifying reservations,
use SkySpeed.
This section describes how to use the shortcut command to access RZ from Airport Check-in.
However, some airlines configure their menu to enable agents to access RZ from their Airport
menu. For more information on RZ, see the Airport Reservations Tool (RZ) User Guide.

To access RZ:

1 At the command prompt, do one of the following:

• To access the main screen, type RZ , then press Enter.

OR

• To access the main screen and pre-fill the go-show fields with the word walk-up, type
RZGO , then press Enter. (Go-show fields are Phone, Comments, and Caller.)

OR

• To access the reservation for a specific passenger, type RZ<pax> , then press Enter. For
example, to access the reservation for the passenger on line 1, enter RZ1.

2 Enter your login information , then press Enter.

3 To return to Airport Check-in, type BYE , then press Enter.

The system returns you to the command prompt from which RZ was originally accessed.

B–6 Airport Check-in User Guide

 APPENDIX B SHORTCUT COMMANDS TO OTHER MANAGEMENT CONSOLE
Shortcut to the Aircraft Zone Report (23)

Shortcut to the Aircraft Zone Report (23)

You can access the Aircraft Zone report (23) from Airport Check-in using the .Z command. This
report displays seating zone information and passenger totals for a flight.
Note: To access the Aircraft Zone Report, you must be assigned the Aircraft Zone Report permission
in Management Console (System Users > Roles).
This section describes how to use the shortcut command to access the Aircraft Zone report from
Airport Check-in. However, some airlines can access this report from the Airport menu. For
more information on the Aircraft Zone report, see the SkyPort Reports User Guide.

To access the Aircraft Zone report:

1 At the command prompt, type .Z , then press Enter.

The Aircraft Zone report displays, prompting you to select a printing device and define the
flight whose zones you want to view. For more information on this report, see the SkyPort
Reports User Guide.

2 To return to Airport Check-in, type EX , then press Enter.

The system returns you to the command prompt from which the Aircraft Zone report was
originally accessed.

Airport Check-in User Guide B–7

 APPENDIX B SHORTCUT COMMANDS TO OTHER MANAGEMENT CONSOLE
Shortcut to the Aircraft Zone Report (23)

B–8 Airport Check-in User Guide

C Troubleshooting

This section identifies some of the problems that may be encountered when using Airport
Check-in, and possible solutions.

Troubleshooting

Seats on hold Seats on “hold” are really not being “held”; the seats can still be assigned in
Airport Check-in.

Solution 1: The “hold” seat status alerts airport agents that someone wants
the seat “held”, but it does not prohibit the seat from being
assigned. The “block” seat command prohibits seats from being
assigned. For information on blocking seats, see Holding or
Blocking Seats on page 5-13.

Printing itineraries When printing itineraries (IT command), the printer number is not working.

Solution 1: Try using the printer name instead of the printer number with
the IT command. For more information on printing itineraries,
see Re-printing Itineraries on page 4-39.

Passenger check-in When trying to check in a passenger, I get the following error message: Cannot
check in passenger on past date flight.

Solution 1: The flight may be too far in advance.

Solution 2: The flight may have already flown. You cannot check in
passengers on flights that have already flown.

.BTP command When I enter the .BTP command, I get the following error message: Print bag
tag option was not selected.

Solution 1: You cannot print bag tags unless you enable bag tag printing for
the current login session. When you first log in to Airport
Check-in, at the prompt “Automatic Print Bag Tags”, type Y.

Passenger check-in I cannot check in passengers if their name has special characters (for example,
ñ, é, ç).

Solution 1: Airport Check-in does not support special characters. When

checking in passengers with special characters, you must do a
name change and replace the special character with its English
equivalent. You can do name changes in Airport Check-in using
the N command (see Modifying Passenger Name Information on
page 9-2).

Airport Check-in User Guide C–1

 APPENDIX C TROUBLESHOOTING

Troubleshooting

FLIFO The FLIFO information for certain flights does not display in Airport Check-in.

Solution 1: Is the flight more than three days out? FLIFO information is built
through a nightly job, which is set to build this information for
three days out. If the flight is greater than three days out, FLIFO
information does not display.

Solution 2: Is the flight an “ad hoc” flight for today? If so, you must
manually build a Flight Following record for the flight if you want
to view the flight information today. Flight Following information
is built through a nightly job; if the flight was created today, then
no FLIFO record has been built for the flight.

C–2 Airport Check-in User Guide

Index
Index

Symbols explained, A-2

. command APIS command
explained, A-2
explained, A-9 APIS. See Advance Passenger Information
. command
explained, A-9 System (APIS)
APISFINAL command
.<reservation> command explained, A-2
displaying all pax on a reservation, 3-8
.TKT command final APIS report, 4-17
APISPRE command
displaying pax with tkt (Airport Check-in), explained, A-3, A-8
3-22
preliminary APIS report, 4-16
APP. See Advance Passenger Processing (APP)
A APPS
.APC command displaying overrides, 3-33
explained, A-9 APPSALL command
.APIS command explained, A-3
displaying pax with APIS info, 3-27 AQQ, 4-12, 4-17
explained, A-9 assigning seats, 5-6
.APIS command for connecting flights, 5-7
explained, A-9
.APIS* command B
explained, A-9 .B command
.APIS/BAD command
explained, A-9 combinations of, A-29
displaying baggage count for a flight, 10-4
.APPSOVR command displaying checked baggage for a pax, 9-29
displaying pax with APPS override, 3-33
explained, A-9 explained, A-9
.BA command
AB command displaying baggage allowance for a pax,
checking in baggage, 6-7
combinations of, A-29 9-31
.BD command, 3-38
explained, A-2 .BTP command
Advance Passenger Information System (APIS)
displaying passengers with info, 3-27 displaying bag tag printers, 6-5
explained, A-10
overview, 4-12, 4-14, 4-15 .BZ command
sending a preliminary report, 4-16
sending the final report, 4-17 explained, A-10
>BAGTAG command
validating pax at check-in using APIS, 4-12, explained, A-3
4-15
Advance Passenger Processing (APP) B command
checking in baggage, 6-7
overview, 4-20 combinations of, A-29
validating pax at check-in using APP
Aircraft Zone report (a0023ros), B-7 explained, A-3
bag drop, 6-12
Airport Check-in bag tag
about, 1-1
command prompt, 1-21 entering manually, 6-13
scanning barcodes, 6-12
online Help, 1-23 bag tag numbers
role settings, 1-12
shortcuts to other utilities about, 6-2
entering manually, 6-2
Aircraft Zone report (a0023ros), B-7 format of, 6-2
Flight Following (FLIFO), B-4 generating automatically, 6-2
General Reference (GS), B-2 bag tag printer
Irregular Operations (IROP), B-3 BTP command, A-32
RZ, B-6 bag tag printers
troubleshooting, C-1 changing, 6-6
Airport menu displaying, 6-5
logging out, 1-21 selecting, 6-6
APC command

Airport Check-in User Guide I–1

 INDEX

bag tags and baggage messages, understanding re-printing boarding passes, 4-39
multi-carrier situations, 6-3 BRD command
baggage boarding all pax on flight, 7-5
baggage information line, 9-29 boarding pax by scanning, 7-3
changing weight, 9-32 boarding pax individually, 7-2
checking in, 6-7 combinations of, A-31
AB command, A-29 explained, A-3
B command, A-29 un-boarding all pax on flight, 7-7
MB command, A-40 un-boarding pax individually, 7-6
using automatic bag tag numbers, 6-7 BS command
using pre-printed bag tags, 6-9 blocking seats, 5-13
combinations of, A-31
with broken printer, 6-7
explained, A-3
displaying baggage BSB command
.B command, A-29 explained, A-3
allowance, 9-31 BSM
checked in for a pax, 9-29 multi-carrier, 6-3
totals for a flight, 10-4 BT command
positive bag tag matching, 6-17 explained, A-3
removing from check-in, 6-15 BTP command
Baggage Count screen, 10-4 combinations of, A-32
baggage information line, 9-29 explained, A-3
baggage messages and bag tags, understanding selecting bag tag printers, 6-6
multi-carrier situations, 6-3 BUM command
baggage totals explained, A-3
.B command, A-29
Baggage Count screen, 10-4 C
displaying for a flight, 10-4
baggage weight .C command
changing, 9-32 displaying checked-in pax, 3-9
bags, check in, 6-12 explained, A-10
barcode .CU command
bag tag, 6-13 displaying pax w/customer accounts, 3-33
boarding pass, 7-3 explained, A-10
entering manually, 6-13 C command
BD command bypassing seat rqmt (confirmed pax), 4-5
combinations of (Airport Check-in), A-30 checking in all pax, 4-7
entering birthdates (Airport Check-in), 9-21 checking in individual pax, 4-5
explained, A-3 checking in pax on int’l flights (APIS), 4-12,
birthdates 4-15
BD command (Airport Check-in), A-30 checking in pax on int’l flights (APPS), 4-20
entering (Airport Check-in), 9-21 checking in pax on int’l flights (iAPP), 4-26,
blocking seats, 5-13 4-28
boarded passengers checking in pax with Secure Flight, 4-24
.QB command, 3-13 combinations of, A-32
displaying, 3-13 explained, A-3
boarding passengers CALL command
about sequence numbers, 4-3 explained, A-4
all pax on flight, 7-5 CF command
BRD command, A-31 closing flights, 8-4
individually, 7-2 explained, A-4
scanning, 7-3 checking in baggage, 6-7
boarding passes checking in passengers
BP command, A-30 about sequence numbers, 4-3
re-printing, 4-39 bypassing seat rqmt (confirmed pax), 4-5
BP command bypassing seat rqmt (standby pax), 4-7
combinations of, A-30 C command, A-32
explained, A-3 code share, 4-30

I–2 Airport Check-in User Guide

 Index

confirmed (all pax on flight), 4-7 checking in pax with Secure Flight, 4-24
code share, 4-32 combinations of, A-34
confirmed (individual pax), 4-5 explained, A-4
code share, 4-31 CSALL command
CS command, A-34 explained, A-4
on international flights (APIS), 4-12, 4-15 CU command
on international flights (APPS, 4-20 associating pax w/customer accounts, 9-25
on international flights (iAPP), 4-26, 4-28 combinations of, A-35
overview, 4-1 explained, A-4
Secure Flight, 4-24 removing customer account associations,
standby (all pax on flight), 4-9 9-26, 9-27
code share, 4-33 custom commands, A-51
standby (individual pax), 4-7 customer accounts
code share, 4-32 associating with passengers, 9-25
tracking check-in progress, 4-1 CU command, A-35
with same-day return, 4-10 displaying passengers with, 3-33
checking in passengers on code share flights removing associations with pax, 9-26, 9-27
MC command, A-41 CW command
checking in pax with Secure Flight, 4-24 changing baggage weight, 9-32
checking in standby passengers, A-41 explained, A-4
CL# command
explained, A-4 D
close-pending flights, 8-3 .D command
closing flights, 8-4 displaying downline pax count, 10-5
CLS command explained, A-10
explained, A-4 .DEST command
code share deleting destination addresses, 9-13, 9-18
checking in passengers, 4-30, A-41 explained, A-10
MCS command, A-41 .DEST* command
RMCS command, A-44 explained, A-4
unchecking passengers, A-44 modifying destination addresses, 9-16, 9-19
command prompt .DN command
Airport Check-in, 1-21 displaying downline pax, 10-6
loading flights from, 2-8 explained, A-10
commands .DOC
Airport Check-in displaying all documents for a passenger,
combinations of, A-28 3-25
custom commands, A-51 .DOC command
ordered by task, A-14 combinations of, A-35
summary of action commands, A-2 displaying pax with int’l documents, 3-25
summary of display commands, A-9 explained, A-10
connecting flights .DOC* command
assigning seats for, 5-7 explained, A-4
connecting passenger list, 10-10 modifying misc int’l documents (Airport
connecting passenger totals, 10-9 Check-in), 9-11
CP command departure/arrival times
explained, A-4 displaying (Airport Check-in), 2-4
setting flights to close pending, 8-3 DEST command
CS command entering destination addresses, 9-14
bypassing seat rqmt (standby pax), 4-7 explained, A-4
checking in all standby pax, 4-9 destination address
checking in individual standby pax, 4-7 displaying, 9-13, 9-18
checking in pax on int’l flights (APIS), 4-12, entering, 9-14
4-14, 4-15 modifying, 9-16, 9-19
checking in pax on int’l flights (APPS), 4-20 displaying passengers
checking in pax on int’l flights (iAPP), 4-26, all pax on a reservation, 3-8
4-28 all pax on flight (Airport Check-in), 3-3

Airport Check-in User Guide I–3

 INDEX

all pax on same reservation, 3-8 field definitions, A-52, A-53

boarded pax, 3-13 schema, A-51
by marketing designator, 3-16 ExternalCommandResponse
by seat assignment, 3-35 schema, A-52
by sequence number, 3-35
by surname (Airport Check-in), 3-9 F
checked-in pax, 3-9
connecting pax, 3-18 .FC command
locked reservations, 3-35 explained, A-11
no seat, 3-15 .fc command, 3-5
no-show pax, 3-14 .FF command
premium fare, 3-20 explained, A-11
standby pax (Airport Check-in), 3-10 .FI command
thru pax, 3-17 combinations of, A-36
un-boarded pax, 3-13 explained, A-11
upgraded pax, 3-18 .FR command
with APIS info, 3-27 explained, A-11
with APPS override, 3-33 viewing flight status history, 10-15
with balance due, 3-38 F command
with customer accounts, 3-33 combinations of, A-36
with international documents, 3-25 displaying all pax (Airport Check-in), 3-3
with loyalty program, 3-34 displaying pax by surname (AC), 3-9
with manifest comments, 3-20 explained, A-10
with tickets (Airport Check-in), 3-22 fare class
without international documents, 3-26 display full, 3-5
DOC command FF command
entering misc int’l documents (Airport explained, A-5
Check-in), 9-9 FF* command
explained, A-4 explained, A-5
DOCI command FF/R command
entering misc int’l docs for infants (Airport explained, A-5
Check-in), 9-9 Flight Following (FLIFO)
DOCS command accessing from Airport Check-in, B-4
explained, A-10 flight information line (Airport Check-in), 2-4
DOCVERIFY/F command, 4-14 flight status
explained, A-4 about, 8-2
DOCX command viewing history of, 10-15
deleting misc int’l documents (Airport viewing in Airport Check-in, 8-2
Check-in), 9-12, 9-20 flights
explained, A-4 .FI command, A-36
Downline Passenger Count screen, 10-5, 10-6 assigning seats (connecting flights), 5-7
downline passenger list assigning seats (non-stop/thru flights), 5-6
.DN command, 10-6 boarding all pax on flight, 7-5
description of, 10-6 boarding passengers by scanning, 7-3
displaying, 10-6 boarding passengers individually, 7-2
downline passenger totals close pending, 8-3
.D command, 10-5 closing, 8-4
description of, 10-5 displaying information about
displaying, 10-5 baggage count, 10-4
connecting pax, 10-10
E connecting pax count, 10-9
downline passenger list, 10-6
.EXST command downline passenger totals, 10-5
explained, A-10 downline pax count, 10-5, 10-6
e-Borders, 4-12
ExternalCommandConfig.xml inbound cnx pax count, 10-9
field definitions, A-54 inbound cnx pax list, 10-10
ExternalCommandRequest total pax count (Airport Check-in), 10-2

I–4 Airport Check-in User Guide

 Index

flight information line (Airport Check-in), Help (online)

2-4 Airport Check-in, 1-23
international check-in (APIS validation), HELP command
4-12, 4-15 Airport Check-in, 1-23
international check-in (APPS validation), explained, A-5
4-20 holding seats, 5-13
international check-in (iAPP validation),
4-26, 4-28 I
L command, A-38
LF command, A-39 .I command
listing, 2-9 displaying connecting pax count, 10-9
loading in Airport Check-in explained, A-11
after login, 2-1 .IN command
from the command prompt, 2-8 displaying connecting pax, 10-10
from the flight list, 2-9 explained, A-11
iAPP. See Interactive Advance Passenger
merging seat maps, 5-8 Processing (iAPP)
opening flights, 8-6
positive bag tag matching, 6-17 IATCI See Inter Airline Through Check-in
II command
Secure Flight validation, 4-24 explained, A-5
status of
viewing flight status history, 10-15 re-printing itineraries, 4-39
inbound cnx passenger list
viewing in Airport Check-in, 8-2 description of, 10-10
tracking check-in progress of, 4-1 displaying, 10-10
un-boarding all pax on flight, 7-7 inbound cnx passenger totals
un-boarding passengers individually, 7-6 description of, 10-9
FLTVERIFY command displaying, 10-9
explained, A-5 Inbound CNX Passengers screen, 10-9, 10-10
FLTVERIFY/F command, 4-14 infants
explained, A-5 entering information for (Airport Check-in)
FLTVERIFYX command misc int’l documents, 9-9
explained, A-5 Inter Airline Through Check-in
frequent flier information assigning seats with, 5-6
maintaining, 9-22 birthdates with, 9-21
full fare class checking in passengers with, 4-5
display, 3-5 destination addresses with, 9-13, 9-14, 9-16,
FYI command 9-18, 9-19
explained, A-11 frequent flier information with, 9-22
handling bags with, 6-3
G remove SSRs, 9-8
gate passes, 4-40 removing bags from check-in with, 6-15
General Reference SSR functionality, 9-6
accessing from Airport Check-in, B-2 travel documents with, 9-9, 9-11, 9-12, 9-20
generating bag tag numbers Interactive Advance Passenger Processing
automatically vs. manually, 6-2 (iAPP)
GP command overview, 4-26, 4-28
explained, A-5 validating pax at check-in using iAPP, 4-26,
printing gate passes, 4-40 4-28
GS command international documents (miscellaneous)
accessing General Reference, B-2 .DOC command, A-35
explained, A-5 deleting (Airport Check-in), 9-12, 9-20
displaying passengers with, 3-25
displaying passengers without, 3-26
H entering (Airport Check-in), 9-9
H command modifying (Airport Check-in), 9-11
combinations of, A-37 international flights
explained, A-5 checking in pax (APIS validation), 4-12,
holding seats, 5-13 4-14, 4-15

Airport Check-in User Guide I–5

 INDEX

checking in pax (APPS validation), 4-20 explained, A-6

checking in pax (iAPP validation), 4-26, 4-28
IROP command M
accessing Irregular Operations, B-3
explained, A-5 .M command
Irregular Operations (IROP) combinations of, A-40
accessing from Airport Check-in, B-3 displaying manifest comments for pax, 9-33
IT command displaying pax w/manifest comments, 3-20
combinations of, A-37 explained, A-11
explained, A-5 .MC command
re-printing itineraries, 4-39 displaying pax by marketing designator,
itineraries 3-16
IT command, A-37 explained, A-12
re-printing, 4-39 manifest comments
.M command, A-40
displaying for a passenger, 9-33
J displaying passengers with, 3-20
J command MB command
changing pax title to CHD, 9-5 checking in baggage, 6-7
combinations of, A-38 checking in bags w/broken printer, 6-7
explained, A-5 combinations of, A-40
explained, A-6
L MC command
checking in all pax, 4-32
.L command checking in individual pax, 4-31
explained, A-11 combinations of, A-41
.LP command explained, A-6, A-7
combinations of, A-39 MCALL command
displaying pax w/loyalty program, 3-34 explained, A-6, A-7
explained, A-11 MCS command
L command checking in all standby pax, 4-33
combinations of, A-38 checking in individual standby pax, 4-32
explained, A-11 combinations of, A-41
listing flights, 2-9 explained, A-6, A-7
LF command MCSALL command
combinations of, A-39 explained, A-6, A-7
explained, A-5 MD command
loading flights, 2-8 explained, A-6
listing flights, 2-9 merging seat maps (for thru flights), 5-8
L command, A-38 MU command
LL command explained, A-6
explained, A-6
loading flights, 2-8
loading flights N
after login, 2-1 .N command
from the command prompt, 2-8 displaying no-show pax, 3-14
from the flight list, 2-9 explained, A-12
LF command, A-39 .NS command
logging in, 1-18 displaying pax without seat, 3-15
logging out explained, A-12
Airport menu, 1-21 N* command
loyalty explained, A-6
.LP command, A-39 modifying passenger names/titles, 9-2
LP command, A-40 no-show passengers, displaying, 3-14
loyalty program
displaying passengers with, 3-34 O
LP command
combinations of, A-40 OF command
explained, A-6

I–6 Airport Check-in User Guide

 Index

opening flights, 8-6 standby (individual pax), 4-7

OP command checking in on international flights (APPS),
explained, A-6 4-20
opening flights, 8-6 customer account associations
OPS command, B-4 creating, 9-25
explained, A-6 removing, 9-26, 9-27
deleting information for (Airport Check-in)
P misc int’l documents, 9-12, 9-20
.P command displaying
displaying all pax on same reservation, 3-8 all pax on a reservation, 3-8
explained, A-12 all pax on flight (Airport Check-in), 3-3
.PS command all pax on same reservation, 3-8
displaying premium fare pax, 3-20 boarded pax, 3-13
explained, A-12 by marketing designator, 3-16
Passenger Count screen, 10-2 by seat assignment, 3-35
passenger information line (Airport Check-in), by sequence number, 3-35
3-3, 3-22 by surname (Airport Check-in), 3-9
passenger list checked-in pax, 3-9
connecting pax, 10-10
connecting pax, 3-18
passenger names
modifying (Airport Check-in), 9-2 locked reservations, 3-35
passenger titles no seat, 3-15
changing to CHD, 9-5 no-show pax, 3-14
J command, A-38 pax with APIS info, 3-27
modifying (Airport Check-in), 9-2 pax with APPS override, 3-33
passenger totals pax with customer accounts, 3-33
connecting pax count, 10-9 pax with int’l documents, 3-25
downline pax count, 10-5 pax with loyalty program, 3-34
Passenger Count screen, 10-2 pax with manifest comments, 3-20
total pax count (Airport Check-in), 10-2
passengers pax without int’l documents, 3-26
assigning seats to premium fare, 3-20
changing seat assignments, 5-10, 5-12 standby pax (Airport Check-in), 3-10
for connecting flights, 5-7 thru pax, 3-17
for non-stop and thru flights, 5-6 un-boarded pax, 3-13
boarding upgraded pax, 3-18
all pax on flight, 7-5 with balance due, 3-38
individually, 7-2 with tickets (Airport Check-in), 3-22
scanning, 7-3 displaying information about
checking in baggage allowance for, 9-31
confirmed (all pax on code share flight), baggage checked in for, 9-29
4-32 manifest comments assigned to, 9-33
confirmed (all pax on flight), 4-7 pax information line, 3-3, 3-22
confirmed (individual code share pax), SSRs assigned to, 9-34
4-31 standby pax information line, 3-10
confirmed (individual pax), 4-5 downline passenger list, 10-6
on international flights (APIS), 4-12, 4-15 downline passenger totals, 10-5
on international flights (iAPP), 4-26, 4-28 downline pax list, 10-6
entering information for (Airport Check-in)
same-day return, 4-10
birthdates, 9-21
Secure Flight, 4-24 misc int’l documents, 9-9
standby (all pax on code share flight),
inbound cnx passenger list, 10-10
4-33 inbound cnx passenger totals, 10-9
standby (all pax on flight), 4-9 modifying info for (Airport Check-in)
standby (individual code share pax), names/titles, 9-2
4-32 titles (changing to CHD), 9-5

Airport Check-in User Guide I–7

 INDEX

modifying information for (Airport removing baggage from check-in, 6-15

Check-in) RB command, A-44
misc int’l documents, 9-11 removing passengers from check-in
removing from check-in all confirmed pax on flight, 4-36
all confirmed pax, 4-36 all standby pax on flight, 4-37
all standby pax, 4-37 individual confirmed pax, 4-35
individual confirmed pax, 4-35 individual standby pax, 4-37
individual standby pax, 4-37 R command, A-43
RS command, A-45
Special Service Requests (SSRs) re-printing
assigning (Airport Check-in), 9-6
boarding passes, 4-39
removing, 9-8 itineraries, 4-39
un-boarding reservations
all pax on flight, 7-7 modifying
individually, 7-6 passenger names/titles (Airport
verifying travel documents, 4-14 Check-in), 9-2
passengers without seat assignments, Reservations tool (RZ)
displaying, 3-15 accessing
passports from Airport Check-in, B-6
.DOC command, A-35 RZ command, A-46
displaying passengers with, 3-25 RMC command
displaying passengers without, 3-26 combinations of, A-44
PNRGOV command RMCS command
combinations of, A-42 combinations of, A-44
explained, A-7 role settings
positive bag tag matching, 6-17 Airport Check-in, 1-12
premium fares RS command
configuring, 1-3, 5-4 combinations of, A-45
printing gate passes, 4-40 explained, A-7
removing all standby pax from check-in,
Q 4-37
.Q command removing individual standby pax from
combinations of, A-43 check-in, 4-37
displaying pax by sequence number, 3-35 RSALL command
explained, A-12 explained, A-7
.QB command RZ command
displaying boarded pax, 3-13 accessing RZ from Airport Check-in, B-6
explained, A-12 combinations of, A-46
.QN command explained, A-7
displaying un-boarded pax, 3-13 RZGO command
explained, A-12 explained, A-8
Q command
explained, A-7 S
.S command
R displaying standby pax (Airport Check-in),
R command 3-10
combinations of, A-43 explained, A-12
explained, A-7 .SF/BAD command
removing all pax from check-in, 4-36 explained, A-12
removing individual pax from check-in, .SSR command
4-35 explained, A-12
RALL command S command
explained, A-7 changing standby priority codes, 9-4
RB command explained, A-8
combinations of, A-44 SA command
explained, A-7 assigning seats (connecting flights), 5-7
removing baggage from check-in, 6-15 assigning seats (non-stop/thru flights), 5-6

I–8 Airport Check-in User Guide

 Index

changing seat assignments, 5-10, 5-12 SSR command

combinations of, A-46 assigning SSRs (Airport Check-in), 9-6
explained, A-8 combinations of, A-48
same-day return check-in, 4-10 displaying valid SSR codes, 10-14
scan explained, A-8, A-12
bag tag barcodes, 6-12 removing SSRs, 9-8
boarding pass barcodes, 7-3 SSR display, configuring
screen descriptions (Airport Check-in) .N command, 3-14
Baggage Count screen, 10-4 .SSR command, 3-21
baggage information line, 9-29 CheckinConfig.xml, 1-5
Downline Passenger Count screen, 10-5, passenger display commands, 3-3
10-6 ST command
flight information line, 2-4 explained, A-8
Inbound CNX Passenger Count screen, for thru flights, 5-8
10-9, 10-10 standby passengers
Passenger Count screen, 10-2 changing standby priority codes, 9-4
passenger information line, 3-3, 3-22 checking in baggage, 6-7
standby pax information line, 3-10 CS command, A-34
seat map displaying (Airport Check-in), 3-10
about, 5-2 MCS command, A-41
displaying, 5-5 RMCS command, A-44
holding or blocking seats, 5-13 standby pax information line, 3-10
merging for thru flights, 5-8 standby pax info line (Airport Check-in), 3-10
premium fares on, 5-4 standby priority codes
SM command, A-47 changing for a passenger, 9-4
SSRs on, 5-2 STBY command, 10-13
status codes on, 5-2 viewing, 10-13
seats STBY command
assigning (connecting flights), 5-7 displaying standby priority codes, 10-13
assigning (non-stop/thru flights), 5-6 explained, A-13
blocking, 5-13
BS command, A-31 T
bypassing seat rqmt (confirmed pax), 4-5
bypassing seat rqmt (standby pax), 4-7 .T command
H command, A-37 displaying thru pax, 3-17
holding, 5-13 explained, A-13
SA command, A-46 .TKT command
un-blocking, 5-16 explained, A-13
US command, A-49 thru flights
sequence numbers assigning seats for, 5-8
about, 4-3 merging seat maps, 5-8
finding passengers by, 3-35 troubleshooting
SM command Airport Check-in, C-1
combinations of, A-47
displaying seat maps, 5-5 U
explained, A-12
for thru flights, 5-8 .U command
merging seat maps, 5-8 displaying upgraded pax, 3-18
Special Service Requests (SSRs) explained, A-13
assigning (Airport Check-in), 9-6 U command
displaying for a passenger, 9-34 explained, A-13
displaying valid SSR codes, 10-14 updating pax count (Airport Check-in), 10-2
removing, 9-8 un-blocking seats, 5-16
SSR command, A-48 un-boarded passengers, displaying, 3-13
.SSR command un-boarding passengers
displaying SSRs for a pax, 9-34 all pax on flight, 7-7
SSR BRD command, A-31
on seat map, 5-2 individually, 7-6

Airport Check-in User Guide I–9

INDEX

unchecking passengers on code share flights

RMC command, A-44
un-checking passengers. See removing
passengers from check-in
unchecking standby passengers, A-44
US command
combinations of, A-49
explained, A-8
un-blocking seats, 5-16

V
V command
creating vouchers for individual pax, 11-2
explained, A-8
VALL command
creating vouchers for all pax, 11-4
explained, A-8
verifying travel documents, 4-14
visas
.DOC command, A-35
displaying passengers with, 3-25
vouchers
creating for all pax on a flight, 11-4
creating for individual passengers, 11-2

W
.WL command
explained, A-13

X
.X command
combinations of, A-49
displaying connecting pax, 3-18
explained, A-13
.XDOC command
displaying pax without int’l documents,
3-26
explained, A-13

Z
.Z command
accessing the Aircraft Zone report, B-7
explained, A-13

I–10 Airport Check-in User Guide