SDCS Load Planning User Guide - 7.1 - A4

Passenger Solutions
SITA Departure Control Services
Load Planning User Guide

Copyright Notice
© SITA, 2000 - 2007
All Rights Reserved
The information contained in this document is the property of SITA. No part of this document may be
reproduced, stored in a retrieval system, or transmitted in any form, or by any means; mechanical,
photocopying, recording, or otherwise, without the prior written consent of SITA. Under the law,
copying includes translating into another language or format. Legal action will be taken against any
infringement.
The information contained in this document is subject to change without notice and does not carry any
contractual obligation for SITA. SITA reserves the right to make changes to any products or services
described in this document at any time without notice. SITA shall not be held responsible for the
direct or indirect consequences of the use of the information contained in this document.
Table of Contents
1. Introduction .................................................................................................................................... 1
1.1. General Information ................................................................................................................................ 1
1.2. Course Objectives................................................................................................................................... 1
2. Manual Flight Creation................................................................................................................... 3

2.1. Manual Flight Creation (LCFD) ............................................................................................................... 3
2.2. Error Responses ..................................................................................................................................... 4
3. Flight Data Display ......................................................................................................................... 5

3.1. Configuration Table Display (CND:A) ..................................................................................................... 5
3.2. Aircraft Registration Data Display (LACD) .............................................................................................. 6
3.3. Flight Data Display (FDD) ....................................................................................................................... 7
3.4. Flight Update Information (FUI)............................................................................................................... 8
3.5. FUI Error Responses .............................................................................................................................. 9
3.6. Flight Initialization (DPT) ......................................................................................................................... 9
3.7. Flight Irregular Operations (FIR) ........................................................................................................... 10
4. List of Active Flights .................................................................................................................... 15

4.1. List of Active Flights in LDP (LFLD) ...................................................................................................... 15
4.2. Error Responses ................................................................................................................................... 15
5. Operational Screen Display ........................................................................................................ 17

5.1. Operational Data Display (LODD)......................................................................................................... 17
5.2. Operational Screen Update (LODU) ..................................................................................................... 19
5.3. Error Responses ................................................................................................................................... 19
6. Fuel Screen ................................................................................................................................... 21

6.1. Fuel Screen Display (LFFD).................................................................................................................. 21
6.2. Fuel Screen Update (LFFU).................................................................................................................. 21
6.3. Error Responses ................................................................................................................................... 21
7. Passenger Payload Screens (LPAD) ..........................................................................................23

7.1. Passenger Area Seating Display (PAX) ................................................................................................ 23
7.2. Passenger Transit Details (PAX1) ........................................................................................................ 24
7.3. Passenger Checked-In Display (PAX2) ................................................................................................ 25
7.4. Passenger Booked Display (PAX3) ...................................................................................................... 26
7.5. ACARS Loadsheet Information ............................................................................................................. 27
7.6. Error Responses ................................................................................................................................... 28
SITA Departure Control Services – Load Planning User Guide

Table of Contents
29 August 2008 – Revision 7.1 Page i
© SITA 2007 All Rights Reserved
7.7. Payload Available Display - Miscellaneous (PAX4) .............................................................................. 29
7.8. Payload Available Display - Transit Miscellaneous1 (PAX5) ................................................................ 29
7.9. Payload Available Display - Transit Miscellaneous2 (PAX6) ................................................................ 30
8. Cargo Payload and Load Distribution Screens.........................................................................31

8.1. Load Distribution Screen (CGO1) ......................................................................................................... 31
8.2. LPAD:Flight/Date/CGO1 Error Responses ........................................................................................... 34
8.3. Trim Display (LPDD) ............................................................................................................................. 35
8.4. Cargo / Mail Allotments (LPCD) ............................................................................................................ 37
8.5. System Selected Deck Version (LDVS) ................................................................................................ 38
8.6. Automatic Load Planning (LALD).......................................................................................................... 38
8.7. LALD: Flight/Date Error Responses...................................................................................................... 40
8.8. Offload Display (LOLD) ......................................................................................................................... 41
8.9. LOLD Error Responses......................................................................................................................... 41
9. Flight Status Screen..................................................................................................................... 43

9.1. Flight Status Display (LFSD)................................................................................................................. 43
9.2. Error Responses ................................................................................................................................... 49
10. Add Special Information and Printing Request ........................................................................51

10.1. Supplementary Information Entry (LMSD) ............................................................................................ 51
10.2. Print Loading Instruction (LDSP)........................................................................................................... 52
10.3. Notification to Captain (NOTOC)........................................................................................................... 54
10.4. Print Load sheet (LLSP)........................................................................................................................ 57
10.5. Error Responses ................................................................................................................................... 58
11. Additional Flight Entries and Information .................................................................................61

11.1. Flight Cancellation (LFIX)...................................................................................................................... 61
11.2. Cabin Loading/Seats Occupied By Cargo (LSCD)................................................................................ 62
11.2.1 Seats Occupied by Cargo (LSCD)............................................................................................. 62
11.2.2 Cabin Loading (LPAD:FLT/DATE/CGO).................................................................................... 62
11.3. Transit Flights ....................................................................................................................................... 63
11.3.1 Transit Flight from an Automated Station .................................................................................. 63
11.3.2 Transit Flight from an Non-Automated Station........................................................................... 63
11.4. Extra Crew (XXXCREW)....................................................................................................................... 69
11.5. Jump Seat Passengers ......................................................................................................................... 70
11.6. Stretcher Passengers ........................................................................................................................... 71
11.7. EZFW Display (LZFW) .......................................................................................................................... 72

Table of Contents
Page ii 29 August 2008 – Revision 7.1
11.8. Seats Occupied Display (LSOD)........................................................................................................... 72
11.9. Payload Transfer Between Flights (LCOP) ........................................................................................... 73
12. Flight A/C Changes ...................................................................................................................... 75

12.1. Flight A/C Version / Type Change......................................................................................................... 75
12.1.1 Before Flight Initialization for both CKI and LDP........................................................................ 75
12.1.2 After CKI Initialization but Before LDP Initialization ................................................................... 75
12.1.3 After CKI and LDP Initialization but Before Flight Closed for CKI .............................................. 76
12.1.4 After Flight Closed for Both CKI and LDP.................................................................................. 76
12.1.5 For an Initialized LDP Flight not Connected to CKI ................................................................... 76
13. LDP Messages .............................................................................................................................. 77

13.1. Movement Message (MVT)................................................................................................................... 77
13.2. MVT Error Responses .......................................................................................................................... 81
13.3. Manually Sending LDP Messages ........................................................................................................ 82
14. LDP Message Address Table ......................................................................................................83

14.1. LDP Airport Information Display (LAID) ................................................................................................ 83
15. Flight Journal History .................................................................................................................. 85

15.1. Help Screen Display (FJ/H)................................................................................................................... 85
15.2. Display Flight History Journal (FJ) ........................................................................................................ 86
15.3. FJ LDP Codes....................................................................................................................................... 88
16. Check List for Last Minute Changes ..........................................................................................89

16.1. LMC For Passengers With Baggage..................................................................................................... 89
16.2. LMC for Cargo and Mail Only................................................................................................................ 89
16.3. LMC for Fuel ......................................................................................................................................... 89
17. Load Planning Check List ........................................................................................................... 91

17.1. Initial Check Lists .................................................................................................................................. 91
17.2. Print Loadsheet / Send Departure Messages / Release Flight Control ................................................. 92
18. Glossary ........................................................................................................................................ 93
19. Index .............................................................................................................................................. 97

Table of Contents
29 August 2008 – Revision 7.1 Page iii
List of Tables
Table 2.1 LCFD Screen Error Responses ............................................................................................ 4
Table 3.1 Flight Update Information Code Explanations ...................................................................8
Table 3.2 Flight Update Information Error Responses....................................................................... 9
Table 3.3 Insert Field Codes................................................................................................................ 11
Table 3.4 Example Reason Code TSTM .............................................................................................11
Table 3.5 Reason Codes...................................................................................................................... 12
Table 3.6 FIR Error Responses........................................................................................................... 14
Table 4.1 LFLD Error Responses ....................................................................................................... 15
Table 5.1 LODD Error Responses ...................................................................................................... 19
Table 6.1 LFFD Error Responses ....................................................................................................... 22
Table 7.1 ACARS Error Responses.................................................................................................... 28
Table 8.1 Restricted Cargo Codes...................................................................................................... 34
Table 8.2 LDM Codes:.......................................................................................................................... 34
Table 8.3 LPAD Error Responses....................................................................................................... 35
Table 8.4 LALD Error Responses ....................................................................................................... 40
Table 8.5 LOLD Error Responses....................................................................................................... 41
Table 9.1 LFSD Error Responses ....................................................................................................... 49
Table 10.1 LLSP Error Responses ..................................................................................................... 59
Table 11.1 LFIX Error Responses....................................................................................................... 61
Table 13.1 MVT Error Responses ....................................................................................................... 81
Table 15.1 Flight Journal LDP Error Responses ..............................................................................88

List of Tables
29 August 2008 – Revision 7.1 Page v
List of Tables
Page vi 29 August 2008 – Revision 7.1
Revision History
Revision Date Changes
6.0 1 Jun 2006 Added:

• Crew Screen to Section 23.
• ACARS section 7.5.
• ACARS to FJ section 15.3.
• documentation changes in Section 5 for software revisions.
• Index.
6.1 5 Jun 2007 Rebranded.
7.0 29 Jun 2007 Customer Release.
7.0.1 07 Jul 2008 Section 4 List of Active Flights revised, other options added.
7.1 29 Aug 2008 Customer Release.

1. Introduction
1.1. General Information
This User Guide describes the main SDCS load control functions and entries required for a load
control specialist to carry out their normal duties. For additional Load Planning entries, please see the
SDCS Database User Guide.
Note: This User Guide is designed as a training guide to support the SITA DCS LDP system.
1.2. Course Objectives

This course is designed for Airline Load Control agents and supervisors. These people should have
previous knowledge of either producing manual load sheets, or producing automated load sheets from
another system.
The course has five main objectives:
1. Give the load control agent/supervisor a clear understanding of all the basic load control functions
and entries with expected system responses.
2. Produce load planning instructions for both containerized and non-containerized aircraft, and add
any special cargo notifications for departure messages as required.
3. Close a flight and make any necessary trim adjustments to produce final load sheet for on-time
departure.
4. Dispatch all LDP departure messages at the end of the flight.
5. Handle any late aircraft version or type changes with least disruption to the passengers.

Introduction
29 August 2008 – Revision 7.1 Page 1
Introduction
Page 2 29 August 2008 – Revision 7.1
2. Manual Flight Creation
2.1. Manual Flight Creation (LCFD)
The LCFD (LCFU) transaction creates or updates a flight schedule in the Load Planning System. The
LCFD transaction will either display a filled-in format of an existing flight or display a fill-in format to
enter flight information for a new flight.
The Load Planning Create Flight Display (LCFD) displays a filled-in format, matching an existing
check-in flight schedule (BF:T or DFD) if the following requirements are met:
An aircraft registration number (ARN) matches the flight schedule’s (BF:T or DFD) equipment and
origin city entered via the FUI: transaction.
Load Planning application is initialized by use of the DPT transaction.
The Initialization is less than 24 hours before departure and not after departure times.
The entry is:
LCFD:FLIGHT NUMBER/DATE
1
LCFD:XS123/.
1 Blank LCFD Screen

LCFU: XS0123/20NOV DATE/TIME:
STN A/C CONFIGURATION ARVL DPTR GATE
ATL GDBAH F12Y96________ 1500 ________
MIA _________ ______________ 1630 _______ ________
____ _________ ______________ _______ _______ ________
____ _______ ________
Note: The entry number under DEFAULT-NBR-LEGS on the LADD: PARAM1 screen determines the
number of blank lines displayed (up to a maximum of 15). However, it is possible to ignore this default
and display the required number of legs by entering the number of legs after the date
(LCFD:XS123/./7).
The required basic entries are Routing, Aircraft Registration, Aircraft Configuration, Departure and
Arrival times. Gate number entries are optional.
1
LCFD:XS123/.

Manual Flight Creation
Response and Entry:
LCFU: XS0123/20NOV DATE/TIME:
STN A/C CONFIGURATION ARVL DPTR GATE
ATL GDBAH F12Y96________ 1500 ________
MIA _________ ______________ 1630 _______ ________
____ _________ ______________ _______ _______ ________
____ _______ ________
Transmit from last character entered and the response should be 'ACCEPTED'.
2.2. Error Responses

Response Explanation
AIRCRAFT Not a valid registration for this airline.
AIRLINE This airline is not created in the database.
AIRPORT This airport is not created in the LAID screen for LDP.
ARR/DEP Invalid or missing arrival/departure time.
CONFIGURATION Not a valid configuration for this aircraft registration.
CONFIGURATION RECORD NOT Class totals do not match configuration in LAFD:PAX1-5

COMPLETE screens database.
DISPLAY/UPDATE NOT ALLOWED User not authorized to create this entry for another station.
FLT/DATE Airline date not active in LDP or is an invalid entry.
FLT RELEASED Flight has been released to next station.
FORMAT Input format other than as specified.
FUNCTION Invalid entry code.
Table 2.1 LCFD Screen Error Responses

Manual Flight Creation
3. Flight Data Display
3.1. Configuration Table Display (CND:A)
This screen provides a one-line summary list, in numeric order, of all the aircraft types / configurations
created in the CND table. This table number is used when building schedules (BF:T or DFD) to
identify which aircraft type and configuration to create. This display contains all the aircraft
configurations created in the system for the Host carrier as well as for any handled carriers. The entry
is:
CND:A
Response:
CND:A
1 XS 767 A F/12 C/63 Y/126
2 XS TU3 A YMTL/76
3 SU TU3 B YLM/76
5 BA 737 A C/12 M/94
7 BA 737 B C/12 MKL/94
8 LH 737 C C/12 M/88
12 OS DC9 A F/8 Y/96
Explanation:
The system will display a full page of all the numbers used, in numeric order. If any number is not
used, it is omitted from the list. It also gives the Airline, the aircraft type and version. The last column
gives the Master class (plus any equivalent classes) and the number of seats in that class. To move
to the next page, enter PN (or NP) after the cursor position.
It is possible to start a display from a specific CND number. The entry is:
CND:R/NUMBER
1
CND:R/78
It is possible to display a specific table number. The entry is:

CND:NUMBER
CND:8
It is also possible to display the list by particular aircraft type.

The entry is:
CND:A/AIRCRAFT TYPE
It is also possible to display the list by particular Airline and / or aircraft type.
The entry is:
CND:AIRLINE/A
or
CND:AIRLINE/A/737

Flight Data Display
Response (CND:BA/A/737):
CND:BA/A/737
5 BA 737 A C/12 M/94
7 BA 737 B C/12 MKL/94
12 BA 737 C C/18 MKL/88
13 BA 737 D C/24 MKL/82
14 BA 737 E C/36 MKL/70
28 BA 737 F C/58 MKL/48
32 BA 737 G C/70 MKL/36
3.2. Aircraft Registration Data Display (LACD)

The LACD: gives a list of aircraft registrations created for an airline in the system database. Aircraft
registrations may be displayed for an airline's entire fleet or for a specific fleet. It is possible to have
many pages of aircraft registrations, and any page may be accessed by adding the page number at
the end of the transaction.
The entries can be:
LACD:AIRLINE
LACD:AIRLINE/FLEET
LACD:AIRLINE/2
Response of LACD:XS
AIRCRAFT REGISTRATION NUMBERS FOR AIRLINE XS

REG # FLEET DATE * REG # FLEET DATE
GABBL B727-100 18APR89 * GBFAF B737A 24FEB90
GAFJK B727-100 02AUG89 * GJOLP B747-236 20DEC89
GCTYU B727-200 18APR89 * GOWYY B757C 01APR97
GBERT B737A 10JAN90 * GOWQD B757C 05MAY97
GBERT B737A 01AUG90
Explanation:
Field Explanation
REG # Aircraft registration or tail number. The system puts the aircraft in order of fleet and
date but not in alphabetical order. It is possible to have the same registration
entered twice with different effective dates.
FLEET Fleet type related to the registration.
DATE Date the aircraft registration became or becomes effective. Therefore it is possible
to create an aircraft registration in advance of its scheduled start of operation by
entering the advance effective date. This prevents using this registration before the
valid date. It is also possible to have the same aircraft registration entered with
different effective dates in the case where a known aircraft data change for that
aircraft will take effect on a specified date.
Note: When an aircraft registration is initially created, the year is left off the date.
This is added by the system during the 'nightly computer run' (this is activated every
night), when the system removes all unwanted records, and executes other
transactions.

Flight Data Display
3.3. Flight Data Display (FDD)
A flight data display may be entered for any flight that has been created by a schedule entry (BF:T) or
(DFD:). It either displays a Master flight (with a date range) or an Active flight (one date only),
depending on the date entered. The basic information displayed, apart from the flight number and
date, is the routing, departure and arrival times (in local time), the (T), CND table number (for
configuration), and the aircraft type and version.
1 A MASTER Flight (FDD:XS587/15MAR):

XS587 11FEB04 23MAR08 156 --MASTER--
ATL 1410 T-32 737/A
JFK 1635
IRREGULAR OPERATION DETAILS
SUPPLEMENTAL INFORMATION
Explanation:
Field Explanation
ATL Originating Station (with departure time of 1410). Copied from schedule.
JFK Next or Final Station (with arrival time of 1635). Copied from schedule.
T-32 CND Table Number for aircraft configuration. Copied from schedule
737/A Aircraft Type and Version. Copied from schedule.
1 Active Flight (FDD:XS587/.):

XS587 14FEB05 --ACTIVE--
ATL ADJ 1510 1/00 LATE T-32 737/A R:G-LMWP
JFK ETA 1735 1/00 LATE
IRREGULAR OPERATION DETAILS

ATL SURFACE WINDS
SUPPLEMENTAL INFORMATION
WINDS EXPECTED TO CALM BY 2100GMT
Explanation:
Field Explanation
R:G-LMWP Aircraft registration number. Entered via FUI: transaction.
ADJ 1510 / ETA 1735 Time adjustment from FIR: or FUI transaction.
1/00 LATE Hours and / minutes of schedule adjustment from FIR or FUI transaction.
IRREGULAR OPERATION DETAILS Location and reason for schedule adjustment. Entered via FIR
transaction.
SUPPLEMENTAL INFORMATION Entered via FIR transaction.
Note: The FDD may be updated via the LMVD / FUI / FIR transactions.

Flight Data Display
3.4. Flight Update Information (FUI)
Use this transaction to enter information such as aircraft registration, gate number, aircraft ramp/apron
position, new ETD times, and new CND table numbers (for change of configuration).
The entry is:
FUI:FLT NUMBER/DATE/ORIGIN CITY/CODE/DATA
To enter the aircraft registration GDBAH the entry would be:
FUI:XS587/./ATL/ARN/GDBAH
Note: The aircraft registration must be entered before LDP flight initialization. Also on transit flights
from non-DCS stations, the aircraft registration must be entered from the first departure station.
Other codes/data entered are:
Code Explanation
ETD/* 1 Enter New Estimated Time of Departure
ETA/* Enter New Estimated Time of Arrival.
CTN/* Enter New CND Table Number.
CTN/0 Return Flight to Original CND Table Number.
GATE/* Enter Gate or New Gate Number.
POS/* Enter Aircraft Position.
GATE/ERS Erase Gate Number.
ARN/ERS Erase Aircraft Registration.
POS/ERS Erase Aircraft Position.
RTNS Return To Normal Status (put Flight back to original characteristics).
OUT/* Actual Departure Time (must come before OFF).
OFF/* Actual Take-Off Time.
ON/* Actual Landed Time (must come before IN).
IN/* Actual Arrival Time (can be entered for all destinations).
NEWTMS/*/* New Estimated Departure/New Estimated Arrival Times. (These times will override
any times entered especially if mistake is made using LMVD message).
OT Returns Flight to ON TIME Status at your Station (Used with ETA or ETD).
Table 3.1 Flight Update Information Code Explanations

If a new ETD involves a day change then it can be entered via FUI with +1, for example:
FUI:FLT/DATE/STN/ETD/0100+1
Note: -RTNS deletes ALL changes made to the FDD display using the FUI, FIR or LMVD transaction.
Be very careful when using this transaction.
1 Codes followed by * require entry of a Time or Number.

Flight Data Display
3.5. FUI Error Responses
DISPLAY/UPDATE NOT User not authorized to display this entry for another station.
ALLOWED
SKED CHANGE The BF:T or DFD is being worked on and has not been activated
or ignored.
SYSTEM ERROR There is something wrong with this entry, either re-check the data
or contact SITA DCS Customer Support.
Table 3.2 Flight Update Information Error Responses
3.6. Flight Initialization (DPT)

Flights are initialized for LDP by first inserting the aircraft registration number (ARN) using the FUI
transaction, then by entering the following transaction:
DPT:
DPT:FLIGHT NUMBER/DATE
The response to this transaction is:
*** FLIGHT ACTIVATION MESSAGE SENT TO LDP ***
This does not mean the flight will be created for LDP as the information sent has to meet certain
criteria such as correct aircraft registration used or ETD is within 24 hours. Also this transaction may
take longer to complete because the entry creates an ASM message which the system sends
internally to the LDP application.
1 ASM Message:
HDQLDXS
.HDQFDXS
ASM
LT
NEW
XS587/14FEB05
J 737 F12Y96 GDBAH
ATL1410 JFK1630
Note: The 'DPT' transaction can only be entered for flights up to 24 hours before ETD.
After the DPT: transaction, you may verify the flight initialized in LDP by displaying the LCFD:FLT/.
Screen. If the flight is initialized a filled in screen is returned.
You may also request any other LDP display such as LFSD:FLT/. or LODD:FLT/. and the response
should be a screen display with the relevant information.

