0029200000000MA04_2-0_FDD-UM

Supply, Installation, Testing and Commissioning of Tower ATS Automation System Flight Data Display User Manual (FDD-UM) Edition: 2 Revision: 0

2 November 2010 Document Number: 0029200000000MA04 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 Torrejón de Ardoz Madrid, Spain Indra Proprietary Information This document contains proprietary data pertaining to items, or components, or processes or other matter developed or acquire d 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º: 0029200000000MA04

Edition: 2 Revision:0 Date: 2 November 2010

This page left intentionally blank

Flight Data Display User Manual

Use or Disclosure of this information is subject to the restrictions on the tile page of this document

Page ii






Page iv



PAGE EDITION AND REVISION RECORD

This document contains the following pages in the indicated editions and revisions PAGE

EDITION

REVISION

All

Draft

0

All

1

0

All

2

0


PAGE

EDITION REVISION

PAGE


EDITION REVISION

Page v






Page vi



REGISTER OF CHANGES TO THE DOCUMENT

EDITION

REVISION

DATE

AFFECTED PAGES

Draft

0

2010-07-30

All

Draft Edition

1

0

2010-08-04

All

First Edition

2

0

2010-11-02

All

Second Edition


REASON FOR CHANGE


Page vii






Page viii



Table of Contents 1

Introduction ...................................................................................................................... A-1 1.1

Scope ....................................................................................................................... A-1

1.2

General system description ........................................................................................ A-1

1.3

Flight Data Display (FDD) Position Overview .............................................................. A-4

1.4

Organization of this Manual ........................................................................................ A-5

1.5

Conventions Used in this Document ........................................................................... A-5

1.6

Selecting Menus, Icons and Field Text Entering .......................................................... A-6

1.6.1

Rules to Enter or Delete Data ............................................................................ A-8

1.7

Common actions in all FDD windows.......................................................................... A-9

1.8

Procedures to Close Actions in Windows ...................................................................A-10

2

Reference Documents .....................................................................................................A-11

3

Functional and Operational Description ............................................................................A-13 3.1

FDD General Information Area (GI_A) .......................................................................A-14

3.1.1 “Q” Queue: AFTN-FP Messages Area (FPM) ....................................................A-15 3.1.1.1 AFTN-FP Messages Validation ..................................................................A-16 3.1.1.2 RVSM Validation .......................................................................................A-17 3.1.1.3 AFTN-FP Messages Action Execution ........................................................A-17 3.1.1.4 AFTN-FP Messages De-queue (“Q”) ..........................................................A-19 3.1.1.4.1 AFTN-FP Correction Windows ............................................................A-20 3.1.1.4.1.1 AFTN-FP Messages Correction Window .....................................A-21 3.1.1.4.1.2 AFTN-FP Text Window ..............................................................A-21 3.1.1.4.1.3 Associated FPs List....................................................................A-22 3.1.1.4.1.4 Action: AFTN Message De-queue (FP Messages) .......................A-22 3.1.1.4.2 AFTN-NOTAM Messages Correction Window ......................................A-23 3.1.2 “AAI” Queue: Erroneous AFTN Header Area (EAH)...........................................A-24 3.1.2.1 “AAI” Messages De-queue.........................................................................A-26 3.1.2.1.1 “AAI” Messages Window .....................................................................A-26 3.1.2.1.2 “AAI” Error Window .............................................................................A-27 3.1.2.1.3 “AAI” Messages Correction Window ....................................................A-27 3.1.2.1.4 “AAI” Window .....................................................................................A-30 3.1.2.1.4.1 Action: AFTN Messages De-queue (Erroneous AFTN Message Header) .....................................................................................A-31 3.1.3 3.2

FDP Failure .....................................................................................................A-32

FDD Main Menu Area (MM_A) ..................................................................................A-34

3.2.1 Icon [FP Act.] Actions on Flight Plans ...............................................................A-35 3.2.1.1 FP Operation Window ...............................................................................A-35 3.2.1.1.1 Flight Plan Status................................................................................A-35 3.2.1.1.2 Edition Area ........................................................................................A-36 3.2.1.1.2.1 Rules for Entering Data ..............................................................A-40 3.2.1.1.2.2 “Route” Field Validation Rules ....................................................A-40 3.2.1.1.3 Command Area ..................................................................................A-42



Page ix



3.2.1.1.3.1 Action: Common Step to Actions on FPs .....................................A-43 3.2.1.1.3.2 Action: Visualize FPL .................................................................A-43 3.2.1.1.3.3 Action: View List of FP Synonyms...............................................A-43 3.2.1.1.3.4 Action: FPL History ....................................................................A-44 3.2.1.1.3.5 Action: Create FPL.....................................................................A-45 3.2.1.1.3.6 Action: Create a Current FPL (CREATE CURRENT) ...................A-45 3.2.1.1.3.7 Action: Modify FPL .....................................................................A-46 3.2.1.1.3.8 Action: Cancel FPL ....................................................................A-46 3.2.1.1.3.9 Action: FP Notification ................................................................A-47 3.2.1.1.3.10 Action: FP Notification Cancel ....................................................A-47 3.2.1.1.3.11 Action: Confirm/Modify ATD .......................................................A-48 3.2.1.1.3.12 Action: Cancel ATD....................................................................A-48 3.2.1.1.3.13 Action: Estimate Actions .............................................................A-48 3.2.1.1.3.14 Action: Passing over Fixpoint......................................................A-49 3.2.1.1.3.15 Action: Confirm/Modify ATA ........................................................A-49 3.2.1.1.3.16 Action: Cancel ATA ....................................................................A-50 3.2.1.1.3.17 Action: AFTN SEND ...................................................................A-50 3.2.1.1.3.18 Action: FP Route Modification .....................................................A-52 3.2.1.1.4 Error Message Area ............................................................................A-52 3.2.1.1.5 List of Synonyms ................................................................................A-52 3.2.1.1.6 Area Warnings Window .......................................................................A-52 3.2.2 Icon [FP Rtr.] Actions on Retrieved FP ..............................................................A-53 3.2.2.1 FP Retrieval Window .................................................................................A-53 3.2.2.1.1 Edition Area ........................................................................................A-54 3.2.2.1.2 Command Area ..................................................................................A-55 3.2.2.1.2.1 Action: Retrieve Multiple FPL......................................................A-55 3.2.2.1.3 Error Message Area ............................................................................A-55 3.2.2.1.4 Retrieved Flight Plan(s) Window ..........................................................A-56 3.2.3 Icon [FP MIN.] Minimal Flight Plan ....................................................................A-57 3.2.3.1 Minimal FP Window ...................................................................................A-57 3.2.3.1.1 Edition Area ........................................................................................A-57 3.2.3.1.2 Command Area ..................................................................................A-58 3.2.3.1.2.1 Action: Create a Minimal FP .......................................................A-58 3.2.3.1.3 Error Message Area ............................................................................A-58 3.2.4

Icon [RPL Act.] Actions on Repetitive Flight Plans .............................................A-58

3.2.5

[Hist Rtr.] Icon..................................................................................................A-59 3.2.5.1.1 Command Area ..................................................................................A-59 3.2.5.1.2 “Historical Retrieved Flight Plan(s)” Window ........................................A-60 3.2.5.1.3 “Historical Information” Window ...........................................................A-61 3.2.5.2 Action: Historical Retrieve => {[Hist Rtr.]}....................................................A-61

3.2.1 [FINDER] Icon .................................................................................................A-63 3.2.1.1 “FINDER” Window .....................................................................................A-64 3.2.1.1.1 Edition Area........................................................................................A-64 3.2.1.1.2 Command Area ..................................................................................A-64 3.2.1.2 Action: Retrieve FP by SSR Code => {[FINDER]} .......................................A-64 3.2.1.3 RPL Operation Window .............................................................................A-65 3.2.1.3.1 Edition/Activation Area ........................................................................A-65 3.2.1.3.2 Command Area ..................................................................................A-67 3.2.1.3.2.1 Action: Common Steps in Actions on RPLs .................................A-67 3.2.1.3.2.2 Action: Visualize RPL .................................................................A-68 3.2.1.3.2.3 Action: Create RPL ....................................................................A-68



Page x



3.2.1.3.2.4 Action: Modify RPL ....................................................................A-68 3.2.1.3.2.5 Action: Cancel RPL ....................................................................A-69 3.2.1.3.3 Error Message Area ............................................................................A-69 3.2.2 Icon [RPL Rtr.] Repetitive Flight Plans Retrieval ................................................A-69 3.2.2.1 RPLs Retrieval Window .............................................................................A-70 3.2.2.1.1 Edition/Activation Area ........................................................................A-70 3.2.2.1.2 Command Area ..................................................................................A-70 3.2.2.1.2.1 Action: Retrieve Multiple RPLs ...................................................A-71 3.2.2.1.3 Error Message Area ............................................................................A-71 3.2.2.2 Retrieved RPLs Window ............................................................................A-72 3.2.3 Icon [Runw] Airport Runways Actions ...............................................................A-72 3.2.3.1 Airport Runways Window ...........................................................................A-72 3.2.3.1.1 Edition Area ........................................................................................A-73 3.2.3.1.2 Command Area ..................................................................................A-73 3.2.3.1.2.1 Action: Visualization of Airport Runways .....................................A-73 3.2.3.1.2.2 Action: Modify Airport Runways ..................................................A-74 3.2.3.1.3 Error Message Area ............................................................................A-74 3.2.4 Icon [AFTN TX] AFTN Transmission .................................................................A-74 3.2.4.1 ICAO AFTN Transmission Window ............................................................A-74 3.2.4.1.1 Edition Area ........................................................................................A-75 3.2.4.1.2 Command Area ..................................................................................A-79 3.2.4.1.2.1 Action: Edit/Transmit ICAO AFTN Messages...............................A-80 3.2.4.1.3 Error Message Area ............................................................................A-80 3.2.4.2 ICAO ADEXP Transmission Window ..........................................................A-80 3.2.4.2.1 Edition Area ........................................................................................A-81 3.2.4.2.2 Command Area ..................................................................................A-86 3.2.4.2.2.1 Action: Edit/Transmit ICAO ADEXP Messages ............................A-86 3.2.4.2.3 Error Message Area ............................................................................A-86 3.2.4.3 Free AFTN Transmission Window ..............................................................A-87 3.2.4.3.1 Edition Area ........................................................................................A-87 3.2.4.3.2 Command Area ..................................................................................A-87 3.2.4.3.2.1 Action: Edit/Transmit Text AFTN Messages ................................A-87 3.2.4.3.3 Error Message Area ............................................................................A-89 3.2.4.4 SVC Transmission Window........................................................................A-89 3.2.4.4.1 Edition Area ........................................................................................A-90 3.2.4.4.2 Command Area ..................................................................................A-90 3.2.4.4.2.1 Action: Transmit SVC Messages ................................................A-91 3.2.5 Icon [ARCHIVE] ...............................................................................................A-92 3.2.5.1 AFTN Retrieve ..........................................................................................A-92 3.2.5.1.1 AFTN Retrieve Window .......................................................................A-92 3.2.5.1.1.1 Edition Area ...............................................................................A-93 3.2.5.1.1.2 Command Area..........................................................................A-93 3.2.5.1.1.2.1 Action: Retrieve Multiple AFTN Messages ............................A-94 3.2.5.1.1.3 Error Message Area ...................................................................A-95 3.2.5.1.2 Retrieve Multiple AFTN Window ..........................................................A-95 3.2.5.1.3 AFTN Element Window .......................................................................A-96 3.2.5.1.3.1 Edition Area ...............................................................................A-96 3.2.5.1.3.2 Error Message Area ...................................................................A-97 3.2.5.1.3.3 Command Area..........................................................................A-97 3.2.5.2 OLDI Retrieve ...........................................................................................A-97 3.2.5.2.1 Edition Area ........................................................................................A-98 3.2.5.2.2 Error Message Area ............................................................................A-98 Flight Data Display User Manual


Page xi


3.2.5.2.3


Command Area ..................................................................................A-98

3.2.6 Icon [A.P.] Airport Pressure ..............................................................................A-98 3.2.6.1 Airport Pressure Window ...........................................................................A-98 3.2.6.1.1 Element List Area ...............................................................................A-99 3.2.6.1.2 Edition Area ........................................................................................A-99 3.2.6.1.3 Command Area ..................................................................................A-99 3.2.6.1.3.1 Action: QNH and Transition Level Visualization ......................... A-100 3.2.6.1.3.2 Action: Modify QNH and Transition level ................................... A-101 3.2.6.1.4 Error Message Area .......................................................................... A-101 3.2.7 Icon [WINDS] Wind Data ................................................................................ A-101 3.2.7.1 Winds Data Window ................................................................................ A-102 3.2.7.1.1 Edition Area ...................................................................................... A-102 3.2.7.1.2 Command Area ................................................................................ A-103 3.2.7.1.2.1 Action: Visualization of Wind Data ............................................ A-103 3.2.7.1.2.2 Action: Modify Wind Data ......................................................... A-104 3.2.7.1.3 Error Message Area .......................................................................... A-104 3.2.8 Icon [AREAS] Restricted Areas ...................................................................... A-104 3.2.8.1 Restricted Areas Window......................................................................... A-105 3.2.8.1.1 Element List Area ............................................................................. A-106 3.2.8.1.2 Description Area ............................................................................... A-107 3.2.8.1.3 Activation/Validity Area ..................................................................... A-108 3.2.8.1.4 Layout Area ...................................................................................... A-109 3.2.8.1.5 Command Area ................................................................................ A-110 3.2.8.1.5.1 Action: Common Step to Restricted Areas Operations ............... A-110 3.2.8.1.5.2 Action: Create Restricted Area ................................................. A-111 3.2.8.1.5.3 Action: Modify Restricted Area .................................................. A-112 3.2.8.1.5.4 Action: Cancel Restricted Area ................................................. A-113 3.2.8.1.6 Error Message Area .......................................................................... A-113 3.2.9 Icon [FLOW] Air Traffic Flow........................................................................... A-114 3.2.9.1 Flow FP Window ..................................................................................... A-114 3.2.9.1.1 Filters Edition Area ........................................................................... A-116 3.2.9.1.2 Command Area ................................................................................ A-116 3.2.9.1.2.1 Action: FPLs Flow .................................................................... A-116 3.2.9.2 FPs Traffic Flow List ................................................................................ A-119 3.2.9.2.1 Command Area ................................................................................ A-123 3.2.9.3 FPs Traffic Congestion List ...................................................................... A-124 3.2.10 Icon [METEO] Meteorological Data ................................................................. A-125 3.2.10.1 Meteorological Information Window .......................................................... A-127 3.2.10.1.1 Selected Message ............................................................................ A-127 3.2.10.1.2 Airport Selection ............................................................................... A-127 3.2.10.1.3 Edition Area ...................................................................................... A-127 3.2.10.1.4 Command Area ................................................................................ A-128 3.2.10.1.4.1 Action: Edit Meteorological Page .............................................. A-128 3.2.11 [NOTAM] Icon ................................................................................................ A-129 3.2.11.1 NOTAM Operation/Retrieval Window ....................................................... A-129 3.2.11.2 Edition Area ............................................................................................ A-130 3.2.11.3 Command Area ....................................................................................... A-131 3.2.11.3.1 Action: Common Action to NOTAM Procedures ................................. A-132 3.2.11.3.2 Action: Create a New NOTAM ........................................................... A-132 3.2.11.3.3 Action: Modify NOTAM...................................................................... A-133 3.2.11.3.4 Action: Cancel NOTAM ..................................................................... A-134 Flight Data Display User Manual


Page xii



3.2.11.3.5 Action: Retrieve Multiple NOTAM ...................................................... A-134 3.2.11.4 Error Message Area ................................................................................ A-135 3.2.12 [T. Flow] Icon ................................................................................................. A-135 3.2.12.1 “FP Flow Actions” Window ....................................................................... A-135 3.2.12.1.1 Edition Area ...................................................................................... A-136 3.2.12.1.2 Command Area ................................................................................ A-136 3.2.12.2 “Flow Restrictions” Window...................................................................... A-137 3.2.12.2.1 Edition Area ...................................................................................... A-137 3.2.12.2.2 Command Area ................................................................................ A-137 3.2.12.3 “Retrieve FP‟s Flow” Window ................................................................... A-138 3.2.12.3.1 Edition Area ...................................................................................... A-138 3.2.12.3.2 Command Area ................................................................................ A-138 3.2.12.3.3 Retrieved FPs List ............................................................................ A-139 3.2.12.4 “Retrieve Slots Flow” Window .................................................................. A-139 3.2.12.4.1 Edition Area ...................................................................................... A-140 3.2.12.4.2 Command Area ................................................................................ A-141 3.2.12.4.3 Retrieved Slots List ........................................................................... A-141 3.2.12.5 Action: Allocate FP to a Slot Element (FixPoint) => {[T.Flow] => [FP Act.]} . A-141 3.2.12.6 Action: Exchange FPs Distribution => {[T.Flow] => [FP Act.]} .................... A-142 3.2.12.7 Action: Cancel FP Distribution => {[T.Flow] => [FP Act.]}........................... A-143 3.2.12.8 Element Slots Procedures => {[T.Flow]=> [Slot Act.]} ................................ A-144 3.2.12.8.1 Action: Visualize Slots => {[T.Flow] => [Slot Act.]} .............................. A-144 3.2.12.8.2 Action: Create Slots => {[T.Flow] => [Slot Act.]}.................................. A-145 3.2.12.8.3 Action: Modify Slots => {[T.Flow] => [Slot Act.]} .................................. A-147 3.2.12.8.4 Action: Cancel Slots => {[T.Flow] => [Slot Act.]} ................................. A-148 3.2.12.9 Action: Retrieve Multiple FPs Distribution => {[T.Flow] => [FPs/ Slot Ret] => [FP]} .................................................................................................. A-149 3.2.12.10 Action: Retrieve Multiple Slots Distribution => {[T.Flow] => [FPs/ Slot Ret] => [SLOTS]}............................................................................................ A-151 3.2.13

Icon [LINES] AFTN Lines Status ..................................................................... A-153

3.2.14 [INFO] Icon .................................................................................................... A-154 3.2.14.1 INFO Window.......................................................................................... A-154 3.2.14.1.1 Command Area ................................................................................ A-154 3.2.15 Icon [EST] Estimate ....................................................................................... A-155 3.2.15.1 EST Window ........................................................................................... A-155 3.2.15.1.1 Edition Area ...................................................................................... A-156 3.2.15.1.2 Command Area ................................................................................ A-156 3.2.15.1.2.1 Action: Quick Estimate Procedure............................................. A-156 3.2.16

[FREE TEXT] Icon ......................................................................................... A-157

3.2.17

[CLOCK] Icon ................................................................................................ A-158

3.2.18 [LOGOUT] Icon .............................................................................................. A-158 3.2.18.1 Freeze Position ....................................................................................... A-159 3.2.19

[PRINTER] .................................................................................................... A-159

Appendix A - Abbreviations and Glossary of Terms ............................................................... A-161 A.1

List of Abbreviations ............................................................................................... A-161

A.2

Glossary of Terms .................................................................................................. A-167

Appendix B - FP Route ........................................................................................................ B-175



Page xiii



B.1

Definitions .............................................................................................................. B-175

B.2

Presentation of Obtained Routes When FP Analyzing .............................................. B-175

B.3

Route Field Analysis ............................................................................................... B-176

Appendix C - Errors Display .................................................................................................C-195 Appendix D - Route Field Messages .....................................................................................D-197 Appendix E - Error Message of Route Field .......................................................................... E-199 E.1

Incorrect Edition ..................................................................................................... E-199

E.2

Unknown Element .................................................................................................. E-199

E.3

Fields Incoherence ................................................................................................. E-199

E.4

Discontinuity........................................................................................................... E-200

E.5

Validate Boundary Point.......................................................................................... E-200

Appendix F - Coordination Messages ................................................................................... F-201 F.1

Reception and Processing of Coordination Messages .............................................. F-201

F.2

AIDC Coordination Messages ................................................................................. F-201

F.3

Local Functions Error Messages List ....................................................................... F-206

F.4

Coordination Messages Windows............................................................................ F-218

a.

ABI Received ......................................................................................................... F-219



Page xiv



List of Figures Figure 1-1:

Example of System Architecture ........................................................................ A-2

Figure 1-2:

Operative Description Example ......................................................................... A-6

Figure 1-4:

FP Action Window. Error detection .................................................................... A-8

Figure 3-1:

FDD General Screen....................................................................................... A-13

Figure 3-2:

FDD Tower with EFS Screen ........................................................................... A-14

Figure 3-3:

FDD General Information Area (GI_A) ............................................................. A-14

Figure 3-4:

AFTN-FP Messages Area ............................................................................... A-15

Figure 3-5:

AFTN-FP Messages Window (“Q”) .................................................................. A-19

Figure 3-6:

AFTN-FP Correction Windows – FPL Correction .............................................. A-21

Figure 3-7:

AFTN-NOTAM Messages Correction Window .................................................. A-23

Figure 3-8:

“AAI” Queue ................................................................................................... A-24

Figure 3-9:

“AAI” Queue ................................................................................................... A-25

Figure 3-10:

“AAI” Messages Window ................................................................................. A-27

Figure 3-11:

“AAI” Error Window ......................................................................................... A-27

Figure 3-12:

“AAI” Messages Correction Window ................................................................ A-28

Figure 3-13:

“AAI” Window ................................................................................................. A-30

Figure 3-14: FDP down ......................................................................................................... A-33 Figure 3-15:

Main Menu Area (MM_A) Without EFS ............................................................ A-34

Figure 3-16:

Main Menu Area (MM_A) With EFS ................................................................. A-34

Figure 3-17:

[FP Act.] Icon .................................................................................................. A-35

Figure 3-18:

FP Operation Window ..................................................................................... A-35

Figure 3-19:

FP Operation Window: Error Detection ............................................................ A-40

Figure 3-20:

List of Synonyms Window ............................................................................... A-44

Figure 3-21:

List of Synonyms ............................................................................................ A-52

Figure 3-22:

Area Warnings Window ................................................................................... A-53

Figure 3-23:

[FP Rtr.] Icon .................................................................................................. A-53

Figure 3-24:

FP Retrieval Window....................................................................................... A-54

Figure 3-25:

Retrieved FP Window. List Elements ............................................................... A-56

Figure 3-26:

[FP Min.] Icon ................................................................................................. A-57

Figure 3-27:

Minimal FP Window ........................................................................................ A-57

Figure 3-28:

[RPL Act.] Icon................................................................................................ A-59

Figure 3-29: “Hist Rtr.” Window ............................................................................................. A-59 Figure 3-30: “Hist Rtr.” Retrieved Window .............................................................................. A-60 Figure 3-31: Historical Information Window ............................................................................ A-61 Flight Data Display User Manual


Page xv



Figure 3-32: [FINDER] Icon ................................................................................................... A-63 Figure 3-33: “FINDER” Window ............................................................................................. A-64 Figure 3-34:

RPL Operation Window ................................................................................... A-65

Figure 3-35:

[RPL Rtr.] Icon ................................................................................................ A-69

Figure 3-36:

RPLs Retrieval Windows ................................................................................. A-70

Figure 3-37:

[Runw] Icon .................................................................................................... A-72

Figure 3-38:

Airport Runways Window ................................................................................ A-73

Figure 3-39:

[AFTN TX] Icon ............................................................................................... A-74

Figure 3-40:

ICAO AFTN Transmission Window .................................................................. A-75

Figure 3-41:

ICAO ADEXP Transmission Window ............................................................... A-81

Figure 3-42:

Free AFTN Transmission Window ................................................................... A-87

Figure 3-43:

SVC Transmission Window ............................................................................. A-90

Figure 3-44:

[ARCHIVE] Icon .............................................................................................. A-92

Figure 3-45:

AFTN Retrieve Window ................................................................................... A-92

Figure 3-46:

Retrieve Multiple AFTN Window ...................................................................... A-96

Figure 3-47:

AFTN Element Window ................................................................................... A-96

Figure 3-48: “OLDI Retrieve” Window .................................................................................... A-97 Figure 3-49:

[A.P.] Icon....................................................................................................... A-98

Figure 3-50:

Airport Pressure Window ................................................................................. A-99

Figure 3-51:

[WINDS] Icon ................................................................................................ A-101

Figure 3-52: Winds Data Window ........................................................................................ A-102 Figure 3-53: “Winds Data” Window: Error Detection ............................................................. A-103 Figure 3-54:

[AREAS] Icon ............................................................................................... A-105

Figure 3-55:

Restricted Areas Window .............................................................................. A-106

Figure 3-56:

Restricted Areas Window. Element List Area ................................................. A-107

Figure 3-57:

Restricted Areas Window. Description Area ................................................... A-107

Figure 3-58:

Restricted Areas Window. Activation/Validity Area.......................................... A-108

Figure 3-59:

Restricted Areas Window. Layout Area .......................................................... A-109

Figure 3-60:

Restricted Areas Window. Command Area .................................................... A-110

Figure 3-61:

[FLOW] Icon ................................................................................................. A-114

Figure 3-62:

FPs Traffic Flow Options ............................................................................... A-114

Figure 3-63:

Flow FP Window ........................................................................................... A-116

Figure 3-64:

FP Found for the given filter .......................................................................... A-120

Figure 3-65:


Figure 3-66:


Figure 3-68:

FPs Traffic Congestion List Graphic ............................................................... A-124



Page xvi



Figure 3-69:

[METEO] Icon ............................................................................................... A-125

Figure 3-70:

Meteorological Information Window ............................................................... A-127

Figure 3-71:

[NOTAM] Icon ............................................................................................... A-129

Figure 3-72:

NOTAM Operation/Retrieval Window ............................................................. A-130

Figure 3-73:

[LINES] Icon ................................................................................................. A-153

Figure 3-74:

AFTN Lines Status Window ........................................................................... A-153

Figure 3-75:

[INFO] Icon ................................................................................................... A-154

Figure 3-76:

PIP Window .................................................................................................. A-154

Figure 3-77:

[EST] Icon .................................................................................................... A-155

Figure 3-78:

EST Window................................................................................................. A-155

