0029200000000ma03 2-0 Sdd-Um

Supply, Installation, Testing and Commissioning of Tower ATS Automation System
Situation Data Display User Manual (SDD-UM)

Edition: 2 Revision: 0
04 November2010
Document Number: 0029200000000MA03
Prepared for: AIRPORTS AUTHORITY OF INDIA (AAI) Airports Authority of India, Rajiv Gandhi Bhawan, Safdarjung Airport, New Delhi - 110
Prepared by:
Indra Sistemas, S.A.

Ctra. de Loeches, 9 28850 Torrejn de Ardoz Madrid, Spain
Indra Proprietary Information This document contains proprietary data pertaining to items, or components, or processes or other matter developed or acquired at the private expense of the Indra Sistemas, S.A. and/or any other titular holder and is restricted to use only by Indra or the Customer under the terms of this Proposal. Neither said document nor said data shall be furnished or disclosed to or copied or used by other persons outside the conditions of this Proposal as applicable without the express written approval of Indra Sistemas and/or any other titular holder.
DOCUMENT N: 0029200000000MA03
Edition: 2 Revision:0 Date: 04 November2010
This page left intentionally blank
Situation Data Display User Manual
Use or Disclosure of this information is subject to the restrictions on the tile page of this document
Page ii
DOCUMENT N: 0029200000000MA03
Page iv
DOCUMENT N: 0029200000000MA03
PAGE EDITION AND REVISION RECORD
This document contains the following pages in the indicated editions and revisions PAGE All All EDITION 01 02 REVISION 0 0 PAGE EDITION REVISION PAGE EDITION REVISION
Page v
DOCUMENT N: 0029200000000MA03
Page vi
DOCUMENT N: 0029200000000MA03
REGISTER OF CHANGES TO THE DOCUMENT
EDITION 1 2
REVISION 0 0
DATE 2010-08-04 2010-11-04
AFFECTED PAGES All All First Edition Second Edition
REASON FOR CHANGE
Page vii
DOCUMENT N: 0029200000000MA03
Page viii
DOCUMENT N: 0029200000000MA03
Table of Contents
1 Introduction ....................................................................................................................... 1-1 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 2 2.1 Scope ........................................................................................................................ 1-1 General System Description ........................................................................................ 1-1 Situation Data Display (SDD) Position Overview .......................................................... 1-3 Manual Structure ........................................................................................................ 1-3 Notation Used in this Manual....................................................................................... 1-4 Selecting Menus, Icons and Field Text Entering ........................................................... 1-6 Rules to Enter and Delete Data .......................................................................... 1-8 Common Actions to all SDD Windows ......................................................................... 1-9 Procedures to Close Actions in Windows ................................................................... 1-10 Common Actions on Windows ................................................................................... 1-11 SDD SIT Area ............................................................................................................ 2-1 Plots.................................................................................................................. 2-2
1.6.1
Functional Description ....................................................................................................... 2-1 2.1.1
2.1.2 Tracks ............................................................................................................... 2-2 2.1.2.1 Track Symbol .............................................................................................. 2-2 2.1.2.2 Track Label ................................................................................................. 2-3 2.1.2.2.1 Controlled Enroute role ......................................................................... 2-3 2.1.2.2.2 Controlled Approach role....................................................................... 2-5 2.1.2.2.3 Controlled Tower role ............................................................................ 2-7 2.1.2.2.4 Inbound Enroute role ............................................................................ 2-8 2.1.2.2.5 Inbound Approach role ........................................................................ 2-10 2.1.2.2.6 Inbound Tower role ............................................................................. 2-11 2.1.2.2.7 OAT traffic seen by GAT sectors. Enroute role ..................................... 2-13 2.1.2.2.8 OAT traffic seen by GAT sectors. Approach role .................................. 2-14 2.1.2.2.9 OAT traffic seen by GAT sectors. Tower role ....................................... 2-15 2.1.2.2.10 Uncontrolled outside the sector. Enroute role ....................................... 2-16 2.1.2.2.11 Uncontrolled outside the sector. Approach role .................................... 2-17 2.1.2.2.12 Uncontrolled outside the sector. Tower role ......................................... 2-18 2.1.2.2.13 Uncontrolled in sector. Inbound Enroute role ........................................ 2-19 2.1.2.2.14 Uncontrolled in sector. Inbound Approach role ..................................... 2-20 2.1.2.2.15 Uncontrolled in sector. Inbound Tower role .......................................... 2-22 2.1.2.2.16 Not correlated. Enroute role ................................................................ 2-23 2.1.2.2.17 Not correlated. Approach role .............................................................. 2-24 2.1.2.2.18 Not correlated. Tower role ................................................................... 2-25 2.1.2.2.19 Not correlated in sector. Enroute role ................................................... 2-25 2.1.2.2.20 Not correlated in sector. Approach role ................................................ 2-26 2.1.2.2.21 Not correlated in sector. Tower role ..................................................... 2-27 2.1.2.2.22 Sensitive Label Fields ......................................................................... 2-28 2.1.2.2.23 Action: Partial Track Label Orientation => {Graphical Mode} ................. 2-29 2.1.2.2.24 Action: Toggle Vertical Speed/Ground Speed => {Graphical Mode} ...... 2-29 2.1.2.3 Extended Label ......................................................................................... 2-30 2.1.2.4 Track Colour ............................................................................................. 2-32
Situation Data Display User Manual Use or Disclosure of this information is subject to the restrictions on the tile page of this document Page ix
DOCUMENT N: 0029200000000MA03
2.1.2.5 Leader Line ............................................................................................... 2-33 2.1.2.5.1 Action: Track Label Free Individual Position Change ............................ 2-34 2.1.2.6 Historical Positions .................................................................................... 2-35 2.1.2.7 Velocity Vector .......................................................................................... 2-35 2.1.2.8 Presentation Range ................................................................................... 2-36 2.1.2.9 Callsign Menu ........................................................................................... 2-36 2.1.2.9.1 Action: Actions in Callsign Menu .......................................................... 2-38 2.1.2.10 Tracks in Distress ...................................................................................... 2-40 2.1.2.11 Special Position Indicator (SPI) .................................................................. 2-40 2.1.2.12 Tracks in STCA ......................................................................................... 2-40 2.1.2.13 Tracks in MTCD ........................................................................................ 2-41 2.1.2.13.1 Action: MTCD Conflict ......................................................................... 2-44 2.1.2.14 Tracks in APW .......................................................................................... 2-47 2.1.2.15 Tracks in MSAW ....................................................................................... 2-48 2.1.2.15.1 Profiles in MSAW Areas ...................................................................... 2-48 2.1.2.16 RVSM Alarm ............................................................................................. 2-49 2.1.2.17 8.33 Alarm ................................................................................................ 2-49 2.1.2.18 CLAM Alert ............................................................................................... 2-49 2.1.2.19 Heading Alarm .......................................................................................... 2-50 2.1.2.20 Route Conformance and Adherence Monitoring (RAM) Alert ....................... 2-50 2.1.2.21 QNH Altitude Correction ............................................................................ 2-50 2.1.2.22 Synthetic Tracks........................................................................................ 2-50 2.1.2.22.1 Creation and cancellation of Synthetic Track ........................................ 2-51 2.1.3 Flight Plan Correlation ...................................................................................... 2-51 2.1.3.1 Automatic Correlation ................................................................................ 2-52 2.1.3.2 Manual Correlation/ Decorrelation .............................................................. 2-52 2.1.3.3 Abbreviated Flight Plan (APL) .................................................................... 2-53 2.1.3.3.1 Action: Create an APL......................................................................... 2-54 2.1.3.4 Minimal Flight Plan .................................................................................... 2-55 2.1.3.4.1 Action: Minimal FP Creation => {Graphical Mode} ................................ 2-56 2.1.4 Meteorological Data ......................................................................................... 2-57 2.1.5 Range Bearing Lines (RBL) .............................................................................. 2-58 2.1.5.1 Action: Create Range Bearing Line => {Graphical Mode} ............................ 2-61 2.1.5.2 Action: Program RBL ALARMS => {[RBL ALM]} ......................................... 2-62 2.1.5.3 Action: Partial RBL Removing => {Graphical Mode} .................................... 2-64 2.1.5.4 Action: Remove RBLs => {[RBL OFF]} ....................................................... 2-64 2.1.6 Flight Plan Route ............................................................................................. 2-65 2.1.6.1.1 Action: Graphical Route Visualization .................................................. 2-65 2.1.6.1.2 Action: Graphical Route Modification ................................................... 2-67 Actions on Owned Tracks................................................................................. 2-69
2.1.7
2.1.8 Transfer Actions............................................................................................... 2-69 2.1.8.1 Action: Transfer to next sector in route ....................................................... 2-69 2.1.8.2 Action: Transfer to any sector .................................................................... 2-70 2.1.8.3 Action: Request of Frequency => [ROF] ..................................................... 2-71 2.1.8.4 Action: Request of Transfer Level .............................................................. 2-72 2.1.9 Miscellaneous Actions within the SIT_A ............................................................ 2-78 2.1.9.1 Cleared Flight Level (CFL) ......................................................................... 2-78 2.1.9.1.1 Action: Input of New CFL => {Graphical Mode} .................................... 2-79 2.1.9.2 Action: Enter New HDG (Heading) ............................................................. 2-80 2.1.9.3 Action: Enter New XFL (Exit Flight Level) ................................................... 2-81
Page x
DOCUMENT N: 0029200000000MA03
2.1.9.4 2.1.9.5 2.1.9.6 2.1.9.7 2.1.9.8 2.2 2.2.1 2.2.2 2.2.3 2.2.4 2.2.5
Action: Enter New SPD (Speed)................................................................. 2-82 Action: Enter New VR (Vertical Rate) ......................................................... 2-83 Action: Enter New RFL(Requested Flight Level) ......................................... 2-84 Action: SSR Code Assignment/ Modification to PSR Track.......................... 2-84 Action: Inter-Console Marker => <Alt> + ............................................... 2-85
SDD General Information Area .................................................................................. 2-87 [ST] Icon .......................................................................................................... 2-88 Minimum Safe Altitude Warning [MSAW] Icon ................................................... 2-88 Short Term Conflict Alert [STCA] Icon ............................................................... 2-88 Area Proximity Warning [APW] Icon .................................................................. 2-89 Medium Term Conflict Detection [MTCD] Icon ................................................... 2-89
2.2.6 Primary Search Radar Tracks [PSR T] Icon ...................................................... 2-89 2.2.6.1 Action: Manual Creation of PSR Tracks => {[PSR T]}.................................. 2-89 2.2.7 [OPTIONS] Icon ............................................................................................... 2-90 2.2.7.1 Action: Activation/Inhibition of History Tracks => {[OPTIONS] -> [HISTORY]} or {<Alt> + <H>} ..................................................................... 2-90 2.2.8 [Operational Mode] Icon ................................................................................... 2-91 2.2.8.1 Action: Operational Mode Selection => {[Operational Mode]} ...................... 2-92 2.2.9 Radar Source [RADAR] Icon ............................................................................ 2-93 2.2.9.1 Action: Select Radar Source => {[RADAR]} ................................................ 2-93 2.2.10 [Presentation Range] Icon ................................................................................ 2-93 2.2.10.1 Action: Presentation Range Selection => {[Presentation Range]} ................ 2-94 2.2.11 Altitude Filters Activation/ Inhibition [FALT] Icon ................................................ 2-95 2.2.11.1 Action: Activate/ Inhibit the Altitude Filter .................................................... 2-95 2.2.11.2 Filters Limits Window .............................................................................. 2-95 2.2.11.3 Action: Height Filter Limits Selection => {[Filter Limits]} ............................... 2-96 2.2.11.4 Action: Activate/ Inhibit Altitude Filters => {[FALT]}...................................... 2-97 2.2.12 Sectors Display ................................................................................................ 2-98 2.2.12.1 Action: Sectors Display .............................................................................. 2-98 2.2.13 Interactive Expansion Scale [EXP+] Icon .......................................................... 2-98 2.2.13.1 Action: Interactive Expansion => {[EXP+]} .................................................. 2-98 2.2.14 Interactive Contraction Scale [EXP-] Icon.......................................................... 2-99 2.2.14.1 Action: Interactive Contraction: {[EXP-]} or {<F10>} .................................. 2-100 2.2.15 Centring [CEN] Icon ....................................................................................... 2-101 2.2.15.1 Action: Presentation Centring => {[CEN]} ................................................. 2-101 2.2.16 De-Centring [DCEN] Icon ............................................................................... 2-101 2.2.16.1 Action: Presentation De-Centring => {[DCEN]} ......................................... 2-101 2.2.17 Flight Plan [FPL] Icon ..................................................................................... 2-101 2.2.17.1 FP Operation Window ............................................................................. 2-102 2.2.17.1.1.1 Flight Plan Status ..................................................................... 2-107 2.2.17.1.1.2 Rules for Entering Data ............................................................ 2-108 2.2.17.1.1.2.1 Route Field Validation Rules ............................................ 2-108 2.2.17.1.2 FPLs Actions .................................................................................... 2-110 2.2.17.1.3 Action: Visualize FPL => {[FP Act.] => [View]} .................................... 2-110 2.2.17.1.4 Action: FPL History => {[FP Act.] => [Hist.]} ....................................... 2-111
Situation Data Display User Manual Use or Disclosure of this information is subject to the restrictions on the tile page of this document Page xi
DOCUMENT N: 0029200000000MA03
2.2.17.1.5 Action: Create FPL => {[FP Act.] => [CREATE]} ................................. 2-112 2.2.17.1.6 Action: Create a Current FPL => {[FP Act.] => [CREATE CURRENT]} 2-114 2.2.17.1.7 Action: Modify FPL => {[FP Act.] => [Modify]} ..................................... 2-115 2.2.17.1.8 Action: Cancel FPL => {[FP Act.] => [TERM]}..................................... 2-116 2.2.17.1.9 Action: Confirm/ Modify ETD => {[FP Act.] => [NOTIF]} ...................... 2-117 2.2.17.1.10 Action: Cancel ETD => {[FP ACTION] => [C.NOTIF]} ......................... 2-118 2.2.17.1.11 Action: Confirm/ Modify ATD => {[FP Act.] => [ATD]}.......................... 2-119 2.2.17.1.12 Action: Cancel ATD => {[FP Act.] => [C.ATD]} ................................... 2-120 2.2.17.1.13 Action: Estimate Actions => {[FP Act.] => [EST]} ................................ 2-121 2.2.17.1.14 Action: Passing over Fixpoint => {[FP Act.] => [POS]} ........................ 2-123 2.2.17.1.15 Action: Confirm/ Modify ATA => {[FP Act.] => [ATA]} .......................... 2-123 2.2.17.1.16 Action: Cancel ATA => {[FP ACTION] => [C.ATA]} ............................. 2-125 2.2.17.1.1 Action: AFTN SEND => {[FP ACTION] => [Aftn Send]} ....................... 2-126 2.2.17.1.2 Action: Strip Printing => {[FP ACTION] => [Strips]} ............................. 2-126 2.2.17.1.3 List of Synonyms .............................................................................. 2-127 2.2.17.2 FPLs Retrieval ........................................................................................ 2-128 2.2.17.2.1.1 Action: Retrieve Multiple FP => {[FPL] -> (FP RETRIEVE)} ........ 2-131 2.2.17.3 Conflict ................................................................................................... 2-132 2.2.17.3.1 Horizontal Future Situation Window (HFS) ......................................... 2-135 2.2.17.3.2 Vertical Future Situation Window (VFS) ............................................. 2-136 2.2.17.3.3 Action: Future Situation Visualization => {[FPL] -> [CONFLICT]}........ 2-137 2.2.18 Maps [MAP] Icon ........................................................................................... 2-139 2.2.18.1 Action: Select Maps => {[MAP]} ............................................................... 2-140 2.2.19 Fixed Configuration [CONFIG] Icon ................................................................ 2-142 2.2.19.1 Action: Retrieve Special Configuration => {[CONFIG]} -> {[LOAD]} ............ 2-143 2.2.19.2 Action: Save Special Configuration => {[CONFIG]} -> {[SAVE]} ................. 2-144 2.2.20 Quick-Look Sectors Selection [QL SC] Icon .................................................... 2-144 2.2.20.1 Action: Select Sectors for Quick-Look => {[QL SC]} .................................. 2-144 2.2.21 Quick-Look [QLOOK] Icon .............................................................................. 2-145 2.2.21.1 Action: Quick-Look Procedure => {[QLOOK]} ........................................... 2-145 2.2.22 Filter OFF [FILTER OFF] Icon ........................................................................ 2-146 2.2.22.1 Action: Activate/Inhibit Total Filters => {[ FILTER OFF]} or {<Alt> + <O>} ... 2-146 2.2.23 [Menu] Icon ................................................................................................... 2-146 2.2.23.1 Action: Display/ Close the Main Menu Window => {[MENU]} or {<Alt> + <M>} ....................................................................................................... 2-147 2.3 Main Menu Window .............................................................................................. 2-147 2.3.1 Common Actions from FP Lists ...................................................................... 2-149 2.3.1.1 Action: Flight Plan Operation Window display => {FP List => Status Indicator => [FP ACTION]}....................................................................... 2-150 2.3.1.2 Action: Conflict Window Display => {FP List => Status Indicator => [CONFLICT]}........................................................................................... 2-150 2.3.1.3 Action: Synthetic Track Creation => {FP List => Status Indicator => [CREATE]} .............................................................................................. 2-151 2.3.1.4 Action: Synthetic Track Deletion => {FP List => Status Indicator => [DELETE]} .............................................................................................. 2-152 2.3.1.5 Configuration Window for Flight Lists ....................................................... 2-153 2.3.1.1 Action: Flight List Configuration => {Configuration Window} ...................... 2-153 2.3.2 2.3.3 FP List [SECTOR LIST] Icon .......................................................................... 2-154 Planner FP List [INBOUND] Icon .................................................................... 2-157
Use or Disclosure of this information is subject to the restrictions on the tile page of this document Page xii
DOCUMENT N: 0029200000000MA03
2.3.4 2.3.5 2.3.6
Coordination Window ..................................................................................... 2-159 Departure FP List [DEPARTURES] Icon ......................................................... 2-161 Arrival FP List [ARRIVALS] Icon ..................................................................... 2-162
2.3.7 VIEW [VIEW1], [VIEW2], [VIEW3] Icon ........................................................... 2-163 2.3.7.1 Command Area ....................................................................................... 2-164 2.3.7.2 Display Area ........................................................................................... 2-165 2.3.7.3 Action: Auxiliary Window Display => {[VIEWX]} ........................................ 2-165 2.3.8 [CLOCK] Icon ................................................................................................ 2-166 2.3.9 Brightness [BRIGHT] Icon .............................................................................. 2-166 2.3.9.1 Brightness Window ............................................................................... 2-166 2.3.9.2 Action: Change Brightness => {[BRIGHT]}................................................ 2-168 2.3.10 [LAST POS] Icon ........................................................................................... 2-170 2.3.10.1 Action: Display of last position of a Lost track => {[LAST POS]} ................. 2-170 2.3.11 Sectors Visualization [SECTORS] Icon ........................................................... 2-170 2.3.11.1 Action: Sectors Visualization => {[SECTORS]} ......................................... 2-171 2.3.12 Local Maps Generation Tool [LMG] Icon ......................................................... 2-171 2.3.12.1 LMG Control Panel Window................................................................... 2-171 2.3.12.2 Primitive Graphic Type Area .................................................................... 2-172 2.3.12.3 Edition Area ............................................................................................ 2-172 2.3.12.4 Command Area ....................................................................................... 2-173 2.3.12.5 Action: Local Maps Generation => {[LMG]} ............................................... 2-173 2.3.13 Tracks Display Configuration [DATBLK] Icon .................................................. 2-175 2.3.13.1 Action: Select Tracks Symbols and Characters Size => {[DATBLK] -> [LABEL SIZE]}......................................................................................... 2-177 2.3.13.2 Action: Select Time Velocity Vector => {[DATBLK] -> [VELOCITY VECT]} . 2-179 2.3.13.3 Action: Select Total Track Label Format =>{[DATBLK] -> ROLE}............... 2-180 2.3.13.4 Action: History Tracks =>{[DATBLK] -> HISTORY} ................................... 2-181 2.3.13.5 Action: Select Total Track Label Format =>{[DATBLK] -> LIST FONT} ...... 2-182 2.3.13.6 Action: Delay Handover => {[DATBLK] -> DELAY HANDOVER} ............... 2-183 2.3.13.7 Action: Stretching factor => {[DATBLK] -> STRETCHING FACTOR} ......... 2-184 2.3.13.8 Action: Route Font => {[DATBLK] -> ROUTE FONT} ................................ 2-185 2.3.13.9 Action: Route Marks => {[DATBLK] -> ROUTE MARKS} ........................... 2-187 2.3.13.10 Action: Global Track Label Orientation => {[DATBLK] -> LABEL ORIENTATION} ...................................................................................... 2-188 2.3.13.11 Action: Track label lines to display selection => {[DATBLK] -> NUMBER OF LINES} .............................................................................................. 2-189 2.3.14 Range Bearing Lines [RBL OFF] Icon ............................................................. 2-190 2.3.14.1 Action: Remove RBLs ............................................................................. 2-190 2.3.15 Label Orientation [ORI OFF] Icon ................................................................... 2-190 2.3.15.1 Action: Total Tracks Label Orientation => {[ORI OFF]} .............................. 2-190 2.3.16 [RANGERINGS] Icon ..................................................................................... 2-191 2.3.16.1 Action: Activation/ Inhibition of Range Rings => {[RANGERINGS]} ............ 2-191 2.3.17 [ROU OFF] Icon ............................................................................................. 2-192 2.3.17.1 Action: Routes Display Cancel => {[ROU OFF]} ........................................ 2-192 2.3.18 2.3.19 Aural Alarms Cancel [ALR CNL] Icon .............................................................. 2-193 [QNH] Icon .................................................................................................... 2-193
Page xiii
DOCUMENT N: 0029200000000MA03
2.3.20 2.3.21
Automatic Orientation of Track Labels [OVERLAP] Icon .................................. 2-194 MTCD Conflicts [CONFL] Icon ........................................................................ 2-194
2.3.22 [AREAS] Icon ................................................................................................ 2-194 2.3.22.1 Action: Activation/ Inhibition of Restricted Areas => {[AREAS]} .................. 2-194 2.3.23 Track Velocity Vector Activation/ Inhibition [VELVECT] Icon ............................ 2-195 2.3.24 Meteorological Data [METEO] Icon ................................................................. 2-195 2.3.24.1 Action: Activation/Inhibition of Weather Data => {[METEO]} ...................... 2-195 2.3.25 Range Bearing Alarms [RBL ALM] Icon .......................................................... 2-196 2.3.26 [QUICKEST] Icon ........................................................................................... 2-196 2.3.26.1 Action: Quick Estimate Operation ............................................................. 2-197 2.3.27 Meteo Messages [MET MSGS] Icon ............................................................... 2-198 2.3.27.1 Airport Selection Area .............................................................................. 2-200 2.3.27.2 Message Type Selection Area ................................................................. 2-201 2.3.27.3 Message List Display Area ...................................................................... 2-201 2.3.27.4 Message Display Area ............................................................................. 2-201 2.3.28 System Messages [SYS MSG] Icon ................................................................ 2-201 2.3.29 Finder [FINDER] Icon ..................................................................................... 2-202 2.3.29.1 Action: Display the position of an element => {[FINDER]} .......................... 2-203 2.3.30 SSR Filter [SSRF] Icon................................................................................... 2-205 2.3.30.1 Action: Track filter by SSR code => {[SSRF]}............................................ 2-206 2.3.31 [F 3D] Icon ..................................................................................................... 2-207 2.3.31.1 Action: 3D Filter => {[F 3D]} ..................................................................... 2-208 2.3.32 [ARROWS] Icons ........................................................................................... 2-209 2.3.32.1 Action: Scrolling on the SDD SIT Area => {[SCROLLING ARROWS]}........ 2-210 2.3.32.2 Action: Position Visualization Increase or Decrease .................................. 2-210 2.3.33 2.3.34 2.3.35 SDD Identification .......................................................................................... 2-210 [PRINT LISTS] Icon ....................................................................................... 2-211 Printer Icon .................................................................................................... 2-211
2.3.36 [LOGIN] Icon ................................................................................................. 2-211 2.3.36.1 Action: Change User => {[LOGIN]} ........................................................... 2-212 2.3.37 [LOGOUT] Icon .............................................................................................. 2-212 2.3.37.1 Action: Freeze the Position => {[LOGOUT]} .............................................. 2-213 2.3.38 Other Windows .............................................................................................. 2-213 2.3.38.1 Lost List .................................................................................................. 2-213 2.3.38.1.1 Information Area ............................................................................... 2-214 2.3.38.2 Hold List ................................................................................................. 2-215 2.3.38.2.1 Information Area ............................................................................... 2-215 2.3.38.2.2 Action: Enter/ Leave Hold List ........................................................... 2-216 2.3.38.3 COORD IN/OUT Lists.............................................................................. 2-217 2.3.38.4 Conflict List ............................................................................................. 2-217 2.3.38.4.1 Information Area ............................................................................... 2-218 2.3.38.5 APW List................................................................................................. 2-218 2.3.38.5.1 Information Area ............................................................................... 2-219 2.3.38.6 MSAW List .............................................................................................. 2-219 2.3.38.6.1 Information Area ............................................................................... 2-220
Situation Data Display User Manual Use or Disclosure of this information is subject to the restrictions on the tile page of this document Page xiv
DOCUMENT N: 0029200000000MA03
2.4
SDD General Information Area in Supervision Mode ................................................ 2-220
2.4.1 Display of Plots .............................................................................................. 2-222 2.4.1.1 Action: Display the plots at SDD SIT Area ................................................ 2-222 2.4.2 [RADAR] Icon ................................................................................................ 2-223 2.4.3 [USERS] icon ................................................................................................ 2-225 2.4.3.1 Action: Users information ......................................................................... 2-225 2.4.4 LMG in Supervisor Mode ................................................................................ 2-226 2.4.4.1 Action: Local maps remote copy => {[LMG]} ............................................. 2-227 Appendix A - ABBREVIATIONS AND GLOSSARY OF TERMS ................................................ A-1 A.1 A.2 B.1 B.2 Abbreviations ............................................................................................................ A-1 Glossary of Terms ..................................................................................................... A-7 Messages sent from SDP to SDD............................................................................... B-1 Messages sent from FDP to SDD ............................................................................... B-1
Appendix B - System Messages List ........................................................................................ B-1
Appendix C - Local Error Messages List .................................................................................. C-1 Appendix D - FP Route ........................................................................................................... D-1 D.1 Definitions ................................................................................................................. D-1 D.2 Presentation of Obtained Routes When FP Analyzing ................................................. D-1 D.3 Route Field Analysis .................................................................................................. D-2 D.4 Errors Display .......................................................................................................... D-20 D.5 Route Field Messages ............................................................................................. D-20 D.6 Error Message of Route Field ................................................................................... D-21 Appendix E - Flight Plan Strips ................................................................................................ E-1
Page xv
DOCUMENT N: 0029200000000MA03
Page xvi
DOCUMENT N: 0029200000000MA03
List of Figures
Figure 1-1: Figure 1-2: Figure 2-39: Figure 2-92: Operative Description Example .......................................................................... 1-5 Window Conventions ......................................................................................... 1-6 Flight Plan Route Display ................................................................................. 2-65 [DATBLK] Icon ............................................................................................... 2-175
MSAW List can be sorted by every field, clicking on fields name, flight plans will be sorted by this field. ................................................................................................... 2-220 Figure E-1: Figure E-2: Figure E-3: Flight Plan Strip Type A (Arrival) ........................................................................ E-2 Flight Plan Strip Type D (Departure) .................................................................. E-2 Flight Plan Strip Type P (Progression) ............................................................... E-3
Page xvii
DOCUMENT N: 0029200000000MA03
Page xviii
DOCUMENT N: 0029200000000MA03
List of Tables
Table 1-1: Table 1-2: Table 1-3: Table 12: Table 13: Table 14: Table 15: Table 16: Table 17: Table 19: Table 30: Table 31: Table 32: Table 33: Mouse Button Functions ..................................................................................... 1-7 Key Functions .................................................................................................... 1-8 Key Combination Functions ................................................................................ 1-8 FP List. Element Information .......................................................................... 2-155 FP List. Element Information .......................................................................... 2-157 Coordination Window ..................................................................................... 2-159 Departure FP List........................................................................................... 2-161 Arrival FP List ................................................................................................ 2-163 Auxiliary Window. Elements ........................................................................... 2-164 Track Display Configuration Window. Icons Description................................... 2-176 APW List. Colours Code................................................................................. 2-219 APW List. Information Area ............................................................................ 2-219 MSAW List. Colours Code .............................................................................. 2-220 MSAW List. Information Area ......................................................................... 2-220
Table 34: Track Flight Plan Route Label ................................................................................. 2-65
Page xix
DOCUMENT N: 0029200000000MA03
Page xx
DOCUMENT N: 0029200000000MA03
1 Introduction
The SDD (Situation Data Display) Position is one of the components of the Enroute Approach and Tower Integrated Control System. Its main aim is to offer help to technical staff in the Traffic Control Centre, providing a work environment able to monitor the whole system in an easy but precise way in real time. This work environment consist of an HMI (Human Machine Interface) computer including screen, mouse and keyboard connected to the subsystems which control the flight plans to allow their monitoring and manage.
1.1
Scope
The scope of this manual is the operational description of the SDD Position available at the AIRCON 2100 system. The intended audience of this manual is controllers who use the SDD Position.
1.2
General System Description
The AIRCON 2100 System is based on a standard product developed by Indra. At the same time, an autonomous simulator addressed to controllers for training purposes to allow analysis of new operational procedures provides the operational system. AIRCON 2100 represents the last product generation and its architecture is based on the experience gained in the development of open systems for the displaying and processing of radar data and flight plans, found on numerous systems installed in Spain (SACTA System), Canada, Germany, Norway, Holland and India. One of the main characteristics of the system is its availability, due to the employment of redundant elements on a distributed scenario, and to the use of tested and highly reliable commercial equipment. The system modularity and distribution determines the software architecture, which uses distributed discrete processes for the different subsystems for its organization. At the same time, the system makes use of communication by messages, both for intercommunications between tasks and for its synchronicity. In order to assure a maximum level of maintenance, communications and application tasks have been isolated. The software running in the system has been tested and proved extensively in different emplacements and during longs periods and, therefore, Indra can guarantee that no additional developments of any kind are required for its correct and stable operation. The Operating System used is RED HAT ENTERPRISE LINUX 5. Following figure shows a full-featured architecture for the AIRCON 2100 System: AIRCON 2100 includes all the necessary functionality required in a modern ATC system. Its main elements are following described: The integration of all its subsystems is performed via: Local Area Network (LAN). A redundant five (5) category with a 1-Gigabyte bandwidth capacity LAN is used and, therefore, future updates of the system can be easily implemented making use of standard communication protocols. Main components: Flight Data Processing (FDP). It is based on RISC redundant computers. It manages the flight plans generated within the System or coming from external sources, including the Repetitive Flight Plans (RPLs). It confirms all flight data inputs, calculates the
Situation Data Display User Manual Use or Disclosure of this information is subject to the restrictions on the tile page of this document Page 1-1
DOCUMENT N: 0029200000000MA03
flights progression and keeps all controllers inform by means of screen displays and flight plan strips printing. Redundant configuration designs the System, having an FDP as operative and another one as reserve, with the possibility to switch them. Surveillance Data Processor (SDP). It is based on RISC redundant computers. It receives and processes data (primary, secondary and meteorological) coming from the radar sites. Next, it performs the merge all the received information to create a coherent airspace picture for controllers (SDD) presentation. It also performs surveillance tasks (STCA, MTCD) between aircraft and integrates the radar information and the flight plan information in order to get a precise tracking. The System is duplicated (operative/reserve) being possible to switch them. Radar Communications Processor (RDCU). It centralizes the System radar communications to interpret and convert the received radar formats to join them. The System is composed of two RDCU units working parallel. It is possible to carry out the received radar data reproduction during an established period. Controlling positions: Situation Data Display (SDD). It is based on powerful workstations that receive data processed by both the SDP and the FDP. Later on, it manages all these information for a coherent displaying at the controllers screens (SDD). At the same time, it displays additional relevant information such as geographic maps, meteorological data, etc. Flight Data Display (FDD). It displays information concerning flight plans not supplying data display of data on air situation. It allows controllers to perform adjustments on flight plans and other significant data. Control and Monitoring Display (CMD). It performs a continuous real time supervision of the System. It also allows monitoring and System elements status change, sectorization modification, management of certain configurable parameters, etc. Auxiliary equipment: Commom Timing Facility (CTF). It receives the GPS time, spread to all the subsystem (via LAN) and all clocks (via Terminals) with NTP protocol. Data Recording Facilities (DRF). It performs the continuous recording of tracks, flight plans data and controller actions to allow a later reproduction and analysis. Data Base Management (DBM). It provides the necessary facilities the creation and modification of the adaptation databases to supply the system with the precise knowledge of its geographical environment to achieve the required efficiency. From this database, all necessary data to define the control centre characteristics are defined (fixpoints, aerodromes, airways, sectorization, adjacent control centres, QNH zones, etc.) Simulator environment: Simulator (SIM). (OPTIONAL) It provides to the controllers an operational replica of the real scenario for training purposes. It is a multiple exercise simulator system and allows the use of several exercises, simultaneously and independently. It allows the analysis of new operational procedures as well as the management and maintenance of the full set of sessions and exercises recorded in the Simulation Library. It also allows the creation of new exercises, the selection of training scenarios and provides a complete set of interactive capacities in order to guarantee full control and management.
Page 1-2
DOCUMENT N: 0029200000000MA03
Instructor Pilot Position (PILOT SM). (OPTIONAL) It allows training scenarios selection, session control and control of aircraft simulated interactively in such a way that it generates the communication answer to the control positions from this position. Exercise Manager (ATG/EPP). (OPTIONAL) This unit simulation manages the exercises.
1.3
Situation Data Display (SDD) Position Overview
The SDD Position consists on a powerful workstation to display radar data and flight plans. Its main functions are: Radar tracks, plots and meteorological outlines display Flight plans lists display Automatic modification of flight plans lists according to the different flight plan statuses Display of lists of flights in Hold, Lost or Conflict Route graphical display of flight plans with estimates of passing time and levels on each route fixpoint Flight Plan route graphical modification Aeronautical maps display Local maps display and generation Restricted areas display. Control of displayed information (range, cantering, filters, RBLs, etc.) Support controllers actions (clearances, ATD, ARR, EST, etc.) Hand-over procedures between sectors and externals Flight plan strip printing both automatically and manually Access to Flight Plans database (retrieve, creation, modification, deletion) Safety Nets display: MSAW (Minimum Safe Altitude Warning), STCA (Short-Term Conflict Alert), and APW (Area Proximity Warning) Display of MTCD (Medium-Term Conflict Alert) and traffic extrapolation for future situations Display and process of data in by-pass mode as a capacity of the Fallback System in case the SDP servers fall down Traffic recording of last 24 hours (tracks, flight plans, screen statuses) Recordings reproduction (24-hours reproduction mode and DRF reproduction mode) These functions are available in all operative control positions and for all controllers roles (TWR, APP and ACC).
1.4
Manual Structure
This manual provides precise information concerning all menus and windows belonging to the SDD position. Chapter 1 Introduction It provides an overview of the overall system, the SDD Position environment, and the contents of this manual. Finally, this manual describes the used conventions. Chapter 2 Functional and Operational Description
Page 1-3
DOCUMENT N: 0029200000000MA03
It presents an explanation of each SDD Position software element, including all the descriptions for a complete starting contact. It describes the selection modes and all SDD Position windows. It also describes all the actions performed by means of the SDD windows as well as the actions performed with the airways. It shows all the possibilities involving the elements described in former Chapter, that is, it is dynamic description. Appendix A Acronyms and Definitions It presents the glossary of terms used in the manual as well as the abbreviation dictionary. Appendix B System Messages List Appendix C Local Error Messages List Appendix D Flight Plan Route It presents a wide description of the Route field. Appendix E Flight Plan Strip It is a description of the flight plan strips generated by the system.
1.5
1. 2. 3. 4. 5.
Notation Used in this Manual

Select X means pointing the cursor on the position denoted by X and then, pressing the LB of the mouse. Press X means the same as Select X. Capital letters describe colour assignment. Sometimes a command, window, etc. must use some specific rules. For these cases, all commands or windows describe the list of applicable rules. Operational descriptions include following sections: Section number and title Two columns describe the actions. The first one (left) describes the actions and the second one (right) describes the result to that action The Access Path to Function and Application Paragraph are included when necessary.
Following figure shows some different notations used when particular fields are selected or edited.
Page 1-4
DOCUMENT N: 0029200000000MA03
Figure 1-1:
6. 7.
Operative Description Example
Brackets list icons and switches; parenthesis lists menu options and quotation marks list fields. Description of windows includes the following parts: Windows layout figure Windows description Edition fields description Window commands and operational description
Next figure illustrates some of the conventions used when making selections and editing data in the fields of the SDD windows.
Page 1-5
DOCUMENT N: 0029200000000MA03
Figure 1-2:
Window Conventions
1.6
Selecting Menus, Icons and Field Text Entering
Menus, menus options, icons and switches access windows, commands, and options. These actions cause windows to display where the SDD functions initiate. The mouse is the main device for controller inputs although, in specific cases, the controller may use the keyboard for that end. Following table describes the logical functions of the mouse buttons:
Page 1-6
DOCUMENT N: 0029200000000MA03
Table 1-1:
Button
Left Button (LB)
Mouse Button Functions

Function
Request information operations and low -level local actions. Copy data from a field. Move windows.
Central Button (CB)
Create/Erase RBLs Close edition windows. Paste data to a field.
Right Button (RB)
Associated with control actions as map selection and RBL creation acceptance.
Pull-down menus: Upon clicking once on the icon, the menu displays. The menu display is kept after button release, and pointing and clicking perform the selection. To close the pull-down menu (with no changes) click on it with the mouse RB. A pull-down menu comprises: Available options list for the icon. Select the option by clicking with the LB on any of them. At the same time, the menu disappears. The corresponding window displays on the screen. Windows: They are displayed by clicking with the mouse LB on the pull-down menu options or directly on icons. The window keeps its display until the operator closes it by means of the [CLOSE] icon or the X icon (situated on the upper right corner). The window is composed of following items: Title, situated at the top of the window, indicates the windows name. Edition fields to input data. Before editing data, the mouse cursor situates within the corresponding field. To validate the data, press <Enter> on the keyboard. Icons to validate or cancel the action. Pop-up menus: They allow a fast and user-friendly operation to modify selected data. This window is displayed by clicking once on the corresponding field or icon. The window keeps its display after mouse button release and marking the option and clicking with the mouse perform selection. Click on the title with the mouse CB in order to close the pop-up windows (without changes). These windows may include following items: Title, with the type of field to be modified (CFL, upper altitude level filter, etc.) Available options list for the field. This list may include a horizontal or vertical slide to allow selection of those options not in view. Initially, the window display focuses on the current value or the first one. To select a new value, click on it with the mouse LB and at the same time, the pop-up window is closed. Edition field where it is possible to input valid values even thought the value is not included in the list. Before the edition, the cursor must focus on the corresponding field. Click on the <Enter> key to validate the input data and to close the pop-up window. Icons: These are elements, which allow a fast access of certain functions by clicking the corresponding symbol. Usually, when clicking on an icon, a window displays.
Page 1-7
DOCUMENT N: 0029200000000MA03
Keyboard: a set of functions can be activated directly by means of the keyboard. These keys (or combination of keys) have an associated function as shown in following table: Table 1-2:
Key
- + <F1> <F2> <F3> <F5> <F6> <F7> <F8> <F9> <F10> <Tab> <Backspace> <Del> or <Supr> <Arrows> <Arrows> field) (within an editable
Key Functions
Function
Reduce the presentation scale. Increase presentation range in discrete steps. Expand the presentation scale. Decrease presentation range in discrete steps. Predefined configuration by default. Displays route of selected track Manual electronic transference of a selected track. Selected label rotation. Create a new minimum flight plan for an assumed flight. Activate the flight plan window of the selected track. Open CFL pop-up menu for a selected track. Expand the presentation scale. Reduce the presentation scale. Move the cursor position from one field to the following one. Delete the character before the cursor position (within a field). Delete the character after the cursor position (within a field). Perform a display scrolling (continuous decentring). Left arrow: moves backward the cursor, character by character, within a field. Right arrow: moves forward the cursor, character by character, within a field.
Table 1-3:
Key Combination
<Alt> + <M> <Alt> + <Alt> + <O> <Alt> + <G> <Alt> + <H> <Alt> + 
Key Combination Functions

Function
Remove/Display the Main Menu Area Invoke the inter-console marker function Inhibit/activate all current filters Inhibit/activate the local map generator tool Activate/inhibit the display of tracks past positions Activate the SSR code modification of primary tracks
1.6.1 Rules to Enter and Delete Data

Windows contain fields where data can be input, (sometimes it is even compulsory). The following rules for entering data apply to all windows within this position.
1. 2. 3.
Input can only be made into a window if the focus is on that window (screen cursor is inside the window area). The field displaying the blinking input cursor is ready to accept inputs. Fields that are shaded in dark GREY do not accept data. When selecting an icon that opens a window, both window and input cursors automatically stand inside the first editable field of the window.
Page 1-8
DOCUMENT N: 0029200000000MA03
4. 5. 6. 7. 8.
After entering data in one field, pressing <Tab> on the keyboard, moves the cursor to the next field. Alternatively, use the input cursor. Pressing <Shift><Tab> on the keyboard moves the input marker backward to the previous field. Click with the RB on the menu to cancel data input in a pop-up window. To enter data, double click to select the whole field and then type the new characters. To delete data, set the cursor after the character to be deleted and press <Backspace> until the character is deleted. It is also possible by clicking twice with the cursor on the data to be deleted then, write the new characters. Once the data input has finished, the system answers about the data input. It also presents information to accept or reject the action.
9.
1.7
Common Actions to all SDD Windows
This section describes the functions to apply to all SDD windows. These actions are directly performed with the mouse on the corresponding window frame and/or title. These areas are light GREY: Move Window: Click with the LB on the window title. Without releasing the LB, move the window to the new position. Release the LB. Bring Window Forward: Move the mouse cursor to the window frame. Click once with the mouse LB on the title The action finishes when the button is released. Window Size Change:
Windows, whose size change, include a re-size icon on the upper right corner:
Click with the mouse LB and do not release the re-size icon. Drag the window frame to the new size. Release the mouse LB. Transfer Window (only for SDD connected with FDD):
Windows, which transfer between the SDD and the FDD, include an icon on the upper right corner:
Click on the transfer icon with the mouse LB. The FDD presents the window just in the last position it had and will be disappeared from the SDD. To come back the window, click on the transfer icon with the mouse LB on the FDD. The SDD presents the window just in the last position it had and will be disappeared from the FDD.
Page 1-9
DOCUMENT N: 0029200000000MA03
It is also possible to perform this action by dragging the window from the SDD to the FDD and vice versa. Just keep the mouse LB, without release it, clicked on the window title and move to the desired position of the other screen. Inhibit: Click on the corresponding icon or switch. The text colour changes from YELLOW to WHITE or BACKGROUND. Activate: Click on the corresponding icon or switch. The text colour changes from WHITE or BACKGROUND to YELLOW. Date Format: Clicking on the labels whose associated data are dates display the appropriate format of the data to be input.
1.8
Procedures to Close Actions in Windows
All actions are finished by means of icons included in the corresponding windows/lists. These procedures are:

Validation and Closure Closure without Validation Data Deletion Printing
Page 1-10
DOCUMENT N: 0029200000000MA03
By means of an example with the FP Operation Window, these procedures are described:
ACTION
1. Validation and Closure:
1.1 Click on the [UPDATE] icon. If input data is correct, the System validates the selected action and the changes are stored when clicking on the [OK] icon.
RESULT
If input data are erroneous, the System presents an error message to the controller. The first erroneous field shows the cursor.
If compulsory fields are not completed, the System presents an error message to the controller. The first erroneous field shows the cursor.
2. Data Deletion
2.1 [CLEAR] Icon Deletion of data input from the FP Operation Window.
3. FP Printing
3.1 Click on the [PRINT] icon The already displayed FP is printed.
4. Close the FP Operation Window

4.1 Click on the [CANCEL] icon The FP Operation Window closes without taking into account the last action, which has not been previously validated.
1.9 Common Actions on Windows

This section describes the functions, which may be applied to all windows in the position. These operations are carried out directly with the mouse on the edge and/or title of the required window. These areas are coloured light GREY. The operations are the following ones: Change size: Windows whose size can be changed have a resize button in a corner. Following these steps changes the windows size: Press and hold the resize button with the LB. Drag the frame to the new position.
Page 1-11
DOCUMENT N: 0029200000000MA03
Release the mouse LB. The windows size is changed. Also it is possible to change window size to a size that allows the simultaneous display (if it is possible) of every list element; this action is performed clicking in the bar (only for windows that include this icon). Change position: Click with the CB while the pointer is on the border of the corresponding window. Move the mouse to drag the windows frame to the new position. Release the mouse button. The window is placed in the new position. Bring to foreground: Move the mouse pointer to the windows border. Click once with the LB on the border. When the button is released the operation is carried out. Inhibit: Click on the corresponding activation icon. The icon text colour changes from YELLOW to WHITE or Background colour. Activate: Click on the corresponding activation icon. The icon text colour changes from WHITE or Background colour to YELLOW. icon in windows title
Page 1-12
DOCUMENT N: 0029200000000MA03
2 Functional Description
This chapter provides information for new users of the SDD Position. It presents every work available window with a description of their formats, layout, icons and menus. The screen is divided into two main areas and a window: General Information Area

SIT Area Main Menu window

General Information Area
SIT Area
Main Menu Area
Figure 2-3: SDD Screen
2.1 SDD SIT Area

The following sections describe the format (colours, sizes, etc.,) of all elements included in the SIT Area of the SDD Position. Table 4: SDD SIT Area. Description Element Plots Tracks Symbols Colours Track Label Track Colour
Use or Disclosure of this information is subject to the restrictions on the tile page of this document Page 2-1
Description
DOCUMENT N: 0029200000000MA03
Element Track Symbol Leader Line Velocity Vector Past Positions Track in STCA Synthetic Track Meteorological Data Range (RBLs) Bearing Lines
Description
Flight Plan Route
2.1.1 Plots
The plots, which have not still created a track, can be displayed for selected radar. Once the track is created, the plot symbol is not longer displayed. The plot symbol is a shape associated to a unique plot, which location in the SIT Area is automatically moved by the system in order to present the actual position of the flight. The symbols to each type of plot are described in following table: Symbol PRIMARY SECONDARY SECONDARY COMBINED with PRIMARY Primary plots after requesting primary track initiation (that is, under tracking) Plot Type
2.1.2 Tracks 2.1.2.1 Track Symbol

The track symbol is a shape associated to a unique track, which location on the SDD SIT Area is automatically moved by the system in order to represent the actual position of the flight. The symbols associated to each type of track are described in following table: Symbol Track Type PRIMARY
Page 2-2
DOCUMENT N: 0029200000000MA03
Symbol SECONDARY
Track Type
SECONDARY COMBINED with PRIMARY CORRELATED ADS ADS COMBINED with PRIMARY ADS COMBINED with SECONDARY ADS COMBINED with PRIMARY and/or SECONDARY SYNTHETIC CODE AMBIGUITY
2.1.2.2 Track Label

The track label is a set of essential information related to the track. This information is organized in lines and fields. The contents for track label can be configured offline, and for each track type, three configurations are currently available, one for each role (approach, enroute and tower). The current role is displayed in the Main Menu area and can be modified by DATABLK window. Tracks in holding status display a symbol in Line 2, Field A. For tracks whose Ground speed is greater than 999 knots, this speed is indicated in track label by the previous ^ symbol in YELLOW colour. Ex. Ground speed of 200 knots is indicated in track label by the value 200, but 1200 knots is indicated as ^200. Here is a brief squema about label fields for each track type in each role, for first given configuration.
2.1.2.2.1
Controlled Enroute role
The following table displays the elements in track label in extended mode (except the fields marked as Only in extended mode) Table 5: Track Label Controlled Enroute : Fields Description Line Line 1 Field Field A Field B Displayed Information Sector name ROF/ RAM/ ASSR/ Heading alert 2 characters FQ/ RO/ SQ/ HG (YELLOW)
Page 2-3
Valid Data 4 alphabetic characters
DOCUMENT N: 0029200000000MA03
Line
Field
Displayed Information 1 character
Valid Data 8 (YELLOW): 8.33 warning. 8 (RED): 8.33 alert. U (YELLOW): UHF equipped. 1 character
Field C
8.33/ UHF warnings
Field D
RVSM
R (RED): RVSM alert. R (YELLOW): RVSM warning. 2 characters AW: MSAW (YELLOW: prediction; RED: violation)
Field E
MSAW/ APW/ MTCD alerts
ZN: APW (YELLOW: prediction; RED: violation) MC: MTCD (YELLOW: prediction; RED: violation) 2 characters EM (RED): Emergency HJ (RED): Hijack RF (RED): Failure Radio Communication
Field F
Distress
LB (YELLOW): CLAM alert Field A Line 2 Field B Field C Field D Field A Field B Coordination required mark Callsign ^ mark Ground speed/ Vertical speed Altitude indicator Mode C 1 character 7 characters 1 character 3 characters 1 character 3 characters 1 character Field C Line 3 Vertical Speed Indicator => Aircraft is climbing => Aircraft is descending Space => Aircraft altitude is enduring 3 characters Field D Field E Line 4 Field A Field B Cleared flight level (CFL)/ PEL Exit flight level (XFL) Aircraft type/ Mode A Wake turbulence category CFL value for controlled tracks PEL value for inbound tracks 3 characters 3 characters 1 character
Page 2-4
DOCUMENT N: 0029200000000MA03
Line
Field Field C Field A Field B
Displayed Information Last point Assigned heading (Only for extended mode) Heading mark (Only for extended mode) Assigned speed (Only for extended mode) Assigned vertical rate indicator (Only for extended mode) Requested flight level (RFL) (Only for extended mode) 5 characters 3 characters 1 character 3 characters 1 character 2 characters
Valid Data
Line 5
Field C Field D Field E
2.1.2.2.2
Controlled Approach role
The following table displays the elements in track label in extended mode (except the fields marked as Only in extended mode) Table 6: Label Controlled Approach : Fields Description Line Field Field A Field B Displayed Information Sector name ROF/ RAM/ ASSR/ Heading alert Valid Data 4 alphabetic characters 2 characters FQ/ RO/ SQ/ HG (yellow) 1 character Field C 8.33/ UHF warnings 8 (YELLOW): 8.33 warning. 8 (RED): 8.33 alert. U (YELLOW): UHF equipped. 1 character Line 1 Field D RVSM R (RED): RVSM alert. R (YELLOW): RVSM warning. 2 characters AW: MSAW (YELLOW: prediction; RED: violation) Field E MSAW/ APW/ MTCD alerts ZN: APW (YELLOW: prediction; RED: violation) MC: MTCD (YELLOW: prediction; RED: violation) Field F
Distress
2 characters
Page 2-5
DOCUMENT N: 0029200000000MA03
Line
Field
Displayed Information
Valid Data EM (RED): Emergency HJ (RED): Hijack RF (RED): Failure Radio Communication
LB (YELLOW): CLAM alert Field A Line 2 Field B Field C Field D Field A Field B Coordination required mark Callsign ^ mark Ground speed/ Vertical speed Altitude indicator Mode C 1 character 7 characters 1 character 3 characters 1 character 3 characters 1 character Field C Line 3 Vertical Speed Indicator => Aircraft is climbing => Aircraft is descending Space => Aircraft altitude is enduring 3 characters Field D Field E Field A Field B Line 4 Field C Last point Cleared flight level (CFL/ PEL) Exit flight level (XFL) Aircraft type/ Mode A (Only for extended mode) Wake turbulence category (Only for extended mode) CFL value for controlled tracks; PEL value for incoming tracks. 5 characters 4 characters 1 characters 7 characters STAR/ DEST: for ARR in TMA; SID/ Exit point: for DEP in TMA; Last point in FIR: for overflight via TMA. Field A Field B Line 5 Field C Field D Assigned heading (Only for extended mode) Heading mark (Only for extended mode) Assigned speed (Only for extended mode) Assigned vertical rate (Only for extended mode) 3 characters 1 character 3 characters 4 characters
Page 2-6
DOCUMENT N: 0029200000000MA03
2.1.2.2.3
Controlled Tower role
The following table displays the elements in track label in extended mode (except the fields marked as Only in basic mode) Table 7: Label Controlled Tower : Fields Description Line Field Field A Field B Displayed Information Sector name ROF/ RAM/ ASSR/ Heading alert 2 characters FQ/ RO/ SQ/ HG (yellow) 1 character Field C 8.33/ UHF warnings 8 (YELLOW): 8.33 warning. 8 (RED): 8.33 alert. U (YELLOW): UHF equipped. Valid Data 4 alphabetic characters
1 character Field D Line 1 2 characters AW: MSAW (YELLOW: prediction; RED: violation) Field E MSAW/ APW/ MTCD alerts ZN: APW (YELLOW: prediction; RED: violation) MC: MTCD (YELLOW: prediction; RED: violation) 2 characters EM (RED): Emergency Field F Distress HJ (RED): Hijack RF (RED): Failure Field A Field B Line 2 Field C Field D Field E Line 3 Field A Field B Coordination required mark Callsign ^ mark Aircraft type/ Mode A Wake turbulence category Altitude indicator Mode C 1 character 7 characters 1 character 4 characters 1 character 1 character 3 characters
Page 2-7
RVSM
R (RED): RVSM alert. R (YELLOW): RVSM warning.
Radio
Communication
LB (YELLOW): CLAM alert
DOCUMENT N: 0029200000000MA03
Line
Field
Valid Data => Aircraft is climbing => Aircraft is descending Space => Aircraft altitude is enduring 3 characters 7 characters STAR/ DEST: for ARR in TMA; SID/ Exit point: for DEP in TMA; Last point in FIR: for overflight via TMA.
Field C
Vertical Speed Indicator
Field D
Ground speed/ Vertical speed
Field E
Last point
Field A Line 4 Field B Field C
3 characters Cleared flight level (CFL)/ PEL (Only for CFL value for controlled tracks; extended mode) PEL value for incoming tracks. Assigned speed (Only for extended mode) Destination aerodrome extended mode) (Only for 3 characters 4 characters
2.1.2.2.4
Inbound Enroute role
The following table displays the elements in track label in extended mode (except the fields marked as Only in basic mode) Table 8: Label Inbound Enroute : Fields Description Line Field Field A Field B Displayed Information Sector name ROF/ RAM/ ASSR/ Heading alert 2 characters FQ/ RO/ SQ/ HG (yellow) 1 character Field C Line 1 8.33/ UHF warnings 8 (YELLOW): 8.33 warning. 8 (RED): 8.33 alert. U (YELLOW): UHF equipped. 1 character Field D RVSM R (RED): RVSM alert. R (YELLOW): RVSM warning. Field E
2 characters AW: MSAW (YELLOW: prediction; RED:

Page 2-8
DOCUMENT N: 0029200000000MA03
Line
Field
Displayed Information violation)
Valid Data ZN: APW (YELLOW: prediction; RED: violation) MC: MTCD (YELLOW: prediction; RED: violation) 2 characters EM (RED): Emergency HJ (RED): Hijack RF (RED): Failure Radio Communication
Field F
Distress
LB (YELLOW): CLAM alert Field A Line 2 Field B Field B Field A Field B Callsign ^ mark Ground speed/ Vertical speed Altitude indicator Mode C 7 characters 1 character 3 characters 1 character 3 characters 1 character Field C Line 3 Vertical Speed Indicator => Aircraft is climbing => Aircraft is descending Space => Aircraft altitude is enduring 3 characters Field D Cleared flight level (CFL)/ PEL CFL for controlled tracks; PEL for incoming tracks. Field E Field A Line 4 Field B Field C Field A Field B Line 5 Field C Field D
Exit flight level (XFL) Aircraft type/ Mode A (Only for extended mode) Wake turbulence category (Only for extended mode) Last point Assigned heading (Only for extended mode) Heading mark (Only for extended mode) Assigned speed (Only for extended mode) Assigned vertical rate indicator (Only for extended mode)
3 characters 3 characters 1 character 5 characters 3 characters 1 character 3 characters 1 character

Page 2-9
DOCUMENT N: 0029200000000MA03
Line
Field Field E
Displayed Information Requested flight level (RFL) (Only for extended mode) 2 characters
Valid Data
2.1.2.2.5
Inbound Approach role
The following table displays the elements in track label in extended mode (except the fields marked as Only in basic mode) Table 9: Label Inbound Approach : Fields Description Line Field Field A Field B Displayed Information Sector name ROF/ RAM/ ASSR/ Heading alert 2 characters FQ/ RO/ SQ/ HG (yellow) 1 character Field C 8.33/ UHF warnings 8 (YELLOW): 8.33 warning. 8 (RED): 8.33 alert. U (YELLOW): UHF equipped. 1 character Field D RVSM R (RED): RVSM alert. R (YELLOW): RVSM warning. Line 1 2 characters AW: MSAW (YELLOW: prediction; RED: violation) Field E MSAW/ APW/ MTCD alerts ZN: APW (YELLOW: prediction; RED: violation) MC: MTCD (YELLOW: prediction; RED: violation) 2 characters EM (RED): Emergency Field F Distress HJ (RED): Hijack RF (RED): Failure Radio Communication Valid Data 4 alphabetic characters
LB (YELLOW): CLAM alert Field A Line 2 Field B Field C Line 3 Field A Field B Callsign ^ mark Ground speed/ Vertical speed Altitude indicator Mode C 7 characters 1 character 3 characters 1 character 3 characters
Page 2-10
DOCUMENT N: 0029200000000MA03
Line
Field
Valid Data => Aircraft is climbing => Aircraft is descending Space => Aircraft altitude is enduring 3 characters
Field C
Field D Field E Field A Field B Line 4 Field C
Cleared flight level (CFL)/ PEL Exit flight level (XFL) Aircraft type/ Mode A Wake turbulence category
CFL value for controlled tracks; PEL value for incoming tracks. 5 characters 4 characters 1 characters 7 characters STAR/ DEST: for ARR in TMA; SID/ Exit point: for DEP in TMA; Last point in FIR: for overflight via TMA. 3 characters 1 character 3 characters 4 characters
Last point (Only for extended mode)
Field A Line 5 Field B Field C Field D
Assigned heading Heading mark Assigned speed Assigned vertical rate
2.1.2.2.6
Inbound Tower role
The following table displays the elements in track label in extended mode (except the fields marked as Only in basic mode) Table 10: Label Inbound Tower : Fields Description Line Line 1 Field Field A Field B Displayed Information Sector name ROF/ RAM/ ASSR/ Heading alert 2 characters FQ/ RO/ SQ/ HG (yellow) Valid Data 4 alphabetic characters
Page 2-11
DOCUMENT N: 0029200000000MA03
Line
Field
Valid Data
1 character Field C 8.33/ UHF warnings 8 (YELLOW): 8.33 warning. 8 (RED): 8.33 alert. U (YELLOW): UHF equipped.
1 character Field D RVSM R (RED): RVSM alert. R (YELLOW): RVSM warning. 2 characters AW: MSAW (YELLOW: prediction; RED: violation) Field E MSAW/ APW/ MTCD alerts ZN: APW (YELLOW: prediction; RED: violation) MC: MTCD (YELLOW: prediction; RED: violation) 2 characters EM (RED): Emergency Field F Distress HJ (RED): Hijack RF (RED): Failure Coordination mark (Only for OAT seen by GAT sectors) Callsign Aircraft type/ Mode A Wake turbulence category Altitude indicator Mode C Radio Communication
LB (YELLOW): CLAM alert Field A Line 2 Field B Field C Field D Field A Field B Line 3 1 character 7 characters 4 characters 1 character 1 character 3 characters 1 character Field C Vertical Speed Indicator => Aircraft is climbing => Aircraft is descending Space => Aircraft altitude is enduring Field D
3 characters
Page 2-12
DOCUMENT N: 0029200000000MA03
Line
Field
Displayed Information 7 characters
Valid Data STAR/ DEST: for ARR in TMA; SID/ Exit point: for DEP in TMA; Last point in FIR: for overflight via TMA.
Field E
Last point
3 characters Cleared flight level (CFL)/ PEL (Only for CFL value for controlled tracks; extended mode) PEL value for incoming tracks. Assigned speed (Only for extended mode) Destination aerodrome extended mode) (Only for 3 characters 4 characters
2.1.2.2.7
OAT traffic seen by GAT sectors. Enroute role
It applies both to OAT traffic seen by GAT sectors and GAT traffic seen by OAT sectors. The following table displays the elements in track label in extended mode (except the fields marked as Only in basic mode) Table 11: Label OAT Traffic seen by GAT sectors. Enroute : Fields Description Line Field Field A Field B Line 1 Field C Distress Displayed Information Sector name ROF 2 characters FQ 2 characters EM (RED): Emergency HJ (RED): Hijack RF (RED): Failure Field A Line 2 Field B Field C Field A Field B Line 3 Field C Vertical Speed Indicator Callsign ^ mark Ground speed/ Vertical speed Altitude indicator Mode C 7 characters 1 character 3 characters 1 character 3 characters 1 character => Aircraft is climbing => Aircraft is descending
Radio
Communication
DOCUMENT N: 0029200000000MA03
Line
Field Field D Field E Field A
Displayed Information Cleared flight level (CFL) Exit flight level (XFL) Aircraft type/ Mode A (Only for extended mode) Wake turbulence category (Only for extended mode) Last point (Only for extended mode) Assigned heading (Only for extended mode) Heading mark (Only for extended mode) Assigned speed (Only for extended mode) Assigned vertical rate indicator (Only for extended mode) Requested flight level (RFL) (Only for OAT traffic seen in GAT sector) (Only for extended mode) 3 characters 3 characters 3 characters 1 character 5 characters 3 characters 1 character 3 characters 1 character 2 characters
Valid Data Space => Aircraft altitude is enduring
Line 4
Field B Field C Field A Field B Field C
Line 5 Field D Field E
2.1.2.2.8
OAT traffic seen by GAT sectors. Approach role
It applies both to OAT traffic seen by GAT sectors and GAT traffic seen by OAT sectors. The following table displays the elements in track label in extended mode (except the fields marked as Only in basic mode) Table 12: OAT Traffic seen by GAT sectors. Approach : Fields Description Line Field Field A Field B Line 1 Field C Distress Displayed Information Sector name ROF 2 characters FQ 2 characters EM (RED): Emergency HJ (RED): Hijack RF (RED): Failure Field A Line 2 Field B Field C Line 3 Field A Callsign ^ mark Ground speed/ Vertical speed Altitude indicator 7 characters 1 character 3 characters 1 character
Page 2-14
Radio
Communication
DOCUMENT N: 0029200000000MA03
Line
Field Field B Mode C
Displayed Information 3 characters 1 character
Valid Data
Field C
=> Aircraft is climbing => Aircraft is descending Space => Aircraft altitude is enduring 3 characters 5 characters (Only for (Only for 4 characters 1 characters 7 characters
Field D Field E Field A Field B Line 4 Field C
Cleared flight level (CFL) Exit flight level (XFL) Aircraft type/ Mode A extended mode) Wake turbulence category extended mode)
Last point (Only for extended mode)
STAR/ DEST: for ARR in TMA; SID/ Exit point: for DEP in TMA; Last point in FIR: for overflight via TMA. 3 characters 1 character 3 characters 4 characters
Line 5
Field A
Assigned heading Heading mark Assigned speed Assigned vertical rate
Field B (in Basic mode: Field C Line 4) Field D
2.1.2.2.9
OAT traffic seen by GAT sectors. Tower role
It applies both to OAT traffic seen by GAT sectors and GAT traffic seen by OAT sectors. The following table displays the elements in track label in extended mode (except the fields marked as Only in basic mode) Table 13: OAT Traffic seen by GAT sectors. Tower : Fields Description Line Field Field A Field B Line 1 Field C Distress Displayed Information Sector name ROF Valid Data 4 alphabetic characters 2 characters FQ 2 characters EM (RED): Emergency HJ (RED): Hijack RF (RED): Failure Radio Communication
Page 2-15
DOCUMENT N: 0029200000000MA03
Line
Field Field A Callsign
Displayed Information 7 characters 4 characters 1 character 1 character 3 characters 1 character
Valid Data
Line 2
Field B Field C Field A Field B
Aircraft type/ Mode A Wake turbulence category Altitude indicator Mode C
Field C Line 3 Field D
=> Aircraft is climbing => Aircraft is descending Space => Aircraft altitude is enduring 3 characters 7 characters STAR/ DEST: for ARR in TMA; SID/ Exit point: for DEP in TMA; Last point in FIR: for overflight via TMA.
Field E
Last point
Cleared flight level (CFL) (Only for extended mode) Assigned speed (Only for extended mode) Destination aerodrome extended mode) (Only for
3 characters 3 characters 4 characters
2.1.2.2.10
Uncontrolled outside the sector. Enroute role
The following table displays the elements in track label in extended mode (except the fields marked as Only in basic mode) Table 14: Uncontrolled outside the sector. Enroute : Fields Description Line Field Field A Field B Line 1 Field C Distress Displayed Information Sector name ROF 2 characters FQ 2 characters EM (RED): Emergency HJ (RED): Hijack RF (RED): Failure
Situation Data Display User Manual Use or Disclosure of this information is subject to the restrictions on the tile page of this document
Radio
Communication
Page 2-16
DOCUMENT N: 0029200000000MA03
Line
Field Field A Callsign ^ mark
Displayed Information 7 characters 1 character 3 characters 1 character 3 characters 1 character
Valid Data
Line 2
Ground speed/ Vertical speed Altitude indicator Mode C
Line 3
Field C
=> Aircraft is climbing => Aircraft is descending Space => Aircraft altitude is enduring 3 characters 5 characters
Field D Line 4 Field A
Cleared flight level (CFL) Last point (Only for extended mode)
2.1.2.2.11
Uncontrolled outside the sector. Approach role
The following table displays the elements in track label in extended mode (except the fields marked as Only in basic mode) Table 15: Uncontrolled outside the sector. Approach : Fields Description Line Field Field A Field B Line 1 Field C Distress Displayed Information Sector name ROF 2 characters FQ 2 characters EM (RED): Emergency HJ (RED): Hijack RF (RED): Failure Field A Line 2 Field B Field C Field A Field B Line 3 Field C Vertical Speed Indicator Callsign ^ mark Ground speed/ Vertical speed Altitude indicator Mode C 7 characters 1 character 3 characters 1 character 3 characters 1 character => Aircraft is climbing => Aircraft is descending
Radio
Communication
DOCUMENT N: 0029200000000MA03
Line
Field Field D Field A
Displayed Information Cleared flight level (CFL) Aircraft type/ Mode A (Only for extended mode) Wake turbulence category (Only for extended mode) Last point (Only for extended mode) 3 characters 4 characters 1 characters 5 characters
Line 4
Field B Field C
2.1.2.2.12
Uncontrolled outside the sector. Tower role
The following table displays the elements in track label in extended mode (except the fields marked as Only in basic mode) Table 16: Uncontrolled outside the sector. Tower : Fields Description Line Field Field A Field B Line 1 Field C Distress Displayed Information Sector name ROF 2 characters FQ 2 characters EM (RED): Emergency HJ (RED): Hijack RF (RED): Failure Field A Line 2 Field B Field C Field D Field A Field B Callsign ^ mark Aircraft type/ Mode A Wake turbulence category Altitude indicator Mode C 7 characters 1 character 4 characters 1 character 1 character 3 characters 1 character Field C Line 3 Field D Field E Ground speed/ Vertical speed Last point Vertical Speed Indicator => Aircraft is climbing => Aircraft is descending Space => Aircraft altitude is enduring 3 characters 7 characters STAR/ DEST: for ARR in TMA; SID/ Exit point: for DEP in TMA;
Radio
Communication
DOCUMENT N: 0029200000000MA03
Line
Field
Displayed Information Cleared flight level (CFL) (Only for extended mode) Assigned speed (Only for extended mode) Destination aerodrome extended mode) (Only for
Valid Data Last point in FIR: for overflight via TMA.
3 characters 3 characters 4 characters
2.1.2.2.13
Uncontrolled in sector. Inbound Enroute role
The following table displays the elements in track label in extended mode (except the fields marked as Only in basic mode) Table 17: Uncontrolled in sector. Inbound Enroute : Fields Description Line Field Field A Field B Displayed Information Sector name ROF/ RAM/ ASSR/ Heading alert 2 characters FQ/ RO/ SQ/ HG (yellow) 1 character Field C 8.33/ UHF warnings 8 (YELLOW): 8.33 warning. 8 (RED): 8.33 alert. U (YELLOW): UHF equipped. 1 character Field D RVSM R (RED): RVSM alert. R (YELLOW): RVSM warning. Line 1 2 characters AW: MSAW (YELLOW: prediction; RED: violation) Field E MSAW/ APW/ MTCD alerts ZN: APW (YELLOW: prediction; RED: violation) MC: MTCD (YELLOW: prediction; RED: violation) 2 characters EM (RED): Emergency Field F Distress HJ (RED): Hijack RF (RED): Failure Radio Communication Valid Data 4 alphabetic characters
LB (YELLOW): CLAM alert

DOCUMENT N: 0029200000000MA03
Line
Field Field A Callsign ^ mark
Displayed Information 7 characters 1 character 3 characters 1 character 3 characters 1 character
Valid Data
Line 2
Ground speed/ Vertical speed Altitude indicator Mode C
Line 3
Field C
=> Aircraft is climbing => Aircraft is descending Space => Aircraft altitude is enduring 3 characters 3 characters 3 characters 1 character 5 characters 3 characters 1 character 3 characters 1 character 2 characters
Field D Field E Field A Line 4 Field B Field C Field A Field B Line 5 Field C Field D Field E
Cleared flight level (CFL) Exit flight level (XFL) Aircraft type/ Mode A (Only for extended mode) Wake turbulence category (Only for extended mode) Last point Assigned heading (Only for extended mode) Heading mark (Only for extended mode) Assigned speed (Only for extended mode) Assigned vertical rate indicator (Only for extended mode) Requested flight level (RFL) (Only for extended mode)
2.1.2.2.14
Uncontrolled in sector. Inbound Approach role
The following table displays the elements in track label in extended mode (except the fields marked as Only in basic mode) Table 18: Uncontrolled in sector. Inbound Approach : Fields Description Line Line 1 Field Field A Field B Displayed Information Sector name ROF/ RAM/ ASSR/ Heading alert 2 characters FQ/ RO/ SQ/ HG (yellow) Valid Data 4 alphabetic characters
Page 2-20
DOCUMENT N: 0029200000000MA03
Line
Field
Valid Data
Field C
8.33/ UHF warnings
8 (YELLOW): 8.33 warning. 8 (RED): 8.33 alert. U (YELLOW): UHF equipped. 1 character
Field D
RVSM
R (RED): RVSM alert. R (YELLOW): RVSM warning. 2 characters AW: MSAW (YELLOW: prediction; RED: violation)
Field E
ZN: APW (YELLOW: prediction; RED: violation) MC: MTCD (YELLOW: prediction; RED: violation) 2 characters EM (RED): Emergency HJ (RED): Hijack RF (RED): Failure Radio Communication
Field F
Distress
LB (YELLOW): CLAM alert Field A Line 2 Field B Field C Field A Field B Callsign ^ mark Ground speed/ Vertical speed Altitude indicator Mode C 7 characters 1 character 3 characters 1 character 3 characters 1 character Line 3 Field C Vertical Speed Indicator => Aircraft is climbing => Aircraft is descending Space => Aircraft altitude is enduring Field D Field E Field A Field B
Cleared flight level (CFL)
3 characters
Exit flight level (XFL) (Only for extended 5 characters mode) Aircraft type/ Mode A (Only for extended mode) Wake turbulence category (Only for 4 characters 1 characters
Page 2-21
Line 4
DOCUMENT N: 0029200000000MA03
Line
Displayed Information extended mode) Last point 5 characters Assigned heading (Only for extended 3 characters mode) Heading mark (Only for extended mode) Assigned speed (Only for extended mode) Assigned vertical rate (Only for extended mode) 1 character 3 characters 4 characters
Valid Data
Line 5
Field C Field D
2.1.2.2.15
Uncontrolled in sector. Inbound Tower role
The following table displays the elements in track label in extended mode (except the fields marked as Only in basic mode) Table 19: Uncontrolled in sector. Inbound Tower : Fields Description Line Field Field A Field B Displayed Information Sector name ROF/ RAM/ ASSR/ Heading alert 2 characters FQ/ RO/ SQ/ HG (yellow) Valid Data 4 alphabetic characters
1 character Field C 8.33/ UHF warnings 8 (YELLOW): 8.33 warning. 8 (RED): 8.33 alert. U (YELLOW): UHF equipped.
Line 1 1 character Field D RVSM R (RED): RVSM alert. R (YELLOW): RVSM warning. 2 characters AW: MSAW (YELLOW: prediction; RED: violation) Field E MSAW/ APW/ MTCD alerts ZN: APW (YELLOW: prediction; RED: violation) MC: MTCD (YELLOW: prediction; RED: violation)
DOCUMENT N: 0029200000000MA03
Line
Field
Displayed Information 2 characters
Valid Data EM (RED): Emergency
Field F
Distress
HJ (RED): Hijack RF (RED): Failure Radio Communication
LB (YELLOW): CLAM alert Field A Line 2 Field B Field C Field A Field B Callsign Aircraft type/ Mode A Wake turbulence category Altitude indicator Mode C 7 characters 4 characters 1 character 1 character 3 characters 1 character Field C Line 3 Field D Ground speed/ Vertical speed Vertical Speed Indicator => Aircraft is climbing => Aircraft is descending Space => Aircraft altitude is enduring 3 characters 7 characters Field E Last point STAR/ DEST: for ARR in TMA; SID/ Exit point: for DEP in TMA; Last point in FIR: for overflight via TMA. Field A Line 4 Field B Field C Cleared flight level (CFL) (Only for extended mode) Assigned speed (Only for extended mode) Destination aerodrome extended mode) (Only for 3 characters 3 characters 4 characters
2.1.2.2.16
Line Field Field A Line 1 Field B Field C
Not correlated. Enroute role

Table 20: Not correlated. Enroute : Fields Description Displayed Information Sector name ROF Distress 2 characters FQ 2 characters EM (RED): Emergency
Page 2-23
DOCUMENT N: 0029200000000MA03
Line
Field
Displayed Information RF (RED): Failure
Valid Data HJ (RED): Hijack Radio Communication
Field A Line 2 Field B Field C Field A Field B Line 3 Field C
SSR code ^ mark Ground speed/ Vertical speed Altitude indicator Mode C
4 characters 1 character 3 characters 1 character 3 characters 1 character => Aircraft is climbing => Aircraft is descending Space => Aircraft altitude is enduring
2.1.2.2.17
Not correlated. Approach role
The following table displays the elements in track label in extended mode (except the fields marked as Only in basic mode) Table 21: Not correlated. Approach : Fields Description Line Field Field A Field B Line 1 Field C Distress Displayed Information Sector name ROF 2 characters FQ 2 characters EM (RED): Emergency HJ (RED): Hijack RF (RED): Failure Field A Line 2 Field B Field C Field A Field B Line 3 Field C Vertical Speed Indicator SSR code ^ mark Ground speed/ Vertical speed Altitude indicator Mode C 4 characters 1 character 3 characters 1 character 3 characters 1 character => Aircraft is climbing => Aircraft is descending
Radio
Communication
DOCUMENT N: 0029200000000MA03
Line
Field
2.1.2.2.18
Not correlated. Tower role
The following table displays the elements in track label in extended mode (except the fields marked as Only in basic mode) Table 22: Not correlated. Tower : Fields Description Line Field Field A Field B Line 1 Field C Distress Displayed Information Sector name ROF 2 characters FQ 2 characters EM (RED): Emergency HJ (RED): Hijack RF (RED): Failure Line 2 Field A Field A Field B Line 3 SSR code Altitude indicator Mode C 4 characters 1 character 3 characters 1 character Field C Vertical Speed Indicator => Aircraft is climbing => Aircraft is descending Space => Aircraft altitude is enduring Field D Ground speed/ Vertical speed 3 characters Radio Communication Valid Data 4 alphabetic characters
2.1.2.2.19
Not correlated in sector. Enroute role
For each track type (controlled, inbound, not controlled), the track label contains the following information: Table 23: Not correlated in sector. Enroute : Fields Description Line Field Field A Field B Line 1 Field C
Displayed Information Sector name ROF 2 characters FQ 2 characters MSAW/ APW alerts
AW: MSAW (YELLOW: prediction; RED: violation)

Page 2-25
DOCUMENT N: 0029200000000MA03
Line
Field
Valid Data ZN: APW (YELLOW: prediction; RED: violation) 2 characters EM (RED): Emergency
Field D
Distress
Field A Line 2 Field B Field C Field A Field B Line 3 Field C
SSR code ^ mark Ground speed/ Vertical speed Altitude indicator Mode C
4 characters 1 character 3 characters 1 character 3 characters 1 character => Aircraft is climbing => Aircraft is descending Space => Aircraft altitude is enduring
2.1.2.2.20
Line Field Field A Field B
Not correlated in sector. Approach role

Table 24: Not correlated in sector. Approach : Fields Description Displayed Information Sector name ROF 2 characters FQ 2 characters AW: MSAW (YELLOW: prediction; RED: violation) ZN: APW (YELLOW: prediction; RED: violation) 2 characters EM (RED): Emergency Valid Data 4 alphabetic characters
Field C Line 1
MSAW/ APW alerts
Field D
Distress
Line 2
Field A Field B
SSR code ^ mark
4 characters 1 character
Page 2-26
DOCUMENT N: 0029200000000MA03
Line
Displayed Information Ground speed/ Vertical speed Altitude indicator Mode C 3 characters 1 character 3 characters 1 character
Valid Data
Line 3 Field C Vertical Speed Indicator
=> Aircraft is climbing => Aircraft is descending Space => Aircraft altitude is enduring
2.1.2.2.21
Line Field Field A Field B
Not correlated in sector. Tower role

Table 25: Not correlated in sector. Tower : Fields Description Displayed Information Sector name ROF 2 characters FQ 2 characters Valid Data 4 alphabetic characters
Field C Line 1
MSAW/ APW alerts
AW: MSAW (YELLOW: prediction; RED: violation) ZN: APW (YELLOW: prediction; RED: violation) 2 characters EM (RED): Emergency
Field D
Distress
Line 2
Field A Field A Field B
SSR code Altitude indicator Mode C
4 characters 1 character 3 characters 1 character => Aircraft is climbing => Aircraft is descending Space => Aircraft altitude is enduring 3 characters
Line 3
Field C
Field D
Page 2-27
DOCUMENT N: 0029200000000MA03
2.1.2.2.22
Sensitive Label Fields
Track label is not only for displaying aircraft values, it also allows to interact with it by value inputs, menus and templates display. Sensitive fields can be configured off-line. Predefined sensitive fields are: For Controlled Tracks: Table 26: Controlled Tracks Label Sensitive Fields Label position Line Field 1 A 2 B 2 D 3 D 3 E 4 A 4 C 5 A 5 C 5 D 5 E For Inbound Tracks: Table 27: Inbound Tracks Label Sensitive Fields Label position Line Field 1 A 2 B 2 D 3 D 4 A 4 C 5 E Function displayed Transference options (Transfer/ Assume) Callsign Menu Toggle: Vertical Speed/ Ground Speed PEL input pop-up display Toggle: Aircraft type/ Mode A Graphical route modification RFL input pop-up display Function displayed Transference options (Transfer/ Assume) Callsign Menu Toggle: Vertical Speed/ Ground Speed PEL input pop-up display XFL input pop-up display Toggle: Aircraft type/ Mode A Graphical route modification Heading input pop-up display Speed input pop-up display Vertical Rate input pop-up display RFL input pop-up display
For Uncontrolled Tracks: Table 28: Uncontrolled Tracks Label Sensitive Fields Label position Line Field 1 A 2 B 2 C
Function displayed Transference options (Transfer/ Assume) Callsign Menu Toggle: Vertical Speed/ Ground Speed
Page 2-28
DOCUMENT N: 0029200000000MA03
For Non-correlated Tracks: Table 29: Non-correlated Tracks Label Sensitive Fields Label position Line Field 1 A 2 B 2 C Function displayed Transference options (Transfer/ Assume) Callsign Menu Toggle: Vertical Speed/ Ground Speed
2.1.2.2.23
Action: Partial Track Label Orientation => {Graphical Mode}
Application: Perform this procedure to re-orient the label for a specific track. ACTION RESULT LB click on the track leader line. The label cycles through the possible label orientation (in 45 steps) counter-clockwise.
RB click on the track leader line. The label cycles through the possible label orientation, in 45 steps clockwise for each RB click on track leader line.
2.1.2.2.24 Action: Toggle Vertical Speed/Ground Speed => {Graphical Mode}

Application: Perform this procedure to toggle the Vertical Speed or Ground Speed display. ACTION RESULT LB Click on line 2, Speed field. The information displayed on the track-field toggles between the Vertical Speed and the Ground Speed.
Page 2-29
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
LB Click on it again. It returns the default display.
2.1.2.3 Extended Label

Extended label window is displayed from Callsign Menu (see 2.1.2.8).
Figure 2-4: Extended Label Table 30: Extended Label Fields Line Field Callsign Displayed Information Callsign Valid Data 7 characters in GREEN colour 1 character W (GREEN): approved; W RVSM status W (YELLOW): RVSM, state; RVSM non-
Line 1
W (RED): non-RVSM, not state. 1 character Y (GREEN): equipped; Y 8.33 status 8.33
Y (YELLOW): 8.33 not equipped, but UHF equipped. Y (RED): equipped. 8.33 not
Full Callsign
Full radio callsign

28 characters in GREEN
Page 2-30
DOCUMENT N: 0029200000000MA03
Line
Field
Valid Data colour 2 characters A/: mode A only; C/: mode A and/ or mode C; S/: mode A, mode C and/or mode S.
Transponder type
Transponder type
Mode A code Aircraft number x Aircraft type Wake turbulence
Mode A code Number of aircraft when in group flight.
4 characters 2 characters
Type of aircraft Wake turbulence
4 characters / + 1 character 27 characters /HOSP /EMER
Line 2 STS
Flight plan status from flight plan field STS (in field 18)
/SAR /HUM /HEAD /STATE.
ORCAM assigned SSR code. ORCAM SSR Departure aerodrome Destination aerodrome Alternate aerodromes Line 3 STAR Only visible when it is different than present mode A code. Aerodrome of departure code Aerodrome of destination code 2 alternate aerodromes in brackets STAR procedure 4 characters in YELLOW
4 characters 4 characters 11 characters 7 characters 7 characters in WHITE, except YELLOW when ROF is used by another sector or when track has been assumed by next unit.
Next Frequency
Frequency of next sector
Route Line 4 FIR exit level

Significant points in route. Maximum 7 41 characters points separated by spaces. Exit level from FIR
4 characters / + 3 digits
Page 2-31
DOCUMENT N: 0029200000000MA03
Line RFL
Field
Displayed Information Requested flight level Assigned vertical rate
Valid Data 6 characters in YELLOW RFL + 3 digits 10 characters RATE: + 4 digits + + or -
Rate
When displayed sign is +: more than displayed rate. When displayed sign is : less than displayed rate.
Line 5 NONPRNAV RVR min
NONPRNAV information, flight plan 8 characters in YELLOW field 10. Minimum RVR from RVR/ in flight plan 6 characters field 18 Not visible when no manual coordination is required. If any value is 7 characters displayed, blue coordination mark * in line 2 of TDB is displayed. ICAO Address; Selected Altitude; Heading; IAS (Knots); Mach; 111111-FFFFFF (3 characters) -180 to 180 0 to 1023 0 to 0,99 0 to 1023 -512 to 511 -16 to 16 - 90 to 90 -180 to 180
Coordination status
Line 6 Mode S data and 7
TAS; Inertial Vertical Velocity; Barometric Vertical Velocity; Track Angle Rate; Roll Angle; True Track Angle.
Line 8
Freetext
2.1.2.4 Track Colour

In order to the controller quickly identifies certain situations, the system provides the capability of classify the tracks by means of colour codes. The colour code is an adaptation data and it is applied to the symbol, leader, track, past positions, and tracks velocity vector. The below table states the colours used to distinguish the different types of tracks as they were defined in the adaptation data used when this manual was written. Alerts are coloured independently from the general label colour.
Page 2-32
DOCUMENT N: 0029200000000MA03
Example
Presentation
Meaning
GREEN
Controlled IFR track
YELLOW
Controlled VFR track
WHITE GREEN
with
the
callsign
Inbound IFR track
WHITE with YELLOW
the
callsign
Inbound VFR track Inbound from OAT seen by GAT sectors track OAT traffic seen by GAT sectors
WHITE with the callsign PINK PINK
GREY
Uncontrolled, outside sector
GREY with the SSR RED
Not controlled in sector
2.1.2.5 Leader Line

The leader line is the solid line that connects the track symbol with its track label. The label is located at 90 in relation with the tracks course.
Page 2-33
DOCUMENT N: 0029200000000MA03
Figure 2-5: Leader Line The track leader line is an active item that allows, by clicking on it, to rotate the leader line together with the track label in 45 steps. Clicking, with the LB, on the track label rotates counter-clockwise. When clicking on the leader line with the RB, the track label rotates clockwise. The system automatically detects and solves any overlapping display (automatic orientation of tracks labels [OVERLAP]). It is also possible to hold the label with CB and move it wherever (freely changing leader lines length and orientation). In such case, the label will not respond to further LB or RB click for step-tostep orientation, until [ORI OFF] disables individual label orientations.
2.1.2.5.1 Action: Track Label Free Individual Position Change

Application: Change track label position to allow a better display and make track label interactions easier.
ACTION RESULT
Click with the RB on the track label, and keep the button pressed.
At first, it seems the RBL creation procedure but immediately the cursor changes to a YELLOW label square jointed by a YELLOW line to the track.
Track only can be moved a configurable (by DATABLK) percentage of window size, known as stretching factor.
Page 2-34
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
Without releasing the RB, select a new position for the track within the screen and finally, release the RB.
2.1.2.6 Historical Positions

The past position of tracks and plots represent previous sites. They are displayed using points of fixed size being of the same colour as their associated tracks.
Figure 2-6: Historical Positions Symbol The number of past positions to be displayed can be selected between zero and ten per track.
2.1.2.7 Velocity Vector

The tracks can be displayed with an associated velocity vector. Velocity vector is a straight line from the track symbol to an extrapolated point. Its orientation is given by the course, and the length represents the space travelled in a selectablecontroller time T (1-10 min.).
Figure 2-7: Velocity Vector Symbol Velocity vector can be adjust in size: From [DATBLK] icon situated in the MM_A (see 2.3.13.2).
Page 2-35
DOCUMENT N: 0029200000000MA03
2.1.2.8 Presentation Range

SDD position display can be adjusted in presentation range to get the display closer or further and get a general or detailed sectors display. Presentation range can be adjusted: Selecting a predefined value from the pop-down menu in General Information Area, Performing manual expansion [EXP +] and [EXP -] actions, in Main Menu Area. By means of the keyboard: <+>/ <-> increase/ decrease presentation range in discrete steps.
2.1.2.9 Callsign Menu

Callsign Menu includes every available functions to be performed in the track. Callsign Menu is displayed by: RB click in Callsign track field. RB click in Callsign field of any flight list. Action selection is performed by LB clicking in the respective button, that displays the window or tool to perform the selected action. Some actions require acceptance for the action, or enter some parameters, and this input is also performed by Callsign menu. The available functions displayed in this menu for each track, depend of the track type (correlated, owned ) and the scenario conditions (alerts activation, radar mode).
Figure 2-8:
Callsign Menu (examples)
The available functions displayed in this menu for each track, depend of the track type (correlated, owned, ) and the scenario conditions (alerts activation, radar mode) and are the following:
Page 2-36
DOCUMENT N: 0029200000000MA03
TITLE ENTRY COORD EXIT COORD EXTENDED LABEL ASSIGN CODE FPL EDIT CREATE FICTITIOUS MINIMAL FP MANUAL CORRELATION DECORRELATE HOLD UNHOLD DECONTROL
FUNCTION Displays the Entry Coordination Window. Displays the Exit Coordination Window. Display the Extended Label for the track. Display the SSR code assignment window. Display the Flight plan operation window. Create a basic Flight plan for flights with special 2000 or 7000 SSR codes. Display the Minimal flight plan creation window. Performs a manual correlation action. Performs a decorrelation action. Performs the hold status for the track. Forces the end of hold status for the track. Performs the decontrol action, and the track becomes uncontrolled.
CONDITIONS TO BE DISPLAYED IN CALLSIGN MENU The coordination is Entry Type. The coordination is Exit Type. Track correlated, or track with Mode S. The track is primary owned and Monoradar is not active. The track is correlated. The track is not correlated, under control; the monoradar option is not active; the SSR code is 2000 or 7000. Not correlated and not under control track. Track not correlated. Track secondary correlated; under control track and the Monoradar option is not active. Track in hold status and under control. Or always in By-pass mode. Track in hold status and under control.
TRANSFER
ACCEPT TRANSFER REJECT TRANSFER ASSUME
FORCE ASSUME NO ALARM ROF

Track correlated; not in transfer phase; an Performs a hand-over advanced internal sector belongs to the action to leave the control route or an advanced external sector of the track. belongs to the route and the out coordination is AIDC type. Track correlated in transfer phase toward a Performs the acceptance sector under control; or a under control of the active transfer. advanced sector belongs to its route and it is in AIDC transferring phase. Performs the rejection of Track correlated and in transfer phase. the active transfer. Performs a hand-over Track not under control, not in transfer request to have the control phase and the By-pass option is not of the track. activated. Performs an ASSUME that does not require Track correlated, not in transfer phase, not agreement by the track under control, and assumed by other user. owner. Inhibits all active track Track under control; or the By-pass option alarms. is active, and the track is alerted. Track correlated and not in transfer phase Performs a request of and: frequency action. Exist advanced sector and under
DOCUMENT N: 0029200000000MA03
TITLE
FUNCTION
CONDITIONS TO BE DISPLAYED IN CALLSIGN MENU control sector is sectorized. Track under control. Track under control and previously forced emergency. Exist track and has STCA alert inhibited. Exist track and has STCA alert active. Exist track and has APW alert inhibited. Exist track and has APW alert active. Exist track and has MSAW alert inhibited. Exist track and has MSAW alert active. --------
Forces an emergence in the track. Allowed FORCE EMER emergencies: HIJ, COM, EME. CANCEL MAN Cancels previously force EMER emergency performed. ENABLE STCA Active STCA alarm. DISABLE STCA Inhibit STCA alarm. ENABLE APW Active APW alarm. DISABLE APW Inhibit APW alarm. ENABLE MSAW Active MSAW alarm. DISABLE MSAW Inhibit MSAW alarm. CLOSE Close the Callsign Menu
2.1.2.9.1 Action: Actions in Callsign Menu

Application: Main available actions, included in previous list (see 2.1.2.8) are quick and easy to be performed by Callsign Menu. ACTION RESULT Click with the RB on the Callsign symbol (both in the track label or in a flight plan list). The callsign menu with available options for the track is displayed.
Click in the action to be performed The action is performed automatically. If data are required to perform the action, an input window is displayed with the required fields. E.g. For Manual Correlation, this window is displayed:
Page 2-38
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
Edit the fields with the correct values (if input values is required). If input values are required, finish the action by clicking on one of the following icons: [OK] icon The action is triggered. The window is closed. [CLEAR] icon (if included) All values in Window are removed from fields. [CLOSE] icon The action is cancelled. The window is closed.
Page 2-39
DOCUMENT N: 0029200000000MA03
2.1.2.10
Tracks in Distress
Tracks may present following distress statuses: HJ. Hijack (7500) RF. Communication Failure (7600) EM. Emergency (7700) The pilot activates these statuses. Changing the frequency, the corresponding visual and aural alert is activated and the characters, which identify each distress type, are displayed on the track label within the Distress field (line 0, field B). These alarm options can be manually assigned by the controller by the Callsign Menu (only in own tracks).
Figure 2-9:
Tracks in Distress
2.1.2.11
Special Position Indicator (SPI)
The pilot sends a signal to cause the flight display on BLUE within the controller screen during 20 seconds in order to attract the controller attention and to indicate its presence within the sector.
Figure 2-10: Special Position Indicator (SPI)
2.1.2.12
Tracks in STCA
STCA Warning Tracks in STCA warning present a yellow circle around concerned tracks symbol; track symbol and velocity vector also turns YELLOW, as well as a YELLOW square surrounding the track label.
Two main conflict statuses can occur when there is a pair of tracks in STCA: Warning or Alert:
Page 2-40
DOCUMENT N: 0029200000000MA03
A yellow line is also displayed between both tracks in their route, and a seconds counter with the countdown to the violation phase.
Figure 2-11: Tracks in STCA Warning STCA Alert Tracks in STCA alert are similar than the STCA warning, but in red colour.
Figure 2-12: Tracks in STCA Alert
2.1.2.13
Tracks in MTCD
A predefined configurable VSP value before the STCA alert, the system warn the controller about this conflict by the MTCD alert. This alert is displayed in track label Alarm Indicator field by a MC yellow or red message, depending on the conflict seriousness. Tracks whose routes will not cross, but their proximity can also create a conflict, are also detected as MTCD conflict. A YELLOW MC message is displayed when the flight plan level in the predicted conflict point is outside the segment formed by the AFL and CFL values. A RED MC message is displayed when the flight plan level in the predicted conflict point is inside the segment formed by the AFL and CFL values.
Figure 2-13: Track in MTCD

DOCUMENT N: 0029200000000MA03
Controller can manually display MTCD conflict zone. When several tracks are in MTCD conflict, or a track is in MTCD conflict with some other tracks, only one MTCD conflict can be displayed at the same time.
Figure 2-14: Tracks in MTCD Conflict zones
Page 2-42
DOCUMENT N: 0029200000000MA03
Figure 2-15: Tracks in MTCD (routes not cross) Conflict zones Clicking in MC field, three zones are displayed: Continuous white line: selected track (MTCD conflict track whose MC message was clicked) Discontinuous white line: not-selected track (MTCD conflict track whose MC message was not clicked) RED line: MTCD conflict zone.
Page 2-43
DOCUMENT N: 0029200000000MA03
2.1.2.13.1
Action: MTCD Conflict
Application: Display several information about an MTCD conflict to analyse the conflict to predict a solution. It is required that tracks in MTCD conflict are under control.
ACTION For two under control tracks in MTCD conflict (MC message displayed in track label, and MTCD conflict mark in flight plan lists), LB click in MC message in one of those track label.
RESULT
Three zones can be distinguished, by: Continuous white line: route for one of tracks in MTCD conflict (the one whose MC field was clicked) Discontinuous white line: route for the other track in MTCD conflict. RED line: route for MTCD conflict zone.
Clicking in MC field for a few seconds, the rest of tracks are displayed in lighter colours to remark selected MTCD conflict. To display Conflict Window with all current MTCD conflicts: LB click in [FLP] icon in General Information area, and select [CONFLICT] option. Conflict window is displayed with every MTCD conflicts.
Page 2-44
DOCUMENT N: 0029200000000MA03
ACTION To display Conflict Window conflicts for a single track: with MTCD
RESULT
LB click in one of MTCD conflict track first field in a Flight plan list. Conflict window is displayed for selected track, including current MTCD conflict.
RB click in graphical zone in conflict window, in one of the tracks in conflict marks (triangle mark) Track horizontal future situation/ vertical future situation (HFS/ VFS) window is displayed.
Page 2-45
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
Finish the action by clicking on the [CANCEL] icon in Conflict Window and in [X] icon in VFS window. The future situation windows is closed.
Page 2-46
DOCUMENT N: 0029200000000MA03
2.1.2.14
Tracks in APW
Track label displays ZN in YELLOW (prediction) or RED (violation) in alarm field (see 2.1.2.2).
Figure 2-16: Track in APW Prediction
Figure 2-17: Track in APW Violation Two main conflict statuses can occur when there is a pair of tracks in APW: Prediction (APW -P) and Intrusion (APW-I): Prediction (APW-P): APW-P comes about when a future intrusion is foreseen, a VSP time before it happens. Intrusion (APW-I). In APW list, tracks in APW-P are displayed in YELLOW colour in APW list, and tracks in APW-I are displayed in RED colour in APW list.
Figure 2-18: APW list Prediction
Figure 2-19: APW list Violation
Page 2-47
DOCUMENT N: 0029200000000MA03
2.1.2.15
Tracks in MSAW
This function is especially necessary if the control center geography forms many mountainous and slopes. The System allows definition of dangerous areas and if an aircraft is flying very low, an alarm triggers. It is necessary to define the MSAW area in the adaptation database in order to trigger a MSAW alert when a track is entering the area. It is defined both the shape and the level. If an aircraft is descending from the area level when crossing that area, it will be in danger, and the track will be in MSAW alert. Track label displays AW in YELLOW in Alarm Indicator (see 2.1.2.2) field for MSAW in prediction phase. The SDD emits an acoustic signal during that status. Track label displays AW in RED in Alarm Indicator field for MSAW in violation. When the aircraft leaves the area or climbs out the area level both the alert graphical presentation and the sound ceased.
Figure 2-20: MSAW alert - Prediction
Figure 2-21: MSAW alert - Violation
Figure 2-22: MSAW List
2.1.2.15.1
Profiles in MSAW Areas
In case an aerodrome within the FIR is situated in a mountainous zone, which may causes warnings, it is necessary to define a MSAW area. It is possible to define profiles to avoid flights, which correctly take off and land by following the established procedures, to emit the MSAW alert. The profiles creation is performed in the adaptation database. The profile consists of a circular area, which surrounds the airport, and a corridor, which goes from this one to the outside of the area outline. Through this corridor, the aircraft does not em it the MSAW Alert but when an aircraft does not follow this profile, it will trigger the MSAW Alert.
Page 2-48
DOCUMENT N: 0029200000000MA03
2.1.2.16
RVSM Alarm
The System provides the possibility to define if a sector supplies navigation with RVSM or not from the adaptation database. If so, the aircraft within the sector between the FL290 and FL410 flight levels must be equipped with RVSM to make better use of the airspace. When the RVSM alarm is displayed, the track label includes this alarm, as defined (see 2.1.2.2) The CMD Position defines the separation parameters in RVSM levels.
Figure 2-23: Track in RVSM alert
2.1.2.17
8.33 Alarm
As the RVSM navigation requests to make better use of the airspace, the 8.33 frequency tries to make better use of the radio frequencies space. This alarm is started when the track is above a flight level defined in Alarm 8.33 Level adaptation parameter, and it is not equipped (Y en N.E. field of Flight Plan Window).
Figure 2-24: Track in 8.33 alarm
2.1.2.18
CLAM Alert
As described in point, it is possible to enter a new Cleared Flight Plan Level (CFL) in a correlated owned track through the CFL field (line 2, field B). If the aircraft does not reach the requested level (with a tolerance parameter defined in Conformance Altitude Threshold VSP) in a time defined by CFL Stability Age adaptation parameter, the CLAM alert (LB) is displayed in YELLOW (see 2.1.2.2).
Figure 2-25: Tracks in CLAM
Page 2-49
DOCUMENT N: 0029200000000MA03
2.1.2.19
Heading Alarm
This alarm is displayed in YELLOW in Alarm Indicator field (see 2.1.2.2) of a correlated track label. The system allows to enter values into heading field (see 2.1.2.2). Then, the System checks if the assigned orientation matches the real one. If entered heading exceeds the Heading Tolerance adaptation parameter, the system waits the time defined in Heading Stability Age adaptation parameter before displaying Heading Alarm.
Figure 2-26: Track in Heading alert
2.1.2.20
Route Conformance and Adherence Monitoring (RAM) Alert
This alert is displayed when the track real position distance to the predicted flight plan is greater than RAM Lateral Distance adaptable value (except for fix points, where the value is 10 NM). In track label, the YELLOW RO message is displayed in Alarm Indicator field (see 2.1.2.2).
Figure 2-27: Track in RAM alert
2.1.2.21
QNH Altitude Correction
The AirCon 2100 system allows definition of pressure areas around the airports. The adaptation database performs this definition by establishing shape, Transition Altitude and the airport where they are situated. For flights below the Transition Altitude, the System displays the Mode C value corrected for the current QNH or QFE-Correction in accordance with the current setting. This display is clearly distinguishable from normal Mode C by adding an A in front of the flight level.
2.1.2.22
Synthetic Tracks
A synthetic track is a track automatically generated by the System or upon controllers request. Synthetic tracks progress based on their FP route. Thus, synthetic tracks base is the existing FP and not the radar information. The track always follows the FP data: level, speed, route, etc. To request the System, this procedure performs a generation of flight positions along the time except when there is no radar information associated to the Flight Plan. Automatically, when the flight passes from a covering radar area to a non-covering radar area, it becomes a synthetic track.
DOCUMENT N: 0029200000000MA03
The label and the colour is the same as for the real tracks (see previous sections). A special symbol distinguishes the synthetic tracks from the real ones.
Figure 2-28: Synthetic Track The controller may fulfil a position report (Fix point, ATO and Flight Plan Level) for a synthetic track. Likewise, it is possible to enter a new CFL for synthetic tracks.
2.1.2.22.1
Creation and cancellation of Synthetic Track
It could be possible to create and cancel a Synthetic Track. The operator could select the corresponding FP and it appear the "FPL Menu" displayed by LB click in Sector List first field Or LB click in Track Symbol.
Figure 2-29: FPL Menu Selecting "CREATE" option, the system will create a Synthetic Track for that FP. Selecting "DELETE" option, the system will cancel a Synthetic Track for that FP.
2.1.3 Flight Plan Correlation

When the radar track (SDP) has a Flight Plan (FDP) associated with the same SSR Code as the track. If the track is Mode S, the Callsign performs the correlation, not using the SSR Code for that purpose. Therefore, if the SDP is not running and/or the Bypass Mode is working, the tracks cannot correlate with Flight Plans. Once the track has correlated, its label changes colour. The Flight Plan information is associated to this track and the flight label presents the most relevant one. The System provides two types of correlation: automatic and manual.
Page 2-51
DOCUMENT N: 0029200000000MA03
2.1.3.1 Automatic Correlation

The System must fulfil following two requirements to correlate a FP automatically: If the track is not Mode S, there must be a FP in the FPs Data Base with the same SSR Code as the track in question. If the track is Mode S, there must be a FP with the same Callsign. The radar track must stay at a minimum distance according to the route and times of that Flight Plan. This functionality is called Geographical Coordination.
2.1.3.2 Manual Correlation/ Decorrelation

Correlation The operator has the possibility to perform a manual correlation of a non-correlated track with a FP with the same SSR Code, independently of the distance between the track and the Flight Plan route. Click on the track symbol, or in the correlation option in Callsign menu. Fill in the Callsign field of the displayed Manual Correlation Window and click in OK, the rest of the fields will be automatically filled. The action finishes with a procedure to close actions.
Figure 2-30: Callsign Menu - Manual Correlation
Figure 2-31: Manual Correlation Window

NOTE: If the Flight Plan Ambiguity is initiated, the operator may force the association via manual correlation by selecting the track considered as correct.
Decorrelation As FPs can be associated, the controller can manually decorrelate a FP of a owned track. That is, take its FP away. The FP keeps the status it has, that is, it is not cancelled nor deleted, and it is only decorrelated. This action is performed by Callsign menu of a own track.
Page 2-52
DOCUMENT N: 0029200000000MA03
Figure 2-32: Manual Decorrelation Once the action is accepted, the track changes the colour defined for non-correlated tracks and it displays the information coming from the radar but not the one of the Flight Plan. The track and the Flight Plan will not be automatically correlated each other any more. If correlation is required, the action must be manual.
2.1.3.3 Abbreviated Flight Plan (APL)

There are two special SSR codes reserve for visual flights: 2000 and 7000. An aircraft with one of the two SSR codes can create an Abbreviated Flight Plan or Fictitious Flight Plan. It is not a real Flight Plan as the track-displayed information, apart from the SSR code, is the Callsign. If the Callsign exists in any other track, the System does not allow that Callsign assignment. The special behaviour of these tracks (including this code) is that there can exist more than two (2) flights with 2000 and 7000 codes without causing track ambiguity (2 or more tracks with the same code).
Figure 2-33: APL Menu Field CALLSIGN CSSR SSR code Table 31: APL Window. Edition Fields Description Aircraft identification 4 digits Valid Data
2 to 7 alphanumeric characters
Page 2-53
DOCUMENT N: 0029200000000MA03
2.1.3.3.1
Action: Create an APL
It's possible to associate an abbreviated flight plan following the next steps: 1. Assume the track by the sector. 2. Click on the callsign field with RB. It appear the following menu: 3. It will be possible to assign a Callsign to that track 4. If the callsign exist for other track, the system don't allow to assign that callsign for that track Application: Perform this procedure to create an abbreviated flight plan. This action is only available for owned tracks with special SSR code 2000 or 7000. ACTION RESULT RB click on the Callsign field of the track label (line 1, field A) of a non correlated track with SSR code 2000 or 7000. The Callsign menu is displayed. Select Create Ficticious. The Abbreviated FP Creation window is displayed.
Enter data in the Callsign field.
If the callsign exist for other track, the system don't allow to assign that callsign for that track.
Finish the action by clicking on one of the following icons: [OK] icon The abbreviated FP is created.
DOCUMENT N: 0029200000000MA03
ACTION [CLOSE] icon
RESULT The creation action is cancelled.
[CLEAR] icon The displayed data is deleted from the Abbreviated FP window (action mode).
2.1.3.4 Minimal Flight Plan

When a track has no Flight Plan associated to it, apart from creating a Flight Plan to associate it with the track, it is possible to create a Minimal Flight Plan just including the necessary fields reducing the FP creation action by far. Minimal FP Window is displayed from Callsign Menu, clicking with the RB on the Callsign field of the track label (line 1, field A)
Figure 2-34: Callsign Menu - Minimal FP
Figure 2-35: Minimal FP Window Field CALLSIGN CSSR SSR code Table 32: FP Min Window. Edition Fields Description Aircraft identification 4 digits
Page 2-55
Valid Data
2 to 7 alphanumeric characters
DOCUMENT N: 0029200000000MA03
Field DEP DEST
Description Departure Aerodrome Destination Aerodrome
Valid Data 4 alphanumeric characters 4 alphanumeric characters Flight level (hundreds of feet): Fxxx where xxx 000 to 999. Altitude (hundreds of feet): Axxx where xxx 000 to 999. Level (tents of meters): where xxxx 0000 to 9999. Sxxxx
CFL
Requested Flight Level
Altitude (tents of meters): Mxxxx where xxxx 0000 to 9999. 2 to 4 alphanumeric characters. The first one shall be an alphabetic character. It shall be known by the system. L= WAKE Type of wake turbulence M= H= J= EQ Equipment light medium heavy super-heavy
TYPE
Type of Aircraft
Up to two alphabetic characters. W = RVSM equipped Y = 8.33 equipped The required fields are Callsign, SSR Code and Destination. If necessary, it is possible to access to the Flight Plan template (FP Operation Window) later on to enter the rest of the fields. If so, the track colour changes to the one corresponding to a normal correlated track and it will not be displayed as a track with Minimal Flight Plan any more.
2.1.3.4.1 Action: Minimal FP Creation => {Graphical Mode}

Application: Perform this procedure to create a minimal FP (only for owned tracks). ACTION RESULT RB click on the Callsign field of the track label (line 1, field A) of a non correlated track. The Callsign menu is displayed. Select Minimal FP option. The Minimal displayed. FP Creation window is
Page 2-56
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
Enter data in the Callsign and Destination Airport fields. Complete the empty fields.
Finish the action by clicking on one of the following icons: [UPDATE] icon The minimum FP is created. [CANCEL] icon The creation action is cancelled. [CLEAR] icon The displayed data is deleted from the FP Operation window (action mode).
2.1.4 Meteorological Data

Meteorological data are displayed as continuous information through seven different intensities. The information is extracted from the radar messages and radar information. A meteorological map consists of several layers with different intensities, which can be displayed in different colours that can be chosen by the controller through a menu.
DOCUMENT N: 0029200000000MA03
The meteorological map is showed like a continuous map up to 7 intensities and with any form. The controller can choose the option of displaying the meteorological maps, pressing the METEO button at the Main Menu window. The operator can display the different intensities selecting the [MET'X'] button and can set and change the colour for each intensity by clicking in each coloured and numbered square. For each selected button, the SDD shows meteorological data received from radars.
Figure 2-36: Meteorological Data Display
Figure 2-37: Meteorological Data Display
2.1.5 Range Bearing Lines (RBL)

The RBLs are dynamic information traces represented between:
DOCUMENT N: 0029200000000MA03
Geographical Point Geographical Point The displayed information is fixed. Geographical Point Track The displayed information is updated according to the track movement. Track Track The displayed information is updated according to the tracks movement. The RBL creation is undergone by means of the keyboard as shown in following table: Mouse Button Action CB RB LB Start/ finish the RBL creation action Abort the RBL creation action Display the geodesic coordinates of the final end of the RBL
Figure 2-38: Range Bearing Lines (RBL) Display RBLs can be removed all together by means of the [RBL OFF] icon, and individually by clicking CB in the RBLs label. Alarms can be programmed for the RBLs if it is attached to a track. The RBL colour is YELLOW while creation action and when this action has finished the colour is BLUE. For all the RBLs with programmed and activated alarm, the colour will be RED for the line and for the fields where the alarm is assigned. The RBL label format depends on its status as shown in following table: Table 33: RBL Label. Format Status RBL between two geographical points
Format
DOCUMENT N: 0029200000000MA03
Status Line 1: B: Azimuth
Format Between initial point (geographical point of activation) and the final point (geographical point where the RBL cursor is located). Line 2: R: Distance Between the two end points (in nautical miles).
RBL between geographical point-track and track-track converging to the same point Line 1: B: Azimuth Between initial point (geographical point of activation) or track and the track. Line 2: R: Distance Between the origin and the associated track or between both associated tracks (in nautical miles). Line 3: T: Time Estimated time, in minutes, to/ from the point of origin to the RBL cursor, assuming that the flight is heading from/ to that direction. Line 4: X: Distance Estimated minimum distance, in nautical miles, between the RBL ends. Depending on the RBL location and its end-points, the fields displayed on the vector label may change: Between geographical point geographical point Display Line 1 (B) and Line 2 (R). Between geographical point track If the track is not going to cross the imaginary perpendicular between the geographical point and the route, only Line 1 (B) and Line 2 (R). If the track is going to cross the imaginary perpendicular between the geographical point and the route, Line 1 (B), Line 2 (R), Line 3 (T) and Line 4 (X). Between track track If according to the tracks heading, these ones are not going to cross each other, only Line 1 (B) and Line 2 (R). If according to the tracks heading, these ones are going to cross each other, Line 1 (B), Line 2 (R), Line 3 (T) and Line 4 (X). Lines 3 and 4 are displayed if the ends of the RBL are approaching. Once the minimum distance point is reached, lines 3 and 4 are removed. The RBL colour is YELLOW during its creation period and, when the creation is finished, the colour is BLUE. RBLs Deletion: Click with the CB on the RBL label to deleted RBLs one by one
DOCUMENT N: 0029200000000MA03
Click with the mouse LB on the [RBL OFF] icon to delete all. It is possible to established alarms for the RBLs for each value. When the value exceeds the established limit, the System activates the alarm and the colour changes to RED for the vector line and for the fields where the alarm is assigned.
2.1.5.1 Action: Create Range Bearing Line => {Graphical Mode}

Application: Perform this procedure to create a new Range Bearing Line in the SDD SIT Area. ACTION RESULT CB Click on the screen to mark the initial point (geographical point, track, etc.) In this phase, the RBL displays a label with the information. The RBL colour in this initial phase is YELLOW.
While the RBL is being created. The mouse buttons have functions different to those normally assigned. LB Displays the geographical coordinates of the free end of the RBL. CB Cancel the RBL creation procedure. RB End the RBL creation.
Page 2-61
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
2.1.5.2 Action: Program RBL ALARMS => {[RBL ALM]}

Application: Perform this procedure to program alarms in the Range Bearing Line. ACTION RESULT Once the RBL has been created, LB click on the [RBL ALM] switch of the Main Menu window. The RBL alarm programming function is activated. RB click on the RBL label corresponding to the alarm to be programmed. Depending on the selected line, the pop-up menu title is different (azimuth, range, time and minimum estimated distance). The pop-up menu contains the different type of alarms: Inhibits a (DISABLE) previous programmed alarm
Warn that the field values are within certain limits (INSIDE) Warn that they are outside limits (OUTSIDE) Warn that the field value is above a limit (OVER) Warn that it is below a limit (UNDER)
Page 2-62
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
Select the type of alarm by LB clicking on the option. Depending on the type of alarm, subsequent pop-up menus or windows are displayed to allow the values selection.
The value selection may be performed: By clicking twice on the desired value or, By entering the data in the Edition field. When the value has been selected, the window is automatically closed (in both cases).
Page 2-63
DOCUMENT N: 0029200000000MA03
ACTION When the alarm is reached, the RBL line and the corresponding field of the RBL label are activated and turn to RED colour.
RESULT
An alarm may be programmed for each field simultaneously. The alarm may be accepted (inhibited) Manually: by clicking on the corresponding alarm with the LB. Automatically: when the alarm has been fulfilled. CB Click on any programming menu or window title. The programming procedure under way is automatically cancelled.
2.1.5.3 Action: Partial RBL Removing => {Graphical Mode}

Application: Perform this procedure to remove only the selected RBL from the SDD SIT Area. ACTION RESULT CB Click on the label first line of a created RBL. The RBL is removed from the screen.
2.1.5.4 Action: Remove RBLs => {[RBL OFF]}

Application: This action starts from the [RBL OFF] icon situated in the MM_A. ACTION RESULT Click in [RBL OFF] in Main Menu Area. Every RBL is removed from SDD display.
Page 2-64
DOCUMENT N: 0029200000000MA03
2.1.6 Flight Plan Route

Correlated track flight plan routes are graphically displayed, using a sequence of vectors which joint the successive route points, starting from the first overflown fix point and ending with the last route point. When no fix points have been overflown, the whole flight plan route is displayed. Each flight plan route vertex has a label with three lines. The flight plan routes are displayed on GREEN (see following figure). When the route is being modificated it is displayed in LIGHT BLUE colour.
Figure 2-39:
Flight Plan Route Display
Each vertex displays the following information: Table 34: Track Flight Plan Route Label
Line Description Format
First Line Second Line Third Line
Display the fix point name. Display the estimated time to over fly the fix point. Display the flight level assigned to the corresponding fix point. HH:MM Hundreds of feet
2.1.6.1.1 Action: Graphical Route Visualization

Application: Use this procedure to display the flight plan route. There are two ways to display Graphical route: From Track Label:
ACTION RESULT
LB click on the LAST POINT field of Track label. The FP route is displayed.
Page 2-65
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
LB click on the LAST POINT field of Track label. The FP route display is inhibited. From Graphical route modification Menu:
ACTION RESULT
LB Click on the LAST POINT field in the track label. The route is showed in LIGHT BLUE colour. A pull-down menu is displayed with several options:
1.- Choose the Display option in the menu. The graphical route is displayed. 2.- Choose the Cancel option in the menu. The action of graphical modification is cancelled and no modification is performed.
DOCUMENT N: 0029200000000MA03
2.1.6.1.2 Action: Graphical Route Modification

Application: Perform this procedure to graphically modify the current flight plan route. Flight Plan route modification can be performed: From the track label From the FP template From the Track label
ACTION RESULT
RB Click on the LAST POINT field in the track label. The route is showed in LIGHT BLUE colour. A pull-down menu is displayed with several options:
There are two options to draw modification or finish the action:
a route
1.- Choose a fix point or an arrival aerodrome in the list. The route is modified directly from current point until the selected fix point or aerodrome. 2.- Choose the Edit option and click on fix points or any geographical point, drawing the desired route. Note: The last point must belong to the former route or an aerodrome or an external point, if it is an external route.
Page 2-67
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
If the selected points to modify the route are valid, the modification is performed. If there is a non-valid point, the action finishes and any modification is not performed. 3.- Choose the Cancel option in the menu. The action of graphical modification is cancelled and no modification is performed. From the flight plan template => {Track symbol -> FP Operation -> [MODIFY]}
ACTION RESULT
RB click in track symbol The flight plan template is displayed LB click in Modify and select the Route field The route field is displayed. Perform a route modification Click in OK button to accept the modification If route entered is correct, the flight plan template turns to View action and route modification is performed. If route entered is wrong, a List of routes window is displayed with available correct routes for that flight. LB double click in a route select it and clicking in OK button performs the acceptance action. Clicking in CLOSE button the modification is cancelled and the flight plan template is closed without changes.
Page 2-68
DOCUMENT N: 0029200000000MA03
2.1.7 Actions on Owned Tracks

Actions to carry out on an owned track: Track Selection from the FPs List Input of New CFL Estimate in Track Enter into the Hold List Exit from the Hold List. Hand-Over Procedure Distress Procedures Minimum FP Creation
2.1.8 Transfer Actions

The track change of sector always requires manual intervention, both if the involving sectors (current and future) are inside the fir, or the track comes from-to an external sector. A VSP time before the internal sector crossing point (COP), the FQ alert is displayed to remind the controller to transfer the track. Several actions can be performed to transfer tracks.
2.1.8.1 Action: Transfer to next sector in route

Application: This action is performed to transfer the control of the track to the next sector in the flight plan route. NOTE: In controller sector, the label sector field displays the next sector that will control the track, and in future sector (where the track is an incoming one) the label sector field displays the current controller sector.
ACTION RESULT
For an own track LB click in the Callsign label field. The Callsign Menu is displayed.
LB click in TRANSFER option.
Page 2-69
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
The transfer process is started. The transfer is marked in Sector field in both positions involved in the transfer. In Controlled position: marked with RED colour. In Future position: ORANGE colour. In the future controller position LB click in Callsign track label field. The Callsign Menu is displayed, with options to Accept and Reject the transference. marked with
To Accept: LB click in ACCEPT TRANSFER. The Callsign Menu is closed and the track is transferred, becoming own in the position and not own in the position that begins the transference. To Reject: LB click in REJECT TRANSFER. The Callsign Menu is closed and the transference is cancelled, remaining the track control as before the transfer action.
2.1.8.2 Action: Transfer to any sector

Application: This action is performed to transfer the control of the track to any FIR sector.
ACTION RESULT
For an own track LB click in the Sector label field.
Page 2-70
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
The Transfer Menu is displayed, with available sectors where can be transferred.
LB click in the sector to transfer. The transfer process is started. The transfer is marked in Sector field in both positions involved in the transfer. In Controlled position: marked with RED colour. In Future position: ORANGE colour. In the position that controls the selected sector LB click in Sector track label field. The Transfer Menu is displayed, with options to ACCEPT and REJECT the transference. To Accept: LB click in ACCEPT TRANSFER. The Transfer Menu is closed and the track is transferred, becoming own in the position and not own in the position that begins the transference. To Reject: LB click in REJECT TRANSFER. The Transfer Menu is closed and the transference is cancelled, remaining the track control as before the transfer action. marked with
2.1.8.3 Action: Request of Frequency => [ROF]

Application: This action is performed in the incoming track to request the transfer of the track.
ACTION RESULT
Page 2-71
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
For an incoming track, LB click in the Callsign label field. The Callsign Menu is displayed.
LB click in ROF field. In both positions (current and future under control sectors) the FQ alert is displayed in track label. This action is finished with a transfer action from the controlled sector
2.1.8.4 Action: Request of Transfer Level

Application: This action is performed to negotiate the flight level for the coordination point. This action can be performed both when the track is controlled and when it is inbound. For Inbound Track:
ACTION RESULT
For an incoming track, RB click in External flight level (PEL) field (see 2.1.2.2)
Page 2-72
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
PEL pop-down menu is displayed with available level values for entering the sector.
Select and accept a value by: LB click in predefined values (automatic acceptance); Entering a value in the edition field (acceptance by <Enter> key); Entering a value by the numbered buttons (acceptance by [Enter] button).
Page 2-73
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
The field value change its colour both in the inbound track and in the position that controls the track. In the position that controls the track:
In the position where the track is inbound:
In the position that controls the track, LB click in the orange coloured field. The XFL menu is displayed, with options to enter a new level (re-negotiate the transfer level), accept the proposed level or reject it.
In the position where the track is inbound, LB click in PEL field will display the PEL menu again, with a REJECT button to cancel the action.
Page 2-74
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
The negotiation action is finished by: Accept proposed level: LB click in ACCEPT option in XFL menu in position that controls the track. Reject proposed level: LB click in REJECT option in XFL menu in position that controls the track. For Controlled Track:
ACTION RESULT
For a controlled track, LB click in External flight level (XFL) field (see 2.1.2.2) XFL pop-down menu is displayed with available level values for entering the sector.
Page 2-75
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
Select and accept a value by: LB click in predefined values (automatic acceptance); Entering a value in the edition field (acceptance by <Enter> key); Entering a value by the numbered buttons (acceptance by [Enter] button). The field value change its colour both in the inbound track and in the position that controls the track. In the position that controls the track:
In the position where the track is inbound:
In the position that controls the track, LB click in the field.
Page 2-76
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
The PEL menu is displayed, with options to enter a new level (re-negotiatethe transfer level), accept the proposed level or reject it.
In the position where the track is controlled, LB click in XFL field will display the XFL menu again, with a REJECT button to cancel the action. The negotiation action is finished by: Accept proposed level: LB click in ACCEPT option in XFL menu in position that controls the track. Reject proposed level: LB click in REJECT option in XFL menu in position that controls the track.
Page 2-77
DOCUMENT N: 0029200000000MA03
2.1.9 Miscellaneous Actions within the SIT_A 2.1.9.1 Cleared Flight Level (CFL)
CFL is used in order to change the Authorized Flight Level of the Flight Plan, but this CFL will not be used to compute a new trajectory calculation. The flight level is changed at the request of the pilot. When the pilot requests the change of the flight level, the following steps will be carried out: 1. Click with the LB on the Track Label, field CFL (see 2.1.2.2), and input the new desired CFL. CB cancels the action.
Figure 2-40: CFL Menu 2. In Synthetic tracks: When the pilot informs to the Controller that the authorized Flight Level has been reached, the Controller will delete this Flight Level from the Track Label (This Flight Level is located at the right of the Callsign). In Radar Tracks: The Flight Level is automatically deleted when the authorized Flight Level has been reached. Remarks: It is necessary to be awarded that the data seen on the controller screen will be those sent by the radar. Of course, if the aircraft is out of the radar overage it is displayed as synthetic track. This synthetic track takes data from the FP.
Page 2-78
DOCUMENT N: 0029200000000MA03
2.1.9.1.1
Action: Input of New CFL => {Graphical Mode}
Application: Perform this procedure to input a new CFL (only for owned tracks). ACTION RESULT RB click on the track CFL field (line 1, field C) The CFL pop-up menu is displayed to select/ enter the desired new one.
The new CFL can be entered either: By LB clicking on the predefined value. Entering the new value into the Edition field via keyboard or via provided numbered buttons. Afterwards it is required to accept it (by Enter key or by ENTER button). The selected or entered value is automatically updated on the track label. At the same time, the window is closed.
If the flight crosses the assigned level but it does not keep the level, the Controller notices a CLAM alert.
Page 2-79
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
2.1.9.2 Action: Enter New HDG (Heading)

Application: Enter a new heading value (only for owned tracks or synthetic tracks).
ACTION RESULT
Click with the mouse LB on the heading field This action displays the Heading Menu to select of the track label, marked with an h (see or enter a new value. 2.1.2.2).
The new HDG can be entered: Clicking with the LB on the predefined value. Predefined values can be increased by activating the +5 button, and the original value is restored by inhibiting the +5 button. Entering the new value into the Edition field via keyboard or via provided numbered buttons. Afterwards it is required to accept it (by <Enter> key or by ENTER button).
The action automatically updates the selected or entered value in the track label. At the same time, the window is closed.
Page 2-80
DOCUMENT N: 0029200000000MA03
2.1.9.3 Action: Enter New XFL (Exit Flight Level)

Application: Enter a new XFL.
ACTION RESULT
Click with the mouse LB on the XFL field of This action displays the XFL Menu to select or the track label (see 2.1.2.2). enter a new value.
Select APPLY option for apply selected value in trajectory calculation (only for ascent flights). The new XFL can be entered: Clicking with the LB on the predefined value Entering the new value into the Edition field via keyboard or via provided numbered buttons. Afterwards it is required to accept it (by <Enter> key or by ENTER button).
Page 2-81
DOCUMENT N: 0029200000000MA03
2.1.9.4 Action: Enter New SPD (Speed)

Application: Enter a new assigned speed (only for owned tracks or synthetic tracks).
ACTION RESULT
Click with the mouse LB on the speed field of This action displays the Speed Menu to select the track label, marked with an s (see or enter a new value. 2.1.2.2).
Values can be displayed in Knots or Mach number, and it can be changed by clicking in the correspondent button. Two predefined values are included in the set of numerical ones: NSP: No ATC Speed Restrictions. MIN: Minimum clean configuration/ Minimum approach speed. The new SPD can be entered: Clicking with the LB on the predefined value. Entering the new value into the Edition field via keyboard or via provided numbered buttons. Afterwards it is required to accept it (by <Enter> key or by ENTER button).
Page 2-82
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
2.1.9.5 Action: Enter New VR (Vertical Rate)

Application: Enter a new Vertical Rate (only for owned tracks or synthetic tracks).
ACTION RESULT
Click with the mouse LB on the vertical rate This action displays the vertical rate menu to field, marked with r, of the track label (see select or enter a new value. 2.1.2.2).
Values are displayed in feet/ minute. The new vertical rate can be entered: Clicking with the LB on the predefined value Entering the new value into the Edition field via keyboard or via provided numbered buttons. Afterwards it is required to accept it (by <Enter> key or by ENTER button). + and - buttons means or more and or less and can be pressed to indicate the entered vertical rate is the minimum or maximum value allowed. The action automatically updates the selected or entered value in the track label. At the same time, the window is closed, and the track label changes the r field to R.
Page 2-83
DOCUMENT N: 0029200000000MA03
2.1.9.6 Action: Enter New RFL(Requested Flight Level)

Application: Enter a new RFL (only for owned tracks or synthetic tracks).
ACTION RESULT
Click with the mouse LB on the RFL field of the This action displays the RFL menu to select or track label (see 2.1.2.2). enter a new value.
Values are displayed in feet/ minute. The new value can be entered: Clicking with the LB on the predefined value Entering the new value into the Edition field via keyboard or via provided numbered buttons. Afterwards it is required to accept it (by <Enter> key or by ENTER button). The action automatically updates the selected or entered value in the track label. At the same time, the window is closed and entered value is displayed in track label.
2.1.9.7 Action: SSR Code Assignment/ Modification to PSR Track

Application: Assign/ Modify an SSR Code to a PSR track. ACTION Click with the mouse LB on the Callsign/ SSR Code of the track (////) Select [ASSIGN CODE] Option. RESULT The Callsign Menu is displayed. This action enables the SSR Code Assignment field.
Page 2-84
DOCUMENT N: 0029200000000MA03
ACTION Enter the SSR Code in the Edition field. Clicking on the [ACCEPT] icon, the action is finished.
RESULT
or ACTION Select the track by pointing it with the mouse. Select the track and press <Alt> + key combination. This action displays the SSR Code Assignment Window again. RESULT
Enter the SSR Code in the Edition field. Clicking on the [ACCEPT] icon, the action is finished.
2.1.9.8 Action: Inter-Console Marker => <Alt> + 

Application: It allows displaying an additional cursor on another SDD by using the SDD own cursor to indicate to another controller the situation of an important element within the airspace. The controller initiating the action gets the cursor with the sector to which it is pointing and the controller receiving the action gets the cursor with the sector of the first controller.
ACTION RESULT
Press <Alt> + keys.
This action displays the Interconsole Marker.
There are two ways of entering the required sector:

DOCUMENT N: 0029200000000MA03
ACTION
RESULT
Enter the sector name via keyboard.
Click with the mouse RB on the SECTOR field. This action displays a menu with the available sectors to select one.
Select one by clicking on it.
The sector automatically gets into the field and the menu is closed.
The action finishes by: Clicking on the [ACCEPT] icon The System validates the action.
As shown in figure, the cursor turns into a YELLOW circle and the SDD position of the selected sector displays the new symbol, and the original sector name is also displayed for identify the origin.
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
Clicking on the [CANCEL] icon
The window is closed and it cancels the action.
2.2
SDD General Information Area
This area is always displayed on the SDD position, that is, no device can close it. It is located at the top of the screen, arranged in one line, and presents two kinds of items: icons and information boxes. Table 35: SDD General Information Area. Items ITEM TYPE DESCRIPTION
MSAW
Information Box Information Box Information Box Information Box
Display the MSAW Alert activation status. When this function is activated (in the CMD), all data are processed to verify the alert status in each track. Display the STCA Alert activation status. When this function is activated (in the CMD), all data are processed to verify the alert status in each track. Display the APW Alert activation status. When this function is activated (in the CMD), all data are processed to verify the alert status in each track. Display the MTCD Alert activation status. When this function is activated (in the CMD), all data are processed to verify the alert status in each track. Activate/Inhibit the PSR tracks manual creation function, if it is activated or inhibited the AUTO. PSR TRACK INITIATION switch in the CMD (see CMD Position User Manual). Display a pull-down menu including options of tracks and plots. Display a pull-down menu to select the operative mode (Integrated, By-pass or Mono-radar) as well as the tracker. Display a pull-down menu to select the radar. If being in BYP mode, the primary tracks are selected. Display a pull-down menu to select the presentation range. Activate/Inhibit the altitude filters for the SDD SIT Area. Display a pull-down menu to select the upper and lower altitude filters to be modified. Display a pull-down menu to select the colour of the plots belonging to a radar, only if the SDD is in Supervisor Mode. In another hand, this icon shows the mode of the SDD.
Page 2-87
STCA
APW
MTCD
PSR T
Icon
OPTIONS Operational Mode RADAR Presentation Range FALT Filter Limits
Icon Icon Icon Icon Icon Icon Information Box
ST
DOCUMENT N: 0029200000000MA03
ITEM Sectors
TYPE Information Box
DESCRIPTION Display the sectors assigned to the position.
EXP+ EXPCEN DCEN FPL MAP FCON QL SC QLOOK FILTER OFF MENU
Icon Icon Icon Icon Icon Icon Icon Icon Icon Icon Icon
Increase the presentation extension of the selected area. Decrease the presentation extension of the selected area. Centre the display. De-centre the display. Display a pull-down menu to perform actions on the FPs. Display a pull-down menu to select the maps to present on the SDD Position. Display a pull-down menu to select an already defined configuration. Display a pull-down menu to select the sectors used for the Quick-look function. Activate/inhibit the Quick-look function. Activate/inhibit the display of all current filters. Display/close the MM_A.
2.2.1 [ST] Icon

See Display of Plots.
2.2.2 Minimum Safe Altitude Warning [MSAW] Icon

The Minimum Safe Altitude Warning (MSAW) is defined in adaptation and it is activated/inhibited by the CMD (see CMD Position User Manual). When it is activated, the icon text colour is GREEN and, when it is inhibited, the icon text colour turns to YELLOW.
Figure 2-41: [MSAW] Icon
2.2.3 Short Term Conflict Alert [STCA] Icon

The Short Term Conflict Alert (STCA) is also defined in adaptation and it is activated/inhibited by the CMD (see CMD Position User Manual). When it is activated, the icon text colour is GREEN and, when it is inhibited, the icon text colour turns to YELLOW.
Figure 2-42: [STCA] Icon

DOCUMENT N: 0029200000000MA03
Two tracks in STCA can be in two conflict states: Prediction or Violation.
2.2.4 Area Proximity Warning [APW] Icon

The Area Proximity Warning (APW) is defined in adaptation and it is activated/inhibited by the CMD (see CMD Position User Manual). When it is activated, the icon text colour is GREEN and, when it is inhibited, the icon text colour turns to YELLOW.
Figure 2-43: [APW] Icon
2.2.5 Medium Term Conflict Detection [MTCD] Icon

The Medium Term Conflict Detection (MTCD) is defined in adaptation and it is activated/inhibited by the CMD (see CMD Position User Manual). When it is activated, the icon text colour is GREEN and, when it is inhibited, the icon text colour turns to YELLOW.
Figure 2-44: [MTCD] Icon
2.2.6 Primary Search Radar Tracks [PSR T] Icon

The [PSR T] icon allows the activation of the PSR tracks manual creation function. If the [AUTO. PSR TRACK INITIATION] function is activated in the CMD, the tracks creation is automatic, and otherwise the [PSR T] icon can be used to initiate the manual tracking by the SDP. (For more information, see CMD Position User Manual). When the PSR tracks manual creation function is activated causes the RDP to initiate the tracking of PSR plots falling in a system parameter size and during a system parameter time. Following colours represents the icon status: Inhibited. WHITE on GREY Activated. BLACK on LIGHT GREY
Figure 2-45: [PSR T] Icon
2.2.6.1 Action: Manual Creation of PSR Tracks => {[PSR T]}

Application: Perform this procedure to create manual PSR Tracks. With this action the system looks for a PSR track by clicking in a SDD SIT point, and it will only apply when the track is situated in a near point from selected one. ACTION RESULT Click on the [PSR T] button situated in the SDD General Information Area. The PSR manual creation function is activated. LB Click on a point in the SDD SIT Area.
DOCUMENT N: 0029200000000MA03
ACTION
RESULT It causes the SDP to initiate the tracking of PSR plots falling in a system parameter size area during a system parameter time.
2.2.7 [OPTIONS] Icon

When clicking on this icon, a pull-down menu is displayed to allow performing different actions on the tracks and plots. The options included in the pull-down menu are the following ones: HISTORY: Activate/inhibit the tracks past positions display. The activation status can be also selected by means of the key combination <Alt> + <H>. PSR PLOT: Activate/inhibit the primary plots display. PSR BYP: Activate/inhibit the primary tracks display. SSR PLOT: Activate/inhibit the secondary plots display. SSR BYP: Activate/inhibit the non-correlated secondary tracks display. CORR: Activate/inhibit the correlated secondary tracks display. FILLED: Activate/inhibit the display of under-control sectors in a different background colour. All the options are selected with the mouse RB. The selected option is displayed with a YELLOW mark (see next figure):
Figure 2-46 Options Pull-down Menu
2.2.7.1 Action: Activation/Inhibition of History Tracks => {[OPTIONS] [HISTORY]} or {<Alt> + <H>}
Application: Perform this procedure to activate/inhibit the display of the history tracks. ACTION RESULT Click on the [OPTIONS] switch situated in the Main Menu window.
->
A pull-down menu is displayed with the available options.

DOCUMENT N: 0029200000000MA03
ACTION
RESULT
Click on the [HISTORY] switch option. If it is inhibited A YELLOW mark is displayed to indicate the history tracks presentation activation. If it is activated The mark returns to background colour to indicate the history tracks presentation inhibition. NOTE: This action can be also performed with the <Alt> + <H> keys.
2.2.8 [Operational Mode] Icon

This icon is used to select the operational mode: INT (Integrated), MON (Mono-radar) or BYP (ByPass). The active tracker (defined in CMD) is displayed at Main Menu, and displayed at SDD. To select one of the operational modes, a pull-down menu is displayed when clicking on the icon. LB click in SFS icon will display a pop-down menu with operational modes, selected by LB clicking on it.
Figure 2-47: Operational Mode Menu (INT) Integrated Mode or Multiradar: The Position displays multiradar tracks processed by the SDP coming from all System radars, which are operative. Thus, the plot position is calculated taking into account the information sent by several radars.
DOCUMENT N: 0029200000000MA03
(MON) Monoradar Mode: The position displays the mono-radar tracks received from the SDP of radar selected by the controller from the radar sites defined by adaptation. (BYP) By-Pass Mode: The SDP does not process the received radar information. It comes directly from the RDCU system of the radar site selected to the SDD. The SDD position is the one in charge of the received information process, track creation, etc. The FDP information is still accessible but as the SDP is not a part of the process, all relation between the FDP and the SDP is cancelled. When every tracker is off, the SDDs display the following window and, at the same time, the picture is frozen.
Figure 2-48: Frozen Picture Display Following functions are not available when the mode of operation is BYP: Correlation of track with Flight Plan STCA Mode C Tracking Synthetic Tracks APW Prediction and Intrusion Hand-over Following table describes the different operational mode colours and their description. Table 36: Operational Mode. Colour Code Operational Mode Integrated (INT) Mono-radar (MON) By-Pass (BYP) By-Pass (BYP) Colour GREEN GREEN YELLOW PINK Description SDD in integrated (multi-radar) mode SDD in mono-radar mode SDP available SDP not available
2.2.8.1 Action: Operational Mode Selection => {[Operational Mode]}

Application: Perform this procedure to select the type of operational mode (INT, MON or BYP). ACTION RESULT When the SDP is running, click with the LB on the [Operational Mode] icon, which is in Integrated Mode (INT) by default. A pull-down menu containing the INT, MON and BYP operational modes is displayed.
When the SDP is not running

DOCUMENT N: 0029200000000MA03
ACTION
RESULT The icon always displays the BYP (By-pass mode) by default.
Select the desired operational mode. The [Operational Mode] icon displays the activated mode.
2.2.9 Radar Source [RADAR] Icon

This icon displays the selected current radar for the following purposes: When being in INT mode, for plot display. When being in MON mode, maximum of 3 active radars, selected in adaptation, are displayed, so now up to three radars can be selected. When being in By-Pass mode, for mono-radar processing. The radar is selected by means of a pull-down menu situated in the General Information Area.
Figure 2-49: Radar Source Pull-down Menu
2.2.9.1 Action: Select Radar Source => {[RADAR]}

Application: Perform this procedure to select the radar for being displayed when the SDD is in Bypass mode as well as for visualize the non-associated plots when the SDD is in Integrated mode and the controller has requested its visualization. ACTION RESULT LB click on the [RADAR] icon of the SDD General Information Area
A pull-down menu containing the radar names list is displayed.
Select the desired radar by clicking on it. The pull-down menu is automatically closed and the selected radar is displayed on the icon text.
2.2.10 [Presentation Range] Icon

This icon displays the current selected range in NM.
DOCUMENT N: 0029200000000MA03
By clicking with the LB on the icon, a pull-down menu displays the possible ranges to select the required one. Once the radar is selected, the pull-down menu is automatically closed. The current selected range is displayed on the pull-down menu with a YELLOW mark on the left. The available ranges are defined by adaptation. And the current range display is displayed permanently in General Information Area in format: RANGE: XXX NM
Figure 2-50: Presentation Range Pull-down Menu
2.2.10.1 Action: Presentation Range Selection => {[Presentation Range]}

Application: Perform this procedure to select the range of the information to be displayed on the SDD SIT Area. ACTION RESULT LB Click on the [Presentation Range] icon of the General Information Area. A pull-down menu with the available ranges is displayed.
Finish the action by: Selecting the desired value. The new range is displayed on the icon and the pull-down menu is automatically closed. LB click anywhere outside the pull-down menu. The pull-down menu is closed without making any change.
Page 2-94
DOCUMENT N: 0029200000000MA03
2.2.11 Altitude Filters Activation/ Inhibition [FALT] Icon

The [FALT] icon allows the activation/inhibition of the altitude filter for the SDD SIT Area. Its activation status is shown by the icon text colour: YELLOW if it is activated, and WHITE if inhibited.
Figure 2-51: [FALT] Icon Colour Status When clicking on this icon, the values previously selected in the Filter Limits window are activated. That is, the filter limits are displayed on the [Altitude Limits] icon.
2.2.11.1 Action: Activate/ Inhibit the Altitude Filter

Application: Active or de-active the defined altitude filters.
ACTION RESULT
Click with the LB on the [FALT] icon (or in the Auxiliary Window). If it is inhibited The text colour and the altitude filter values of the GI_A change to BLACK on LIGHT GREY (activated action).
If it is activated
The colour of the icon text changes to WHITE and the background colour is GREY (inhibited action).
2.2.11.2 Filters Limits Window

The edition of a new altitude filter, both lower and upper, is performed in the corresponding Filters Limits window. There is a window for each limit (lower and upper). The new value selection is not displayed on the icon until the [FALT] icon is activated. Clicking on the icon and selecting from one of the two options included in the pull-down menu display the corresponding window (see previous figure). The windows cannot be displayed at a time.
Page 2-95
DOCUMENT N: 0029200000000MA03
Figure 2-52: Filter Limits Windows It is composed of the following items: Vertical Scroll Bar To display the pre-determined values which are not in view due to window size. It is possible to select a value, by clicking twice on it. Edition Field It allows the edition of a value by using the keyboard. Keyboard arrows allow the selection of the suitable value. Press enter to accept these actions.
2.2.11.3 Action: Height Filter Limits Selection => {[Filter Limits]}

Application: Perform this procedure to select the Height Filter Limits. ACTION RESULT Click with the mouse LB on one of the [Limit Filter] icons to edit a new altitude filter. There are two icons: lower and upper. The icons purpose is: Display the altitude range in hundreds of feet when activating the altitude filter.
Enter the value for the altitude filter (lower/upper) by means of a menu. A pull-down menu containing the upper and/or lower limits is displayed. Depending on the selection, the Filter Limits window (upper or lower) containing predefined values is displayed. A scroll bar allows the display of those values not in view.
Page 2-96
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
Selection of value may be performed either: By clicking on the desired value. By entering the data, in the Edition field, with the keyboard. In both cases, the window is automatically closed when the value selection is performed. CB Click on the window edition field. The window is closed and the action is aborted. NOTE: The entered values are not displayed on the icon and they are not activated until the [FALT] button is depressing.
2.2.11.4 Action: Activate/ Inhibit Altitude Filters => {[FALT]}

Application: Perform this procedure to activate/inhibit the altitude filter status. ACTION RESULT Depress the [FALT] button at the General Information Area. (or in Aux. Window) If it is inhibited. The icon text/ background colour turns to BLACK/ GREY and the action is activated. If it is activated. The icon text/ background colour turns to WHITE/ BLACK and the action is aborted.
NOTE: Once the icon is activated, the height filter limits selection is displayed on its corresponding icon.
Page 2-97
DOCUMENT N: 0029200000000MA03
2.2.12 Sectors Display

It displays the sectors assigned to the position. Figure 2-53: Sector Information Box Also, clicking on the [SECTORS] icon in the Main Menu a window is displayed with all the sectorization.
2.2.12.1 Action: Sectors Display

Application: When controlled sectors can not be totally displayed in Sector Information Box because of their length exceeds the maximum size of this box, the [ ] indication is included in the box. The complete sectorization can be displayed with the following action procedure. ACTION RESULT Check the Sector Information Box includes the symbol [ ], which means the complete SDD sectorization can not be displayed in this box. Click in any point in the Sector Information Box. The extended box is displayed, with the complete controlled sectors list. Click again in any point in the Sector Information Box. The Sector Information Box returns to its start form.
2.2.13 Interactive Expansion Scale [EXP+] Icon

This icon is used to activate the expansion function to expand an area of the SDD SIT Area once the new position centre is determined.
Figure 2-54: [EXP+] Expansion Icon It is also possible to activate/inhibit the Expansion function by pressing the <F9> key.
2.2.13.1 Action: Interactive Expansion => {[EXP+]}

Application: Perform this procedure to increase the presentation range of the SDD SIT Area. ACTION RESULT There are two ways of expanding the screen presentation. By means of the mouse device:
DOCUMENT N: 0029200000000MA03
ACTION LB Click on the [EXP+] icon of the General Information Area.
RESULT
The expansion function is activated. LB Click on the geographic point to be expanded. The mouse cursor becomes a YELLOW cross to identify the procedure.
Without releasing the mouse pointer, enlarge the geographical area to be expanded. A YELLOW area (box) is displayed.
Release the mouse pointer to finish the action by LB clicking The selected area is expanded.. If CB Clicking while performing the action. The action in process is cancelled. By means of keyboard device: By pressing on the <F9> key. Activate/inhibit the expansion procedure (step 1.1)
2.2.14 Interactive Contraction Scale [EXP-] Icon

This icon is used to activate the contraction function to contract an area of the SDD SIT Area once the new position centre is determined.
Figure 2-55: [EXP-] Expansion Icon

DOCUMENT N: 0029200000000MA03
It is also possible to activate/inhibit the Contraction function by pressing the <F10> key.
2.2.14.1 Action: Interactive Contraction: {[EXP-]} or {<F10>}

Application: Perform this procedure to decrease the presentation range of the SDD SIT Area. ACTION RESULT There are two ways of expanding the screen presentation. By means of the mouse device: LB Click on the [EXP-] icon of the General Information Area. The contraction function is activated. LB Click on the geographic point to be contracted. The mouse cursor becomes a YELLOW cross to identify the procedure.
Without releasing the mouse pointer, size the geographical area to be contracted. A YELLOW area (box) is displayed.
Release the mouse pointer to finish the action by LB clicking. The selected area is contracted. If CB clicking while performing the action. The action in process is cancelled. By means of keyboard device: By pressing on the <F10> key
DOCUMENT N: 0029200000000MA03
ACTION
RESULT Activate/inhibit the expansion procedure (step 1.1)
2.2.15 Centring [CEN] Icon

This icon performs a return of the SDD SIT Area to geographical centre determined by the system.
Figure 2-56: Centring [CEN] Icon
2.2.15.1 Action: Presentation Centring => {[CEN]}

Application: Perform this procedure to centre the SDD SIT Area display. ACTION RESULT LB Click on the [CEN] icon of the General Information Area The SDD SIT Area returns to its geographical centre.
2.2.16 De-Centring [DCEN] Icon

This icon performs the change of current SIT Area centre display to another point.
Figure 2-57: Centring [DCEN] Icon
2.2.16.1 Action: Presentation De-Centring => {[DCEN]}

Application: Perform this procedure to de-centre the SDD SIT Area display. ACTION RESULT LB Click on the [DCEN] icon of the General Information Area The SDD SIT Area changes its display centre.
2.2.17 Flight Plan [FPL] Icon

When clicking on the [FPL] icon, situated in the SDD General Information Area, a pull-down menu is displayed. This pull-down menu allows the controller to select the type of FP-operation to be performed.
Page 2-101
DOCUMENT N: 0029200000000MA03
Figure 2-58: Flight Plan Pop-up Menu As the procedures are triggered from four options displayed at the [FLP] icon, the section is divided into four subsections where available FPLs actions from each icon are described. Following table lists the FPLs actions associated to each option, as well as the window associated to the option.
Table 37: FP Operation Windows. Functions Option Operational Window View FPL FPL History Create FPL Create Current FPL Modify FPL Terminate FPL FP ACTION Notify FPL FP Operation window (in action Cancel Notify FPL mode and Creation Mode) Confirm/Modify ATD Cancel ATD Input FP Estimates Position Reports Confirm ATA Cancel ATA Strips printing FP RETRIEVE CONFLICT FPs Retrieval window FP Conflicts Retrieve FPL FPL in Conflict FP Action
2.2.17.1 FP Operation Window

The FP Operation Window in action mode consists of a form including fields to be filled in by the operator (edition area), a command area at the bottom of the window and an error message area.
Page 2-102
DOCUMENT N: 0029200000000MA03
This window allows choosing different actions or just information displays (View and Hist.) for an existing FP or creation of a non-existing FP, upon selection of the corresponding command. Editable fields depend on the selected command/action.
Figure 2-59: Flight Plan Operation Window
Field Flight ID Radio Callsign NO A/C TYPE
Table 2.2.17.1-1: FP Operation Window. Edition Area Description Valid Data Aircraft Identification or ACID Phonetic Airline Operator Number of Aircrafts Type of Aircraft 2 to 7 alphanumeric characters Up to 20 characteres. Non-editable field. Defined in DBM. Up to 2 numerical characters (1-99) 2 to 4 alphanumeric characters. The first one shall be an alphabetic character. It shall be known by the system. L= M= H= J= light medium heavy super-heavy
Type of wake turbulence
DEP
Departure Aerodrome
Four alphabetic characters. If unknown, then enter the ZZZZ keyword. If created while aircraft is airborne, then enter the AFIL keyword.
DEST NAV/ COM
Destination Aerodrome Navigational/ Communications Equipment
Four alphabetic characters. Up to 20 alphabetical characters N= S= Non-equipped Equipped

Page 2-103
DOCUMENT N: 0029200000000MA03
A= C= D= E= H= I= L= M= O= P= R= T= U= V= W= Y= RVSM RVSM Capability Status EQ = equipped
LORAN A LORAN C DME Decca HF RTF Inertial Navigation ILS Omega VOR Doppler RNAV TACAN UHF RTF VHF RTF RVSM Frequency 8.33 Mz
NO = non-equipped (for civil flights) UN = unknown EX = exempted (for military flights) SURVEILLANCE SSR Equipment. EQUIPMENT Up to 20 alphabetical characters N=> None. (The aircraft transponder equipment). do not carry
It is not allowed this value if an SSR Code is assigned. A=> Mode A (Transponder equipment can send positional information but without altitude information) C=> Mode C (Transponder equipment can send both positional and altitude information) X=> Mode S (nor aircraft identification transmission neither pressure altitude information) P=> Mode S (Transponder equipment can send pressure altitude transmission but it cannot sent aircraft identification transmission) I=> Mode C (Transponder can send aircraft identification transmission but it cannot send pressure altitude transmission)
DOCUMENT N: 0029200000000MA03
S=> Mode S (Transponder can send both aircraft identification and pressure altitude transmission) Blank = C CSSR ICAO SSR Code 4 numerical characters (octal) Blank = It allows the FDP to automatically assign an SSR Code R Flight Rules I= V= Y= Z= FT Flight Type S= N= G= M= X= SID FIR ROUTE Standard Instrumental Departure Procedure FP route IFR VFR IFR followed by VFR VFR followed by IFR scheduled non-scheduled general aviation military other
Blank = I
Blank = other Alphanumeric characters (2 to 7). Must be a known SID. Up to 480 characters. See following NOTE Validation Rules. STAR EOBD EOBT MSG Standard Terminal Route Procedure Arrival on Route Field
Alphanumeric characters (2 to 7). Must be a known STAR. YYMMDD (00 to 99 and 01 to 12 and 01 to 31) date of departure. HHMM (00 to 23 and 00 to 59) AFTN message; e.g.: FPL, DLA, CHG, If the FPL only has the first AFTN message(the FPL message), on the field appear FPL HHMM (00 to 23 and 00 to 59) Updated with message. the last received CFMU
Estimated Off-Block Date Estimated Off-Block Time Last AFTN Message Received
CTOT
Calculated Take-Off Time
ATFMC ATD
Last CFMU Message
Received
Type of the last received CFMU message; e.g.: SAM, SRM, SLC, FLS, DES, HHMM (00 to 23 and 00 to 59)
Actual Time of Departure
Page 2-105
DOCUMENT N: 0029200000000MA03
EET/ ETA
Estimated Elapsed Time Estimated Time of Arrival
HHMM (00 to 23 and 00 to 59)
CRUISING SPEED
Cruise Speed
Kxxxx: 4 numerical characters (Km/h) Nxxxx: 4 numerical characters (Knots) Mxxx: 3 numerical characters (Mach number)
CRUISING LEVEL
Requested Flight Level
Flight level (hundreds of feet): Fxxx where xxx 000 to 999. Altitude (hundreds of feet): Axxx where xxx 000 to 999. Level (tents of meters): Sxxxx where xxxx 0000 to 9999. Altitude (tents of meters): Mxxxx where xxxx 0000 to 9999.
ESTIMATE FIX ESTIMATE TIME ESTIMATE LEVEL Pos SPEED
Estimate Fix Point Estimated time significant point Cleared Flight Level over a
Up to five alphabetic characters. It shall be known by the system. HHMM (00 to 23 and 00 to 59) 3 digits (hundreds of feet) Indicated Speed on the Position Report Next Fixpoint to overfly indicated on the Position Report Indicated time to overfly the fixpoint on the Position Report 9 alphanumeric characters: Airport(Space)Airport (Each airport 4 characters)
Report Speed Fixpoint Estimated Time Overfly Alternate Airports
Pos Report FIX Pos Report ETO ALT AD(S)
FIELD 18 FREE TEXT
Additional information Notes
Defined Field from ICAO Free text This Free text is visible from the lists on the SDDs
CFL
Clearance Flight Level
Clearence Flight Level Flight level (hundreds of feet): Fxxx where xxx 000 to 999.
ECL
Requested Level
En-Route Cruise Level Flight level (hundreds of feet): Fxxx where xxx 000 to 999.
S
Strip
2 alphanumeric (number of the sector to print

Page 2-106
DOCUMENT N: 0029200000000MA03
the strip, only applicable on the SDD position) REG STS MODE S ORIGINAL ROUTE Aircraft Register Status Aircraft Identification Original Route from Field 15 8 alphanumeric characters 20 alphanumeric characters 6 hexadecimals characters (0-9, A-F) Up to 480 characters.
2.2.17.1.1.1
Flight Plan Status
Depending on the actions performed on a Flight Plan and the System current time, the Flight plan may assume following statuses: Initial Its the default status, when the flight plan is not in any of the other status. Departure Flight Plan is in the period of time defined in VSP Time before of EOBT display a CLD. Flight Plan entering the FIR but it is not under center control yet. RPL (Repetitive Flight Plan) just converted into Flight Plan. Pending Initial internal departures flight plans are transitioned to Pending fight plans VSP time before the ETD. Notified Departure Flight Plan being its EOBT 20 minutes (configurable parameter) sooner than the current time. Departure Flight Plan on which a Notification action has been performed. A Notified FP has SSR assigned and SID procedure, if there is one. Active Flight Plan coming from other sector but still it is not under control of the position with that sector. Departure Flight Plan on which an ATD action has been performed. Flight Plan on which an EST (estimate) has been performed. Terminated Arrival Flight Plan, which has exceeded the ATA or ETA. Arrival Flight Plan, which has exceeded the exit time from the FIR. Flight Plan on which a Cancellation action has been performed. If a Flight Plan is Terminated, it is stored in the FDP and it is deleted from the Flight Plan Lists. The FP SSR Code gets free and another FP can use it. No action can be performed on it, except retrieval, visualization, history display or copy.
Page 2-107
DOCUMENT N: 0029200000000MA03
2.2.17.1.1.2
Rules for Entering Data
Dark GREY fields do not allow data to be input or changed. Fields displayed on WHITE allow data entering or changing. Fields displayed on RED have erroneous data or are mandatory and have not been filled in.
Figure 2-60: FP Operation Window (Modification Mode): Error Detection If the field exceeds the maximum number of allowed characters, the cursor goes to the first character position in next field. If there are different errors when editing a FP, the message displayed on the Error Area corresponds to the first field with error. Some fields allow knowing the data valid format within the FP Operation Window: For several fields, mouse LB clicking on the field name, performs a toggle between the field name and the valid format.
Figure 2-61: FP Operation Window: Valid data input help
2.2.17.1.1.2.1
Route Field Validation Rules
When editing the Route field in the FP Operation Window follow these requirements: A single space separates elements. Elements consists of more than (1) character but less than (30). The Route field allows up to forty (40) elements. Only digits cannot compose elements. If only alphabetical characters form elements, the maximum longitude is 2 to 7 characters. Points can be fixpoint or LAT_LON coordinated. Elements can consist on alphanumerical characters, vertical slash and asterisks (*).
DOCUMENT N: 0029200000000MA03
It is possible to add estimates of time on a reporting point with character /H. Example: [FIX1 FIX2/H1230 FIX3] For incoming flights, the first route point must be FIR external and the following ones must be internal. At least one route fixpoint must include a time estimate so the System can calculate the entry time. Example: [P_EXT P_INT/H1450 P_INT DCT ] First route characters will be automatically fulfilled with ** for incoming flights. For exiting flights, the last route point must be external to the FIR and the previous ones must be internal. Example: [P_INT P_INT P_EXT] Last route characters will be automatically fulfilled with ** for exiting flights. For transit flights, the first and last route point must be external to the FIR and the rest must be internal. At least one route point must include a time estimate so the System can calculate the entry time. Example: [P_EXT/H2015 F_INT F_INT F_INT F_EXT] First and last route characters will be automatically fulfilled with ** for transit flights. DCT (direct): Keyword that is entered between 2 fixpoints to avoid discontinuity. This situation when the 2 fixpoints do not belong to the same route or when, at least, one of them is a LAT_LON coordinate. A route cannot consist of a single element, unless it is DCT keyword. If this is the case, DEP and DEST must be known and at least one of them must be in the local IFR. Routes must be continuous. The following types of routes are continuous: Route starting with a Departure Aerodrome, which is inside the FIR and its first element, is the DCT keyword, a transition point on the STAR or an airway that includes a transition point on the STAR. Route made up of two geographic points. Route made up of a FIX and a geographic point (or a geographic point and a FIX) separated by DCT. Route made up of two FIXES connected by DCT, two FIXES connected by an airway, or two FIXES connected by more than one airway. Route made up of several airways as long as there is a single crossing point for the two airways. Modifications in route elements, which have already been over-flown, are not allowed as they cause a route error. An element not complying with the above rules will cause a syntax error. When the Route field is erroneous, it presents a new window over the FP Operation Window showing the following information: R: It is the route entered by the controller. C: It is the route calculated by the system. It marks the point where the error is. S: It is a Standard Route. Only when there is a standard route defined in the DBM.
Page 2-109
DOCUMENT N: 0029200000000MA03
The route field checks the restricted area intrusion, and displays a window when this event is produced.
Figure 2-62: Area Warning Window
2.2.17.1.2
FPLs Actions
This section gathers the procedures triggered from the [FP Act.] icon of the Main Menu Area of the FDD screen. Actions in FPLs can be performed by FP Operation Window, which can be displayed by: RB click in Track Symbol (the template includes the selected track data). LB click in Track Symbol/ LB click in the first field of a FP in any flight list, and then click in FP Action (the template includes the selected track data). LB click in [FPL] in General Information Area, and then click in FP Action (the template is displayed empty). LB click in FPL EDIT option in Callsign Menu (when the option is available) (the template includes the selected track data). From this point on, the actions are described according to the operations performed by the command switches. Each command will have compulsory fields and accessible fields. Compulsory fields are always accessible. If there are not explicit accessible fields, only the compulsory ones can be modified.
2.2.17.1.3
Action: Visualize FPL => {[FP Act.] => [View]}
Application: Display the data of a Flight Plan for visualization. NOTE: This action is also used as a starting step to perform any FPL action available from the FP Operation window (action mode). That is, when performing any action, it is necessary to display the corresponding FP in order to carry out the operational function. ACTION RESULT Click on the [View] switch, situated at the bottom of the window, with LB. The switch changes to YELLOW.
Page 2-110
DOCUMENT N: 0029200000000MA03
ACTION Enter data on the corresponding fields (Call Sign field is mandatory) to retrieve the FP. Finish the action by clicking on one of the following icons: [UPDATE] icon
RESULT
If entered data are correct, the FP Operation window (action mode) displays the FP matching the entered data. All fields are inaccessible. If entered data are erroneous, an error message is displayed. If mandatory fields are not filled in, an error message is displayed. [CANCEL] icon The FP Operation window (action mode) is closed. The action is aborted, if it has not been previously validated ([UPDATE] icon). [CLEAR] icon The displayed data is deleted from the FP Operation window (action mode). [PRINT] Icon Print the historical information of a FP. Compulsory Fields: FLIGHT ID
2.2.17.1.4
Action: FPL History => {[FP Act.] => [Hist.]}
Application: Request the history of an existing FPL. The system displays a report containing the information of the FPL and all actions performed on it. Even for Terminated flight plan, History can be retrieved. ACTION RESULT Perform the FP visualization action Click on the [Hist.] switch, situated at the bottom of the window, with LB. The switch becomes YELLOW, and the FP History window is displayed including all actions performed in the FP. The FP Operation window (action mode) automatically changes to View mode ([View] switch activated) and all fields are inaccessible.
Page 2-111
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
Finish the action by clicking on one of the following icons: [UPDATE] icon The FP History window is closed while the FP Operation window remains displayed. [CANCEL] icon The FP Operation window (action mode) is closed. [CLEAR] icon The FP History window is closed while the FP Operation window (action mode) remains displayed. All data included in the FP Operation window (action mode) are deleted and the window automatically changes to View mode ([View] switch activated). [PRINT] Icon Print the historical information of a FP. Compulsory Fields: FLIGHT ID. Only if the FP visualization action has not been previously performed.
2.2.17.1.5
Action: Create FPL => {[FP Act.] => [CREATE]}
Application: Use this function to create a new Flight Plan. The flight plan will be stored in the system FP database and it is created in active status. ACTION RESULT Click on the [CREATE] switch situated at the bottom of the window, with the LB. The switch changes to YELLOW.
Page 2-112
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
Enter data in the corresponding fields.
Finish the action by clicking on one of the following icons. [UPDATE] icon The system process. triggers the data validation
If entered data are correct, the flight plan is added to the FPL database and the FP Operation window remains displayed. If entered data are erroneous, an error message is displayed. If mandatory fields are not filled in, an error message is displayed. [CANCEL] icon The FP Operation window (creation mode) is closed. The action is aborted, if it has not been previously validated ([UPDATE] icon). [CLEAR] icon The displayed data are deleted from the FP Operation window (creation mode). [PRINT] Icon Print the historical information of a FP. Compulsory Fields: FLIGHT ID, A/C TYPE, DEP, DEST, FIR ROUTE, EOBT, CRUISING SPEED, CRUISING LEVEL..
Page 2-113
DOCUMENT N: 0029200000000MA03
2.2.17.1.6 Action: Create a Current FPL => {[FP Act.] => [CREATE CURRENT]}
Application: Use this function to create a flight plan for an aircraft that is already flying. This action creates the FP in live status. ACTION RESULT Click on the [CREATE CURRENT] switch, situated at the bottom of the window, with LB. The switch changes to YELLOW. Enter data in the corresponding fields.
Finish the action by clicking on one of the following icons: [UPDATE] icon The system process. triggers the data validation
If entered data are correct, the flight plan is added to the FPL database and the FP Operation window (action mode) remains displayed. If entered data are erroneous, an error message is displayed. If mandatory fields are not filled in, an error message is displayed. [CANCEL] icon The FP Operation window (action mode) is closed. The action is aborted, if it has not been previously validated ([UPDATE] icon). [CLEAR] icon The displayed data are deleted from the FP Operation window (action mode). [PRINT] Icon Print the historical information of a FP. Compulsory Fields: FLIGHT ID, A/C TYPE, DEP, DEST, FIR ROUTE, EOBT, CRUISING SPEED, CRUISING LEVEL, ESTIMATE FIX, ESTIMATE TIME, ESTIMATE LEVEL.
DOCUMENT N: 0029200000000MA03
2.2.17.1.7
Action: Modify FPL => {[FP Act.] => [Modify]}
Application: Modify an existing Flight Plan. Once it is modified, the Flight Plan is permanently changed. ACTION RESULT Perform the FP visualization action Click on the [Modify] switch, situated at the bottom of the window, with LB. The switch changes to YELLOW and the accessible fields for the action are displayed in WHITE background.
Modify the desired fields. Some fields do not allow modification and some other are mandatory. Finish the action by clicking on one of the following icons: [UPDATE] icon The modification process is triggered. If entered data are correct, The FP Operation window (action mode) is displayed in View mode ([View] switch activated). All fields are displayed inaccessible.
If entered data are erroneous, an error message is displayed. If mandatory fields are not filled in, an error message is displayed.
[CANCEL] icon The FP Operation window (action mode) is closed. The action is aborted, if it has not been previously validated ([UPDATE] icon). [CLEAR] icon The displayed data is deleted from the FP Operation window (action mode) and the [View] switch is automatically activated.
DOCUMENT N: 0029200000000MA03
ACTION [PRINT] Icon
RESULT Print the historical information of a FP.
Compulsory Fields:
FLIGHT ID, A/C TYPE, DEP, DEST, FIR ROUTE, EOBT, CRUISING SPEED, CRUISING LEVEL. Only if the visualization action has not been previously performed.
2.2.17.1.8
Action: Cancel FPL => {[FP Act.] => [TERM]}
Application: Terminate an existing Flight Plan. Once the Flight Plan is cancelled, no actions can be performed on it except the retrieve and history actions. ACTION Perform the FP visualization action Click on the [TERM] switch, situated at the bottom of the window, with LB. The switch changes to YELLOW and the accessible fields for the action are displayed in WHITE background. RESULT
Finish the action by clicking on one of the following icons: [UPDATE] icon The FP termination process is triggered. If entered data are correct, the FP Operation window is displayed in view mode ([View] switch activated). The system transits the FP to terminated status. All fields are inaccessible. If entered data are erroneous, an error message is displayed. [CANCEL] icon The FP Operation window (action mode) is closed and the action is aborted, if it has not been previously validated ([UPDATE] icon). [CLEAR] icon
Page 2-116
DOCUMENT N: 0029200000000MA03
ACTION
RESULT All data included in the FP Operation window (action mode) are deleted and the window automatically changes to View mode ([View] switch activated).
[PRINT] Icon Print the historical information of a FP. Compulsory Fields: FLIGHT ID, DEP, DEST, EOBT. Only if the FP visualization action has not been previously performed.
2.2.17.1.9
ACTION
Action: Confirm/ Modify ETD => {[FP Act.] => [NOTIF]}

RESULT
Application: Confirm or modify the estimated time of departure. Perform the FP visualization action Click on the [NOTIF] switch, situated at the bottom of the window, with LB.
The switch changes to YELLOW and the accessible fields for the action are displayed in WHITE background. A BLUE frame is displayed around the ETD field. Confirm or modify the data presented in the ETD field. Finish the action by clicking on one of the following icons: [UPDATE] icon The validation process is triggered. If entered data are correct, The FP Operation window (Action mode) is displayed in View mode ([View] switch activated. All fields are displayed inaccessible.
Page 2-117
DOCUMENT N: 0029200000000MA03
ACTION [CANCEL] icon
RESULT The FP Operation window (action mode) is closed and the action is aborted, if it has not been previously validated ([UPDATE] icon).
[CLEAR] icon All data included in the FP Operation window (action mode) are deleted and the window automatically changes to View mode ([View] switch activated). [PRINT] Icon Print the historical information of a FP. Compulsory Fields: Note: FLIGHT ID, DEP, DEST, EOBT. Only if the visualization action has not been previously performed. This action is allowed once. For re-performing the ETD action, the operator shall perform a cancel ETD (C.NOTIF) action. The ETD action is not allowed when previously performed an ATD action.
2.2.17.1.10
Action: Cancel ETD => {[FP ACTION] => [C.NOTIF]}
Application: Cancel a previous ETD action. That is, the flight plans turns to passive status (if the entered hour with respect to the current one is lower than a defined parameter). ACTION RESULT Perform the FP visualization action Click on the [C.NOTIF] switch, situated at the bottom of the window, with LB. The switch changes to YELLOW and the accessible fields for the action are displayed in WHITE background.
Finish the action by clicking on one of the following icons: [UPDATE] icon The ETD cancellation process is triggered if the ETD action was previously performed. The FP Operation window (action mode) is displayed in View mode ([View] switch
DOCUMENT N: 0029200000000MA03
ACTION [CANCEL] icon
RESULT activated). All fields are displayed inaccessible. The FP Operation window (action mode) is closed and the action is aborted, if it has not been previously validated ([UPDATE] icon).
[CLEAR] icon All data included in the FP Operation window (action mode) are deleted and the window automatically changes to View mode ([View] switch activated). [PRINT] Icon Print the historical information of a FP. Compulsory Fields: Note: FLIGHT ID, DEP, DEST, EOBT. Only if the visualization action has not been previously performed. This action can be performed when an ETD action was previously performed.
2.2.17.1.11
Action: Confirm/ Modify ATD => {[FP Act.] => [ATD]}
Application: Mark a flight plan as having taken off and allow the operator to change or confirm the ATD proposed by the system. ACTION RESULT Perform the FP visualization action. Click on the [ATD] switch, situated at the bottom of the window, with LB. The switch changes to YELLOW and the accessible fields for the action are displayed in WHITE background. A BLUE frame is displayed around the ETD field.
Confirm or modify the data displayed on the CSSR field.
Page 2-119
DOCUMENT N: 0029200000000MA03
ACTION Finish the action by clicking on one of the following icons: [UPDATE] icon
RESULT
The validation process is triggered. If entered data are correct, the FP Operation window (action mode) is displayed in View mode ([View] switch activated. All fields are displayed inaccessible.
[CANCEL] icon The FP Operation window (action mode) is closed and the action is aborted, if it has not been previously validated ([UPDATE] icon). [CLEAR] icon All data included in the FP Operation window (action mode) are deleted and the window automatically changes to View mode ([View] switch activated). [PRINT] Icon Print the historical information of a FP. Compulsory Fields: Note: FLIGHT ID, DEP, DEST, EOBT, ATD. Only if the visualization action has not been previously performed. This action can be performed once. To perform it again, the operator must previously execute a C. ATD action. Once the ATD action is performed, the ATD action cannot be executed.
2.2.17.1.12
Action: Cancel ATD => {[FP Act.] => [C.ATD]}
Application: Cancel a previous ATD action. That is, the flight plan turns to active. This is only allowed if a departure message was previously input.
DOCUMENT N: 0029200000000MA03
ACTION Perform the FP visualization action Click on the [C. ATD] switch, situated at the bottom of the window, with LB.
RESULT
The switch changes to YELLOW and the accessible fields for the action are displayed in WHITE background.
Finish the action by clicking on one of the following icons: [UPDATE] icon The ATD cancellation process is triggered if a previous ATD action was performed. The FP Operation window (action mode) is displayed in View mode ([View] switch activated. All fields are displayed inaccessible. If an ATD action was not previously performed, the system sends an error message. [CANCEL] icon The FP Operation window (action mode) is closed and the action is aborted, if it has not been previously validated ([UPDATE] icon). [CLEAR] icon All data included in the FP Operation window (action mode) are deleted and the window automatically changes to View mode ([View] switch activated). [PRINT] Icon Print the historical information of a FP. Compulsory Fields: Note: FLIGHT ID, DEP, DEST, EOBT. Only if the visualization action has not been previously performed. This action can be performed only if a previous ATD action was executed.
2.2.17.1.13
Action: Estimate Actions => {[FP Act.] => [EST]}
Application: Perform estimate actions on a future reporting point of the flight plan route.
DOCUMENT N: 0029200000000MA03
ACTION Perform the FP visualization action Click on the [EST] switch, situated at the bottom of the window, with LB.
RESULT
The switch changes to YELLOW. The accessible fields for the action are displayed on a WHITE background and a BLUE frame rounds the ETO field. The window displays on the Fix Point, ETO and CFL fields the data calculated by the system for the next route point to be overflown.
Enter the future point (FixPoint field) of the flight plan route, if not displayed, and confirm or modify the values for the ETO and CFL fields. The Fix Point and CFL fields are mandatory. The ETO field, although accessible, is not mandatory due to the system automatically calculation. Finish the action by clicking on one of the following icons: [UPDATE] icon The system validates the estimates and calculates the ETO, if not entered. If entered data are correct, the FP Operation window (action mode) is displayed in View mode ([View] switch activated. All fields are displayed inaccessible.
[CANCEL] icon The FP Operation window (action mode) is closed and the action is aborted, if it has not been previously validated ([UPDATE] icon). [CLEAR] icon
DOCUMENT N: 0029200000000MA03
ACTION
RESULT All data included in the FP Operation window (action mode) are deleted and the window automatically changes to View mode ([View] switch activated).
[PRINT] Icon Print the historical information of a FP. Compulsory Fields: ESTIMATE FIX, ESTIMATE LEVEL. Only if the visualization action has not been previously performed.
2.2.17.1.14
Action: Passing over Fixpoint => {[FP Act.] => [POS]}

ACTION RESULT
Perform the FP visualization action. Click on the [POS] switch with the LB. The switch becomes YELLOW. The accessible fields for the action are WHITE background.
Enter the information concerning the last overflown fixpoint FIXPOINT and the time of that event ETO as well as the next route fixpoint NEXT FIX and the estimated time for the FP to overfly that fixpoint N.ETO. Click with the LB on the [OK] icon. To avoid receiving the PO alert in the track label, send the position report. Finish the action clicking in CLOSE icon. Compulsory Fields: FLIGHT ID, DEP, EOBT, DEST, ESTIMATE FIX, ETO, ESTIMATE LEVEL.
2.2.17.1.15
Action: Confirm/ Modify ATA => {[FP Act.] => [ATA]}
Application: Report to the system on the actual time of arrival (ATA) of the FPL. ACTION RESULT Perform the FP visualization action.
DOCUMENT N: 0029200000000MA03
ACTION Click on the [ATA] switch, situated at the bottom of the window, with LB.
RESULT
The switch changes to YELLOW and the accessible fields for the action are displayed in WHITE background. A BLUE frame is displayed around the ETA field.
Confirm or modify the estimated time of arrival in the ETA field. Finish the action by clicking on one of the following icons: [UPDATE] icon The validation process is triggered. If entered data are correct, the FP Operation window (action mode) is displayed in View mode ([View] switch activated). The system takes the value input in step 3 as the actual time of arrival. All fields are inaccessible.
[CANCEL] icon The FP Operation window (action mode) is closed and the action is aborted, if it has not been previously validated ([UPDATE] icon). [CLEAR] icon All data included in the FP Operation window (action mode) are deleted and the window automatically changes to View mode ([View] switch activated). [PRINT] icon Print the historical information of a FP.
Page 2-124
DOCUMENT N: 0029200000000MA03
Compulsory Fields:
FLIGHT ID, DEP, DEST, EOBT, ETA. Only if the visualization action has not been previously performed.
2.2.17.1.16
Action: Cancel ATA => {[FP ACTION] => [C.ATA]}
Application: Cancel a previous ATA action. That is, the actual time of arrival entered in the system is cancelled. ACTION RESULT Perform the FP visualization action Click on the [C.ATA] switch, situated at the bottom of the window, with LB. The switch changes to YELLOW and the accessible fields for the action are displayed in WHITE background.
Finish the action by clicking on one of the following icons: [UPDATE] icon The ATA cancellation process is triggered if the ATA action was previously performed. The FP Operation window (action mode) is displayed in View mode ([View] switch activated. All fields are displayed inaccessible. [CANCEL] icon The FP Operation window (action mode) is closed and the action is aborted, if it has not been previously validated ([UPDATE] icon). [CLEAR] icon All data included in the FP Operation window (action mode) are deleted and the window automatically changes to View mode ([View] switch activated). [PRINT] Icon Print the historical information of a FP. Compulsory Fields: Note:
DEST, EOBT. Only if the visualization action has not been previously performed. This action can be performed only if a previous ATA action was
DOCUMENT N: 0029200000000MA03
executed.
2.2.17.1.1
Action: AFTN SEND => {[FP ACTION] => [Aftn Send]}
Application: Performs an AFTN template with fulfilled the FPL data on the ICAO template. ACTION RESULT Perform the FP visualization action Click on the [Aftn Send] switch, situated at the bottom of the window, with LB. The switch changes to YELLOW and the accessible fields for the action are displayed in WHITE background. New window appears with all data of the FPL to be sended via AFTn thorugh the AFTN ICAO template
[UPDATE] icon The action is performed information via AFTN. [CANCEL] icon The FP Operation window (action mode) is closed and the action is aborted, if it has not been previously validated ([UPDATE] icon). [CLEAR] icon All data included in the FP Operation window (action mode) are deleted and the window automatically changes to View mode ([View] switch activated). [PRINT] Icon Print the historical information of a FP. to send the
2.2.17.1.2
Action: Strip Printing => {[FP ACTION] => [Strips]}
Application: Performs or planificates a strip printing action, by selecting the moment for strip printing (entering a sector or reaching a fix point).
DOCUMENT N: 0029200000000MA03
ACTION Perform the FP visualization action Click on the [Strips] switch, situated at the bottom of the window, with LB.
RESULT
The switch changes to YELLOW and the accessible fields for the action are displayed in WHITE background.
Enter the FIXPOINT data or the S sector data for which the strip is going to be printed. Finish the action by clicking on one of the following icons: [UPDATE] icon The action is performed; when the Fixpoint or the Sector previously entered is reached, a paper strip will be printed. The FP Operation window (action mode) is displayed in View mode ([View] switch activated. All fields are displayed inaccessible. [CANCEL] icon The FP Operation window (action mode) is closed and the action is aborted, if it has not been previously validated ([UPDATE] icon). [CLEAR] icon All data included in the ICAO AFTN TRANSMISSION window are deleted and the window automatically changes to View mode ([View] switch activated). Compulsory Fields: ESTIMATE FIX or S (excluyent).
2.2.17.1.3
List of Synonyms
When two or more Flight Plans have the same Callsign and the Controller performs a view operation ([View] switch), the System displays the List of Synonyms over the FP Operation Window. This List of Synonyms includes all flight plans that have the same Callsign.
Page 2-127
DOCUMENT N: 0029200000000MA03
Figure 2-63: List of Synonyms Click twice on a Flight Plan within the List of Synonyms to present all FP data within their corresponding fields in the FP Operation Window.
2.2.17.2 FPLs Retrieval

This option triggers all FPLs retrieval procedures for subsequent actions on them. By clicking on the FP Retrieve option of the [FPL] pop-up menu, the FPs Retrieval window is displayed.
Figure 2-64: Flight Plan Menu [FPL] This window is used to define filter for the FPLs retrieval and to display the data of one FPL that matches the set of specific parameters entered by the controller. When the controller performs a query to the system on the FPs Retrieval window, the system displays the list of flight plans matching the specific parameters. The layout of these windows is shown in figure below.
Figure 2-65: FPs Retrieval Window Edition Area: Most of the fields are the same as for the FP Operation Window in action mode. Following table shows those fields, which are different including a description with their valid data. Table 2: FPs Retrieval Window. Edition Area
Page 2-128
DOCUMENT N: 0029200000000MA03
Field CALLSIGN R FT DEP EOBD EOBT DEST ROUTE REG STS FROM UNTIL Flight Rules Flight Type
Description Aircraft identification
Valid Data 1 to 8 alphanumeric characters 1 character 1 character 4 alphanumeric characters Date (YYMMDD) (00 to 99, 01 to 12 and 01 to 31) Hour (HHMM) (00 to 23 and 00 to 59) 4 alphanumeric characters Name of fixes known by the system 5 alphanumeric characters HOSP, EMER, HEAD, STATE SAR, HUM,
Departure Aerodrome Estimated Off-Block Date Estimated Off-Block Time Destination Aerodrome One or more fixes. If there is more than one, they are separated by the AND (+) or OR (|) operators Alternative aircraft identification Status. Defined in FP field 18. Time determining the start of a temporal filter for FPL retrieval Time determining the end of a temporal filter for FPL retrieval
HHMM (00 to 23 and 00 to 59) HHMM (00 to 23 and 00 to 59)
Rules for Entering Data: Dark GREY shaded fields do not allow data to be input or changed. Fields displayed on WHITE can be input or changed. Fields displayed on RED have an erroneous data or they are mandatory and have not been filled in. If maximum number of characters allowed in a field is filled in, the cursor automatically goes to the first character position in next field. If there are different errors (compulsory, syntactic, etc.,) when editing a FP, the message displayed on the error message area corresponds to the first field with error where the cursor is situated. Command Area: Following table shows the different commands included in the FPs Retrieval Window. The operational behaviour is described in Chapter 3. Table 3: FPs Retrieval Window. Command Area Icon/Switch Description Allows the filter by flight plan status. It can be displayed flights in status: INIT: Initial PEND: Pending State NOTIF: Notificated ACTIV: Active
DOCUMENT N: 0029200000000MA03
Icon/Switch TERM: Terminated
Description
ALL: All flights (no state filter) Summary Retrieve UPDATE CANCEL CLEAR Pr All Display the number of FPs matching the criteria (filters). Trigger the actions performed in the current window. Close the window. If actions were not previously validated, they will not be taken into account by the system. Delete the data displayed on the fields of the window. Print all the retrieved FP.
Error Message Area: It displays the error associated to the field where the mouse is focused on. A list of error messages is provided in Annex B. Retrieved Flight Plan(s) Window: This window is displayed when clicking on the [UPDATE] icon of the FPs Retrieval Window. The FPs not in view can be visualized by means of the vertical scroll bar available in the window right side. Each line included in this window contains the following information: Table 4: Retrieved Flight Plan(s) Window. List Element Element CALLSIGN R FT N TYPE DEP EOBD EOBT SPEED RFL DEST ETA CSSR ROUTE
Description Indicative Flight Rules Flight Type Number of Aircrafts Aircraft Type Departure Aerodrome Estimated Off-Block Date Estimated Off-Block Time Cruise Speed Requested Flight Level Destination Aerodrome Estimated Time of Arrival SSR Code FP Route
DOCUMENT N: 0029200000000MA03
Element REG STS STATUS Alternative aircraft identification Status Status of the FP.
Description
2.2.17.2.1.1
Action: Retrieve Multiple FP => {[FPL] -> (FP RETRIEVE)}
Application: Perform this procedure to display one or more Flight Plans, from the FPLs database, that match the selection criteria. ACTION RESULT LB click on the FP RETRIEVE option of the [FPL]. The FPs Retrieval window is displayed.
To display the FPs: If input parameters are known, enter the data in the corresponding fields and click on the [UPDATE] icon. The Retrieved Flight Plan(s) window is displayed with the flight plan(s) matching the specific parameters. If input parameters are unknown, click on the [UPDATE] icon. The Retrieved Flight Plan(s) window is displayed with all flight plans.
Once the Retrieved Flight Plan(s) window is displayed, it is possible to select one of the FPs: By clicking twice corresponding FP. on the The selected FP is displayed on the FPs Retrieval window. That is, the Retrieved Flight Plan(s) window is removed from screen and the FPs Retrieval window is displayed instead of.
DOCUMENT N: 0029200000000MA03
ACTION From this point on, all possible FP actions may be performed on the selected FP. If clicking on the [Summary Retrieve] switch at the bottom of the FPs Retrieval window with the LB and the on the [UPDATE] icon
RESULT
An indication of the number of FPs that matches the selection criteria is displayed over the FPs Retrieval window. Finish the action by clicking on one of the following buttons: [CANCEL] icon All windows are closed. [CLEAR] icon The displayed data is deleted from the FPs Retrieval window. Compulsory Fields: None.
2.2.17.3 Conflict
The controller can request the list of FP pairs if detected to be in conflict by the MTCD (Medium Term Conflict Detection) function. This list is displayed on the FP Conflicts window with a title containing the time at which the conflict was requested. The FP Conflicts window is displayed when performing any of the following actions: By clicking on the Conflict option of the [FPL] pop-up menu. This option displays all the current conflict pairs.
Figure 2-66: Flight Plan Menu By clicking on the Conflict option of the [FPL] pop-up menu displayed when accessing a FP from the Flight Plan list. This option displays the FPs in conflict with the selected flight plan. By clicking with the LB on the MTCD indicator of the track label. This option displays the FPs in conflict with the selected flight plan.
Page 2-132
DOCUMENT N: 0029200000000MA03
The FP Conflicts window has two main sections (areas) and a command area, as described below:
Figure 2-67: FP Conflicts Window First Window Section (List Area): It is situated in the window upper section and it contains the list of FP pairs in conflict. Following table describes the information involving this area: Table 5: FP Conflicts Window. First Window Section (List Area) Element C/S ADEP SEGMENT ENTRY SEGMENT EXIT Call Sign Departure Aerodrome Start of the segment at which the flight enters in conflict / ETO / Level at the inbound fix End of the segment at which the flight exits from the conflict / ETO / Level at the outbound fix Description
Second Window Section (Chart Area):

DOCUMENT N: 0029200000000MA03
It is a graphic display of the conflict. The conflict is represented in an X-Y chart, where X represents the time in minutes counted from the time displayed on the window title (time 0 is the time at which the conflict was requested) and Y represents the distance between the FP projected to be in conflict. Each conflict is displayed in the chart with a symbol, together with the conflict identification number and a horizontal vector The symbol location on the chart for each conflict is determined as follows: the X coordinate is the time at which the flights are projected to reach their minimum separation; the Y coordinate represents the minimum distance between the flight plans in conflict. . The vector start is placed in the conflict symbol, and extends to the conflict entry time. The conflicts in the chart are displayed in two colours: RED (hight severity) or YELLOW (medium severity). The criteria to display on one of the colours depends on two adapted parameters: Minimum warning distance.
Minimum warning time.
An imaginary line is drawn in the chart with the following coordinates: X = 0, Y = minimum warning distance
X = minimum warning time, Y = 0
All conflicts, situated on the left of this imaginary line, are displayed in RED. All conflicts situated on the right of this imaginary line are displayed in YELLOW.
Figure 2-68: FP Conflicts Window Warning/ Conflicts Areas
Page 2-134
DOCUMENT N: 0029200000000MA03
The interaction with the conflict symbol allows the access to the Future Horizontal and Vertical Situation windows, described below. Command Area: Following table shows the different commands, which are included in the FP Conflicts window. Table 6: FP Conflicts Window. Command Area Icon CANCEL Close the FP Conflict window. Command
2.2.17.3.1
Horizontal Future Situation Window (HFS)
The HFS window comprises a Radar Data Display window, which is similar to the SDD SIT Area. It is used to display the FPs future air traffic situation. To display the window, LB click on the conflict symbol (conflict chart). The window shows the extrapolated FPs is displayed centred in the position and time at which the minimum distance will be reached.
Figure 2-69: Horizontal Future Situation Window Command Area: The Command Area is located at the top of the HFS window and consists of the following items: Table 7: HFS Window. Command Area Icon Presentation Range Time (+ or -)
Command Display the presentation range. When clicking on it, a pop-up menu is displayed to select a new presentation range in nautical miles. Display the time (in the future). When clicking on it, a pop-up menu is displayed to select the time when the extrapolation is performed. The time
DOCUMENT N: 0029200000000MA03
Icon
Command may be augmented or decreased (from 1 to 5 minutes) with the + and icons. The default time is running 10 minutes faster than the current system time. Display a pop-up menu to select the type of map to be displayed at the Display Area.
Maps
Display Area: It represents the geographical visualization of the future situation.
2.2.17.3.2
Vertical Future Situation Window (VFS)
The VFS window represents the traffic over-flying a determined correlated track at a determined time. To display the window, RB click on the conflict symbol (conflict chart). The window showing the FPs in conflict will be displayed, centred in the next fix of the conflict-starting segment of the first flight, and extrapolated to the time at which the minimum distance will be reached.
Figure 2-70: Vertical Future Situation Window Command Area: The Command Area is located at the top of the VFS window and consists of the following items: Table 8: VFS Window. Command Area Icon Presentation Range Flight Level Time (+ or -)
Command Display the presentation range. When clicking on it, a pop-up menu is displayed to select a new presentation range in nautical miles. Display the flight level. When clicking on it, a pop-up menu is displayed to select a new flight level. Display the time (in the future). When clicking on it, a pop-up menu is
DOCUMENT N: 0029200000000MA03
Icon
Command displayed to select the time when the extrapolation is performed. The time may be augmented or decreased (from 1 to 5 minutes) with the + and icons. The default time is running 10 minutes faster than the current system time.
Display Area: It represents the geographical visualization of the future conflict situation. The window is centred in the selected track. The X-axis represents distances to the fix and the Yaxis represents flight levels.
2.2.17.3.3
Action: Future Situation Visualization => {[FPL] -> [CONFLICT]}
Application: Perform this procedure to display the list of FP pairs if detected to be in conflict by the MTCD function. ACTION RESULT Click on the [FPL] icon of the SDD General Information Area. A pull-down menu is displayed.
LB click on the Conflict option The Conflict window is displayed.
Page 2-137
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
LB click in a track symbol (triangle symbol)
The future horizontal situation window displayed, extrapolated to the conflict time.
is
RB click in a track symbol (triangle symbol)
The future vertical situation window is displayed, extrapolated to the conflict time.
Page 2-138
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
Finish the action by clicking on the [CANCEL] icon in Conflict Window and by clicking on the [X] icon in HFS/ VSF window. The Conflict and HFS/ VFS windows are closed.
2.2.18 Maps [MAP] Icon

This icon allows the activation/inhibition of maps visualization, by displaying a pop-up menu including the different maps categories. The map category is selected with the LB. The selected map is displayed with a YELLOW mark (see following figure), and the non-selected map is displayed with the mark in background colour. It is available to select more than one category without closing the pop-up menu. To de-select a map category, click with the LB on the current selected one.
Page 2-139
DOCUMENT N: 0029200000000MA03
Figure 2-71: Maps Selection Pop-up Menu It is also possible to select sub-maps from the corresponding map category by clicking the desired option on the pop-up sub-menus, with the LB. If defined (as shown in previous figure), the symbol is displayed besides the map name.
2.2.18.1 Action: Select Maps => {[MAP]}

Application: Perform this procedure to activate/inhibit the map category display. ACTION RESULT LB Click on the [MAP] icon of the SDD General Information Area. A pull-down menu is displayed to select the required type of map.
Page 2-140
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
To select/de-select map category: RB click on the desired map. The corresponding map is selected showing a YELLOW mark on the left side. At the same time, the selected map is displayed on the SDD SIT Area. It is possible to select different categories of maps at a time within the same process. RB click again on the selected map. The map is de-selected and the mark returns to background colour. To select/de-select sub-maps: Some maps categories include defined sub-maps. The arrow displayed on the name right side recognizes them. LB click on the corresponding maps arrow. The sub-maps pop-up menu is displayed to select the required one.
Page 2-141
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
Finish the action by LB clicking outside the pull-down menu area. The pop-up menu(s) is closed.
2.2.19 Fixed Configuration [CONFIG] Icon

When clicking on the [CONFIG] icon, a pop-up menu is displayed to allow, by means of two options, the selection of a fixed configuration or the programming of a new one. LOAD sub-menu allows the selection of a previously saved configuration. SAVE sub-menu allows the selection of a profile to store current configuration.
Figure 2-72: Fixed Configuration Pop-up Menu. LOAD Option By clicking on SAVE and selecting an option, the new configuration is saved.
Page 2-142
DOCUMENT N: 0029200000000MA03
Figure 2-73: Fixed Configuration Pop-up Menu. SAVE Option Table 9: CONFIG Menu. Elements Element DEFAULT CONFIGX FCONX USERPREF It is readable and writable. This configuration can be loaded or stored, as it is readable and writable. There are four different available configurations: CONFIG1 to CONFIG4. These predefined configurations can only be loaded, as they are no writable. Each user can save and load its own configuration in option USERPREF, which will be distributed by the system and charged in every SDD position. Description This predefined configuration is loaded the first time a user login in the position.
2.2.19.1 Action: Retrieve Special Configuration => {[CONFIG]} -> {[LOAD]}

Application: Perform this procedure to recover a special configuration. ACTION RESULT Click on the [CONFIG] icon of the SDD General Information Area. A pull-down menu with available configurations is displayed. Click on the LOAD option (LB). A pull-down submenu is displayed with the different configurations already established by adaptation and created by the controller.
Page 2-143
DOCUMENT N: 0029200000000MA03
ACTION Select one of the available configurations (LB).
RESULT The screen displays the selected configuration.
2.2.19.2 Action: Save Special Configuration => {[CONFIG]} -> {[SAVE]}

Application: Perform this procedure to program a special configuration. ACTION RESULT Perform the necessary modifications on the position. Click on the [CONFIG] icon of the SDD General Information Area. A pop-up menu with available configurations is displayed. Click on the SAVE option (LB). A pop-up submenu is displayed with the four possible options.
Select one of the configurations names.
possible The desired configuration is loaded with the name of the previously selected configuration.
2.2.20 Quick-Look Sectors Selection [QL SC] Icon

The [QL SC] icon allows the selection of sectors used for Quick-Look. By clicking on it, a pop-up menu of possible sectors is displayed for selection. The sectors assigned to the working position are displayed on background colour and cannot be selected for Quick-Look.
Figure 2-74: Quick-Look Sectors Pop-up Menu
2.2.20.1 Action: Select Sectors for Quick-Look => {[QL SC]}

Application: Perform this procedure to select the sectors for Quick-Look function.
DOCUMENT N: 0029200000000MA03
ACTION LB click on the [QL SC] icon of the Main Menu window.
RESULT
A pull-down menu of possible sectors is displayed. Sectors assigned to the working position are displayed on Background colour and cannot be selected for Quick-Look.
Once the pull-down menu is displayed, RB click on the corresponding one(s) to select/de-select the sector(s). It is possible to select/de-select various sectors at a time. When the sector is selected, a YELLOW mark is displayed at its left. LB click outside the menu area The pull-down menu is closed.
2.2.21 Quick-Look [QLOOK] Icon

The [QLOOK] icon is used to activate/inhibit the Quick-Look function to visualize the selected sector tracks. Its activation status is shown by the icon text colour: YELLOW if it is activated, and WHITE, if inhibited.
Figure 2-75: Quick-Look [QLOOK] Icon
2.2.21.1 Action: Quick-Look Procedure => {[QLOOK]}

Application: Perform this procedure to activate/inhibit the Quick-Look function. ACTION RESULT Depress the [QLOOK] button of the General Information Area. The Quick-Look function is activated. The icon text colour changes to YELLOW. All the tracks under the jurisdiction of the selected Quick-Look sectors are displayed with the enlarged label (including Line 0).
DOCUMENT N: 0029200000000MA03
ACTION Release the [QL] button
RESULT The Quick-Look function is inhibited and the icon text colour turns to WHITE.
2.2.22 Filter OFF [FILTER OFF] Icon

It allows the activation/inhibition of all current filters defined for the SDD SIT Area. Its activation status is shown by the icon text colour: WHITE, if it is inhibited, and YELLOW, if activated. It is also possible to toggle the activation/ inhibition by pressing <Alt> + <O>.
Figure 2-76: Filter OFF [FILTER OFF] Icon
2.2.22.1 Action: Activate/Inhibit Total Filters => {[ FILTER OFF]} or {<Alt> + <O>}
Application: Perform this procedure to activate/inhibit all the current filters established for the SDD SIT Area. ACTION RESULT To activate/inhibit all current filters, there are two possible ways. Using the mouse device: Depress the [FILTER OFF] icon of the General Information Area. If it is inhibited. The icon text colour turns to YELLOW activating all current filters. If it is activated. The icon text colour turns to WHITE inhibiting all current filters. Using the keyboard: Press on the <Alt> + <O> combination keys. Toggle the activation status to inhibition status and vice versa.
2.2.23 [Menu] Icon

This [Menu] icon displays or closes the Main Menu window, which is displayed at the bottom of the SDD screen.
Page 2-146
DOCUMENT N: 0029200000000MA03
Its activation status is shown by the icon text colour: YELLOW if it is activated, and WHITE if inhibited. If the [Menu] icon is not activated and the system receives a warning message, the icon text starts blinking until the controller activates it. It is also possible to toggle the activation/inhibition by pressing <Alt>+ <M>.
Figure 2-77: [MENU] Icon
2.2.23.1 Action: Display/ Close the Main Menu Window => {[MENU]} or {<Alt> + <M>}
Application: Perform this procedure to display/ close the Main Menu window presentation. ACTION RESULT There are two ways for displaying/closing the Main Menu window. By means of the mouse device: Depress the [MENU] icon of the General Information Area. If it is activated (YELLOW) The icon text colour turns to WHITE. At the same time, the Main Menu window situated at the bottom of the SDD SIT Area is removed. If it is inhibited (WHITE) The icon text colour turns to YELLOW and the Main Menu window is displayed. By means of the keyboard device: Pressing on the <Alt> + <M> combination keys. The Main Menu window is displayed/closed. NOTE: If the Main Menu window is not activated and a system warning message is received in the working position, the [MENU] icon is forced to blink until the controller activates the Main Menu window.
2.3 Main Menu Window

The Main Menu window is located at the bottom of the SDD screen. It is composed of icons and switches, which perform the different functions.
DOCUMENT N: 0029200000000MA03
The Main Menu window is displayed or closed from the [Menu] icon, located in the SDD General Information Area. Its activation status is shown by the icon text colour: WHITE, if it is inhibited, and YELLOW, if activated. Flight plan lists include a set of fields with flight plan data; these fields can be changed off-line from GTI. In this manual a predefined set of fields is provided as an example.
Figure 2-78: [MENU] Icon Table 10: Main Menu Window. Items Item SECTOR LIST INBOUND DEPARTURES ARRIVALS VIEW1 VIEW2 VIEW3 CLOCK BRIGHT LAST POS SECTORS LMG DATBLK RBL OFF ORI OFF RANGERINGS ROU OFF ALM CNL QNH OVERLAP CONFL AREAS VELVECT METEO
Type Icon Icon Icon Icon Icon Icon Icon Icon Icon Icon Icon Icon Icon Icon Icon Icon Icon Icon Icon Icon Icon Icon Icon Icon
Description Display/close the FP List. Display/close the FP InboundList. Display/close the Departure FP List. Display/close the Arrival FP List Display/close the Auxiliary Window (number 1) Display/close the Auxiliary Window (number 2) Display/close the Auxiliary Window (number 3) Display/close the System Clock. Display/close the Brightness window. Display/close the Last Position Window. Display/close the Assigned Sectors list. Display/close the LMG Control Panel window to allow the local maps generation. Display/close the Track Display Configuration window. Delete the display of all the active RBLs in the screen. Return to all tracks labels to the default position. Display/close the range rings. Delete all FPs routes from the screen. Inhibit all the aural alarms. Display/close the QNH window including zone and values information (in inches and milibars) Activate/inhibit the function for the automatic orientation of track labels Activate/inhibit the display of MTCD alarm in track labels. Display/close the active Restricted areas Activate/inhibit the display of Velocity Vector. Activate/inhibit the display of the primary plots with
Page 2-148
DOCUMENT N: 0029200000000MA03
Item RBL ALM QUICKEST MET MSGS SYS MSGS FINDER SSR F F 3D
Type Icon Icon Icon Icon Icon Icon Icon Icon Icon Icon Icon Icon Icon
Description meteorological information. Activate/inhibit the Range Bearing Alarms Display/Inhibit the Quick Estimated Window. Display/close the Meteo Messages Window. Display/close the System Messages Window. Display/close the Finder Window Display/close the SSR Filter Window Display/close the 3D Filter Window Decrease presentation range in discrete or continuous steps. Current range is displayed over this icon. Increase presentation range in discrete or continuous steps. Current range is displayed over this icon. Perform a left scrolling movement within the screen as a horizontal scroll bar. Perform a right scrolling movement within the screen as a horizontal scroll bar. Perform an upwards-scrolling movement within the screen as a vertical scroll bar. Perform a downwards-scrolling movement within the screen as a vertical scroll bar. Print the tabular of the SDD position. Selection among available printers, allowing editing predefined printer. Freeze all the actions that can be performed in the position. At the same time, it displays the Login window to unfreeze the position. Freeze all the actions that can be performed in the position. At the same time, it displays the Login window to unfreeze the position.
PRINT LISTS PRINTERS LOGIN
Icon Icon Icon
LOGOUT
Icon
2.3.1 Common Actions from FP Lists

Flight plan lists include some fields with interaction capability. From Status Indicator field, several actions can be performed, as defined in the following table. Table 11: Common actions in FP Lists Field Status Indicator
Mouse button LB
Action Flight plan operation window display (see 2.3.1.1).
Page 2-149
DOCUMENT N: 0029200000000MA03
Field Status Indicator Status Indicator Status Indicator C/S COP COOR
Mouse button LB LB LB RB LB/ RB RB
Action MTCD Conflict (see 2.3.1.2). Synthetic track creation (see 2.3.1.3). Synthetic track deletion (see 2.3.1.4). Callsign Menu (see 2.1.2.9). Graphical route display. Display the Coordination Window.
2.3.1.1 Action: Flight Plan Operation Window display => {FP List => Status Indicator => [FP ACTION]}
Application: Perform this procedure to display Flight plan template from a Flight plan list. ACTION RESULT Open a Flight Plan list (Sector List, Inbound, Arrivals, Departures) and LB click in Status indicator field. FPL Menu is displayed.
LB click in [FP ACTION] button. Flight plan template is displayed, containing selected flight data.
2.3.1.2 Action: Conflict Window Display => {FP List => Status Indicator => [CONFLICT]}
Application: Perform this procedure to display, from a Flight Plan list, Conflicts Window, that display conflicts for selected flight plan. ACTION RESULT Open a Flight Plan list (Sector List, Inbound, Arrivals, Departures) and LB click in Status indicator field. FPL Menu is displayed.
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
LB click in [CONFLICT] button. Conflict window is displayed, with data about the conflicts the flight plan is involved in.
2.3.1.3 Action: Synthetic Track Creation => {FP List => Status Indicator => [CREATE]}
Application: Perform this procedure to create a synthetic track from a flight plan included in a flight plan list. ACTION RESULT Open a Flight Plan list (Sector List, Inbound, Arrivals, Departures) and LB click in Status indicator field. FPL Menu is displayed.
Page 2-151
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
LB click in [CREATE] option, located in SYNTH. TRACKS square. If flight plan complies all requirements to create a synthetic track, it is created.
2.3.1.4 Action: Synthetic Track Deletion => {FP List => Status Indicator => [DELETE]}
Application: Perform this procedure to delete a synthetic track from a flight plan included in a flight plan list. The track deletion means no modification in the Flight Plan. It is just a graphical representation deletion. ACTION RESULT Open a Flight Plan list (Sector List, Inbound, Arrivals, Departures) and LB click in Status indicator field. FPL Menu is displayed.
For a Synthetic track, LB click in [DELETE] option, located in SYNTH. TRACKS square. Synthetic track is removed from the system.
Page 2-152
DOCUMENT N: 0029200000000MA03
2.3.1.5 Configuration Window for Flight Lists

Every flight plan list can be configured: its fields can be added or removed for display, as well as the size of the font, the display mode and the sorting fields in the list can be changed. All these actions are performed by the Configuration Window for each flight list. The fields that are included in this window, and that can be included in each flight list are off-line configured by GTI tool. All flight lists (Sector List, Inbound, Departures, Arrivals, Coordination) have this window and it is displayed by RB click in the top bar of the list. Configuration of list font size: Three font sizes can be selected: Small, Medium and Large. Selected size is the one with its bistate icon in YELLOW colour. List Mode Display: Two display modes can be selected: Short and Extended. Selected mode is the one with its bistate icon in YELLOW colour. Configuration of displayed fields in flight list: Configuration window includes the list of available fields for the flight plan list, and each one has a bi-state icon. This icon can be activated (YELLOW) and the field is included in the list, or inhibited (background colour) and the field is removed from the list. Sorting Options: The flights inside every flight plan list can be sorted clicking in the field title. A second and a third sorting criteria can be included by the configuration window.
Figure 2-79: Configuration Window
2.3.1.1 Action: Flight List Configuration => {Configuration Window}

Application: Perform this procedure configure a flight list.
DOCUMENT N: 0029200000000MA03
ACTION RB click on the list top bar.
RESULT The Configuration Window for this list is displayed.
Select the font size (Small, Medium, Large) by clicking in the bi-state icon. Select the flight list mode (Extended, Short) by clicking in the bi-state icon. Select the fields to display in the flight list clicking in the bi-state icon (YELLOW for active, background colour to inhibit the field). Select the fields for sorting criteria by selecting them in the Sorting options pop-up menus. The configuration is applied only in the flight list affected by the Configuration Window. Finish the action by clicking in: [ACCEPT]: The changes in the flight list are saved. [CANCEL]: The changes in the flight list are not saved, the list turns to the status previous to the configuration.
2.3.2 FP List [SECTOR LIST] Icon

Click on the [SECTOR LIST] icon to display the FP List including all FPs crossing the sector. The icon changes to GREY when being selected.
Figure 2-80: Sector List

DOCUMENT N: 0029200000000MA03
There are two ways to display the list: short and extended. To get the list in the short mode, click with the RB on the titles row to display the configuration menu and select (SHORT) or (EXTENDED). Sector List can be sorted by every field, clicking on fields name, flight plans will be sorted by this field. Second and third sorting criteria are also defined by configuration menu. It includes all active FPs, which belong to the under-control sectors. Flight assumption must be manually performed. Deletion of flights is automatic from the Sector Lis when the flight is assumed by other sector or it becomes Terminated. The FP List displays following information: Table 12:
Element
FP List. Element Information

Description
Status Indicator
FP: C (Correlated FP) - (Non-correlated FP) L (Lost FP) H (Holding FP) F (FP in Conflict) A (Correlation Ambiguity) S (Synthetic Track)
D ADS CPDLC WARN RVSM
Displays a coloured (yellow or green) circle for eastbound and westbound traffic. ADS Status CPDLC Status Displays the warnings in the flight. RVSM equipped/Not equipped EQ Equipped (Blank) Non-Equipped
C/S SSR ATYP R EOBT ADEP SID

Aircraft Indicator SSR Code Aircraft Type Flight Rules Estimated Off-Block Time. It may be filled with "C"; which indicates the reception of CTOT indication. Departure Aerodrome. SID Procedure
DOCUMENT N: 0029200000000MA03
ADES STAR RFL NCOP PEL
Destination Aerodrome STAR Procedure Requested Flight Level Coordination Point Planned Entry Level With (*), Activation level With (F), the RFL from the FP
NTIME BOUNDARY 1 BOUNDARY 2 XCOP XTIME COOR COM FREE TEXT Counter
Sector Entry Time. Boundary Point. Boundary Point. Exit Coordination Point Sector exit time. Coordination Status Communication Status FP Free Test Field (included in flight plan Free text field) It displays the number of FPs included in the upper/lower list.
Page 2-156
DOCUMENT N: 0029200000000MA03
2.3.3 Planner FP List [INBOUND] Icon

Click on [INBOUND] icon to display the FP list of inbound flights. The icon changes to GREY when being selected. There are two ways to display the list: short and extended. To get the list in the short mode, click with the RB on the titles row to display the configuration menu and select (SHORT) or (EXTENDED). Inbound List can be sorted by every field, clicking on fields name, flight plans will be sorted by this field. Second and third sorting criteria are also defined by configuration menu.
Figure 2-81: Inbound List This FP list will include: FPs in initial status (they take off from an internal aerodrome or adjacent sector). It includes Active FPs, which belong to any other sector. Departure time lists the flights in this area, that is, when they change to notified status or when the VSP forces the display of an active FP before the sector entry time. Flights enter Inbound list a VSP FP List Presentation Time before the flight enters the controlled sector. Deletion of flights is automatic in the following cases: When the flight becomes Terminated; When the VSP FP List Removal Time time before the flight leaves the sector is reached; When the FP is assumed by the controller. Table 13:
Element
FP List. Element Information

Description
Status Indicator
FP: C (Correlated FP) - (Non-correlated FP) L (Lost FP) H (Holding FP) F (FP in Conflict) A (Correlation Ambiguity) S (Synthetic Track)
D ADS CPDLC
Display a coloured (yellow or green) circle for eastbound and westbound traffic. ADS status CPDLC status
DOCUMENT N: 0029200000000MA03
WARN RV C/S SSR ATYP R EOBT ADEP ADES RFL XFL
Display the flight warnings. RVSM equipment Aircraft Indicator SSR Code Aircraft Type Flight Rules Estimated Off-Block Time. It may be filled with "C"; which indicates the reception of CTOT indication. Departure Aerodrome. Destination Aerodrome Requested Flight Level Exit flight level With (*), Activation level With (F), the RFL from the FP
PEL
Planned Entry Level With (*), Activation level With (F), the RFL from the FP
NTIME NCOOR NCOM ENTRY
Sector entry time (HH:MM) Coordination Status. Communication Status. Sector entry point The fixpoint name as it is defined by adaptation. The symbols - -, if the fixpoint is unknown (sector limit course). Departure Aerodrome name, if internal.
EXIT
Sector exit point The name of the point, as it is defined by adaptation. The symbols - -, if the point is unknown (sector limit course). Destination Aerodrome name, if internal.
XCOP XFL
Exit Coordination Point Exit flight level With (*), Activation level With (F), the RFL from the FP
XTIME
Sector exit time Minutes from current or past time (HH:MM)
Page 2-158
DOCUMENT N: 0029200000000MA03
COORD COM Free Text Counter
Coordination Status. Communication Status. FP Free Test Field (included in flight plan Free text field) It displays the number of FPs included in the upper/lower list.
The Callsign background is remarked when selecting the FP. If there is any conflict the FP first field turns to RED. The FP List includes scroll bars when the number of FPs exceeds the window size.
2.3.4 Coordination Window

RB click on the COORD field of SECTOR LIST, INBOUND list and DOORD list will display the Coordination Window, that allows Entry/ Exit Coordination. By means of this window, a coordination message is manually send to external centers both entry and exit. Coordination window can different, depending the coordination type between the centers, and can be both entry or exit. Each window includes the data and available coordination messages depending on the coordination type, and the current coordination phase.
Figure 2-82: Coordination Window Table 14: FIELD CALLSIGN ADEP ADEST EOBD EOBT
Coordination Window
DESCRIPTION Aircraft Identification Departure Aerodrome Destination Aerodrome Estimated Off-Block Date It may include C, which means the CTOT indication reception. Estimated Off-Block Time
DOCUMENT N: 0029200000000MA03
FIELD COP ETO TFL CDN ACP EST REJ TOC AOC COOR ICON SEND CANCEL
DESCRIPTION Coordination Fixpoint Estimated Time Over Fixpoint Transfer Flight Level Coordination message Acceptance message Estimation Rejection Transfer Of Control Assume Of Control Coordination dialogue establishment DESCRIPTION Coordination message sending Cancel the coordination message process
Page 2-160
DOCUMENT N: 0029200000000MA03
2.3.5 Departure FP List [DEPARTURES] Icon

The Departure FP List includes all FPs to take off from an airport within one of the position sectors. The list shows the flights, which are going to take off or have already taken off but are still within our sector. The Departure FP List, for ACC and APP roles, has two sections: First List Area (upper): It includes all departure flight plans in active status, that are also assumed by the controller. Second List Area (lower): It includes all departure Flight Plans in notified status, and active status, that are not assumed. When a FP is assumed, this is removed from lower area. The Departure FP List, for TWR role, has two sections: First List Area (upper): It includes all flight plans in active status, which have taken off from a sector aerodrome. A Flight Plan does not change from notified status to active status automatically but it is necessary to receive or perform an ATD on that Flight Plan. The Flight Plans disappear from this area a time value defined by Departure Tower NO Volume Deletion VSP, or when they become Terminated. Second List Area (lower): It includes all Flight Plans in notified status, which are going to departure from a sector aerodrome. A Flight Plan automatically changes from pending to notified a time before its EOBT defined in the VSP Departure FP Notification Time. When the FP changes from notified to active status, this will be deleted from this list and will be displayed on the first one (upper).
There are two ways to display the list: short and extended. To get the list in the short mode, click with the RB on the titles row to display the configuration menu and select (SHORT) or (EXTENDED). Departure List can be sorted by every field, clicking on fields name, flight plans will be sorted by this field. Second and third sorting criteria are also defined by configuration menu.
Figure 2-83: Departure FP List Table 15:

FIELD
Departure FP List
DESCRIPTION
C (Correlated FP) Status Indicator - (Non-correlated FP) L (Lost FP)

DOCUMENT N: 0029200000000MA03
FIELD
DESCRIPTION
H (Holding FP) F (FP in Conflict) A (Correlation Ambiguity) S (Synthetic Track) C/S CSSR ADEP Type R CFL EOBT CTOT ATD SID RFL FREETEXT <number> Aircraft Identification Flight SSR code Departure Aerodrome Aircraft Type Flight Rules Clearance Flight Level Estimated Off-Block Time It may include C, which means the CTOT indication reception. Calculated take-off time Actual Time of Departure Standard Instrument Departure Requested Flight Level Free Text Number of FPs included in the list (upper/lower).
2.3.6 Arrival FP List [ARRIVALS] Icon

The Arrival FP List includes all Flight Plans in active status, which land in a sector aerodrome. The flights automatically enter the list a VSP value that differs between the position role: For ACC and APP roles: the flight enter Arrival list a previous VSP time before the flight enters in the sector. This time is defined in FP List Presentation Time VSP. For TWR role: the flight enter Arrival list a previous VSP time before the flight becomes terminated. This time is defined in Arrival Tower NO Volume Presentation Time VSP. The flights are automatically deleted from the list when a time has passed since they arrived or can be manually deleted (ATA) from the FP Operation Window. There are two ways to display the list: short and extended. To get the list in the short/ extended mode, click with the RB on the titles row to display the configuration menu and select (SHORT) or (EXTENDED). Arrival List can be sorted by every field, clicking on fields name, flight plans will be sorted by this field. Second and third sorting criteria are also defined by configuration menu.
Page 2-162
DOCUMENT N: 0029200000000MA03
Figure 2-84: Arrival FP List The Configuration Window is displayed by clicking in the windows title. This window includes: Font size selection: available font sizes are Small, Medium, Large. Mode selection: selecting short mode, the list includes the fields selected in the lower area of this window; extended mode includes all the fields available for the list. Fields for short mode: allow select the fields to display in the list. Table 16:
FIELD
Arrival FP List
DESCRIPTION
C (Correlated FP) - (Non-correlated FP) L (Lost FP) Status Indicator H (Holding FP) F (FP in Conflict) A (Correlation Ambiguity) S (Synthetic Track) SQ C/S CSSR ADES ATYP EOBT ETA STAR <number> Sequence number Aircraft Identification SSR Code. Destination Aerodrome Aircraft Type Estimated Off-Block Time It may include C, which means the CTOT indication reception. Estimated Time of Arrival Standard Instrument Arrival Route Number of FPs included in the list.
2.3.7 VIEW [VIEW1], [VIEW2], [VIEW3] Icon

Use these icons to display/ close the Auxiliary Windows. Three Auxiliary Windows are provided in order to provide multiple displays to controllers.
DOCUMENT N: 0029200000000MA03
The Auxiliary Window includes the GI_A and SIT_A graphical representation possibilities. The Controller may situate the window at any point within the map.
Figure 2-85: View Window Click on the [VIEWX] icon and then select a specific point in the screen to display the Auxiliary Window. Its behaviour is autonomous, that is, some actions performed within this window do not affect the SDD SIT_A. Moreover, it includes an icon, which allows window resizing. As shown in previous figure, the Auxiliary Window has two main areas:
2.3.7.1 Command Area

Similar to the one of the SDD GI_A: Table 17:
Element Type
Auxiliary Window. Elements

Description
PRESENTATION RANGE FALT LIMITS FILTER EXP+

Icon Icon Icon Icon
Display a menu to select the presentation range Activate/ Inhibit the altitude filters for the SIT_A Auxiliary Window Display a menu to select the altitude upper and lower filters to be modified Increase the selected area display extension
Page 2-164
DOCUMENT N: 0029200000000MA03
Element
Type
Description
EXPCEN DCEN MAP
Icon Icon Icon Icon
Decrease the selected area display extension Centre the display De-centre the display Display a menu to select maps to be displayed on the SDD position
2.3.7.2 Display Area

This area displays the SDD map with the selected centre when opening the window. The options selected from the Command Area are within this area.
2.3.7.3 Action: Auxiliary Window Display => {[VIEWX]}

Application: Perform this procedure to use auxiliary windows to perform current different displays. ACTION LB click in [VIEWX] icon in Main Menu Area (X is 1, 2 or 3). The mouse pointer turns into a YELLOW cross when it is moved by SIT area. RESULT
LB click in a point in SIT area. Auxiliary window is displayed, centred in selected point.
Several display settings can be adjusted in General information area in Auxiliary window. Their working procedure is the same than the ones in SDD General Information Area. The rest of auxiliary windows can be currently displayed, with selected centre for each one.
DOCUMENT N: 0029200000000MA03
2.3.8 [CLOCK] Icon

This icon is used to display/close the System Clock window. It is the system time (UTC) in HH:MM:SS format.
Figure 2-86: System Clock Window
2.3.9 Brightness [BRIGHT] Icon

This icon is used to display/close the Brightness window. Its activation status is shown by the icon font/ background colours: BLACK/ LIGHT GREY if it is activated, and WHITE/ DARK GREY, if inhibited.
Figure 2-87: [BRIGHT] Icon
2.3.9.1 Brightness Window

This window allows the controller to alter the colour and brightness of maps.
Page 2-166
DOCUMENT N: 0029200000000MA03
Figure 2-88: Brightness Window As shown in previous figure, to modify the colour and the brightness, there are three horizontal scroll bars for general bright purposes, and twelve more for maps related bright configuration, which slip left and right according to necessities by means of mouse pointer. Clicking in MAPS biestate button, all map type is displayed for its bright modification. The number on the top of the scroll bar indicates the current value. Clicking on [DEFAULT] button restore changes to the bright values active when Bright adjustment window was opened. Clicking on [RESET] button sets all bright values to 0 and all the scroll bars to the central position.
DOCUMENT N: 0029200000000MA03
The following items are available for it individual bright adjustment: LABELS: Brightness for track display. LOCALS: Brightness for local map display. BACKGROUND: Brightness for main windows background display. RANGE RINGS: Brightness for range rings display. MAPS: Displays the brightness adjustment for those map types: MSAW RADARS QNH VOR_FIXPOINTS NDB_FIXPOINTS ROU_FIXPOINTS APP_FIXPOINTS AIRWAYS AIRPORTS RUNWAYS PROFILES BOUNDARY
2.3.9.2 Action: Change Brightness => {[BRIGHT]}

Application: Perform this procedure to modify the general brightness of the SDD, as well as that of the maps, tracks and RBLs in the SDD SIT Area. ACTION RESULT Depress the [BRIGHT] button of the Main Menu window. The icon turns to YELLOW and the Brightness window is displayed.
For brightness change in maps, LB click in

DOCUMENT N: 0029200000000MA03
ACTION MAPS bi-state icon.
RESULT The map brightness options are displayed.
LB Click on the vertical scroll bars and move left and right without releasing the mouse button. The number (zero by default) increases or decreases depending on the movement selection. Click in [DEFAULT] button to change current brightness values to the initial ones (the values when the bright control window was displayed). Click in [RESET] button to change current
DOCUMENT N: 0029200000000MA03
ACTION brightness values all to zero.
RESULT The brightness values changes and brightness of SDD elements also changes. the
Release the [BRIGHT] button. The icon text colour changes to Background colour and the window is closed.
2.3.10 [LAST POS] Icon

This icon is used to display/close the Last Position window to visualize the last position of a lost track after it disappears from Lost list. The system allows the display of last position for lost tracks since it appears in Lost list in the following 15 minutes.
Figure 2-89: Last Position Window User can enters both Callsign or SSR code to look for last position.
2.3.10.1 Action: Display of last position of a Lost track => {[LAST POS]}
Application: Perform this action to display the last position of a lost track, when it was removed from Lost list. It will only be useful in the next 15 minutes since the track appears in Lost list. ACTION RESULT Click in [LAST POS] button of the Main Menu window. The Last Position window is displayed to display the last position of a lost track.
Complete the Callsign or the SSR field and click in OK button. The lost track is displayed in its last position registered in the system.
2.3.11 Sectors Visualization [SECTORS] Icon

This icon is used to display/close the Sectors window to visualize the sectors assigned to the system control positions. When clicking on this icon, the Sectors window is displayed.
Page 2-170
DOCUMENT N: 0029200000000MA03
Figure 2-90: Sectors Window The window displays each system control position and the sectors assigned to them.
2.3.11.1 Action: Sectors Visualization => {[SECTORS]}

Application: Perform this procedure to request the visualization of the Sector Control Positions sectors assignment. ACTION RESULT Depress the [SECTORS] button of the Main Menu window. The Sectors window is displayed to visualize to which Sector Control Position the sectors are assigned.
Release the [SECTORS] button. The Sectors window is closed.
2.3.12 Local Maps Generation Tool [LMG] Icon

By clicking on the [LMG] icon, the tool for generating local maps is activated or inhibited. The tool activation/inhibition may be also toggle by pressing <Alt> + <G>.
2.3.12.1 LMG Control Panel Window

The [LMG] icon allows the activation/inhibition of the Local Map Generation Tool. When clicking on the icon, the LMG Control Panel window is displayed/closed.
Page 2-171
DOCUMENT N: 0029200000000MA03
Figure 2-91: LMG Control Panel Window The LMG Control Panel window consists of the following main areas: Primitive Graphic Type Area

Edition Area Command Area
2.3.12.2 Primitive Graphic Type Area

This area is composed of icons that represent the different graphics to be drawn: Circumference. It requires central point and radius. Circle. It requires central point and radius. Filled Polygons. It requires, at least, three vertices not crossing each other. Polylines. It requires, at least, three vertices not crossing each other. Vectors. It requires two points. ATC Symbols. It requires selecting the symbol and position. Text. It requires introducing the text within the edition area. Arcs. It requires two points. Sectors. It requires central point and arc points. Filled Sectors. It requires central point and arc points.
2.3.12.3 Edition Area

The edition area is only used to enter the data when the selected primitive graphic is text. To enter any other primitive graphic, following <key> + mouse button actions are carried out: Ctrl + LB Ctrl + CB
Select the geographic position (centre, radius, first point, etc) Cancel the last primitive graphic edition
DOCUMENT N: 0029200000000MA03
Ctrl + RB
Accept the primitive graphic
2.3.12.4 Command Area

Following icons are included in this area: Table 18: LMG Control Panel Window. Command Area Icon SEL CLR COLOR ACCEPT CANCEL LOAD SAVE DELETE Selected Delete the shape Colour of the shape Trigger the creation action of the primitive graphic. Reject the last action and start again the drawn map from the last step. Recover a local map saved into disk. Save the current local map into disk (changes made on local map are saved). Delete current local map display (local map to be generated starts from zero). Meaning
2.3.12.5 Action: Local Maps Generation => {[LMG]}

Application: Perform this procedure to allow the Local Maps Generation. ACTION LB click on the [LMG] icon to activate the Local Maps Generation tool. NOTE: This action can be also initiated by pressing the <Alt> + <G> keys. The LMG Control Panel window is displayed. RESULT
Select the type of primitive graphic by clicking on the corresponding icon of the LMG Control Panel window. Text is displayed on the control panel to indicate the next action to be performed depending on the selected primitive graphic.
DOCUMENT N: 0029200000000MA03
ACTION If the primitive graphic is a text, input data by means of the keyboard. If the primitive graphic is a figure, the following mouse actions are carried out: Crtl + LB: selects a geographic position (centre, radius, first point, etc).
RESULT
As shown in figure, the mouse cursor changes into a YELLOW cross. Move the cursor, without releasing the LB, in order to size the primitive graphic.
Crtl + CB: cancels the last primitive graphic edition (before being accepted). All steps may be cancelled successively. It is also possible to cancel the primitive graphic by clicking on the [CANCEL] icon of the LMG Control Panel. Crtl + RB: accepts the primitive graphics, which then form part of the LMG map category. It is also possible to accept the primitive graphic by clicking on the [ACCEPT] icon of the LMG Control Panel window.
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
Once the primitive graphic is accepted, click on the [SAVE] icon at the bottom of the control panel to save it. A pull-down menu is displayed with the available option names. Click on the [LOAD] icon, at the bottom of the LMG Control Panel window to load the primitive graphic. A pull-down menu is displayed with available option names. Click on the [DELETE] icon. To erase the already created primitive graphic. Click again on the [LMG] icon. The LMG Control Panel window is closed. If the new graphic has not been activated, the creation action is cancelled.
2.3.13 Tracks Display Configuration [DATBLK] Icon

Click on this icon to display the Track Display Configuration Window. Use this window to configure the different aspects in relation to the tracks display on the SIT_A.
Figure 2-92:
[DATBLK] Icon
Page 2-175
DOCUMENT N: 0029200000000MA03
Figure 2-93: Track Display Configuration Window Table 19:

Icon
Track Display Configuration Window. Icons Description

Description
LABEL SIZE
Present a menu with three different sizes for track label symbols and characters. The available options are: S Small M Medium L Large
VELOCITY VECTOR
Click on the arrow-buttons, the number increases or decreases in 1 unit. The vector longitude steps are 1 minute with a maximum of 5 and a minimum of 1. A small transversal trace to the velocity vector delimits each minute. The track future position (in that minutes quantity) shows the velocity vector end taking into account the current track flight speed and heading.
LABEL ROLE
Present the menu with the available SDD roles, that will affect the track label format. Options are the following ones: APP Approach ACC Route TWR Tower
Page 2-176
DOCUMENT N: 0029200000000MA03
Icon
Description
HISTORY
By means of the arrow-buttons, the number of past positions is increased or decreased for each track. The number of available past positions is 10 as maximum and 1 as minimum.
LIST FONT
Present the menu with the available formats for the Flight Plans Lists size. The options are: S Small M Medium L Large
DELAY HANDOVER
By means of the arrow-buttons, the time (in seconds), for which the Flight Plan route accepted after a hand-over between two sectors is displayed, is selected. The number of seconds is 10 as maximum and 0 as minimum. By means of the arrow-buttons, the distance (in screen size percentage) that the track label can be manually moved from its original position. The available percentage is from 10 to 80 in gaps of 10. Present the menu with the available formats for the graphical route font size. The options are: S Small M Medium L Large
STRETCHING FACTOR
ROUTE FONT
ROUTE MARKS
By means of a pop-up menu, the graduation in the route marks can be selected, both in NM or in minutes. The available values, both for NM and for MIN are from 2 to 20 in gaps of 2. By means of a bi-state icon, route marks can be displayed in graphical route display or not.
LABEL ORIENTATION NUMBER OF LINES
By means of the arrows, the label orientation can be selected. The centre symbol performs a label rotation in anti-clockwise by means of 45. Number of lines to be displayed in label (when track is not selected)
Click on the [X] icon to close the Track Display Configuration Window.
2.3.13.1 Action: Select Tracks Symbols and Characters Size => {[DATBLK] -> [LABEL SIZE]}
Application: Perform this procedure to select the size for track symbols and characters.
Page 2-177
DOCUMENT N: 0029200000000MA03
ACTION LB click on the [DATBLK] icon situated in the Main Menu window.
RESULT
The Track Display Configuration window is displayed.
Click on the [LABEL SIZE] icon. A pull-down menu with the available sizes is displayed.
The options available in the pull-down menu are: S - small M - medium L - large Select the desired track label format by clicking on it. Automatically, the size is displayed on the track symbols and characters.
Page 2-178
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
2.3.13.2 Action: Select Time Velocity Vector => {[DATBLK] -> [VELOCITY VECT]}
Application: Perform this procedure to select the unit time for the velocity vector. ACTION RESULT LB click on the [DATBLK] icon situated in the Main Menu window. The Track Display Configuration window is displayed.
Click on the [VELOCITY VECTOR] arrows (up and down).
The time unit (number) is increased or reduced in

DOCUMENT N: 0029200000000MA03
ACTION
RESULT 1-minute unit (with a maximum of 10 and a minimum of 1). Automatically, the size is displayed.
2.3.13.3 Action: Select Total Track Label Format =>{[DATBLK] -> ROLE}
Application: Perform this procedure to select the label role. ACTION Depress the [DATBLK] button of the Main Menu window The Track Display Configuration window is displayed. RESULT
Click on the [ROLE] icon.

DOCUMENT N: 0029200000000MA03
ACTION
RESULT
A pop-up menu with the available formats is displayed. The menu options are: APP- Approach ACC- Route TWR- Tower Once the pop-up menu is displayed, select the desired label role format Automatically, label role is modified.
2.3.13.4 Action: History Tracks =>{[DATBLK] -> HISTORY}

Application: Perform this procedure to select the number of past positions (historic) to be displayed for each track. ACTION RESULT LB click on the [DATBLK] icon situated in the Main Menu window. The Track Display Configuration window is displayed.
Page 2-181
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
Click on the [HISTORY] arrows (up and down).
The time unit (number) is increased or reduced in 1-minute unit (with a maximum of 10 and a minimum of 1).
2.3.13.5 Action: Select Total Track Label Format =>{[DATBLK] -> LIST FONT}
Application: Perform this procedure to select the size for list font. ACTION RESULT Depress the [DATBLK] button of the Main Menu window The Track Display Configuration window is displayed.
Page 2-182
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
Click on the [LIST FONT] icon.
A pop-up menu with the available sizes is displayed. The menu options are: S Small M Medium L Large Once the pop-up menu is displayed, select the desired size for list font Automatically, list font is resized.
2.3.13.6 Action: Delay Handover => {[DATBLK] -> DELAY HANDOVER}

Application: Perform this procedure to select the delay for handover procedures.
DOCUMENT N: 0029200000000MA03
ACTION LB click on the [DATBLK] icon situated in the Main Menu window.
RESULT
The Track Display Configuration window is displayed.
Click on the [DELAY HANDOVER] arrows (up and down).
The time unit (number) is increased or reduced in 1-minute unit (with a maximum of 10 and a minimum of 1).
2.3.13.7 Action: Stretching factor => {[DATBLK] -> STRETCHING FACTOR}

Application: Perform this procedure to select the percentage of screen length that a track leader line length can have. ACTION RESULT LB click on the [DATBLK] icon situated in the Main Menu window. The Track Display Configuration window is displayed.
Page 2-184
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
Click on the [STRETCHING arrows (up and down).
FACTOR] The percentage is increased or reduced in 10percentaje units (with a maximum of 80 and a minimum of 10.
Re-allocate a track label
The track can only be moved the percentage of the length screen previously selected.
2.3.13.8 Action: Route Font => {[DATBLK] -> ROUTE FONT}

Application: Perform this procedure to select the number of reports. ACTION RESULT LB click on the [DATBLK] icon situated in the
DOCUMENT N: 0029200000000MA03
ACTION Main Menu window.
RESULT The Track Display Configuration window is displayed.
Click on the [ROUTE FONT] arrows (up and down).
A pop-up menu with the available sizes is displayed. The menu options are: S Small M Medium L Large Select the desired route font size by clicking on it. Automatically, the size is displayed on the track symbols and characters.
Page 2-186
DOCUMENT N: 0029200000000MA03
2.3.13.9 Action: Route Marks => {[DATBLK] -> ROUTE MARKS}

Application: Perform this procedure to include graduated marks in graphical route display. ACTION RESULT LB click on the [DATBLK] icon situated in the Main Menu window. The Track displayed. Display Configuration window is
Click on the [ROUTE MARKS] bi-state icon.
The route marks are active. Click on NM row bi-state icon. (or in MIN row bi-state icon)
The graduation is performed by NM units. Click on the icon. A pop-up menu is displayed with available values. Click in one of them and the selection is performed.
Page 2-187
DOCUMENT N: 0029200000000MA03
2.3.13.10 Action: Global Track Label Orientation => {[DATBLK] -> LABEL ORIENTATION}
Application: Perform this procedure to select the delay for handover procedures. ACTION RESULT LB click on the [DATBLK] icon situated in the Main Menu window. The Track Display Configuration window is displayed.
For a concrete orientation click in the arrow in Label Orientation option that represents the desired orientation.
For changing the label orientation in steps of 45 (clockwise), click in the symbol in the centre of Label orientation option . Every track displayed changes its orientation to the selected one.
Page 2-188
DOCUMENT N: 0029200000000MA03
2.3.13.11 Action: Track label lines to display selection => {[DATBLK] -> NUMBER OF LINES}
Application: Perform this procedure to adjust the number of lines displayed in the track label when the track is not selected. ACTION RESULT LB click on the [DATBLK] icon situated in the Main Menu window. The Track Display Configuration window is displayed.
LB click in Number of lines icon displays the popdown with available values for lines to be displayed in track label (2-5 and FULL).
Select one value in pop-down. Every track label in SDD is displayed with the selected number of lines, and will only display its full content when a track is selected.
Page 2-189
DOCUMENT N: 0029200000000MA03
2.3.14 Range Bearing Lines [RBL OFF] Icon

The [RBL OFF] icon is used to delete the display of all the active RBLs in the screen.
Figure 2-94: [RBL OFF] Icon
2.3.14.1 Action: Remove RBLs

Application: Perform this procedure to remove all active RBLs from the SDD SIT Area. ACTION RESULT LB click on the [RBL OFF] button of the Main Menu window All active RBLs are removed from the screen. Following figure shows the removing action; first window displays the screen including all the RBLs; and second window displays the screen without the RBLs.
2.3.15 Label Orientation [ORI OFF] Icon

By clicking on the [ORI OFF] icon, the track labels with manually selected position, return to their default position.
Figure 2-95: [ORI OFF] Icon
2.3.15.1 Action: Total Tracks Label Orientation => {[ORI OFF]}

Application: Perform this procedure to bring all tracks labels back to their default position. ACTION RESULT LB click on the [ORI OFF] button of the Main Menu window
Page 2-190
DOCUMENT N: 0029200000000MA03
ACTION
RESULT All track labels with manually selected position return to the default one.
2.3.16 [RANGERINGS] Icon

The [RANGERINGS] icon is used to activate or inhibit the display of range rings.
Figure 2-96: [RANGERINGS] Icon Range rings is a set of ten (10) concentric circles whose radius are differenced in 5 NM among them.
Figure 2-97: Range Rings Display
2.3.16.1 Action: Activation/ Inhibition of Range Rings => {[RANGERINGS]}

Application: This functionality is used to display ten concentric rings, whose radius differences is fixed (5 NM), to measure distances in SIT Area.
Page 2-191
DOCUMENT N: 0029200000000MA03
ACTION LB click on the [RANGERINGS] icon to activate the Range Rings display.
RESULT
If a previous range rings action was performed, range rings are displayed in previous selected position. Mouse pointer changes to a YELLOW cross mark.
LB click in a position in SIT area. Range rings are displayed, centred in selected position.
LB click on the [RANGERINGS] icon to inhibit the Range Rings display. Range rings are inhibited to display.
2.3.17 [ROU OFF] Icon

By clicking on the [ROU OFF] icon, all FP routes which are displayed on the screen, are deleted.
Figure 2-98: [ROU OFF] Icon
2.3.17.1 Action: Routes Display Cancel => {[ROU OFF]}

Application: Perform this procedure to cancel all graphical route display. ACTION RESULT LB click on the [ROU OFF] button of the Main Menu window
DOCUMENT N: 0029200000000MA03
ACTION
RESULT All graphical route displays are cancelled.
2.3.18 Aural Alarms Cancel [ALR CNL] Icon

This icon is used to cancel all aural alarms due to any reason.
Figure 2-99: [ALR CNL] Icon
2.3.19 [QNH] Icon

This icon displays the QNH (Altimeter sub-scale sitting to obtain elevation when on the ground) and the zone where is taken from. It displays three fields: Airport: Aerodrome where the pressure zone is located Pressure: Current pressure value for that zone (in mb) Height: Transition Level (in hundreds of feet)
Figure 2-100: QNH Window When clicking on the QNH window, a pop-up menu is displayed to select the defined QNH and corresponding zone.
Page 2-193
DOCUMENT N: 0029200000000MA03
Figure 2-101: QNH and Zone Selection Pop-Up Menu
2.3.20 Automatic Orientation of Track Labels [OVERLAP] Icon

The [OVERLAP] switch is used to activate or inhibit the function for the automatic orientation of track labels.
Figure 2-102: [OVERLAP] Switch
2.3.21 MTCD Conflicts [CONFL] Icon

The [CONFL] switch is used to activate or inhibit the display of MTCD alarm in track labels.
Figure 2-103: [CONFL] Switch
2.3.22 [AREAS] Icon

The [AREAS] switch is used to activate or inhibit the display of the active Restricted Areas.
Figure 2-104: [AREAS] Switch
2.3.22.1
Action: Activation/ Inhibition of Restricted Areas => {[AREAS]}
Application: Perform this procedure to activate/ inhibit the display of the active restricted areas in the SDD SIT Area.
Page 2-194
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
LB Click on the [AREAS] switch of the Main Menu window. The colour switch turns to YELLOW and the predefined restricted areas are displayed.
Clicking again on the [AREAS] switch The restricted areas are removed from the screen and the switch colour turns to Background.
2.3.23 Track Velocity Vector Activation/ Inhibition [VELVECT] Icon

Use the [VELVECT] icon to activate or inhibit the display of tracks extrapolation vectors (velocity vectors). The activation and inhibition also toggles by pressing <Alt> + <V>.
Figure 2-105: [VELVECT] Icon In addition, the operator may display/hide the extrapolation vector of just one track by clicking with the RB on the label track field. This selection is independent of the activation of the [VELVECT] icon.
2.3.24 Meteorological Data [METEO] Icon

The [METEO] switch is used to activate or inhibit the meteorological information display.
Figure 2-106: [METEO] Switch When selected, the system displays the "Meteorological Data Display".
2.3.24.1 Action: Activation/Inhibition of Weather Data => {[METEO]}

Application: Perform this procedure to activate/inhibit the display of PSR weather data.
Page 2-195
DOCUMENT N: 0029200000000MA03
ACTION LB click on the [METEO] switch of the Main Menu window.
RESULT
The switch colour turns to YELLOW and the weather data is displayed. Click again on the [METEO] switch. The weather data are inhibited (the switch turns to Background colour).
2.3.25 Range Bearing Alarms [RBL ALM] Icon

The [RBL ALM] switch is used to activate or inhibit the Range Bearing Alarms. The colour switch provides following information: Figure 2-107: [RBL ALM] Switch
2.3.26 [QUICKEST] Icon

This icon is used to directly perform an EST action without accessing the FP template.
Figure 2-108: [Q EST] Icon When [QUICKEST] icon is clicked a new window is displayed. First, user has to fill out the CALLSIGN field and so, the rest of the fields are retrieved automatically. Then, user can enter the FIX, ETO and CFL to perform an EST operation.
Figure 2-109: EST window Table 20:

Field
CALLSIGN FIX Fix name
EST Window. Edition Area

Description
Aircraft identification
Page 2-196
DOCUMENT N: 0029200000000MA03
SPEED ETO CFL CSSR
Aircraft speed Estimated time over fix. Flight level of the aircraft when fly over the fix. SSR code
Table 21:
Icon/Switch
UPDATE CLEAR
EST Window. Command Area

Command
Perform the EST action over the entered fix (if data are correct). Delete the data displayed on the EST Window.
2.3.26.1 Action: Quick Estimate Operation

Application: Perform this procedure to carry out an EST operation directly, entering the Fix point, ETO, CFL and Speed of an owned track (Callsign or SSR code). ACTION RESULT Depress the [QUICKEST] button of the Main Menu window. A window to edit the Fix point, ETO, CFL and Speed is displayed
Enter the callsign value in the corresponding field and then [ENTER]. Some fields are filled out automatically and others remain blank. Fill out the fields and click [UPDATE] The window is closed and the estimated time over the entered fix point is performed. To cancel the action: Release the [QUICKEST] button. The window is closed without validating the entered data.
Page 2-197
DOCUMENT N: 0029200000000MA03
2.3.27 Meteo Messages [MET MSGS] Icon

Click on this button to display meteo messages. Those messages are classified by Airport and by type.
Figure 2-110: [MET MSG] Switch This function allows the controller to request for the different meteorological information by means of a window corresponding to the selected message. Up to 15 airports may be available for meteorological information. Click on the button with the airport name whose messages shall be displayed. The airport marked with YELLOW is the one whose messages are being displayed. The meteo messages available for selection are: ATIS or Airport Traffic Information System. A continuous broadcast of airport information, commonly found at tower-controlled airports. It usually includes weather information, runways in use, and any important notices. The information is normally updated hourly, and each update is identified by a letter in the phonetic alphabet (alpha, bravo, charlie, etc.) AIRMET or Airmen's Meteorological Information, is a weather advisory issued by a meteorological watch office for aircraft that is potentially hazardous to low-level aircraft /aircraft with limited capability. Compared to SIGMETs, AIRMETs cover less severe weather: moderate turbulence and icing, surface winds of 30 knots, or widespread restricted visibility. AIRMETs are broadcast on the ATIS at ATC facilities, and are referred to as Weather Advisories. AIRMETs are valid for six hours. There are three types of AIRMET, all identified by a phonetic letter: S (Sierra), T (Tango), and Z (Zulu). Sierra describes IFR conditions or mountain obscuration. Tango describes turbulence, high winds, or no convective Low Level Wind Shear. Zulu deals with icing and freezing levels. METAR or Meteorological Reports-Aviation Routine Weather Report is a format for reporting weather information. A METAR weather report is predominantly used by pilots in fulfilment of a part of a pre-flight weather briefing, and by meteorologists, who use aggregated METAR information to assist in weather forecasting. METAR reports typically come from airports or permanent weather observation stations. Reports are typically generated once an hour; however, if conditions change significantly, they may be updated in special reports called SPECI's. Some reports are encoded by an automated airport weather station located at airports, military bases and other sites. Some locations still use-augmented observations, which are recorded by digital sensors and encoded via software, but are reviewed by certified weather observers or forecasters prior to being transmitted. Trained observers or forecasters, who manually observe and encode their observations prior to their being transmitted, may also take observations. SIGMET or Significant Meteorological Information is a weather advisory that contains meteorological information concerning the safety of all aircraft. There are two types of SIGMETs, convective and non-convective. The criteria for a non-convective SIGMET to be issued are severe or greater turbulence over a 3000 square mile area or severe or greater icing over a 3000 sq mile area or IMC conditions over a 3000 sq mile area due to dust, sand, or volcanic ash.
DOCUMENT N: 0029200000000MA03
This information is usually broadcast on the ATIS at ATC facilities. A SIGMET is a forecast valid for up to four hours. They are assigned an alphabetic designator from N (November) through Y (Yankee) of course, excluding S and T. A Convective SIGMET is issued for convection over the Continental U.S. Convective SIGMETs are issued for an area of thunderstorms affecting an area of 3000 sq miles or greater, a line of thunderstorms at least 60 nm long, and/or severe or embedded thunderstorms affecting any area that are expected to last 30 minutes or longer. TAF or Terminal Area Forecast is a format for reporting weather forecast information, particularly as it relates to aviation. Generally, a 9- or 12-hour forecast, though some TAFs can cover an 18- or 24-hour period, it complements and uses similar encoding to METAR reports. A human forecaster based on the ground always produces TAFs. For this reason, there are far fewer TAF locations than there are METARs. TAFs are much more accurate than Numerical Weather Forecasts, since they take into account local, small-scale, geographic effects. SPECI is special weather report issued when there is significant deterioration or improvement in airport weather conditions, such as significant changes of surface winds, visibility, cloud base height and occurrence of severe weather. The format of the SPECI report is similar to that of the METAR and the elements used have the same meaning. The identifier METAR or SPECI at the beginning of the weather report differentiates them. SNOWTAM is a message describing the conditions of the runways, taxiways and apron at an aerodrome. GAMET is a message emitted for high traffic density of low-level flights (under FL100); and it includes information about meteorological phenomena hazardous for those lowlevel flights (e.g. strong wind, low visibility, thunderstorms, significant clouds, icing and turbulence) as well as additional information required by low-level flights (synoptic situation, surface wind, upper-air wind, upper-air temperature, visibility, cloud, freezing level and lowest QNH).
Page 2-199
DOCUMENT N: 0029200000000MA03
Figure 2-111: MET Window This window includes options to select airports and meteo message types, and a visualization area.
2.3.27.1 Airport Selection Area
Figure 2-112: Airport Selection Area

DOCUMENT N: 0029200000000MA03
This area includes one button for each airport; and each airport can be selected for meteo messages display clicking on it. If button is in WHITE colour, meteo messages display for the airport is inhibit; if button is in YELLOW colour, meteo messages display for the airport is active.
2.3.27.2 Message Type Selection Area
Figure 2-113: Message Type Selection Area This area includes a bi-estate icon for each meteo message type, that can be active (YELLOW colour) or inhibit (WHITE colour). When each type is active, the respective Message List Display Area is displayed. If it is inhibit, the respective Message List Display Area is hidden for display.
2.3.27.3 Message List Display Area
Figure 2-114: Message List Display Area This area is filled with the list of meteo messages (one area for each meteo message type), one row for each message; and it includes a scroll bar, active when the list of messages is greater than the area size.
Figure 2-115: Message List Display Area Airport selection Clicking in the airport name (EPBY in this example), a list of airports is displayed and can be selected the airport whose messages are to be displayed in this list.
2.3.27.4 Message Display Area
Figure 2-116: Message Display Area If a message is selected (click in a message in a message list display area), it is detailed in this area, and can be acknowledged by clicking in ACK button. It includes a scroll bar, active when the list of messages is greater than the area size.
2.3.28 System Messages [SYS MSG] Icon

This icon is used to display/close the System Messages window.
Figure 2-117: [SYS MSG] Icon
Page 2-201
DOCUMENT N: 0029200000000MA03
It is a message list generated by the system, which warn the controller about the important changes in the system, as well as the errors that have taken place. When a message is received, the icon starts blinking. The blinking stops when the window is displayed. The messages are deleted when clicking on the [ACKN] icon situated on the bottom centre of the System Messages window.
Figure 2-118: System Messages Window The vertical scroll bar allows the visualization of all messages, which are not in view due to window size. The messages are sorted by last time of reception. The information displayed on the System Messages window is described in following table: Table 22: System Messages Window. Information Display Item Time Date-Message Text Description System time at which the system message was generated (HH:MM) Date(YYYY-MM-DD)-Brief description of the message
2.3.29 Finder [FINDER] Icon

This icon is used to find and mark the position of an element.
Figure 2-119: [FINDER] Icon When [FINDER] icon is clicked a new window is displayed. User has the following options: Enter a coordinate (Latitude, longitude) to find it on the map, Enter the airport code, Enter the fixpoint name, Enter a Callsign, Enter an SSR.
Page 2-202
DOCUMENT N: 0029200000000MA03
Figure 2-120: FINDER window After an element is entered, the exact position of the element is displayed in the main window.
2.3.29.1 Action: Display the position of an element => {[FINDER]}

Application: Perform this action to locate significant points (or any point by a its coordinates) in the FIR. ACTION RESULT Click on [FINDER] button of the Main Menu window. Finder window is displayed with the available possibilities.
Click on the button with the name of the desired element type to be displayed. The fields for the element identification are displayed as available for data enter.
Page 2-203
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
Enter the correct value for requested data and click [OK] button. If entered criteria was LAT LON, AIRPORT or POINT, the element is marked in the SIT Area.
If entered criteria was Callsign, then the pointed is situated over the track that matchs the entered Callsign.
Page 2-204
DOCUMENT N: 0029200000000MA03
ACTION
RESULT If entered criteria was SSR, then the FINDER Window will display the Callsign that matchs the entered SSR Code.
To cancel the action: Click on [X] icon in the Finder Window. The window is closed without validating the entered data.
2.3.30 SSR Filter [SSRF] Icon

This icon is used to filter by SSR code criteria. It will filter the tracks that match the SSR code criteria described in it (by SSR code range or by an expression) and will only affect to tracks that are not owned, not advanced and not in alert status.
Figure 2-121: [SSRF] Icon
Figure 2-122: SSR Filter window SSR Filter: By range: the system will not display the tracks not owned, not advanced and not in alert status which SSR code are in the code range described by minimum and maximum values entered.
Page 2-205
DOCUMENT N: 0029200000000MA03
By expression: the system will not display the tracks not owned, not advanced and not in alert status which SSR code check the expression defined by numbers and * (* is the representation for any one-digit value). The SSR filter requires the Enable bi-state activation for its filter function activation.
2.3.30.1 Action: Track filter by SSR code => {[SSRF]}

Application: Perform this action to filter tracks display in SIT area by SSR criteria. This window allows to filter by a SSR code range or by an unique SSR code. ACTION RESULT Click on [SSRF] button of the Main Menu window. SSR filter window is displayed with the available functions.
This window can filter tracks both by an SSR code or by an SSR code range. Filter by SSR Range: Click in RANGE bi-state icon. The MIN and MAX edition fields are displayed as available. Enter four-digit values for MIN and MAX SSR codes (MIN value must be smaller than MAX value), in order the SSR filter will apply in the range between the entered SSR codes. Click in Enable bi-state button to activate the filter. To validate the action: Click [APPLY] button. The window is closed and the tracks with its SSR code between the entered range are displayed. To cancel the action: Click on [X] icon in the Finder Window. The window is closed without validating the entered data. Filter by SSR Code Expression: Click in EXPR bi-state icon.
DOCUMENT N: 0029200000000MA03
ACTION By clicking in each numbered box a pop-up menu is displayed with numbers from 0 to 9. Clicking in the value for the digit performs its selection. After selecting the four values for SSR code, click in Enable bi-state button to active the filter. To validate the action: Click [APPLY] button.
RESULT
The window is closed and just the track with the selected SSR code is displayed. To cancel the action: Click on [X] icon in the Finder Window. The window is closed without validating the entered data.
2.3.31 [F 3D] Icon

This icon is used to filter tracks inside a cylinder zone.
Figure 2-123: [F 3D] Icon The system allows to create up to five cylinder zones where tracks will be hidden for display. Tracks hidden for display in those zones are tracks not owned, not advanced and not in alert status. Each cylinder zone is created entering the centre point, the radius and the minimum and maximum level where filter will apply. The centre point can be defined by a lat-long coordinate or by a fixpoint.
Figure 2-124: 3D Filter window

DOCUMENT N: 0029200000000MA03
2.3.31.1 Action: 3D Filter => {[F 3D]}

Application: Performs this action to filter track display in SIT area. F 3D creates a cylindrical area where to filter tracks display. ACTION RESULT Click on [F 3D] button of the Main Menu window. 3D Filter window is displayed with the available possibilities.
Each zone is created entering the centre lat-long coordinates (or fixpoint), the radius and minimum and maximum level values. To activate the defined zone, click in the bi-state icon that is situated in the row of defined values. To activate the 3-D filtering function (the defined and active cylinder zones, Enable bi-state icon must be active. A drawing help is included by the icon, and allows the manual definition of 3D filter.
To validate the action: Click [APPLY] button. The window is closed and the defined 3D filters are active.
Page 2-208
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
To cancel the action: Click on [X] icon in the Finder Window. The window is closed without validating the entered data.
2.3.32 [ARROWS] Icons

When clicking on these icons, different actions in relation to the SDD SIT Area are performed.
Figure 2-125: Arrows Table 23: Arrows Description Symbol Description Decrease the presentation range in defined intervals. Increase the presentation range in defined intervals. Perform a left scrolling movement within the screen as a horizontal scroll bar. Perform a right scrolling movement within the screen as a horizontal scroll bar. Perform an upwards-scrolling movement within the screen as a vertical scroll bar. Perform a downwards-scrolling movement within the screen as a vertical scroll bar.
Page 2-209
DOCUMENT N: 0029200000000MA03
2.3.32.1 Action: Scrolling on the SDD SIT Area => {[SCROLLING ARROWS]}
Application: Perform this procedure a scrolling movement within the screen. ACTION RESULT Click on the corresponding [ARROW] icon situated in the Main Menu window.
The scrolling movement will be performed left, up, right and down depending on the selected icon.
2.3.32.2 Action: Position Visualization Increase or Decrease

Application: Perform this procedure to allow the visualization of a greater zone of the SDD SIT Area. Increase => {[ZOOM ARROW]} or {<->} ACTION There are two ways of enlarge the screen presentation. By clicking on the button, successively. In both cases, the presentation range is expanded in discrete steps. RESULT
By pressing on the <-> key, successively Decrease => {[ZOOM ARROW]} or {<+>} Application: Perform this procedure to allow the visualization of a smaller zone of the SDD SIT Area. ACTION RESULT There are two ways of enlarge the screen presentation. In both cases, the presentation range is contracted in discrete steps.
By clicking on the
button, successively.
By pressing on the <+> key, successively
2.3.33 SDD Identification

It is a non-editable field that includes information about the login user, SDD identification and its role. SDD roles can be: APP: approach ACC: enroute
DOCUMENT N: 0029200000000MA03
TWR: tower
Figure 2-126: SDD Identification Icon
2.3.34 [PRINT LISTS] Icon

When clicking on this icon, every list with FPs inside is printed in selected laser printer, with all those data.
Figure 2-127: Print Lists Icon
2.3.35 Printer Icon

When clicking on this icon, a window with all available laser printers is displayed. It includes all printers and a YELLOW mark on selected one.
Figure 2-128: Printer Icon The Set as default printer allows to change the predefined printer to the currently selected one. The name of selected printer is displayed in SDD Printer button.
Figure 2-129: SDD Printer Icon
2.3.36 [LOGIN] Icon

When clicking on this icon, the position is frozen, that is, no action can be performed. This functionality is performed to change the position user.
Figure 2-130: [LogIn] Icon
Page 2-211
DOCUMENT N: 0029200000000MA03
2.3.36.1 Action: Change User => {[LOGIN]}

Application: Perform this procedure to change the current position user. ACTION RESULT Click on the [LOGIN] icon situated in the Main Menu window. The position is frozen. At the same time, the Login window is displayed.
Enter data in the corresponding fields. Finish the action by pressing on the <Enter> key. The position is unfrozen with a new user.
2.3.37 [LOGOUT] Icon

When clicking on this icon, the position is frozen, that is, no action can be performed. Figure 2-131: [LogOut] Icon At the same time, the confirmation window is displayed and after accepting, Login window is displayed to unfreeze the position.
Figure 2-132: Confirmation Window
Figure 2-133: Login Window As shown in previous figure, this window consists of two fields. The first one identifies the positions user and the second one is the password for entering.
Page 2-212
DOCUMENT N: 0029200000000MA03
If the data are properly entered, when finishing, press <Enter> key and the action will be validated coming back the position to normal operation.
2.3.37.1 Action: Freeze the Position => {[LOGOUT]}

Application: Perform this procedure to freeze any type of action to be performed in the position. ACTION RESULT Click on the [LOGOUT] icon situated in the A confirmation window is displayed. Main Menu window.
Click on [YES] button.
The position is frozen. At the same time, the Login window is displayed.
Enter data in the corresponding fields. Finish the action by pressing on the <Enter> key. The position is unfrozen.
2.3.38 Other Windows

The operator cannot open or close some windows for special situations. Some circumstances automatically display these windows and when the circumstances end, these windows disappear from the screen. The user can only change their position on the screen. These windows are following described: Lost List, Hold List and Conflict List.
2.3.38.1
Lost List
When radar information is lost for more than a certain number of radar scans, the track is terminated and the information associated to the track is transferred to the Lost List. When radar information is retrieved, the track and the label are automatically re-established in the screen, provided that the aircraft has an ICAO or domestic transponder and has an associated flight plan.
Page 2-213
DOCUMENT N: 0029200000000MA03
Figure 2-134: Lost List For correlated PSR tracks, this re-establishment must be undergone manually. The flight plan is deleted from the Lost List when the label is re-established or until a time (design parameter) has expired. The controller can automatically inhibit the flight plan deletion from the Lost List. The flight plan deletion also causes its deletion from the Lost List.
2.3.38.1.1
Information Area
Table 24: Lost List. Information Area
The information displayed on the Lost List goes as follows: Field L (LOST FP) by default C (Correlated FP) - (Non-correlated FP) Status Indicator (1 character) H (Holding FP) F (FP in conflict) A (Correlation Ambiguity) S (Synthetic track) For tracks in alert, this field is displayed in RED colour. C/S ADES AFL (3 digits) CFL (3 digits) LOCK (1 character) <number> Aircraft Indicator Destination Airport Actual Flight Level Cleared Flight Level D (Deleted after time-out) K (Inhibited for deletion) Total number of Lost Flights. It also provides a menu to sort flights Meaning
Some of the Lost List fields have the capability of performing operational actions. Following table describes which are the sensitive fields and the undergone actions. Table 25: Lost List. Sensitive Fields Options Field Status Indicator C/S Deletion Indicator (LOCK)
Option Display the FP pop-up menu (LB) Decode Callsign / SSR Code (LB) Hand Over (RB) Toggle the deletion type (D or K)
Page 2-214
DOCUMENT N: 0029200000000MA03
2.3.38.2
Hold List
This list gathers the information related to all the tracks, which are in holding status. The window is automatically displayed when the system detects that a tracks is in holding status (action performed by the controller). The window remains displayed until no track is in holding status. Each line on the list is related to a different track in holding status. Track label in holding status displays a symbol before its callsign.
Figure 2-135: Hold List
2.3.38.2.1
Information Area
The Hold List contains the following information: Table 26: Hold List. Information Area Field H (Hold) Status Indicator (1 character) C/S ATYP AFL CFL FIX ETO ETA ADES <number> F (Conflict) L (Lost) Aircraft Identification (7 characters) / SSR code Aircraft Type Actual Flight Plan Level Cleared Flight Level Fixpoint where the aircraft is in holding Estimated Time Over a Fix Estimated Time of Arrival Destination Aerodrome Total number of flights in holding status. It also provides a menu to sort the flights Description
Some of the Hold List fields have the capability of performing operational actions. Following table describes which are the sensitive fields and the undergone actions. Table 27: Hold List. Sensitive Fields Options
Page 2-215
DOCUMENT N: 0029200000000MA03
Field Status Indicator C/S Mode C or H
Option Display the FP pop-up menu (LB) Decode Call Sign / SSR Code (LB) Hand Over (RB) Delete the flight plan from the list (RB)
Hold List can be sorted by every field, clicking on fields name, flight plans will be sorted by this field.
2.3.38.2.2
ACTION
Action: Enter/ Leave Hold List

RESULT
Application: Perform a hold action over an owned track. Click in a controlled track callsign (in track label or in a flight plan list) Click in Hold option. The Callsign Menu is displayed. The Hold field is displayed.
Enter the hour (HHMM) the track will enter in The Hold List is displayed (if it was not) and Hold status and confirm the action by clicking contains the data corresponding to the track. The [Accept] button. Status Indicator field of the Hold List displays an H. The track label displays a YELLOW # symbol before its Callsign.
Click in the track callsign (in track label or in a flight plan list. Click in Unhold option
The Callsign Menu is displayed. The track leaves hold status, and hold list.
Page 2-216
DOCUMENT N: 0029200000000MA03
2.3.38.3
COORD IN/OUT Lists
These lists includes the information related with flight plans that have pending coordination dialogue, and includes, in COM field, the current coordination status. From COM field, the Coordination window can be displayed, allowing the completion of coordination dialogue. These lists are automatically displayed when any flight plan has pending coordination dialogue, and automatically disappears when the coordination dialogue is completed.
Figure 2-136: Coordination Lists Table 28: Coordination Inbound List. Information Area Field H (Hold) Status Indicator (1 character) A C C/S ADEP ADES EOBT F (Conflict) L (Lost) ADS Status CPDLC Status Aircraft Identification (Callsign) Departure Aerodrome. Destination Aerodrome Estimated Off-Block Time. It may be filled with "C"; which indicates the reception of CTOT indication. COPX ETO XFL Coordination Fixpoint Estimated Time Overfly Planned Entry/ Exit Level With (*), Activation level With (F), the RFL from the FP COOR COM <number> Coordination Dialogue Establishment Coordination status Total number of flights in holding status. It also provides a menu to sort the flights Description
2.3.38.4
Conflict List
This list gathers the information related to all the tracks in STCA conflict.
DOCUMENT N: 0029200000000MA03
The window is automatically displayed when the System detects that there are tracks in STCA conflict. The window remains displayed until no track is in STCA conflict. Each line on the list is related to a different STCA conflict (two tracks) and has a different colour depending if the aircraft is in prediction status or violation status. Prediction (PR) Violation (VI) Yellow Red
Figure 2-137: Conflict List
2.3.38.4.1
Information Area
The Conflict List contains the following information: Table 29: Conflict List. Information Area Field Call Sign / SSR Code Call Sign / SSR Code CDIS MDIS <number> Description Aircraft 1 Identification (7 characters) / SSR code. Aircraft 2 Identification (7 characters) / SSR code. Current distance between the aircrafts in conflict. Minimum distance reached between two flights in STCA conflict. Total number of elements in the Conflict List
Conflict List can be sorted by every field, clicking on fields name, flight plans will be sorted by this field.
2.3.38.5
APW List
This list gathers the information related to all tracks in APW conflict. When the System detects that there are tracks that will enter in a restricted area, the APW list automatically displays. The window remains displayed until no track is in APW conflict (prediction or intrusion).
Figure 2-138: APW List
Page 2-218
DOCUMENT N: 0029200000000MA03
2.3.38.5.1
Information Area
Table 30: APW List. Colours Code
Meaning
Colour
YELLOW RED
Track in APW prediction Track in APW intrusion
The APW List contains following information: Table 31:

Field
APW List. Information Area

Description
L (LOST FP) by default C (Correlated FP) - (Non-correlated FP) Status Indicator H (Holding FP) F (FP in conflict) A (Correlation Ambiguity) S (Synthetic Track) C/S SSR <number> Aircraft Identification (7 characters) SSR Code Total number of elements in the APW List
APW List can be sorted by every field, clicking on fields name, flight plans will be sorted by this field.
2.3.38.6
MSAW List
This list gathers the information related to all tracks in MSAW alert. When the System detects that there are tracks that may be in danger by minimum safe altitude, the MSAW list automatically displays. The window remains displayed until no track is in MSAW conflict.
Figure 2-139: MSAW List
Page 2-219
DOCUMENT N: 0029200000000MA03
2.3.38.6.1
Information Area
Table 32: MSAW List. Colours Code
Meaning
Colour
YELLOW RED
Track in MSAW prediction Track in MSAW intrusion
The MSAW List contains following information: Table 33:

Field
MSAW List. Information Area

Description
L (LOST FP) by default C (Correlated FP) - (Non-correlated FP) Status Indicator H (Holding FP) F (FP in conflict) A (Correlation Ambiguity) S (Synthetic Track) C/S SSR <number> Aircraft Identification (7 characters) SSR Code Total number of elements in the MSAW List
MSAW List can be sorted by every field, clicking on fields name, flight plans will be sorted by this field.
2.4 SDD General Information Area in Supervision Mode

The SDD in supervisor mode has some additional functionality to let the control and supervision of other workstations. When the SDD is in Supervisor mode the [ST] icon, in the screen top left hand corner, is enabled. The screen of the Supervisor is the following:
Page 2-220
DOCUMENT N: 0029200000000MA03
Figure 2-140: Screen of the Technical Supervisor
Figure 2-141: Technical Supervisor Mode Role Indicator The Supervisor has the following special functionalities: Only the supervisor can distribute to all the workstations the maps that he created locally.

The supervisor can visualize all the plots of each radar (each one in different colour). All alerts are displayed in Supervisor SDD.
DOCUMENT N: 0029200000000MA03
Supervisor SDD has not Sectorization. The logs and the status of another work positions are displayed from a Supervisor SDD.
2.4.1 Display of Plots

The [ST] icon is used to show if the Supervisor Mode is enabled. When the SDD is in Supervisor Mode, a pull-down menu is displayed if the [ST] icon is clicked. User must select the radars for displaying the generated plots. One different colour is activated to each radar. Then, the plots are displaying at the SIT area.
Figure 2-142: Display of plots
2.4.1.1 Action: Display the plots at SDD SIT Area

Application: Perform this procedure to display the plots emitted from radars. For each radar, the plot is displayed in a different colour. ACTION RESULT LB click on the [ST] button at the General Information Area. The pull-down menu with the radars is displayed.
Depress the buttons from the radar of which the User wants to see the corresponding plots. As a result the button changes its colour. Press [OK] button.
Page 2-222
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
The plots of the selected radars are displayed on SDD SIT Area.
Release the previously selected radars buttons. The plots of the selected radars are not showed now. CB click on the Radars menu. The pull-down menu disappears.
2.4.2 [RADAR] Icon

This icon is used to display the Radar Status Window, which includes a list of available radars and their status (by a colour code).
Figure 2-143: [RADAR] Switch
Page 2-223
DOCUMENT N: 0029200000000MA03
Figure 2-144: Radars Menu Radar Icon is displayed in Main Menu area in a colour that means: Table 34: Radar Colour Code Colour GREEN RED ORANGE Description All radars are ON and operative. At least one radar is manually changed to OFF at CMD, or the radar RDCU line is not operative. At least one radar is manually changed to MANTENANCE at CMD, and the rest are ON and operative.
RED colour is the most restrictive, so if any radar is OFF or its RDCU line is not operative, radar icon will display in Red, even the rest of them are ON, or are in MANTENANCE mode. ORANGE colour is more restrictive than GREEN colour, so if any radar is in MANTENANCE mode, radar icon will be displayed in ORANGE colour, even the rest are ON. Table 35: Radar Status Window Radar Icon in Main Menu Radar Status Window
Page 2-224
DOCUMENT N: 0029200000000MA03
Radar Icon in Main Menu
Radar Status Window
2.4.3 [USERS] icon

The [USERS] icon is used to show the log of the SDD.
Figure 2-145: Users icon Upon clicking on the [USERS] icon, a new window is displayed with all the SDD of the System. The user may check the status and the log of each SDD.
Figure 2-146: USERS window
2.4.3.1 Action: Users information

Application: Perform this procedure to display the status and the log of all SDDs in the System. ACTION RESULT Depress the [USERS] button at the Main Menu window. The window with all SDDs in the System is displayed.
Page 2-225
DOCUMENT N: 0029200000000MA03
ACTION
RESULT
RB click on one/several icon/s of a SDD The log is showed at the button, and also information is displayed about this SDD on the information panel.
Release [USERS] button. The USERS window is closed.
2.4.4 LMG in Supervisor Mode

In addition of the main functionality of LMG tool, Supervisor Mode also includes the local maps remote copy functionality. Remote Copy allows the copy of maps in remote SDD positions.
Figure 2-147: LMG Tool in Supervisor Mode The Remote Copy function provides the following buttons:
DOCUMENT N: 0029200000000MA03
Maps button: allow the selection of local maps to copy. It displays a pop-down menu with available maps to copy. The available options are LOCALX for a single local map or ALL MAPS to copy all local maps. SDDs button: allow the selection of SDD positions where to copy the local maps. It displays a pop-down menu with available SDDs where to copy. The available options are SDDX for a single SDD where to copy local maps, or ALL SDD, to copy local maps in all available SDDs. Copy button: performs the remote copy of selected maps in selected positions.
2.4.4.1 Action: Local maps remote copy => {[LMG]}

Application: Perform this procedure to display the status and the log of all SDDs in the System. ACTION RESULT In Supervisor Mode, LB click in [LMG] button. LMG tool is displayed.
Check that local maps are defined, or create some. LB click in [ALL MAPS] button and select the maps to install. LB click in [ALL SDDS] button and select the SDD where to install. LB click in [COPY] button. The maps are copied in SDDs selected.
Page 2-227
DOCUMENT N: 0029200000000MA03
Page 2-228
DOCUMENT N: 0029200000000MA03
Appendix A - ABBREVIATIONS AND GLOSSARY OF TERMS A.1

A AAI ABI A/C ACC ACID ACK ACP ACT A/D ADA ADEP ADES ADEXP AFIL AFL AFTN A/G AIC AIDC AIP AIRMET AIS ALT AMC ANS APP APW ARR ASTERIX ATA ATC ATCAS ATCC ATD ATFM ATIS ATM FDD Message Queue Advanced Boundary Information Message Aircraft Area/Airspace Control Centre Aircraft Identification Acknowledge(ment) Accept message Activation Message Analog-To-Digital Programming language Aerodrome of Departure Aerodrome of Destination ATS Data Exchange Protocol Aircraft Filed Flight Plan Actual Flight Level Aeronautical Fixed Telecommunications Network Air/Ground, Air-To-Ground Aeronautical Information Circular Air Traffic Services Interfacility Data Communications Aeronautical Information Publication Airman Meteorological Information Aeronautical Information Service Altitude/Alternate Airspace Management Cell Air Navigation Services Approach Centre Area Proximity Warning Arrival Message All Purpose Structured Eurocontrol Radar Information Exchange Actual Time of Arrival Air Traffic Control Air Traffic Control Automation System Air Traffic Control Centre Actual Time of Departure Air Traffic Flow Management Airport Traffic Information System Air Traffic Management Use or Disclosure of this information is subject to the restrictions on the tile page of this document Page A-1
Abbreviations
Definition
Abbreviation
DOCUMENT N: 0029200000000MA03
Abbreviation
ATS AUP AUX B BYP C CA CAA CAD CB CBA CBT CCR CD CDR CFL CFMU CHG CIN CLAM CMD CNL CNS COP COTS CPL CSCI CSSR CTF CTOT CWP D DBM DCT DEP DEP DEST DL DLA DLS DRF Data Base Management Direct Route Qualifier Departure Message Departure Aerodrome Destination Aerodrome Data Link/Downlink Delay Data link Service Data Recording Facility Conflict Alert (see STCA) Civil Aviation Administration/Authority Computer-Aided Design Mouse Central Button Cross-Border Areas Computer-Based Training Communications Compressor Radar Compact Disk Conditional Routes Cleared Flight Level Central Flow Management Unit Change Message See NIC Cleared Level Adherence Monitoring Alert Control and Monitoring Display Cancellation Message Communications, Navigation and Surveillance Coordination Point Commercial Off-The-Shelf Current Flight Plan Computer Software Configuration Item SSR Code Common Timing Facility Calculated Take-off Time Control Working Position By-Pass Mode of Operation Air Traffic Services Airspace Usage Plan Auxiliary
Definition
Page A-2
DOCUMENT N: 0029200000000MA03
Abbreviation
E EET ENSI ENSO EOBD EOBT EST ETA ETD ETO F FANS FBS FCON FDA FDD FDP FDPS FIFO FIR FIX FL FMU FP FPL FUA G GAT GByte GHz GPS GRIB GUI H HCI HDLC HFS HMI HOLD HWCI Hz Human-Computer Interface High-Level Data Link Communication Horizontal Future Situation Human-Machine Interface Hold(Ing) Hardware Configuration Item Hertz General Air Traffic Gigabyte Gigahertz Global Positioning System Wind Meteorological Message Graphical User Interface Future Air Navigation Systems Fallback System Fixed Configuration Flight Data Assistant Flight Data Display Flight Data Processing Flight Data Processing System First In, First Out Flight Information Region Fix Point Flight Level Flow Management Unit Flight Plan Flight Plan Flexible Use of Airspace Estimated Elapsed Time Expected Sorted Number Input Expected Sorted Number Output Estimated Off-Block Date Estimated Off-Block Time Estimate Estimated Time of Arrival Estimated Time of Departure Estimated Time Over a Fix
Definition
Page A-3
DOCUMENT N: 0029200000000MA03
Abbreviation
I ICAO IEEE IFPS IFR ILS INB INF INT ISO K Kb Kbits Kbps KBps KCAS Kgls KHz KIAS Km KPS Kt KW L LAM LAN LAT LB LCD LMG LONG M M Mb Mbar MET METEO METAR MHz MM MON Match/Meter Millibars Milibar Meteorological Information Meteorological Meteorological Aviation Routine Weather Report Megahertz Millimetres Monoradar Mode of Operation Logical Acknowledgement Message Local Area Network Latitude Mouse Left Button Liquid Crystal Display Local Maps Generation Longitude Kilobytes Kilobits Kilobits per second Kilobytes per second Knots Calibrated Airspeed Kinematics GPS Landing System Kilohertz Knots Indicated Airspeed Kilometre KB per second Knots (NM/ hour) Kilowatts International Civil Aviation Organization Institute of Electrical and Electronics Engineers Integrated Initial Flight Plan Processing System Instrument Flight Rules Instrumental Landing System Inbound Information Message Integrated Mode of Operation International Standards Organization
Definition
Page A-4
DOCUMENT N: 0029200000000MA03
Abbreviation
ms MSAW MSB MSL MTCD N NAV NE NIC NM NOTAM O OAT OLDI ORCAM P PAC PCA PEL PLT POS PSR PSR T PTS Q Q QFE QNH R RAD RAM RAW RB RBL RCA RDCU RDP RDPS RETD RFL RIE Radar Route Adherence Monitoring Restricted Area Warning Mouse Right Button Range Bearing Line Reduced Coordination Airspace Radar Data Communication Processor Radar Data Processing Radar Data Processing System Revised Estimated Time of Departure Requested Flight Level Route Insertion Error FDD Messages Queue Pre-activation Message Prior Coordination Airspace Planned Entry Level Pilot Position Report Primary Surveillance Radar Primary Surveillance Radar Track Panoramic Tower Simulator Operational Air Traffic On-Line Data Interchange Originating Region Code Assignment Method Navigation Navigation Equipment Navigation Integrity Control Nautical Miles Notice To Airmen millisecond Minimum Safe Altitude Warning Most Significant Bit Minimum Sea Level Medium-Term Conflict Detection
Definition
Atmospheric pressure at aerodrome elevation or at runway threshold Altimeter sub-scale sitting to obtain elevation when on the ground
Page A-5
DOCUMENT N: 0029200000000MA03
Abbreviation
RISC RMCDE ROC ROD RPL RVSM RWY S SAM SAR SBY SDD SDP SFPL SID SIGMET SIM SMC SPECI SPI SQ SQL SSR SSS STAR STCA ST-RAW T TACT TAF TAIS TAS TCP TCP/IP TMA TFL TL TOC TOD TRA TSA Tactical System Terminal Area Forecast (ICAO) Total Aircraft Information System True Airspeed Transmission Control Protocol TCP/Internet Protocol Terminal Maneuvering Area Transfer Fly Level Transition Level Top of Climb Top of Descent Temporary Reserved Area Temporary Segregated Area Slot Allocation Message (CFMU Message) Search and Rescue Standby Situation Data Display Surveillance Data Processing System Flight Plan Standard Instrument Departure Significant Meteorological Information Simulator System System Monitoring Computer Special Forecast Special Position Identification Sequence Number Structured Query Language Secondary Surveillance Radar Software System Specification Standard Instrument Arrival Route Short-Term Conflict Alert Short-Term Restricted Area Warning Reduced Instruction Set
Definition
Radar Message Conversion and Distribution Equipment Rate of Climb Rate of Decent Repetitive Flight Plan Reduced Vertical Separation Minimum Runway
Page A-6
DOCUMENT N: 0029200000000MA03
Abbreviation
TSP TWR U UAC UTC UUP V VFS VFR VSP W WAN Wi-Fi WWW X X.25 Standard Protocol In Telecommunications Wide Area Network Wireless Fidelity World Wide Web Vertical Future Situation Visual Flight Rules Variable System Parameter Upper Airspace Control Centre Universal Time Coordinated Updated Airspace Usage Plan Technical Supervisor Tower or Tower Control
Definition
A.2
Glossary of Terms
Actual Time of Departure (ATD) An aircraft, which is just taking off, has performed a tacking manoeuvre (some seconds after the wheels lose contact with the runway) at the time. Actual Time of Arrival (ATA) An aircraft, which is landing, reduces speed to TAXI phase speed at the time. Adaptation Set of system-specific data adapted by and used by a system. Adaptation Data Values entered into the System to control processes such as definition of Flight Plan insertion into a List, activation/inhibition of certain alerts, etc. Adjust Correction Correction (azimuth and range) applied to all plots received from the radar when the System detects an adjustment error. The adjustment error is calculated by subtracting the range and azimuth of the fixed transponder (received from the radar) from the nominal values, which are within the adaptation data for the fixed transponder. Aerodrome Defined area (including any buildings, installations, and equipment) intended to be used either wholly or in part for arrival, departure and surface movement of aircraft and operational vehicles. Aircraft A either craft flies in the air fixed or rotary wing.
Page A-7
DOCUMENT N: 0029200000000MA03
Airway It is a corridor for air traffic that is equipped with radio navigational aids, which is used by the aircraft to maintain its position within the corridor. An airway is defined by a series of fixpoints. Aircraft Identification (ACID or Callsign) A group of alphanumeric characters used to identify an aircraft in air-to-ground communications. Airspace It is a volume, above the earth surface, to a specified altitude. It can be designated to be under the control of an air traffic controller. Altitude Vertical distance of a level, a point, or an object considered as a point, measured from mean sea level. Altitude Filter Operational display filter that suppresses the display of tracks whose corresponding altitude is not within the filter limits. Tracks assumed by the display are not subject to filtering. Bypass Mode SDD mode of operation indicating that the radar data processing feeding the display of the SDD is mono-radar tracking running in SDD processor. The information coming from SDP central server (if it is running) is not taken into account by the SDD. Collimation Error It is composed of a range error and an azimuth error. The collimation error is calculated when the primary plot reinforces a secondary plot by calculating the primary plot differences in range and azimuth from the secondary plot. Conflict Predicted converging of aircraft in space and time, which constitutes a violation of a given set of minimum separations. Conflict Alert Predictive function, which involves the monitoring of all aircraft-pairs, equipped with Mode C transponders. Conflict Alert warns the controller of potential collisions due to airspace violations. Controlled Airspace Airspace of defined dimensions, which supplies air traffic control service for flights controlled by a controller. Controller Person authorized to provide air traffic control service. Coordination Process Procedure to reach an agreement on clearances, control transference, advice or information to be communicated to aircraft by means of information interchange between air traffic services dependencies or between controller working positions within those dependencies. Correlation Assignment process (manually or automatically) of radar track and a flight plan based on predefined criteria.
Situation Data Display User Manual Use or Disclosure of this information is subject to the restrictions on the tile page of this document Page A-8
DOCUMENT N: 0029200000000MA03
Cruising Level A level maintained during a significant portion of a flight. CTOT Departure estimated time of a FP controlled by CFMU. Current Flight Plan (CPL) Flight plan, including changes, if any, brought about by subsequent clearances. Fixpoint Reference point specified either by geographic coordinates (latitude, longitude), a name, or as a distance and bearing from a navigational aid. Flight Data Data related to real or foreseen movements of an aircraft, usually displayed in abbreviated or in code form. Flight Information A service provided for giving advice and information useful for the safe and efficient conduct of flights. Flight Level A surface of constant atmospheric pressure that is related to a specific pressure datum, 1013.2 hectopascals (hPa), and is separated from other such surfaces by specific pressure intervals. Flight Plan Defined information that, with respect to a projected flight or part of an aircraft flight is subjected to the ATC facilities. Flight Plan Route Planned or actual specified path of an aircraft using some or all of the following items: departure aerodrome, SID, Fixes, Airways, Holding Pattern, STAR, and/or destination aerodrome. FP Strip It is a device including information on a flight progress and status. These are displayed on the specific working positions to communicate the flight information to the controller in charge. FUA With the FUA (Flexible Use of Airspace Concept) application, the airspace is not divided into civil and military but it is considered as a unique continuous and assigned airspace taking into account the user requirements. The FUA Concept allows the maximum-shared use of the airspace by improving the civil/military coordination. The FUA Concept application guarantees that any airspace segregation is temporal and based on a real use during a specific period. Hand-Over Procedure Process to transfer flights between controllers. Heading Direction to which the aircraft longitudinal axis is pointed, usually expressed in degrees from North (true, magnetic, compass or grid). The grid north is an imaginary direction parallel to the Greenwich meridian measured in the true North sense.
DOCUMENT N: 0029200000000MA03
Height Vertical distance of a level, a point or an object considered as a point, measured from a sp ecified datum (ground). Leader Line It joins the data label to its corresponding track. Level A generic term relating to the vertical position of an aircraft in flight, which indistinctly means, height, altitude, or flight level. Lost FP A track (aircraft) is lost when a radar return has not been received for a particular target. When this happens, the target tracker projects a target position based on the targets previous positions and generates a new track position update for the display. A lost track is dropped from both the display and the target trackers database if its lost time exceeds a Variable System Parameter limit. Medium Term Conflict Detection (MTCD) Predictive function, which involves the monitoring of the trajectory of all the System flight plans under control of the ATC centre. The MTCD function alerts the controller on the potential violation of separation criteria (longitudinal, lateral and vertical). Minimum Safe Altitude Warning (MSAW) It is a predictive function, which involves the monitoring of all aircrafts reporting valid altitude data messages. MSAW warns the controller of potential collisions with ground-based objects. Mode 3/A See SSR Code. Mode C Setting on the aircraft transponder equipment that sends pulses situating the aircraft pressure altitude. Mono-radar Track Information set, evolving in time, related to an aircraft, based upon radar information received from a unique radar site and used by the computer for tracking purposes. Multi-radar Track Information set, evolving in time, related to an aircraft and obtained from the synthesis of all monoradar tracks that represent the above referenced aircraft. Play Back (Reproduction) This process recovers and presents: Information previously recorded Data, which have been displayed to the Positions Controllers (SDD) Configuration, which have been displayed to Positions Controllers (SDD). Plot Set of information, with relation to an aircraft, received from the radar set.
Page A-10
DOCUMENT N: 0029200000000MA03
Pop-up Menu Menu displayed upon clicking once on a selectable option, usually a track field. The menus position on the display depends on the location of the selectable option. Menu display is kept after button release and selection is performed pointing and clicking (usually LB). Primary Surveillance Radar (PSR) Radar sensor used to determine the position of an aircraft. Process Program segment that is usually dedicated to a functionally cohesive activity, recognized and scheduled for execution. Pull-down Menu Menu displayed upon clicking once on an icon. The menus position is fixed. Menu display is kept after button release and selection is performed pointing and clicking (usually LB). Quick-look Function to display manually a track label for information purposes. Radar A device which, by measuring the time interval between transmission and reception of radio pulses and correlating the angular orientation of the radiated antenna beam or beams in azimuth and/or elevation, provides information on range, azimuth, and/or elevation of objects in the path of the transmitted pulses. Recording System common information and local information (each SDD) methodically gathered in a specific period. Reduced Vertical Separation Minimum (RVSM) Within the airspace it represents a change of significant meaning to the operational environment of involved sectors and centres. STCA RVSM and MTCA RVSM are STCA and MTCA with calculus taking into account the RVSM in sectors where RVSM applies. Restricted Area Defined airspace volume, where the flights are restricted under certain conditions, or where, dangerous activities for flights are performed. Runway A defined rectangular area on a land aerodrome prepared for the aircraft landing and take-off. Secondary Surveillance Radar (SSR) Radar sensor used to interrogate aircraft transponder equipment to receive SSR Codes, barometric pressure information, and/or the SPI. The Mode 3/A SSR Codes are used to identify individual flights in ATS. When the SSR detects a flight, its SSR Code is used to correlate the flight with the corresponding Flight Plan. SSR Codes assignment and management is a fundamental part of the civil ATS systems. As SSR Codes are based on 4 octal-digits, there are only 4096 available codes to use around the world.
Page A-11
DOCUMENT N: 0029200000000MA03
Sector Designated control area subdivision, which belongs to a controller or to a small group of controllers. The entire sector must belong to one controller jurisdiction at a time. In addition, sectors composing a controller jurisdiction must be adjacent. Sectorization It is an action to alter the current existing configuration when changing the allocation of some or all sectors with respect to the working positions. Short Term Conflict Alert (STCA) It is a predictive function, which involves the monitoring of all aircraft pairs, which are equipped with Mode C transponders. Conflict Alert warns the controller of potential collisions due to airspace violations. Situation Data Display (SDD) The computer display where Air Traffic Controllers view targets (aircraft) and radar returns. Special Position Identification (SPI) Feature of aircraft transponder equipment that, when it is enabled, causes the aircrafts corresponding Present Position Symbol (PPS) to change to the Special Purpose Indicator on the SDD. This PPS is used to differentiate the aircrafts PPS from others that may be in the same immediate area. SSR Code Four-octal digit code sent from aircraft transponder to identify uniquely the aircraft. Standard Instrument Departure (SID) It is a special route overflown by an aircraft during its take-off (using the <Take Off> command). A SID connects an airway to an airport and it is defined by a series of fixpoints/level pairs that begin at or near the departure runway and end at or near the airway. Synthetic Track Type of track generated by the System upon controllers request. A special track symbol distinguishes these tracks from the real ones. Terminal It is the computer and application software. Terminals are grouped together in various combinations to form a working position. Test Plot It is radar information that responds to a fixed transponder. Track It is the projection on the earth surface of the aircraft route. The route direction at any point is expressed in degrees (magnetic North). Track Label Collection of tabular data displayed on one to four lines. The data label is linked to its corresponding track by a leader line. Track Symbol It is a visual representation of a type of track.
DOCUMENT N: 0029200000000MA03
Traffic Flow Set of reports, which are provided by the System under operators request. These reports support the user for decision-making on air traffic flow smoothing within either a determined airspace, or flight plan route or departure/origin aerodrome, in order to make the best use of the airspace. Transit Flights passing through the working area (FIR). Transition Level Altitude at which, or below, the vertical position of an aircraft is controlled by altitudes reference. Transponder L-band radar receiver/transmitter carried aboard certain aircraft. It transmits a beacon code and Mode C altitude (if so equipped), in response to an interrogation from Secondary Surveillance Radar. The data provided by a transponder can be in any of the following forms: Mode 3/A, Mode 2, or Mode C. Variable System Parameter (VSP) It is a system parameter, which can be modified on line. Working Position Terminals group specially built which are included in a single cabinet structure. Workstation It is the computer and application software. Workstations are grouped together in various combinations to form a working position.
Page A-13
DOCUMENT N: 0029200000000MA03
Page A-14
DOCUMENT N: 0029200000000MA03
Appendix B - System Messages List B.1 Messages sent from SDP to SDD
IMPOSSIBLE CREATE APL Fictitious (INCOMPLETE) Error when trying to create a fictitious FP without fulfilling all fields of the fictitious window IMPOSSIBLE CREATE APL Fictitious (ALREADY EXISTS) Error when trying to create an already existing fictitious FP in the System Callsign UNABLE TO CREATE HACT > LAST ETO Error when trying to create manually or automatically a synthetic track starting from a Flight Plan whose route has been already overflown. Callsign UNABLE TO CREATE HACT < FIRST ETO Error when trying to create manually or automatically a synthetic track starting from a Flight Plan whose route has not started yet to be overflown yet. Callsign UNABLE TO CREATE INCOMPLETE ROUTE Error when trying to create a synthetic track starting from a Flight Plan without route.
B.2
Messages sent from FDP to SDD
"MODIFY ROUTE (CALLSIGN-ADEP-EOBD-EOBT-ADES) xxxx" xxxx -> "Fp Already Exists" "Fp doesn't exist" "Exceeded File" "Fp not Accessible" "Erroneous Ident" "Ssr Code in Use" "Reference Point out of Route" "Inaccessible Element" "Too Many Points" "Route Out of FIR"
Situation Data Display User Manual Use or Disclosure of this information is subject to the restrictions on the tile page of this document Page B-1
DOCUMENT N: 0029200000000MA03
"Too Many Sectors" "Incoherence FP Date" "Not Connection with ADES" "UNKNOWN ERROR" It is an error in a graphical route modification, indicating where the error is situated
"CFL INPUT (CALLSIGN-ADEP-EOBD-EOBT-ADES) xxxxx xxxx -> "FP already exists" "FP does not exist" "Full FP file" "Inaccessible FP" "No trans received msg" "Offline Line " "Success" "Queueing not allowed" "Full queue" "Notam already exist" "Notam not exist" "Unknown message type" "Confirm message sending" "Illegal shape" "Print error" "No data available" "Exceeded capacity" "Not valid for coord evolution" "Not valid for fp conditions" "Coord not accessible" "Impossible Chg Action" "Keywords Field not Matching" "UNKNOWN ERROR" It is an error when entering a CFL (it is NOT an error in a particular field). It indicates the aircraft and type of error
Page B-2
DOCUMENT N: 0029200000000MA03
"XFL INPUT (CALLSIGN-ADEP-EOBD-EOBT-ADES) xxxxx xxxx -> "FP already exists" "FP does not exist" "Full FP file" "Inaccessible FP" "No trans received msg" "Offline Line " "Success" "Queueing not allowed" "Full queue" "Notam already exist" "Notam not exist" "Unknown message type" "Confirm message sending" "Illegal shape" "Print error" "No data available" "Exceeded capacity" "Not valid for coord evolution" "Not valid for fp conditions" "Coord not accessible" "Impossible Chg Action" "Keywords Field not Matching" "UNKNOWN ERROR" It is an error when entering a XFL (it is NOT an error in a particular field). It indicates the aircraft and type of error "CFL INPUT (CALLSIGN-ADEP-EOBD-EOBT-ADES) xxxxx yyyyy xxxxx -> "CALLSIGN: " "ADEP: " "EOBD: " "EOBT: "
DOCUMENT N: 0029200000000MA03
"ADES: " "FLIGHT RULES: " "SSR EQUIPMENT: " "NUM AIRCRAFT: " "AIRCRAFT TYPE: " "RFL: " "SPEED: " "ROUTE: " "ETA: " "FREE TEXT: " "WAKE TURBULENCE: " "SSR CODE: " "SID: " "STAR: " "ENTRY POINT: " "ENTRY POINT ETO: " "CFL: " "FLIGHT TYPE: " "ALTERNATES: " "NCA EQUIPMENT: " "RVSM EQUIPMENT: " "AIRCRAFT REGISTRATION: " "REPORTED SPEED: " "NEXT REPORTING POINT: " "NEXT REPORTING TIME: " "AIRCRAFT ADDRESS: " yyyy -> "Compulsory" "Syntactic" "New CALLSIGN in use" "Range Error" "Unknown element" "Field Error" "Inaccessible Element"
DOCUMENT N: 0029200000000MA03
"Incoherence" "Discontinuity" "FIR Time not Computable" "External Point does not exist" "Validate External Point" "Too Segments" "Too Points" "Extraction Error" "Too Sectors" "Message not allowed" "Ssr Code not assignable" "Impossible to reach" "Ssr Code already in use" "Area not found" "Area already existing" "FP Keyword not matching" "UNKNOWN ERROR" It is an error in a FP field when entering a CFL. It indicates the aircraft, field and type of error. "XFL INPUT (CALLSIGN-ADEP-EOBD-EOBT-ADES) xxxxx yyyyy xxxxx -> "CALLSIGN: " "ADEP: " "EOBD: " "EOBT: " "ADES: " "FLIGHT RULES: " "SSR EQUIPMENT: " "NUM AIRCRAFT: " "AIRCRAFT TYPE: " "RFL: " "SPEED: " "ROUTE: " "ETA: " "FREE TEXT: "
DOCUMENT N: 0029200000000MA03
"WAKE TURBULENCE: " "SSR CODE: " "SID: " "STAR: " "ENTRY POINT: " "ENTRY POINT ETO: " "CFL: " "FLIGHT TYPE: " "ALTERNATES: " "NCA EQUIPMENT: " "RVSM EQUIPMENT: " "AIRCRAFT REGISTRATION: " "REPORTED SPEED: " "NEXT REPORTING POINT: " "NEXT REPORTING TIME: " "AIRCRAFT ADDRESS: " yyyy -> "Compulsory" "Syntactic" "New CALLSIGN in use" "Range Error" "Unknown element" "Field Error" "Inaccessible Element" "Incoherence" "Discontinuity" "FIR Time not Computable" "External Point does not exist" "Validate External Point" "Too Segments" "Too Points" "Extraction Error" "Too Sectors" "Message not allowed"
DOCUMENT N: 0029200000000MA03
"Ssr Code not assignable" "Impossible to reach" "Ssr Code already in use" "Area not found" "Area already existing" "FP Keyword not matching" "UNKNOWN ERROR" It is an error in a FP field when entering an XFL. It indicates the aircraft, field and the type of error. "STRIP FP (#) OF (#) NOT PRINTED" It is an error when printing a strip because there is no printer or it is off. It is an error when printing a strip in the alternative printer instead of the primary one. This message comes out in the position to which the strip belongs, indicating the position where it has been printed. "STRIP FP (#) ALTERNATE PRINTING FOR POSITION #" It is an error when printing a strip in the alternative printer instead of the primary one. This message comes out in the secondary position, indicating to which position the strip belongs.
Page B-7
DOCUMENT N: 0029200000000MA03
Page B-8
DOCUMENT N: 0029200000000MA03
Appendix C - Local Error Messages List

DE-CANTERING LIMIT REACHED MINIMUM RANGE "value" NM MAXIMUM RANGE "value" NM Errors when de-cantering and enlarging or reducing the working area with maximum and minimum values defined in the SDD CONFLICTS REQUESTED FOR "Flight Plan" MTCD DATA BASE LIMIT EXCEEDED!! Report when requesting a Flight Plan conflict from the track Conflicts maximum number has been exceeded (medium time conflict detect) REQUEST ERROR FOR "Flight Plan" Error within the request of a conflict for a Flight Plan, which does not exist LMG OPERATION NOT ALLOWED Invalid operation when creating or modifying a local map NUMBER MAXIMUM AREAS EXCEEDED Exceeded the maximum number to create defined areas RBL ALARM FUNCTION DISABLED Inhibited the RBLs alarm function RESTRICTED ACTION, GRAPHIC ROUTE MODIFICATION ACTIVATED Invalid action when modifying a route graphically RADAR INACTIVE It is displayed when inhibiting the radar from the Supervision Position "PRINTING ERROR: TABULAR FILES NOT CREATED" "PRINT ERROR: NO PRINTER AVAILABLE" General printing errors CURSOR ACTIVATION NOT POSSIBLE Invalid action in the auxiliary window request
Page C-1
DOCUMENT N: 0029200000000MA03
INTERCONSOLE MARKER ACTIVATION NOT POSSIBLE Request of interconsole marker activation within an invalid context (for example, on an invalid sector) QNH/TL CHANGED It is displayed on reception of a QNH modification message RDP DOWN RDP subsystem fall-down has been detected FDP UP FDP subsystem recovery has been detected GAMET INFO CHANGED Gamet message reception AIRMET INFO CHANGED aerop Airmet parameters modification reception METAR INFO CHANGED aerop Metar parameters modification reception SIGMET INFO CHANGED aerop Sigmet parameters modification reception SPECI INFO CHANGED aerop Speci parameters modification reception TAF INFO CHANGED aerop Taf parameters modification reception AREA REST CANCEL area Restricted area deletion message reception AREA REST ACTIVATED area Restricted area creation message reception
Situation Data Display User Manual Use or Disclosure of this information is subject to the restrictions on the tile page of this document Page C-2
DOCUMENT N: 0029200000000MA03
Appendix D - FP Route D.1 Definitions
An Original Route is defined as the characters string that takes up the E/R field in a specific moment. The FP Route Automatic Calculation Algorithm analyzes that field when FP is analyzed. As output to that analysis, following three types of Routes are obtained: Purged Route It is obtained from the Original Route by eliminating from this one the Route elements with no Interest for the System, such as external points and aerodromes, situated at the characters string limits. Calculated Route It is the Route obtained once the route automatic calculation has been performed. It consists of a points sequence belonging to the System controlled airspace. Within these points the flight plan rules for the FP are IFR. Standard Route Each route consists of a points sequence defining a way, interval to the System controlled airspace, between the FP aerodromes pair, which is extracted by the Route Automatic Calculation Algorithm. It is obtained from the information of the departure aerodrome, destination aerodrome, first point and last point of the analyzed Route. The Standard Routes set is not fixed. They are only displayed when errors are detected in the Original Route analysis. The number of Standard Routes is between 0 and 5; depending on if there are Standard Routes, which are valid for the FP being analyzed, in the Adaptation Data Base.
D.2
Presentation of Obtained Routes When FP Analyzing
The Routes List is displayed over the FP Operation Window. This consists of different characters strings, each one corresponding to an output route of the Route Automatic Calculation Algorithm. Alongside each one of the routes, a letter to identify the route is displayed on the left side: `O' => Purged Route. `C' => Calculated Route. `E' => Standard Route (it there are) The order within the Routes List goes as Purged Route, Calculated Route and Standard Route. The route filling the pre-format Route field, in a given moment, is displayed on the Display Area of the Routes List with characters in reverse video mode whilst the remaining routes of that Routes List are displayed in normal video mode.
Page D-1
DOCUMENT N: 0029200000000MA03
First time the Routes List is displayed, after the FP analysis process, the Purged Route is automatically selected. If an error was detected in that field analysis, all characters will be displayed in reverse video mode; if no error is detected, they will be displayed in normal video mode. The operator may modify the selected route in that moment or may select another one from the Routes List.
D.3
Route Field Analysis Route Morphology
It is a field composed of characters. Its number will be different according to the field source. The maximum number of characters for a message coming from the AFTN network will be 320 and the maximum number or characters in a screen format will be 156. The filed will consist of following characters: Alphabetical: Capital letters within the range A..Z Numerical: Digits within the range 0..9 Special: (,), *, y /. Blank character One or more blank characters will separate elements forming the field. Elements with more than 30 characters will not be allowed. If there is an element with more than 30, it will be divided into two or more elements, having the first element the first 20 characters and the second one the remaining ones, taking into account these elements as morphological error. Elements with characters different from the aforementioned ones will not be allowed. Elements with just one character will not be allowed. Elements exclusively including digits will not be allowed. Elements exclusively including alphabetical characters will have a length between 2 and 7 characters. Elements including alphanumerical characters, with or without special ones, will have a length between 2 and 29 characters. Elements including special characters will have to fulfil following conditions, too:
1. 2. 3.
Only two asterisks or none may be displayed within an element. Only one parenthesis may be displayed within an element and always the open parenthesis, (, has to be previous to the close one, ). Elements will have only one or two slashes /.
Route Semantic
Characters are grouped resulting in meaningful elements. It is attempted to acknowledge the separated elements within the Route morphological analysis being not erroneous elements. It is convenient to define certain sub-elements to be used later on within the Route elements composition before it is displayed.
Page D-2
DOCUMENT N: 0029200000000MA03
TIME expresses the estimated time of point crossing level. It is a string of five characters in the form: T c1 c2 c3 c4 where c1 is a digit. The two first digits, c1 c2, express the day absolute time, forming a number between 00 and 23, both inclusively. The two remaining digits, c3 c4, express the hour minutes, forming a number between 00 and 59, both inclusively. LEVEL expresses the included level or the one is desired to reach when crossing a point. It is a string of four or five characters, depending on the units it is expressed. The first character will be a letter indicating the measurement unit it is being used. a) Altitude in hundredths of feet: A c1 c2 c3. Where ci is a digit. b) Flight Level: F c1 c2 c3. Where ci is a digit. c) Altitude in tenths of meters: M c1 c2 c3 c4. Where ci is a digit. d) Standard metrical level in tenths of meters: S c1 c2 c3 c4. Where ci is a digit. If the values exceed the limits allowed by the System and given by Adaptation, the element will be considered as SEMANTIC_ERROR. SPEED expresses the velocity to be reached when crossing a point. It is a string of four or five characters, depending on the units it is expressed. The first character will be a letter indicating the measurement unit it is being used. a) Speed in kilometres/hour. K c1 c2 c3 c4. Where ci is a digit. b) Speed in knots. N c1 c2 c3 c4. Where ci is a digit. c) Mach number rounded to the hundredths closest to the Mach unit.
Situation Data Display User Manual Use or Disclosure of this information is subject to the restrictions on the tile page of this document Page D-3
DOCUMENT N: 0029200000000MA03
M c1 c2 c3. Where ci is a digit. If the values exceed the limits allowed by the System and given by Adaptation, the element will be considered as SEMANTIC_ERROR. Elements must be isolated and acknowledged. Different types of elements will be considered: Known elements: Keywords. Elements that for being acknowledged need to be queried in the System Adaptation Tables: SRXXX Keywords, Points, Airways, and Procedures Elements with associated Information. Once the points are acknowledged, these may have associated Information about the estimated time of crossing, required level Following are described the different elements that may form the Route field. POINT Point encoded designator. (FIX POINT) String of 2 to 6 characters. The string has to be acknowledged as a point designator by the System, given by Adaptation. If it is not so, the string will be considered as meaningless. Expression of a point in geodesic coordinates Only degrees String of 7 characters as: c1 c2 L1 c2 c4 c5 L2. where ci is a digit and Li is a letter. The two first digits show the Latitude in degrees, expressing a number between 0 and 89, both inclusively. Letter L1 may take the values N for North or S for South. Following are three digits showing the Longitude in degrees, expressing a number between 0 and 179, both inclusively. Letter L2 may take the values E for East or W for West. The correct number of digits is completed, when it is necessary, by inserting zeros. Degrees and minutes String of 11 characters as follows: c1 c2 c3 c4 L1 c5 c6 c7 c8 c9 L2. Being ci a digit and Li a letter. The four first digits express the Latitude in degrees and tenths and units of minutes; the first ones express a number between 0 and 89, both inclusively, and the two remaining ones express a number between 0 and 59, both inclusively. Letter L1 may take the values N for North or S for South.
Page D-4
DOCUMENT N: 0029200000000MA03
Following are five digits expressing the Longitude in degrees and tenths and units of minutes, the three first ones express a number between 0 and 179, both inclusively, and the remaining ones express a number between 0 and 59, both inclusively. Letter L2 may take the values E for East or W for West. The correct number of digits is completed, when it is necessary, by inserting zeros. Expression of a point in Bearing and Range with respect to a navigational aid String of 8 to 11 characters as follows: a1 a2 c1 c2 c3 c4 c5 c6 a1 a2 a3 c1 c2 c3 c4 c5 c6 a1 a2 a3 a4 c1 c2 c3 c4 c5 c6 a1 a2 a3 a4 a5 c1 c2 c3 c4 c5 c6 Being ci a digit and ai a letter. The characters set (ai) identify a POINT. The three first characters show the bearing from the navaid, giving the magnetic degrees. They will consist of a number between 0 and 359, both inclusively. The three last digits show the range from the navaid, giving the nautical miles. They will consist of a number between 0 and 999, both inclusively. The correct number of digits is completed, when it is necessary, by inserting zeros. FICTITIOUS POINT It expresses a point over the line joining other two Route points. String of 5 to 16 characters as follows: DISTANCE (POINT) Being DISTANCE a string of 1 to 3 digits expressing a distance in nautical miles between the current point and the previous one within the route. They will form a number between 0 and 999, both inclusively. AIRWAY The ATS route encoded designator is a string of 2 to 6 characters. The string has to be acknowledged as an airway designator by the System and given by Adaptation. If it is not so, the string will be considered as meaningless. KEYWORD The encoded keyword designator is a string of 2 to 10 characters depending on the keyword, being either Fix Point Designator Keywords or Non-Fix Point Designator Keywords. FIX POINT DESIGNATOR KEYWORDS GA/OMA (OAT/GAT) Strings of 4 characters. They represent a sign indicating that within the Route elements that follow, it is taken into account that the type of flight has changed. DCT String of 3 characters. It indicates that the way between two points is the line that joints them.
Page D-5
DOCUMENT N: 0029200000000MA03
If it is displayed as first Route element, the direct way starts in the departure aerodrome. If it is displayed as last Route element, the direct way ends in the destination aerodrome. DR String of 2 characters. It defines route sections predefined in the Adaptation Data Tables, consisting of a series of fictitious points that link two points of the Route. Those points are the one identifying the section in the Adaptation Data Tables. IFR/VFR Strings of 3 characters. They define a change in the flight rules for a section from a point. If the IFR keyword is displayed, the FP changes into instrumental rules, the FP will continue with those rules until the VFR keywords are displayed, the current section finishes, or until the Route end. If the VFR is displayed, the FP changes into visual rules, the FP will continue with those rules until the IFR keyword is displayed, the current section finishes, or until the Route end. SID/STAR Strings of 3 or 4 characters. They define departure or arrival standard procedures. The System does not consider them. SR String of 2 characters. It defines route sections predefined in the Adaptation Data Tables, formed by a series of points, pertaining to airways, linking two route points. For that pair of Route points, it will be searched within the Adaptation Data Tables, if a section that linked them has been defined. SECTIONS SEPARATOR String of 2 characters: *. It defines the sections separation where the FP crosses the System controlled airspace and the FP rules are instrumental. NON-FIX POINT DESIGNATOR KEYWORDS SRXXX String of 5 characters. The two first are the letters S and R. The remaining ones are digits identifying each keyword. It defines route sections predefined in the Adaptation Data Table, consisting of a series of points, pertaining to airways. If the keyword is known as predefined in the Adaptation Data Tables, the points set defining the section will substitute the keyword. PROCEDURE The encoded designator of departure or arrival standard way to an aerodrome will consist of a string of 2 to 7 characters. The string has to be acknowledged as a System procedure designator, given by adaptation. POINTS WITH INFORMATION In this case different types will be distinguished: POINT WITH HOUR String of 8 to 17 characters as follows: POINT/HOUR POINT WITH SPEED AND LEVEL CHANGE String of 11 to 22 characters as follows:
DOCUMENT N: 0029200000000MA03
POINT/SPEED LEVEL POINT WITH CRUISE CLIMB String of 17 to 29 characters as follows: C / POINT / SPEED INITIAL LEVEL FINAL LEVEL C / POINT / SPEED INITIAL LEVEL PLUS Where PLUS is the word Plus. All these cases may be considered once acknowledged, as POINTS. SPEED AND LEVEL ELEMENT Speed and Level Element associated with a point with hour. String of 8 to 10 characters as follows: SPEED LEVEL. This element will be always related to a previous point that is a point with associated hour.
Route Syntax
This subchapter will try to identify the elements relations with their neighbours: Syntactic sequence is defined as the elements set related with each other by syntactic rules. Following sequence are acknowledged: POINT WITH KEYWORDS Form sequence: POINT (keyword1) (keyword2) Where POINT is any expression of geographic point as previously defined. Where (keyword1) is one of the following keywords: GA (OAT), OMA (GAT), IFR and VFR. It is an optional element. Neither two keywords of GA/OMA (OAT/GAT) nor two IFR/VFR keywords can be given together. If the IFR keyword is displayed, the point will have associated hour; otherwise, the point and the syntax error keyword in the Route would be indicated. A keyword GA (OAT), OMA (GAT), IFR or VFR can be only displayed in a sequence of this type. The generic name will be used: POINT_KEYWORDS The name FIXPOINT_KEYWORDS will be used, if the point is expressed in encoded designator. The name COORD_KEYWORDS will be used, if the point is expressed in geodesic coordinates or in bearing and range to a navaid. COORDINATES SEQUENCE Sequence as follows: nothing nothing FICTITIOUS.POINT DCT COORD_KEYWORDS (/COORD_KEYWORDS) DCT SECTIONS.SEQUENCE SECTIONS.SEQUENCE Where FICTITIOUS.POINT is the expression of a fictitious point. Where SECTIONS.SEQUENCE is the sections separator keyword.
Page D-7
DOCUMENT N: 0029200000000MA03
The notation (/COORD_KEYWORDS) COORD_KEYWORDS followed as desired. FICTITIOUS POINTS SEQUENCE
means
that
they
are
as
much
elements
Sequence as follows: POINTFICTITIOUS.POINT (/FICTITIOUS.POINT)POINT_KEYWORDS Where FICTITIOUS POINT is a fictitious point. It will be checked that both POINT and POINT_KEYWORDS are not within the external airspace to the one controlled by the System. It will be checked that all fictitious points are internal to the airspace controlled by the System. The sum of all distances between each fictitious point and the previous one has to be lower than the distance between POINT and POINT_KEYWORDS. The number of fictitious points followed by a sequence is optional. If within any of the checks last condition is not fulfilled, all the sequence fictitious points will be marked with SYNTAX_ERROR. DR SEQUENCE Sequence as follows: POINTDRPOINT_KEYWORDS It defines a fictitious points section between POINT and POINT_KEYWORDS. That section will be searched within the Adaptation Data Tables from the designators of previous and subsequent point to keyword. The proposed route section must exist within the System. If it is not exist, the keyword will be marked with SYNTAX_ERROR. SR SEQUENCE Sequence as follows: FIXPOINT_KEYWORDSSRFIXPOINTS_KEYWORDS It defines a points section between FIXPOINT_KEYWORDS and FIXPOINT_KEYWORDS. That section will be searched within the Adaptation Data Tables from the designators of previous and subsequent point to keyword. The proposed section must exist within the System. If it is not exist, the keyword will be marked with SYNTAX_ERROR. POINT WITH SPEED LEVEL AND HOUR SEQUENCE Sequence as follows: POINT/HOURSPEEDLEVEL Where POINT/HOUR is the expression of a point with associated hour. Where SPEEDLEVEL is an element consisting of the expression of associated speed followed by associated level. If the point has no associated hour or the first element does not exist, the second element will be marked with SYNTAX_ERROR. Apart from the elements syntax sequences within the Route elements syntax analysis, following rules have to be taken into account: DCT KEYWORD POSITION ANALYSIS Any DCT keyword displayed on the Route field has to be presented in environments of following type: Nothing nothing POINT_KEYWORDS DCT POINT_KEYWORDS If it is not the case, the keyword will be marked as SYNTAX_ERROR.
DOCUMENT N: 0029200000000MA03
Exceptions: If the first Route element is a DCT keyword, the departure aerodrome could not be AFIL (FP created in flight) If the DCT keyword is the last Route element, the aerodromes, both departure and destination, will belong to the System controlled airspace. SECTION SEPARATOR KEYWORD POSITION ANALYSIS A sections separator keyword will be considered as syntactically correct, if it is displayed on one of the following sequences: SECTION.SEQUENCEPOINTRemaining Route POINTS_KEYWORDS_ASSIGNATION.SECTIONPOINT_KEYWORDS_BRemaining RemainingPOINT_KEYWORDS_ASSIGNATION.SECTION Where SECTION.SEQUENCE is the sections separator keyword. SPEED AND LEVEL VALIDATION In an element with associated speed and level, it will be checked if the indicated values are compatible with the characteristics of the aircraft, which will perform the flight, and given by Adaptation. If values exceed the ones allowed to the aircraft, the element will be marked with SYNTAX_ERROR. AIRWAYS VALIDATION If an element is an airway, it will be analyzed, if it belongs to the upper or lower airspace. If the FP current level belongs to one of those airspaces and the airway to another one, the airway will be considered as SYNTAX_ERROR. GA/OMA (OAT/GAT) KEYWORDS VALIDATION A GA (OAT) keyword will be considered as erroneous, if when going through the elements before the Route, another GA (OAT) is found before an OMA (GAT) keyword or a sections separator keyword is located. An OMA (GAT) keyword will be considered as erroneous, if when going through the elements before the Route, another OMA (GAT) keyword is found before a GA (OAT) keyword or a sections separator keyword is located. A keyword considered as erroneous will be marked with SYNTAX_ERROR. A mixed military FP is that one including in its route any of the following keywords: GA (OAT), OMA (GAT). In this case, the Flight Type field must include the letter x, otherwise it will be marked with INCOHERENCE_BETWEEN_FIELDS. IFR/VFR KEYWORDS VALIDATION An IFR keyword is considered as erroneous, if when going through the elements before the Route, another IFR keyword is found before a VFR keyword or a sections separator keyword is located. A VFR keyword is considered as erroneous, if when going through the elements before the Route, another VFR keyword is found before an IFR keyword or a sections separator keyword is located. A keyword considered as erroneous will be marked with SYNTAX_ERROR. PROCEDURES VALIDATION If a procedure is the first Route element, it must be a departure procedure from departure aerodrome. Otherwise, it will be marked with SYNTAX_ERROR.
DOCUMENT N: 0029200000000MA03
If a procedure is the last Route elements, it must be an arrival procedure from the destination aerodrome. Otherwise, it will be marked with SYNTAX_ERROR. If the procedure is the only Route element or it is neither the first nor the last Route element, it will be considered as SYNTAX_ERROR. SID/STAR KEYWORDS VALIDATION If a SID keyword is the first Route element, it will be deleted. If it is not the first element, it will be marked with SYNTAX_ERROR. If a STAR keyword is the last Route element, it will be deleted. If it is not the last element, it will be marked with SYNTAX_ERROR. If there is only one Route element and it is a SID/STAR keyword, it will be marked with SYNTAX_ERROR.
Purged Route
The Purged Route is extracted from the Original Route once the morphological, semantic and syntactic analysis has been performed. If the departure aerodrome is correct and it is not an aerodrome internal to the System controlled airspace, this will try to find the first internal or boundary point when going through the Route from left to right. a) b) If it is a boundary point, the previous elements will be deleted. If it is an internal point and previous external point(s) has been detected, the previous elements to the last detected external point will be deleted.
If the destination aerodrome is correct and it is not an aerodrome internal to the System controlled airspace, this will try to find the first internal or boundary point when going through the Route form right to left. a) b) If it is a boundary point, the subsequent elements will be deleted. If it is an internal point and previous external point(s) has been detected, the subsequent elements to the last detected external point will be deleted.
The aim is to delete the external elements, known or unknown by the System, at the Route start and end when the FP starts or finishes within the external airspace. The Purged Route length, as Algorithm output, is fixed. If there are more than 156 characters in the Purged Route, only first 156 will be displayed. Only whole elements, none will be split; if when displaying 156 characters, the last element is split, it will be completely deleted and the characters will be fulfilled with blank characters.
Calculated Route
If the departure aerodrome belongs to the System controlled airspace and the first Route element is not a procedure designator, the System will try to recognize a departure procedure from the information included in the Route field. A departure procedure will consist of a points succession making up a departure runway from an aerodrome. It will allow linking the aerodrome, if it belongs to the System controlled airspace, with an airway. Through the last point of the departure procedure sequence, one airway, at least, will cross; that point will be defined as Transition Fix Point. The System will try to recognize a departure procedure from the Route field elements in following cases:
DOCUMENT N: 0029200000000MA03
a. First element is an airway: If that airway crosses a Transition Fix Point of that aerodrome, the point will be inserted and a procedure will be recognized. If the airway crosses more than one Transition Fix Point of that aerodrome, a fix point will be selected and a procedure will be recognized if: a.1 The element subsequent to the airway is a point belonging to the airway. a.2 The selected Fix Point, without being identical to the point subsequent to the airway, is the one with lower number of intermediate points in the airway to go to the subsequent point. b. First Route elements make up a points sequence not linked by DCT keywords: The system will select that departure procedure containing the sequence points and in the expressed order. If no procedure is found fulfilling the conditions, no procedure will be considered. If the destination aerodrome belongs to the System controlled airspace and the last Route element is not the procedure designator, the System will try to recognize an arrival procedure from the information included in the Route field. An arrival procedure will consist in a points succession making up an arrival runway to an aerodrome. It will allow linking the aerodrome, if it belongs to the System controlled airspace, with an airway. Through the first point of the arrival procedure sequence, one airway, at least, will cross; that point will be defined as Transition Fix Point. The System will try to recognize an arrival procedure from the Route Field elements in following cases: a. Last element is an airway: If that airway crosses a Transition Fix Point of that aerodrome, the point will be inserted and a procedure will be recognized. If the airway crosses more than one Transition Fix Point of that aerodrome, a Fix Point will be selected and a procedure will be recognized if: a.1 The element before the airway is a point belonging to the airway. a.2 The selected Fix Point, without being identical to the point before the airway, is the one with lower number of intermediate points in the airway to go to the previous point. b. Last Route elements make up a points sequence not linked by DCT keywords: The System will select that arrival procedure containing the sequence points and in the expressed order. If no procedure is found fulfilling the conditions, no procedure will be considered. CONTINUITY HYPOTHESIS Continuity in Route when there is only one element or a point with DCT keywords linked with the aerodromes. The cases: {Sacta Departure} {Sacta Departure} Destination} DCT DCT {Sacta Destination} BOUNDARY_point_BOUNDARY_coordinate {Non_SACTA {Sacta Departure} DCT POINT/COORDINATE DCT {Sacta Destination}
{Non_Sacta Departure} BOUNDARY_point/ BOUNDARY_coordinate DCT {Sacta Destination}

DOCUMENT N: 0029200000000MA03
Where BOUNDARY_point and BOUNDARY_coordinate refer to the expressions of boundary point of the System controlled airspace. They will result in continuous Routes. If the departure aerodrome is AFIL, only those cases where the first element is not a DCT keyword will be valid. Before proceeding with the Route elements continuity, it is necessary to make clear the airway concept fulfilling level and direction conditions and the airway selection rules between the set crossing two points. An airway crossing between two points fulfils direction and level conditions when: a. The FP level in the first considered point is lower than the maximum allowed to the airway and higher or equal to the minimum allowed to the airway. b. The Adaptation Data Table gives the airway direction when the message is received from the AFTN string. c. The airway direction within the remaining cases is considered as a return one. Airways selection rules crossing two given points will be the following ones: a. Those fulfilling level and direction conditions will be selected. b. If among the selected ones, it is the airway where the FP has reached to the first one of the points, this will be selected. c. Those airways with lower number of intermediate points between the given points will be selected. If there is more than one with no intermediate points, one is selected at random. d. If there is still more than one airway, if between the points there is the same number of intermediate points. None is selected and ambiguity is considered. General rules of continuity between Route elements: a. A points sequence of a same recognized procedure form a continuous route. b. A correct fictitious points sequence makes up a continuous route. c. Two contiguous points expressed as coordinates are continuous. They are supposed to be linked by a straight line, having an implicit DCT keyword. d. A point, recognized by the System, and a coordinate make up a continuous section, if first element has an associated DCT keyword. POINTDCTCOORDINATE COORDINATEDCTPOINT e. Two points recognized by the System make up a continuous section if: Being the sequence POINT_1 POINT_2. e.1 There is DCT keyword between them. e.2 If one airway, and only one, can be found crossing both points and fulfilling direction and levels conditions. The Route will be completed with the intermediate points to POINT_1 and POINT_2 belonging to the found airway. It will remain: Original sequence => route PTO_1 PTO_2 remaining_route Airway sequence => previous_point PTO_1 PTO_3 ... PTO_n PTO_2 remaining Final sequence =>
DOCUMENT N: 0029200000000MA03
route PTO_1 PTO_3 ... PTO_n PTO_2 remaining_route If more than one airway is found, the airways selection rules described in previous paragraph will be applied. e.3 They do not belong to the same airway, but POINT_1 is crossed by one airway, AWY_1, and POINT_2 is crossed by one airway AWY_2 too. Both of them will intersect in a unique point INTERSECTION_POINT. Thus, just one airway, and only one, AWY_1 is found crossing a POINT_1 and INTERSECTION_POINT and fulfilling direction and levels conditions, and just airway, and only one, AWY_2 is found crossing INTERSECTION_POINT and POINT_2 and fulfilling direction and level conditions. The Route will be completed, firstly by inserting INTERSECTION_POINT between POINT_1 and POINT_2, secondly with the AWY_1 points, which are intermediate to POINT_1 and INTERSECTION_POINT inserting them between those points, and finally, with the AWY_2 points which are intermediate to INTERSECTION_POINT and POINT_2 inserting them between those points. Remaining situations will mark the two points with DISCONTINUITY_ERROR. f. Two airways known by the System. Being the sequence: AWY_1 AWY_2 f.1 If they have just one intersection point between both of them, INTERSECTION_POINT, the original sequence will be replaced by the sequence: AWY_1POINT_INTERSECTIONAWY_2 Before proceeding to analyze the Route elements continuity. f.2 They have no single intersection point or they do not intersect each other. Both elements will be considered as DISCONTINUITY_ERROR.
g. Sequences with point and airway Being the sequences something_or_nothingAWY_1POINT POINT AWY_1something_or_nothing with something_or_nothing, the element different from point or lack of element is presented. Following cases may happen: g.1 When POINT belongs to AWY_1. The two sequences will be considered as discontinuous and POINT and AWY_1 will be marked with DISCONTINUITY_ERROR. g.2 When POINT does not belong to AWY_1. If one airway, and only one, AWY_2, crosses POINT intersecting AWY_1 in a unique intersection point, INTERSECTION_POINT and the sequences INTERSECTION_POINT POINT and POINT INTERSECTION_POINT behave as e.2 paragraph, following steps will be performed: g.2.1. INTERSECTION_POINT will be inserted between POINT and AWY_1. g.2.2. The Route will be completed with the airway intermediate points between POINT and INTERSECTION_POINT. g.2.3. INTERSECTION_POINT and DISCONTINUITY_ERROR.
AWY_1
will
be
marked
with
Page D-13
DOCUMENT N: 0029200000000MA03
Remaining situations will DISCONTINUITY_ERROR. Being the sequence: POINT_1AIRWAYPOINT_2 Following cases will be given:
cause POINT
and
AWY_1 to be marked
with
h. Sequences with two points and an airway in between.
h.1 Points belong to the airway. If airway fulfils direction and levels conditions, the intermediate AIRWAY points to POINT_1 and POINT_2 will replace this. If airway does not fulfil those conditions, the three elements will be marked with DISCONTINUITY_ERROR. h.2 One of the points does not belong to the airway. h.2.1. POINT_1 does not belong to the AIRWAY. If one airway, and only one, AWY_1, is found crossing POINT_1 and intersecting AIRWAY in just one point, INTERSECTION_POINT. If AWY_1 fulfils direction and level conditions between POINT_1 and INTERSECTION_POINT, and AIRWAY fulfils direction and level conditions between INTERSECTION_POINT and POINT_2, the original sequence is considered continuous and following process will be performed: a.) INTERSECTION_POINT will be inserted between POINT_1 and AIRWAY. b.) The Route will be completed between POINT_1 and INTERSECTION_POINT with the intermediate points belonging to AWY_1, between both points. c.) AIRWAY will be deleted. d.) The Route will be completed between INTERSECTION_POINT and POINT_2 with the intermediate points belonging to AIRWAY, between both points. If direction and level conditions are not fulfilled in any of the steps for some of the airways or there is ambiguity within the appropriate airway searching, the three elements will be marked with DISCONTINUITY_ERROR. h.2.2. POINT_2 does not belong to AIRWAY. If one airway, and only one, AWY_2 is found crossing POINT_2 and intersecting AIRWAY in just one point, INTERSECTION_POINT. If AWY_2 fulfils direction and level conditions between INTERSECTION_POINT and POINT_2, and AIRWAY fulfils direction and level conditions between POINT_1 and INTERSECTION_POINT, the original sequence is considered continuous and following process will be performed: a.) INTERSECTION_POINT will be inserted between AIRWAY and POINT_2. b.) The Route will be completed between INTERSECTION_POINT and POINT_2 with the points intermediate to AWY_2, between both points. c.) AIRWAY will be deleted.
Page D-14
DOCUMENT N: 0029200000000MA03
d.) The Route will be completed between POINT_1 and INTERSECTION_POINT with the intermediate points belonging to AIRWAY, between both points. If direction and level conditions are not fulfilled in any of the steps for some of the airways or there is ambiguity in the appropriate airway searching, the three elements will be marked with DISCONTINUITY_ERROR. h.3 Points do not belong to the airway. If following conditions are fulfilled: a.) If one airway, and only one, AWY_1, is found crossing POINT_1 and intersecting AIRWAY in just one point, POINT_C1, and fulfilling direction and level conditions between POINT_1 and POINT_C1. b.) If one airway, and only one, AWY_2, is found crossing POINT_2 and intersecting AIRWAY in just one point, POINT_C2, and fulfilling direction and level conditions between POINT_C2 and POINT_2. c.) If direction and level conditions are fulfilled in AIRWAY between POINT_C1 and POINT_C2. The original sequence is considered as continuous and following process is performed: a.) POINT_C1 will be inserted between POINT_1 and AIRWAY. b.) The Route will be completed between POINT_1 and POINT_C1 with the intermediate points belonging to AWY_1, between both points. c.) POINT_C2 will be inserted between AIRWAY and POINT_2. d.) The Route will be completed between POINT_C2 and POINT_2 with the intermediate points belonging to the AWY_2, between both points. e.) AIRWAY will be deleted. f.) The Route will be completed between POINT_C1 and POINT_C2 with the intermediate points belonging to AIRWAY, between both points.
If described conditions are not fulfilled, the three elements will be marked with DISCONTINUITY_ERROR. i. Continuity Departure Aerodrome and First Route Point. i.1 If the aerodrome belongs to the System internal controlled airspace. First element is continuous when there is no error and: a.) It is a sections separator keyword. b.) It is a DCT keyword. c.) It is a point of the departure procedure sequence. i.2 If the aerodrome does not belong to the System internal controlled airspace. First element is continuous when there is no error and: a.) It is a sections separator keyword. b.) It is a DCT keyword. c.) It is a Fix Point or Coordinate. j. Continuity Destination Aerodrome and Last Route Point.
Page D-15
DOCUMENT N: 0029200000000MA03
j.1
If the aerodrome belongs to the System internal controlled airspace. Last element is continuous when there is no error and: a.) It is a sections separator keyword. b.) It is a DCT keyword. c.) It is a point of the arrival procedure sequence.
j.2
If the aerodrome does not belong to the System internal controlled airspace. Last element is continuous when there is no error and: a.) It is a sections separator keyword. b.) It is a DCT keyword. c.) It is a FIX POINT or a COORDINATE.
ROUTE SEPARATION INTO SECTIONS A section will be defined as a points sequence defining a route controlled by the System. Those points have to belong to the System controlled airspace and the flight rules have to be IFR. It is necessary to distinguish within each section: a. Entry point. That one where the route starts. It can be a Departure Aerodrome (internal aerodrome and IFR flight rules), boundary point or internal point with flight rules change into IFR. Except for the first section, an entry point will have associated a crossing time. b. Exit point. That one where the route ends. It can be a Destination Aerodrome (internal aerodrome and IFR flight rules), boundary point or internal point with flight rules change into VFR. Points where a section starts and ends at the same time will not be allowed. If that case is given, that point will be marked with VALIDATE_BOUNDARY_POINT error. Following circumstances will cause a section change: a. Change from internal airspace, controlled by the System, to external airspace. The border is crossed to the exterior. b. Change from external airspace, non-controlled by the System, to internal airspace. The border is crossed to the interior. c. Internal points or boundary points where flight rules are fulfilled. c.1 Change from VFR rules to IFR rules. c.2 Change from IFR rules to VFR rules. In the Route Automatic Calculation Algorithm output, the FP sections are separated by means of the sections separation keyword. Thus, a section will be a Route elements sequence limited by the sections separation keyword. The only exception is presented when the section is limited in any of its extremes by a controlled airspace aerodrome; in this case, one of the extremes, or both of them, will have no section separator. The System will try to separate the Route into different sections. Firstly, it will try to separate them by means of geographical criteria. The geographical point, where the System will take contact with the FP and the geographical point where the contact will finish, will be searched. The section entry is defined with one of the following sequences:
Page D-16
DOCUMENT N: 0029200000000MA03
a. Departure aerodrome belonging to the System controlled airspace, providing that the first Route element is not a sections separator keyword. b. Boundary point to the System controlled airspace. c. Internal point to System controlled airspace. Whenever one of the following circumstances is given: c.1 It is the first Route element and the aerodrome does not belong to the System controlled airspace. c.2 It is the last known point before a sections separator keyword. d. External point to the System controlled airspace. Whenever it is the last external recognized point with associated time, speed and level before the first internal recognized point when searching a section entry. The two points define, each other, a boundary crossing. If the Route has already sections separators keywords, these ones will mark the searching of boundaries crossing. Between each two section separator keywords, the boundary crossings searching will be similar to the one performed to the completed Route without those keywords. The section exit is defined with one of the following sequences: a. Destination aerodrome belonging to the System controlled airspace, providing that the last Route element is not a sections separator keyword. b. Boundary point to the System controlled airspace, except when it is linked by a continuous route with the following element, which will be an internal or boundary point. c. Internal point to the System controlled airspace. Whenever one of the following circumstances is given: c.1 It is the last Route element and the destination aerodrome does not belong to the System controlled airspace. c.2 It is the last known point before a sections separator keyword. d. External point to the System controlled airspace. Whenever it is the first external recognized point with associated time, speed and level subsequent to the last internal recognized point when searching a section exit. The two points define, each other, a boundary crossing. An element is considered an internal point to sections: a. Boundary point including continuity (DCT or airway keyword) with the previous and subsequent points when these are internal or boundary. Later on, the sections will be purged by means of IFR/VFR keywords. Points where flight rules are visual will be deleted. Following four type of sequences are considered: a. Sequence without flight rules change. The resulting sequence will be identical to the original one. b. Sequence where flight starts with visual rules and changes into instrumental rules: elem_1 elem_2 ... elem_i IFR elem_j ... elem_n It will remain as: elem_i IFR elem_j ... elem_n Whenever no erroneous IFR/VFR keyword is found in the deleted sequence. c. Sequence where flight starts with instrumental rules and changes to visual rules:
DOCUMENT N: 0029200000000MA03
elem_1 elem_2 ... elem_i VFR elem_j ... elem_n It will remain as: elem_1 elem_2 ... elem_i VFR Whenever no erroneous IFR/VFR keyword is found in the deleted sequence. d. Sequence where the points with visual rules are in between. elem_1 elem_2 ... elem_i VFR elem_j ... elem_i IFR elem_m ... elem_n It will be divided into two sections: elem_1 elem_2 ... elem_i VFR elem_i IFR elem_m ... elem_n Whenever no erroneous IFR/VFR keyword is found in the deleted sequence. Finally, boundary points in the extremes of the different obtained sections will be calculated. For the left section extreme, following cases will be presented:
1.
Sequence:
Boundary_pointRemaining_elements The boundary point is presented and there is no need of calculation.

2.
Sequence:
Internal_point_with_IFR_keyword Remaining_elements The boundary point is not calculated.

3.
Sequences: Point_2 Remaining_elements
Point_1
Continuity between Point_1 and Point_2. With Point_1 point external to the System and Point_2 point internal to the System; an intermediate point matching the border will be calculated. The calculated point will replace Point_1 the VALIDATE_BOUNDARY_POINT error will mark it.
4.
Sequences:
Point_1 Point_2 Remaining_elements With Point_1 and Point_2 points internal to the System and being continuous the route defined by those points, both belong to one airway crossing through them and fulfilling direction and level conditions. That airway will be travelled in the direction (Point_1 => Point_2); if a boundary point is found before Point_1, the points belonging to the airway will be inserted into the Route elements: Boundary_point Point_to ... Point_previous_to_Point_1 These last points will be marked to validate them with VALIDATE_BOUNDARY_POINT error.
5.
Sequence:
{Near external aerodrome} Internal_Point A point of the line joining both points that is in the border to the System controlled airspace will be calculated. It will be inserted before Internal_Point and will be marked with VALIDATE_BOUNDARY_POINT error.
6.
Remaining cases. It is not calculated. If first section element is correct, it will be marked with VALIDATE_BOUNDARY_POINT error.
DOCUMENT N: 0029200000000MA03
For the right section extreme, following cases will be presented:

1.
Sequence:
Remaining_elementsBoundary_point The boundary point is presented and there is no need of calculation.

2.
Sequence:
Remaining_elements Internal_point_with_IFR_keyword The boundary point is not calculated.

3.
Sequences: Point_2 Point_1
Remaining_elementsPoint_2 DCT Point_1 Remaining_elements Continuity between Point_1 and Point_2. With Point_1 point external to the System and Point_2 point internal to the System; an intermediate point matching the border will be calculated. The calculated point will replace Point_1 and the VALIDATE_BOUNDARY_POINT error will mark it.
4.
Sequences:
Remaining_elementsPoints_2 Points_1 With Point_1 and Point_2 points internal to the System and being continuous the route defined by those points, both belong to one airway crossing through them and fulfilling direction and level conditions. That airway will be travelled in the direction (Point_2 => Point_1); if a boundary point is found subsequent to Point_1, the points belonging to the airway will be inserted into the Route elements: Point_subsequent_to_Point_1 ... Point_to Boundary_point These last points will be marked to validate them with VALIDATE_BOUNDARY_POINT error.
5.
Sequence:
Internal_Point {Near external aerodrome} A point of the line joining both points that is in the border to the System controlled airspace will be calculated. It will be inserted subsequent to Internal_Point and will be marked with VALIDATE_BOUNDARY_POINT error.
6.
Remaining cases. It is not calculated. If last section element is correct, it will be marked with VALIDATE_BOUNDARY_POINT error.
Special cases where section is considered correct. {Sacta Departure} DCT POINT_COORDINATE DCT {Sacta Destination} {Sacta Departure} DCT BOUNDARY_point/BOUNDARY_coordinate {Non_Sacta Destination} {Non_Sacta Destination} Departure} BOUNDARY_point/BOUNDARY_coordinate DCT {Non_Sacta
{Sacta Departure} DCT POINT/COORDINATE DCT {Near_Non_Sacta_Destination} {Near_Non_Sacta_Departure} DCT POINT/COORDINATE DCT {Sacta Destination}
Page D-19
DOCUMENT N: 0029200000000MA03
In this case, there is section once the followed trajectory is known, this is within the controlled airspace, covering the whole section where the FP has to receive assistance and the section consists of more than one point, even when only one is specified.
Standard Routes Calculation

When any error is detected in either the Purged Route or Calculated Route, Standard Routes will be attempted to get between the two aerodromes. To obtain those Standard Routes, the Adaptation Data Tables will be accessed. Those Standard Routes defined between the departure and destination aerodromes will be search. If none is found, Standard Routes will be attempted to obtain between the first Route element and the destination aerodrome. If none is found, Standard Routes will be attempted to obtain between the departure aerodrome and the last Route point. Finally, if none is found, Standard Routes will be attempted to obtain between the first and last Route point. If there is a Standard Routes set, those fulfilling the following conditions will be selected from the set: To be valid the day the flight will be executed. The Standard Routes altitudes interval allows the cruising level for the FP. If there is more than one Route fulfilling these conditions, those closest to the Route valid point will be selected.
D.4
Errors Display
If erroneous elements were detected in either the Purged Route or Calculated Route, those elements will be displayed in the Routes Table of the underlined Display Area. When the cursor lays on an E/R field character. A message corresponding to the first detected error will be displayed on the MESSAGE field of the Information Area. If the Purged Route has any erroneous element, the message corresponding to the first erroneous element (underlined) will be displayed going through the route from left to right. If the Purged Route is correct but not the Calculated Route, the message will correspond to the first erroneous element (underlined) found in the Calculated Route when going through this from left to right. When the cursor lays on an E/R field character and no erroneous element is found both in the Purged Route and Calculated Route, a message is displayed on the MESSAGE field with the text CORRECT FIELD or a general-purpose message such as FIR TIME NOT CALCULABLE, text with blank spaces,
D.5
Route Field Messages
When the cursor is on an E/R field character. Any of the following texts may be displayed on the MESSAGE field of the Information Area: CORRECT FIELD. INCORRECT EDITION. UNKNOWN ELEMENT. FIELDS INCOHERENCE. DISCONTINUITY. VALIDATE BOUNDARY POINT.
Page D-20
DOCUMENT N: 0029200000000MA03
D.6
Error Message of Route Field Incorrect Edition
Description A Morphological error has been detected in the analysis; the erroneous element is underlined when displayed. User Options There are two options for the user: Erroneous field correction. Rejection of the function in process.
Unknown Element
Description An error has been detected while analyzing, the element is unknown by the System and element is underlined when displayed. User Options There are two options for the user: Erroneous field correction. Rejection of the function in process.
Fields Incoherence
Description An error may happen in some of the following circumstances: When validating a determined element position within the characters string and its relation with neighbouring elements. That element is underlined. When a Fictitious Points sequence is not properly defined. The sequence is underlined. When the level defined for the airway is not compatible with the existing cruising level when analyzing the airway. The airway is underlined. When the element is cruise climb or point with associated speed and level, if values are not compatible with the aircraft characteristics. The whole element is underlined. When the element is point with associated time, speed and level, if speed and level values are not compatible with the aircrafts characteristics. The speed and level element is underlined. When the element is point with associated speed and level and previous element is not a point with associated time, the last one is underlined. When there is some of the GA (OAT) or OMA (GAT) keywords but there is no x in the Flight Type field. User Options There are two options for the user: Erroneous field correction. Current function rejection.
DOCUMENT N: 0029200000000MA03
Discontinuity
Description An error has been detected when performing the continuity hypothesis according to point 3 of this annex. The elements making up the erroneous sequence are underlined. User Options There are two options for the user: Discontinuity deletion by following the continuity criteria as established in point 3 of this annex. Function rejection.
Validate Boundary Point

Description This message may happen in some of the following circumstances: When a point is calculated, between one external point and another internal one, which belongs to the border. Only the calculated point that replaces the external element is underlined. When a boundary point is calculated by going through an airway until reaching the border. All inserted points are underlined. User Options As follows: Change the current route for the calculated one and click to validate the boundary point.
Page D-22
DOCUMENT N: 0029200000000MA03
Appendix E - Flight Plan Strips

The System generates the flight plan strips and sends the information to the proper printers. There are two types of flight plan strips to print automatically: Warning or Pre-Activation Strips (Departure and Arrivals) Flight Plan Progression Strips (Progression) Pre-Activation Strips: These are generated to the Tower Position (if it exists) as well as to the first APP sector responsible for the flight departure aerodrome when the Flight Plan changes its status to notified. These are generated for a flight entering into the FIR in the first entry sector. Progression Strips: These are generated for all sectors involved in a flight a time (VSP) before entering into each one of the sectors. Progression Strips are generated again when: There is an important modification of the estimates in the route fixpoints. There is a modification of the route fixpoints. Any flight plan strip is generated under manual request. When there is failure in the current printer, the flight plan strip is sent to the alternative one.
Page E-1
DOCUMENT N: 0029200000000MA03
Flight Plan Strips are configurable in both format and content by means of an edition tool. Following figures represent the different Flight Plan Strips: Warning or Pre-Activation Strip (Arrival)
Figure E-1:
Callsign ETA Aircraft Type /Wake Turbulence Cruising Speed Aerodrome FP Route
Flight Plan Strip Type A (Arrival)

RVSM Entry Point Entry Time Strip printing date and time Strip Type
Warning or Pre-Activation Strip (Departure)
Figure E-2:
Callsign
Flight Plan Strip Type D (Departure)

FP Route Departure Time Strip Type
Aircraft Type /Wake Turbulence Aerodrome
Cruising Speed
SSR Code
Strip printing date and time
Page E-2
DOCUMENT N: 0029200000000MA03
Progression Strip
Figure E-3:
Flight Plan Strip Type P (Progression)
Callsign
Previous Point
Passing Time
Flight Level
Plan
Next Point
Departure Aerodrom e
FP Route
Strip Type
Aircraft Type /Wake Turbulence Cruising Speed
Time
Significative Point
Time
FP Route
Destination Aerodrome
RVSM SSR Code
Strip printing date and time
Strip Version
Page E-3
DOCUMENT N: 0029200000000MA03
Page intentionally left blank
This is the last page of this document
Page E-4

0029200000000ma03 2-0 Sdd-Um

Cargado por

Información del documento

Descripción original:

Título original

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

0029200000000ma03 2-0 Sdd-Um

Cargado por

Copyright:

Formatos disponibles

Supply, Installation, Testing and Commissioning of Tower ATS Automation System

Situation Data Display User Manual (SDD-UM)

Indra Sistemas, S.A.

Edition: 2 Revision:0 Date: 04 November2010

This page left intentionally blank

Situation Data Display User Manual

Edition: 2 Revision:0 Date: 04 November2010

This page left intentionally blank

Situation Data Display User Manual

Edition: 2 Revision:0 Date: 04 November2010

PAGE EDITION AND REVISION RECORD

Situation Data Display User Manual

Edition: 2 Revision:0 Date: 04 November2010

This page left intentionally blank

Situation Data Display User Manual

Edition: 2 Revision:0 Date: 04 November2010

REGISTER OF CHANGES TO THE DOCUMENT

DATE 2010-08-04 2010-11-04

AFFECTED PAGES All All First Edition Second Edition

REASON FOR CHANGE

Situation Data Display User Manual

Edition: 2 Revision:0 Date: 04 November2010

This page left intentionally blank

Situation Data Display User Manual

Edition: 2 Revision:0 Date: 04 November2010

Functional Description ....................................................................................................... 2-1 2.1.1

Edition: 2 Revision:0 Date: 04 November2010

Situation Data Display User Manual

Edition: 2 Revision:0 Date: 04 November2010

Edition: 2 Revision:0 Date: 04 November2010

Situation Data Display User Manual

Edition: 2 Revision:0 Date: 04 November2010

2.3.4 2.3.5 2.3.6

Situation Data Display User Manual

Edition: 2 Revision:0 Date: 04 November2010

Edition: 2 Revision:0 Date: 04 November2010

SDD General Information Area in Supervision Mode ................................................ 2-220

Appendix B - System Messages List ........................................................................................ B-1

Situation Data Display User Manual

Edition: 2 Revision:0 Date: 04 November2010

This page left intentionally blank

Situation Data Display User Manual

Edition: 2 Revision:0 Date: 04 November2010

Situation Data Display User Manual

Edition: 2 Revision:0 Date: 04 November2010

This page left intentionally blank

Situation Data Display User Manual

Edition: 2 Revision:0 Date: 04 November2010

Table 34: Track Flight Plan Route Label ................................................................................. 2-65

Situation Data Display User Manual

Edition: 2 Revision:0 Date: 04 November2010

This page left intentionally blank

Situation Data Display User Manual

Edition: 2 Revision:0 Date: 04 November2010

General System Description

Edition: 2 Revision:0 Date: 04 November2010

Situation Data Display User Manual

Edition: 2 Revision:0 Date: 04 November2010

Situation Data Display (SDD) Position Overview

Situation Data Display User Manual

Edition: 2 Revision:0 Date: 04 November2010

Notation Used in this Manual