Flight Data Display
However if the response is 'FLT/DATE' or the LCFD: screen is not filled in the flight has not been
initialized. This could be for any of the following reasons:
1. No aircraft registration shown on the FDD screen.
2. Wrong aircraft registration entered and it does not match the CND/configuration displayed.
3. The aircraft registration is missing the configuration entry from the
LADD:AIRLINE/REGISTRATION/CONF.
4. The destinations entered are not created on the LAID:AIRLINE/DEST screens.
5. For some reason the ASM message did not get transferred internally to LDP, and instead went to
the reject queue.
If everything appears correct but the flight is still not initialized in LDP, it is possible to create
the flight manually using the LCFD:FLIGHT/DATE transaction. If the routing and configuration
entered via the LCFD screen matches the routing and configuration in Check-in, then the link between
Check-in and LDP is still established.
It is possible to check this by displaying the LFSD:FLT/DATE screen and check whether CKI = O
(OPEN) or U (UNABLE). If it is O it means it is linked.
If a second DPT transaction is required, for example, the LDP initialized schedule is canceled
(LFIX:FLT/DATE/CNCL) and now being reinitialized, the following transaction is required:
DPT:/$
Otherwise, the following response is returned if the DPT:FLT/. or DPT: entry is performed a second
time:
FLT activation message already sent - Use /$ to send RPL ASM.
Note: LDP initialization (DPT) will not connect LDP to CKI if the ARN is not entered from the origin
(first) station shown on the CKI schedule. The LCFD: schedule must match that of the DFD or BFT.
3.7. Flight Irregular Operations (FIR)

The FIR: transaction communicates flight irregular operation information, via the FDD display, to all
airline staff. Use this information for planning purposes, record keeping and customer service.
Note: The FUI and FIR transactions overlap on some transactions affecting the FDD: display.
Remember the FUI primarily updates flight times (IE out / off, on / in, ETD / ETA,) and ARN / gate
numbers.
The FIR updates information and times related to delays and diversions.
The entry is:FIR:FLIGHT/DATE
Response of FIR Entry:
FOU: XS827 / 28MAY /
ARR INFO DEP INFO INSERT REASON CTN R:GS-737
ATL/ / / / / T-10
LAX/ / / / /

Flight Data Display
1 Entering a Flight Delay 'REASON' Code and 'SUPPLEMENTAL INFORMATION':
ATL/ / 0030LT / / TSTM / T-10
LAX/ / / / /
HEAVY BAND OF THUNDERSTORMS EXPECTED TO CLEAR THE ATLANTA AREA BY 2100 GMT-ALL
Response of Returned Display after Transmission:

ATL/ / 030L / / TSTM / T-10
LAX/ 0030L/ / / THRU /
HEAVY BAND OF THUNDERSTORMS EXPECTED TO CLEAR THE ATLANTA AREA BY 2100 GMT-ALL
Explanation: ARR INFO / DEP INFO

Field Explanation
0030 hhmm Hours and minute.
L Late. Maximum value for a late time is 68 hours 15 minutes.
E Early (not shown in example).
T Time correction is applied to arrivals and departures for all downline cities. Used in
conjunction with L and E (LT or ET).
INSERT
The INSERT field contains codes that apply to either the codes in the REASON field or to the DCN
entry in the departure field. Inserts accepted for valid codes in the REASON field are:
Code Explanation
GMT 0200Z.
PSBLD Possible delay.
SUBJFD Subject to further delay.
NONE Clears the INSERT field for the city indicated (on same line).
Table 3.3 Insert Field Codes

REASON
Code Explanation
TSTM Reason for delay (Thunderstorms)
Table 3.4 Example Reason Code TSTM

These codes will appear on the FDD: display under IRREGULAR OPERATION DETAILS. The city associated
with the reason is also displayed.

Flight Data Display
The system accepts the following reason codes:
Reason Code Explanation Reason Code Explanation
ACCUM Accumulative PAS Passenger accommodation
ALTNOP Alternate Operation PD Possible diversion
APTCND Airport Condition PNOS Possible No Stop
ATC Air Traffic Control PSBLD Possible delay
ATCIN Air Traffic In PXLTN Possible Cancellation
ATCOFF Air Traffic Out Q Equipment
ATCWXF Air Traffic and WX QATC Equip due ATC
BQ Balance Equipment QMAINT Equipment Maintenance
C Connection QNEEDS Equipment Needs
CIQ Alternate Operation QTA Equip turn-around
CTA Crew turn around QWXF Equip due weather
CURFEW Curfew RC Ramp congestion
DCN Decision (see Supple- RDX Ramp damage

mental Information)
DEICG De-icing RTND Returned
FOFR See Remarks SI SFCWND Surface winds
FOG Fog SVS Servicing
FRZR Freezing rain THRU Late through
HLDG Holding THRUT Late through all downline
LDS Loading TSTM Thunderstorms
MAINT Maintenance WAF Winds Aloft
NONE No Reason Applies WTGTO Waiting take-off mini-mums
NOS No Stop WXAPT Weather/airport conditions
OLF Operating limits WXF Weather
ORIG Originating XLD Cancelled
Table 3.5 Reason Codes

Flight Data Display
CTN
T-10 CND Table number (Configuration) read from FDD display.
The CTN field contains the configuration table reference number (T-nnn) of the aircraft. This field is
supplied from the flight schedule or FUI entry and must agree with the aircraft registration number.
R:GS-737 ARN (Aircraft Registration Number) read from FDD: display.

Supplemental Information
At the bottom of the display there are a maximum of 14 lines of free format entries for the
'SUPPLEMENTAL INFORMATION'. This information will be displayed on the FDD:FLIGHT/DATE
display. Use the 'TAB' key to position the cursor at the correct start of entry for each line. Please note
that the maximum free format lines will decrease by one for every flight leg over four. Example: 4 flight
legs = 14 lines, 5 flight legs = 13 and 6 flight legs will have 12 lines.
Other FIR Input Examples and Explanations
NONE or NONET typed over an entry will clear it from the FIR screen. This is required for each
manually entered item on the screen. Remove extra characters with the space bar.
DCN. When an arrival or departure time for a transit city is not definite, this code is entered in the
Departure field of the transit city in question. The time a decision will be made or updated about the
departure time must be entered in the INSERT field. This example also shows PXLTN (Possible
Cancellation MIALAX).
FIR Entry Where Decision is Needed on Departure Transit City:
ARR INFO DEP INFO INSERT REASON CTN
ATL/ / 0100LT / / QMAINT / T-10 R:GS-737
MIA/ / DCN / 2200Z / PXLTN /
LAX/ / / / /
FIR Response to DCN Entry:

MIA/ 0100L / DCN / 2200Z / PXLTN / R:GS-737
LAX/ 0100L/ / / THRU /
In the following examples the INSERT field is used to show flight 300 is subject to a further delay.
FIR Entry:
MIA/ 0100L / DCN / 2200Z / PXLTN / R:GS-737
LAX/ 0100L/ / / THRU /
FIR Response:
FOU: XS300 / 07JUL /
ATL/ / 0100L / SUBJFD / QMAINT / T-2
MIA/ 0100L / / / THRU /
Error Responses

Flight Data Display
CITY Invalid CITY entered or missing.
IRR CODE Incorrect entry of REASON or INSERT code.
TIME Incorrect entry of time. The L may be missing.
NEED OUT TIME Attempted to set 'OFF' time before 'OUT' time.
NO CHANGE Entry ignored as not correct.
ORIGIN Attempted to set 'ARRIVAL' time for origin.
TIME REPEATED Attempted to set 'ESTIMATED' time after 'ACTUAL' time entered.
Table 3.6 FIR Error Responses

Flight Data Display
4. List of Active Flights
4.1. List of Active Flights in LDP (LFLD)
This screen display gives a list of the active flights in LDP for either the host airline or a handled
carrier. It displays the flights in creation order and not in numeric order.
The entry is:
LFLD: AIRLINE/DATE
1 LFLD:XS/.
►LFLD:XS/12FEB/ATL/1
FLIGHT NUMBER FLIGHT NUMBER FLIGHT NUMBER
0100 0576 0344
If there is more than one page of flights (it is possible to have up to a maximum of nine pages) to
display, it is possible to enter a (/) followed by the page number after the date
(LFLD:AIRLINE/DATE/3).
Other Options
LFLD:./ALL Displays all flights, including through flights
LFLD:XS/./MIA Displays flights out of MIA

AIRLINE This airline is not created in the database.
DATE Invalid date.
DATE OUT OF RANGE No flights are active for the date entered.
DISPLAY/UPDATE NOT User not authorized to display the entry for another station.
ALLOWED
FORMAT Incorrect entry format.
PAGE Invalid page number entered.
Table 4.1 LFLD Error Responses

List of Active Flights
List of Active Flights
5. Operational Screen Display
5.1. Operational Data Display (LODD)
This screen displays the operational data for the aircraft registration and comes from the
LADD:AIRLINE/REGISTRATION/CERT screen when the flight is activated. It includes:
number of cockpit and cabin crew
maximum take-off and landing weights
basic / dry operating weights and index
The entry is:LODD:FLIGHT/DATE
When the system finds the flight, the response displays on the screen.
1 LODU Display:
LODU:XS0100T/29NOV/BUDPRG A/C G-737 737 29NOV05/19:16:51
1 WEIGHT KG TEMP 0C___ ETD 2300 GATE CREW 2 _4
0
2 J/S ________________ ________________ ________________
3 ________________
CONF F12Y94 CPM ____________________ OTH
F12Y94______________
4 SPARE WHEEL N RAFTING N PANTRY Y
OEW-ADJ INDEX DESCRIPTION CREW COMPLEMENT

5 _____ _______ CATERING REQUIREMENT
6 DECK VERSION NONE
_____ _______ _________________________
7 _____ _______ _________________________
BASIC: WGT ___30075 IDX ___52.70 DRY OPERATION: WGT 30075 IDX 52.70
8
9
10 PWR/FLAP DECK VERSION __ __
11 RUNWAY ___ ___ _ ___ _ ___ _ ___ _ ___ _ PFD-LND-RNY 10L_
ATOGW _54204 ______ ______ ______ ______ ______ A-LND-WT __47624
12 MODE STD
LND-FLAP __
PREPARED BY: ________________
CHECKED BY: ________________ APPROVED BY: ________________

Operational Screen Display
Explanation:
Row Explanation
1.1 CREW. Any crew changes are entered here, and providing the corresponding crew complement is found
on the LADD:REGISTRATION/CREW, their weight and index adjustment is added to the DOW/DOI. The
first figure is for pilots, the second is for cabin crew, and the third is for any extra crew checked-in with
the code XXXCREW in check-in. XXXCREW only shows here after the CCL. The XXXCREW figure
adds the passenger weight to the OEW-ADJ /INDEX field and update the DRY OPERATION WT /
INDEX.
Note: If there is a change to the cockpit crew and the screen is inadvertently transmitted in
the empty field before the cabin crew figure, the system converts the cabin crew figure to 0
(zero) so be careful when updating this field.
If a crew change is entered on the LODD screen that does not correspond to the crew details on the
LADD/CREW screen, the system responds with a warning 'CREW NBRS DO NOT MATCH A/C
DATABASE'.
J/S. Names of up to four Jump Seat Passengers. These names must not be entered as JMP
passengers in the CKI application because the weight is processed differently. Here the
weight is added to the Dry Operating Weight / Index and in CKI the weight is included in the
Total Passenger Weight of the COM message. If the J/S passenger is entered in both
systems the weights would be doubled. See Section 11.5.
The response "JUMP SEAT COUNT EXCEEDS AIRCRAFT MAX" is returned if the J/S amount is more
than the number of service seats shown on the LADD:CERT screen.
2.2 CONF. Aircraft configuration is entered by the system.
CPM. Free format entry for the configuration code used in the CPM and LPM messages.
OTH. Whatever is displayed here is printed on the load sheet. It is a free format line so it is possible to
over-write the configuration with any specific airline configuration code as defined by the User.
3.3 Any entries on the LADD:REGISTRATION/EQUP screen are displayed here. If:
Y is entered, the weight and index of the selected item is added to the DOW/DOI.
N is displayed, the system ignores it.
4.4 It is possible to manually enter any weight and index with a description of a specific item not displayed
above.
5.5 BASIC WGT / DRY OPERATION WGT. The Basic Weight displayed here is actually the operating
weight, without crew or catering, for Basic weight carriers, and the operating weight, including crew and
catering, for DOW carriers. The Dry Operation weight is for any further adjustments such as crew and
catering for Basic weight carriers. It is possible to have the same figure displayed for Basic weight and
Dry Operation weight for DOW carriers if there are no adjustments.
The agent can change the BASIC WT and INDEX when the fields have underlines.
6.6 ADJ. +/- values used to adjust maximum TOW. These adjustments are the limiting value in the
remaining fields on this screen. This is a conditional parameter from PARAM1.
Reason. Displays with ADJ field. Enter the reason for the adjustment value in the ADJ field.
7.7 PWR FLAP. Not used.
DECK VERSION. Normally the LALD (automatic load planning) transaction for non-containerized aircraft
selects the most suitable deck version and displays the selected deck version number here. It is possible
to select a specific deck version for LALD by entering the required deck version number here.
8.8 ATOGW / A-LND-WT. Any restrictive adjustments to the take-off weight (TOW), or landing weight (LND-
WT), which must not be above the aircraft maximum (as entered on the CERT screen), can be entered
here.
9.9 MODE. Fuel management mode. STD indicates standard fuel loading and ALT indicates alternate fuel
loading.
CLIMB. Conditional parameter.
10.10 OTH LIMIT. Conditional parameter.
LND-FLAP. The setting of the landing flap.
11.11 PREPARED BY. Identity of agent that entered loading information.

Row Explanation
12.12 CHECKED BY. Identity of load planner.
APPROVED BY. Captains name.
5.2. Operational Screen Update (LODU)

The LODU code must be used when entering any changes. This is displayed after entering the
LODD:FLT/DATE transaction.
Note: After transmitting the LODU screen, the response is a re-display of the LODD screen with all
the lines removed. No further changes can be added to this screen, until the LODD:FLT/DATE is
transmitted again.
Note: Always transmit from the bottom of the LODU screen.

ACTIVE RECORD CHANGED Redisplay the screen before transmitting.

REDISPLAY
CK A-LND-WT Landing weight entered exceeds the MAX.
CK ATOGW Take-off weight entered exceeds the MAX.
CK DECK VERSION Invalid deck version entered.
CK T/O Invalid take-off adjustment.
DISPLAY/UPDATE NOT ALLOWED User not authorized to display the entry for another station.
FLIGHT RELEASED This flight leg has already been released.
FLT/DATE Flight not active in LDP.
REASON Adjustment entered without a reason.
WEIGHT Weight entry is missing or incorrect.
Table 5.1 LODD Error Responses

6. Fuel Screen
6.1. Fuel Screen Display (LFFD)
This screen allows the load control agent to manually enter the fuel figures for the flight. If the USE
HISTORY RECORD is set to Y on the PARAM1 screen, then the system updates the screen with the
same figures used the last time this flight operated, providing the destinations and aircraft types are
the same.
The entry is:
LFFD:FLIGHT/DATE
Example:
LFFD:XS978/.
Response of LFFD: XS978/. entry:

LFFU:XS978/17SEP ATL-MIA A/C GZGKL F12Y96 GATE
WEIGHT KG 737 ETD 2100 DATE/TIME 17SEP/1818
FUEL _ ARVL: _____ WEIGHT INDEX
ADD: 12000 MIN: 3000 FUEL BALLAST: ________________
RSRV: _____ MAX: 14400 WATER INJECT: ________________
TAXI: 300 SUG: ______ TANKERING ________________
_ B/O: 8700 TOF: 12000
TOTAL FUEL: 12300 CODE:STD DENSITY: 0.8
FUEL DISTRIBUTION:
TTL_WT TANK1 TANK2 TANK3 TANK4 CENTER R1 R2 R3 R4
REMARKS: ________________________________________________________________
FUEL DISTRIBUTION NOT FOUND
6.2. Fuel Screen Update (LFFU)

The normal entries that are updated are the ADD (additional) and B/O (burn-off) fields. The ARVL
(arrival) is only used if the flight has come from a previous DCS automated station, and the RSRV
(reserve) is only used if there is a known amount to be used as reserve fuel. The taxi figure comes
from the LADD:AIRLINE/REGISTRATION/CERT screen.
Note: It is possible to enter a different taxi fuel weight, more or less than the standard figure.
The system always displays the CODE as STD (standard fuel). If the alternate fuel table is required
then enter ALT in place of STD. The alternate fuel table must be available in the database.
If FUEL BALLAST, WATER INJECT, or TANKERING (excess fuel carried but not needed to operate
the flight) is used then the amount (weight) and index adjustments are manually entered under
WEIGHT and INDEX.
The FUEL DISTRIBUTION is not used unless a fuel sheet printout is required, and then this
distribution must be created in the database through the LFDD screen.
The response to any update on this screen will be the free format message for FUEL DIST WARNING
entered on the LLAL:PARAM2 screen.
Also whenever the fuel figures are adjusted (perhaps to accommodate more payload), this adjustment
is not reflected in check-in (SDD:FLT/DATE) until the LPAD:FLT/DATE/CGO screen has been re-
transmitted.


Fuel Screen
ACK - FUEL Fuel was changed after load sheet was issued.
DISTRIBUTION NOT FOUND REGEN Re-print the load sheet.

LOADSHEET
ACTIVE RECORD CHANGED REDISPLAY Redisplay the screen before transmitting.
ALT AIRCRAFT DATA REQUIRED ALT information missing in LADD:COG5 screen.
INDEX REQUIRED Enter the missing index, even if 0.
CODE Incorrect code, must be STD or ALT.
DISPLAY/UPDATE NOT ALLOWED User not authorized to display the entry for another
station.
FLIGHT RELEASED Update not allowed as flight released.
INCORRECT ADD OR ARRVL FUEL The sum of the fuel is less than the minimum fuel.
INCORRECT B/O B/O is greater than or equal to the minimum fuel.
INCORRECT TAXI Taxi fuel is greater than on CERT screen.
INVALID DENSITY Invalid density table is not in the SDCS Database.
PAYLOAD EXCEED BY */KG The fuel entered exceeds the payload by the
amount specified.
TOTAL FUEL The sum of total fuel exceeds the maximum fuel.
EXCEEDS A/C MAX WEIGHT Invalid weight entered for the aircraft.
Table 6.1 LFFD Error Responses

Fuel Screen
7. Passenger Payload Screens (LPAD)
7.1. Passenger Area Seating Display (PAX)
This Load Planning Payload Available Display (LPAD) screen gives the total passengers checked-in
by class and gender, and also displays the area seating distribution.
The entry is:
LPAD:FLIGHT/DATE/PAX
1 LPAD:XS198/./PAX Entry:
LPAU:XS198/14FEB__PAX ATL_LAX A/C GSTWL C58M48 ETD 1505
WEIGHT KG B737-236
LFSD _ GENDER REQD Y ALT WGTS N
M F C I T
AVG PSGR WGT: 78 68 43 10
PASSENGERS: C 23 3
M 17 21 1 _
TTL 40 24 1
0A 0B 0C
COMPARTMENT CAPACITY: 30 46 30
COMPARTMENT COUNT: 11 30 24 USE Y
COMPARTMENT DISTR: 13 27 25
PAYLOAD REMAINING: 37427 AVERAGE BAGGAGE WGT: 14
CARGO SPECIAL HNDLG: _______________________________________
REMARKS: _______________________________________
Explanation:
If a Y is entered beside LFSD, the system displays the LFSD screen requested after the transmit key
is pressed.
If the flight is Non-Gender, then A (adults) will be displayed in place of M and F. C and I provide the
Child and Infant passenger counts, and T designates the Transit passenger count. The AVG PSGR
WGT is used when there is no interface between LDP and CKI. When LDP is interfaced with CKI, the
passenger figures are added to this screen. In this case the only item that can be changed is the
AVERAGE BAGGAGE WGT for load planning, and any change to this item is displayed on the
LPAD:FLIGHT/DATE/PAX3 screen.
If the flight is not connected to check in, then a field ALT_WGTS displays next to GENDER. This is
followed by Y or N to indicate if passenger weights are modified from the standard weight.
The COMPARTMENT CAPACITY is the maximum number of seats in each cabin zone.
The COMPARTMENT COUNT is the actual cabin seating of the checked-in passengers from the CKI
seat map. The COMPARTMENT COUNT includes transit passengers updated via the SOM.
The COMPARTMENT DISTR is the computer suggested trim for passengers. The COMPARTMENT
DIST includes transit passenger updated via the LDM.

Passenger Payload Screens (LPAD)
If the flight is out of trim at the last minute, and it is too late to move cargo, it is possible to ask some
passengers to move to a different cabin area, 'cut the link' with CKI (on the LFSD:FLIGHT/DATE
screen), and manually over-ride the COMPARTMENT COUNT on this screen, by entering Y in place
of N beside 'USE', and enter the new cabin area seating distribution to get the flight back into trim.
This is only recommended if there is no alternative solution, and to minimize any flight delay.
For LDP flights that are not 'LINKED' with CKI, the passenger details are manually entered so they will
be displayed on the load sheet under the balance conditions with the area seating and the passenger
figures on the LDM.
7.2. Passenger Transit Details (PAX1)

This screen is only used on a transit flight. The figures can either come from the LDM of a non-
automated station or they can be manually entered. If the flight is 'LINKED' upline to DCS, the figures
will appear here. Even though a LDM may have been received, the passenger transit figures can be
manually adjusted on this screen if required (if the response is 'UPDATE NOT ALLOWED', check
Section 11.3 under LDM for explanation).
The entry is:
LPAD:FLIGHT/DATE/PAX1
Response of LPAD:XS927/./PAX1:
LPAU:XS927/19JAN05/PAX1 ATL_SFO A/C GDLPT F12Y96 ETD 1900
WEIGHT KG B737
*****TRANSIT*****
PAX BY GENDER SEATS OCC. BY CLASS TOTALS
DEST M F C I F Y
SFO 15 8 1 1 2 2 24
TOTALS 24