Figure 3-79:

EST Window................................................................................................. A-155

Figure 3-80: “FREE TEXT” Icon........................................................................................... A-157 Figure 3-81: Channel selection for Free Text........................................................................ A-157 Figure 3-82: “FREE TEXT” Window ..................................................................................... A-158 Figure 3-83: “CLOCK” Icon.................................................................................................. A-158 Figure 3-84: Clock Window ................................................................................................. A-158 Figure 3-85:

[LOGOUT] Icon ............................................................................................. A-159

Figure 3-86:

Login Window ............................................................................................... A-159

Figure 3-87:

Printer Selection ........................................................................................... A-160

Figure F-1:

Transitions of AIDC coordination messages .................................................... F-203



Page xvii






Page xviii



List of Tables Table 1-1:

Mouse Button Functions .................................................................................... A-7

Table 1-2:

Key Functions ................................................................................................... A-8

Table 3-1:

General Information Area (GI_A). Elements ..................................................... A-15

Table 3-2:

AFTN-FP Messages Window (“Q”). Filters ....................................................... A-20

Table 3-3:

AFTN-FP Messages Correction Window. Command Area ................................ A-21

Table 3-4:

AFTN-FP Text Window. Command Area .......................................................... A-22

Table 3-5:

AFTN-NOTAM Messages Correction Window. Command Area ........................ A-24

Table 3-6:

“AAI” Messages Correction Window. Command Area ....................................... A-28

Table 3-7:

“AAI” Window. Command Area ........................................................................ A-30

Table 3-8:

FDD Main Menu Area. Commands Icon Row ................................................... A-34

Table 3-9:

FP Operation Window. Edition Area ................................................................. A-36

Table 3-10:

FP Operation Window (action mode). Command Area ...................................... A-42

Table 3-11:

Area Warnings Window ................................................................................... A-53

Table 3-12:

FP Retrieval Window. Edition Area .................................................................. A-54

Table 3-13:

FP Retrieval Window. Command Area ............................................................. A-55

Table 3-14:

Retrieved Flight Plan(s) Window. List Element ................................................. A-56

Table 3-15:

Minimal FP Window. Edition Area .................................................................... A-57

Table 3-16:

Minimal FP Window. Command Area............................................................... A-58

Table 3-3:

RPL Operation Window. Edition/Activation Area ............................................... A-66

Table 3-4:

RPL Operation Window. Command Area ......................................................... A-67

Table 3-5:

RPLs Retrieval Window. Command Area ......................................................... A-70

Table 3-6:

Retrieved RPLs Window. List Element ............................................................. A-72

Table 3-7:

Airport Runways Window. Edition Area ............................................................ A-73

Table 3-8:

Airport Runways Window. Command Area ....................................................... A-73

Table 3-9:

ICAO AFTN Transmission Window. Edition Area.............................................. A-75

Table 3-10:

ICAO AFTN Transmission Window. Command Area ........................................ A-79

Table 3-11:

ICAO ADEXP Transmission Window. Edition Area ........................................... A-81

Table 3-12:

ICAO AFTN Transmission Window. Command Area ........................................ A-86

Table 3-13:

Free AFTN Transmission Window. Edition Area ............................................... A-87

Table 3-14:

Free AFTN Transmission Window. Command Area .......................................... A-87

Table 3-15:

SVC Transmission Window. Edition Area ......................................................... A-90

Table 3-16:

SVC Transmission Window. Command Area ................................................... A-90

Table 3-17:

AFTN Retrieve Window. Edition Area .............................................................. A-93

Table 3-18:

AFTN Retrieve Window. Command Area ......................................................... A-93

Table 3-19:

AFTN Element Window. Edition Area............................................................... A-96



Page xix



Table 3-20:

AFTN Element Window. Command Area ......................................................... A-97

Table 3-23:

Airport Pressure Window. Edition Area ............................................................ A-99

Table 3-24:

Airport Pressure Window. Command Area ....................................................... A-99

Table 3-25:

Winds Data Window. Edition Area ................................................................. A-102

Table 3-26:

Winds Data Window. Command Area ............................................................ A-103

Table 3-27:

Restricted Areas Window. Element List Area ................................................. A-107

Table 3-28:

Restricted Areas Window. Description Area ................................................... A-107

Table 3-29:

Restricted Areas Window. Activation/Validity Area.......................................... A-108

Table 3-30:

Restricted Areas Window. Layout Area .......................................................... A-109

Table 3-31:

Restricted Areas Window. Command Area .................................................... A-110

Table 3-32:

Flow FP Window. Filters Edition Area ............................................................ A-116

Table 3-33:

Flow FP Window. Command Area ................................................................. A-116

Table 3-34:

FPs Traffic Flow List. Aerodrome ................................................................... A-120

Table 3-35:

FPs Traffic Flow List. Fix ............................................................................... A-122

Table 3-36:

FPs Traffic Flow List. Sector .......................................................................... A-123

Table 3-37:

FPs Traffic Flow List. Command Area ............................................................ A-123

Table 3-38:

FPs Traffic Congestion List Graphic. Edition Area .......................................... A-124

Table 3-39:

FPs Traffic Congestion List Graphic. Graphical Area ...................................... A-124

Table 3-40:

FPs Traffic Congestion List Graphic. Command Area ..................................... A-124

Table 3-41:

Meteorological Information Window. Edition Area ........................................... A-127

Table 3-42:

Meteorological Information Window. Command Area...................................... A-128

Table 3-43:

NOTAM Operation/Retrieval Window. Edition Area ........................................ A-130

Table 3-44:

NOTAM Operation/ Retrieval Window. Command Area .................................. A-131

Table 3-2:

INFO Window. Command Area ..................................................................... A-154

Table 3-3:

EST Window. Edition Area ............................................................................ A-156

Table 3-4:

EST Window. Command Area ....................................................................... A-156



Page xx



1 Introduction The Flight Data Display (FDD) Position is one the AIRCON 2100 System components. Its aim is to provide a work environment to the operational personnel of the Air Traffic Control Centre for flight plans handling. This environment consists of an HMI computer (screen, mouse and keyboard) connected to the subsystem that manages Flight Plans so that the entire flight plan related information is easily reachable by the operator. The FDD Position allows the controller mainly to handle flight plans during the strat egic planning phase. That is, the controller of this position manages future flight plans (Flight plans received trough AFTN and Repetitive Flight Plans (RPL)).

1.1

Scope

The scope of this manual is the operational description of the FDD Position available at the AIRCON 2100 System. The intended audience of this manual is controllers who use the FDD 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.



Page A-1



Following figure shows a full-featured architecture for the AIRCON 2100 System:

Figure 1-1:

Example of System Architecture

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 flights‟ progression and keeps all controllers inform by means of screen displays and flight plan strips printing. The System is designed in redundant configuration, 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.



Page A-2



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, which is 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. Instructor Pilot Position (PILOT SM). (OPTIONAL) It allows the training scenarios selection, session control and control of aircraft simulated interactively in such a way that from this position the communication answer to the control positions is generated. Exercise Manager (ATG/EPP). (OPTIONAL) From this unit simulation, exercises are managed.



Page A-3


1.3


Flight Data Display (FDD) Position Overview

The FDD Position is based in a workstation that allows managing all information related with flight plans, AFTN messages, restricted areas, etc. The main functions of the FDD position are: FPL handling: Creation Visualization Modification Retrieval Deletion RPL handling: Creation Visualization Modification Retrieval Deletion AFTN messages handling: AFTN messages reception and correction AFTN messages edition and transmission Access to FPLs and RPLs databases Winds Data input Restricted Areas handling: Creation Visualization Modification Retrieval Deletion Flow Planning (FPLs) AFTN Lines Configuration NOTAM and Meteorological messages handling



Page A-4


1.4


Organization of this Manual

The FDD Position User Manual provides instructions on menus and operating windows. The manual consists of four chapters as described below: Chapter 1

Introduction

It provides an overview of the overall system, the FDD Position environment, and the contents of this manual. Finally, the conventions used in this manual are described. Chapter 2

Reference Documents

It present the reference document related with this manual. Chapter 3

Functional and Operational Description

It presents an explanation of each FDD Position software element, including all the descriptions for a complete starting contact. It describes the selection modes and all FDD Position windows. It also describes all the actions performed by means of the FDD windows such as, Flight Plan handling (FPL, RPL), Traffic Flow actions, AFTN messages handling and Meteorological Data functions. Appendix A Abbreviations and Glossary of Terms It presents the glossary of terms used in the manual as well as the abbreviation dictionary. Appendix B FP Route The characters string is. Appendix C Error Display It present an erroneous elements were detected. Appendix D Route Field Messange It present the different “MESSAGE” of the Information Area. Appendix E Error Message of Route Field It present the a Morphological error. Appendix F Local Functions Error Messages It present the definition of error messages. Appendix G Coordination Messages It present the three-phase process.

1.5

Conventions Used in this Document

“Select X” means to move the mouse so that the screen cursor is at the top of the X, and press and release left mouse button. “Press on X”, means the same as “Select X”. Capital letters describe colour assignment. Every window, operation, or command whose use must accomplish certain rules, is described together with the numbered list of those rules. The operational descriptions includes the following parts: Number of section and title Flight Data Display User Manual


Page A-5



“Access path to the function” and “Application” paragraph, if applicable Two columns that describe the steps to be performed. The first column describes the action to be carried out and the second one describes the result of that action.

Figure 1-2:

Operative Description Example

The icons and switches are listed in brackets; the menu options between parenthesis, edition fields and windows are listed between quotation marks. Description of windows includes the following parts: Window‟s layout figure Window‟s description Edition fields‟ description Window commands‟ description and operational behaviour Next figure illustrates some of the conventions used when making selections and editing data in the fields of the FDD windows.

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 FDD 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 A-6


Table 1-1:

Mouse Button Functions

Button Left button (LB)


Function Data entering, display pull-down menus Drag a window by “pressing and hold” the mouse central button on the window title Copy data field

Central button (CB)

Paste data field

Right button (RB)

Without a defined use

Pull-down menus: This menu is displayed upon clicking once on the icon. 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 CB. A pull-down menu comprises: An available options list for the icon. An option can be selected by clicking on it with the LB, which causes the menu to disappear. The corresponding window is displayed 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 [CANCEL] 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 window‟s name Edition fields to input data. Before editing data, the mouse cursor must be situated within the corresponding field. To validate the data, press 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.) An 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 is focused 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. An 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 be focused on the corresponding field. Click on the 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 A-7



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

Key Functions Function

Move the cursor position from one field to the following one.

+

Move the cursor position back from one field to the previous one.

Delete the character before the cursor position (within a field).

(Or )

Delete the character after the cursor position (within a field).

Left arrow: moves backward the cursor, character by character, within a field. Right arrow: moves forward the cursor, character by character, within a field.

1.6.1 Rules to Enter or Delete Data Windows contain “fields” where data can be input, (sometimes it is even compulsory). The following rules for entering data apply to all FDD windows. Input can only be made into a window if the “focus” is in 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 entering or modification Fields in WHITE accept data entering or modification. Fields in RED contents erroneous information or are compulsory fields.

Figure 1-3:

FP Action Window. Error detection

When an icon that opens a window is selected, both window and input cursor are automatically positioned inside the first editable field of the window. After entering data in one field, pressing on the keyboard, moves the cursor to the next field. Alternatively, use the input cursor. Pressing + on the keyboard, moves the input marker backward to the previous field. To enter data, double click to select the whole field and then type the new characters. For data elimination, the cursor must be placed after the character to erase, and press in the keyboard after the character is erased. It also is done by double click with the cursor in the data to erase for selecting it, and then enter the new characters.



Page A-8



Once the data input has finished, the system answers about the data input. It also presents information to accept or reject the action.

1.7

Common actions in all FDD windows

This section describes the functions to apply to all FDD windows. These actions are directly performed with the mouse on the corresponding window frame and/or title. These areas are light GREY: Change of position Click with LB over the title of the window. Keep on clicking with LB to drag the frame of the window to the new position Drop the LB. Move to foreground Move the mouse pointer to the edge of the window. Click on it with LB in the title bar of the window. Drop the LB and the operation is completed. Resize window Only for resizable windows, which have a resize button in the top right hand corner resizing:

. For

Click and keep clicked the resize button with LB. Drag the frame to the new position. Drop the LB. Transfer window Only for windows with this capacity, transfer between FDD and SDD. With a transfer icon in the top right hand corner . For transfer window:

Click in transfer button with LB. The window appears in the last position where was in SDD and disappears in FDD. To return FDD, click in the transfer icon with LB since SDD. The window appears in the last position where was in FDD and disappears in SDD. It is also possible to do the same action dragging the window since FDD to SDD and vice versa, keeping clicked LB over the window title and move it to the final position in the other window. Inhibit Click in bi-state icon. The text colour will turn from YELLOW to WHITE or to BACKGROUND colour. Active Click in bi-state icon. The text colour will turn from WHITE or BACKGROUND colour to YELLOW. Date format



Page A-9



LB click in labels which associated data are date, shows the appropriate format for data introduction.

1.8

Procedures to Close Actions in Windows Every action to be done have an ending by Windows/lists icons. The ending may be: Validation and closing Closing without validation Data erase Print Closing procedures will be explained by an example with the FP Operation Window example: ACTION

1.

Validation and closing 1.1. Clicking in [UPDATE] icon

RESULT If data entered are right, the FP Operation Window shows the FP that coincides with selection criteria.

If input data are erroneous, the System presents an error message to the controller.

If compulsory fields are not filled, an error message is shown to the controller. 1.2. Click in [CANCEL] icon 2.

Closing without validation 2.1. Click in [CANCEL] icon

3.

Data erasing

The FP Operation Window is closed, validating the action. The FP Operation Window is closed, without validating the action. Data entered are erased from FP Operation Window.

3.1. [CLEAR] icon 3.2. Click in [CANCEL] icon 4.

FP print

FP Operation Window is closed validating the action. The displayed Flight Plan is printed.

4.1. Click in [PRINT] icon



Page A-10



Reference Documents The next table shows all main references from standards, rules and procedures for Air Traffic Management referred in this document. REFERENCE Ref. [1]

Ref. [2]

TITTLE AND CODE

ORIGIN

Air Traffic Management - Procedures for Air Navigation Services (Doc. 4444)

ICAO

Originating Region SSR Code Assignment Method

EUROCONTROL

DATE 14th Edition 01/ 11/ 2001 1.0 30/09/2004

(ORCAM) Improvement Study Ref. [2]

EUR REGIONAL AIR NAVIGATION PLAN

ICAO

Supplement to EUR ANP FASID



CAL Ed 2 May 2006

Page A-11






Page A-12



2 Functional and Operational Description This chapter provides information for new users of the FDD Position. The screen has following main areas: General Information Area (GI_A) Main Menu Area (MM_A)

Figure 2-1:


FDD General Screen


Page A-13


Figure 2-2:

2.1


FDD Tower with EFS Screen

FDD General Information Area (GI_A)

This area is always displayed at the FDD position, that is, no device can close it. It is located on the top of the screen. Use this area to display windows from the MM_A and to access to the AFTN messages correction.

Figure 2-3:

FDD General Information Area (GI_A)

There are two different queues to manage the received messages: “Q” Queue: FP Messages (FPM): Body error messages “AAI” Queue: Erroneous AFTN Header (EAH) Following table describes the information:



Page A-14


Table 2-1:


General Information Area (GI_A). Elements

Item

Type

Description

“Q” AFTN Messages Counter

Information Box

Queue identifier and display of the number of stored AFTN messages

SUMMARY

Icon

Access to the AFTN list filtered in the “Q” queue. If the AFTN message is FP type, it is visualized in the AFTN-FP Correction Window (see 2.1.1.4.1) If the AFTN message is NOTAM type, it is visualized in AFTNNOTAM Correction Window (see 2.1.1.4.2)

“AAI” AFTN Messages Counter

Information Box

Queue identifier and display of the number of AFTN messages with erroneous header or SVC (non-repetition) messages, which are stored in the queue until they are processed

SUMMARY

Icon

Access to the AFTN message list with erroneous head, and to SVC message non-repetitive User can select one of them and visualize it.

2.1.1 “Q” Queue: AFTN-FP Messages Area (FPM) It is composed of several items: “Q” Queue identifier and AFTN Messages Counter [SUMMARY] icon to de-queue the messages. If clicked it on, a new window is displayed with the queued messages.

Figure 2-4:

AFTN-FP Messages Area

FP messages not automatically processed are sent to “Q” queue for its manual confirmation. These messages are the following ones: Body erroneous messages Correct and erroneous messages, when the processing for a type of messages has been conditioned (from the CMD position) to a manual confirmation from FDD position FP status non suitable for automatic processing Correct and erroneous NOTAM messages (always). MET messages (METAR, SPECI, TAF, SIGMET, ATIS, AIRMET, SNOWTAM and GAMET) with errors. FP messages following described have no automatic fields‟ validation. If there is no error, the modification messages cause the FP updating. If any field (not the ones marked as optional) cannot be detected nor has errors, the message is sent to the “Q” Queue for manual correction.

Following messages are received (from the IFPS or any other source), in ICAO format: FPL (Filed Flight Plan message)



Page A-15



CPL (Current Flight Plan message) CHG (Change message) DLA (Delay message) CNL (Cancel message) ARR (Arrival message) EST (Estimate message) POS (Position Report message) DEP (Departure message) RQP (Request FP message) ALR (Alarm) RCF (Radio Communication Failure message) AFP (Flight Plan Proposal message) SPL (Supplementary Flight Plan message) Following messages are received (from the IFPS or any other source), in ADEXP format: IFPL (Filed Flight Plan message) ICHG (Change message) IDLA (Delay message) ICNL (Cancel message) IARR (Arrival message) IDEP (Departure message) IRQP (Request FP message) IRQS (Request supplementary FP message) IAFP (Flight Plan Proposal message) IAPL (ATC Flight Plan message) All NOTAM messages, with their extracted fields, are placed in the FPM queue for manual confirmation. Other messages, regarded as “unknown”, including meteorological messages, are directly sent to the FPM queue.

2.1.1.1 AFTN-FP Messages Validation Regardless of the Flight Plan source, either received from AFTN / IFPS, or entered manually, all flight plans are checked for: Format errors



Page A-16



All flight plans are processed according to a common format, in which the exist ence or absence of each field will be accordingly marked. Syntax errors Messages are checked to verify that they conform to the corresponding standards and interface specifications. Semantic and Coherence errors Correctness and coherence of fields making up the message, and the coherence between the flight plan fields and the flight plan data will be analyzed. Compatibility Conformance between aircraft type, speed, flight level/ altitude, EET, departure aerodrome, route within the defined route system, destination, RVSM capability and 8.33 channel spacing versus airspace requirements will be analyzed. Previous receipt of the same flight plan Validity time Accessibility regarding flight plan status and source The flight plan status and the flight plan source establish if the proposed action on the flight plan can be performed. It is also verified that, for an SFPL in “ACTIVE” status, the source of the input is either the currently assigned sector, or a sector/unit involved in the future control of the flight, and a change to the SFPL at a sector work position does not affect the SFPL at a point upstream from the point at which the sector is responsible for the SFPL. Validity checks conform to ICAO and EUROCONTROL regulations, as well as to domestic specific practices. Erroneous messages received from AFTN / IFPS are sent to the FPM queue. The original text of the message, the flight plan data extracted from the message and the routes list (if the message included the route field) are sent to the queue management function. Erroneous messages from an FDD are returned to the operator. Any error detected during the validity checks will be highlighted to warn the control position where the data was entered. Along with the highlighted field, a message reports the type of error. Messages accepted by the System are entered into the FDP database.

2.1.1.2 RVSM Validation The RVSM information is extracted from the corresponding field in the Flight Plan. As a result, Flight Plans are identified as “RVSM Equipped”, “RVSM Non-Equipped”, “RVSM Unknown”, or “RVSM Exempted” flights. Finally, the FDP distributes the RVSM status to the System (SDP, FDDs and SDDs). The System has the capability to change the RVSM flight status according to the information received from the coordination messages and the manual input. The System permits the operator to temporarily disable the RVSM processing for RVSM aircraft. Likewise, the operator can temporarily impose the RVSM processing for non-RVSM aircraft.

2.1.1.3 AFTN-FP Messages Action Execution Once the message has been validated and the information properly extracted, the System executes the corresponding action for each type of message: Flight Data Display User Manual


Page A-17



An FPL/ IFPL creates a new flight plan, provided the flight plan does not exist; A CPL creates a flight plan in “Active” status or change an exiting one to “Active” status; A CHG/ ICHG changes the flight plan fields according to the message data; A DLA/ IDLA changes the flight plan's departure time and it changes to “Notified” or “Initial” status; A DEP/ IDEP updates the departure time and change the flight to “Active” status, provided the flight is departing from an aerodrome within the system responsibility area; An ARR/ IARR updates the ETA to ATA and mark the flight plan for termination; The System provides the capacity to undo the arrival indication as long as the SFPL is not deleted; After removal of the arrival indication, the SFPL is reverted to its prior status; A CNL/ ICNL cancels the flight plan, provided it is not in “Notified” or “Active” status; The System provides the capacity to undo a cancellation, through retrieving and re-creating the same flight plan; After undoing a cancellation, the flight plan is reverted to its initial status; An EST updates the flight plan ETOs and change the flight plan to “Active” status; A POS updates the flight plan ETOs and change the flight plan to “Active” status; A NOTAMN creates a new NOTAM in the database; A NOTAMR updates an existing NOTAM; A NOTAMC cancels the referred NOTAM; METAR, SPECI, TAF, ATIS, AIRMET, and SIGMET messages update the MET database for the corresponding aerodrome or FIR.



Page A-18



2.1.1.4 AFTN-FP Messages De-queue (“Q”) When clicking on the [SUMMARY] icon, the AFTN-FP Messages Window is displayed. The window allows displaying a limited number of messages but when this number exceeds the window size, a scroll bar is displayed to allow vertical and horizontal movement to view the remaining messages. The queue operates on a FIFO basis (first in, first out). However, entries to “Q” Queue are prioritized, that is, depending on the message type, the insertion criterion is different. This happens for NOTAM messages which have top priority. So these messages are included firstly in the queue (both corrected and erroneous) so the operator can acknowledge as soon as possible.

Figure 2-5:

AFTN-FP Messages Window (“Q”)

The AFTN-FP Messages Window (“Q”) has two main areas: Visualization Area: The “Q” Queue messages list is displayed in this area. The user may display the whole information of any message by clicking twice with the LB on the corresponding one. Command Area: The user may filter the messages by clicking with the LB on the corresponding message type icon. The selected type messages are not displayed, if the icon is activated (RED). The selected type messages are displayed, if it is inhibited (GREEN). Following table displays the different filters to perform:



Page A-19



Table 2-2:

AFTN-FP Messages Window (“Q”). Filters

Icon

Description

FP

Filter for AFTN-FP messages in the “Q” Queue. If it is selected, the FP messages are not displayed on the “Q” Queue but when the icon is released, they are visualized.

NOTAM

Filter for AFTN-NOTAM messages in the “Q” Queue. If it is selected, the NOTAM messages are not displayed on the “Q” Queue but when the icon is released, they are visualized.

TACT

Filter for AFTN-TACT messages in the “Q” Queue. If it is selected, the TACT messages are not displayed on the “Q” Queue but when the icon is released, they are visualized.

COORD

Filter for coordination messages (AFTN) in the “Q” Queue. If it is selected, the coordination messages are not displayed on the “Q” Queue but when the icon is released, they are visualized.

UNKNOWN

Filter for unknown messages in the “Q” Queue. If it is selected, the unknown messages are not displayed on the “Q” Queue but when the icon is released, they are visualized.

REFRESH

Updates the window entires.

CANCEL

Close the window.

The user may visualize one of these messages by clicking twice on any of them. The message is then displayed in any of the following windows: AFTN-FP Correction Windows In case the message type is AFTN "FP" and it is incorrect or it is correct but its automatic processing has been disabled by the CMD. AFTN-NOTAM Messages Correction Window In case, the message type is "NOTAM". The AFTN Messages Counter does not alter the number until the message has been properly corrected or deleted. The message selected in the queue by an FDD operator cannot be accessed by any other FDD.

2.1.1.4.1 AFTN-FP Correction Windows If receiving a correct AFTN message of “FP” type and the automatic process of this type of messages is activated in the CMD, it is automatically processed by the System. Otherwise, it is queued on the “Q” Queue. When clicking on the [SUMMARY] icon and clicking twice on any “FP” type message, this is displayed on three windows: AFTN-FP Messages Correction Window. FP template where the message is included. AFTN-FP Text Window. Message text as it was received. Associated FPs List (optional). It depends on whether the message may apply to more than one Flight Plan.



Page A-20


Figure 2-6:

2.1.1.4.1.1


AFTN-FP Correction Windows – FPL Correction

AFTN-FP Messages Correction Window

The AFTN-FP Messages Correction Window displays the message, within the corresponding fields, when double-clicking on any entry in the messages window. The displayed window is composed of the following areas: Window Title: It changes depending on the type of AFTN-FP message. Edition Area: It is composed by a set of fields where the System displays the data extracted from the AFTN-FP text message. The System indicates the erroneous fields for operator modification. Only WHITE and RED fields (compulsory or erroneous fields) are accessible to the operator. Error Message Area: It is where the System displays any error message to warn the operator of the erroneous fields. If the Error Message is “FP no exists”, another action is included in the AFTN-FP Messages Correction Window. This action provides the capacity to request the FP corresponding to the message received in the “Q” Queue. Command Area: It is composed by a set of icons that are described in the following table: Table 2-3:

AFTN-FP Messages Correction Window. Command Area

Icon

Description

PREV

Force the display of the previous AFTN message. If there is no previous message, the windows are closed.

NEXT

Force the display of the next AFTN message. If there is no next message, the windows are closed.

DELETE

Delete the current displayed message. The AFTN Message Counter is decreased one value (1).

UPDATE

Trigger the modification process performed on the message, if any, and process the message, if it is correct.

CANCEL

Close the windows and cancel any modification, if it was not previously triggered.

Rqp

Request the FP corresponding to the received message that has been sent to the “Q” Queue. (Only when the error in the received message is “FP no exist”).

2.1.1.4.1.2

AFTN-FP Text Window

It displays the AFTN-FP message in “text” format. Therefore, the information displayed is the same as for the AFTN-FP Messages Correction Window. The scroll bar allows the display of the message information not in view due to window size. Command Area: Following table describes the unique icon included in the AFTN-FP Text Window:



Page A-21



Table 2-4:

AFTN-FP Text Window. Command Area

Icon

Description

PRINT

Print the text of the AFTN message.

2.1.1.4.1.3

Associated FPs List

It displays the Flight Plans, which match the AFTN message callsign. The displayed fields of the FP are the same as those displayed on the Retrieved Flight Plan(s) Window (see point 2.2.2.1.4) plus the “FREE TEXT” field of the FP.

2.1.1.4.1.4

Action: AFTN Message De-queue (FP Messages)

ACTION

RESULT

1.

Click with the LB on the [SUMMARY] icon to request the queued AFTN message.

The System displays the “Q” Queue. The user filter the corresponding message, updates the messages in the queue or close the window.

2.

When clicking twice on any entry to correct the message.

The System Windows.

3.

Click on the icons [PREV] or [NEXT]

The next or previous AFTN message within the queue is displayed. The displayed message

4.

Once the message is selected, following actions can be performed: 4.1.

displays

the

AFTN-FP

Messages

Correction

Click with the LB on the [DELETE] icon A confirmation menu is displayed.

4.1.1.

Click in [YES ] icon

The displayed AFTN message is deleted from the queue (counter decreases in one unit).

4.2.

Click with the LB on the [CANCEL] icon

The displayed AFTN message is deleted from the window but it remains in the messages queue.

4.3.

Select the [Rqp] switch and click with the LB on the [UPDATE] icon.

A request message is sent and the previous message is kept in the message queue.

(Only when the error message is ”FP not exist”). a)

Modify data (it is only possible in the AFTN-FP Messages Correction Window).



Page A-22


ACTION


RESULT

b)

Click with the LB on the [UPDATE] icon (it is only possible in the AFTN-FP Messages Correction Window).

c)

Click with the LB on the [PRINT] icon (it is only possible in the AFTN-FP Messages Correction Window).

The AFTN message is printed.

2.1.1.4.2 AFTN-NOTAM Messages Correction Window When receiving an AFTN message, which type is “NOTAM”, either correct or incorrect, the system queues the message in the “Q” Queue. When clicking on the [SUMMARY] icon, the FP Messages Window is displayed to filter the messages by type: FP, NOTAM, TACT (tactical), COORD (coordination) and UNKNOWN being selectable one or more filters (see point 2.1.1.4) Clicking twice on one of the entries, if the message of the queue is NOTAM type, AFTN NOTAM Messages Correction Window is displayed including the whole message text and the fields of the Flight Plan, which generates it.

Figure 2-7:

AFTN-NOTAM Messages Correction Window

This window is composed of the following areas: Window Title It changes depending on the type of AFTN-NOTAM message. Message Text Area It contains the AFTN message text of NOTAM type displayed on the screen. By clicking on the [PRINT] icon, the message text printing is performed. Edition Area Flight Data Display User Manual


Page A-23



It is composed by a set of fields where the system displays the data extracted from the AFTN-NOTAM text message. The system indicates the erroneous fields for operator modification. Only WHITE and RED fields (compulsory and erroneous fields) are accessible to the operator. Error Message Area It is where the system displays any error message to warn the operator of the erroneous fields. Command Area It is composed by a set of icons that are described in following table: Table 2-5:

AFTN-NOTAM Messages Correction Window. Command Area

Icon

Description

PREV

Force the display of the previous AFTN message. If there is no previous message, the window is closed.

NEXT

Force the display of the next AFTN message. If there is no next message, the window is closed.

DELETE

Delete the current displayed message. The AFTN message counter is decreased one unit (1).

UPDATE

Trigger the modification process performed on the message, if any, and process the message, if it is correct.

CANCEL

Close the window and cancel any modification, if it was not previously triggered.

2.1.2 “AAI” Queue: Erroneous AFTN Header Area (EAH) It is composed of following elements: “AAI” Queue Identifier and “AAI” AFTN Messages Counter with erroneous header and the service (SVC) message, which are not of repetition [SUMMARY] icon to access the messages. Select this icon to display a new window, with all queued messages.

Figure 2-8:

“AAI” Queue

Prior to the processing of the message text, the FDP validates all data contained in the AFTN message header: Addresses Filing time Originator indicator Circuit Id Sequence number Transmission time Priority If any one of the message header fields is erroneous, the message is sent to the “AAI” Queue for manual correction at the FDD. Flight Data Display User Manual


Page A-24



The received message sequence number is compared with the expected one, and if a discontinuity is found, the System automatically generates a service message to request the repetition of the lost messages, or to warn the issuing office of the error, depending on the type and extent of the discontinuity. Apart from allowing to manually handling the correction of erroneous headers, the FDD provides the capacity to handle: Repetition of transmitted messages; Request of repetition of incoming messages; Consult recorded AFTN messages; Manually modify the expected sequence numbers (for incoming and outgoing messages); Modify status of the lines.

Figure 2-9:


“AAI” Queue


Page A-25



2.1.2.1 “AAI” Messages De-queue The “AAI” Queue attends the messages that have some error in the header and service messages (SVC) other than "repetition". The window allows displaying a limited number of messages but when the number of messages exceeds the window size, a scroll bar is displayed to allow vertical or horizontal movement to visualize those messages not in view. The queue operates on a FIFO basis (first in, first out). Whenever the received message Sorting Number (number of sequence) is less than the expected one, or bigger than ten units, the message is queued in the “AAI” Queue. Then, a message indicating this event is automatically sent (the Sorting Number of the next sending message is increased in one unit). In case the difference between the received Sorting Number and the expected one is less or equal than 10, then the message is processed. That is, it is not queued in the “AAI” Queue and a message indicating this event is sent (the Sorting Number of the next sending message is increased in one unit). When clicking on the [SUMMARY] icon, a set of messages (up to ten) is displayed on a window. If user clicks twice on one of these entries and the message has any error in the header, it is displayed on the “AAI” Messages Correction Window. The messages counter does not change the number until the message is processed or deleted. The message selected in the queue by an FDD operator cannot be accessed by any other FDD. When an AFTN message is received and its header has any error, these three windows are displayed: “AAI” Messages Window “AAI” Error Window “AAI” Messages Correction Window

2.1.2.1.1 “AAI” Messages Window When receiving an erroneous message or it is a SVC message (but not “repetition”), it is queued on the “AAI” Queue. The messages sent to the “AAI” Queue are displayed in the messages window. Up to 30 messages are displayed. The user can visualize any of them with double-click on the message. There are two possible actions: [Refresh]: Display the new messages that are going to enter in “AAI” Queue. [Close]: Close the window.



Page A-26


Figure 2-10:


“AAI” Messages Window

2.1.2.1.2 “AAI” Error Window The “AAI” Error Window displays the error message to warn the operator about the erroneous fields.

Figure 2-11:

“AAI” Error Window

2.1.2.1.3 “AAI” Messages Correction Window The “AAI” Messages Correction Window displays the data message within their corresponding fields when double-clicking on any entry of the messages window.



Page A-27


Figure 2-12:


“AAI” Messages Correction Window

This window has the following areas: Edition Area: It is composed of a set of fields where the system displays the AFTN message header data. The system indicates the erroneous fields for modification. Only fields in WHITE and RED (compulsory or erroneous) are accessible for operator control. Message Text Area: This area presents the AFTN message text whose header contains any error. The text cannot be modified. By clicking on the [PRINT] icon, the message printing is performed. Command Area: This area consists of a set of icons, which are described in following figure: Table 2-6: Icon

“AAI” Messages Correction Window. Command Area Description

PREV

Force the display of the previous AFTN message whose header is erroneous. If there is no previous message, the window is closed.

NEXT

Force the display of the next AFTN message whose header is erroneous. If there is no message, the window is closed.

DELETE

Delete the current message in the window. The “AAI” Message Counter decreases by one (1).

UPDATE

Trigger the modification action performed in the message.

EXIT

Close the window and cancel the modification process, if it was not previously validated ([UPDATE]).

When clicking on the [UPDATE] icon, one of the following situations is initiated:



Page A-28



If the message is a FPL and its content is correct, it will be processed but, if it is not correct, it will go to the FPs (“Q”) queue, explained in point 2.2.1. If the message is not a FPL and it is not corrected, the message will remain in the queue with another special window (“AAI” Window) where the message only can be printed or deleted. If the message is an SVC of repetition (RPT) and it is corrected, it will be processed. There are two messages of repetition processed by the FDP: Message repetition request with Circuit Id and a Sorting Number or a Sorting Number range: SVC QTA RPT xxxn-m where, xxx is the Circuit Id, n is the message Sorting Number to be repeated, or lower Sorting Number of the range of messages to be repeated. m is the Sorting Number or the range of messages to be repeated. If only a message is going to be repeated, it is not necessary. Message repetition query with Filling Day Time and Originator: SVC QTA RPT ddhhmm address, where ddhhmm is the Filling Day Time, and address is the Originator In both cases the header will display: Destination: value defined in adaptation. Originator: value defined in adaptation.



Page A-29



2.1.2.1.4 “AAI” Window The “AAI” Window displays all the SVC messages other than “repetition” and the messages which are not FPL and whose header is not corrected in the “AAI” Messages Correction Window. This window consists of the following areas:

Message Text Area

Command Area

Figure 2-13:

“AAI” Window

Message Text Area This area displays the SVC AFTN message of repetition (RPT) whose header has some error or the SVC AFTN message, which are not of repetition. The text cannot be modified. By clicking on the [PRINT] icon, the message printing is performed. Command Area: This area consists of a set of icons, which are described, in following table: Table 2-7: Icon

“AAI” Window. Command Area Description

PREV

Force the display of the previous message in the “AAI” Queue. If there is no previous message, the window is closed.

NEXT

Force the display of the next message in the “AAI” Queue. If there is no following message, the window is closed.

DELETE

Delete the current message in the window. The “AAI” Queue Messages Counter decreases by one.

CANCEL

Close the windows and cancel the modification process, if it was not previously validated.

PRINT

Print the current message.



Page A-30


2.1.2.1.4.1 ACTION 5. Click


Action: AFTN Messages De-queue (Erroneous AFTN Message Header) RESULT

GI_A.

The “AAI” Messages Window is displayed. The user may update the messages coming into the queue or cancel the action, by closing the window.

6.

Click twice on any message entry to visualize or correct it.

The System displays the “AAI” Error Window and the “AAI” Messages Correction Window.

7.

Click with the LB on the [PREV] o [NEXT] icons.

The previous or next AFTN message in the queue is displayed. The previously displayed message is stored again in the queue.

8.

Once the message is selected, following actions can be performed: 8.1.

with the LB on the [SUMMARY] icon, situated in the

Click with the LB on the [DELETE] icon A confirmation menu is displayed.

8.1.1. 8.2.

Click in [YES ] icon

The displayed AFTN message is deleted from the queue (counter decreases in one unit).

Modify data (it is only possible in the “AAI” Messages Correction Window).



Page A-31



ACTION 8.3.

RESULT Click with the LB on the [UPDATE] icon (it is only possible in the “AAI” Messages Correctio n Window).

The validation process is triggered. If the message is a FPL and its content is correct, it will be processed but, if it is not correct, it will go to the FPs (“Q”) queue. If the message is an SVC of repetition (RPT) and it is corrected, it will be processed. In both cases, the counter decreases one unit. If the message is not a FPL and it is not corrected, the message will remain in the queue with another special window (“AAI” Window) where the message only can be printed [PRINT] or deleted [DELETE].

The [PREV] and [NEXT] icons display the previous and next message within the “AAI” Queue.. 8.4.

Click with the LB on the [PRINT] icon (it is only possible in the “AAI” Messages Correction Window and “AAI” Window).

The AFTN message is printed.

8.5.

Click with the LB on the [EXIT] icon (it is only possible in “AAI” Window).

The “AAI” Window and the “AAI” Messages Correction Window are closed.

2.1.3 FDP Failure When no FDP is available, a warning window will be displayed in FDD to warn about the failure.



Page A-32



Figure 2-14: FDP down



Page A-33


2.2


FDD Main Menu Area (MM_A)

The Main Menu Area is located at the bottom of the FDD Position screen. It is composed of icons that perform different functions. The general layout of this window is shown in following figure:

Figure 2-15:

Figure 2-16:

Main Menu Area (MM_A) Without EFS

Main Menu Area (MM_A) With EFS

The icons, included in the MM_A, are described in following figure. Table 2-8:

FDD Main Menu Area. Commands Icon Row

Icon

Description

FP Act.

Display the FP Operation Window (action mode) to view, create, modify, cancel, etc., a FP.

FP Rtr.

Display the FP Retrieval Window to allow the retrieval of the specified FP(s).

FP Min.

Display the Minimal FP Window to create a minimal FP.

Hist Rtr.

Displays the “Historical Retrieve” Window.

RPL Act.

Display the RPL Operation Window to view, modify, cancel, etc. a RPL.

RPL Rtr.

Display the RPL‟s Retrieval Window to allow the retrieval of the specified RPL(s).

Runw

Display the Airport Runways Window.

AFTN TX

Display a menu to select the AFTN messages type (ICAO, FREE text or of Service) to be edited.

ARCHIVE

Display the AFTN Retrieve Window that includes the sent and received messages that match the operator searching criteria.

A.P.

Display the Airport Pressure Window.

WINDS

Display the Winds Data Window to view and/or modify the wind data.

AREAS

Display the Restricted Areas Window to perform several actions (view, creation, modification, etc) on restricted areas.

FLOW

Display a menu to choose the traffic type to be analyzed.

METEO

Display the Meteorological Information Window to obtain, by previous meteorological message selection, the corresponding information.

NOTAM

Display the NOTAM Operation/Retrieval Window.

T.Flow

Display a menu to select the different traffic flow options.

LINES

Display the window that visualizes the status, SIN, SON, of the AFTN lines. It also allows access to the modification window of those parameters.

INFO

Display the window that visualizes the application help.

EST

Display the window to perform a quick Estimate operation without accessing the FP template.

FREETEXT

Display the window that allow the free text messages input in any of its three channels.

CLOCK

Display the clock window, that contains system time and date (non-available in FDD associated to an SDD position).

EFS

Display the Electronic Flight Strips windows (only available in off-line configurated FDD positions) An EFS User Manual is provided with a complete explanation of this functionality.



Page A-34



LOGOUT

Lock the position and display the Log-In Window (non-available in FDD associated to an SDD position)

PRINTER

Display the window that allow selection among available printers.

2.2.1 Icon [FP Act.] Actions on Flight Plans This icon triggers all procedures related to FP actions. By clicking on the [FP Act.] icon, the FP Operation Window is displayed.

Figure 2-17:

[FP Act.] Icon

2.2.1.1 FP Operation Window The FP Operation Window 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.

Figure 2-18:

FP Operation Window

2.2.1.1.1 Flight Plan Status Depending on the actions performed on the Flight Plan and the System current time, the Flight Plan can follow these statuses: Initial It‟s 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



Page A-35



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.

2.2.1.1.2 Edition Area Previous figure showed the fields included in the FP Operation Window. On top of each field, there is a small title to identify it. Following table describes every field and its corresponding associated information. As it was previously mentioned, editable fields (in white) depend on the selected command. Table 2-9: Field

FP Operation Window. Edition Area

Description

Valid Data

Flight ID

Aircraft Identification or ACID

2 to 7 alphanumeric characters

Radio Callsign

Phonetic Airline Operator

Up to 20 characteres. Non-editable field. Defined in DBM.

NO

Number of Aircrafts

Up to 2 numerical characters (1-99)

A/C TYPE

Type of Aircraft

2 to 4 alphanumeric characters. The first one shall be an alphabetic character. It shall be known by the system.

W

DEP

Type of wake turbulence

Departure Aerodrome

L=

light

M=

medium

H=

heavy

J=

super-heavy

Four alphabetic characters. If unknown, then enter the “ZZZZ” keyword. If created while aircraft is airborne, then enter the “AFIL” keyword.

DEST Flight Data Display User Manual

Destination Aerodrome

Four alphabetic characters.


Page A-36



NAV/ COM

RVSM

Navigational/ Communications Equipment

RVSM Capability Status

Up to 20 alphabetical characters N=

Non-equipped

S=

Equipped

A=

LORAN A

C=

LORAN C

D=

DME

E=

Decca

H=

HF RTF

I=

Inertial Navigation

L=

ILS

M=

Omega

O=

VOR

P=

Doppler

R=

RNAV

T=

TACAN

U=

UHF RTF

V=

VHF RTF

W=

RVSM

Y=

Frequency 8.33 Mz

EQ = equipped NO = non-equipped (for civil flights) UN = unknown EX = exempted (for military flights)

SSR Equipment. SURVEILLANCE 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)



Page A-37



I=> Mode C (Transponder can send aircraft identification transmission but it cannot send pressure altitude transmission) 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=

IFR

V=

VFR

Y=

IFR followed by VFR

Z=

VFR followed by IFR

Blank = I FT

Flight Type

S=

scheduled

N=

non-scheduled

G=

general aviation

M=

military

X=

other

Blank = other SID

Standard Instrumental Departure Procedure

Alphanumeric characters (2 to 7). Must be a known SID.

FIR ROUTE

FP route

Up to 480 characters. See following NOTE Validation Rules”.

“Route

Field

STAR

Standard Terminal Route Procedure

EOBD

Estimated Off-Block Date

YYMMDD (00 to 99 and 01 to 12 and 01 to 31) date of departure.

EOBT

Estimated Off-Block Time

HHMM (00 to 23 and 00 to 59)

MSG

Last AFTN Message

AFTN message; e.g.: FPL, DLA, CHG,…

CTOT

Arrival

on

Received

Alphanumeric characters (2 to 7). Must be a known STAR.

If the FPL only has the first AFTN message(the FPL message), on the field appear “FPL”

Calculated Take-Off Time

HHMM (00 to 23 and 00 to 59) Updated with message.

ATFMC


Last CFMU Message

Received

the

last

received

CFMU

Type of the last received CFMU message; e.g.: SAM, SRM, SLC, FLS, DES,…


Page A-38



ATD

Actual Time of Departure

HHMM (00 to 23 and 00 to 59)

EET/ ETA

Estimated Elapsed Time

HHMM (00 to 23 and 00 to 59)

Estimated Time of Arrival 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 Fix Point

Up to five alphabetic characters. It shall be known by the system.

ESTIMATE TIME

Estimated time significant point

ESTIMATE LEVEL

Cleared Flight Level

Pos SPEED

over

Report Speed

a

HHMM (00 to 23 and 00 to 59) 3 digits (hundreds of feet) Indicated Speed on the Position Report

Pos Report FIX

Fixpoint

Next Fixpoint to overfly indicated on the Position Report

Pos Report ETO

Estimated Time Overfly

Indicated time to overfly the fixpoint on the Position Report

ALT AD(S)

Alternate Airports

9 alphanumeric characters: Airport(Space)Airport (Each airport 4 characters)

FIELD 18

Additional information

Defined Field from ICAO

FREE TEXT

Notes

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.



Page A-39



S

Strip

2 alphanumeric (number of the sector to print the strip, only applicable on the SDD position)

REG

Aircraft Register

8 alphanumeric characters

STS

Status


MODE S

Aircraft Identification

6 hexadecimals characters (0-9, A-F)

ORIGINAL ROUTE

Original Route from Field 15

Up to 480 characters.

2.2.1.1.2.1

Rules for Entering Data

GREY fields do not allow data input or modification. 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-19: FP Operation Window: Error Detection If maximum number of characters allowed in a field is filled in, the cursor goes to the first character position in next field. If there are different errors (compulsory, synthetic, etc.,) 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.

2.2.1.1.2.2

“Route” Field Validation Rules

Following requirements must be fulfilled when editing the “Route” field in the FP Operation Window. Elements are separated by a single space. Elements consists of more than (1) character but less than (30). More than (40) elements in the route are not allowed. Only digits cannot compose elements.



Page A-40



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 (*). 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 has been erroneously filled in, a new window is displayed over the FP Operation Window showing the following information: R: It is the route entered by the controller. Flight Data Display User Manual


Page A-41



C: It is the route calculated by the system. It marks the point where the error is found. S: It is a Standard Route. It is only displayed when there is a standard route defined in the DBM. For detailed information on the “Route” field, see Appendix B - .

2.2.1.1.3 Command Area Following table shows the different commands, which are included in the FP Operation Window. All the operations involving flight plan management are described in following sections. Table 2-10:

FP Operation Window (action mode). Command Area

Icon/Switch

Command

View

Display an existing FP data

Hist.

Display the history of a FP already created or received. The System presents a report containing the FP information plus all the actions performed on it with the date and time of all modifications and positions which performed the changes.

Create

Creation a FPL. The Flight Plan is stored once it is created in the System FPLs database and in “PENDING” or “NOTIFIED” status. This option allows creating a copy of an already existing FP whenever there are modifications in the main fields.

Create Current

Create a Current Flight Plan for an aircraft that is already flying. This action creates the FP in “ACTIVE” status.

Modify

Modify an existing FP. If modification is correct, the FP keeps the change permanently.

Term

Terminate an existing FP. The status changes to “TERMINATED”. Once the FP is cancelled, no modifications can be performed on it, except retrieval, view, history display or copy by means of the [Create] switch.

Notif

It allows changing a FP from “INITIAL” or “PENDING” to “NOTIFIED” (this status will be kept until it takes off). It is possible to assign an SSR code or the System will automatically assign one according to the ORCAM rules.

C.Notif

Cancel a previous Notification action. The FP returns to previous status (Initial or Pending), if the entered hour is earlier than the current one in a defined parameter.

ATD

Mark a flight as having taken off and it allows the controller to change or confirm the ATD time proposed by the System. The FP is in “ACTIVE” status.

C.ATD

Cancel a previous ATD action. The flight turns to the status previous to the Activation action: “NOTIFIED”, “PENDING” or “INITIAL”. This action is only possible if the ATD was previously activated.

EST

Perform the time estimate action on a reporting point of the flight plan route. The rest of the fields are calculated by the System.

POS

Send a position report including the last fixpoint overflown by the aircraft and the passing time, the next fixpoint and the estimated time.

AFTN SEND

Open a new window with the ICAO template. The corresponding fields to the FPL shall be fulfilled.

Strip

Print the Flight Plan strip. (only on SDD position)

UPDATE

Trigger the validation process of the current action performed on the selected window.

CANCEL

Close the selected window. If the actions performed were not validated previously ([UPDATE]), they will not be taken into account by the system.

CLEAR

Delete the data displayed on all the fields of the selected window.

PRINT

Print the historical information of a FP.

This point includes all the procedures to perform on the FP Operation Window. A common step to all actions is following described:



Page A-42


2.2.1.1.3.1


Action: Common Step to Actions on FPs

ACTION

RESULT

1.

The System displays the FP Operation Window with all fields empty. If the FP database contains Flight Plans, the [View] switch is automatically activated (YELLOW).

Click with the LB on the [FP Act.] icon, situated in the MM_A.

From this point on, the actions are described according to operations performed from the switches (commands). Each command has compulsory and accessible fields. The compulsory fields are always accessible.

2.2.1.1.3.2

Action: Visualize FPL

NOTE: This action is also used as a starting step to perform any FPL action available from the FP Operation Window. That is, when performing any action, it is necessary to display the corresponding FP in order to carry out the operational function.

ACTION 1.

Click on the [View] switch.

2.

Enter data on the corresponding fields to retrieve the FP.

3.

Finish the operation by performing a close action (see 1.8)

RESULT The switch changes to YELLOW.

Compulsory Fields: FLIGHT ID.

2.2.1.1.3.3

Action: View List of FP Synonyms

When two or more flight plans have the same Callsign and a [View] action is performed, the List of Synonyms Window is displayed over the FP Operation Window including the flight plans with the same Callsign. Clicking twice with the LB on one of the FPs of the list, the selected FP is displayed on the FP Operation Window. The displayed FP fields are the same as those displayed on the Retrieved Flight Plan(s) Window (see point 2.2.2.1.4) plus the field “FREE TEXT” of the FP.



Page A-43


Figure 2-20:

2.2.1.1.3.4


List of Synonyms Window

Action: FPL History ACTION

1.

Perform the FP View action (see 2.2.1.1.3.2)

2.

Click with the LB on the [Hist.] switch.

RESULT The switch becomes YELLOW, and the FP History Window is displayed including all actions performed in the FP. If the information is bigger than the window size, a scroll bar is displayed to allow visualization. This window allows resizing.

The FP Operation Window automatically changes to View mode ([View] switch activated) and all fields are inaccessible.

3.


Compulsory Fields: FLIGHT ID, only if the FP View action has not been previously performed.



Page A-44



2.2.1.1.3.5

Action: Create FPL ACTION

RESULT

1.

Click with the LB on the [CREATE] switch.

The switch changes to YELLOW.

2.

Enter data in the corresponding fields.

The System checks if entered data are correct. If they are correct, the new FP is stored in the Flight Plans database in “INITIAL” or “NOTIFIED” status. If they are incorrect, the System displays a message corresponding to the erroneous data.

3.


Compulsory Fields: FLIGHT ID, A/C TYPE, DEP, EOBT, CRUISING LEVEL, DEST and FIR ROUTE.

NOTE: It is also possible to create and FPL from an existing one. The action is speeded up.

2.2.1.1.3.6

Action: Create a Current FPL (CREATE CURRENT) ACTION

RESULT

1.

Click with LB on the [CPL Create] switch.

The YELLOW.

switch

changes

2.


The System checks if entered data are correct.

to

If they are correct, the new FP is stored in the Flight Plans database in “ACTIVE” status. If they are incorrect, the System displays a message corresponding to the erroneous data.

3.