7.3. Passenger Checked-In Display (PAX2)
This screen displays the checked-in passengers and their baggage. If the flight is 'LINKED' with CKI,
the figures are updated as the passenger's check-in. Any attempt to manually amend these figures
gives the response 'CHECK-IN LINK OVERRIDES'.
Note: If the PARAM1 screen displays CKI-OVERRIDE = Y, the passenger figures can be amended
after the flight has been CLOSED for Check-in. Remember to update the PAX screen so both sets of
figures match.
If the situation arises where these figures need to be amended, the 'LINK' with CKI can be cut on the
LFSD:FLIGHT/DATE screen (CKI = M). The new passenger figures can be entered on the
LPAD:FLIGHT/DATE/PAX2 and PAX screens (these must match).
If connected to check-in this will show the number of booked passengers that still need to be checked
in.
The entry is:
Response for PAX2 Screen:
LPAU:XS927/20MAR05PAX2 ATL_JFK A/C GALPR F12Y96 ETD 1245
WEIGHT KG B737
*****CHECKED*****
PAX BY GENDER SEATS OCC. BY CLS TOTALS BAG WEIGHT
DEST M F C I F Y PREF OTHER TRANS
SFO 24 12 3 1 8 31 39 80 420 60
TOTALS 39 80 420 60
Explanation:
The BAG WEIGHT is split into three groups. The PREFERD bag is the amount of baggage for the
class defined on PARAM1 for PREFERRED CLASS and is for the first class bag container on non-
containerized aircraft (if no class is defined here then all the baggage apart from TRANSFR goes to
OTHER). The TRANSFR bag is the amount of baggage for passengers in any class who are
transferring onto another flight at the transfer point of this flight. OTHER is the remainder of the
baggage not included in either PREFERD or TRANSFR.
If connected to check-in the shows the number of booked passengers that have not checked in.
Note: If the bag weight has to be changed, once a flight has CLOSED for both CKI and LDP, the new
bag weight should be entered under 'ACTWGT' on the LPAD:FLIGHT/DATE/CGO screen and not
here.

7.4. Passenger Booked Display (PAX3)
If this flight is 'LINKED' with CKI, the BOOKED passenger figures are entered from the PNL. If it is not
'LINKED' to CKI, these figures can be entered manually and changed as required.
The entry is:LPAD:FLIGHT/DATE/PAX3
Response of PAX3 Screen:
LPAU:XS927/17JUN06/PAX3 ATL_JFK A/C GAWLT F12Y96 ETD 1245
WEIGHT KG B737
*****BOOKED*****
PAX BY GENDER SEATS OCC. BY CLS TOTALS BAG WEIGHT
DEST M F C I F Y PREF OTHER TRANS
SFO 21 9 4 1 5 29 34 70 280 126
TOTALS 34 70 280 126
Explanation:
If the estimated bag weights do not appear, it is possible to enter some estimated bag weights by
displaying the LPAD:FLIGHT/DATE/PAX screen and changing the AVERAGE BAG WGT. Then
transmit from the bottom of the screen with the weight entered. Check the PAX3 screen again and the
estimated bag weight should now be displayed.
Note: If the estimated baggage does not appear on the LPAD/PAX3 screen check the following:
Is it a transit flight? If the station attempting to get the estimated baggage is not the first station on the
routing, it is not possible to display the estimated baggage.
Is the flight connected to CKI? If not, the estimated baggage has to be manually added, as
transmitting of LPAD/PAX screen will not work in this condition.
What CW table has been used for this flight? Ensure the planning weight (the figure after the date) is
higher than the average Passenger or Male weight.
What is the estimated ZFW weight on the flight? If the estimated ZFW is less than the first (minimum)
figures entered on the LADD/COGS or COG2 screen, this will cause the problem. Amend these
screens to the aircraft BW or DOW weight and everything should work correctly.
As passengers check-in, the passenger and baggage figures transfer from the PAX3 screen to the
PAX2 screen. This enables the load control agent to see how many passengers and baggage are
checked-in, and how many are left to check-in, at any time during the flight LPAD(CGO1).

7.5. ACARS Loadsheet Information
This transaction displays the ACARS loadsheet information.
Entry:
LACS:FLIGHT/DATE
If this transaction is attempted before any fuel is entered on the LFFD:Flight/Date screen or there is
unallocated payload on the LPAD:Flight/date screen then the response is either ‘NO TRIP FUEL’ or
‘UNALLOCATTED PAYLOAD’. The load control agent must first enter the fuel and/or payload details
before requesting the display.
Response (LACS:XS123/.):
LACS:XS123/31MAY / ATL MIA ACARS PRELIM
LOADSHEET
ATL MIA G-737 02/04
ZFW ACT 30075 MAX 43091
TOF 9800
TOW ACT 39875 MAX 54204
TF 4500
LAW ACT 35375 MAX 47624 L
UNDERLOAD 12249
PAX 0/0 TTL 0
BALANCE AND SEATING
BI 52.70 DOI 52.70
LILAW 48.28 MAXLAW 22.25
LIZFW 52.70 MACZFW 26.44
LITOW 51.49 MACTOW 23.45
DLI 52.70 DLMAC 26.44
STAB TO 00.2
PRELIM/FINAL: __ (P OR F)
If a ‘Prelim’ ACARS load sheet is required, then enter ‘P’ in the ‘PRELIM/FINAL’ field.
The ACARS load sheet is sent to the address specified on the LLAL:PARAM2 screen. If a PID
number is specified on the ‘Load Sheet Printer LDPP’ field of the DPID screen, then a copy of the
ACARS load sheet will also be sent there.

Response of a ‘Prelim’ ACARS load sheet to PID number:
DVC- 2189 1406 31MAY05
LOADSHEET PRELIM 1406 02
XS123/ 31MAY05
ATL MIA G-737 02/04
ZFW 32399 MAX 43091
TOF 9800
TOW 41899 MAX 54204
TIF 4500
LAW 37399 MAX 47624 L
UNDLD 10225
PAX/5/15 TTL 20
BI 52.70
DOI 52.70
LILAW 44.24
MAXLAW 19.56
LIZFW 48.54
MACZFW 22.91
LITOW 47.65
MACTOW 21.10
DLMAC 27.49
DLI 54.52
STAB TO 00.1
;
Note. The information listed after ‘PRELIM’ indicates the time of the request in ‘GMT’ (not local) and
the version number of the request.
If a ‘FINAL’ ACARS load sheet is required, then enter ‘F’ the ‘PRELIM/FINAL’ field. The same display
is sent to the system address except that ‘PRELIM’ is replaced by ‘FINAL’.
Note: Once a ‘FINAL’ ACARS load sheet has been requested and sent, it is no longer possible to
send another.
Also, if a flight is re-opened and the ‘LACS’ entry is attempted, the response is ‘Flight Not Closed’.
Once the flight is closed again, the ‘LACS’ entry can be used but without the options ‘PRELIM/FINAL:
__ (P OR F)’ being displayed on the screen.

FORMAT Incorrect entry.
GENDER ADULT Gender indicator must be Y or N.
GENDER/CLASS COUNTS NOT Passenger counts by gender must equal counts by class
EQUAL for each destination.
ILLEGAL CHAR Character entered was not a Y.
INVALID COMP COUNT Passenger count per compartment must equal the
passenger count per class for this compartment.
Table 7.1 ACARS Error Responses

7.7. Payload Available Display - Miscellaneous (PAX4)
The screen is designed for the display of EXTRA CREW by class, DEADHEAD CREW BY CLASS,
SEATS BLOCKED FOR A STRETCHER (by row and total blocked), and REMARKS. The Remarks
field will be included in the Load Message (LDM) for the PAX4 destination.
The entry is:
LPAD:FLIGHT/DATE/PAX4/DEPARTURE STATION
LPAD:FLIGHT/DATE/PAX4/DEPARTURE STATION
LPAU:XS100/21FEB/PAX4___ATL_ MIA A/C G-737 C12M94 ETD 2300

WEIGHT KG 737 DATE/TIME: 21FEB03/15:30:43
****** MISC *****
XCR BY CLASS DHC BY CLASS STRETCHER
DEST C M C M ROW BLKD REMARKS
MIA __ __ __ __ __ __ _________________________
SJU __ __ __ __ __ __ _________________________
7.8. Payload Available Display - Transit Miscellaneous1 (PAX5)

The screen is designed for the display of Miscellaneous information at the transit station. The display
provides the following information to the transit station by class and destination: EXTRA CREW,
EXTRA SEATS and PADS.
The entry is:
*****TMISC-1*****
XCR BY CLASS XST BY CLASS PADS BY CLASS DHC BY CLASS
DEST C M C M C M C M
MIA __ __ __ __ __ __ __ __

7.9. Payload Available Display - Transit Miscellaneous2 (PAX6)
This display provides the following information to the transit station by destination: STRETCHER
BLOCKED SEATS by row and total, JUMP-SEATS, UNACCOMPANIED MINORS, WHEEL CHAIRS,
PETS IN CABIN (PETC) and ALIVE ANIMALS IN HOLD (AVIH).
The entry is:
*****TMISC-2*****
STRETCHER JMP UM WCH PETC AVIH
DEST ROW BLKD
MIA __ __ __ __ __ __ __

8. Cargo Payload and Load Distribution Screens
8.1. Load Distribution Screen (CGO1)
The load distribution screen is used for entering the baggage, cargo, and mail details, plus any transit
load from a previous non-mechanized station. The screen response is the same for both
containerized and non-containerized aircraft, with the exception that on non-containerized aircraft the
type of pallet or container must be added, with the serial number of the container/pallet. (If the serial
number is not entered then that container/pallet information will not be transmitted on the UCM
message at the end of the flight.)
The entry is:LPAD:FLIGHT/DATE/CGO1
Note: If the DEFAULT-PAYLOAD-DISPLAY on the PARAM1 screen is set to CGO then it is possible
to enter just LPAD:FLIGHT/DATE
1 LPAD:FLT/./CGO1 for Non-containerized Aircraft:

LPAU:XS227/03MAR06/CGO1 ATL_JFK A/C GKKGA F12Y96 ETD 2030
WEIGHT KG B737
LFSD:__ LPDD:__ CUMULATIVE CHECKS: Y
PAYLOAD REMAINING: 2506 STATUS FINAL
DEST ACTWT ESTWT TYPE SERIAL CONT POS / PRI RESTRICT CARGO DST
JFK 220 220 C 1 A01 RRY/RPB________ __
JFK 388 600 B 2 A01 _______________ __
JFK 360 360 M 4 A01 _______________ __
JFK 260 260 B-T 2 A01 _______________ __
The T after B (B-T) indicates that this is a Transit flight, and this is the Transit Bag from a previous
station.
Response for Containerized Aircraft:
LPAU:XS883/03MAR06/CGO1 ATL_JFK A/C GSTWA F18Y250 ETD 2030
WEIGHT KG DC10
LFSD:__ LPDD:__ CUMULATIVE CHECKS: Y
DEST ACTWT ESTWT TYPE SERIAL CONT POS / PRI RESTRICT CARGO DST
JFK 1180 1180 C UAK9557XS P1P 11P A01 RRY/RPB_________ ___
BOS 360 360 B AVE9933XS LD3 31R A01 ________________ ___
BOS 280 600 FB AVE7438XS FRCL 31R A01 ________________ ___
JFK 650 650 M AVE6924XS LD3 33R A01 ________________ ___
BOS 478 478 M AVE2982XS MIXD 33R A01 ________________ ___
JFK 600 600 S AVE1464XS LD3 32R A01 ________________ ___

Cargo Payload and Load Distribution Screens
For containerized aircraft, the estimated baggage figures are entered under ESTWT and the required
hold position under POS. The system does not allow the entry of the same POS more than once
except by using the displays of SORT (used as a last minute container for a mixture of B, C, or M),
FRCL (mixture of normal and First class bag), and MIXD (used for a mixture of destinations) entered
under CONT.
SORT Mixed Cargo/Baggage Same or Different Destination

MIXD Same Type Cargo Same or Different Destination
FRCL Mixed Baggage Same Destination
The agent has to manually plan the trim, and can check the result on the LPDD:FLIGHT/DATE screen.
If the required trim is achieved, then a loading instruction can be issued. The actual cargo and mail
figures are entered under ESTWT and ACTWT. If the flight is interfaced with CKI, the actual bag
figures appear under ACTWT.
Any restricted cargo codes are entered under RESTRICT CARGO codes but only the code is entered
not the weight. There is a maximum entry of five restricted cargo codes per line.
The following table displays the restricted codes that can be entered. The last column (ID) indicates
the information required when entering the details for the LDM on the LMSD:FLIGHT/DATE/LLDM
screen in IATA format.
H Hold position only.
H/W Hold position and weight.
H/I Hold position and index (for radioactive material).
C/C Number of passengers in each class.
S/W Number of seats occupied and weight.
S/C Number of seats occupied for stretcher and number of passengers traveling by class.
Code Description LDM Format ID
AOG Urgent A/C Spares .AOG/1 H
AVI Live Animal in the aircraft Hold .AVI/4 H
BAL Ballast .BAL/3/1000 H/W
BIG Item Loaded over two Pallets .BIG/11P12P/1567 H/W
COM Company Mail .COM/2/15 H/W
DIP Diplomatic Mail .DIP/2 H
EAT Foodstuffs .EAT/1 H
EIC Equipment in Compartment .EIC/5/120 H/W
FIL Undeveloped Film .FIL/3 H
FKT Flight Kit .FKT/1/75 H/W
HEA Heavy Item .HEA/1/196 H/W
HEG Hatching Eggs .HEG/22P H
HUM Human Remains in Coffin .HUM/4/258 H/W
ICE Dry Ice .ICE/11R H

LHO Live Human Organs/Blood .LHO/2 H
MAG Magnetic Material DO NOT PUT ON LDM
NIL No Items Loaded .NIL
OBX Obnoxious Dead Load (Smelly) .OBX/6 H
OHG Item Overhanging Two Pallets .OHG/EF/G100 H/W
PER Perishable Cargo .PER/2 H
RCL Cryogenic Liquid .RCL/5 H
RCM Corrosive Material .RCM/2 H
REX Normally Forbidden Explosive .REX/1 H
RFG Flammable Compressed Gas .RFG/3 H
RFL Flammable Liquid .RFL/2 H
RFS Flammable Solid .RFS/2 H
RFW Dangerous when Wet .RFW/12P H
RHF Harmful - Stow Away from Food .RHF/6 H
RIS Infectious Substance .RIS/43R H
RMD Miscellaneous Dangerous Goods DO NOT PUT ON LDM
RNG Non-Flammable Compressed Gas .RNG/1 H
ROP Organic Peroxide .ROP/2 H
ROX Oxidizing Material .ROX/4 H
RPB Poison .RPB/2 H
RPG Poisonous Gas .RPG/5 H
RRW Radioactive – White Label DO NOT PUT ON LDM
RRY Radioactive - Yellow Label .RRY/1/6 H/I
RSB Polystyrene Beads .RSB/23L/95 H/W
RSC Spontaneously Combustible .RSC/4 H
RXB Explosives 1.4B .RXB/1 H
RXC Explosives 1.4C .RXC/7 H
RXD Explosives 1.4D .RCD/2 H
RXE Explosives 1.4E .RXE/6 H
RXG Explosives 1.4G .RXG/3 H
RXS Explosives 1.4S .RXS/5 H

VAL Valuable Item DO NOT PUT ON LDM
WET Wet Material (e.g., Fish in Ice) .WET/11P H
XPS Priority Small Package .XPS/1 H
Table 8.1 Restricted Cargo Codes

In addition to the above codes, DCS also adds the following codes to the LDM, when the flight is
connected to CKI:
BED Stretcher Installed .BED/6/1Y S/C
PAD Passenger Available for Disembarking .PAD/0/3 C/C
SOC Seat Occupied by Cargo .SOC/2/95 S/W
XCR Crew Occupying Passenger Seats .XCR/0/3 C/C
Table 8.2 LDM Codes:

For non-containerized aircraft the estimated and actual cargo and mail figures are entered under
ESTWT and ACTWT. The serial numbers of the ULDS are entered under SERIAL (it is important that
the same serial number is not entered twice otherwise this will cause a problem to the LALD
transaction), and the type of pallet or container is entered under CONT. There is no need to enter any
positions as the LALD (automatic load planning) program will work out the best trim. The agent can
either accept the trim or manually change it as required.
Note: The loading instruction figures come from the ESTWT figures, and the loadsheet figures come
from the ACTWT figures.
The available TYPES of cargo codes are defined by the Airline on the PARAM1 screen. However the
most common ones are B for baggage, FB for first class baggage container (wide body aircraft only),
C for cargo, M for mail, S for sort container (wide body), TB for transfer baggage (wide body), and X
for empty pallet or container (wide body). If the cargo code is followed by a T in the last position, this
means that it is transit load
The status priority codes are only used for non-containerized aircraft, although they are always
displayed as A01 on containerized aircraft screens. The A signifies automatic distribution, and an M
signifies a manual distribution. If for some reason the flight has too many pallets or containers, then
the system will display an O, signifying that this item has been off-loaded. The number after the status
signifies how full or empty that particular pallet or container is (0 = Full, 1 = 3/4 Full, 2 = 1/2, 3 = 1/4, 4
= Empty). Priority is currently not used but appears as 1.
The DST is for the final destination, and is only used if a particular pallet or container is being
transferred onto another destination at the end of this flight.
Change Baggage Weights on Non-Containerized Aircraft after Flight Close:
On a Non-containerized aircraft, once check-in is closed the LDP agent can change the baggage
weights on LPAD:CGO screens. Additionally, on non-containerized aircraft, if CKI and LDP are closed
and the CKI is reopened and more passengers are added and CKI is then re-closed with LDP then
reopened, a message will show on the LFSD: 'REOPEN CKI - ALLOCATE BAGGAGE'. CKI will have
to be reopened while LDP is open for the additional baggage to show in LDP.
8.2. LPAD:Flight/Date/CGO1 Error Responses

ACTIVE RECORD CHANGED REDISPLAY Screen was not re-displayed before entry.

AIRPORT Invalid airport code.
CARGO/MAIL NOT ALLOWED Only bag entry allowed in this position.
CGO STATUS CODE Status code must be A, M, or O.
CGO TYPE Type not defined in PARAM1 screen.
CGO WGT Weight is not numeric.
FORMAT Incorrect entry.
ILLEGAL CHAR Character entered was not a Y.
INVALID CONT Not a valid type for this aircraft.
INVALID EMPTY WT Cannot be less than the tare weight.
INVALID LDV/MDV POSITION Positions not defined for this deck version.
INVALID POSITION Position not valid for this aircraft.
INVALID VOL CODE Not used.
MAIN POSITION NOT FOUND Use of SORT/MIXD/FRCL is not preceded by ULD

type/position.
MAX POSITION WGT EXCEEDED Maximum weight for this position exceeded.
MAX WGT EXCEEDED Maximum weight for aircraft exceeded.
MAX HOLD WGT EXCEEDED Maximum weight for this hold exceeded.
NO SUCH RC CODE Not a valid restricted cargo code.
POS DUPLICATED Position already being used.
POSITION WEIGHT < TARE WEIGHT The estimated weight for this position must be equal
to or greater than the empty ULD weight.
PRIORITY Invalid priority, or missing.
SERIAL NBR Invalid serial number.
SORT NOT ALLOWED Sort container not allowed for this aircraft.
THRU INDICATOR The Thru (transit) must be T or blank.
Table 8.3 LPAD Error Responses
8.3. Trim Display (LPDD)

The trim display gives the estimated ZFW CG (zero fuel weight centre of gravity), the TOWMAC (take-
off) or LAWMAC (landing), along with the FWD/AFT CG limits. If the aircraft is nose or tail heavy, this
information also displays on the LPDD, with the difference in the actual percent MAC and the
FWD/AFT limit. It is not possible to update any data on this screen, as it is for display purposes only.
It is possible to see two different trims depending on which previous screen was displayed. If the
LFSD:FLT/DATE screen was previously entered, the system gives either an estimated or actual trim
depending on whether the flight is closed or open. If the LPAD:FLT/DATE/PAX screen was previously
displayed then the system will give a trim based on the area seating suggested by the system. This
may be different from the actual seating and explains why there might be a different trim from one
screen to another when nothing was added or changed. It is also possible for the agent to enter his
own passenger area seating and override the computer to see a different estimated trim.
The entry is:
LPDD:FLIGHT/DATE
Response for Non-Containerized Aircraft
LPDD:XS 2121 /21JAN /ATLMIA/2 A/C A-737 C12M94
WEIGHT KG B737 ETD 2000 GATE
PAX 000/000
POS DEST WGT TYPE PR SERIAL-NBR CONT-TYPE RESTRICTED CARGO
1 MIA 01000 C 01
4 MIA 00500 B 01
TOTAL WGT: 001500

ELAW (KG): 031574 FWD LIMIT CG: LAWMAC: 23.19 AFT LIMIT CG:
ETOW (KG): 031574 FWD LIMIT CG: 6.91 TOWMAC: 23.19 AFT LIMIT CG: 35.91
EZFW (KG): 031574 FWD LIMIT CG: 7.43 EZFMAC: 23.19 AFT LIMIT CG: 35.91
CARGO SPECIAL HNDLG:
REMARKS:
COG5 SCREEN EMPTY - DEFAULTS TO TOW COG
Note: The LPDD displays a message “LAW COG NOT FOUND” if no LAW limits are found, and
instead defaults to use the TOW limits.

Response for Containerized Aircraft
►LPDD:XS100/20FEB /ATLMIA/2 A/C GDACY Y363
WEIGHT KG DC10-30 ETD 1600 GATE
PAX 362
POS DEST WGT TYPE PR SERIAL-NBR CONT-TYPE RESTRICTED CARGO
31L MIA 00598 B 01 AKE
31R MIA 00598 B 01 AKE
32L MIA 00598 B 01 AKE
32R MIA 00598 B 01 AKE
33L MIA 00598 B 01 AKE
33R MIA 00598 B 01 AKE
34L MIA 00598 B 01 AKE
34R MIA 00598 B 01 AKE
35L MIA 00598 B 01 AKE
35R MIA 00403 B 01 AKE
TOTAL WGT: 005785