Compulsory Fields: FLIGHT ID, A/C TYPE, DEP, EOBT, CRUISING LEVEL, DEST, FIR ROUTE, ESTIMATE FIX, ETO and CFL. NOTE: The difference between [Creat.] and [CPL] is that the second one is the same as [Crea.] + [ATD] or [Crea.] + [Est] as, apart from creating a FP, its status is “Active”. Moreover, [CPL] requires the “FIXPOINT”, “ETO” and “CFL” fields entered by means of the [Crea.] switch. A CPL can be created starting from an already existing FP to speed up the action.



Page A-45


2.2.1.1.3.7


Action: Modify FPL ACTION

RESULT

1.


2.

Click with the LB on the [MODIFY] switch.

The switch changes to YELLOW and the accessible fields for the action are displayed in WHITE background.

3.

Modify the desired fields. Some fields do not allow modification and some other are mandatory.

The System checks if entered data are correct. If they are correct, the new FP is stored with the last modifications. If they are incorrect, the System displays a message corresponding to the erroneous data.

4.


Compulsory Fields: FLIGHT ID, A/C TYPE, DEP, DEST, EOBT, CRUISING SPEED, ESTIMATE LEVEL and FIR ROUTE only if the visualization action has not been previously performed.

NOTE: It is only possible to modify already existing data. Deletion is not allowed.

2.2.1.1.3.8

Action: Cancel FPL ACTION

1.


2.

Click with the LB on the [TERM] switch.

3.



Compulsory Fields: FLIGHT ID and DEP only if the FP visualization action has not been previously performed. NOTE: If entered data were correct, the System changes the FP status to “TERMINATED”. All fields are inaccessible.



Page A-46


2.2.1.1.3.9


Action: FP Notification ACTION

RESULT

1.


2.

Click with the LB on the [NOTIF] switch.


3.

Enter data into the “CSSR” field, if needed. Click on [UPDATE] icon with the mouse LB.

The status changes to “Notified” and: If correct SSR Code, it is stored. If incorrect SSR Code, a SSR Code is assigned according to the ORCAM code. If no SSR Code, a SSR Code is automatically assigned.

4.


Compulsory Fields: None NOTE: This action is allowed once. For re-performing the action, the operator must perform a Cancel Notification [C.NOTIF] action. The Notification action is not allowed when an ATD action has been previously performed.

2.2.1.1.3.10 Action: FP Notification Cancel ACTION

RESULT

1.


2.

Click with the LB on the [C.NOTIF] switch.


3.

Click on the [UPDATE] icon

The FP status changes to “Initial” or “Pending”.

4.


NOTE: This action can be performed when a Notification action was previously performed.



Page A-47



2.2.1.1.3.11 Action: Confirm/Modify ATD ACTION

RESULT

1.


2.

Click with the LB on the [ATD] switch.

The switch becomes YELLOW. The accessible fields are WHITE background and a BLUE frame surrounds the “CSSR” field.

3.

Confirm or modify the data displayed on the “CSSR” field.

The FP status changes to “Active”.

4.


Compulsory Fields: FLIGHT ID and DEP only if the FP visualization action has not been previously performed. NOTE: This action allows one performing. To perform the action again, the controller must execute a previous cancel ATD action [C.ATD]. Once an ATD action is performed, it is not allowed to execute a Notification action.

2.2.1.1.3.12 Action: Cancel ATD ACTION

RESULT

1.


2.

Click with the LB on the [C. ATD] switch.


3.

Click with the LB on the [UPDATE] icon.

A previous ATD action triggers the ATD cancellation process. Otherwise, the System sends an error message. The FP status changes to the one it has before performing the ATD action: “Notified” to “Initial” or “Pending”. The FP Operation Window is displayed on view mode ([View] switch is activated). All fields are inaccessible.

4.


NOTE: This action can be performed only if a previous ATD action was executed.

2.2.1.1.3.13 Action: Estimate Actions ACTION 1.

RESULT




Page A-48


2.

Click with the LB on the [EST] switch.

3.

Enter the future fix point (“FixPoint” field) of the flight plan route, if not displayed, and confirm or modify the values for the “ETO” and “CFL” fields. The ETO field, although accessible, is not mandatory due to the system automatically calculation.

4.

Click with the LB on the [UPDATE] icon

5.



The switch becomes YELLOW. The accessible fields for the action are WHITE background and a BLUE frame surrounds the “ETO” field. The System displays on the “Fixpoint”, “ETO” and “CFL” fields the data calculated by the system for the next route point to be overflown.

The “ROUTE” field displays the estimate point followed by the characters “/H” + point reporting time.

Compulsory Fields: If the FP visualization action has not been previously performed, the “ESTIMATE FIX” and “ESTIMATE LEVEL” fields are mandatory.

2.2.1.1.3.14 Action: Passing over Fixpoint ACTION

RESULT

1.


2.

Click with the LB on the [POS] switch.

The switch changes to YELLOW and the accessible fields for the action are displayed in WHITE background.

3.

Enter the information concerning the last overflown fixpoint “FIXPOINT” and the time of that event “TIME” as well as the next route fixpoint “NEXT FIX” and the estimated time for the FP to overfly that fixpoint “ETO”. Click with the LB on the [UPDATE] icon.

To avoid receiving the PO alert in the track label, send the position report.

4.


Compulsory Fields: If the FP visualization action has not been previously performed, the “ESTIMATE FIX” and “ESTIMATE LEVEL” fields are mandatory.

2.2.1.1.3.15 Action: Confirm/Modify ATA ACTION


RESULT


Page A-49


1.


2.

Click with the LB on the [ATA] switch.

3.

Confirm or modify the estimated time of arrival in the “ETA” field.

4.



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.

Compulsory Fields: FLIGHT ID, DEP, ETD and ETA only if the FP visualization action has not been previously performed.

NOTE: It is impossible to perform the EST or ACT actions once the ATA action has been executed.

2.2.1.1.3.16 Action: Cancel ATA ACTION

RESULT

1.


2.

Click with the LB on the [C.ATA] switch.


3.

Click with the LB on the [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.

4.


Compulsory Fields: DEST, EOBT. Only if the visualization action has not been previously performed. NOTE: This action can be performed only if a previous ATA action was executed.

2.2.1.1.3.17 Action: AFTN SEND ACTION

RESULT

Perform the FP visualization action



Page A-50



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 to send the 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.



Page A-51



2.2.1.1.3.18 Action: FP Route Modification ACTION

RESULT

1. Click with the LB on the [FP Act.] icon.

The action displays the FP Operation Window.

2. Enter the data in the corresponding fields (“FLIGHT ID” is mandatory) to retrieve the desired FP. The switch becomes YELLOW, and the accessible fields for the action are WHITE background.

3. Click on the [Mod] switch. 4. Modify the “ROUTE” field to enter the desired route and click with the LB on the [UPDATE] icon. 5. Finish the action performing a close procedure (see 1.8)

2.2.1.1.4 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 ¡Error! No se encuentra el origen de la referencia..

2.2.1.1.5 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.

Figure 2-21:

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.1.1.6 Area Warnings Window This window is automatically displayed on top of the FP Operation Window. It allows warning the controller on the following cases: When the flight is about to cross a restricted area. When the flight has already crossed the restricted area.



Page A-52


Figure 2-22:


Area Warnings Window

Following table describes the information included in the Area Warnings Window: Table 2-11:

Area Warnings Window Field

Name of the restricted area. Entry fixpoint before the restricted area. If the flight is about to cross the restricted area, the displayed fixpoint is the first fix of the flight plan route within the restricted area. Fix point next to the restricted area.

2.2.2 Icon [FP Rtr.] Actions on Retrieved FP This icon triggers all procedures related to the FPs data retrieval for subsequent actions. When clicking on the [FP Rtr.] icon, the FP Retrieval Window is displayed.

Figure 2-23:

[FP Rtr.] Icon

2.2.2.1 FP Retrieval Window This window allows defining the filters to retrieve and display the FP data, which match the set of specific parameters entered by the operator. When the operator performs a query to the System on the FP Retrieval Window, the System displays the list of flight plans matching the specific parameters. The layout of these windows is shown in figure below:



Page A-53


Figure 2-24:


FP Retrieval Window

2.2.2.1.1 Edition Area Most of the fields are the same as for the FP Operation Window. Following table shows those fields, which are different including a description with their valid data. Table 2-12:

Field

FP Retrieval Window. Edition Area

Description

Valid Data

CALLSIGN

Aircraft identification


R

Flight Rules

1 character

N

Number of aircrafts

2 character

TYPE

Aircraft Type

4 character

NAV/COM

Equipment


SURVEILLANCE EQUIPMENT

Surveillance Equipment


DEP

Departure Aerodrome


ETD

Estimated Departure Time

HHMM (00 to 23 and 00 to 59)

SPEED

Speed

5 character

RFL


Flight Level

DEST



EET

Estimated Time

HHMM (00 to 23 and 00 to 59)

ROUTE

One or more fixes. If there is more than one, they are separated by the AND (+) or OR (|) operators

Name of fixes known by the system

FREE TEXT

Free text field

Alphanumeric characters

FROM

Time determining the start of a temporal filter for FPL retrieval.

DATE and HHMM (00 to 23 and 00 to 59)

UNTIL

Time determining the end of a temporal filter for FPL retrieval.

DATE and HHMM (00 to 23 and 00 to 59)



Page A-54



2.2.2.1.2 Command Area Following table shows the different commands included in the FP Retrieval Window. Table 2-13:

FP Retrieval Window. Command Area

Icon/Switch

Description

Status

Display only the FPs matching the entered status criteria. Allowed values are: Initial, Pending, Notificated, Active, Terminated, or All.

Summary Retrieve

Display the number of FPs matching the criteria (filters).

UPDATE

Trigger the actions performed in the current window.

CANCEL

Close the window. If actions were not previously validated ([UPDATE]), they will not be taken into account by the system.

CLEAR

Delete the data displayed on the fields of the window.

Pr All

Print all the Retrieved FP.

2.2.2.1.2.1

Action: Retrieve Multiple FPL ACTION

1.

Click with the LB on the [FP Rtr.] icon.

2.

To display the FPs:

3.

2.1.

If input parameters are known, enter the data in the corresponding fields and click on the [UPDATE] icon. It is not necessary to enter the whole string only first character is necessary.

The Retrieved Flight Plan(s) Window is displayed with the flight plan(s) matching the specific parameters.

2.2.

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: 3.1.

By clicking twice on the corresponding FP.

3.1.1.

3.2.

4.

RESULT The FP Retrieval Window is displayed.

The selected FP is displayed on the FP Operation Window (action mode). That is, the FP Retrieval Window is closed and the FP Operation Window (action mode) is displayed.

From this point on, all possible FP actions can be performed on the selected FP (see 2.2.1.1.3)

By clicking on the [Summary Retrieve] switch and then on the [UPDATE] icon.

An indication of the number of FPs that matches the selection criteria is displayed.


Compulsory Fields: None.




Page A-55



2.2.2.1.4 Retrieved Flight Plan(s) Window This window is displayed when clicking on the [UPDATE] icon of the FP Retrieval Window. The FPs not in view can be visualized by means of the vertical scroll bar available in the window right side.

Figure 2-25:

Retrieved FP Window. List Elements

Each line included in this window contains the following information: Callsign - R – FT - N - Type - DEP – EOBD - EOBT - Speed - RFL - Dest - ETA - CSSR Route – REG – STS - Status Table 2-14:

Retrieved Flight Plan(s) Window. List Element

Element

Description

Callsign

Aircraft Identifier

R

Flight Rules

FT

Flight Type

N

Number of Aircrafts

Type

Aircraft Type

DEP

Departure Aerodrome

EOBD


EOBT


Speed

Cruising Speed

RFL


Dest


ETA

Estimated Time of Arrival

CSSR

SSR Code

Route

FP Route

REG

Alternative aircraft identification

STS

Status

Status

FP Status

Counter

Window elements counter



Page A-56



2.2.3 Icon [FP MIN.] Minimal Flight Plan This icon triggers the creation of a Minimal FP.

Figure 2-26:

[FP Min.] Icon

2.2.3.1 Minimal FP Window This window allows a minimal Flight Plan creation. So the user does not have to fill out all the fields within the FP Operation Window to create a FP. It is an easy way to create a FP. When the operator click with the LB on the [FP Min.] icon, the next window is displayed:

Figure 2-27:

Minimal FP Window

2.2.3.1.1 Edition Area All the fields in this window are compulsory and have to be filled out. Table 2-15: Field

Minimal FP Window. Edition Area

Description

Valid Data

CALLSIGN



CSSR

SSR code

4 digits

DEP

Departure Aerodrome


DEST



CFL


3 digits (hundreds of feet)

TYPE

Type of Aircraft

2 to 4 alphanumeric characters. The first one shall be an alphabetic character. It shall be known by the system.

WAKE

EQ

Type of wake turbulence

Equipment


L=

light

M=

medium

H=

heavy

J=

super-heavy

Up to two alphabetic characters.


Page A-57



W = RVSM equipped Y = 8.33 equipped

Rules for Entering Data 1. 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. 2. If maximum number of characters allowed in a field is filled in, the cursor automatically goes

to the first character position in next field. 3. If there are different errors (compulsory, syntactic, etc.,) when creation a minimal FP, the

message displayed in the error message area corresponds to the first field with error where the cursor is situated.

2.2.3.1.2 Command Area Following table shows the different commands included in the Minimal FP Window. Table 2-16:

Minimal FP Window. Command Area

Icon

Description

UPDATE

Create a FP with the minimum fields.

CANCEL

Close the window. If actions were not previously validated, they will not be taken into account by the system.

CLEAR


2.2.3.1.2.1

Action: Create a Minimal FP ACTION

RESULT

1.

Click with the LB on the [FP Min.] icon,

The Minimal FP Window is displayed.

2.

Fill out all the fields in the Minimal FP Window and click [UPDATE].

If data are correct, then the FP is created, else the error is displayed at the window and the action is not performed.

3.


Compulsory Fields: All.


2.2.4 Icon [RPL Act.] Actions on Repetitive Flight Plans This icon triggers all procedures related to RPL actions. When clicking on the [RPL Act.] icon, the RPL Operation Window is displayed.



Page A-58



Figure 2-28:

[RPL Act.] Icon

The RPLs can be loaded from any external device by copying them into the directory used for this purpose. If the FDD is associated to an SDD, this option can be not accessible. From the FDD, the RPLs can be created only manually into the template for that purpose. The tool to load RPLs from a file is called “p_load_rlps” and it has to be done from the FDP: p_load_rplsl 0 file_rpls Where file_rpls must include all rpls to be loaded in Eurocontrol standard format (Document IFPS User Manual). NOTE: The off-line RPL management facility is not available in the system. Nevertheless, the on-line functionality related to RPLs is allowed

2.2.5 [Hist Rtr.] Icon This icon triggers a template to retrieve historical flight plan data. When clicking on the [Hist Rtr.] icon, the “Hist Rtr.” Window is displayed.

Figure 2-29: “Hist Rtr.” Window Table 2.2.3.1-1: “Hist Rtr.” Window. Edition Area Description Valid Data

Field DATE

Date filter


CALLSIGN



DEP

Departure Aerodrome


EOBD



EOBT


HHMM (00 to 23 and 00 to 59)

DEST



2.2.5.1.1 Command Area Following table shows the different commands included in the “FP min” Window. The operational behaviour is described in Chapter 3. Table 2.2.3.1-2: “FP Min” Window. Command Area



Page A-59


Icon / Switch


Description

UPDATE

Create a FP with the minimum fields.

CANCEL

Close the window. If actions were not previously validated, they will not be taken into account by the system.

CLEAR

Delete the data displayed on the window fields

2.2.5.1.2 “Historical Retrieved Flight Plan(s)” Window This window is displayed when clicking on the [UPDATE] icon of the “Hist. Rtr.” Window.

Figure 2-30: “Hist Rtr.” Retrieved 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: CALLSIGN – DEP – EOBD – EOBT – DEST - Counter

Element

Table 2.2.3.1-3: “Hist Rtr.” Retrieved Window. List Element Description



Page A-60


CALLSIGN

Indicative

DEP

Departure Aerodrome

EOBD


EOBT


DEST


Counter

Window elements counter


2.2.5.1.3 “Historical Information” Window This window is displayed when double clicking an element in “Hist Rtr.” Retrieved Window. It includes the information for a retrieved historical flight plan.

Figure 2-31: Historical Information Window Table 2.2.3.1-4: Historical Information Window. Command Area Element Description Print

Prints retrieved information (included in this window)

2.2.5.2 Action: Historical Retrieve => {[Hist Rtr.]} Application: Performs an historical retrieve. ACTION

RESULT

Click on the [Hist Rtr.] switch, at the bottom of the FDD Main menu area. The historical retrieve window is displayed.

Enter values to filter results. Click in UPDATE button. The Historical Retrieve Results window is displayed, with the results that match the retrieved



Page A-61


ACTION


RESULT criteria.

LB double click in an Historical Retrieve Result entry. The Historical information for the selected flight plan is displayed.



Page A-62


ACTION


RESULT

Perform the finishing action by: [PRINT] Icon in Historical retrieve window. Historical retrieved data is printed in predefined printer. [CANCEL] Icon in Main Historical retrieve window. The Historical retrieve window is closed. [CLEAR] Icon in retrieve window.

Main

Historical Retrieve criteria are erased and template is displayed empty.

2.2.1 [FINDER] Icon This icon is used to retrieve the flight plan data that matches with input SSR code, and display them in Flight Plan Operation Window. Figure 2-32: [FINDER] Icon



Page A-63



2.2.1.1 “FINDER” Window “Finder” Window consist in a unique edit field to input the SSR Code value.

Figure 2-33: “FINDER” Window

2.2.1.1.1 Edition Area Table 2.2.1.1-1: “Finder” Window. Edition Area Description Valid Data

Field SSR

SSR Code

4 numerical characters (octal value)

2.2.1.1.2 Command Area Table 2.2.1.1-2: “FINDER” Window. Command Area Command

Icon / Switch UPDATE

Trigger all actions performed in current window.

CANCEL

Close the window. If the actions were not previously validated, they will not be taken into account by the system.

2.2.1.2 Action: Retrieve FP by SSR Code => {[FINDER]} Application Display the Flight Plan Operation Window that match a concrete SSR Code. ACTION RESULT Click on the [FINDER] switch in Main Menu Area. Finder Window is displayed.

Input a SSR Code and click in UPDATE Icon. If SSR Code match with a current existing one: The Flight Plan Operation Window is displayed, with flight plan data of requested SSR Code Flight Data Display User Manual


Page A-64



ACTION

RESULT flight.

If SSR Code does not match with a current existing one: A window is displayed with the message “No FP‟s for current filter” To perform a new flight plan retrieve click in [CLEAR] Icon in Finder window and restart the action. To finish the action, click in [X] icon in Finder window.

2.2.1.3 RPL Operation Window The RPL Operation Window 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.

Figure 2-34:

RPL Operation Window

2.2.1.3.1 Edition/Activation Area Following table shows for each field included in the "RPL Operation” Window, a description of those fields with their valid data.



Page A-65



Table 2-3: Field / Switch

RPL Operation Window. Edition/Activation Area Description

Valid Data

Callsign



R

Flight Rules

1 alphabetical character: I= IFR V=

VFR

Y=

IFR followed by VFR

Z=

VFR followed by IFR

Blank = I N

Number of Aircrafts

Up to 2 numeric characters (1-99)

TYPE

Type of Aircraft

2 to 4 alphanumeric characters The first one is an alphabetic character. It must be known by the system.

W

EQ

Wake Turbulence Category

Navigation Equipment

L= M=

light medium

H=

heavy

J=

super heavy

Up to 20 alphabetical characters: N=

Non equipped

S=

Equipped

A=

LORAN A

C=

LORAN C

D= E=

DME Decca

F=

ADF

H=

HF RTF

I=

Inertial navigation

L=

ILS

M=

Omega

O=

VOR

P=

Doppler

R= T=

RNAV TACAN

U=

UHF RTF

V=

VHF RTF

W=

RVSM

Y =

8.33 Mz Frequency

SURVEILLANCE EQUIPMENT

Surveillance Equipment

Up to 20 alphabetical characters:

DEP

Departure Aerodrome

Four alphabetic characters. If unknown, then the “ZZZZ” keyword. If created while aircraft is airborne, then the “AFIL” keyword.

ETD

Estimated Time of Departure/ Revised Estimated Time of Departure or Actual Time of Departure (depending on the FP status)

HHMM (00 to 23 and 00 to 59)

SPEED

Cruising Speed

Kxxxx: 4 numerical characters (Km/h) Nxxxx: 4 numerical characters (Knots) Mxxx: 3 numerical characters (Number of Mach)



Page A-66


Field / Switch


Description

RFL

Valid Data


Up to 5 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): Sxxxx where xxxx 0000 to 9999. Altitude (tents of meters): Mxxxx where xxxx 0000 to 9999.

DEST


Four alphabetic characters.

EET

Elapsed Estimated Time

HHMM (00 to 23 and 00 to 59)

ROUTE

FP Route

Up to 480 characters. See the NOTE on “Route Field Validation Rules” included in section 2.2.1.1.2.2.

FREE TEXT

Notes

VALID PERIOD FROM

Time defining the start of the validity period for the RPL.

YYMMDD (00 to 99, 01 to 12 and 01 to 31)

UNTIL

Time defining the end of the validity period for the RPL.

YYMMDD (00 to 99, 01 to 12 and 01 to 31)

Indicate the days of the week when the RPL is scheduled.

From Monday to Sunday

OPERATION DAYS MTWTFSS

2.2.1.3.2 Command Area Following table shows the different commands, which are included in the RPL Operation Window. Table 2-4:

RPL Operation Window. Command Area

Icon / Switch

Command

View

Display the RPL data.

Create

Create a new RPL.

Modify

Modify an RPL.

Cancel

Terminate an RPL.

UPDATE


CANCEL

Close the window. If the actions were not previously validated, ([UPDATE]) they will not be taken into account by the system.

CLEAR


Pr All

Print all the retrieved FP

2.2.1.3.2.1

Action: Common Steps in Actions on RPLs ACTION

1.

Click with the LB on the [RPL Act.] icon.


RESULT The system displays the RPL Operation Window in View mode ([View] switch activated) with all fields empty. If the RPL database contains flight plans, the [View] switch is automatically activated (YELLOW).


Page A-67



NOTE: According to 2.2.4, the “off-line” facility of RPL management is not available in the System. Nevertheless, the functionality “on-line” related to RPLs is allowed.

2.2.1.3.2.2

Action: Visualize RPL ACTION

1.

Click with the LB on the [View] switch.

2.

Enter the specific data in the corresponding fields to retrieve the RPL.

3.



Compulsory Fields: CALLSIGN. Accessible Fields: CALLSIGN, ORIG, ETD, DEST and VALIDITY PERIOD (FROM and UNTIL). Note: The visualization action is only possible if there are RPLs in the database. Otherwise, the “RPL Operation” error message area displays a system error message.

2.2.1.3.2.3

Action: Create RPL ACTION

1.

Click with the LB on the [Create] switch. NOTE: This action may start from a previous visualization action (see 2.2.1.3.2.2).

2.


Input data in the corresponding fields. The [Operation Days] switches are activated (YELLOW) when the window is displayed. To inhibit them, click, with the mouse LB, on the corresponding day of the week switch.

3.


Compulsory Fields: CALLSIGN, ORIG, VALIDITY PERIOD (FROM and UNTIL), and OPERATION DAYS (the days of the week are activated when the RPL Operation Window is displayed. To inhibit them, click on the corresponding day). The mandatory fields are displayed only if the visualization action was not previously performed. Accessible Fields: All of them.

2.2.1.3.2.4

Action: Modify RPL ACTION

1.

RESULT

Perform the Visualization action 2.2.1.3.2.2.



Page A-68



The switch becomes YELLOW and the accessible fields for the action are displayed in WHITE background.

2.

Click with the LB on the [Modify] switch.

3.

Modify the required fields. Some of them do not allow modifications and some others are mandatory.

4.


Compulsory Fields: CALLSIGN, ORIG, VALIDITY PERIOD (FROM and UNTIL), and OPERATION DAYS (the days of the week are activated when the RPL Operation Window is displayed. To inhibit them, click on the corresponding day). The mandatory fields are displayed only if the RPL visualization action was not previously performed. Accessible Fields: All of them, except: SOURCE and STATUS. NOTE: Only already existing data can be modified. Deletion is not allowed.

2.2.1.3.2.5

Action: Cancel RPL ACTION

RESULT

1.

Perform the Visualization action 2.2.1.3.2.2.

2.

Click with the LB on the [Cancel] switch, at the bottom of the "RPL Operation" window, with the LB.

3.


The switch becomes YELLOW and the accessible fields for the action are displayed in WHITE background.

Compulsory Fields: CALLSIGN, ORIG, VALIDITY PERIOD (FROM and UNTIL), and OPERATION DAYS (the days of the week are activated when the RPL Operation Window is displayed. To inhibit them, click on the corresponding day). The mandatory fields are displayed only if the RPL visualization action was not previously performed. Accessible Fields: All of them.


2.2.2 Icon [RPL Rtr.] Repetitive Flight Plans Retrieval This icon is related to all the RPL data retrieval procedures for subsequent actions. When clicking on the [RPL Rtr.] icon, the RPL‟s Retrieval Window is displayed.

Figure 2-35:

[RPL Rtr.] Icon

NOTE: If the FDD is associated to an SDD, this option could be not available.



Page A-69



2.2.2.1 RPLs Retrieval Window This window allows defining the filters for the RPLs retrieval and displaying those data matching the set of specific parameters entered by the operator. When the operator performs a query to the system in the RPLs Retrieval Window, the System displays a flight plan list matching the specific parameters. The layout of these windows is shown in figure below.

Figure 2-36:

RPLs Retrieval Windows

2.2.2.1.1 Edition/Activation Area Fields included in this area are near the same as for the RPL Operation Window (see section 2.2.1.3.1).

2.2.2.1.2 Command Area Following table shows the different commands, which are included in the RPLs Retrieval Window. Table 2-5:

RPLs Retrieval Window. Command Area

Icon/Switch

Description

Summary Retrieve

Not available

UPDATE

Trigger the actions performed in current window.

CANCEL


CLEAR


Pr All

Print all the retrieved FP.



Page A-70


2.2.2.1.2.1


Action: Retrieve Multiple RPLs ACTION

1.

Click with the LB on the [RPL Rtr.] icon.

2.

To display the RPLs:

3.

4.

RESULT The RPLs Retrieval Window is displayed.

2.1.

If input parameters are known, enter the data in the corresponding fields and click on the [UPDATE] icon.

The Retrieved RPLs Window is displayed with the RPLs matching the specific parameters.

2.2.

If input parameters are unknown, click on the [UPDATE] icon.

The Retrieved RPLs Window is displayed with all RPLs.

Once the Retrieved RPLs Window is displayed, it is possible to select one of the RPLs: 3.1.

Click twice on the corresponding RPL.

3.2.

From this point on, all possible RPLs actions can be performed on the selected RPL (see 2.2.1.3.2.1)

The selected RPL is displayed on the RPL Operation Window. That is, the RPLs Retrieval Window is closed and the RPL Operation Window is displayed instead of.






Page A-71



2.2.2.2 Retrieved RPLs Window This window is displayed when clicking on the [UPDATE] icon of the RPLs Retrieval Window. The RPLs not in view can be visualized by means of a vertical scroll bar available at the window right side. Each row within the Retrieved RPLs Window contains the following information: Table 2-6:

Retrieved RPLs Window. List Element

Element

Description

Callsign


R

Flight Rules

N

Number of Aircrafts

Type

Aircraft Type

DEP


ETD

Estimated Time of Departure

Speed

Cruising Speed

RFL


Dest


EET


Route

FP Route

Valid Period (From-Until)

Start and end time for the RPL

Operat. Days (MTWTFSS)

Days of the week

2.2.3 Icon [Runw] Airport Runways Actions This icon allows performing actions on the airport runways. When clicking on the [Runw] icon, the Airport Runways Window is displayed.

Figure 2-37:

[Runw] Icon

2.2.3.1 Airport Runways Window This window is used to modify and visualize the current runway configuration of a selected airport. Each runway can be configured as departure and/or arrival runway.



Page A-72


Figure 2-38:


Airport Runways Window

2.2.3.1.1 Edition Area Following table describes the fields included in the Airport Runways Window: Table 2-7:

Airport Runways Window. Edition Area

Field

Description

AIRPORT

The desired airport name whose runways are to be viewed and/or modify.

Runways

Runway Identification.

Dep / Arr (switches)

Configure the runway use (arrivals, departures or both)

2.2.3.1.2 Command Area Following table explains the commands included in the Airport Runways Window: Table 2-8:

Airport Runways Window. Command Area

Icon/Switch

Command

View

Display of the runways configuration for the selected airport.

Modify

Perform modifications over an airport runway.

UPDATE


CANCEL

Close the window. If the actions were not previously validated, they will not be taken into account.

CLEAR


2.2.3.1.2.1

Action: Visualization of Airport Runways ACTION

RESULT

1.

Click with the LB on the [RUNW] icon.

The Airport Runways Window is displayed.

2.

Enter the corresponding airport (“Airport” field) and click on the [View] switch.

The switch changes to YELLOW and the data are displayed on their corresponding fields.



Page A-73


3.



Compulsory Fields: AIRPORT.

2.2.3.1.2.2

Action: Modify Airport Runways ACTION

RESULT

1.

Perform the visualization action.

2.

Click with the LB on the [Modify] switch.

3.

Modify the required runways.

4.



Compulsory Fields: AIRPORT.

2.2.3.1.3 Error Message Area It displays the error associated to the field. A list of error messages is provided in ¡Error! No se encuentra el origen de la referencia..

2.2.4 Icon [AFTN TX] AFTN Transmission The [AFTN TX] icon allows the operator to edit and transmit AFTN messages. When clicking on this icon, a menu is displayed to select the type of AFTN message. There are three options included in the menu as shown in following figure:

Figure 2-39:

[AFTN TX] Icon

2.2.4.1 ICAO AFTN Transmission Window When selecting from the menu of the [AFTN TX] icon the (ICAO AFTN) option, the ICAO AFTN Transmission Window is displayed. The layout of this window is shown if figure below:



Page A-74


Figure 2-40:


ICAO AFTN Transmission Window

2.2.4.1.1 Edition Area Following table lists, for each field included in the ICAO AFTN Transmission Window, a description with the valid data. Table 2-9: Field

ICAO AFTN Transmission Window. Edition Area Description

Valid Data

Priority

AFTN priority indicator

Follow ICAO rules

Addresses

Transmission Addresses

Up to 22 AFTN addresses separated by blanks. Each AFTN address must be a sequence of 8 letters

Filling Time

Time when the flight plan was filed out at the Flight Service Office. The filing time is extracted from all AFTN messages.

DDHHMM (00 to 31, 00 to 23 and 00 to 59)

Originator Indicator

A sequence of 8 letters. If not filled in, the Local Address defined in adaptation will be automatically entered.

Originator


The time is a future time. If the field is not filled in, the current time (DDHHMM) will be automatically filled in.


Page A-75



Field Message Type

Description Type of message

Valid Data FPL: Filed Flight Plan DEP: Departure CNL: Cancellation DLA: Delay EST: Estimation ARR: Arrival RQP: Request Flight Plan ALR: Alarm RCF: Radio Communication Failure RQS: Flight Plan Application AFP: Flight Plan Proposal SPL: Supplementary Flight Plan CPL: Current Flight Plan CHG: Change


Aircraft Identification (ACID or Callsign)

Alphanumeric characters (1 to 7).

SSR Mode

SSR Mode

1 character. Although the system does not perform a check of the data included in this field, the correct values are: A C S

SSR Code

ICAO SSR Code

4 octal digits Left blank = it allows FDP to automatically assign an SSR Code.

Flight Rules

Flight Rules

I=

IFR

V=

VFR

Y=

IFR followed by VFR

Z=

VFR followed by IFR

Left Blank = I Type Flight

Aircraft Type

S= N=

scheduled non-scheduled

G=

general aviation

M=

military

X=

other

Left blank = general aviation Number

Number of Aircrafts


Aircraft Type

Aircraft Type

2 o 4 alphanumeric characters. The first character must be alphabetic. It must be known by the System.

Wake Turb. Cat



L= M=

light medium

H=

heavy

J=

super heavy


Page A-76



Field Equipment

Description

Valid Data

Navigation/Communication Equipment

Up to 20 alphabetical characters: N = Not equipped; S = Equipped; A = LORAN A; C = LORAN C; D = DME; E = Decca; F = ADF; H = HF RTF; I = Inertial Navigation; L = ILS; M = Omega; O = VOR; P = Doppler; R = RNAV; T = TACAN; U = UHF RTF; V = VHF RTF The N or S characters can be only in the first place. If N is the first, no more characters can follow it.

Field

Surveillance Equipment.

Up to 20 alphabetical character: First character: SSR Equipment: N=> None. equipment).

(The

aircraft do

not carry

transponder

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 transmissio n 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) S=> Mode S (Transponder can send both aircraft identification and pressure altitude transmission) Blank = C Second character: ADS Equipment: D=> ADS capability Departure Aerodrome

Aerodrome of departure

4 alphabetic characters. If unknown, then the “ZZZZ” Word. If created while aircraft is airborne, then the “AFIL” Word.

EOBT

EOBT (for aerodrome)

known

departure

HHMM (00 to 23 and 00 to 59)

Or Estimated or actual arrival time to the first route fix-point referenced in the flight plan. Reference Point

Point with an associated information for a FP.

Up to 11 alphanumeric characters. It must be known by the System. Possible entries: Fixpoint name; Geographic position (Lat Lon).



Page A-77


Field


Description

Valid Data

Time

Time at the reference point

HHMM (00 to 23 and 00 to 59)

Auth. Level

Cleared Level at the reference point.


Supl. Level

Supplementary Level at the reference point.

See format/valid data for the “Auth. Level” field.

Cross C.

Crossing Condition

A= Above B= Below

Cruising Speed

Cruise Speed

Knots: Nxxxx or xxx(x) Kilometres per hour: Kxxx(x) Mach number: Mxxx

Level

Cruise Level


Route

Flight Plan Route


Destination Aero.


4 alphabetic characters. If unknown ZZZZ.

Total EET

Total Estimated Elapsed (Estimated flight duration)

Altn Aerodrome

Alternative Aerodrome

Time

HHMM (00 to 23 and 00 to 59) ICAO aerodrome indicator. 4 alphabetic characters. If unknown ZZZZ.

2nd. Altn Aerodrome

Second Alternative Aerodrome

ICAO aerodrome indicator. 4 alphabetic characters. If unknown ZZZZ.



Page A-78



Field Other Information

Description

Valid Data

Statement of any other necessary information.

Up to 67 characters, digits, slashes “/”, dots “.” or blank spaces, with the appropriate abbreviation followed by a slash and the information to be recorded. EET/

Significant points or FIR boundary designators and EET over such points or FIR boundaries.

RIF/

The route details the revised destination aerodrome followed by the ICAO location indicator of the aerodrome (4 ICAO letters).

REG/

Aircraft registration, only if necessary and if different from the aircraft identification in the “Aircraft Identification” field.

SEL/

SELCAL code, prescribed by the appropriate ATS authority.

OPR/

Operator name, if it is not clear in the Identification” field.

STS/

Reason for special handling by ATS (e.g. hospital aircraft) Type(s) of aircraft, preceded, if necessary, by number of aircraft and if “ZZZZ” is used in the “Aircraft Type” field. Aircraft performance data, if so, prescribed by the appropriate ATS authority.

TYP/

PER/

“Aircraft

COM/ Significant data related to communication equipment as required by the appropriate ATS authority. NAV/

Significant data related to navigation equipment as required by the appropriate ATS authority.

DEP/

Departure aerodrome name, if ZZZZ is inserted in the “Departure Aerodrome” field, or the ICAO four-letter location indicator of the ATS unit from which supplementary flight plan data can be obtained, if AFIL is inserted in the “Departure Aerodrome” field.

DEST/

Destination aerodrome name, if ZZZZ is inserted in the “Destination Aero” field.

ALTN/ Alternate aerodrome name, if ZZZZ is inserted in the “Altn Aerodrome” field. RMK/

Any other note required by the appropriate ATS authority.

Emergency Description


Free Text

Supplementary information

Additional Information

Free Text

Alert Information

Alert Information

Free Text

Communication Information


Free Text

2.2.4.1.2 Command Area Following table describes commands included in the ICAO AFTN Transmission Window. Table 2-10:

ICAO AFTN Transmission Window. Command Area

Icon/Switch

Command

VIEW

Information visualization.

TRANS

Send the information.

AUTO SEND

Insert the message into the System.

UPDATE

Trigger the performed actions in the window.

CANCEL

Close the ICAO AFTN Transmission Window.



Page A-79



Icon/Switch CLEAR

Command Delete the information included in the ICAO AFTN Transmission Window.

2.2.4.1.2.1

Action: Edit/Transmit ICAO AFTN Messages ACTION

RESULT

1.

Select form the [AFTN TX] icon the (ICAO AFTN) option. Click on TRANS bi-state button.

2.

Fill in the fields. The mandatory fields depend on the type of message being edited.

3.

The data transmission depends on the addressee: 3.1.

To the ATC System which is generating the message– click on the [Auto Send] switch.

3.2.

To the addresses edited in the associated field – click on the [Trans] icon.

The ICAO AFTN Transmission Window is displayed.

In all cases, the ICAO AFTN message is transmitted when the data entered are correct. If the data entered are erroneous, an error message is displayed. If mandatory fields are not filled in, an error message is displayed.

4.


Compulsory Fields: It depends on the type of message.


2.2.4.2 ICAO ADEXP Transmission Window When selecting from the menu of the [AFTN TX] icon the (ICAO ADEXP) option, the ICAO ADEXP Transmission Window is displayed. The layout of this window is shown if figure below:



Page A-80


Figure 2-41:


ICAO ADEXP Transmission Window

2.2.4.2.1 Edition Area Following table lists, for each field included in the ICAO ADEXP Transmission Window, a description with the valid data. Table 2-11: Field

ICAO ADEXP Transmission Window. Edition Area Description

Valid Data

Priority

ADEXP priority indicator

Follow ICAO rules

Addresses


Up to 22 addresses separated by blanks. Each address must be a sequence of 8 letters

Filling Time

Time when the flight plan was filed out at the Flight Service Office. The filing time is extracted from all ADEXP messages.

DDHHMM (00 to 31, 00 to 23 and 00 to 59) The time is a future time. If the field is not filled in, the current time (DDHHMM) will be automatically filled in.

Originator





Page A-81



Field Message Type

Description Type of message

Valid Data IFPL: Filed Flight Plan IDEP: Departure ICNL: Cancellation IDLA: Delay IARR: Arrival IRQP: Request Flight Plan IRQS: Flight Plan Application IAPL: ATC Flight Plan IAFP: Flight Plan Proposal


Aircraft Identification (ACID or Callsign)

Alphanumeric characters (1 to 7).

SSR Mode

SSR Mode

1 character. Although the system does not perform a check of the data included in this field, the correct values are: A C S

SSR Code

ICAO SSR Code

4 octal digits Left blank = it allows FDP to automatically assign an SSR Code.

Flight Rules

Flight Rules

I=

IFR

V=

VFR

Y=

IFR followed by VFR

Z= VFR followed by IFR Left Blank = I Type Flight

Aircraft Type

S= N=

scheduled non-scheduled

G=

general aviation

M=

military

X=

other

Left blank = general aviation Number

Number of Aircrafts


Aircraft Type

Aircraft Type

2 o 4 alphanumeric characters. The first character must be alphabetic. It must be known by the System.

Wake Turb. Cat



L=

light

M=

medium

H=

heavy

J=

super heavy


Page A-82



Field Equipment

Description

Valid Data

Navigation/Communication Equipment

Up to 20 alphabetical characters: N = Not equipped; S = Equipped; A = LORAN A; C = LORAN C; D = DME; E = Decca; F = ADF; H = HF RTF; I = Inertial Navigation; L = ILS; M = Omega; O = VOR; P = Doppler; R = RNAV; T = TACAN; U = UHF RTF; V = VHF RTF The N or S characters can be only in the first place. If N is the first, no more characters can follow it.

Field

Surveillance Equipment.

Up to 20 alphabetical character: First character: SSR Equipment: N=> None. equipment).

(The

aircraft do

not carry

transponder

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 transmissio n 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) S=> Mode S (Transponder can send both aircraft identification and pressure altitude transmission) Blank = C Second character: ADS Equipment: D=> ADS capability Departure Aerodrome

Aerodrome of departure

4 alphabetic characters. If unknown, then the “ZZZZ” Word. If created while aircraft is airborne, then the “AFIL” Word.

EOBT

EOBT (for aerodrome)

known

departure

HHMM (00 to 23 and 00 to 59)

Or Estimated or actual arrival time to the first route fix-point referenced in the flight plan. Reference Point

Point with an associated information for a FP.

Up to 11 alphanumeric characters. It must be known by the System. Possible entries: Fixpoint name; Geographic position (Lat Lon).



Page A-83


Field


Description

Valid Data

Time

Time at the reference point

HHMM (00 to 23 and 00 to 59)

Auth. Level

Cleared Level at the reference point.


Supl. Level

Supplementary Level at the reference point.


Cross C.

Crossing Condition

A= Above B= Below

Cruising Speed

Cruising Speed

Knots: Nxxxx or xxx(x) Kilometres per hour: Kxxx(x) Mach number: Mxxx

Level

Planned level for the first step or the whole route to be flown.


Route

Flight Plan Route


Destination Aero.


4 alphabetic characters. If unknown ZZZZ.

Total EET

Total Estimated Elapsed (Estimated flight duration)

Altn Aerodrome

Alternative Aerodrome

Time

HHMM (00 to 23 and 00 to 59) ICAO aerodrome indicator. 4 alphabetic characters. If unknown ZZZZ.

2nd. Altn Aerodrome

Second Alternative Aerodrome

ICAO aerodrome indicator. 4 alphabetic characters. If unknown ZZZZ.



Page A-84



Field Other Information

Description

Valid Data

Statement of any other necessary information.

Up to 67 characters, digits, slashes “/”, dots “.” or blank spaces, with the appropriate abbreviation followed by a slash and the information to be recorded. EET/

Significant points or FIR boundary designators and EET over such points or FIR boundaries.

RIF/

The route details the revised destination aerodrome followed by the ICAO location indicator of the aerodrome (4 ICAO letters).

REG/

Aircraft registration, only if necessary and if different from the aircraft identification in the “Aircraft Identification” field.

SEL/

SELCAL code, prescribed by the appropriate ATS authority.

OPR/

Operator name, if it is not clear in the Identification” field.

STS/

Reason for special handling by ATS (e.g. hospital aircraft) Type(s) of aircraft, preceded, if necessary, by number of aircraft and if “ZZZZ” is used in the “Aircraft Type” field. Aircraft performance data, if so, prescribed by the appropriate ATS authority.

TYP/

PER/

“Aircraft

COM/ Significant data related to communication equipment as required by the appropriate ATS authority. NAV/

Significant data related to navigation equipment as required by the appropriate ATS authority.

DEP/

Departure aerodrome name, if ZZZZ is inserted in the “Departure Aerodrome” field, or the ICAO four-letter location indicator of the ATS unit from which supplementary flight plan data can be obtained, if AFIL is inserted in the “Departure Aerodrome” field.

DEST/

Destination aerodrome name, if ZZZZ is inserted in the “Destination Aero” field.

ALTN/ Alternate aerodrome name, if ZZZZ is inserted in the “Altn Aerodrome” field. RMK/

Any other note required by the appropriate ATS authority.



Free Text

Supplementary information

Additional Information

Free Text

Alert Information

Alert Information

Free Text



Free Text



Page A-85



2.2.4.2.2 Command Area Following table describes commands included in the ICAO ADEXP Transmission Window. Table 2-12:

ICAO AFTN Transmission Window. Command Area

Icon/Switch

Command

VIEW

Information visualization.

TRANS

Send the information.

AUTO SEND

Insert the message into the System.

UPDATE

Trigger the performed actions in the window.

CANCEL

Close the ICAO ADEXP Transmission Window.

CLEAR

Delete the information included in the ICAO ADEXP Transmission Window.

2.2.4.2.2.1

Action: Edit/Transmit ICAO ADEXP Messages ACTION

RESULT

1.

Select form the [AFTN TX] icon the (ICAO ADEXP) option.

2.

Fill in the fields. The mandatory fields depend on the type of message being edited.

3.

The data addressee:

transmission

depends

on

The ICAO ADEXP Transmission Window is displayed.

the

3.1.


3.2.

To the addresses edited in the associated field – click on the [Trans] icon.

In all cases, the ICAO ADEXP message is transmitted when the data entered are correct. If the data entered are erroneous, an error message is displayed.

If mandatory fields are not filled in, an error message is displayed.

4.


Compulsory Fields: It depends on the type of message.

2.2.4.2.3 Error Message Area It displays the error associated to the field where the mouse is focused on. Flight Data Display User Manual


Page A-86



A list of error messages is provided in ¡Error! No se encuentra el origen de la referencia..

2.2.4.3 Free AFTN Transmission Window When selecting from the [AFTN TX] menu the (FREE AFTN) option, the Free AFTN Transmission Window is displayed. The layout of this window is shown if figure below: Figure 2-42:

Free AFTN Transmission Window

2.2.4.3.1 Edition Area Following table lists for each field included in the Free AFTN Transmission Window a description with the valid data. Table 2-13: Field

Free AFTN Transmission Window. Edition Area

Description

Valid Data

Priority

AFTN priority indicator

Follow ICAO rules

Addresses


Up to 22 addresses separated by blank spaces. Each AFTN address must be a sequence of 8 characters.

Filling Time

Time when the flight plan was filled in at the Flight Service Office. The filling time is extracted from all AFTN messages.

DDHHMM (00 to 31, 00 to 23 and 00 to 59) The time will be a future time. If the field is not filled in, the current time (DDHHMM) will be automatically filled in.

Originator



Free Text

Any text

Text

2.2.4.3.2 Command Area Following table describes the commands included in the "FREE AFTN Transmission” Window. Table 2-14:

Free AFTN Transmission Window. Command Area

Icon/Switch

Command

AUTO SEND

Message self-sending. That is, the message is sent to the message originator.

PRINT

Not available.

TRANS

Send the AFTN message.

CANCEL

Close the Free AFTN Transmission Window.

CLEAR

Delete the information displayed in the Free AFTN Transmission Window.

2.2.4.3.2.1

Action: Edit/Transmit Text AFTN Messages

ACTION


RESULT


Page A-87



ACTION

RESULT

1.

Click on the [AFTN TX] icon and in the (FREE AFTN) option.

The Free AFTN Transmission Window is displayed.

2.

Enter data into the corresponding fields.

3.

The data transmission depends on the addressee: 3.1




Page A-88


ACTION 3.2


RESULT To the addresses edited in the associated field – click on the [Trans] icon.

In all cases, the ICAO AFTN message is transmitted when the data entered are correct. If the data entered are erroneous, an error message is displayed.

If mandatory fields are not filled in, an error message is displayed.

4.


Compulsory Fields: At least one of the three “Addresses” fields must be completed.


2.2.4.4 SVC Transmission Window When selecting from the [AFTN TX] icon the (SVC) option, the SVC Transmission Window is displayed. The SVC Transmission Window consists of an edition area including fields to be filled in by the operator and a command area at the bottom of the window. The layout of this window is shown if figure below:



Page A-89



Figure 2-43:

SVC Transmission Window

2.2.4.4.1 Edition Area Following table lists a description for each field included in the SVC Transmission Window. Table 2-15:

SVC Transmission Window. Edition Area

Field

Description

Line 1 / Line 2

AFTN line through which the messages are sent.

Sorting Number (Lower)

Editable field. Sequence number of the service AFTN message to transmit, or minimum sequence number of the group of messages to be transmitted (000-999).

Sorting Number (Higher)

Editable field. Maximum sequence number of the group of messages to transmit (000-999).

If the “Sorting Number (higher)” field is empty, only the message corresponding to the sequence number entered in the “Sorting Number (lower)” field will be sent. If both fields have data, the messages, whose sequence number is among the values entered in those fields, will be sent. The maximum message number that can be simultaneously transmitted is 10.

2.2.4.4.2 Command Area Following table lists the different commands included in the SVC Transmission Window. Table 2-16:

SVC Transmission Window. Command Area

Icon

Command

UPDATE

Send the selected service AFTN message or group of messages.

CANCEL

Close the SVC Transmission Window.

CLEAR

Delete the information displayed on the SVC Transmission Window.



Page A-90


2.2.4.4.2.1


Action: Transmit SVC Messages

ACTION

RESULT

1.

Click on the [AFTN TX] icon and select the (SVC) option.

The SVC Transmission Window is displayed.

2.

Select the AFTN line through which the message is going to be sent by clicking repeatedly in [Line 1/Line 2] until the icon label displays the one to be used.

3.

Enter the corresponding data into the fields.

4.

a)

If only a message is transmitted, only first number must be completed.

b)

If a group of message is going to be transmitted (maximum 10 messages), both numbers must be completed.


If all data are correct, the SVC AFTN message is always sent.

Compulsory Fields: First “number” of the AFTN message.



Page A-91



2.2.5 Icon [ARCHIVE] This icon allows retrieving all sent and received AFTN messages. When clicking on the [ARCHIVE] icon, a pop-up menu is displayed that allows to select between AFTN and OLDI Retrieve Window.

Figure 2-44:

[ARCHIVE] Icon

2.2.5.1 AFTN Retrieve 2.2.5.1.1 AFTN Retrieve Window This window allows defining filters to retrieve all sent and received AFTN messages and display those data messages matching the set of specific parameters entered by the operator. When the operator performs a query to the system in the AFTN Retrieve Window, the system displays the sent and received AFTN messages matching the specific parameters. The layout of these windows is shown in figure below:

Figure 2-45:


AFTN Retrieve Window


Page A-92


2.2.5.1.1.1


Edition Area

Following table lists the fields and their corresponding description: Table 2-17:

AFTN Retrieve Window. Edition Area

Field

Description

Date

Valid Data

Sending or reception date of the AFTN messages to be retrieved.

AAMMDD, where AA = year (00 to 99) MM = month (01 to 12) DD = day (01 to 31)

Circuit Indicator. Line through which the AFTN messages to be retrieved where sent or received.

Circuit Id

XXX.- Line 1 Sending XXX.- Line 2 Sending XXX.- Line 1 Reception XXX.- Line 2 Reception XXX: These values are defined in adaptation.

Tx Time Interval

AFTN message sending or reception time.

From

Temporal filter starting time for AFTN message retrieval.

HHMM (00 to 23 and 00 to 59)

To

Temporal filter final time for AFTN message retrieval.

HHMM (00 to 23 and 00 to 59)

Sort Number

Sequence number of the message(s) to be retrieved.

From

Sequence number filter starting number.

(000-999)

To

Sequence number filter starting number.

(000-999)

Prior

AFTN priority indicator.

Follow ICAO rules

Destination

Transmission Address

8 characters sequence

Originator



Free Search

Text

2.2.5.1.1.2

Command Area

Following table lists the different commands included in the AFTN Retrieve Window. Table 2-18:

AFTN Retrieve Window. Command Area

Icon

Description

UPDATE


CANCEL


CLEAR

Delete the data displayed on the window.



Page A-93



2.2.5.1.1.2.1 Action: Retrieve Multiple AFTN Messages ACTION 1.

Click with the LB on the [ARCHIVE] icon.

2.

To display the sent or received AFTN messages: 2.1.

If input parameters are known, enter the data in the corresponding fields and click on the [UPDATE] icon.

RESULT The AFTN Retrieve Window is displayed.

If data are erroneous, an error message is displayed.

If mandatory fields are not filled in, an error message is displayed. If data are correct, the Retrieve Multiple AFTN Window is displayed.

3.

Once the Retrieve Multiple AFTN Window is displayed, it is possible to select one of the messages from the window:



Page A-94


ACTION 3.1.

4.

By clicking message.

twice


RESULT on

the

corresponding