ELAW (KG): 166726 FWD LIMIT CG: 8.23 LAWMAC: 19.32 AFT LIMIT CG: 22.47
ETOW (KG): 199226 FWD LIMIT CG: 9.80 TOWMAC: 22.17 AFT LIMIT CG: 23.33
EZFW (KG): 154026 FWD LIMIT CG: 8.65 EZFMAC: 17.30 AFT LIMIT CG: 20.76
CARGO SPECIAL HNDLG:
REMARKS:
8.4. Cargo / Mail Allotments (LPCD)

This screen is used to enter any cargo or mail allotments for containerized aircraft only, when the
actual figures are not yet known, but a provisional automatic load plan is required. The entry is:
1 LPCD: for a Flight Operating ATL-JFK-BOS:

LPCU:XS127/28FEB05/1 CARGO/MAIL ALLOTMENTS PER SEGMENT
* CARGO * MAIL * EMPTY
SEGMENT BLK WGHT TP MP SP CNT BLK WGHT TP MP SP CNT TP MP SP CNT
ATL/JFK ___ 2000 __ __ 2 ___ ___ 600 ___ ___ 1 ___ __ __ __ ___
ATL/BOS ___ 1100 __ __ 1 ___ ___ 300 ___ ___ 1 ___ __ __ __ ___
JFK/BOS ___ 1500 __ __ 1 ___ ___ ___ ___ ___ __ ___ __ __ _1 ___
Explanation:
Field Explanation
BULK Volume (not weight) expected to be utilized in the BULK hold of the aircraft.
WEIGHT Allotted weight of cargo or mail for this flight.
TP/MP/SP Types of pallets (tall, medium, short) that are allotted for this flight. Normally tall or medium pallets
are only fitted on Main deck version aircraft; therefore only short pallets can be utilized for Lower
deck versions.
CNTR Number of containers allotted for cargo or mail on this flight.
EMPTY Use if there are empty pallets or containers.
Once the figures have been entered on this screen, the system can create a provisional automatic
load plan. Later on, once the actual figures for cargo and mail are known, then these should be
entered on the LPAD:FLIGHT/DATE/CGO screen, and the LALD transaction re-run.

8.5. System Selected Deck Version (LDVS)
The LDVS screen is used for containerized aircraft. Once the cargo, and mail figures and
pallet/container types have been entered on the LPAD:FLIGHT/DATE/CGO1 screen (or the allotments
added to the LPCD screen), then by displaying the LDVS screen, the system determines the best deck
version, and the number of pallets and containers to use for the cargo, mail, and estimated baggage
(providing the estimated bag figures are displayed on the LPAD:FLIGHT/DATE/PAX3 screen).
Entry:
LDVS:FLIGHT/DATE
LDVS Response:
XS558/28FEB ATL/JFK B767
DECK VERSION 30/10 MAIN DECK 0P, LOWER DECK 3P10A BULK 900
BAGGAGE CARGO MAIL

SEGMENT BULK ULDS BULK ULDS BULK ULDS
ATL/JFK 0 2100/5A 0 2250/2P 0 620/1A
REMARKS: THERE ARE 1P+4A EMPTY ULDS EX ATL

THERE ARE 1 FRCL CNTRS EX
8.6. Automatic Load Planning (LALD)

The known cargo/mail figures are entered on the LPAD:FLT/./CGO1 screen without specifying any
hold positions. When the LALD transaction is entered, the system locates the nearest valid deck
version for the number of PALLETS and ULDS needed, and then displays this outline on the screen.
Entry:
LALD:FLIGHT/DATE
LALD:FLT/DATE,F(For All Empty POS to be NOFIT)
LALD Response:
LUPD: (PAGE CMDS: EX, ST, DEL)
XS558/28FEB05 30/10 LOWER-DECK FWD=
_________________ _________________ ___________________
: JFK C : JFK C : JFK X :
: 1250KG : 1000KG : 140KG :
:P1P :P1P :P1P :
:UAK3886XS :UAK9557XS : :
: : : :
:_____________13P: 12P:_______________11P:
:____________ ____________ ____________ ___________ ____________
: JFK M : JFK B : JFK B : JFK X : JFK X :
: 620KG : 700KG : 700KG : 0KG : 0KG :
:LD3 :LD3 :LD3 :LD3 :LD3 :
:AVE4583XS : : : : :
:_________42L:__________41L:_________3L:________32L:_________31L:
: JFK TB : JFK FB : JFK S : JFK X : JFK X :
: 225KG : 130KG : 345KG : 0KG : 0KG :
:LD3 :LD3 :LD3 :LD3 :LD3 :
: : : : : :
:_________42R:________ 41R: 33R:________32R:_________31R:
Explanation:
The pallet or container contains information concerning the destination (JFK), the contents (C = Cargo,
M = Mail, X = Empty, B = Baggage, FB = First Class Baggage, TB = Transfer Baggage, S = Sort
Container), the weight of the contents, the ULD type (LD3 for container, P1P for pallet, etc.), the serial
number of the individual ULD (if entered on the LPAD:FLT/DATE screen), and the position number on

the aircraft. The blank lines on the display indicate where the door is fitted (12P and 41R in the above
example).
The transactions that can be entered with LUPD are:
Command Explanation
ST (STATUS) Displays IPC (the number of index pages, currently not used),
DPC (the number of data pages), and
CPN (the current page number).
It is possible to page through the data pages by entering the number of the page required
(example ►LUPD:2).
LOA (LOADING It is possible to get a teletype 'pictorial' printout of the LALD display sent to any address
INSTRUCTION) specified on the CGO (maximum of 5 addresses) line of the LAID screen by entering LOA
followed by the number (1 to 5) of the address required (Example LOA1).
EX (EXIT) Exits the ALD program (but does not release the program) so that the agent can
access other displays and can return to this same program by just entering 'LALD:'
(flight number is not required).
The response to ►LUPD:EX is 'PAGING PROGRAM TERMINATED'.
Note: EX or DEL must be entered before moving to another screen.
DEL (DELETE) It is very important that once ALD has been completed, that the program is
released correctly, otherwise DCS receives system errors if too many LALD
programs are left unreleased in the system. The entry is:
►LUPD:DEL
The response is 'PAGING PROGRAM TERMINATED - PAGE FILE RELEASED'.
Other transactions that can be performed on this screen are:
Transaction Explanation
SEL nn/nn Select a specific Deck Version.
NOFIT P NOFIT a particular position (or NOFIT ALL for all empty positions).
UPD Update and re-run the LALD program again.
USE P/I To use an off loaded Pallet or Container, or to move to a new position, using its index number.
MOV P1/P2 Move a Pallet or Container to new position.
SWI P1/P2 Switch a valid Pallet or Container position with another.
Note: The difference between MOV and SWI is that SWI is used when both positions are occupied
and a change is required, whereas MOV is normally used when moving from an occupied position to
an empty or NO-FIT position.

8.7. LALD: Flight/Date Error Responses
ACTIVE RECORD CHANGED REDISPLAY Screen was not redisplayed before the entry.
BULK HOLD NOT DEFINED BULK hold defined on the LADD:REG/CGO1 but
missing from LADD:REG/CGO(2-13) screen.
FORMAT/FUNCTION Incorrect entry or code not valid.
INVALID DECK VERSION Selected deck version not valid.
NO DECK VERSION AVAILABLE No deck version found for this fleet.
STATION Enter station code.
P1/P2 INVALID Invalid positions for SWI or MOV or type of

container/pallet differs.
POSN NOT SAVED IN DISPLAY MODE Check database as container/pallet position invalid or
position is not specified correctly on following screen
LADD:AIR/REG/ULDS or CGO1.
SYNTAX ERROR Wrong entry (space is required after the first entry).
Table 8.4 LALD Error Responses

8.8. Offload Display (LOLD)
The LOLD transaction displays a filled in format showing the distribution of cargo and baggage to the
various bin and container locations. The display can be requested from a downline station as the
output contains only the cargo/baggage that is to be offloaded at that station.
Note: For a through load display please use the payload distribution display (LPDD) discussed in
Section 8.3.
8.9. LOLD Error Responses

AIRCRAFT Unable to obtain the aircraft data.
AIRLINE Invalid airline code or airline is not in the system.
DATE The date is invalid.
DECK VERSION REQUIRED The deck version, if selected, is not available.
DISPLAY/UPDATE NOT ALLOWED Only the host airline is allowed access to data for another
airline.
FETCH RCODES-REC Internal database error.
FLEET The fleet identification is invalid.
FLT The input flight is not in the correct format.
FLT/DATE Flight/date not active or field is in error.
FORMAT Input format entered is not correct.
FUNCTION Function code is not valid.
IMPART ERROR Internal database error.
INDEX The page index is not numeric or is zero.
OPEN ERROR Internal database error.
PAYLOAD Unable to obtain the payload data.
STATION Invalid (City / Airport) Station code.
STATION NON MECH Offload display is not permitted for a non mechanized port.
SYSTEM PROBLEM Internal database error.
Table 8.5 LOLD Error Responses

9. Flight Status Screen
9.1. Flight Status Display (LFSD)
The flight status screen displays whether the LDP flight is open, closed, or released. It also displays
whether the flight is linked to CKI (O or C means the flight is linked, U or M means it is not), and if it is
still open for passenger check-in or closed. This screen displays either estimated or actual weights
and trim depending on whether the flight is open or closed. The screen also displays either estimated
or actual weights and trim depending on whether the flight is open or closed.
Entry:
LFSD:FLT/DATE
LFSD Response:
LFSU:XS558/28FEB ATL/JFK A/C GLTYP ETD2000 GATE
1 LCWS __ LLSP __ B767
2 STATUS _ LDP: O CKI: O FUEL: N CONF F12C63Y126
WEIGHT EST EST MAXIMUM MIN A/E MAC %
3 THRU 000000 PAYLOAD 007174 32158 DLW E 24.66%
4 CARGO 003010 ADJ OEW 082600 ZFW E 26.51%
5 BAGS 000480/022 ZFW 089774 114758 TOW E 25.21%
6 PSGRS 003684/041 FUEL STD 23000 47984 006000
7 TOGW ZFW 112774 137758
8 RANGE F 000/000 C 000/000 Y 000/000 TRIM
9 HOLD __1__ __3__ __4__ __5__ __ __ __ __ __ __

ACT WGT 2390 0 1100 0
MAX WGT 9798 8165 5000 2426
CGO SPECIAL HNDLG:
REMARKS: NONE
Note: If a NOTOC (LNTC) or special load notification (LNTS) has been completed, then LNTP__ will
appear after LLSP__. Enter Y to print NOTOC along with the load sheet.

Flight Status Screen
Explanation of Line Numbers 1 - 9.
Line Explanation
1 LCWS = CURRENT WEIGHT STATUS. This can only be displayed on the screen by entering a Y on
this screen, and the flight must be closed and in trim.
1 LCWS Display:
ATL MIA XS927/05 G-IEMY
B767 02/08 05MAR
ZFW ACT 101371 MAX 114758
TOF 55800
TOW ACT 157171 MAX 159179 L
TF 40000
LAW ACT 117171 MAX 126098
BALANCE AND SEATING
DOI 104.00
LILAW 103.59
LIZFW 107.51
LITOW 108.46
DLI 98.53
TTL PAX 74 UNDERLOAD 2008

LLSP = LOADSHEET PRINT. When the flight is closed and trim, there are two ways to print the
loadsheet. The first is to enter a Y beside LLSP on this screen. The other is to enter a separate
transaction 'LLSP:FLIGHT/DATE'. Only one of these entries is necessary, not both.
Note: It is only possible to print the loadsheet providing the flight is closed for both check-in
and load planning, the flight is in trim and under maximum weight restrictions, and all other
flight checks have been made, such as all cargo/mail /baggage has been allocated, hold (or
hold combinations) maximums have not been exceeded, and valid fuel figures have been
entered.
Note: The error response 'PAX/CMPT COUNTS DIFFER' is returned and the LOADSHEET
will not print if the Service Seats on the LADD:REGISTRATION/CERT screen are less than
the total JMP and XXXCREW LDP: on the aircraft.
2 STATUS - LDP = This determines what stage a flight is at in load planning. There are three stages that
can be displayed:
LDP: O - (Flight is OPEN in load planning)
LDP: C - (Flight is CLOSED for load planning)
LDP: R - (Flight has been RELEASED)
LDP: I - (Flight Released without sending any Load Messages
The first stage (O) appears when the flight is created, and it is impossible to produce a loadsheet at this
point until it goes to the second stage (C). If the flight is connected to check-in, it is impossible to go to
the second stage (C), until the flight has been closed for check-in (CKI: C).

Line Explanation
2 (Cont) Once check-in has been closed (CKI: C), a C is manually entered beside LDP (in place of O). If the
weight and balance data is correct, a loadsheet can be produced. The last stage (R) is entered at the
end of the flight. It has two functions. The first function dispatches all the load messages to the
addresses specified on the LAID:STATION screens (this happens if the 'CLOSE MSGS BY LFSU' is set
to Y on the LLAL:PARAM1 screen). The other function releases control of the flight to the next
downline station, for multi-sector flights (the next downline station cannot produce a loadsheet till the
upline station releases the flight). (To release a flight without sending the messages, enter an (I) to
inhibit the messages.)
Note: Release 'R' and Inhibit 'I' can only be entered by the authorized sign-in user group
code as defined beside 'USER-GROUP' on the LLAL:PARAM1 screen.
STATUS - CKI This determines what stage a flight is at in check-in, or if the flight is connected to
check-in. The options are:
CKI: U - Flight is UNCONNECTED to check-in.
CKI: M - Flight has been MANUALLY disconnected from check-in.
CKI: O - Flight is OPEN in check-in.
CKI: C - Flight is CLOSED for check-in.
When the flight is created in LDP, and the CKI status is U, this means either the aircraft configuration
and/or destination details in CKI do not match LDP. Therefore the system cannot link the two together,
or the flight has not yet been initialized in CKI. Perhaps the PNL has not arrived yet, or has not been
loaded onto the flight, so the system cannot find any CKI details. Perhaps this flight has only been
created for LDP and not CKI.
In all of these cases, LDP will have to manually enter the passenger and baggage details, as these will
not come from check-in. When the CKI status shows M, this can mean either the flight was originally
connected to CKI but that the load control agent has manually disconnected it from check-in (perhaps to
use area trim rather then seat row trim, or for some other reason) to produce the loadsheet, or the CKI
status was originally U (and the system will not allow the loadsheet to be produce till the CKI status is
either C or M).
Note: If the flight is not connected to CKI (CKI: U), that the CKI status be changed to M, to
produce the loadsheet.
If the flight is connected to CKI, the CKI status displays O until the flight is closed for check-in, at which
time the CKI status changes to C. This field cannot be changed to C by the load control agent, and the
loadsheet cannot be produced until the CKI status is C. If at this stage the load control agent wants to
override the system, then by changing the CKI status to M, they can now control the flight but will lose
all further connections to CKI.
Note: Even if the connection between LDP and CKI is cut, the system will not delete the
passenger details already stored in the LDP area. If at a later stage the flight is reconnected
to check-in, it is possible for the system to transfer all the latest passenger and baggage
details from CKI to LDP, providing there were no manual changes done to the passenger
figures in the LDP. Once the CKI status is C and the LDP status is C, if CKI re-open the flight
to accept more passengers and baggage, these details will not be transferred to LDP unless
the LDP status is changed to O as well. If after both CKI and LDP status is C, it is possible
for LDP to make changes, (such as new load distribution, or alter the fuel figures). In this
case it is not necessary to make the LDP status O. It can be left as C, but the loadsheet will
have to be re-produced.

Line Explanation
2 It is possible on non-containerized aircraft for LDP to change baggage weights. In addition, on non-
(Cont.) containerized aircraft, if CKI and LDP are closed and CKI is reopened, allowing more passengers to be
added, and then re-closed, and LDP is then reopened, a message will be shown on the LFSD:
'REOPEN CKI - ALLOCATE BAGGAGE'. CKI will have to be reopened while LDP is open for the
additional baggage to be shown in LDP.
FUEL = is the indicator for issuance of a fuel sheet. It is always displayed as N. However, if the item
'FUEL-SHEET-MAN' is set to Y on the LLAL:PARAM1 screen, then a fuel distribution sheet must be
printed before a load sheet can be issued. In this case the FUEL status would be changed to Y and the
applicable fuel details will print.
To use this function, the Fuel Distribution Table must be completed for the fleet and fuel weight:
(LFDD:AIRLINE/(FLEET)/DENSITY/FUEL WEIGHT) and the LAID screen has the address of the
teletype address of the Fuel Sheet Printer.
The fuel sheet may also be transmitted using the entry:
LFFP:FLIGHT/DATE/STN/ADDRESS
3 THRU - Stands for 'THROUGH' or 'TRANSIT' load. These figures come from the
LPAD:FLIGHT/DATE/CGO screen for any load specified as transit (B_T, C_T, M_T, etc.) and appear in
the TRANSIT field.
PAYLOAD - Calculated using the adult passenger weight (from the CW entry if connected to check-in)
times the number of passengers booked, plus the weight of any checked in stand-by passengers,
baggage or cargo (plus any transit load). The maximum payload available is determined by the fuel
figures entered. (Estimated / Actual). Based on the PARAM1 value. If PARAM1 shows Use Booking
Figures, then these figures will be based on the booked passengers.
If the LDP application is not connected to check-in, the passenger weight comes from the LAFD:
(FLEET)/PAX/CONFIGURATION screen.
A/E MAC % = Actual (A) or estimated (E) MAC % index for DLW (deadload weight), ZFW (zero fuel
weight), and TOW (take-off weight). If the flight is connected to CKI, these figures are displayed as E
until the flight has been closed in CKI (CKI status is C). If the flight is not connected to CKI, A displays.
4 CARGO - Includes all cargo and mail, but not baggage displayed on the LPAD:FLT/DATE/CGO screen
and includes the ULD weight.
ADJ OEW - Adjusted operating weight as displayed on the LODD:FLT/DATE screen.
5 BAGS - Weight and number of bags checked-in. The weight comes from the LPAD:FLT/DATE/CGO
screen, and the number comes from the SDD:FLT/DATE screen in CKI.
ZFW - Estimated ZFW which includes the payload plus the operating weight, and the maximum allowed
ZFW.
6 PSGRS - Weight and number of passengers booked (from the PNL/ ADL) plus any accepted stand-by
and thru passengers before the flight is closed in CKI, or the total number of passengers checked-in
after the flight is closed in CKI. Will also include estimated hand carry weight if it is shown on
LAFD:Fleet/Pax/Config.
FUEL STD - Indicates the take-off fuel entered, and STD indicates standard fuel loading is being used.
It is possible for some aircraft types to use ALT (alternate) fuel loading. The initial fuel figures (take-off
and in-flight burn-off) must be entered on the LFFD:FLT/DATE screen, however it is possible to enter
last minute changes to the take-off fuel by entering the amended figure here without having to go back
to the LFFD screen. This is to save time at the last minute, as a new load sheet can be requested at
the same time the new take-off fuel figure is entered through this screen. The maximum and minimum
fuel figures for this aircraft type are also displayed but cannot be amended.

Line Explanation
7 TOGW = Indicates the actual take-off weight and also displays limits which restrict (TOW, Landing, or
ZFW) this flight. This limitation displays as:
ZFW - (For Zero fuel weight)
CERT - (For Take-off weight)
LNS - (For Landing weight)
W/T - (For Restricted Take-off weight)
Note: TOGW will be ZFW until the fuel weight is entered. TOGW comes from the LODD
screen (ATOW).
How Figures are Compiled on the LFSD Screen Using a Manual Loadsheet Outline:
The ALLOWED TAKE-OFF weight for ZFW is 137758, for TOW is 156489, and for LANDING is
140298. This shows that ZFW is the lowest and is the limit which restricts this flight. ZFW is displayed
as the TOGW on the LFSD display, and the restricted maximum weight is displayed as 137758. The
maximum payload is the maximum allowed take-off weight of 137758 minus the operating weight of
105600, leaving the figure of 32158. The underload on the flight is calculated by subtracting the
estimated payload from the maximum payload.
8 RANGE – Displays the actual checked in passengers by class.
TRIM – Values come from the SDCS Database table.
9 HOLD - The hold numbers fitted on this aircraft. The next line indicates the total estimated or actual
load (depending on flight stage) in each hold and the line below indicates the maximum allowed load in
each hold.
The LFSD: now displays a warning message at the bottom of the screen for nose heavy, tail heavy
and the percent MAC when the aircraft is out of CG trim. This is the same type of message that
appears on the LPDD.

Entry:
LFSD:FLT/DATE:
LFSD Response for Nose Heavy Aircraft:
LFSU:XS_0111/21JAN05/ATL___ MIA A/C JWF738 ETD 1900 GATE
LCWS _ LLSP_ B737-800 DATE/TIME: 21JAN/15.22.13
STATUS _ LDP: O CKI: C FUEL:N CONF Y116
WEIGHT ACTUAL KG ACTUAL MAXIMUM MINIMUM A/E MAC %
THRU 000000 PAYLOAD 001900 15897 DLW A 12.44%
CARGO 001900 ADJ OEW 038760 ZFW A 12.44%
BAGS 000000/ ZFW 040660 054657 TOW A 12.44%
PSGRS 000000/000 FUEL STD _____0 22162 002200
TOGW ZFW 040660 54657 TRIM 006.4
RANGE Y 000/000
HOLD __1__ __2__ __3__ __4__ __ __ __ __ __ __ __ __ __ __ __ __

ACT WGT 800 1100 0 0
MAX WGT 888 1118 2409 763
CGO SPECIAL HNDLG:

REMARKS: NONE
AIRCRAFT NOSE HEAVY AT ZFW 0.91 PERCENT MAC
On manual flights that have no passengers or bags, a warning message now appears at the bottom of
the screen indicating that no bags or passengers have been accepted for this flight.
1 LFSD for Manual Flights with no Passengers or Bags:

LFSU:XS_0100T/21FEB05/ATL__ MIA A/C G_737 ETD 2300 GATE
LCWS _ LLSP _ 737 DATE/TIME: 21FEB/20.25.51
STATUS _ LDP: C I: M FUEL: N CONF C12M94
WEIGHT ACTUAL KG ACTUAL MAXIMUM MINIMUM A/E MAC %
THRU 000000 PAYLOAD 000177 13016 DLW A 25.88%
CARGO 000000 ADJ OEW 030075 ZFW A 25.39%
BAGS 000000/ ZFW 030252 043091 TOW A 22.54%
PSGRS 000000/000 FUEL STD _10000 15691 000201
TOGW ZFW 040252 53091 TRIM 000.2UP
RANGE C 001/001 M 000/000
HOLD __1__ __0__ __4__ __ __ __ __ __ __ __ __ __ __ __ __ __ __

ACT WGT 100 0 0
MAX WGT 2488 1000 3401
CGO SPECIAL HNDLG:

REMARKS: NONE
NO PASSENGERS AND/OR BAGGAGE ACCEPTED FOR THIS FLIGHT
Note: In the event a flight contains passengers OR baggage (not both), this message displays at the
bottom of the screen. If cargo is accepted on the flight but no passengers or baggage are accepted,
this message will not display.

ACTIVE RECORD CHANGED REDISPLAY Redisplay the screen before transmitting.
A/C FUEL DATA REQUIRED Fuel figures are missing.
ACT IN TRIM BUT EST TRIM NOSE/TAIL Flight is in trim on actual weights but is out of trim on
HEAVY estimate weights.
AGENT FUEL IS GREATER THAN MAX Fuel figure entered is more than the maximum value
FCP (FUEL CURVE POINT) entered in LADD:/FUL.
AGENT FUEL IS LESS THAN MIN FCP The fuel figure is less than the lowest value in
database LADD:/FUL1.
AIRCRAFT NOSE/TAIL HEAVY Aircraft is out of trim.
CKI STATUS CKI is not C (closed) or M (manual).
COG DATA RQRD COGS or COG2 screen entry missing for this aircraft
type.
EST IN TRIM BUT ACT TRIM NOSE/TAIL Flight is in trim on estimated weights but is out of trim
HEAVY on actual weights.
FLT STATUS LDP is not O (open) or C (closed) or R (released).
FUEL REQUIRED Fuel entry missing from LFFD screen.
INCOMPLETE TRANSIT DETAILS Upline station has not Released flight.
LLSP/LCWS NOT ALLOWED Not allowed before LDP closed.
LOADSHEET REQUIRED Load sheet must be produced before flight released.
NO TRIP FUEL Trip fuel missing from LFFD screen.
TOTAL WGT LESS MIN CG-WGT ZFW is less than the lowest value in database
LADD:/COG2.
UNALLOCATED PAYLOAD Cargo position missing from LPAD:screen.
USER GROUP User group not allowed to release flight.
Table 9.1 LFSD Error Responses

10. Add Special Information and Printing Request
10.1. Supplementary Information Entry (LMSD)
Any required supplementary information (SI) to be added to the LDP messages may be entered
through the LMSD screen.
The entries can be:
LMSD:FLIGHT/DATE/LLDM (For LDM)
LLPM (LPM)
LCPM (CPM)
LSLS (SLS)
LLSP (Loadsheet)
LDSP (Loading Instructions)
1 LMSD Display:
LMSU:XS498/06MAR/LLDM/ATLORDA/C GWPTH ETD 2000
LLDM MESSAGE SUPPLEMENTARY INFORMATION
_______________________________________________________________________
_______________________________________________________________________
_______________________________________________________________________
1 LMSU: With Supplementary Information

LMSU:XS498/06MAR/LLDM/ATLORD A/C GWPTH ETD 2000
LLDM MESSAGE SUPPLEMENTARY INFORMATION
SEAT 7A HAS BROKEN SEATBELT DO NOT USE
___________________________________________________________________________
___________________________________________________________________________
___________________________________________________________________________
This message will now be displayed on the LDM when it is dispatched to the next station.

Add Special Information and Printing Request
10.2. Print Loading Instruction (LDSP)
After all the estimated baggage, cargo, and mail figures are entered on the LPAD:FLIGHT/DATE/CGO
screen, with allocated hold numbers or positions, the loading instruction can be printed out.
The entry is:
LDSP:FLIGHT/DATE LDSP:FLIGHT/DATE/ZZ LDSP:FLIGHT/DATE/TELETYPE

ADDRESS ADDRESS
This loading instruction is printed out on the printer assigned to the DPID file of the agent's CRT (and
also to any telex address specified for the 'LOAD INSTR ADDRESS' on the LAID screen of the
originating station).

1 LDSP Loading Instructions:
LOADING INSTRUCTION/REPORT CONFIG PREPARED BY EDNO
ALL WEIGHTS IN KG M218 01
FROM/TO FLIGHT A-C/REG D/V VERSION CREW DATE TIME

BUDPRG XS 0111 HALHD 763 2/08 03MAY 1452
PLANNED LOAD
PRG M 0 C 007200 M 000000 B 000000 E 000000
JOINING SPECS
TRANSIT SPECS
RELOADS
-------------------------------------------
CPT 1 FWD MAX 009280 ::CPT TOTAL :
----------------------
:11L : :
:ONLOAD PRG C/00800 :ONLOAD
:REPORT :REPORT
-------------------------------------------
CPT 2 FWD MAX 009280 1+2 018560 ::CPT 1 TOTAL :
:21L : :
:REPORT :REPORT
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
:24L : :
:REPORT :REPORT
-------------------------------------------
CPT 3 AFT MAX 007160 ::CPT 2 TOTAL :
----------------------
:31L : :
:REPORT :REPORT
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
:33L : :
:REPORT :REPORT
-------------------------------------------
CPT 4 AFT MAX 005370 3+4 012530 ::CPT 3 TOTAL :
----------------------
:41L : :
:REPORT :REPORT
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
:42L :42R :
:ONLOAD PRG C/00800 :ONLOAD PRG C/00800
:REPORT :REPORT
-------------------------------------------
CPT 5 AFT MAX 002800 4+5 015330 ::CPT 4 TOTAL :
----------------------
:51 :
:ONLOAD PRG C/00800
:REPORT
::CPT 5 TOTAL :
SI
THIS AIRCRAFT HAS BEEN LOADED IN ACCORDANCE WITH THESE
INSTRUCTIONS AND THE DEVIATIONS SHOWN ON THIS REPORT. THE
CONTAINER/PALLETS AND BULK LOAD HAVE BEEN SECURED IN
ACCORDANCE WITH COMPANY INSTRUCTIONS.
SIGNATURE:
Notes: If the flight is open, the total passengers (CKI and BKD) and bags show in the Planned Load.
When the flight is closed, only CKI passengers show.

Entry LDSP:FLIGHT/DATE/CITY/S displays the loading instruction on the CRT screen so verification
can be made on correct allocation of cargo, bags, and mail.
EDNO, EDN1,… are sequential numbers designating the Edition Number of the Loading
Instruction/Report.
10.3. Notification to Captain (NOTOC)

The Notification to Captain (NOTOC) is designed as a formatted screen display to enter required
details in order to notify the captain when dangerous goods and / or other special loads are included in
the load.
There are two different screen displays for entering NOTOC details:
1. For dangerous / restricted cargo the entry is:
LNTC:FLIGHT/DATE
1 LNTC Display (NOTOC):

1 LNTU:XS0300T/11AUG05/ATL SPCL LOAD NOTIFICATION PREPARED BY __________
2 FROM ATL ***DANGEROUS GOODS*** A/C REG G-737
3 TO AWB NR CL/DV UN/ID SUB RRR PCK IMP
4 COMP NBR RSK CAT GRP DRIL CAO POS ULD CODE
5 PCS QTY/TI
6 001.___ ________ ___ ___ ___ ___ ___ ___ ___ ___ ________
7 ____ ____ ___ ___ ____
8 _________________________________________________________
9 _________________________________________________________
10 ________________________ ___ _____ ( ___ X ___ X ___ __ )
11 ________________________ ___ _____ ( ___ X ___ X ___ __ )
12 ________________________ ___ _____ ( ___ X ___ X ___ __ )
13 TOTAL: _____ _______
14 002.MIA 12345678 _7 UN ___ II_ __ RRY ___ 11L AMA0712XS
15 2982 ____
16 RADIOACTIVE-YELLOW* RADIOACTIVE MATERIAL, N.O.S.____________
17 ____________________________________________________________
18 THALLIUM 201__________ __2 0.2TI_ (_10 X _10 X _10 CM )
19 MOLYBDENUM 99_________ __1 0.1TI_ (_10 X _10 X _10 CM )
20 GALLIUM 67____________ __2 0.4TI_ (_15 X _15 X _15 CM )
21 TOTAL: ____5 1.3TI_
22 SI _______________________________________________________
23 _______________________________________________________MORE Y/N _
Explanation of LNTC display by line number:
Line Explanation
1. Header, Prepared By (Add Agents Name).
2. Station of Loading, Title of Display, Aircraft Registration number from FUI.
3. Header Descriptors, To (City of unloading), AWB NR (Air waybill number), CL/DV (Class/Division),
UN/ID (United Nations/Identification Number), SUB (Subsidiary risk), RRR (Radioactive category),
PCK (Packing Group), MP (Cargo IMP code).
4. Header Descriptors, Comp (compatibility group - apart of CL/DV), DRIL (International Civil Aviation
Organization Drill Code), CAO (Cargo Aircraft Only), POS (Position), ULD CODE (Unit Load Device
Code).
5. Header Descriptors, PCS (Number of packages), QTY/TI (Net Quantity/Transport Index.
6. Station of unloading, Last eight digits of Air Waybill, CL or DV as per Shipper's Declaration, United
Nations (UN) or Identification (ID) as per Shipper's Declaration, Subsidiary, Radioactive Category
(III,II,I), Packing or Cargo group number (I,II,III), Cargo IMP code as per AHM 510, Enter CAO if for
only cargo aircraft, Loading Position or hold number, ULD ID code if on non-containerized aircraft.

Line Explanation
7. Compatibility Group (Class 1 goods only), from Shippers Declaration, United Nations or
Identification number from Shipper's Declaration, Group, International Civil Aviation Organization
(ICAO) DRILL Code), when published.
8. Proper Shipping Name per Shipper's Declaration. Maximum of 60 printable characters.
9. Supplementary line for use when the Proper Shipping Name exceeds 60 characters. Maximum of
60 printable characters.
10. Article by name, technical name, Number of pieces, Quantity or Transport Index followed by KG,
L, or TI, as applicable, Dimension in Centimetres.
11. Same as 10.
12. Same as 10.
13. Total Pieces in shipment and weight followed by KG, L or TI as applicable.
14 - 21. Next shipment. (Items are filled in as an example.)
22. Supplementary Information
23. Supplementary Information, MORE Y/N - Type Y if more pages required.
SPECIAL LOAD ITEMS

For Special Load items the entry is:
LNTS:FLIGHT/DATE
1 LNTS:Flight/Date Entry Response (Special Loads):

1 LNTU:XS0300T/11AUG05/ATL SPL LOAD NOTIFICATION PREPARED BY ______________
2 FROM ATL ***OTHER SPECIAL LOAD*** A/C REG G-737
3 TO AWB CONTENTS PCS QTY IMP POS
4 NR GOODS DESCRIPTION ULD CODE CODE
5 001. ________________________ ___ ____ KG ____ ___
6 ___ ________ ________________________ ________
7 002. ________________________ ___ ____ KG ____ ___
8 ________ ________________________ ________
9 003. ________________________ ___ ____ KG ____ ___
10 ___ ________ ________________________ ________
11 004. ________________________ ___ ____ KG ____ ___
12 ___ ________ ________________________ ________
13 005. ________________________ ___ ____ KG ____ ___
14 ___ ________ ________________________ ________
15 006. ________________________ ___ ____ KG ____ ___
16 ___ ________ ________________________ ________
17 007. ________________________ ___ ____ KG ____ ___
18 ___ ________ ________________________ ________
19 008. ________________________ ___ ____ KG ____ ___
20 ___ ________ ________________________ ________
21 SI ____________________________________________________________
22 ____________________________________________________________
Explanation of LNTS Display by Line Number:
Line Explanation
1. Header. PREPARED BY (Add Agents name.)
2. From station of loading. Aircraft Registration number.

Line Explanation
3 - 4. Header descriptors.
TO - City of unloading
AWB NR - Airway Bill
Contents and Goods Description
PCS - pieces
QTY - quantity
ULD code
IMP code
POS - position
5. Item number
Content and description
Number of packages
Weight
IMP code
POS - position or hold number
6. City of unloading
Last eight digits of air waybill
Description of goods
ULD code
7. - 20. Same as line 5 to 6.
21. SI - Supplementary Information
22. Additional Supplementary Information. MORE Y/N - Type Y if additional pages required.
Printing NOTOC
The NOTOC may be printed using three different entries:
An entry on the LNTC: or LNTS displays.
Using the NOTOC print entry: LNTP:FLT/DATE
Inserting "Y" (Yes) next to the LNTP field on the LFSD: screen.
Note: Entering LNTP:Flight/Date/City/S will display NOTOC on CRT screen.

10.4. Print Load sheet (LLSP)
There are two ways to print the load sheet:
1. Display the LFSD:FLT/DATE screen and enter a Y beside LLSP and transmit.
2. Enter the following transaction 'LLSP:FLIGHT/DATE'.
Note: The error response 'PAX/CMPT COUNTS DIFFER' will be returned and the LOADSHEET will
not print if the Service Seats on the LADD:REGISTRATION/CERT screen are less than the total JMP
and XXXCREW on the aircraft.
The load sheet may be directed to the CRT by entering LLSP:Flight/Date/City/S.
1 Load sheet:
L O A D S H E E TCHECKED BY APPROVED EDNO
ALL MASSES IN KG 01
FROM/TO FLIGHT A/C REG VERSION CREW DATE TIME
ATL JFK XS193 G-RKYS F12Y189 2/8/0 27FEB05 1150
MASSES DISTRIBUTION
LOAD IN COMPARTMENTS 6140 1/2700 3/0 4/2440 5/0 0/0
PASSENGER/CABIN BAG 7956 76/24/2/1 TTL 102 CAB 0
PAX 2/100
TOTAL TRAFFIC LOAD 14096
DRY OPERATING WEIGHT 82600
ZERO FUEL MASS ACTUAL 96696 MAX 114758 ADJ
____________________________________________________
TAKE OFF FUEL 32000
TAKE OFF MASS ACTUAL 128696 MAX 156489 ADJ
____________________________________________________
TRIP FUEL 15000
LANDING MASS ACTUAL 113696 MAX 126098 L ADJ
____________________________________________________
BALANCE AND SEATING CONDITIONS LAST MINUTE CHANGES
DOI 104.00 DLI 97.71 DEST SPEC CL/CPT + - WEIGHT
LIZFM 101.93
LITOM 108.94
SEATING (FREE SEATING)

0A/2 0B/25 0C/75
UNDERLOAD BEFORE LMC 12402 LMC TOTAL + -
LOADMESSAGE AND CAPTAINS INFORMATION BEFORE LMC

BM 12696 KGS BI 106.50
ZFW 027990 KGS TOW 032399 LBS LAW 030194 LBS
TO-FUEL 4409 LBS TRIP FUEL 2205 LBS
CG LIMIT ZFM FWD 14.97 AFT 40.00

TOM FWD 16.49 AFT 40.00
LAM FWD 0.00 AFT 0.00
*** NO CONNECTION TO CHECK-IN APPLICATION ***
THIS AIRCRAFT HAS BEEN LOADED IN ACCORDANCE WITH THE
LOADING INSTRUCTIONS INCLUDING THE DEVIATIONS RECORDED.
THE LOAD HAS BEEN SECURED IN ACCORDANCE WITH COMPANY
REGULATIONS
SIGNED________________
NOTOC - NIL
Note: If there are no notifications to the captain completed on the flight, 'NIL NOTOC' prints at the
bottom of the load sheet.

Providing the flight is closed for both LDP and CKI, and there are no errors (flight out of trim or
overweight, etc.), the load sheet should start printing on the printer assigned to the agent's CRT (the
loadsheet will also be sent to any valid telex address specified for the 'LOAD SHEET ADDRESS' on
the LAID screen of the originating station).
If the ‘L/S CONNECT MSG’ is set to ‘Y’ on the ‘LLAL:Airline/PARAM1’ screen, and the LDP flight is
not connected to Check-in, the following message is printed on the load sheet under the ‘Captain’s
Information’ field.
1
BW 30075 KGS BI 52.70
*** NO CONNECTION TO CHECK-IN APPLICATION ***
Note: When the load sheet print request is made through the LFSD or LLSP entries, the current
responses to the screen still apply. The warning message is not displayed on the screen, it is only
printed on the load sheet.
If the ‘SPECIAL TEXT ON L/S’ is set to ‘Y’ on the ‘LLAL:Airline/PARAM1’ screen, the following
special text message prints on the load sheet under the ‘Captain’s Information’ field. If the flight is not
connected to check-in, and the parameter is set to print the warning message, then the special text
appears after the warning message.
1
BW 30075 KGS BI 52.70
THIS AIRCARFT HAS BEEN LOADED IN ACCORDANCE WITH THE
LOADING INSTRUCTIONS INCLUDING THE DEVIATIONS RECORDED.
THE LOAD HAS BEEN SECURED IN ACCORDANCE WITH THE COMPANY
REGULATIONS
SIGNED ______________.

A/C FUEL DATA REQUIRED Fuel figures are missing.
AGENT FUEL IS GREATER The fuel figure entered is more than the maximum fuel for this
THAN MAX FCP (FUEL aircraft.
CURVE POINT)
AGENT FUEL IS LESS THAN The fuel figure entered is less than the minimum fuel for this aircraft.
MIN FCP
A/C NOSE/TAIL HEAVY Aircraft is out of trim.
CKI/LDP TRANSIT COUNTS Conflicting transit passenger counts. Check SDD and
DO NOT MATCH LPAD:FLT/./PAX1 and make sure they match.
CKI/FLT STATUS CKI is not C (closed) or M (manual) or LDP is not C.
COG DATA RQRD Check COGS/COG2 as a/c data may be missing.
FUEL REQUIRED Fuel entry missing from LFFD screen.
MAX ATOGW/ZFW Aircraft weight is over stated maximum weight.

EXCEEDED BY 'X' KGS
NO TRIP FUEL Trip fuel missing from LFFD screen.

PAYLOAD UPDATE Check the LPAD:FLT/DATE/CGO screen and re-transmit the display
REQUIRED (even if no errors).
TOTAL WGT LESS OR Check MIN/MAX figures entered on COGS/COG2for a/c registration
GREATER THAN MIN/MAX used (current flight weight is below/above the figures displayed on
CG-WGT these screens).
UNALLOCATED PAYLOAD Hold position is missing from the CGO screen.
INCOMPLETE TRANSIT Upline station has not Released flight.

DETAILS
Table 10.1 LLSP Error Responses

11. Additional Flight Entries and Information
11.1. Flight Cancellation (LFIX)
If necessary a flight can be canceled in LDP.
The entry is:
LFIX:FLIGHT/DATE/CNCL
1
LFIX:XS109/./CNCL
Response:
XS FLIGHT NUMBER 0109 DELETED
It is possible to re-create this flight again either by entering the registration via the FUI
(FUI:FLT/DATE/STN/ARN/REGISTRATION) and DPT: transactions, or through the
LCFD:FLIGHT/DATE transaction. If the flight is already created in check-in and the new LDP flight
matches the details (routing, aircraft type, and configuration), then the LDP flight will pick-up all the
check-in details again, even if the flight was half-way through check-in. However all the payload
details (cargo, mail etc.), and fuel details (unless the HISTORY record is used) will have to be re-
entered and a new load distribution planned.
Error Response
AIRLINE Invalid airline code entered.
CNCL CODE CNCL code missing or incorrectly entered.
CODE LFIX code missing or incorrectly entered.
DATE Invalid date entered.
DISPLAY/UPDATE NOT ALLOWED User not authorized to display the entry for another station.
FLT/DATE Invalid flight/date entered.
FORMAT Invalid entry.
FUNCTION Invalid function code entered.
Table 11.1 LFIX Error Responses

Additional Flight Entries and Information
11.2. Cabin Loading/Seats Occupied By Cargo (LSCD)
There are two ways to enter load in the cabin:
1. By specifying the rows used with the LSCD transaction.
2. By entering the area zone used on the LPAD:FLT/DATE/CGO screen (under POS).
SEATS OCCUPIED BY CARGO (LSCD)
11.2.1 Seats Occupied by Cargo (LSCD)
The entry for this transaction is:
LSCD:FLIGHT/DATE
Seats Occupied By Cargo (LSCD) Response:
LSCU:XS558/01MAR/ATL A/C GSTTQ F12Y189 ETD 2000
WGT KG PAYLOAD REMAINING 28608 B767 DATE/TIME:
DEST WEIGHT ROW SEATS DEST WEIGHT ROW SEATS DEST WEIGHT ROW SEATS
CHI 150 12 2 CHI 60 01 1_ __ __ __ __
____ ___ ___ _ ____ __ __ _ __ __ __ __
____ ___ ___ _ ____ __ __ _ __ __ __ __
It is possible to enter the weight and row number here but not to indicate the type of cargo (cargo or
mail etc.) or specific seat. The weight and the index (system knows the index from the row specified)
are included in weight and balance calculations. There is no link between LDP and CKI regarding the
rows used, so the load control agent must make sure check-in blocks the required seats (X) on the
seat map, to ensure passengers are not seated in the occupied cargo seats. The T specified after the
row number specifies this is a transit flight and this row was occupied by cargo at a previous station.
11.2.2 Cabin Loading (LPAD:FLT/DATE/CGO)

Some airlines have a specific area for cabin loading and they build a special passenger configuration
in their database so passengers cannot be seated in that zone. In this case they enter the weight and
individual code (cargo or mail) and zone area used on the LPAD:FLT/DATE/CGO1 screen. For those
airlines which do not have a particular zone area, in addition to the above procedure, the load control
agent must decide where the cabin loading is going and advise check-in to block the required number
of seats (code X) so passengers cannot be seated in that area.
Note: Cabin zones can only be specified on the LPAD:FLIGHT/DATE/CGO1 screen if these zones
have been defined for that aircraft type and configuration on the
'LAFD:(FLEET)/PAX/CONFIGURATION * (* is the cabin loading indicator as defined on the
'LLAL:PARAM1' screen under 'MIXED-CONF-IND').
Cabin Loaded Mail Shown on Cargo Screen:
LPAU:XS227/03MAR06/CGO1 ATL_JFK A/C GKKGA F12Y96 ETD 2030
WEIGHT KG B737
LFSD: LPDD: CUMULATIVE CHECKS: Y
DEST ACTWT ESTWT TYPE SERIAL CONT POS/PRI RESTRICT CARGO DST
JFK 388 600 B 1
JFK 360 360 M 4
JFK 300 300 M B