The selected message is automatically displayed on the AFTN Element Window.

Finish the action by clicking with the LB on any of the following icons: 4.1.

[TRANSMIT] icon

Transmit a previous sent out message, in such a way that the sending message is equal to the prior one but for the “Circuit Id” field that will be the one corresponding to the line through which the message is being sent now and the “Sort Number” field that will be the corresponding one. If a received message attempts to be transmitted (“Circuit ID” field = XXX {INU or IND}), the error message “Impossible Trans Received Msg” will be provoked.

4.2.

[RETRANSMIT] icon

Transmit a previous sent out message. The sending message is equal to the prior one but for the “Sort Number” field that will be the corresponding one and the “DUPE” key that will be added at the end of the message. If a received message attempts to be transmitted (“Circuit ID” field = XXX {INU or IND}), the error message “Impossible Trans Received Msg” will be provoked and if the line through which the message is attempted to be transmitted is not available, the error “ERROR: Line is offline” will be emitted.

4.3.

[PRINT] icon

Print the AFTN message.

4.4.

[CANCEL] icon

All windows are closed.

4.5.

[CLEAR] icon

All data included in AFTN Retrieve Window are deleted.

Compulsory Fields: Date, Channel ID.

2.2.5.1.1.3

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 ¡Error! No se encuentra el origen de la referencia..

2.2.5.1.2 Retrieve Multiple AFTN Window This window is displayed when clicking on the [UPDATE] icon of the AFTN Retrieve Window. It displays the sent or received AFTN messages matching the entered searching criteria. If there are not messages with the searching criteria it displays: “NO AFTNS FOR THESE FILTERS”. The Retrieve Multiple AFTN Window is displayed to complete the header fields.



Page A-95


Figure 2-46:


Retrieve Multiple AFTN Window

2.2.5.1.3 AFTN Element Window This window is displayed by clicking twice, with the mouse LB, on a selected message included in the Retrieve Multiple AFTN Window. The AFTN Element Window displays the data of the message within the corresponding fields. Figure 2-47:

AFTN Element Window

This window has the following areas:

2.2.5.1.3.1

Edition Area

It is composed of a set of fields where the system displays the AFTN message header data. The system highlights the erroneous fields for modification. Only fields in WHITE and RED (compulsory or erroneous) are accessible to the operator. Following table lists for each field included in the AFTN Element Window a description with the valid data. Table 2-19: Field Circuit Id

AFTN Element Window. Edition Area Description

Circuit Indicator. Line through which the AFTN messages to be retrieved where sent or received.

Valid Data XXX.- Line 1 Sending XXX.- Line 2 Sending XXX.- Line 1 Reception XXX.- Line 2 Reception XXX: These values are defined in adaptation.

Sort Number

Sequence number of the retrieved message.

(0000 – 9999)

Tx Day Time

AFTN message sending or reception time.

HHMM (00 to 23 and 00 to 59)

Prior

AFTN priority indicator.

Follow ICAO rules



Page A-96


Field


Description

Valid Data

Dest

Transmission Address.


Filling Day Time

Time when the AFTN message was filled in at the Flight Service Office.

DDHHMM (00 to 31, 00 to 23 and 00 to 59)

Originator

Originator Indicator.


Text

Text.

2.2.5.1.3.2

Error Message Area

It is where the system displays any error message to warn the operator of the erroneous fields.

2.2.5.1.3.3

Command Area

It is formed by a set of icons, which are described in following table: Table 2-20:

AFTN Element Window. Command Area

Icon TRANSMIT

Description Transmit a previously transmitted message. The sending message is the same as the one formerly sent except for: The “Circuit Id” field that will be the one corresponding to the line through which the message is sent. The “Sort Number” field that will be the corresponding one. If there is an attempt of transmitting a received message (“Circuit Id” field = XXX or YYY), the error “Impossible Trans Received Msg” will be generated.

RETRANSMIT

Transmit a previously transmitted message. The sending message is the same as the one formerly sent except for: The “Sort Number” field that will be the one corresponding and The “DUPE” key that will be added at the end of the message. If there is an attempt of transmitting a received message (“Circuit Id” field = XXX or YYY), the error “Impossible Trans Received Msg” will be generated. In addition, if the line, through which the retransmission is being attempted, is not available, the error “ERROR: Line is offline” will be generated.

CANCEL


PRINT

Print the message.

2.2.5.2 OLDI Retrieve This window is displayed by LB clicking in [ARCHIVE] -> [OLDI]. It is a filter by some fields for OLDI messages.

Figure 2-48: “OLDI Retrieve” Window Flight Data Display User Manual


Page A-97



This window has the following areas:

2.2.5.2.1 Edition Area It is composed of a set of fields that can be completed in order to filter OLDI messages by a pattern entered in one o some fields. Following table lists for each field included in the OLDI retrieve window. Table 2-21: OLDI Retrieve Window. Edition Area Field Description DATE

Sending/ reception messages data.

CTRL CENTER

External control center. Displays a pop-down menu with available values.

TX DAY TIME

OLDI message sending or reception time interval.

Valid Data

DDMMYY

FROM: HHMM (00 to 23 and 00 to 59) TO: HHMM (00 to 23 and 00 to 59)

FREE SEARCH

Entered data is a partner for filter by any part of the message.

2.2.5.2.2 Error Message Area It is where the system displays any error message to warn the operator of the erroneous fields.

2.2.5.2.3 Command Area It is formed by a set of icons, which are described in following table: Table 2-22: OLDI Element Window. Command Area Icon Description UPDATE

Apply the filtering and displays a retrieve of OLDI messages that fulfil it.

CANCEL


CLEAR

Erase all data entered in every window edition field.

2.2.6 Icon [A.P.] Airport Pressure This icon triggers the procedures related to QNH. By clicking on the [A.P.] icon, the Airport Pressure Window is displayed.

Figure 2-49:

[A.P.] Icon

2.2.6.1 Airport Pressure Window The Airport Pressure Window 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 A-98


Figure 2-50:


Airport Pressure Window

2.2.6.1.1 Element List Area This area presents a list with the different data by Zone (airports) and includes the QNH and the Transition Level. By clicking twice on any of the rows included in the list, the data will be displayed on their corresponding fields within the Edition Area.

2.2.6.1.2 Edition Area Only the “Zone” field is editable. Using the keyboard or clicking twice on the corresponding row of the Element List Area can fill in this field. Following table describes the different fields included in the Airport Pressure Window. Table 2-23: Field

Airport Pressure Window. Edition Area Description

Zone

Display the previously selected airport. Do not allow entering modifications.

QNH

Display and allow modifications on the QNH.

TRANS LEVEL

Display the Transition Level for the selected zone and allow modifications.

2.2.6.1.3 Command Area Following table describes the commands included in the window: Table 2-24: Icon/Switch View

Airport Pressure Window. Command Area Command

Display the QNH information of a selected zone (airport).



Page A-99



Modify

Modify the information related to the QNH.

UPDATE

Trigger the actions performed in the Airport Pressure Window.

CANCEL

Close the Airport Pressure Window. If the actions were not previously validated, they will not be taken into account by the System.

CLEAR

Delete the information displayed on the Airport Pressure Window.

2.2.6.1.3.1

Action: QNH and Transition Level Visualization ACTION

1.

Click with the LB on the [A.P.] icon.

2.

The visualization action can be performed by:

3.

2.1.

Entering the name of the required airport in the “Zone” field.

2.2.

Clicking twice on the corresponding line of the Element List Area.

RESULT The Airport Pressure Window is displayed.


Compulsory Fields: Zone



Page A-100


2.2.6.1.3.2


Action: Modify QNH and Transition level ACTION

RESULT The Airport Pressure Window is displayed.

1.

Click with the LB on the [A.P.] icon.

2.

Enter the name of the required airport in the “Zone” field.

3.


4.

Modify the desired data.

5.


The data presented on the upper list are displayed on the corresponding fields.

Compulsory Fields: Zone, QNH and Transition Level.


2.2.7 Icon [WINDS] Wind Data Winds data are used to calculate the flight profile trajectory. The current and foreseen wind speeds (if available) together with the direction values are stored for each defined area and level. The [WINDS] icon allows performing actions on winds. When clicking on this icon, the Winds Data Window is displayed.

Figure 2-51:


[WINDS] Icon


Page A-101



2.2.7.1 Winds Data Window For each of the adapted zones (rows) and each of the defined layers (columns), the operator may change the winds directions and speed. The wind/speed combinations are defined for eight different levels (layers).

Figure 2-52: Winds Data Window

2.2.7.1.1 Edition Area Following table lists fields included in the Winds Data Window and a description of those fields with their valid data. Table 2-25: Field

Winds Data Window. Edition Area Description

Valid Data

TO

Display the end of the validation period of the data presented on the window.

DD/HH:MM (00 to 31, 00 to 23 and 00 to 59)

Zone

Display the identification of geographic areas.

Defined by adaptation

Layer

Relevant levels defined for each geographic area.

Up to eight

Wind Direction

Winds direction in the associated area/level.

In degrees from true north

Speed

Speed of the wind in the associated area/level.

From 0 to 250 kilometres per hour.

Temperature

Temperature in the associated area/level.

From -99 to 099 degrees.

Rules for Entering Data: 1. 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.



Page A-102



Figure 2-53: “Winds Data” Window: Error Detection 2. If maximum number of characters allowed in a field is filled in, the cursor automatically goes

to the first character position in next field. 3. If there are different errors (compulsory, syntactic, etc.,) when editing data, the message

displayed in the error message area corresponds to the first field with error where the cursor is situated.

2.2.7.1.2 Command Area Following table describes the commands included in the Winds Data Window. Table 2-26:

Winds Data Window. Command Area

Icon/Switch

Description

View

Display the wind information.

Modify

Modify the wind information.

UPDATE


CANCEL

Close the window. If the actions were not previously validates, they will not be taken into account.

2.2.7.1.2.1

Action: Visualization of Wind Data ACTION

1.

Click with the LB on the [WINDS] icon.

2.



RESULT The Winds Data Window is displayed in view mode ([View] switch activated).


Page A-103


3.



2.2.7.1.2.2

Action: Modify Wind Data ACTION

RESULT

1.

Click with the LB on the [WINDS] icon.

The Winds Data Window is displayed in view mode ([View] switch activated).

2.

Click with the LB on the [Modify] switch with the mouse LB.

The switch turns to YELLOW.

3.

Modify the desired fields. If wind‟s direction is entered, it is compulsory to introduce the speed and vice versa.

4.


Compulsory Fields: If entering new wind direction, it is compulsory to enter the corresponding speed and vice versa.


2.2.8 Icon [AREAS] Restricted Areas Restricted Areas are elements, which are created on-line and have two associated characteristics: Geography: the operator may define up to 3 dimensional areas for the restricted airspace. Planning: the operator may provide a schedule for the restricted airspace activation or inhibition. The Restricted Areas can be created/modified/cancelled from the FDD. Up to 64 restricted areas can be created in the ATC working area. A Restricted Area can be a circle or a zone being defined in both cases the minimum and maximum area. To create a circle, it is necessary to establish the centre and radius. Flight Data Display User Manual


Page A-104



To create a polygon, it is necessary to include up to 25 points. In both cases, it is possible to establish geographical coordinates or fix points defined as input data. Defining the validity period, operation days and activation hours, may perform the Restricted Area planning. When the Restricted Area is activated, the FDP distributes the information throughout the whole System and displays a presentation and deletion message when the activation period ends. The FDP deletes the restricted Areas when the validation period expires. Within the restricted area it is possible to select/de-select the STCA detection. The Restricted Areas are displayed on the SDDs while they are activated and they are used to warn about the RAW (Restricted Area Intrusion Detection Warning) and APW (Area Proximity Warning) alerts which are performed from the FDP and SDP, respectively. The [AREAS] icon allows performing actions on restricted areas visualization, edition, modification and cancellation. When clicking on the icon, the Restricted Areas Window is displayed.

Figure 2-54:

[AREAS] Icon

2.2.8.1 Restricted Areas Window The Restricted Areas Window consists of a form that includes the following areas: Element List Area Description Area (of the restricted area) Activation/Validity Area (of the restricted area) Layout Area (of the restricted area) Command Area Error Message Area



Page A-105


Figure 2-55:


Restricted Areas Window

Each field has a small title for identification. Some of them are open fields for input data, some of them need to be previously activated, and some others are mandatory data for the action processing.

2.2.8.1.1 Element List Area This list contains all the existing restricted areas. The restricted areas are automatically included in the list once they have been created and they are automatically deleted when the validity period is over. The vertical scroll bar allows the visualization of the restricted areas not in view due to list size.



Page A-106


Figure 2-56:


Restricted Areas Window. Element List Area

Each row included in the list contains the following information: AREA ID - TYPE - ACTIVITY - STATUS - VALIDITY - CLASS The operator may select any of the existing restricted areas by clicking twice with the LB on the line (it turns to BLACK). Once it is selected, the data are displayed on the corresponding fields. The information displayed in a line is: Table 2-27:

Restricted Areas Window. Element List Area

Element

Description

AREA ID

Display the restricted area identification.

TYPE

Display the restricted area type.

ACTIVITY

Display the activity type description that is undergone in the restricted area.

STATUS

Display the restricted area status. It depends on the restricted area activation periods.

VALIDITY

Display the restricted area validity period.

CLASS

Display the class of the Restricted Area. It could be Active (A), Inactive (I), or Scheduled (S)

2.2.8.1.2 Description Area It is the area located under the restricted area list. It is where the description of a restricted area is displayed.

Figure 2-57:

Restricted Areas Window. Description Area

This area is composed of the following items: Table 2-28:

Restricted Areas Window. Description Area

Item/Switch

Description

TOTAL

Display the number of restricted areas.

AREA ID

Display the restricted area identification (view mode). Enter the restricted area name (creation/retrieval mode).

TYPE

Type of restricted area (dangerous, forbidden, etc.)

ACTIVITY

Description of the activity type that is performed in the restricted area (military operation, etc)

DESCRIPTION

Brief description of the restricted area.

CLASS

Describe the assigned class to the restricted area.



Page A-107



Item/Switch

Description

Stca Alert Display

Switch that allows activate/inhibit the STCA alert function within the restricted area.

2.2.8.1.3 Activation/Validity Area

Figure 2-58:

Restricted Areas Window. Activation/Validity Area

These fields are used to define the validity period and the activation times. The periods may be entered on a daily or weekly basis or by defining concrete dates ("From" and "Until" fields). Table 2-29: Field/Switch

Description

Valid Data

Switch. When it is activated (YELLOW) the “From” and “Until” fields are accessible. It marks the relation with the validity period for the restricted area.

Validity Period FROM

Restricted Areas Window. Activation/Validity Area

Define the starting date for the validity period of the restricted area.

YYMMDD, where YY = year (00 to 99) MM = month (01 to 12) DD = day (01 to 31)

UNTIL

Define the ending date for the validity period of the restricted area.

YYMMDD, where YY = year (00 to 99) MM = month (01 to 12) DD = day (01 to 31)

Enter Activity Range Daily

Legend that indicates that the fields are used to introduce the activity period of the area or dates when the area is active.

Select a daily activation mode for the restricted area.

The switch colour code indicates the selection status. YELLOW = Selected Background = Not selected

FROM

TO

Define the starting time of the day for the activation period of the restricted area.

HHMM, where

Define the ending time of the day for the activation period of the restricted area.

HHMM, where HH = hour (00 to 23)

HH = hour (00 to 23) MM = minutes (00 to 59)

MM = minutes (00 to 59) Week

Select a weekly activation mode for the restricted area.


MTWTFSS

Select the day of the week when the restricted area is activated (from Monday to Sunday).




Page A-108



Field/Switch FROM

Description Define the starting time of the selected days of week, for the activation period of the restricted area.

Valid Data HHMM, where HH = hour (00 to 23) MM = minutes (00 to 59)

TO

Define the ending time of the selected days of week, for the activation period of the restricted area.

HHMM, where HH = hour (00 to 23) MM = minutes (00 to 59)

Dates On

Select the activation mode by events.


The system allows the definition of up to 4 activation periods for the restricted area.

YYMMDD/HHMM – YYMMDD/HHMM, where

In this mode of activation, the activation limits (starting and ending) are defined by time and date, not only time as in previous cases.

MM = month (01 to 12)

YY = year (00 to 99) DD = day (01 to 31) HH = hour (00 to 23) MM = minutes (00 to 59)

2.2.8.1.4 Layout Area This area is used to define the 3-D shape of the restricted area. The operator enters the vertical limits (upper and lower) and the type of shape for the restricted area (circle or polygon). When creating a circle, the centre point and the radius must be entered. When zones are being created, a set of points must be entered (up to 25).

Figure 2-59: Table 2-30: Field/Switch

Restricted Areas Window. Layout Area Restricted Areas Window. Layout Area

Description

VERTICAL LIMITS

Valid Data

Legend that indicates that the fields are related to the vertical limits definition for the restricted areas.

UPPER

Upper vertical limit of the restricted area.

From lower vertical limit to 999.

LOWER

Lower vertical limit of the restricted area.

From 000 to upper vertical limit.

Circle

Select the shape of the restricted area as a circle.


CENTER

Circle centre point.

A fix point known by the system or geodesic coordinates of a point within the system working area.

RADIUS

Circle radius.

Up to three numeric characters.



Page A-109



Field/Switch

Description

Valid Data The entered value is considered as Km.

Polygon

Select the shape of the restricted area as a polygon.


Points

Geodesic coordinates (latitude / longitude) of each point forming the polygon or the name of a fix if it is known by the system.

GGGMMSSLggmmssl where: GGG: from 000 to 180 MM:

from 00 to 59

SS:

from 00 to 59

L:

N or S

gg:

from 00 to 90

mm:

from 00 to 59

ss: l:

from 00 to 59 E or W

or Up to 7 alphanumeric characters

2.2.8.1.5 Command Area

Figure 2-60:

Restricted Areas Window. Command Area

Commands included in this area are described in following table: Table 2-31:

Restricted Areas Window. Command Area

Icon/Switch

Command

View

Display the data of the selected restricted area.

Create

Create a new restricted area.

Modify

Modify a restricted area.

Cancel

Delete a restricted area.

UPDATE


LIST SUMMARY

Request the existing restricted area list.

CANCEL


CLEAR

Delete the data displayed on the window fields.

2.2.8.1.5.1

Action: Common Step to Restricted Areas Operations

Click with the LB on the [AREAS] icon, situated in the Main Menu Area, to display the Restricted Areas Window. From this point on, that is, with the Restricted Areas Window displayed, all possible actions on restricted areas are performed.



Page A-110


2.2.8.1.5.2


Action: Create Restricted Area ACTION

1.

Once the Restricted Areas Window is displayed, click on the [Create] switch with the LB.

2.

Input data in the corresponding fields (description, validity, and layout).

3.


RESULT The switch becomes YELLOW and the accessible fields are displayed in WHITE background.

Compulsory Fields: Area ID, Type, Activity, Description, Validity (From and Until), Range of Dates, Vertical Limits and Lateral Bounds (Circle or Polygon).



Page A-111


2.2.8.1.5.3


Action: Modify Restricted Area ACTION

1.

Once the Restricted Areas Window is displayed, click with the LB on the [Modify] switch.

2.

Modify the required fields.

3.



Compulsory Fields: Area ID, Type, Activity, Description, Validity (From and Until), Range of Dates, Vertical Limits and Lateral Bounds (Circle or Polygon).



Page A-112


2.2.8.1.5.4


Action: Cancel Restricted Area ACTION

1.

Once the Restricted Areas Window is displayed, click with the LB on the [Cancel] switch, at the bottom of the "Restricted Areas" window, with the LB.

2.



Compulsory Fields: Area ID.




Page A-113



2.2.9 Icon [FLOW] Air Traffic Flow This functionality allows analyzing in advance, the future air traffic flow in order to warn the positions on the future air traffic congestions and complex air traffic situations. By means of this icon all actions related to the air traffic flow are performed. By clicking on the [FLOW] icon, a menu is displayed to select the type of flight plans to be analyzed (FPL).

Figure 2-61:

[FLOW] Icon

A sub-menu is displayed including the filter element type (Aerodrome/ Fix/ Sector) allowing traffic flow presentation. This functionality allows displaying the traffic volume of adjacent route sectors and displaying the traffic volume of adjacent route sectors in adjacent FIRs. The operator receives a warning if the current or future traffic flow of an element exceeds a defined limit for that element.

Figure 2-62:

FPs Traffic Flow Options

2.2.9.1 Flow FP Window The Flow FP Window allows the operator to restrict the query to flight plans database by a set of defined parameters (traffic flow element identification (Aerodrome/ Fix/ Sector) and FP time). The layout of the Flow FP Window is the same for any of the traffic flow elements previously selected. Only the “Flow Filter Element” field (“Aerodrome”, “Filter” and “Fix”) changes. It lists the number of allowed flights during the day which are going to overfly a specific airspace (airport, fix or sector) during a defined time segment. This option presents to the operator both a planned flights list for the day (according to the established filter) and a congestion list (for the same established filter). These actions are performed by means of queries to the FPLs database.



Page A-114



Filters Command Area

Flow Area

List


Command Area


Page A-115



Filters Edition Area

Command Area

Figure 2-63:

Flow FP Window

2.2.9.1.1 Filters Edition Area Following table lists for each field included in the Flow FP Window, a description with their valid data. Table 2-32:

Flow FP Window. Filters Edition Area

Field/Switch

Description

Valid Data

Aerodrome / Fix / Sector

Airport identification / Fix point identification / Sector identification.

Known by the System

FROM

Lower temporal limit (time) for filtering the FPLs (FROM)


UNTIL

Upper temporal limit (time) for filtering the FPLs (TO)


2.2.9.1.2 Command Area Following table shows the different commands included in the Flow FP Window. Table 2-33:

Flow FP Window. Command Area

Icon

Command

F.LIST

Display the FPs Traffic Flow List.

C. CHART

Displays the FPs Congestion Chart

CANCEL

Close the Flow FP Window.

CLEAR

Delete the information displayed on the Flow FP Window.

2.2.9.1.2.1

Action: FPLs Flow ACTION


RESULT


Page A-116



ACTION

RESULT

1.

Click with the LB on the [FLOW] icon.

A menu is displayed to select the type of flow element.

2.

Click on the desired filter element (aerodrome, fix or sector).

The Flow FP Window is displayed.

In this case, the selected type of flow element is Aerodrome.

3.

Define the filters for the query by entering the specific data in the corresponding fields.

4.

Finish the action according to following icons:



Page A-117


ACTION 4.1.

Click with the LB on the [F.LIST] icon of the Flow FP Window.


RESULT If entered data are correct, the FPs Traffic Flow List is displayed (see point 2.2.9.2)

The layout of the FPs Traffic Flow List depends on the type of flow element selected (step 2). So that, the information displayed in the list is the following: If Aerodrome, The list displays the FPLs departing or arriving from/to the selected aerodrome. If Fix, The list displays the FPLs that include the fix in their route. The list distinguishes flights plan going to or from the fix. If sector, The list displays the FPLs (without distinction between arrivals and departures) whose route fix belong to the sector. From this list, the operator may click on the [CANCEL] icon, and all windows are closed. 4.2.

Click twice on any line of the FPs Traffic Flow List.



Page A-118


ACTION


RESULT The FP Operation Window is displayed and the user can perform the allowed operations.

4.3.

Click with the LB on the [C. CHART] to display the FPs Traffic Congestion List in graphical mode.

Theses statistics windows allow filtering the data by entering the corresponding values in the Edition Area. They also allow selecting the time interval for data display among 5, 15, 30 and 60 minutes by clicking on the corresponding icons. Likewise, the graphic can be printed by clicking on the [PRINT] icon and close the window by clicking on the [CANCEL] icon. For detailed information see 2.2.9.3. Compulsory Fields: For the Aerodrome Element: the “Aerodrome” field For the Fix Element: the “FixPoint” field. For the Sector Element: the “Sector” field.

2.2.9.2 FPs Traffic Flow List When clicking on the [F. LIST] icon of the Flow FP Window, the FPs Traffic Flow List is displayed. This list contains the FPs information that match the filters defined in the Flow FP Window. The list consists of the following areas:

Applied Filter:



Page A-119



This area includes the name of the selected traffic flow element (aerodrome, fix, or sector) and the previously edited values for the temporal filters (“FROM” and “TO”), if any. These fields are informative fields, that is, cannot be modified. FPs List Area Depending on the selected traffic element (aerodrome, fix, or sector), the list arranges the information in a different way: List by Aerodrome It includes the FPs arriving or departing to/from the selected aerodrome with the ETA/ETD within the selected range. The list is ordered by ETD (departures) and ETA (arrivals).

Figure 2-64: Table 2-34:

FP Found for the given filter

FPs Traffic Flow List. Aerodrome

Element ARRIVALS


Description Arrival FPs


Page A-120


Element


Description

DEPARTURES

Departure FPs

DEP

Departure Aerodrome

CALLSIGN


EOBD


EOBT


TYPE

Aircraft Type

ETA


DEST


CALLSIGN


EOBD


EOBT


TYPE

Aircraft Type

List by Fix It includes the FPs either arriving or departing which contain the selected fix point in their routes. ETO orders this list.

Figure 2-65:


FP Found for the given filter


Page A-121


Table 2-35:


FPs Traffic Flow List. Fix

Element

Description

ARRIVALS

Arrival FPs

DEPARTURES

Departure FPs

DEP

Departure Aerodrome

DEST


CALLSIGN


EOBD


EOBT


TYPE

Aircraft Type

LEVEL

Flight Level

ETO

Estimated Time Over a significant point

DEP

Departure Aerodrome

DEST


CALLSIGN


EOBD


EOBT


TYPE

Aircraft Type

LEVEL

Flight Level

List by Sector It does not include a distinction between arrivals and departures. Displayed flights are those whose fix points belong to the sector. It is ordered by sector entry time.



Page A-122


Figure 2-66: Table 2-36:


FP Found for the given filter FPs Traffic Flow List. Sector

Element

Description

DEP

Departure Aerodrome

DEST


CALLSIGN


EOBD


EOBT


TYPE

Aircraft Type

LEVEL

Flight Level

ROUTE

Flight Plan Route

2.2.9.2.1 Command Area Table 2-37:

FPs Traffic Flow List. Command Area Icon

Description

CANCEL

Close the FPs Traffic Flow List

PRINT

Print the FPs Traffic Flow List

If double click is performed on an entry of List flow, user can access to FP Operation Window.



Page A-123



2.2.9.3 FPs Traffic Congestion List This window is displayed when clicking on the [C.CHART] icon situated in the Flow FP Window once the filter has been selected. The graphic allows viewing the Flight Plans number within the selected time interval, in 5, 15, 30 or 60 time intervals. Tittle Edition Area

Graphical Area

Command Area Figure 2-67: Table 2-38:

FPs Traffic Congestion List Graphic

FPs Traffic Congestion List Graphic. Edition Area Element

Table 2-39:

Description

From

Starting time for filter application.

To

Ending time for filter application.

FPs Traffic Congestion List Graphic. Graphical Area

Element

Description

Sector/ Fixpoint/ Aerodrome Overpasses

Number of flights (different or repetitive), which passed within the predefined interval by the sector/ fix/ aerodrome.

Time

Application time in the graphic.

Table 2-40:

FPs Traffic Congestion List Graphic. Command Area Element


Description

Interval length

Time interval longitude to perform the graphic.

CANCEL

Close the FPs Traffic Congestion List.

PRINT

Not applicable.


Page A-124



2.2.10 Icon [METEO] Meteorological Data Following meteorological messages are received from the AFTN and AIS and are automatically processed by the System: ATIS; SIGMET; TAF; METAR; AIRMET; SPECI; SNOWTAM; GAMET. These messages are stored in the FDPS disc. The FIR aerodrome of these messages is extracted and used as key for a posterior access from the controller positions. The validity period of these messages is taken into account for automatic deletion of messages which are expired. The operator receives a warning when the validity period of the meteorological data has expired. The QNH value for specific zones, defined in adaptation, is extracted from the METAR and SPECI messages. Following meteorological information can be entered once the users have been defined: Meteorological Reports-Aviation Routine Weather Report (METAR); Special Meteorological Aeronautical Report (SPECI); Terminal Area Forecast (TAF). This icon allows performing the edition action of the meteorological and aeronautical information manually entered.

Figure 2-68:

[METEO] Icon

When clicking on the [METEO MSG] icon, a menu is displayed to select the message to obtain the meteorological information: ATIS: Air Traffic Information System 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



Page A-125



greater icing over a 3000 sq mile area or IMC conditions over a 3000 sq mile area due to dust, sand, or volcanic ash. 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. 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. 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. 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.



Page A-126



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).

2.2.10.1

Meteorological Information Window

When selecting any of the options included in the [METEO MSG] icon, the Meteorological Information Window is displayed. The Meteorological Information Window 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. The window title indicates the meteorological page selected. The layout of this window is shown in figure below.

Figure 2-69:

2.2.10.1.1

Meteorological Information Window

Selected Message

The window title depends on the selected message when clicking on the [METEO MSG] icon.

2.2.10.1.2

Airport Selection

By clicking on the icon situated at the top right corner of the Meteorological Information Window, a menu is displayed to select the airport from which the meteorological information is obtained.

2.2.10.1.3

Edition Area

It is formed by three fields, which are described in following table: Table 2-41:

Meteorological Information Window. Edition Area

Field From

Description Define the starting date DDHHMM (DD – Day, HH – Hour, MM – Minutes)

To


Define the ending date


Page A-127



DDHHMM (DD – Day, HH – Hour, MM – Minutes) Text

Free Text

The vertical and horizontal scroll bars allow the visualization of the text not in view due to window size.

2.2.10.1.4

Command Area

Following table shows the different commands included in the Meteorological Information Window. Table 2-42:

Meteorological Information Window. Command Area

Icon/Switch

Command

Edit

Allow the data input within the corresponding fields.

UPDATE

Send the edited message, but the window remains displayed.

CANCEL

Close the Meteorological Information Window.

CLEAR

Delete the information displayed in the Meteorological Information Window.

PRINT

Print the data included in the Meteorological Information Window.

2.2.10.1.4.1 Action: Edit Meteorological Page ACTION

RESULT

1.

Click with the LB on the [METEO MSG] icon.

A pull-down menu for selecting the desired meteorological page is displayed.

2.

Select one of the options from the menu.

The Meteorological Information Window is displayed.

3.

Enter data in the “Edition” field. The airport is selected by clicking on the icon situated in the top right of the window.

4.




Page A-128



2.2.11 [NOTAM] Icon This icon allows performing different actions related to the NOTAM information. The FDPS manages the NOTAMs received from the AFTN or those entered manually from the positions. The NOTAM messages are sent to the “Q” Queue for operator validation. If the operator validates the NOTAM message, it is included into the NOTAMs database. When clicking on the icon, the NOTAM Operation/Retrieval Window is displayed.

Figure 2-70:

2.2.11.1

[NOTAM] Icon

NOTAM Operation/Retrieval Window

The System maintains a NOTAMs database. The FDD operator can perform the following functions on that database: Query (display) a NOTAM; Create a new NOTAM; Modify a NOTAM; Cancel a NOTAM; Print a NOTAM; Retrieve several NOTAMs by means of searching criteria: NOTAM identifier Validity period starting date (campo B) Validity period ending date (campo C) NOTAM category (QCODE). Obsolete NOTAM are deleted from the database automatically when the validity period has expired. The NOTAM Operation/Retrieval Window 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 A-129



Figure 2-71:

2.2.11.2

NOTAM Operation/Retrieval Window

Edition Area

Following table describes the fields included in the NOTAM Operation/Retrieval Window and the correct values: Table 2-43: Field

NOTAM Operation/Retrieval Window. Edition Area

Description

ID

NOTAM identification type

Valid Data A or B plus 4 numeric characters plus “/” plus YY, where YY = year (00 to 99)

Field A)

Airport

ICAO airport indicator. 4 alphabetic characters.

Field F)

Level

Hundreds of feet: Fxxx where xxx 000 to 999 Tens of meters: Sxxxx where xxx 0000 to 9999

Field G)

Level

Hundreds of feet: Fxxx where xxx 000 to 999 Tens of meters: Sxxxx where xxx 0000 to 9999

Field Q) FIR

4 characters (ICAO indicator)

CODE

Two characters.

STAT

Two characters. NOTAM code meaning.

REMAINDER

Following string: “/”



Page A-130



Field

Description Traffic

Valid Data I, V or IV, where I = IFR V = VFR IV = Both IFR and VFR

“/” Purpose

3 alphabetical characters B, O, M, BO, NB, NBO

“/” Range

1 or 2 alphabetical characters AA, E, W, AE

Limits

XXX/xxx, where XXX = 3 numeric characters (000 to 999) xxx = 3 numeric characters (000 to 999)

“/” Geodesic coordinates

GGGMMSSLggmmssl where: GGG: from 000 to 180 MM: from 00 to 59 SS: from 00 to 59 L: N or S gg: from 00 to 90 mm: from 00 to 59 ss: from 00 to 59 l: E or W

Field B) From

YYMMDDHHMM, where YY = year (00 to 99) MM = month (01 to 12) DD = day (01 to 31) HH = hour (00 to 23) MM = minutes (00 to 59)

Field C) Until

YYMMDDHHMM, where YY = year (00 to 99) MM = month (01 to 12) DD = day (01 to 31) HH = hour (00 to 23) MM = minutes (00 to 59)

Field D) Schedule

D/D/D/ HHMM/HHMM, where D = day (1 to 31) HH = hour (00 to 23) MM = minutes (00 to 59)

Field E) TEXT

2.2.11.3

Free text


Command Area

Following table shows the commands included in the NOTAM Operation/ Retrieval Window. Table 2-44:

NOTAM Operation/ Retrieval Window. Command Area

Icon/Switch

Command

View

Display the NOTAM data.

Cre.

Create a new NOTAM.



Page A-131


Icon/Switch

2.2.11.3.1


Command

Mod.

Modify an existing NOTAM.

Can.

Delete an existing NOTAM.

Mul.

Display all NOTAM included in the database.

PRINT

Print the single NOTAMs.

UPDATE

Trigger all input data.

CANCEL

Close the NOTAM Operation/Retrieval Window.

CLEAR

Delete the data displayed on the NOTAM Operation/Retrieval Window.

Action: Common Action to NOTAM Procedures

ACTION

RESULT

1.

The System displays the NOTAM Operation/Retrieval Window in visualization mode ([View] switch selected). All fields are accessible except “ID” field.

Click with the LB on the [NOTAM] icon.

From this point on, actions are described according to command procedure.

2.2.11.3.2

Action: Create a New NOTAM ACTION

1.

Click with the LB on the [Cre.] switch


RESULT The switch becomes YELLOW. All fields are accessible to input data.


Page A-132


2.

Enter the data.

3.



Compulsory Fields: ID, FIR, Code, Stat, From and Until.

2.2.11.3.3

Action: Modify NOTAM ACTION

RESULT

1.

Perform the 2.2.11.3.1).

2.

Click with the LB on the [Mod.] switch.

3.

Modify the required fields. Some of them do not allow to be changed. Some others are mandatory.

4.


visualize

NOTAM

action

(see The switch becomes YELLOW. All fields are accessible.

Compulsory Fields: ID but only if the NOTAM visualization action was not previously performed.



Page A-133


2.2.11.3.4


Action: Cancel NOTAM ACTION

1.

Perform the visualize NOTAM action (see 2.2.11.3.1).

2.

Click with the LB on the [Can.] switch.

3.


RESULT The switch becomes YELLOW. All fields related to the action are accessible.

Compulsory Fields: ID but only if the NOTAM visualization action was not previously performed.

2.2.11.3.5

Action: Retrieve Multiple NOTAM ACTION

RESULT

1.

Perform the visualize NOTAM action (see 2.2.11.3.1).

2.

Click with the LB on the [Mul.] switch

The switch becomes YELLOW.

3.


The NOTAM Multiple Window is automatically displayed on top.



Page A-134



ACTION 4.

RESULT



2.2.11.4

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 ¡Error! No se encuentra el origen de la referencia.

2.2.12 [T. Flow] Icon This icon allows performing all actions related to the traffic flow. When clicking on it, a pull-down menu is displayed as shown in following figure:

Figure 2.2.12-1: [T. Flow] Icon This pull-down menu presents the following options: ● FP Act. – When clicking on this option, the “FP Flow Actions” Window is displayed. ●

Slot Act. – When clicking on this option, the “Flow Restrictions” Window is displayed.

●

FPs/ Slots Retrieve – When clicking on this option, a pull-down submenu is displayed to select the FP or Slots retrieval filters:

Figure 2.2.12-2: [T.Flow] Icon. Retrieve Option The retrieve options displayed are the following ones: ● FPs – Display the “Retrieve FP‟s Flow” Window ●

Slots – Display the “Retrieve Slots Flow” Window

2.2.12.1 “FP Flow Actions” Window This window allows the FPs traffic distribution for crossing the defined element (fix point), either automatically or manually.



Page A-135



Figure 2.2.12-3: “FP Flow Actions” Window The “FP Flow Actions” Window consists of a form including fields to be filled in by the operator (edition area) and a command area at the bottom of the window.

2.2.12.1.1

Edition Area

This area includes fields, which are described in following table: Table 2.2.12.1-1: “FP Flow Actions” Window. Edition Area Field Description F.ELEMENT

Fix point

CALLSIGN


DEPARTURE

Departure Aerodrome FP1

FP 1

FP2

FP 2

EOBD

End Of Block Date

EOBT


DEST


SLOT START

Slot starting time (not editable)

OV. TIME

Time when the slot is overflown (not editable)

ALLOC. TIME

FP allocation time. If the value is not introduced, it is automatically filled in.

2.2.12.1.2

Command Area

The commands included in this area are described in following table: Table 2.2.12.1-2: “FP Flow Actions” Window. Command Area Icon / Switch Command Allocate

Allocate a FP (Initial or Pending) to an element (fix)

Exchange

Exchange between FPs (FP1-FP2)

Release

Delete the FP

UPDATE

Trigger the actions performed in current window

CANCEL

Close the window. If the actions were previously validated, they will not be taken



Page A-136



into account by the system. CLEAR


2.2.12.2 “Flow Restrictions” Window This window defines the flow restrictions for a flow element (fix point).

Figure 2.2.12-4: “Flow Restrictions” Window The “Flow Restrictions” Window consists of a form including fields to be filled in by the operator (edition area) and a command area at the bottom of the window.

2.2.12.2.1

Edition Area

This area is formed by fields, which are described in following table: Table 2.2.12.2-1: “Flow Restrictions” Window. Edition Area Field Description F.ELEMENT

Fix Point

FROM

Slot starting time (fix) HHMM (HH – hour, MM – minutes)

TO

Slot ending time (element-fix) HHMM (HH – hour, MM – minutes)

RANGE

2 numeric characters (FPs per hour)

1, 2, 3

Number of slots by element that can be created.

2.2.12.2.2

Command Area

The commands included in this area are described in following table: Table 2.2.12.2-2: “Flow Restrictions” Window. Command Area Icon / Switch Command FP Act.

Display the “FP Flow Actions” Window.

Ret, FP’s

Display the “Retrieve FP‟s Flow” Window.

Ret. Slots

Display the “Retrieve Slots Flow” Window.



Page A-137



View

Display the flow restriction data for the selected flow element (fix).

Create

Define the flow restrictions for a new flow element.

Modify

Modify the flow restrictions for the retrieved flow element.

Cancel

Delete the flow restrictions for the retrieved flow element.

UPDATE


CANCEL


CLEAR


2.2.12.3 “Retrieve FP’s Flow” Window This window allows the retrieval of FPs overflying a selected flow element.

Figure 2.2.12-5: “Retrieve FP’s Flow” Window The “Retrieve FP‟s Flow” Window 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 a list of retrieved FPs.

2.2.12.3.1

Edition Area

This area only includes the “F_ELEMENT” (fix) field. This field is the filter to retrieve the FPs overflying the selected flow element (fix).

2.2.12.3.2

Command Area

The commands included in this area are described in following table: Table 2.2.12.3-1: “Retrieve FP’s Flow” Window Command Area Icon / Switch Command Alloc

Retrieve and display all FPs allocated to the flow element (fix).



Page A-138



Not Alloc

Retrieve and display all FPs, which are not allocated to the flow element (fix).

UPDATE


CANCEL


CLEAR


2.2.12.3.3

Retrieved FPs List

This list presents all FPs (allocated or not allocated, depending on the selection) that overflown the selected element. The data included in the list are the following ones: ● ACID – Aircraft identification ●

DEP – Departure aerodrome

●

EOBD – Estimated off-block date

●

EOBT – Estimated off-block time

●

DEST – Destination aerodrome

●

ETD – Actual Departure Time. This field is not displayed when the previous selection was “Not Allocated”.

●

SLOT START – Slot starting time. This field is not displayed when the previous selection was “Not Allocated”.

●

SLOT END – Slot final time. This field is not displayed when the previous selection was “Not Allocated”.

2.2.12.4 “Retrieve Slots Flow” Window This window allows the retrieval of the defined slots for a flow element.



Page A-139



Figure 2.2.12-6: “Retrieve Slots Flow” Window The “Retrieve Slots Flow” Window 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 a list of retrieved Slots.

2.2.12.4.1

Edition Area

This area only includes the “F_ELEMENT” (fix) field. This field is the filter to retrieve the Slots defined for the flow element (fix). When clicking on the [UPDATE] icon before entering the element name, a window including all the elements where flow restrictions has been defined is displayed ("Rest. SLOT Frame" Window). The selection is performed clicking twice on the desired element in this window.



Page A-140



Figure 2.2.12-7: “Retrieve Slots Flow” Window. Elements Window

2.2.12.4.2

Command Area

The commands included in this area are described in following table: Table 2.2.12.4-1: “Retrieve Slots Flow” Window. Command Area Icon / Switch Command Alloc

Display all Slots allocated to the fix.

Not Alloc

Display all Slots not allocated to the fix.

UPDATE


CANCEL


CLEAR


2.2.12.4.3

Retrieved Slots List

This list presents all Slots (allocated or not allocated, depending on the selection) that overflow the selected element. The data included in the list are the following ones: ● Slot START Time – Slot starting time ●

Slot END Time – Slot final time

2.2.12.5 Action: Allocate FP to a Slot Element (FixPoint) => {[T.Flow] => [FP Act.]} Application: Allocate a FP to a Slot element previously defined. ACTION

RESULT

Click on the [T.Flow] icon of the Main Menu Area. A pull-down menu is displayed.



Page A-141


ACTION


RESULT

Select the “FP Act.” option. The “FP Flow Actions” window is displayed with the corresponding accessible edition fields. The [Allocate] switch is activated. Enter data in the corresponding fields.

Finish the action by clicking on one of the following icons: [UPDATE] icon If the entered data are correct, the allocation action is triggered. If the entered data are erroneous, an error message is displayed. If mandatory fields are not filled in, an error message is displayed. [CANCEL] icon The window is closed and the action is aborted, if was not previously validated ([UPDATE] icon). [CLEAR] icon The displayed data are deleted from the window.

2.2.12.6 Action: Exchange FPs Distribution => {[T.Flow] => [FP Act.]} Application: Exchange the distribution between two FPs on the basis of an element Slot previously defined. ACTION RESULT Click on the [T.Flow] icon of the Main Menu Area. A pull-down menu is displayed.



Page A-142


ACTION


RESULT

Select the “FP Act.” option. The “FP Flow Actions” window is displayed with the corresponding accessible edition fields. The [Allocate] switch is activated.

Enter data in the corresponding fields. Click on the [Exchange] switch. The fields corresponding to FP 2 are activated (become WHITE). Enter data in the fields corresponding to the second FP.

Finish the action by clicking on one of the following icons: [UPDATE] icon If the entered data are correct, the exchange action is triggered. If the entered data are erroneous, an error message is displayed. If mandatory fields are not filled in, an error message is displayed. [CANCEL] icon The window is closed and the action is aborted, if was not previously validated ([UPDATE] icon). [CLEAR] icon The displayed data are deleted from the window.

2.2.12.7 Action: Cancel FP Distribution => {[T.Flow] => [FP Act.]} Application: Delete the FP allocated to an element Slot previously defined.



Page A-143


ACTION


RESULT


Select the “FP Act.” option. The “FP Flow Actions” window is displayed with the corresponding accessible edition fields. The [Allocate] switch is activated. Enter data in the corresponding fields. Click on the [Release] switch.

Finish the action by clicking on one of the following icons: [UPDATE] icon If the entered data are correct, the deletion action is triggered. If the entered data are erroneous, an error message is displayed. If mandatory fields are not filled in, an error message is displayed. [CANCEL] icon The window is closed and the action is aborted, if was not previously validated ([UPDATE] icon). [CLEAR] icon The displayed data are deleted from the window.

2.2.12.8 Element Slots Procedures => {[T.Flow]=> [Slot Act.]} 2.2.12.8.1

Action: Visualize Slots => {[T.Flow] => [Slot Act.]}

Application: Visualize the slots defined for an element. ACTION

RESULT

Click on the [T.Flow] icon of the Main Menu



Page A-144


ACTION


RESULT

Area. A pull-down menu is displayed.

Select the “Slot Act.” option. The “Flow Restrictions” window is displayed.

Enter data in the “F.Element” field. Finish the action by clicking on one of the following icons: [UPDATE] icon If the entered data are correct, the data are displayed on their corresponding fields. If the entered data are erroneous, an error message is displayed. If mandatory fields are not filled in, an error message is displayed. [CANCEL] icon The window is closed and the action is aborted, if was not previously validated ([UPDATE] icon). [CLEAR] icon The displayed data are deleted from the window.

2.2.12.8.2

Action: Create Slots => {[T.Flow] => [Slot Act.]}

Application: Create slots for an element. ACTION

RESULT




Page A-145


ACTION


RESULT


Click on the [Create] switch. Enter data in the corresponding fields.

Finish the action by LB click on one of the following icons: [UPDATE] icon If the entered data are correct, the data are displayed on their corresponding fields.

If the entered data are erroneous, an error message is displayed. If mandatory fields are not filled in, an error message is displayed. [CANCEL] icon The window is closed and the action is aborted, if was not previously validated ([UPDATE] icon). Flight Data Display User Manual


Page A-146


ACTION


RESULT

[CLEAR] icon The displayed data are deleted from the window.

2.2.12.8.3

Action: Modify Slots => {[T.Flow] => [Slot Act.]}

Application: Modify the element slots. ACTION

RESULT



Perform the visualization action to release the element (see 2.2.12.8.1).

Click on the [Modify] switch.

Modify the data in the corresponding fields. Finish the action by clicking on one of the Flight Data Display User Manual


Page A-147


ACTION


RESULT

following icons: [UPDATE] icon If the entered data are correct, the action is triggered. If the entered data are erroneous, an error message is displayed. If mandatory fields are not filled in, an error message is displayed. [CANCEL] icon The window is closed and the action is aborted, if was not previously validated ([UPDATE] icon). [CLEAR] icon The displayed data are deleted from the window.

2.2.12.8.4

Action: Cancel Slots => {[T.Flow] => [Slot Act.]}

Application: Cancel the element slots. ACTION

RESULT



Perform the visualization action to release the element (see 2.2.12.8.1).



Page A-148


ACTION


RESULT

Click on the [Cancel] switch.

Finish the action by clicking on one of the following icons: [UPDATE] icon If the entered data are correct, the action is triggered and the element slot is deleted. If the entered data are erroneous, an error message is displayed. If mandatory fields are not filled in, an error message is displayed. [CANCEL] icon The window is closed and the action is aborted, if was not previously validated ([UPDATE] icon). [CLEAR] icon The displayed data are deleted from the window.

2.2.12.9 Action: Retrieve Multiple FPs Distribution => {[T.Flow] => [FPs/ Slot Ret] => [FP]} ACTION

RESULT




Page A-149


ACTION


RESULT

Select the “FPs/ Slot Ret” option. A pull-down submenu is displayed.

Select the “FP” option. The “Retrieve FP‟s Flow” window is displayed.

Enter the selection values (element). Click on the [UPDATE] icon. The Retrieved FPs List is displayed including the FPs distributed by the selected element.

The [Alloc] switch is activated by default and all FPs allocated to the element are displayed. To display the no-allocated FPs, click on the [Not Alloc] switch and perform the same step. Finish the action by clicking on the [CANCEL] icon The window is closed.



Page A-150



2.2.12.10 Action: Retrieve Multiple Slots Distribution => {[T.Flow] => [FPs/ Slot Ret] => [SLOTS]} ACTION

RESULT


Select the “FPs/ Slot Ret” option. A pull-down submenu is displayed.

Select the “SLOTS” option. The “Retrieve Slots Flow” window is displayed.

Enter the selection values (element). Click on the [UPDATE] icon. The Retrieved Slots List is displayed including the Slots distributed by the selected element.



Page A-151


ACTION


RESULT

The [Alloc] switch is activated by default and all slots allocated to the element are displayed. To display the no-allocated slots, click on the [Not Alloc] switch and perform the same step. If clicking on the [UPDATE] icon without entered any element. Following window is displayed.

When clicking twice with the LB on any element, the datum is entered in the corresponding field of the “Retrieve Slots Flow” window. Finish the action by clicking on the [CANCEL] icon. The window is closed.



Page A-152



2.2.13 Icon [LINES] AFTN Lines Status This icon visualizes the AFTN Lines Window to inform about the status, the ESNI (Expected Sorted Number Input) and ESNO (Expected Sorted Number Output) of AFTN lines.

Figure 2-72:

[LINES] Icon

The window that allows modifying the parameters of one of the AFTN lines is displayed when clicking on the corresponding button (LINE1, LINE2) from the Panel Lines window. The AFTN line status might be one of the following ones: ON .- Line is in ONLINE status (available). OFF .- Line is in OFFLINE status (not available). The line is manually closed and it is not opened again automatically. FAIL .- Line is in FAIL status. A CH (Channel Check) has not been received from AFTN Lines within 20 seconds timeout.

Figure 2-73:

AFTN Lines Status Window

The FDP sends, every 20 seconds, a CH (Channel Check) through the lines and waits for receiving another CH as answer. If, within 2 seconds, the FDP does not receive an answer, the corresponding line turns to “FAIL” status. If the line status is “FAIL” and any message is received, the line status turns to “ON”. The criteria used to send messages through the lines from the FDP are the following one: Line 1 and Line 2 are in ON status. Messages will be transmitted alternating both lines. One of the lines is in ON status and the other one is in OFF or FAIL status. Messages will be transmitted through the line with the ON status. Line 1 and Line 2 are in OFF or FAIL status. Messages are not transmitted.



Page A-153



2.2.14 [INFO] Icon This icon displays the Info Window that shows the AIP (Aeronautical Information Publication).

Figure 2-74:

2.2.14.1

[INFO] Icon

INFO Window

The INFO Window consist on a form to consult the AIP (Aeronautical Information Publication). Every document could be selected throw a hyperlink. The main menu shows a list of hyperlinks. Every hyperlink links a document that should be displayed when selected.

Figure 2-75:

PIP Window

This Window shows hyperlinks to every necessary document. Selecting a hyperlink, the user has the possibility to show the document.

2.2.14.1.1

Command Area Table 2-2:

INFO Window. Command Area

Icon/Switch Back

Command Shows the last selected document.



Page A-154


Home

Go up to the main menu of the “PIP Window”

Exit

Close the “PIP Window”.


2.2.15 Icon [EST] Estimate

Figure 2-76:

[EST] Icon

This icon displays the EST Window that performs a quick estimate without having to access to the FP Operation Window.

Figure 2-77:

EST Window

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.

2.2.15.1

EST Window

This window allows performing a quick EST operation.

Figure 2-78:

EST Window

User can enter the fix point where is desired to make an EST operation and enter another data too. In this form, user can perform this action directly without accessing the FP template to do it. EST Window consists of a form including fields to be filled in by the operator (edition area) and a command area.



Page A-155


2.2.15.1.1


Edition Area

Following table presents for each field included in the EST Window, a description. Table 2-3:

EST Window. Edition Area

Field

2.2.15.1.2

Description

CALLSIGN


FIX

Fix name

SPEED

Aircraft speed

ETO

Estimated time over fix.

CFL

Flight level of the aircraft when fly over the fix.

CSSR

SSR code

Command Area

Following table describes the different commands included in the EST Window. Table 2-4:

EST Window. Command Area

Icon/Switch

Command

UPDATE

Perform the EST action over the entered fix (if data are correct).

CLEAR

Delete the data displayed on the EST Window.

2.2.15.1.2.1 Action: Quick Estimate Procedure ACTION

RESULT

1.

Click on the [EST] icon

A window to edit the Fixpoint, ETO, Level and Speed is displayed.

2.

Enter the callsign value in the corresponding field and press key.

Some fields are filled out automatically.



Page A-156



ACTION

RESULT

3.

Fill out the fields and click [UPDATE]

The window is closed and the estimated time over the entered fix point is performed.

4.

To cancel the action:

The window is closed without validating the entered data.

4.1.

Click with the LB the [EST] icon again.

2.2.16 [FREE TEXT] Icon Figure 2-79: “FREE TEXT” Icon

Figure 2-80: Channel selection for Free Text Free Text icon displays a pop-up menu with three channel to select. Once the channel is selected, the Free Text window is displayed, which is used to perform communication and dialogue between the FDD positions. A warning at each FDD indicates the arrival of any message through these channels.



Page A-157



Figure 2-81: “FREE TEXT” Window

2.2.17 [CLOCK] Icon

Figure 2-82: “CLOCK” Icon This icon is only available for FDD‟s non associated to a SDD position. By clicking in this icon, clock window is displayed/ inhibited. This window includes current system time and date.

Figure 2-83: Clock Window Table 2.2.15.1-1: Clock Window. Items Description Item

Format

Date

Week day ”,” (space) month (space) day number (space) YYYY YYYY = four digits of the year

Time

HH: MM (HH = Hour; MM = Minutes)

2.2.18 [LOGOUT] Icon By selecting this icon, the position is blocked, so it is not possible to perform any action.



Page A-158


Figure 2-84:


[LOGOUT] Icon

At the same time, it displays the Login Window to unlock the position.

Figure 2-85:

Login Window

As the figure shows, the window consists of two fields. The first one is used to introduce user's code and the second to introduce the password. Finally, when concluding the data input, press . If the FDD is assigned to an SDD, the [LOGOUT] icon may be not included in the FDD being its common action with that of the same name to which is in the SDD.

2.2.18.1

Freeze Position ACTION

1.

Click on the [LOGOUT] icon.

RESULT The position is frozen. At the same time, the “Login” Window is displayed.

2.

Introduce the correspondent data in the fields.

3.

Finish the action by pressing the key.

The position is unfrozen.

2.2.19 [PRINTER] Click on this icon to display all current available printers. Selected printed is marked with a yellow mark, and it can be changed by clicking in another one‟s mark.



Page A-159


Figure 2-86:



Printer Selection


Page A-160



Appendix A - Abbreviations and Glossary of Terms A.1

List of Abbreviations

Abbreviation

Definition

A AAI

FDD Message Queue

ABI

Advanced Boundary Information Message

A/C

Aircraft

ACC

Area/Airspace Control Centre

ACID


ACK

Acknowledge(ment)

ACP

Accept message

ACT

Activation Message

A/D

Analog-To-Digital

ADA

Programming language

ADEP

Aerodrome of Departure

ADES

Aerodrome of Destination

ADEXP

ATS Data Exchange Protocol

ADF

Automatic Dependent Finder

AFIL

Aircraft Filed Flight Plan

AFTN

Aeronautical Fixed Telecommunications Network

A/G

Air/Ground, Air-To-Ground

AIC

Aeronautical Information Circular

AIDC

Air Traffic Services Interfacility Data Communications

AIP

Aeronautical Information Publication

AIRMET

Airman Meteorological Information

AIS

Aeronautical Information Service

ALT

Altitude/Alternate

AMC

Airspace Management Cell

ANS

Air Navigation Services

APP

Approach Centre

APW

Area Proximity Warning

ARR

Arrival Message

ARTAS

ATM Surveillance Tracker and Server

ASTERIX

All Purpose Structured Eurocontrol Radar Information Exchange

ATA

Actual Time of Arrival

ATC

Air Traffic Control

ATCAS

Air Traffic Control Automation System

ATCC

Air Traffic Control Centre

ATD

Actual Time of Departure

ATFM

Air Traffic Flow Management

ATIS

Airport Traffic Information System



Page A-161


Abbreviation


Definition

ATM

Air Traffic Management

ATS

Air Traffic Services

AUP

Airspace Usage Plan

AUX

Auxiliary

B BYP

By-Pass Mode of Operation

C CA

Conflict Alert (see STCA)

CAA

Civil Aviation Administration/Authority

CAD

Computer-Aided Design

CB

Mouse Central Button

CBA

Cross-Border Areas

CBT

Computer-Based Training

CCR

Communications Compressor Radar

CD

Compact Disk

CDR

Conditional Routes

CFL


CFMU

Central Flow Management Unit

CHG

Change Message

CIN

See NIC

CLAM

Cleared Level Adherence Monitoring Alert

CMD

Control and Monitoring Display

CNL

Cancellation Message

CNS

Communications, Navigation and Surveillance

COP

Coordination Point

COTS

Commercial Off-The-Shelf

CPL

Current Flight Plan

CSCI

Computer Software Configuration Item

CSSR

SSR Code

CTF

Common Timing Facility

CTOT

Calculated Take-off Time

CWP

Control Working Position

D DBM

Data Base Management

DCT

Direct Route Qualifier

DEP

Departure Message

DEP

Departure Aerodrome

DEST


DF

Directional Finder

DL

Data Link/Downlink

DLA

Delay

DLS

Data link Service



Page A-162


Abbreviation DRF


Definition Data Recording Facility

E EET


ENSI

Expected Sorted Number Input

ENSO

Expected Sorted Number Output

EOBD


EOBT


EST

Estimate

ETA


ETD

Estimated Time of Departure

ETO

Estimated Time Over a Fix

F FANS

Future Air Navigation Systems

FBS

Fallback System

FCON

Fixed Configuration

FDA

Flight Data Assistant

FDD

Flight Data Display

FDP

Flight Data Processing

FDPS

Flight Data Processing System

FIFO

First In, First Out

FIR

Flight Information Region

FIX

Fix Point

FL

Flight Level

FMU

Flow Management Unit

FP

Flight Plan

FPL

Flight Plan

FUA

Flexible Use of Airspace

G GAT

General Air Traffic

GByte

Gigabyte

GHz

Gigahertz

GPS

Global Positioning System

GRIB

Wind Meteorological Message

GUI

Graphical User Interface

H HCI

Human-Computer Interface

HDLC

High-Level Data Link Communication

HFS

Horizontal Future Situation

HMI

Human-Machine Interface

HOLD

Hold(Ing)

HWCI

Hardware Configuration Item

Hz

Hertz



Page A-163


Abbreviation


Definition

I ICAO

International Civil Aviation Organization

IEEE

Institute of Electrical and Electronics Engineers

IFPS

Integrated Initial Flight Plan Processing System

IFR

Instrument Flight Rules

ILS

Instrumental Landing System

INB

Inbound

INF

Information Message

INT

Integrated Mode of Operation

ISO

International Standards Organization

K Kb

Kilobytes

Kbits

Kilobits

Kbps

Kilobits per second

KBps

Kilobytes per second

KCAS

Knots Calibrated Airspeed

Kgls

Kinematics GPS Landing System

KHz

Kilohertz

KIAS

Knots Indicated Airspeed

Km

Kilometer

KPS

KB per second

Kt

Knots (NM/ hour)

KW

Kilowatts

L LAM

Logical Acknowledgement Message

LAN

Local Area Network

LAT

Latitude

LB

Mouse Left Button

LCD

Liquid Crystal Display

LMG

Local Maps Generation

LONG

Longitude

M M

Match/Meter

Mb

Millibars

Mbar

Milibar

MET

Meteorological Information

METEO

Meteorological

METAR

Meteorological Aviation Routine Weather Report

MHz

Megahertz

MM

Millimeters

MON

Monoradar Mode of Operation

ms

millisecond



Page A-164


Abbreviation


Definition

MSAW

Minimum Safe Altitude Warning

MSB

Most Significant Bit

MSL

Minimum Sea Level

MTCD

Medium-Term Conflict Detection

N NAV

Navigation

NE

Navigation Equipment

NIC

Navigation Integrity Control

NM

Nautical Miles

NOTAM

Notice To Airmen

O OAT

Operational Air Traffic

OLDI

On-Line Data Interchange

ORCAM

Originating Region Code Assignment Method

P PAC

Pre-activation Message

PCA

Prior Coordination Airspace

PLT

Pilot

POS

Position Report

PSR

Primary Surveillance Radar

PSR T

Primary Surveillance Radar Track

PTS

Panoramic Tower Simulator

Q Q

FDD Messages Queue

QFE

Atmospheric pressure at aerodrome elevation or at runway threshold

QNH

Altimeter sub-scale sitting to obtain elevation when on the ground

R RAD

Radar

RAM

Route Adherence Monitoring

RAW

Restricted Area Warning

RB

Mouse Right Button

RBL

Range Bearing Line

RCA

Reduced Coordination Airspace

RDCU

Radar Data Communication Processor

RDP

Radar Data Processing

RDPS

Radar Data Processing System

RETD

Revised Estimated Time of Departure

RFL


RIE

Route Insertion Error

RISC

Reduced Instruction Set

RMCDE

Radar Message Conversion and Distribution Equipment

ROC

Rate of Climb



Page A-165


Abbreviation


Definition

ROD

Rate of Decent

RPL

Repetitive Flight Plan

RVSM

Reduced Vertical Separation Minimum

RWY

Runway

S SAM

Slot Allocation Message (CFMU Message)

SAR

Search and Rescue

SBY

Standby

SDD

Situation Data Display

SDP

Surveillance Data Processing

SFPL

System Flight Plan

SID

Standard Instrument Departure

SIGMET

Significant Meteorological Information

SIM

Simulator System

SMC

System Monitoring Computer

SPECI

Special Forecast

SPI

Special Position Identification

SQL

Structured Query Language

SSR

Secondary Surveillance Radar

SSS

Software System Specification

STAR

Standard Instrument Arrival Route

STCA

Short-Term Conflict Alert

ST-RAW

Short-Term Restricted Area Warning

T TACT

Tactical System

TAF

Terminal Area Forecast (ICAO)

TAIS

Total Aircraft Information System

TAS

True Airspeed

TCP

Transmission Control Protocol

TCP/IP

TCP/Internet Protocol

TMA

Terminal Maneuvering Area

TFL

Transfer Fly Level

TL

Transition Level

TOC

Top of Climb

TOD

Top of Descent

TRA

Temporary Reserved Area

TSA

Temporary Segregated Area

TSP

Technical Supervisor

TWR

Tower or Tower Control

U UAC

Upper Airspace Control Centre

UTC

Universal Time Coordinated



Page A-166


Abbreviation UUP


Definition Updated Airspace Usage Plan

V VFS

Vertical Future Situation

VFR

Visual Flight Rules

VSP

Variable System Parameter

W WAN

Wide Area Network

Wi-Fi

Wireless Fidelity

WWW

World Wide Web

X X.25

A.2

Standard Protocol In Telecommunications

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. 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.



Page A-167



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. 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. Flight Data Display User Manual


Page A-168



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. Height Vertical distance of a level, a point or an object considered as a point, measured from a specified datum (ground). Leader Line It joins the data label to its corresponding track.



Page A-169



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 target‟s previous positions and generates a new track position update for the display. A lost track is dropped from both the display and the target tracker‟s 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. Pop-up Menu Menu displayed upon clicking once on a selectable option, usually a track field. The menu‟s 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.



Page A-170



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 menu‟s 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. 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.



Page A-171



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 aircraft‟s corresponding Present Position Symbol (PPS) to change to the Special Purpose Indicator on the SDD. This PPS is used to differentiate the aircraft‟s 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 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 controller‟s 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. Traffic Flow Set of reports, which are provided by the System under operator‟s 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. Flight Data Display User Manual


Page A-172



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-173



Page intentionally left blank



Page A-174



Appendix B - FP Route B.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.

B.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. 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



Page B-175



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.

B.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: Only two asterisks or none may be displayed within an element.

1.

1.

Only one parenthesis may be displayed within an element and always the open parenthesis, “(“, has to be previous to the close one, “)”.

2.

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. TIME expresses the estimated time of point crossing level. It is a string of five characters in the form: T c1 c2 c3 c4



Page B-176



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. 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.



Page B-177



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. 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 Flight Data Display User Manual


Page B-178



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. 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. Flight Data Display User Manual


Page B-179



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: 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.



Page B-180



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. The notation (/COORD_KEYWORDS) COORD_KEYWORDS followed as desired.

means

that

they

are

as

much

elements

FICTITIOUS POINTS SEQUENCE 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.



Page B-181



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. 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 Flight Data Display User Manual


Page B-182



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. 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.



Page B-183



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)