11.3. Transit Flights
There are two types of transit flights where the previous station was:
1. automated.
2. non-automated.
11.3.1 Transit Flight from an Automated Station

The transit passenger details display on the LPAD:FLIGHT/DATE/PAX1 screen, and the transit load
details display on the LPAD:FLIGHT/DATE/CGO screen after the flight has been released upline. The
flight is then processed normally.
11.3.2 Transit Flight from an Non-Automated Station

The transit passenger and transit load details can either be manually entered (via the
LPAD:FLT/DATE/PAX1 for passenger details and LPAD:FLT/DATE/CGO for load details) or the
figures can be updated by the system when it receives a valid SOM, LDM, LPM, or CPM (for non-
containerized aircraft) which has been sent from the non-automated station.
The DCS system requires the following addresses be used so these messages will read into the
system providing they are in the correct format:
HDQCS** 2for SOM
HDQLP**for LDM/LPM/CPM
Note: In addition to the system addresses, the USER should also specify a hardcopy teletype address
in their control office, to help identify error read-in formats and also as a check or warning when these
messages have or have not been, received at a station for a particular flight.
SOM
The SOM (Seats Occupied Message) message adds transit passenger details to the SDD screen. It
also puts a T on the seat map (SE:FLT/DATE) for transit seats in the CKI area and enters the area
seating position of these transit passengers into the LPAD:FLIGHT/DATE/PAX screen in LDP.
2 ** indicates Host Airline

1 A SOM Routing SFO-LAX-HOU for Airline XS:
TY HDQCSXS
.SFOKKXS
SOM
XS593/01MAR SFO PART 1
-LAX.1AB 7ABCDEFG 8ACFG 11ABC 12EFG 13AB 22ABCD
25EFG 26ABCDEFG 27ABFG
-HOU.1DEFG 2EFG 12ABCD 27ABC 28ABCEFG 29ABCDEFG
30ABCDEFG 31ACDF
PROT EX
NIL
SI
PAD
NIL
XCR
NIL
SOC
NIL
ENDSOM
Once a SOM is received, it is possible for the system to accept another corrected SOM (by inserting a
line above SOM and adding the word COR) for any amendments to the original figures. It is also
possible to enter the corrections manually by using the BX transaction in CKI, and any changes are
included in the LPAD:FLT/DATE/PAX screen.
Note: If a BX transaction is done before the SOM is received into the system, the SOM is rejected,
and the remaining transit seats will be blocked by the BX transaction.
The system keeps a record of any SOMs received (in correct format). These can be displayed by
entering 'MD:SOM/FLIGHT/DATE/CITY'. A SOM received in error is rejected to the KS queue of the
Host's DCS Office Queues. A correct SOM goes to the KS queue but will show 'SOM ACCEPTED'
without additional details.
LDM
The LDM (LoaD Message) is a message that enters the transit passenger totals (gender and class)
onto the LPAD:FLT/DATE/PAX1 screen.
1 A LDM Routing SFO-LAX-HOU for Airline XS:

TY HDQLPXS
.SFOKLXS
LDM
XS593/01.G-GDEF.F12Y189.02/08
-LAX.49/18/5/3.0.T3313.1/1523.4/1790
.PAX/2/70.PAD/0/2
-HOU.22/13/7/1.T4040.1/2530.3/1510
.PAX/7/35.PAD/0/0
SI
;

If there are no passengers or load for a particular destination, the LDM must show 0 (zero) in all
relevant places, as the system will not accept NIL. The system only tracks rejected LDMS received in
incorrect format by placing them on the LE queue of the Host's DCS office queues. If a LDM is
successfully loaded onto the flight, it is erased from the system.
Once a LDM has been received, it is possible for the system to accept another corrected LDM (by
inserting a line before LDM and adding the word AMEND) for any amendments to the original figures.
However it is also possible to enter the corrections manually by entering the correct passenger figures
directly on to the LPAD:FLT/DATE/PAX1 screen.
Note: It is only possible to amend the figures directly on the LPAD:FLT/DATE/PAX1 screen if the
previous station is not automated (LAID:DEST has LDP = N), otherwise the response will be 'UPDATE
NOT ALLOWED'.
If the LAID:DEST screen displays LDP = Y (whether in error or station is normally automated) and the
passenger figures now need to be added, there are two ways to do it:
A\By sending a manual LDM with all the details (see previous example for reference).
If the LDM is sent in the correct format, the Transit Passenger details are inserted into the
LPAD:FLIGHT/DATE/PAX1 and PAX screens, and no further action is required except to add the
Transit Load details to the LPAD:FLIGHT/DATE screen (or send and LPM message, see following
section).
B\By performing the following steps.
1. Display the LAID:DEST (change LDP = N).
2. Cancel the Flight in LDP (LFIX:FLIGHT/DATE).
3. Re-enter the Aircraft Registration (FUI:FLT/DATE/STN/ARN/REG).
4. Re-enter all Fuel and Load distributions.
5. Enter the Transit Passengers (LPAD:FLIGHT/DATE/PAX1).
LPM
The LPM (Load Planning Message) is a message that enters the transit load details onto the
LPAD:FLT/DATE/CGO screen.
1 A LPM Routing SFO-LAX-HOU for Airline XS:

TY HDQLPXS
.SFOKLXS
LPM
XS593/01.G-GDEF.F12Y189
-SFO.PAX/9/105.B1655.C4053.M1440
.ZFW098163.LIZFW+0091.9
.11P/HOU/C1120
.13P/LAX/C1523
.15P/HOU/C1410
.31L/HOU/X0
.31R/HOU/X0
.32L/HOU/M690
.32R/HOU/TB120
.33L/HOU/B635
.33R/HOU/FB65
.41L/LAX/B120
.41R/LAX/FB20
.42L/LAX/M750
.42R/LAX/B900
SI
;

For containerized aircraft, the LPM message would show hold numbers instead of pallet or container
positions (example .1/HOU/C600). Once a LPM has been received, it is possible for the system to
accept another corrected LPM (by inserting a line before LPM and adding the word AMEND) for any
amendments to the original figures. However it is also possible to manually enter the corrections
directly to the CGO screen.
Note: If sending a manual LPM message, the station indicated on the line below the flight number is
the originating station and not the destination. Also the ZFW and LIZFW are mandatory elements and
must be included on the message.
1 Transit Load on LPAD:FLT/DATE/CGO1 Screen:

LPAU:XS847/03MAR06/CGO1 ATL_MIA A/C GKTLQ F12Y96 ETD 1015
WEIGHT KG B737
LFSD: LPDD: CUMULATIVE CHECKS: Y
DEST ACTWT ESTWT TYPE SERIAL CONT POS/PRI RESTRICT CARGO DST
MIA 360 360 C T 1
MIA 420 420 B T 1
MIA 240 240 M T 4
The 'T' displayed at the end of the TYPE (C, M, B, etc.) indicates the 'THRU' (or TRANSIT) load.
The system only keeps a record of any rejected LPMS received in incorrect format by placing them on
the LE queue of the Host's DCS office queues. If a LPM has been successfully loaded onto the flight,
then any copy of it gets erased from the system.
Note: If passengers and baggage are checked-in at the transit station before the LPM has been
received, the transit baggage (B) items are rejected from the LPAD:FLT/DATE/CGO screen, and will
have to be manually added.

CPM
The CPM (Container/Pallet Message) is a message that enters the transit load details, including the
container or pallet type, and available volume, onto the LPAD:FLT/DATE/CGO screen. Normally a
CPM message is sent for a containerized aircraft and takes the place of a LPM message.
1 A CPM Routing SFO-LAX-HOU for Airline XS:

TY HDQLPXS
.SFOKLXS
CPM
XS593/01.G-GDEF.F12Y189
-11P/UAK2384XS/HOU/1120/C3-
-13P/UAK1919XS/LAX/1523/C2
-15P/UAK8171XS/HOU/1410/C2-
-31L/AVK0245XS/PRG/X - 31R/AVE7002XS/HOU/X
-32L/AVK7491XS/HOU/690/M0 - 32R/AVE7771XS/HOU/120/T3
-33L/AVE2155XS/HOU/635/B1 - 33R/AVE3155XS/HOU/65/F3
-41L/AVE2883XS/LAX/120/B3 - 41R/AVE9932XS/LAX/20/F3
-42L/AVK9117XS/LAX/750/M0 - 42R/AVE2184XS/LAX/900/B0
-43L/LAX/X-43R/LAX/X
-51/LAX/501/M.AV0
SI
;
Note: If the CPM SERIAL NUM is set to N on the LLAL:PARAM1 screen, the CPM message only
displays the first three characters of the serial number (example AVE instead of AVE9914XS etc.).
Once a CPM is received, it is possible for the system to accept another corrected CPM (by inserting a
line before CPM and adding the word AMEND) for any amendments to the original figures. However it
is also possible to enter the corrections manually by entering the correct figures on the
LPAD:FLT/DATE/CGO screen.
The system only tracks any rejected CPMS received in incorrect format by placing them on the LE
queue of the Host's DCS office queues. If a CPM has been successfully loaded onto the flight, then
any copy of it gets erased from the system.
UCM
The UCM (ULD Control Message) is not utilized by the system. It is just a message that keeps a
record of the containers and pallet numbers used on a flight from a particular station and is usually
sent to an airline's control office, where a station location record of all the containers and pallets are
kept.
SITA has a ULD control program. If the Host airline uses this system, it is possible at the end of a flight
for DCS to send this message to the IBM computer for action.
Note: DCS can only create a UCM message if the container/pallet serial numbers have been entered
on the LPAD:FLT/DATE/CGO screen. If only some serial numbers have been entered, then only
those ULDS with numbers will appear on the message.
1 UCM for Airline XS:

UCM
XS593/01.G-GDEF.SFO
IN
.N
OUT
.UAK9923XS.UAK2387XS.UAK1177XS.AVE2223XS
.AVE1945XS.AVE9914XS.AVE4455XS.AVE9367XS
.AVE4567XS.AVE4953XS
SI

SLS
The SLS (Statistical Load Message) is a message that sends statistical information such as the total
number of passengers on a flight, the amount of baggage, cargo and mail carried. The message is
dispatched at the end of a flight to the addresses specified on the LAID screen of the departure
station.
1 SLS Message:
SLS
XS102/24.GHOPT.F12Y126.ATL.24JUL05
-ORD.FF/1.YY/26.GG/2/1.B/310.C/1200.M/750
-JFK.FF/2.YY/30.GG/6/2.B/375.C/950.M/300
SI
Explanation:
Code Explanation
FF Number of First class passengers.
YY Number of Y class passengers.
GG Number of ID passengers including infants, followed by total number of infants.
B Weight of baggage.
C Weight of Cargo.
M Weight of Mail.

11.4. Extra Crew (XXXCREW)
If there are extra crew occupying passenger seats on a flight, and the flight is connected to check-in, it
is very important to know how they have been checked-in, as it can cause some confusion to the
passenger figures for the load control agent. There is a specific code (XXXCREW) for extra crew
occupying seats that is used in check-in. If check-in uses the XXXCREW code, note the following:
In check-in the XXXCREW are included in the passenger figures on the SDD:FLIGHT/DATE
screen, and are also shown separately under the code XCR on the same screen.
In the COM message (sent from CKI to LDP) the XXXCREW are not included in the passenger
figures but are included in the extra crew figures.
In LDP the XXXCREW are not included on the checked-in passengers, as displayed on the
LPAD:FLIGHT/DATE/PAX2 screen.
On the LODD:FLIGHT/DATE screen the XXXCREW are shown as extra crew on the crew figures
display, and their weight and index is displayed as an adjustment to the DOW (Dry Operating
Weight) and DOI (Dry Operating Index). They are also shown on the LPAD:/PAX4 screen by
class.
1 XXXCREW Response on the LODD Screen:

WEIGHT KG TEMP 0___ ETD 1200 GATE CREW 2_8 2
J/S_________________ ________ ____ __________
CONF F12Y189 CPM OTH F12Y189
SPARE WHEEL N EXTRA CATERING N
OEW-ADJ 146 INDEX -0.4 DESCRIPTION CREW COMPLEMENT

___ ___________ CATERING REQUIREMENT
___ ___________ DECK VERSION NONE
___ ___________ ___________________________
___ ___________ ___________________________
BASIC WT 82600 IDX 104.00 DRY OPERATE WT 82746 IDX 103.54
Explanation:
Field Explanation
CREW 2_8 2 Two Pilots, eight Cabin crew, and two Extra crew.
OEW-ADJ 146 Additional weight and index adjustment of the two extra crew. The weight comes from the
INDEX -0.4 standard passenger weights used at check-in. The index is calculated using the arm effect
for the row they are seated in.
DRY OPERATION These figures include the extra crew adjustment.
WT/IDX
If extra crew is checked-in using a different code (or their own names), then they will be included in the
normal passenger details, and will not appear on the LODD screen. In this case it is not necessary for
the load control agent to be aware of them as they will already be included in all the weight and
balance calculations.
If the extra crew are not using passenger seats, but are traveling on the flight, then it is possible to
amend the Pilot/Cabin crew figures directly on the LODD screen, and providing the system finds the
matching crew figures on the LADD:REGISTRATION/CREW screen. The DOW/DOI will be adjusted.

11.5. Jump Seat Passengers
Jump seats are seats allocated for crew seating. However, when a flight is full, airlines may authorize
seating (usually by staff) in crew seats not needed by crew on this flight. The total of jump seats
allowed must be shown on the LADD:/CERT screen (Service Seats) and on the EQC: (Seat Map
Creation) entry.
There are two ways a jump seat passenger may be put on a flight:
1.In CKI by checking-in the passenger with the code JMP.
If the flight is connected to CKI, these passengers are checked-in with the item JMP, and are issued a
boarding card without a seat number on it. The following should be noted:
In check-in the jump seat passenger is not included in the passenger figures on the
SDD:FLIGHT/DATE screen, but is shown separately under the code J on the same screen.
In the COM message (sent from CKI to LDP) the jump seat passenger is not included in the
passenger figures but is included in the total passenger weights.
In LDP the jump seat passenger is included in both the class and gender totals on the checked-in
passengers, as displayed on the LPAD:FLIGHT/DATE/PAX2 screen.
On the load sheet the jump seat passenger is included in the class and gender totals, and the
weight included in the total traffic load.
The LDM does include the jump seat passenger in the load details.
2.In LDP by adding the name to the LODD screen.

Normally this method is only used if the flight is not connected to CKI (although it is possible to use this
method even if the flight is connected to CKI). The LODD:FLIGHT/DATE screen is displayed and the
required name is added to the J/S line. Do not add the JMP to both CKI and LDP as the weights will
be doubled.
1 Jump Seat Name Added on the LODD Screen:

LODU:XS477/28FEB/ATLMIA A/C G-BLPP B767
WEIGHT KG TEMP 0___ ETD 1200 GATE CREW 2_8 0
J/S ANDREWS/J
CONF F12Y189 CPM OTH F12Y189
BASIC WT 82600 IDX 104.00 DRY OPERATE WT 82678 IDX 103.10

Note the following:
The weight and index of the jump seat passenger comes from the LADD:REG/CERT screen and it
gets added to the DOW/DOI. The CERT screen must show a Max Service Seat figure and agree
with the equipment's EQC: to prevent an error CLASS/CMPT TOTALS.
In LDP the jump seat passenger is not included in either the class or the gender totals of checked-
in passengers as displayed on the LPAD:FLIGHT/DATE/PAX2 screen.
On the load sheet the jump seat passenger is not included in the class and gender totals, and the
weight is not included in the total traffic load, but it is included in the Dry Operating weight.
The LDM does not include the jump seat passenger in the load details but it does display the
following remark under SI:1 JUMP SEAT RIDER.
If the jump seat passenger is checked-in using JMP you must not add names via the LODD
screen as it causes a duplication of J/S weight.
11.6. Stretcher Passengers

For flights that are connected to CKI, the general procedure to handle a stretcher passenger in DCS is
as follows:
1. The weight of the stretcher must be entered on LODD in the OEW-ADJ field.
2. The seats for stretcher passengers should be indicated on the seat map using the seat code K, by
using either the EQC: for seat map creation or the SCC: to amend a seat map. Normally a
stretcher will occupy six to nine seats.
3. The booked passenger having the PNL remarks code STCR is checked in. The system issues a
boarding card having the code STCR in place of the seat number (SN).
4. The stretcher passenger is included in the SDD class totals, and is also shown by code STCR.
5. In the COM message (sent from CKI to LDP) the STCR passenger is included in the passenger
gender and weight figures but is not included in the class total.
6. In LDP the stretcher passenger is included in both the class and the gender totals on the checked-
in passengers, as displayed on the LPAD:FLIGHT/DATE/PAX2 screen.
7. On the load sheet the stretcher passenger is included in the class and gender totals, and the
weight is included in the total traffic load. Also the number of seats blocked by class are displayed
by the item BLKD.
8. The LDM does not include any information about the stretcher passenger unless it has been
added for the SI information on the LMSD:FLIGHT/DATE/LLDM screen. It is also possible to add
some information on the LPAD:FLIGHT/DATE/PAX4 screen, however the free format information
is added after the PAD information and not the SI information.

11.7. EZFW Display (LZFW)
It is possible to get an estimated zero fuel weight display to the screen at any time during a flight.
The entry is:
LZFW:FLIGHT/DATE/CITY/S(LZFW:FLT/DATE will direct to printer)
Example Zero Fuel Weight Display Response:
EZFW XS992/06MAR G-CKKL F12Y189 02/08/00 ATL/HOU
PASSENGER 001794KG
BAGGAGE 000353KG
CARGO 003390KG
MAIL 000000KG
TR DEADLOAD 000000KG
TR PASSENGER 000000KG
TTL TRAFFIC LOAD 005537KG
F 003 Y 018
TTL PASSENGER 021
BW 082600KG
WT ADJ 000000KG
ADJ-DOW 082600KG
EST ZFW 088137KG OR 194309LB
11.8. Seats Occupied Display (LSOD)

It is possible to display the seats occupied on a flight providing the flight is connected to check-in.
The entry is:
LSOD:FLIGHT/DATE
1 Seats Occupied Display (LSOD) Response:

LSOD:XS888/06MAR05/ATLLAX A/C G-SJDA ETD 1900
SEATS OCCUPIED FOR FLIGHT/LEG
ROW OCC ROW OCC ROW OCC ROW OCC
1 1 25 4
2 2 26 1
7 27 3
8 2 28 3
9 5 29
10 30 6
This screen can be useful if trying to check any discrepancies between seats occupied (or even to
check rows built in the LDP database compared to the seat numbers built on the seat map) in check-in
and LDP. It is a display only and no changes can be made to this screen.

11.9. Payload Transfer Between Flights (LCOP)
It is possible to transfer the payload (baggage, cargo, mail, plus any transit details etc.) from one flight
to another (for example, when one flight is canceled or delayed). The only restriction is this entry can
only be used for a containerized aircraft to another containerized aircraft, or a non-containerized
aircraft to a non-containerized aircraft. It is not possible to transfer the payload from a containerized to
a non-containerized , or vice versa. The entry is:
LCOP:FLIGHT/DATE/SEGMENT/NEW FLIGHT/DATE
If the segment is omitted, the system defaults to the current station as the departure station and the
last station of the new flight as the destination.
Note: If the destination of the transferred payload is not on the itinerary of the new flight, the final
destination field is updated with the original destination, and the first destination field becomes the next
downline station.
It should also be noted if LDP and CKI are connected the LCOP transaction will break the link between
the applications of the new flight. The LFSD display shows (M) next to the CKI: field and the following
response at the bottom of the display:
TRANSACTION ACCEPTED / FLT NOT CONNECTED TO CKI.
This is an acceptable precautionary response because baggage is being added manually to the new
flight.
If Bulk Recheck is not done prior to the LCOP: transaction, the total bag weight is still shown on the
original flight's LPAD:/CGO1 screen, (even though the bag weight has been copied to the new flight),
until the passengers are moved with the BRC: check-in transaction.

12. Flight A/C Changes
12.1. Flight A/C Version / Type Change
The way an aircraft version / type change is handled in DCS depends on the following conditions:
12.1.1 Before Flight Initialization for both CKI and LDP
If the flight is not initialized, it is possible to either enter the correct CND table number via the FUI entry
(FUI:FLIGHT/DATE/STATION/CTN/NUMBER) or to amend the schedule (DFD:FLIGHT/DATE) with
the correct CND table number.
CKI Steps
No further action is required by CKI.
Note: If the aircraft version change involves a MP (moveable partition) transaction, and not a new
CND table number, the version change must be updated after CKI is initialized. Once the MP
transaction is completed in check-in, a FUI: message is sent to LDP (FUI:XS123/01DEC05/ATL/
MVP/CD65MYBKLQWGVSN57). When LDP is initialized via the DPT transaction the correct
configuration appears on the LCFD screen. This transaction is recorded in the FJ history display.
LDP Steps
No further action is required by LDP.
12.1.2 After CKI Initialization but Before LDP Initialization

CKI Steps
If check-in has not started, it is possible to enter the change via the FUI entry and no further action is
required. However if check-in has started, either a MP (moveable partition) transaction (for version
change only) can be used (if it applies), or an AEC (aircraft equipment change) transaction must be
used.
Note: If the new version/type change involves a class change, the AEC transaction cannot be used
unless the CND table contains the classes of service for the new aircraft. A master class can be
shown as a subclass on the CND table to allow this process.
LDP Steps
If a new CND has been entered via FUI before flight is initialized for LDP, LDP does not have to do
anything (except enter the correct aircraft registration). However, if the new CND has not been
entered or the change was done by a MP transaction, the load control agent must either enter on the
LDP flight initialization, the correct CND number and new registration via the FUI
(FUI:FLT/DATE/STATION/
CTN/NUMBER/ARN/REG) entry. Alternatively, the aircraft registration and configuration can be
entered via the LCFD screen. Otherwise CKI and LDP would not match, and the check-in details will
not be transferred over to LDP.

Flight A/C Changes
12.1.3 After CKI and LDP Initialization but Before Flight Closed for CKI
CKI Steps
Once check-in has started either a MP (moveable partition) transaction can be entered (if it applies), or
an AEC (aircraft equipment change) transaction must be used.
LDP Steps
The load control agent must enter the correct CND number and aircraft registration via the FUI entry,
or, enter the aircraft registration and configuration via the LCFD screen, otherwise CKI and LDP will
not match, and the check-in details will not be transferred over to LDP.
12.1.4 After Flight Closed for Both CKI and LDP

LDP Steps
The load control agent must enter the correct CND number and aircraft registration via the FUI entry or
enter the aircraft registration and configuration via the LCFD screen. If, at this stage it is decided not
to change (update) CKI, the best solution would be for LDP to cut the 'link' with CKI (make CKI:M on
the LFSD:FLIGHT/DATE screen), and manually enter the passenger area seating on the
LPAD:FLIGHT/DATE/PAX screen. The load sheet can now be produced normally.
12.1.5 For an Initialized LDP Flight not Connected to CKI

LDP Steps
If the flight is not connected to CKI, but was built by a BF:T schedule, the new CND number and
aircraft configuration are entered via the FUI entry. If the flight was built by the LCFD entry, the new
aircraft registration and configuration can only be entered via the LCFD screen.

Flight A/C Changes
13. LDP Messages
13.1. Movement Message (MVT)
This is an input shell only and is constructed by flight number and not by station. Whatever input code
you search for will show the last input. The station input will determine if the message type is valid, for
example, an AA input is not valid for the origin station nor is an ED acceptable after AD. The entry to
transmit the aircraft's arrival or departure information is:
LMVD:FLIGHT/DATE/STATION/CODE
If the STATION is omitted, the system defaults to the CRT station. Codes that can be entered include:
ED Estimated Departure Time
AD Actual Departure Time
EO Estimated Airborne Time
EA Estimated Arrival Time
AA Actual Arrival Time
RR Return to Ramp
FR Forced Return
1 LMVD Screen Display with ED Code:

LMVU:XS466/07MAR06/ATL/ED A/C G-AKOR DATE/TIME:
DEPARTURE
AD __ ____ / __ ____ FT ____ DL __ / __ / ____ / __
PX ______________________________________________
ARRIVAL
AA __ ____ / __ ____ EB __ ____ EA __ ____
DELAYED DEPARTURE
ED __ ____ NI __ ____ DL __ / __ / ____ / __
DELAYED TAKE-OFF
AD __ ____ EO __ ____ FT ____ DL __ / __ / ____ / __
RETURN TO RAMP
AD __ ____ RR __ ____ DL __ / __ / ____ / __
RETURN FROM AIRBORNE

FR __ ____ / __ ____
SUPPLEMENTARY INF _______________________________________________

ADDRESS ____________ ___________ ____________ ____________
Note: Use the correct code to request this screen, otherwise the system will transmit the wrong
information for entered data. For example if you want to enter some free format text on the
'SUPPLEMENTARY INF' line for ED message but in error enter it under AD entry code, when the MVT
message is transmitted, the information is sent in the AD message.
Note: All times must be in GMT, not local time.

LDP Messages
Explanation of the Departure (AD) Line of LMVT Screen:
DEPARTURE
AD 06 1015 / 06 1025 FT 0320 DL 21 / __ / 0010 / __
PX __________________________________________________________
Field Explanation
AD Actual Departure time. The first field is for the date, followed by the OFF-BLOCKS time in hours
and minutes. The following field is for the date and AIRBORNE time in hours and minutes. If the
date is not entered, the response is 'INSUFFICIENT DATA ENTERED'.
FT Flying Time. The estimated flying time entered allows the system to give an estimated arrival time
to the next station from the actual departure time entered. This is a mandatory entry. If left blank
the response is 'INSUFFICIENT DATA ENTERED'.
DL Delay codes and duration. The first two fields contain the reason codes. Only a maximum of two
reason codes can be specified. If there are more than two, enter the two main delay codes. The
last two fields are for the duration of the delay in hours and minutes. The reason codes can be
alpha or numeric characters.
PX Passengers. This field is a free format area and is for entering the total number of passengers on
board.
Explanation of the Arrival (AA/EA) Line on the LMVT:

ARRIVAL
AA 06 2002 / 06 2014 EB __ ____ EA __ ____
Field Explanation
AA Actual Arrival time. The first field is the date, followed by the TOUCH DOWN time in hours
and minutes. The following field is for the date and ON-BLOCKS time in hours and
minutes. If the date is not entered, the response is 'INSUFFICIENT DATA ENTERED'.
The date is a mandatory entry.
EB Estimated Block time. This field is the date, followed by the ESTIMATED ON-BLOCKS
time in hours and minutes.
EA Estimated Arrival time. This field is the date, followed by the ESTIMATED ARRIVAL time
in hours and minutes.

LDP Messages
Explanation of the Delayed Departure (ED) Line on LMVT:
DELAYED DEPARTURE
ED 06 1745 NI 06 1530 DL __ / __ / ____ / ___
Field Explanation
ED Estimated Departure time. This field is the date, followed by the ESTIMATED DEPARTURE
time in hours and minutes.
NI Next Information time. This field is the date followed by the NEXT INFORMATION time in
hours and minutes.
DL Delay codes and duration.
Explanation of the Delayed Take-Off (EO) Line on LMVT:

DELAYED TAKE-OFF
AD 15 2352 EO 16 0007 FT 0410 DL 11 / 28 / 0017 / 0005
Field Explanation
AD Actual Departure time. The first field is today's date, followed by the OFF-BLOCKS time in
hours and minutes. The following field is for the date and AIRBORNE time in hours and
minutes.
EO Estimated Off Time. This field is the date, followed by the ESTIMATED OFF time in hours and
minutes.
FT Flying Time.
Explanation of the Return to Ramp (RR) Line on LMVT:

RETURN TO RAMP
AD 06 1025 RR 06 0942 DL 33 / __ / 0050 / __
Field Explanation
AD New Actual Departure time. This field is the date, followed by the ACTUAL DEPARTURE time in
hours and minutes.
RR Returned to Ramp (before take-off) time. This field is the date, followed by the RETURNED to
RAMP arrival time in hours and minutes.

LDP Messages
Explanation of the Return from Airborne (FR) Line on LMVT:
RETURN FROM AIRBORNE
FR 06 1209 / 06 1222
Field Explanation
FR Forced Return (after take-off) time. The first field is for the date, followed by the TOUCH
DOWN time in hours and minutes. The following field is for the date, and ON-BLOCKS time in
hours and minutes.
Supplementary Information (SI) Line on LMVT:

SUPPLEMENTARY INF ATC DELAY DUE ONE RUNWAY OPERATION
Field Explanation
SI Supplementary Information. This is a free format area available for up to 60 characters. Each
reason code has its own SI field. It is important the correct reason code is input on the header
entry; otherwise the wrong SI information will be dispatched on the wrong MVT message.
Address Line on LMVT:

AADDRESS LHRKPBA LHRKLBA LHRLCBA LHRAPBA
LTNKKBA LTNAPBA
Field Explanation
ADDRESS Normally the MVT addresses are entered on the LAID screen for the specified station. However
it is possible to add extra addresses (maximum of 16) just for this particular flight and reason
code. It is important the correct reason code is input on the header entry, otherwise the wrong
MVT information message may be transmitted to the specified addresses.
1 MVT Message:
QU MIAKPXS
.ATLCRXS
MVT
XS893/16.G-OPCV.ATL
AD1700/1706 EA1906 MIA
DL22/0050
PX 6/97
SI ATC DELAY DUE ONE RUNWAY OPERATION AT ATL

LDP Messages
13.2. MVT Error Responses
ACTIVE RECORD CHANGED Re-display the screen before transmitting.

REDISPLAY
ADDRESS Address missing or invalid.
AIRLINE Invalid airline code entered.
AIRPORT Invalid airport code or does not exist (check LAID).
CITY NOT ON FLT ITINERARY City input is not on flight routing.
DATE Invalid date entered.
FLT/DATE Flight not active or invalid date entered.
FLIGHT TIME MISSING Estimated time en route not entered.
FORMAT Invalid input entered.
FUNCTION Invalid function code entered.
ILLEGAL DATE/TIME Invalid date (must be between 01 - 31) or time (must be

between 0001 - 2359) entered.
INSUFFICIENT DATA ENTERED MVT can not be processed as one or more fields are
missing.
INVALID DELAY CODE Delay code must be alpha or numeric.
INVALID MESSAGE CODE Invalid MVT message type code entered.
MSG NOT ALLOWED ON OPEN FLT Flight must be closed for this type of message.
NO MESSAGE TYPE SPECIFIED Message type not specified.
STATION Invalid station, or station not automated.
SELECT ED OR NI FIELDS ED or NI data fields are missing for this type of message.
Table 13.1 MVT Error Responses

LDP Messages
13.3. Manually Sending LDP Messages
Normally the load messages are sent at the end of flight (when LDP:R is entered on the LFSD screen)
to the addresses specified on the LAID screen for the stations on the flight route. However it is
possible to manually generate or re-generate these messages to the addresses created on the LAID
screen by the following entries:
LLDM:FLIGHT/DATE For LDM
LLPM:FLIGHT/DATE For LPM
LCPM:FLIGHT/DATE For CPM
LUCM:FLIGHT/DATE For UCM
LSLS:FLIGHT/DATE For SLS
The LLDM, LLPM, LCPM, LUCM and LSLS messages can now be sent to a teletype or ZZ address.
Example:
LLDM:FLT/DATE/ATL/ATLZZXS
The MVT message cannot be sent using this procedure.
If the flight is a multi-sector flight, it is possible to manually dispatch the messages only for a specific
downline station if required.
LLDM:FLIGHT/DATE/ORIGINATING STN/SPECIFIC DESTINATION
Note: If the station is the final station of the flight, the message goes to the addresses specified on the
LAID screen for this station, with the types A, F, or E. If it is not the final destination, it will only send
the message to the addresses specified by type A.

LDP Messages
14. LDP Message Address Table
14.1. LDP Airport Information Display (LAID)
A message address table must be set-up for every station and all handled carriers. This table
shows all the teletype addresses (with options) for each of the LDP messages shown.
At departure all the station records (LAID displays) on the flight itinerary, starting with the flight/leg
origin, are read and the address options are analyzed to determine the address to which the
messages are sent.
The entry to display an Airport Information Display table is:
LAID:AIRLINE/STATION
1 LAID: Screen
IATA CODE:ATL AIRLINE:XS MECH IND: CKI Y LDP Y
LOAD SHEET ADDRESS:_________ FUEL SHEET ADDRESS:__________

LOAD INSTR ADDRESS:_________
EZFW ADDRESS:_________ REJECT CITY CODE : ATL
LDM O ATLKLXS O ATLKPXS T ATLKLXS __ _____________
_ _______ _ _______ _ _______ __ _____________
LPM _ _______ _ _______ _ _______ __ _____________
_ _______ _ _______ _ _______ __ _____________
CPM O ATLKDXS O ATLGOXS T ATLKDXS __ _____________
_ _______ _ _______ _ _______ __ _____________
UCM _ _______ _ _______ _ _______ __ _____________
_ _______ _ _______ _ _______ __ _____________
SLS ATLSLXS _ _______ _______ _____________
CGO _ _______ _ _______ _ _______ __ _____________
MVT _ _______ _ _______ _ _______ __ _____________
_ _______ _ _______ _ _______ __ _____________
REJ OFF/CD LPI COM ASM LPM LDM CPM SOM GEN
501/LE 501/LK 501/LF 501/LE 501/LE 501/LE 501/LE 501/LE 501/LE
Explanation:
Field Explanation
MECH IND: CKI Y LDP Y Indicates whether this station is automated (a mechanized station using
the SITA DCS system of the Host Airline). If SITA DCS of the host
airline is not being used the indicators should show CKI N and LDP N.
Defaults to Y (Yes).
Note: If these indicators have been incorrectly set, and have been
amended after a flight has already been created, the best way to get the
system to pick-up the correct details is to cancel the flight
(LFIX:FLIGHT/DATE/CNCL), and recreate it by entering the aircraft
registration via FUI and entering the DPT: transaction again, or creating
the flight by using the LCFD transaction. The system will then pick up
the correct information.
LOAD SHEET ADDRESS Not required as the loadsheet printing is associated with the printer PID entered
on the CONLINK FILE of the CRT requesting the loadsheet. However it is
possible to send a loadsheet via Teletype (perhaps for sending a copy of a
loadsheet to a handled carrier for approval) by entering a valid (seven letter)
telex address code here. Be careful if entering an address, as every time a
loadsheet is requested, a copy will also go to the this address.
The same applies to FUEL SHEET, LOAD INSTR (loading instruction) and
EZFW addresses. These do not need to be entered unless they are really
required to be sent to a Teletype address.

LDP Message Address Table
Field Explanation
REJECT CITY CODE City code to which rejected messages are sent. The same city code should
appear on each LAID screen and match the city code entered on the
LLAL:LDPREC screen.
LDM/LPM/CPM/UCM/SLS/ These are the departure messages, sent at the end of a flight. A maximum of
MVT ten addresses are allowed per message, except for SLS, which is restricted to
five. The types of messages are:
LDM - Load Message.
LPM - Load Planning Message.
CPM - Container/Pallet Message.
UCM - ULD Control Message.
SLS - Statistical Load Summary.
MVT - Movement Message.
CGO Address line used for sending the ALD (automatic load plan) or LDVS display to
a teletype address. This is done by entering T at the end of the input:
LDVS:FLIGHT/DATE,T
ADDRESS OPTIONS These are the options that determine which LDP message the system will send
(O/F/T/E/A/N) once the flight is released. The various options are:
O (Origin) - option to use when this station is the origin of the flight/leg.
F (Final) - option to use when this station is the final destination of the flight
leg.
T (Transit) - option to use when this station is not the origin, nor the final
destination of the flight leg.
E (Endpoint) - option to use as a combination of O and F, when this station is
sometimes the origin and sometimes the final destination of the flight leg.
A (All) - option to use if this station is sometimes the origin of the flight, or the
destination of the flight/leg (but not the final destination).
N (Any) - option to use when this station is not the origin, nor the destination
of the flight/leg. This would not be used with the CGO message.
REJ OFF/CD Office Queue and Office Number the rejected messages will be sent. The
codes entered here (and the REJECT CITY CODE) must match the codes
defined in the LLAL:LDPREC screen.

LDP Message Address Table
15. Flight Journal History
15.1. Help Screen Display (FJ/H)
The flight journal history is a record of certain transactions that were input on a particular flight, or of
certain LDP database functions that might affect all flights. All times specified are in G.M.T.
If a supervisor forgets the entry format it is possible to enter the following:
FJ/H
The response is a display to the screen.
1 Flight Journal Help Screen FJ/H:

* * * * * * * * * * * * * * * *
* F L I G H T J O U R N A L - H E L P S C R E E N *
* *
* FJ:FLT/FLT DATE/LOPT/AGENT/FUNC/PID/DATE,TIME-DATE,TIME *
* FLT : FLIGHT NUMBER AND SUFFIX REQUESTED. *
* FLT DATE : DATE OF DEPARTURE FOR REQUESTED FLIGHT. *
* LOPT : LIST OPTION.FUNC/PIDNO/RANGE *
* AGENT : IF ENTERED, ONLY THIS AGENT IS SCANNED. *
* FUNC : IF ENTERED, ONLY THIS FUNCTION IS LISTED. *
* PID : IF ENTERED, OUTPUT IS REDIRECTED TO THAT PID. *
* DATE,TIME : ONLY THIS DATE,TIME RANGE IS SCANNED. *
* *
* *** EXAMPLE *** *
* FJ:XS100/13DEC98/D/A100/CCL/P1946/10DEC98,0100-26DEC98,1200 *
* *
* THE RESULT IS A DETAILED REPORT OF CCL TRANSACTIONS FOR *
* FLIGHT XS100 ON 13DEC98 MADE BY AGENT 100 BETWEEN DATES OF *
* 10DEC98,0100 AND 26DEC98,1200. OUTPUT TO PRINTER PID 1946 *
* (ALL UNSPECIFIED FIELDS DEFAULT TO PREDETERMINED VALUES.) *
* FOR A FURTHER EXPLANATION, PLEASE REFER TO CHAPTER 6, *
* SECTION 8, CHECK-IN FUNCTIONAL SPECIFICATION MANUAL. *
* * * * * * * * * * * * * * * * * * *

Flight Journal History
15.2. Display Flight History Journal (FJ)
The flight history record can contain various items, depending on the type of report requested.
The two types of reports are:
DETAIL (D)
SUMMARY (S)
The Detail report will show the actual transaction entry input, while the Summary report will only
display the function code used.
For flights more than one day past, a search range must be entered. The entry form is
FJflight/date/D/01APR05,0001-02APR05,2359. This type of transaction requests all transactions
within the time frame. If the flight has been stored to tape, then only a single date can be entered for
the range. The FLIGHT HISTORY for a flight can be accessed for up to ten (10) days on the 'ON-
LINE' system before it is transferred to 'STORAGE TAPES'. Once the information has gone on to
'STORAGE TAPES' it can be further accessed for up to ninety (90) days before it is erased. The main
difference between accessing the 'STORAGE TAPES' and the 'ON-LINE' system is it takes longer for
the system to process the entry from the tapes, and it is only possible to get a 'DETAILED' report for
the whole flight and not by an individual transaction.
An example of a Detail report request to the transmitting CRT:
FJ:FLIGHT/DATE/D/TRANSACTION CODE
For specific history, the actual transaction input code must be used. For example, to look for an LFSD
transaction, use the input code LFSU.
The Flight Journal Transmission Response:
FLIGHT JOURNAL - NOTIFICATION
YOUR JOURNAL REQUEST HAS BEEN PROCESSED. THE REPORT

WILL BE SENT TO PID: 07382
YOU MAY ERASE THIS SCREEN AND CONTINUE WORKING
A 'MSG WAIT' appears on the CRT, and the report is displayed by transmitting the 'MSG WAIT' key.
Note: The response can take longer than normal (depending on the history report entered), because
the system has to go through all the records to get the required information.
1 FJ:XS479/./D/LFSU
The FJ Format Example:
DVC-7382 0919 03JUN05
PREPARED:03JUN05 SITA DEPARTURE CONTROL FLIGHT JOURNAL
DETAILED REPORT
ALL TIMES G.M.T.
1 FJ:XS479/./D/LFSU
_____________________________________________________________________
2 03JUN05 1340 00761 LFSU XS 479 03JUN05 ATL
3 LFSU:XS0479_/03JUN___ATL_ MIA A/C G-OTHER ETD 1605

LCWS _ LLSP Y B737 DATE/TIME: 03JUN05/13.40.35
STATUS- LDP: C
_____________________________________________________________________
END REPORT
Explanation:
1. This shows the input flight history entry requested.
2. This shows the time of the transaction, the number of the agent who input the entry, the function
code input, the date, and the city where the transaction was input.

3. This shows the actual input entry.
If the report is required to be sent to a printer, the entry is:
FJ:FLIGHT/DATE/D/TRANSACTION CODE/P PID NUMBER
1
FJ:XS479/./D/LFSU/P1390'
An example of a summary report request entry to the transmitting CRT:

FJ:FLIGHT/DATE/S/TRANSACTION CODE
1
FJ:XS479/./S/LFSU'
After the usual response, and transmitting the 'MSG WAIT' key, the report will be in the following
format:
1 Flight Journal Summary Report :

DVC-7382 0919 03JAN06
PREPARED:03JAN05 SITA DEPARTURE CONTROL FLIGHT JOURNAL
SUMMARY REPORT
ALL TIMES G.M.T.
FJ:XS479/./S/LFSU
_____________________________________________________________________
TRANSACTION FLIGHT FLIGHT
DATE TIME AGENT FUNCTION NUMBER DATE CITY
_______ ____ _____ ________ ______ _______ _____
03JAN06 1340 00761 LFSU XS 479 03JAN06 ATL
_____________________________________________________________________
END REPORT
Explanation:
The summary report only gives the function code used (in this example CCL), but does not give the
actual input entry.
Note: With this type of report it is not possible to tell whether the function code was being 'ADDED' to
the flight or being 'DELETED'.
The entry to get all the transactions on a flight (this includes all CKI and LDP entries) is:
FJ:FLIGHT/DATE/D
FJ:FLIGHT/DATE/S

15.3. FJ LDP Codes
The following transaction codes are accessed by specifying the flight number in the FJ entry:
FJ:FLIGHT/DATE/D/CODE
FJ:FLIGHT/DATE/S/CODE
1
FJ:XS413/03APR/D/FUI
FUI LACS LALD LCOP LCPM LDSP LFFU LFIX
LFSU LLDM LLPM LLSP LMSU LMVU LODU LPAU
LPCU LPDU LSCU LUCM LUPD LZFW
The following transaction codes are not associated with a flight number and can only be accessed by
entering a time and date in the FJ entry:
FJ:D/CODE/DATE,TIME-DATE,TIME
Example
FJ:D/LAIU/01APR05,0001
LADU LAFU LAIU LAIX LCAD LCLU LCWU LDAT
LDFU LDVU LFDU LFLX LLAU LLBU LXAD
Note: This transaction is limited to one day only.

Error Responses
AUTHORITY The agent is not allowed to enter the transaction.
DATE The date/time range is invalid.
DEVICE Invalid PID number specified, or belongs to another Host Airline.
FORMAT Invalid entry.
OPTION The option specified is not 'S' or 'D'.
Table 15.1 Flight Journal LDP Error Responses