If it is a boundary point, the previous elements will be deleted.

b)

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)

If it is a boundary point, the subsequent elements will be deleted.

b)

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, w ill 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: 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:



Page B-184



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}

DCT

{Sacta Destination}

{Sacta Departure} DCT POINT/COORDINATE DCT {Sacta Destination} {Sacta Departure} Destination}

DCT

BOUNDARY_point_BOUNDARY_coordinate

{Non_SACTA

{Non_Sacta Departure} BOUNDARY_point/ BOUNDARY_coordinate DCT {Sacta Destination} 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.



Page B-185



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 => 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 Flight Data Display User Manual


Page B-186



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. Remaining situations will DISCONTINUITY_ERROR.

AWY_1

cause POINT

and

will

be

marked

AWY_1 to be marked

with with

h. Sequences with two points and an airway in between. Being the sequence: POINT_1AIRWAYPOINT_2 Following cases will be given: 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.



Page B-187



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. 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.



Page B-188



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. 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:



Page B-189



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: 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.



Page B-190



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: 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.



Page B-191



Sequence:

2.

Internal_point_with_IFR_keyword Remaining_elements The boundary point is not calculated. 3.

Sequences:

Point_1

Point_2 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 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.

For the right section extreme, following cases will be presented: Sequence:

1.

Remaining_elementsBoundary_point The boundary point is presented and there is no need of calculation. 7.

Sequence:

Remaining_elements Internal_point_with_IFR_keyword The boundary point is not calculated. 8.

Sequences:

Remaining_elementsPoint_2 DCT Point_1 Remaining_elements

Point_2

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 and the VALIDATE_BOUNDARY_POINT error will m ark it. 9.

Sequences:

Remaining_elementsPoints_2 Points_1



Page B-192



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. 10.

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. 11.

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} 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.



Page B-193






Page B-194



Appendix C - 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, …



Page C-195






Page C-196



Appendix D - 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-197






Page D-198



Appendix E - Error Message of Route Field E.1

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.

E.2

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.

E.3

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 aircraft‟s 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.



Page E-199


E.4


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.

E.5

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 E-200



Appendix F - Coordination Messages F.1

Reception and Processing of Coordination Messages

Coordination is a three-phase process, which includes Notification, Coordination, and Transfer. The Coordination phase may lead to a dialogue, in cases where such a procedure is configured with the corresponding partner. The development of the coordination process depends on the communication protocol available between two adjacent centres (AIDC).

F.2

AIDC Coordination Messages

ABI (ADVANCE BOUNDARY INFORMATION) The System uses the ABI message to give advance information on flights and transmit it at a bilaterally agreed time or position (VSP) before the common boundary. The System communicates changes to a previously transmitted ABI by means of another ABI. Changes to the cleared route of flight results in the retransmission of an ABI message. ACP (ACCEPTANCE) The System uses the ACP message to confirm that the contents of a received CPL, CDN, EST or PAC message are accepted. The System provides the capability of generating ACP messages automatically or manually. AOC (ASSUMPTION OF CONTROL) The System sends an AOC message in response to a TOC to indicate acceptance of executive control of a flight. CDN (COORDINATION) The System uses the CDN message to propose changes to the coordination conditions agreed to in a previously transmitted CPL, EST, PAC or CDN message. The System receives an ACP message to terminate the initial coordination dialogue; otherwise, if the System receives a REJ message, it leaves the coordination conditions as previously agreed. CPL (CURRENT FLIGHT PLAN) The System uses the CPL message to initiate initial coordination dialogue with another automated ATS system for a specific flight. EST (COORDINATION ESTIMATE) The System uses the EST message to inform the receiving centre of the crossing conditions for a flight and to indicate that the conditions are in compliance with agreements between both parties. The System receives an ACP message to complete the coordination process. LAM (LOGICAL ACKNOWLEDGEMENT MESSAGE)



Page F-201



The System sends a LAM message for each message (except for another LAM or LRM) that has been received, processed, found free of errors and, where relevant, is available for presentation to a control position. If the System expects to receive a LAM message, buy it is not received, it warns the controller. LRM (LOGICAL REJECTION MESSAGE) The System uses the LRM message to reject a message which contains invalid information. MAC (COORDINATION CANCELLATION) The System uses the MAC message specifically to indicate to a receiving centre that all notification and/or coordination received for a flight is no longer relevant to that centre. PAC (PREACTIVATION) The System uses the PAC message to inform the receiving centre of the crossing conditions for a flight which has not yet departed and to indicate that the conditions are in compliance with agreements between both parties. The System receives an ACP message to complete the coordination process. REJ (REJECTION) The System uses the REJ message to reject a clearance proposed by a CDN to a previously coordinated flight and terminate the coordination dialogue. After a receiving a REJ message, the System leaves the clearance as was previously agreed. TOC (TRANSFER OF CONTROL) The System uses the TOC message to offer the receiving centre executive control of a flight. The following diagram depicts the possible flight state transitions within the System upon reception of AIDC coordination messages.



Page F-202



CDN

ABI CPL

ABI

Pre-Notifying

Notifying

Negotiating

MAC EST PAC ACP

Coordinating MAC ACP CDN CDN

Transferred

Transferring AOC

Coordinated

Re-negotiating

TOC ACP

REJ

ACP CDN

LEGEND

REJ

Backward Re-negotiating

MSG

MSG transmitted by the controlling ATS unit

MSG

MSG transmitted by the downstream ATS unit

CDN MSG

MSG transmitted by either the controlling or the downstream ATS unit

Figure F-1:

Transitions of AIDC coordination messages

The system implements an AIDC messages management policy. AIDC messages is identified for the system by a unique identification The system defines three different priorities for AIDC messages; Emergency, Urgent and Normal. AIDC messages are processed taking into account its priority as first criteria and its reception time as second criteria. Surveillance data transfer messages is classified as Urgent. The System defines two different kind of AIDC messages depending if either they need response or not. Furthermore, messages that need response, is classified in response messages and messages waiting for response. The System provides the possibility to filter AIDC messages that fulfil previous conditions. If an AIDC message belongs to an arranged group of AIDC messages, it includes the identification of previous and next message as well as the source of referenced message. All data transferred is controlled by Surveillance messages. The System supports abbreviated AIDC dialogue. The System supports up to 15 different AIDC dialogues. AIDC workstation keeps all messages sent or received. Operators will have the possibility to check this historical information. 1st Phase: Notification Upstream sector



Page F-203



An adapted time before COP, the Upstream sector sends an ABI message (not a mandatory action) to notify the Downstream sector of the coming coordination. The controller may also initiate a semi-automatic notification phase. If the controller starts a SEND ABI command, the Upstream sector sends an ABI message to notify the Downstream sector. The System sends revised ABI messages if changes affecting notification data take place. In either case, if an ACP message is received in return, the “Status” field displays “ABI RCV” (ABI received) for the corresponding flight in the Flight Plan list. If after an adapted timeout the ACP message is not received, the “Status” field displays “ABI TO” (ABI ACP time-out) for the corresponding flight plan. The System sends a MAC message to indicate to the Downsector sector that the notification previously effected for a flight is being abrogated. If an ACP message is received in return, the “Status” field displays “MAC RCV” (MAC received) for the corresponding flight in the Flight Plan list. If after an adapted timeout the ACP message is not received, the “Status” field displays “MAC TO” (MAC ACP time-out) for the corresponding flight plan. The System sends a PAC message to initiate a notification and pre-departure coordination with the Downstream sector, when the time of flight (from departure to the COP) is less than that which would be required to comply with the activation message transmission time parameters. If an ACP message is received in return, the “Status” field displays “PAC RCV” (PAC received) for the corresponding flight in the Flight Plan list. If after an adapted timeout the ACP message is not received, the “Status” field displays “PAC TO” (PAC ACP time-out) for the corresponding flight plan. Downstream sector If received messages are correct, the Downstream sector sends back an ACP message to the Upstream sector. If the ABI or PAC messages contain errors, the Downstream sector sends them to the FPM queue. The corresponding operator may retrieve these messages from the FPM queue to edit them. If messages are corrected, they are reprocessed as if newly arrived. If a MAC message contains errors, the Downstream sector is notified by means of a system error message. Upon receiving a MAC message, the FP Status is reverted to INITIAL. The Downstream sector updates its flight plans with the data extracted from these messages. Upon PAC reception, the FP Status at the Downstream sector changes to ACTIVE. 2nd Phase: Coordination Upstream sector An adapted time before COP, the Upstream sector sends an EST message (this is a mandatory action for the coordination process) to initiate coordination with the Downstream sector. If an ACP message is received in return, the “Status” field displays “EST RCV” for the corresponding flight in the Flight Plan list.



Page F-204



If after an adapted timeout the ACP message is not received, the “Status” field displays “EST TO” (EST ACP time-out) for the corresponding flight plan. In any case, the Upstream controller may manually coordinate with the Downstream controller. Then upon clicking COORD-UPDATE in the FP Template, the “Status” field displays “MAN” (Manual) for the corresponding flight plan, to indicate that manual coordination has taken place. Either automatically or upon controller command, the Upstream sector sends a CDN message to modify coordination data with the Downstream sector. If an ACP message is received in return, the “Status” field displays “CDN ACP” (REV accepted) for the corresponding flight in the Flight Plan list. If a REJ message is received in return, the “Status” field displays “CDN REJ” (REV rejected) for the corresponding flight in the Flight Plan list. In this case, the Upstream controller may initiate a verbal revision with the Downstream controller. Then upon clicking COORD-UPDATE in the FP Template, the “Status” field displays “MAN” (Manual) for the corresponding flight plan, to indicate that manual coordination revision has taken place. The System sends a MAC message to indicate to the Downstream sector that the coordination previously effected for a flight is being abrogated. If an ACP message is received in return, the “Status” field displays “MAC RCV” (MAC received) for the corresponding flight in the Flight Plan list. If after an adapted timeout the ACP message is not received, the “Status” field displays “MAC TO” (MAC ACP time-out) for the corresponding flight plan. Downstream sector If messages are correct, the Downstream sector sends back an ACP message to the Upstream sector. If messages contain errors, the Downstream sector sends them to the FPM queue. The corresponding user may retrieve messages from the FPM queue for editing and correction. If messages are corrected, they are then re-submitted to the System for processing as if newly arrived. The Downstream sector updates its flight plans with the data extracted from these messages. Upon coordination initiation (with an EST message), the FP Status at the Downstream sector changes to ACTIVE. If the flight plan does not exist, its data is kept in the FPM queue, the icon of which becomes RED. The System automatically creates a minimal flight plan. If a MAC message contains errors, the Downstream sector is notified by means of a system error message. Upon receiving a MAC message, the FP Status is reverted to NOTIFIED. If a MAC message is received for an assumed flight, it is not updated. 3rd Phase: Transfer The System provides the capacity to initiate the transfer phase with the Upperstream sector automatically or manually sending a TOC message. The Downstream is capable of accepting the transfer by sending an AOC message. Both parties has the capability of initiating a backward re-negotiation by sending CDN messages, which may be accepted (ACP) or rejected (REJ).



Page F-205


F.3


Local Functions Error Messages List

MESSAGES Compulsory

Syntactic



Page F-206



Rank error

Unknown element



Page F-207



Element not accessible

Incoherence



Page F-208



Discontinuity

FIR time not computable



Page F-209



External point expected

New FP Keywords in Use



Page F-210



RFL doesn‟t fit with airway

Too many points



Page F-211



Extraction error

Already in use



Page F-212



Flight plan already exists

Inaccessible FP



Page F-213



Different shape to adapted



Page F-214



Line is offline

None found



Page F-215



No response

Restricted Area Warning



Page F-216



CSSR Not Assignable

Keyword Fields not Matching



Page F-217



No data available

No FPs for this filter

F.4 1.

Coordination Messages Windows ABI (Advanced Boundary Information)



Page F-218



a. ABI Received

2.

ACP (Accept message)

3.

CDN (Coordination message)



Page F-219


4.

ACT (Activation Message)

5.

AIDC (Air Traffic Services Interfacility Data Communications)

6.

ARR (Arrival Message)




Page F-220


7.

CHG (Change Message)

8.

CNL (Cancellation Message)




Page F-221


9.

CPL Correction (Current Flight Plan)

10.

DEP (Departure Message/List)

11.

DES (Data Exchange System)




Page F-222


12.

DLA (ATS Message indicator for delay)

13.

EST (Estimated)

14.

FLS (Flight Suspension Message)

15.

LAM (Logical Acknowledgement Message)




Page F-223


16.

LRM (Logical Rejection Message)

17.

MAC (Message for the Abrogation of Coordination)

18.

NOTAMC (Notice To Airmen Cancellation)




Page F-224


19.

NOTAMN (Notice To Airmen N)

20.

NOTAMR (Notice To Airmen R)




Page F-225


21.

PFL (Planned Flight Level)

22.

REJ (Rejection Message)

23.

REV (Revision Message)

24.

SVC (Service)




Page F-226


25.


SVC RFP (Service for Repetitive Flight Plans)



Page F-227



This page is left intentionally blank This is the last page of this document



Page F-228

0029200000000MA04_2-0_FDD-UM

Recommend Documents