16. Check List for Last Minute Changes
16.1. LMC For Passengers With Baggage
If the flight has been CLOSED for both CKI and LDP, do the following steps:
1. Re-open LDP LFSD:FLIGHT/DATE LDP = O
2. Re-open CKI CCL: - FLIGHT
3. Enter new Passenger and Baggage details in CKI PA or PU or PW
4. Make sure new CKI details are updated in LDP Re-transmit LPAD/CGO screen
5. Close CKI CCL:FLIGHT
6. Close LDP LFSD:FLIGHT/DATE LDP = C
7. Issue Load sheet.
Note: Both CKI and LDP must be OPEN when the LMC is entered and that a LDP screen is re-
transmitted to pick-up the changes before the flight is CLOSED again, otherwise the CKI and LDP
figures may not match.
16.2. LMC for Cargo and Mail Only

If the flight has been CLOSED for both CKI and LDP, the following steps should be followed:
1. Enter new Cargo or Mail details on the LPAD:FLIGHT/DATE screen.
Note: It is not necessary to re-open CKI or LDP to add the changes.
16.3. LMC for Fuel

LMC for Trip (BURN-OFF) Fuel:
1. Enter new TRIP (B/O) fuel on the LFFD:FLIGHT/DATE screen.

Check List for Last Minute Changes
LMC for Take-Off Fuel:
If there is enough time, follow these steps:
1. Enter new TAKE-OFF fuel on the LFFD:FLIGHT/DATE screen.
If there is not much time left before departure, it is possible to do the following:
1. Enter new TAKE-OFF fuel directly onto the LFSD:FLIGHT/DATE screen and at the same time set
'LLSP = Y' to get Load sheet printed
Note: The LFFD screen will still display the original figure. After flight departure the LFFD screen
should be manually updated with the correct figure.

Check List for Last Minute Changes
17. Load Planning Check List
17.1. Initial Check Lists
ENTER A/C REGISTRATION (MAX 24 HOURS BEFORE STD):
FUI:FLIGHT NUMBER/DATE/STATION/ARN/REGISTRATION
DPT:FLT/DATE LCFD: may be displayed to build schedule if DPT: did not Process
CHECK FLIGHT CREATED IN LDP AND LINKED TO CKI:

LFSD:FLIGHT NUMBER/DATE
CHECK CORRECT A/C REGISTRATION ENTERED:

LODD:FLIGHT NUMBER/DATE
ENTER ANY CHANGE OF A/C REGISTRATION:

LCFD:FLIGHT NUMBER/DATE
ENTER ANY CREW/TOW/LAW/DOW/DOI/EQUP AMENDMENTS:

LODD:FLIGHT NUMBER/DATE
ENTER CORRECT TAKE-OFF/TRIP FUEL FIGURES:

LFFD:FLIGHT NUMBER/DATE
ENTER ESTIMATED BAG FIGURES (AFTER PNL LOADED):

LPAD:FLIGHT NUMBER/DATE/PAX
CHECK 'AVERAGE BAG WT' AND TRANSMIT FROM BOTTOM OF SCREEN
CHECK BOOKED PASSENGERS AND ESTIMATED BAGGAGE FIGURES:

LPAD:FLIGHT NUMBER/DATE/PAX3
For Containerized Aircraft:

ENTER/PLAN DISTRIBUTION OF CARGO/MAIL/ESTIMATED BAG FIGURES:
LPAD:FLIGHT NUMBER/DATE/CGO1
PRINT LOADING INSTRUCTION:

LDSP:FLIGHT NUMBER/DATE
ADD ANY SPECIAL INFO FOR LDM:

LMSD:FLIGHT NUMBER/DATE/LLDM
CHECK FLIGHT STATUS AND CLOSE FLIGHT:

ENTER ANY LAST MINUTE LOAD ADJUSTMENTS:

CHECK TRIM:
LPDD:FLIGHT NUMBER/DATE

Load Planning Check List
For Non-Containerized Aircraft and Automatic Load Planning:
ENTER CARGO AND MAIL PALLET/CONTAINER DETAILS:
NOTE: DO NOT ENTER ANY BAGGAGE FIGURES OR HOLD POSITIONS
CHECK FOR SYSTEM SELECTED DECK VERSION:

LDVS:FLIGHT NUMBER/DATE
REQUEST SYSTEM TO DO AUTOMATIC LOAD DISTRIBUTION:

LALD:FLIGHT NUMBER/DATE
ENTER ANY ADJUSTMENTS FOR PALLET/CONTAINER POSITIONS:

LUPD:(MOVE/SWITCH/NOFIT)
EXIT AUTOMATIC LOADING PROGRAM:

LUPD:DEL
ENTER ANY MANUAL CARGO/MAIL/BAG POSITION CHANGES:

PRINT LOADING INSTRUCTION:

LDSP:FLIGHT NUMBER/DATE
ADD ANY SPECIAL INFO FOR LDM (CPM/UCM)

LMSD:FLIGHT NUMBER/DATE/LLDM (LCPM/LUCM)
CHECK FLIGHT STATUS AND CLOSE FLIGHT:

ENTER ANY LAST MINUTE LOAD ADJUSTMENTS:

CHECK TRIM:
LPDD:FLIGHT NUMBER/DATE
17.2. Print Loadsheet / Send Departure Messages / Release Flight Control

PRINT LOADSHEET (2 WAYS):
1/LFSD:FLIGHT NUMBER/DATE (LLSP=Y LDP=C CKI=C)
2/LLSP:FLIGHT NUMBER/DATE
DISPATCH LDP MESSAGES AND RELEASE FLIGHT:

LFSD:FLIGHT NUMBER/DATE (LDP=R)
NOTE. PARAM1 MUST HAVE 'CLOSE MSGS SENT BY LFSU = Y
TO DISPATCH MESSAGES INDIVIDUALLY:

LLDM:FLIGHT NUMBER/DATE/STATION (SAME FOR LPM/CPM/UCM/SLS)

Load Planning Check List
18. Glossary
-A-
ADL - PNL addition/deletion list
AEC - Automatic Equipment Change
ALP - Automatic Load Planning
API - Advanced Passenger Information
-B-
BI - Basic Index
BRA - Bulk Recheck Accepted passengers
BRN - Bulk Recheck Not Checked-In Passengers
BTM - Baggage Transfer Message
BW - Basic Weight
-C-
CKI - Check-in
CND - Configuration Table Number Display
COG - Center of Gravity
COM - Close Out (final) Message. (Dispatched to all stations)
CPM - Containerized Pallet Message
CRT - Cathode Ray Tube, this is the display
CSD - Created Schedule Data
CSM - Created Schedule Modification
-D-
DFL - Delete Flight
DOI - Dry Operating Index
DOW - Dry Operating Weight
DPID - Entry for Printer/Check-in Zone Information
DRC - Destination Remarks Creation
-E-
EDIFACT - Electronic Data Interchange for Administration, Commerce and Transport.
ETL - Electronic Ticket List.
ETM - EDIFACT Transfer Message (ITCI partner listed from departure city LH only).
-F-

Glossary
FCP - Fuel Curve Point.
FDC - Flight Schedule.
FDD - Flight Data Display.
FIR - Flight Irregular Operations.
FLP - Flight Planning
FTL - Frequent Traveler List.
FUI - Flight Update Information.
-G-
GMT - Greenwich Mean Time
-I-
IDM - Industry Discount Message. (Dispatched to next downline station on Multi-sector flights).
IFM - Interline (EDIFACT flights) Fallback Message.
-L-
LDP - Load Planning.
LDVS - System Selected Deck Version.
-M-
MAC - Mean Aerodynamic Chord.
MD - Manifest Display.
MP - Moveable Partition.
-N-
NAM - SSName Check-In with Seat Selection.
NOTOC - Notification to Captain.
NPRO - Releases all records, except the PNL / ADL records for the flight, and clears the Manifest
Index so a PNL will no longer show processed.
-P-
PCI - Passenger Statistics
PCTC - Passenger Contact
PDQ - Physical Device Queuing.
PFS - Passenger Final Sales message. (Originating station only)
PID - Physical device identifier. Numeric address of a peripheral device that is also known as position
identifier or port identifier.
PIL - Passenger Information List. (Originating station only).

Glossary
PIM - Passenger Information Message.
PN - Page Next.
PNL - Passenger Name List.
PRL - Passenger Reconciliation List.
PSM - Passenger Service Message. (Dispatched to all stations)
PTM - Passenger Transfer Manifest. (Dispatched to all stations having transfer).
-S-
SLS - Statistical Load Summary.
SOM - Seats Occupied Message. (Dispatched to next downline station)
SSR - Special Service Request
STD - Scheduled Time of Departure.
SUD - Special Usage Description.
-T-
TOW - Take off Weight.
TPM - Teletype Passenger Manifest. (Dispatched to all stations).
-U-
UCM - ULD Control Message.
UTC - Coordinated Universal Time (same as GMT).
-V-
VDT - Video Display Terminal. A computer display.
VPID - View/Print Priority Messages on PID Queue.
-W-
WTN - Weight Table Number.
-Z-
ZFW - Zero Fuel Weight.
Style Symbols
1 - Example indicator
X - Start of Entry indicator

Glossary
Glossary
19. Index
ACARS Codes
Error Responses.....................................28 Flight Journal LDP..................................88
ACARS Loadsheet Information .....................27 LDM ........................................................34
Configuration Table Display............................ 5
Active Flight
Container/Pallet Message.............................67
Example....................................................7
Active Flights Containerized Aircraft
List ..........................................................15 Example..................................................31

LPDD Example.......................................37
Add Special Information ................................51
Containerized Aircraft
Additional Flight Entries and Information ......61
Check List...............................................91
Address Line on LMVT..................................80
CPM Message ..............................................67
Aircraft Registration Data Display ...................6
Create
Aircraft Version/Type Change .......................75
Manual Flight............................................ 3
Arrival Line on LMVT.....................................78 Delayed Departure Line on LMVT ................79
ASM Message Delayed Take-off Line on LMVT ...................79
Example....................................................9 Departure Line on LMVT ..............................78
Automatic Load Planning ..............................38
Display
Automatic Load Planning Check List ............92
FJ/H ........................................................85
Burn-off Fuel .................................................89 LOLD ......................................................41
Payload Available.............................29, 30
Cabin Loading ...............................................62
Display
Cargo Allotment ............................................37
Passenger Checked-In...........................25
Cargo and Mail Display
LMC ........................................................89 LSOD......................................................72
Cargo Payload Screen ..................................31 Display
CGO1 Screen................................................31 LCOP......................................................73
Change Display Flight History Journal .......................86
Aircraft Version/Type ..............................75 DPT Screen .................................................... 9
Change Baggage Weights Error Responses
Non-Containerized Aircraft .....................34 ACARS ...................................................28
Check List FIR..........................................................13
Initial .......................................................91 FUI............................................................ 9
Load Planning.........................................91 LALD.......................................................40
LCFD Screen............................................ 4
Check List LFFD.......................................................21
Containerized Aircraft .............................91 LFIX ........................................................61
Check List LFLD.......................................................15
LFSD ......................................................49
Non-containerized Aircraft ......................92 LLSP.......................................................58
Check List LODD......................................................19
LOLD ......................................................41
Automatic Load Planning........................92 LPAD ......................................................34
Check List for Last Minute Changes .............89 MVT ........................................................81
CND A Screen.................................................5 Example
Index
Containerized Aircraft .......................31, 37 Flight Journal History ....................................85
CPM Message ........................................67
Flight Journal Summary Report Example .....87
FJ Format ...............................................86
Flight Journal Summary Report..............87 Flight Status Screen......................................43
Jump Seat Passenger ............................70
LALD.......................................................38 Flight Update Information ............................... 8
LCWS Screen .........................................44 Fuel
LDSP ......................................................53
LDVS ......................................................38 LMC ........................................................89
LMVD Screen .........................................77 Fuel Screen Display......................................21
LNTC ......................................................54 FUI Error Responses ...................................... 9
Load Message ........................................64
LODU Display .........................................17 FUI Screen...................................................... 8
LPAD ......................................................23 General Information ........................................ 1
LPM ........................................................65
MVT Message.........................................80 Help Screen Display .....................................85
Non-containerized Aircraft ......................31
History, Flight Journal ...................................85
PAX2 Screen ..........................................25
PAX4 Screen ..........................................29 Initial Check lists ...........................................91
PAX5 Screen ..........................................29
Jump Seat Passenger
PAX6 Screen ..........................................30
Seats Occupied Display .........................72 Example..................................................70
SLS Message .........................................68 Jump Seat Passengers.................................70
SOM........................................................64
Transit Load............................................66 LACD Screen .................................................. 6
UCM........................................................67 LAID
Zero Fuel Weight Display .......................72
Extra Crew.....................................................69 LDP Airport Information Display.............83
LALD
EZFW Display ...............................................72
Error Responses ....................................40
FDD Screen ....................................................7 Example..................................................38
FIR LALD Screen.................................................38
Error Responses.....................................13 Last Minute Changes
FIR Screen ....................................................10 Check List...............................................89
FJ LCFD Screen .................................................. 3
Display ....................................................86 Blank......................................................... 3
FJ LDP Codes...............................................88 Error Responses ...................................... 4
LCOP Display ...............................................73
FJ/H
LCWS Screen
Display ....................................................85
Flight Aircraft Changes..................................75 Example..................................................44
LDM Codes ...................................................34
After CKI and LDP Initialization ..............76
After CKI Initialization .............................75 LDP Airport Information Display ...................83
After Flight Closed for CKI and LDP.......76
Before Flight Closure..............................76 LDP Message Address Table .......................83
Before Flight Initialization .......................75 LDP Messages..............................................77
Before LDP Initialization .........................75
Initialized Flight not Connected to CKI ...76 Manually Sending...................................82
Flight Cancellation.........................................61 LDSP
Flight Data Display ......................................5, 7 Screen

LDSP Screen
Flight Initialization............................................9
Example..................................................53
Flight Irregular Operations ............................10
Index
LDVS Screen ................................................38 Print ........................................................57
LFFD Screen.................................................21 Loading Instruction, Print ..............................52
LFFU Loadsheet Information
Update ....................................................21 ACARS ...................................................27

LFIX LODD Screen................................................17
Error Responses.....................................61 LODU Screen................................................19

Screen ....................................................61 LOLD
LFLD
Error Responses ....................................41
Error Responses.....................................15 LOLD Display................................................41
LFLD Screen .................................................15
LPAD
LFSD
Example..................................................31
Error Responses.....................................49 Screen ....................................................62
Manual Flight ..........................................48 LPAD Error Responses ................................34
LFSD Screen
LPAD Screen ................................................23
Nose Heavy Aircraft................................48
LPCD Screen ................................................37
LFSD Screen.................................................43
LPDD Display................................................35
List of Active Flights ......................................15
LPDD Example
LLSP
Containerized Aircraft.............................37
Error Responses.....................................58
LSCD
LLSP Screen .................................................57
Screen ....................................................62
LMC for Cargo and Mail ................................89
LSOD Display ...............................................72
LMC for Fuel .................................................89
Mail Allotment ...............................................37
LMC for Passengers with Baggage ..............89
Manual Flight
LMC for Take-off Fuel ...................................90
LFSD ......................................................48
LMSD Manual Flight Creation.................................... 3
Screen ....................................................51 Manually Sending LDP Messages................82
LMVT
Master Flight
Address Line...........................................80
Example.................................................... 7
Arrival Line..............................................78
Delayed Departure Line..........................79 Message Address Table
Delayed Take-off Line ............................79 LDP.........................................................83
Departure Line ........................................78
Return from Airborne Line ......................80 Miscellaneous Display ..................................29
Return to Ramp Line ..............................79 Movement Message......................................77
Supplementary Information Line.............80
MVT Error Responses ..................................81
LNTC
MVT Message
Example..................................................54
Screen ....................................................54 Example..................................................80
Load Distribution Screen...............................31 Non-Containerized
Load Message...............................................64 Change Baggage Weights .....................34
Load Planning Check List .............................91 Non-containerized Aircraft
Load Planning Message................................65 Check List...............................................92

Load Distribution ....................................31
Load sheet Nose Heavy Aircraft
Index
LFSD.......................................................48 Printing Request ...........................................51
Notification to Captain ...................................54 Release Flight Control ..................................92
NOTOC .........................................................54 Return from Airborne Line on LMVT.............80
Printing....................................................56 Return to Ramp Line on LMVT .....................79
Offload Display..............................................41
Screen
Operational Data Display ..............................17
Cargo Distribution...................................31
Operational Screen Display ..........................17 CGO1 .....................................................31
Flight Status ...........................................43
Passenger Area Seating Display ..................23
LDSP ......................................................52
Passenger Booked Display ...........................26 LDVS ......................................................38
LFSD ......................................................43
Passenger Checked-In Display.....................25 LLSP.......................................................57
Passenger Payload Screens.........................23 LMSD......................................................51
LNTC ......................................................54
Passenger Transit Details .............................24 Load Distribution ....................................31
Passengers with Baggage LPAD ......................................................62
LSCD ......................................................62
LMC ........................................................89
Seats Occupied by Cargo.............................62
PAX1 Screen.................................................24
Seats Occupied Display................................72
PAX2 Screen.................................................25
Seats Occupied Message.............................63
Example..................................................25
PAX3 Send Departure Messages ...........................92
Example..................................................26 SLS Message................................................68

Screen ....................................................26 Statistical Load Summary .............................68
PAX4 Display ................................................29 Stretcher Passengers ...................................71
PAX4 Screen Supplementary Information Entry .................51
Example..................................................29 Supplementary Information Line on LMVT ...80
PAX5 Screen
System Selected Deck Version ....................38
Display ....................................................29
Example..................................................29 Transit Flight .................................................63
PAX6 Screen Automated Station..................................63
Non-automated Station ..........................63
Display ....................................................30
Example..................................................30 Transit Miscellaneous 2 Display ...................30
Payload Available Display.......................29, 30 Transit Miscellaneous Display ......................29
Payload Transfer Between Flights ................73 Trim Display ..................................................35
Print Load Sheet ...........................................57 ULD Message ...............................................67
Print Loading Instruction ...............................52 Update
Print Loadsheet .............................................92 Fuel Screen ............................................21
Operational Screen ................................19
Printing NOTOC ............................................56

Index

SDCS Load Planning User Guide - 7.1 - A4

Uploaded by

Copyright:

Available Formats

You might also like

SDCS Load Planning User Guide - 7.1 - A4

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SDCS Load Planning User Guide - 7.1 - A4

Uploaded by

Copyright:

Available Formats

Passenger Solutions

SITA Departure Control Services

Load Planning User Guide

1.2. Course Objectives................................................................................................................................... 1

2. Manual Flight Creation................................................................................................................... 3

2.2. Error Responses ..................................................................................................................................... 4

3. Flight Data Display ......................................................................................................................... 5

3.2. Aircraft Registration Data Display (LACD) .............................................................................................. 6

3.3. Flight Data Display (FDD) ....................................................................................................................... 7

3.4. Flight Update Information (FUI)............................................................................................................... 8

3.5. FUI Error Responses .............................................................................................................................. 9

3.6. Flight Initialization (DPT) ......................................................................................................................... 9

3.7. Flight Irregular Operations (FIR) ........................................................................................................... 10

4. List of Active Flights .................................................................................................................... 15

4.2. Error Responses ................................................................................................................................... 15

5. Operational Screen Display ........................................................................................................ 17

5.2. Operational Screen Update (LODU) ..................................................................................................... 19

5.3. Error Responses ................................................................................................................................... 19

6. Fuel Screen ................................................................................................................................... 21

6.2. Fuel Screen Update (LFFU).................................................................................................................. 21

6.3. Error Responses ................................................................................................................................... 21

7. Passenger Payload Screens (LPAD) ..........................................................................................23

7.2. Passenger Transit Details (PAX1) ........................................................................................................ 24

7.3. Passenger Checked-In Display (PAX2) ................................................................................................ 25

7.4. Passenger Booked Display (PAX3) ...................................................................................................... 26

7.5. ACARS Loadsheet Information ............................................................................................................. 27

7.6. Error Responses ................................................................................................................................... 28

SITA Departure Control Services – Load Planning User Guide

7.8. Payload Available Display - Transit Miscellaneous1 (PAX5) ................................................................ 29

7.9. Payload Available Display - Transit Miscellaneous2 (PAX6) ................................................................ 30

8. Cargo Payload and Load Distribution Screens.........................................................................31

8.2. LPAD:Flight/Date/CGO1 Error Responses ........................................................................................... 34

8.3. Trim Display (LPDD) ............................................................................................................................. 35

8.4. Cargo / Mail Allotments (LPCD) ............................................................................................................ 37

8.5. System Selected Deck Version (LDVS) ................................................................................................ 38

8.6. Automatic Load Planning (LALD).......................................................................................................... 38

8.7. LALD: Flight/Date Error Responses...................................................................................................... 40

8.8. Offload Display (LOLD) ......................................................................................................................... 41

8.9. LOLD Error Responses......................................................................................................................... 41

9. Flight Status Screen..................................................................................................................... 43

9.2. Error Responses ................................................................................................................................... 49

10. Add Special Information and Printing Request ........................................................................51

10.2. Print Loading Instruction (LDSP)........................................................................................................... 52

10.3. Notification to Captain (NOTOC)........................................................................................................... 54

10.4. Print Load sheet (LLSP)........................................................................................................................ 57

10.5. Error Responses ................................................................................................................................... 58

11. Additional Flight Entries and Information .................................................................................61

11.2. Cabin Loading/Seats Occupied By Cargo (LSCD)................................................................................ 62

11.2.1 Seats Occupied by Cargo (LSCD)............................................................................................. 62

11.2.2 Cabin Loading (LPAD:FLT/DATE/CGO).................................................................................... 62

11.3. Transit Flights ....................................................................................................................................... 63

11.3.1 Transit Flight from an Automated Station .................................................................................. 63

11.3.2 Transit Flight from an Non-Automated Station........................................................................... 63

11.4. Extra Crew (XXXCREW)....................................................................................................................... 69

11.5. Jump Seat Passengers ......................................................................................................................... 70

11.6. Stretcher Passengers ........................................................................................................................... 71

11.7. EZFW Display (LZFW) .......................................................................................................................... 72

SITA Departure Control Services – Load Planning User Guide