Flight Data Display User Manual (FDD-UM).pdf

PRELIMINARY COPY

FOR TRAINING PURPOSE ONLY

FDD-UM

Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey

Indra Sistemas S.A. ▪ Ctra. de Loeches, 9 ▪ 28850 Torrejón de Ardoz ▪ Madrid ▪ Tlf. (+34) 916268197 ▪ Fax (+34) 916268002 Doc.Nº: 0026700000002MA02 Edic./Rev.: A/0 Fecha / Date: 04/05/2010

Flight Data Display User Manual (FDD-UM)

Proyecto / Project: Procurement of the Renovation of Existing Radar and Additional Requirements

Programa / Program: Turkey

Expediente / Contract : 2008/156060 Subtítulo / Subtitle: N/A

INDRA

Nombre Name

Firma Signature

Fecha Date

Cargo Responsibility

Preparado Prepared Carlos Martínez Ramos Enginnering

Revisado Revised Systems

Aprobado Approved

Ana Isabel Moreno Alcántara Quality Manager

Autorizado Authorized Andrés Vizcaíno Martín Programme Director

Los datos e información que aquí se incluyen son propiedad de Indra Sistemas, S.A. Estos datos e información no

pueden ser revelados total ni parcialmente a terceros. Tampoco deben ser copiados total o parcialmente (excepto para ser utilizados dentro de Programa al que pertenecen), ni pueden utilizarse para propósitos distintos a la ejecución del programa para el que han sido proporcionados sin el previo consentimiento por escrito de Indra Sistemas, S.A.

Indra owns the copyright of this document, which is supplied confidentially and must not be used for any purpose other than that for which it is supplied. It must not be reproduced either wholly or partially, copied or transmitted to any person without the authorization of Indra.

PRELIMINARY COPY


FDD-UM


II Doc.Nº: 0026700000002MA02

Edic./Rev.: A/0 Fecha / Date: 04/05/2010

PRELIMINARY COPY


FDD-UM


Doc.Nº: 0026700000002MA02 Edic./Rev.: A/0 Fecha / Date: 04/05/2010

III

REGISTRO DE EDICIONES Y REVISIONES DE PÁGINAS Record of editions and page revisions Este documento contiene las páginas siguientes, en las ediciones y revisiones que se indican: This document contains the following pages in the editions and revisions shown

Capítulo Chapter

Edic./Rev. Edit./Rev.

Capítulo Chapter


Capítulo Chapter


Capítulo Chapter


i-xvii A/0 5 A/0 D A/0 1 A/0 6 A/0 E A/0 2 A/0 A A/0 F A/0 3 A/0 B A/0 4 A/0 C A/0

REGISTRO DE CAMBIOS EN EL DOCUMENTO Document changes record


Fecha Date

Capítulos Chapters

Razón del Cambio Reason for change

A/0 04/05/2010 1-6, A-F New Document

HOJA DE DISTRIBUCIÓN Distribution sheet Nº Copia Copy no.

Empresa / Organismo Company / Organization

Departamento Department

Nombre y Apellidos Name and surname

PRELIMINARY COPY


FDD-UM


IV Doc.Nº: 0026700000002MA02


ÍNDICE GENERAL Table of contents

Capítulo Descripción Página Chapter Description Page

1. INTRODUCTION........................................................................................................................... 1-1

2. PURPOSE ..................................................................................................................................... 2-1

3. SCOPE .......................................................................................................................................... 3-1

3.1 GENERAL SYSTEM DESCRIPTION ..................................................................................................... 3-1

3.2 FLIGHT DATA DISPLAY (FDD) POSITION OVERVIEW ....................................................................... 3-3

3.3 ORGANIZATION OF THIS MANUAL ..................................................................................................... 3-4

3.4 CONVENTIONS USED IN THIS DOCUMENT........................................................................................ 3-5

3.5 SELECTING MENUS, ICONS AND FIELD TEXT ENTERING ............................................................... 3-7

3.5.1 Rules to Enter or Delete Data ......................................................................................................... 3-9

3.6 COMMON ACTIONS IN ALL FDD WINDOWS .................................................................................... 3-10

3.7 PROCEDURES TO CLOSE ACTIONS IN WINDOWS ......................................................................... 3-11

4. DOCUMENTS ............................................................................................................................... 4-1

4.1 APPLICABLE DOCUMENTS ................................................................................................................. 4-1

4.2 REFERENCE DOCUMENTS .................................................................................................................. 4-1

5. DEFINITIONS AND ACRONYMS ................................................................................................ 5-1

5.1 DEFINITIONS ......................................................................................................................................... 5-1

5.2 ACRONYMS ........................................................................................................................................... 5-7

6. FUNCTIONAL AND OPERATIONAL DESCRIPTION ................................................................. 6-1

6.1 FDD GENERAL INFORMATION AREA (GI_A) ..................................................................................... 6-2

6.1.1 “Q” Queue: AFTN-FP Messages Area (FPM)................................................................................. 6-3

6.1.1.1 AFTN-FP Messages Validation ..................................................................................................................... 6-4

6.1.1.2 RVSM Validation ............................................................................................................................................. 6-5

6.1.1.3 AFTN-FP Messages Action Execution ......................................................................................................... 6-6

6.1.1.4 AFTN-FP Messages De-queue (“Q”) ............................................................................................................ 6-6

6.1.1.4.1 AFTN-FP Correction Windows .................................................................................................................. 6-9

6.1.1.4.1.1 AFTN-FP Messages Correction Window .......................................................................................... 6-10

6.1.1.4.1.2 AFTN-FP Text Window ..................................................................................................................... 6-11

6.1.1.4.1.3 Associated FPs List ........................................................................................................................... 6-11

6.1.1.4.1.4 Action: AFTN Message De-queue (FP Messages) ........................................................................... 6-11

6.1.1.4.2 AFTN-NOTAM Messages Correction Window ........................................................................................ 6-12

6.1.2 “AAI” Queue: Erroneous AFTN Header Area (EAH) ................................................................... 6-14

6.1.2.1 “AAI” Messages De-queue .......................................................................................................................... 6-15

PRELIMINARY COPY


FDD-UM



V



6.1.2.1.1 “AAI” Messages Window .......................................................................................................................... 6-16

6.1.2.1.2 “AAI” Error Window .................................................................................................................................. 6-16

6.1.2.1.3 “AAI” Messages Correction Window ........................................................................................................ 6-17

6.1.2.1.4 “AAI” Window ........................................................................................................................................... 6-19

6.1.2.1.4.1 Action: AFTN Messages De-queue (Erroneous AFTN Message Header) ........................................ 6-20

6.1.3 System Time and Date .................................................................................................................. 6-22

6.1.4 FDP Failure .................................................................................................................................... 6-22

6.2 FDD MAIN MENU AREA (MM_A) ........................................................................................................ 6-23

6.2.1 Icon [FP Act.] Actions on Flight Plans ........................................................................................ 6-24

6.2.1.1 FP Operation Window .................................................................................................................................. 6-24

6.2.1.1.1 Flight Plan Status ..................................................................................................................................... 6-24

6.2.1.1.2 Edition Area ............................................................................................................................................. 6-25

6.2.1.1.2.1 Rules for Entering Data ..................................................................................................................... 6-28

6.2.1.1.2.2 “Route” Field Validation Rules ........................................................................................................... 6-29

6.2.1.1.3 Command Area ........................................................................................................................................ 6-31

6.2.1.1.3.1 Action: Common Step to Actions on FPs .......................................................................................... 6-32

6.2.1.1.3.2 Action: Visualize FPL ......................................................................................................................... 6-32

6.2.1.1.3.3 Action: View List of FP Synonyms ..................................................................................................... 6-33

6.2.1.1.3.4 Action: FPL History ............................................................................................................................ 6-33

6.2.1.1.3.5 Action: Create FPL ............................................................................................................................ 6-34

6.2.1.1.3.6 Action: Create a Current FPL (CPL) .................................................................................................. 6-34

6.2.1.1.3.7 Action: Modify FPL ............................................................................................................................ 6-35

6.2.1.1.3.8 Action: Cancel FPL ............................................................................................................................ 6-35

6.2.1.1.3.9 Action: Status Change from “Passive” to “Notified” ........................................................................... 6-36

6.2.1.1.3.10 Action: Status Change from “Notified” to “Passive” ........................................................................... 6-36

6.2.1.1.3.11 Action: Confirm/Modify ATD .............................................................................................................. 6-37

6.2.1.1.3.12 Action: Cancel ATD ........................................................................................................................... 6-38

6.2.1.1.3.13 Action: Estimate Actions .................................................................................................................... 6-38

6.2.1.1.3.14 Action: Passing over Fixpoint ............................................................................................................ 6-39

6.2.1.1.3.15 Action: Confirm/Modify ATA .............................................................................................................. 6-40

6.2.1.1.3.16 Action: Request Flight Plan Strips Printing ........................................................................................ 6-40

6.2.1.1.3.17 Action: FP Route Modification ........................................................................................................... 6-41

6.2.1.1.4 Error Message Area ................................................................................................................................. 6-41

6.2.1.1.5 List of Synonyms ...................................................................................................................................... 6-42

PRELIMINARY COPY


FDD-UM


VI Doc.Nº: 0026700000002MA02




6.2.1.1.6 Area Warnings Window ........................................................................................................................... 6-42

6.2.2 Icon [FP Rtr.] Actions on Retrieved FP ........................................................................................ 6-44

6.2.2.1 FP Retrieval Window .................................................................................................................................... 6-44

6.2.2.1.1 Edition Area ............................................................................................................................................. 6-45

6.2.2.1.2 Command Area ........................................................................................................................................ 6-45

6.2.2.1.2.1 Action: Retrieve Multiple FPL ............................................................................................................ 6-46


6.2.2.1.4 Retrieved Flight Plan(s) Window ............................................................................................................. 6-47

6.2.3 Icon [FP MIN.] Minimal Flight Plan ............................................................................................... 6-49

6.2.3.1 Minimal FP Window ..................................................................................................................................... 6-49

6.2.3.1.1 Edition Area ............................................................................................................................................. 6-49

6.2.3.1.2 Command Area ........................................................................................................................................ 6-50

6.2.3.1.2.1 Action: Create a Minimal FP .............................................................................................................. 6-50


6.2.4 Icon [RPL Act.] Actions on Repetitive Flight Plan ...................................................................... 6-51

6.2.4.1 RPL Operation Window ............................................................................................................................... 6-51

6.2.4.1.1 Edition/Activation Area ............................................................................................................................. 6-51

6.2.4.1.2 Command Area ........................................................................................................................................ 6-53

6.2.4.1.2.1 Action: Common Steps in Actions on RPLs ...................................................................................... 6-53

6.2.4.1.2.2 Action: Visualize RPL ........................................................................................................................ 6-53

6.2.4.1.2.3 Action: Create RPL ............................................................................................................................ 6-54

6.2.4.1.2.4 Action: Modify RPL ............................................................................................................................ 6-54

6.2.4.1.2.5 Action: Cancel RPL ........................................................................................................................... 6-55


6.2.5 Icon [RPL Rtr.] Repetitive Flight Plans Retrieval ........................................................................ 6-56

6.2.5.1 RPLs Retrieval Window ............................................................................................................................... 6-56

6.2.5.1.1 Edition/Activation Area ............................................................................................................................. 6-57

6.2.5.1.2 Command Area ........................................................................................................................................ 6-57

6.2.5.1.2.1 Action: Retrieve Multiple RPLs .......................................................................................................... 6-58


6.2.5.2 Retrieved RPLs Window .............................................................................................................................. 6-59

6.2.6 Icon [Runw] Airport Runways Actions ........................................................................................ 6-60

6.2.6.1 Airport Runways Window ............................................................................................................................ 6-60

6.2.6.1.1 Edition Area ............................................................................................................................................. 6-60

PRELIMINARY COPY


FDD-UM



VII



6.2.6.1.2 Command Area ........................................................................................................................................ 6-61

6.2.6.1.2.1 Action: Visualization of Airport Runways ........................................................................................... 6-61

6.2.6.1.2.2 Action: Modify Airport Runways ......................................................................................................... 6-61


6.2.7 Icon [AFTN TX] AFTN Transmission ............................................................................................ 6-62

6.2.7.1 ICAO AFTN Transmission Window ............................................................................................................. 6-62

6.2.7.1.1 Edition Area ............................................................................................................................................. 6-62

6.2.7.1.2 Command Area ........................................................................................................................................ 6-68

6.2.7.1.2.1 Action: Edit/Transmit ICAO AFTN Messages .................................................................................... 6-68


6.2.7.2 ICAO ADEXP Transmission Window .......................................................................................................... 6-70

6.2.7.2.1 Edition Area ............................................................................................................................................. 6-70

6.2.7.2.2 Command Area ........................................................................................................................................ 6-75

6.2.7.2.2.1 Action: Edit/Transmit ICAO ADEXP Messages ................................................................................. 6-75


6.2.7.3 Free AFTN Transmission Window .............................................................................................................. 6-77

6.2.7.3.1 Edition Area ............................................................................................................................................. 6-78

6.2.7.3.2 Command Area ........................................................................................................................................ 6-78

6.2.7.3.2.1 Action: Edit/Transmit Text AFTN Messages ...................................................................................... 6-79


6.2.7.4 SVC Transmission Window ......................................................................................................................... 6-80

6.2.7.4.1 Edition Area ............................................................................................................................................. 6-81

6.2.7.4.2 Command Area ........................................................................................................................................ 6-81

6.2.7.4.2.1 Action: Transmit SVC Messages ....................................................................................................... 6-82

6.2.8 Icon [ARCHIVE] AFTN Messages Retrieval ................................................................................. 6-83

6.2.8.1 AFTN Retrieve Window ................................................................................................................................ 6-83

6.2.8.1.1 Edition Area ............................................................................................................................................. 6-84

6.2.8.1.2 Command Area ........................................................................................................................................ 6-84

6.2.8.1.2.1 Action: Retrieve Multiple AFTN Messages ........................................................................................ 6-85


6.2.8.2 Retrieve Multiple AFTN Window ................................................................................................................. 6-87

6.2.8.3 AFTN Element Window ................................................................................................................................ 6-87

6.2.8.3.1 Edition Area ............................................................................................................................................. 6-88


6.2.8.3.3 Command Area ........................................................................................................................................ 6-89

PRELIMINARY COPY


FDD-UM


VIII Doc.Nº: 0026700000002MA02




6.2.8.4 OLDI Retrieve Window ................................................................................................................................. 6-90

6.2.8.4.1 Edition Area ............................................................................................................................................. 6-90


6.2.8.4.3 Command Area ........................................................................................................................................ 6-91

6.2.9 Icon [A.P.] Airport Pressure ......................................................................................................... 6-92

6.2.9.1 Airport Pressure Window ............................................................................................................................ 6-92

6.2.9.1.1 Element List Area .................................................................................................................................... 6-92

6.2.9.1.2 Edition Area ............................................................................................................................................. 6-92

6.2.9.1.3 Command Area ........................................................................................................................................ 6-93

6.2.9.1.3.1 Action: QNH and Transition Level Visualization ................................................................................ 6-93

6.2.9.1.3.2 Action: Modify QNH and Transition level ........................................................................................... 6-94


6.2.10 Icon [WINDS] Wind Data ............................................................................................................... 6-95

6.2.10.1 Winds Data Window ..................................................................................................................................... 6-95

6.2.10.1.1 Edition Area ............................................................................................................................................. 6-95

6.2.10.1.2 Command Area ........................................................................................................................................ 6-96

6.2.10.1.2.1 Action: Visualization of Wind Data .................................................................................................... 6-96

6.2.10.1.2.2 Action: Modify Wind Data .................................................................................................................. 6-97


6.2.11 Icon [AREAS] Restricted Areas .................................................................................................... 6-98

6.2.11.1 Restricted Areas Window ............................................................................................................................ 6-98

6.2.11.1.1 Element List Area .................................................................................................................................... 6-99

6.2.11.1.2 Description Area .................................................................................................................................... 6-100

6.2.11.1.3 Activation/Validity Area .......................................................................................................................... 6-101

6.2.11.1.4 Layout Area ........................................................................................................................................... 6-103

6.2.11.1.5 Command Area ...................................................................................................................................... 6-104

6.2.11.1.5.1 Action: Common Step to Restricted Areas Operations ................................................................... 6-104

6.2.11.1.5.2 Action: Create Restricted Area ........................................................................................................ 6-105

6.2.11.1.5.3 Action: Modify Restricted Area ........................................................................................................ 6-106

6.2.11.1.5.4 Action: Cancel Restricted Area ....................................................................................................... 6-106

6.2.11.1.6 Error Message Area ............................................................................................................................... 6-106

6.2.12 Icon [FLOW] Air Traffic Flow ...................................................................................................... 6-107

6.2.12.1 Flow FP Window ......................................................................................................................................... 6-107

6.2.12.1.1 Filters Edition Area ................................................................................................................................ 6-109

PRELIMINARY COPY


FDD-UM



IX



6.2.12.1.2 Command Area ...................................................................................................................................... 6-109

6.2.12.1.2.1 Action: FPLs Flow ............................................................................................................................ 6-109

6.2.12.2 FPs Traffic Flow List .................................................................................................................................. 6-113

6.2.12.2.1 Command Area ...................................................................................................................................... 6-117

6.2.12.3 FPs Traffic Congestion List ....................................................................................................................... 6-118

6.2.13 Icon [METEO MSG] Meteorological Data ................................................................................... 6-120

6.2.13.1 Meteorological Information Window ........................................................................................................ 6-122

6.2.13.1.1 Selected Message ................................................................................................................................. 6-122

6.2.13.1.2 Airport Selection ..................................................................................................................................... 6-122

6.2.13.1.3 Edition Area ........................................................................................................................................... 6-122

6.2.13.1.4 Command Area ...................................................................................................................................... 6-123

6.2.13.1.4.1 Action: Edit Meteorological Page ..................................................................................................... 6-123

6.2.14 [NOTAM] Icon .............................................................................................................................. 6-124

6.2.14.1 NOTAM Operation/Retrieval Window ....................................................................................................... 6-124

6.2.14.2 Edition Area ................................................................................................................................................ 6-125

6.2.14.3 Command Area ........................................................................................................................................... 6-127

6.2.14.3.1 Action: Common Action to NOTAM Procedures .................................................................................... 6-127

6.2.14.3.2 Action: Create a New NOTAM ............................................................................................................... 6-128

6.2.14.3.3 Action: Modify NOTAM .......................................................................................................................... 6-129

6.2.14.3.4 Action: Cancel NOTAM .......................................................................................................................... 6-130

6.2.14.3.5 Action: Retrieve Multiple NOTAM .......................................................................................................... 6-131

6.2.14.4 Error Message Area ................................................................................................................................... 6-131

6.2.15 Icon [T. Flow] Traffic Flow .......................................................................................................... 6-132

6.2.15.1 FP Flow Actions Window ........................................................................................................................... 6-132

6.2.15.1.1 Edition Area ........................................................................................................................................... 6-133

6.2.15.1.2 Command Area ...................................................................................................................................... 6-133

6.2.15.1.2.1 Action: Allocate FP to an Element (Fix Point) .................................................................................. 6-134

6.2.15.1.2.2 Action: Exchange the FP Distribution .............................................................................................. 6-135

6.2.15.1.2.3 Action: Cancel an FP Distribution .................................................................................................... 6-136

6.2.15.2 Flow Restrictions Window ......................................................................................................................... 6-136

6.2.15.2.1 Edition Area ........................................................................................................................................... 6-137

6.2.15.2.2 Command Area ...................................................................................................................................... 6-137

6.2.15.2.2.1 Action: Slot Visualization ................................................................................................................. 6-138

6.2.15.2.2.2 Action: Slot Creation ........................................................................................................................ 6-139

PRELIMINARY COPY


FDD-UM


X Doc.Nº: 0026700000002MA02




6.2.15.2.2.3 Action: Slots Modifying .................................................................................................................... 6-140

6.2.15.2.2.4 Action: Cancel Slots ........................................................................................................................ 6-141

6.2.15.3 Retrieve FP’s Flow Window ...................................................................................................................... 6-142

6.2.15.3.1 Edition Area ........................................................................................................................................... 6-142

6.2.15.3.2 Command Area ...................................................................................................................................... 6-142

6.2.15.3.3 Retrieved FPs List ................................................................................................................................. 6-143

6.2.15.3.3.1 Action: FPs Distribution Multiple Recovery ..................................................................................... 6-143

6.2.15.4 Retrieve Slots Flow Window ..................................................................................................................... 6-144

6.2.15.4.1 Edition Area ........................................................................................................................................... 6-145

6.2.15.4.2 Command Area ...................................................................................................................................... 6-146

6.2.15.4.3 Retrieved Slots List ................................................................................................................................ 6-147

6.2.15.4.3.1 Action: Retrieve Multiple Slots Distribution ...................................................................................... 6-147

6.2.16 Icon [LINES] AFTN Lines Status ................................................................................................ 6-150

6.2.17 [PIP] Icon ...................................................................................................................................... 6-151

6.2.17.1 PIP Window ................................................................................................................................................. 6-151

6.2.17.1.1 Command Area ...................................................................................................................................... 6-151

6.2.18 Icon [EST] Estimate ..................................................................................................................... 6-152

6.2.18.1 EST Window ............................................................................................................................................... 6-152

6.2.18.1.1 Edition Area ........................................................................................................................................... 6-153

6.2.18.1.2 Command Area ...................................................................................................................................... 6-153

6.2.18.1.2.1 Action: Quick Estimate Procedure ................................................................................................... 6-153

6.2.19 [PRINTER1] .................................................................................................................................. 6-155

6.2.20 [LOGOUT] Icon ............................................................................................................................ 6-156

6.2.20.1 Freeze Position ........................................................................................................................................... 6-156

A. FP ROUTE .................................................................................................................................... A-2

A.1 DEFINITIONS ........................................................................................................................................ A-2

A.2 PRESENTATION OF OBTAINED ROUTES WHEN FP ANALYZING .................................................. A-2

A.3 ROUTE FIELD ANALYSIS .................................................................................................................... A-3

B. ERRORS DISPLAY ...................................................................................................................... B-2

C. ROUTE FIELD MESSAGES ......................................................................................................... C-2

D. ERROR MESSAGE OF ROUTE FIELD ....................................................................................... D-2

D.1 INCORRECT EDITION .......................................................................................................................... D-2

PRELIMINARY COPY


FDD-UM



XI



D.2 UNKNOWN ELEMENT ...........................................................................................................................D-2

D.3 FIELDS INCOHERENCE ........................................................................................................................D-2

D.4 DISCONTINUITY ....................................................................................................................................D-3

D.5 VALIDATE BOUNDARY POINT ............................................................................................................D-3

E. LOCAL FUNCTIONS ERROR MESSAGES ................................................................................ E-2

F. COORDINATION MESSAGES .................................................................................................... F-2

F.1 RECEPTION AND PROCESSING OF COORDINATION MESSAGES ................................................. F-2

F.2 ONLINE DATA INTERCHANGE (OLDI) COORDINATION ................................................................... F-3

F.3 AIDC COORDINATION MESSAGES ..................................................................................................... F-6

F.4 COORDINATION MESSAGES WINDOWS ......................................................................................... F-11

No se encontraron elementos de tabla de contenido.

PRELIMINARY COPY


FDD-UM


XII Doc.Nº: 0026700000002MA02


ÍNDICE FIGURAS Figures index

Descripción Página Description Page

Figure 3.1-1. System Architecture ......................................................................................................................... 3-2

Figure 3.4-1. Operative Description Example ........................................................................................................ 3-6

Figure 3.4-2. Conventions Used in this Document ................................................................................................ 3-7

Figure 3.5.1-1. FP Action Window. Error detection ............................................................................................... 3-9

Figure 6-1. FDD Screen ........................................................................................................................................ 6-1

Figure 6.1-1. FDD General Information Area (GI_A) ............................................................................................. 6-2

Figure 6.1.1-1. AFTN-FP Messages Area ............................................................................................................. 6-3

Figure 6.1.1.4-1. AFTN-FP Messages Window (“Q”) ............................................................................................ 6-7

Figure 6.1.1.4.1-1. AFTN-FP Correction Windows ................................................................................................ 6-9

Figure 6.1.1.4.1.1-1. AFTN-FP Message Correction Window. Error ................................................................... 6-10

Figure 6.1.1.4.2-1. AFTN-NOTAM Messages Correction Window ...................................................................... 6-13

Figure 6.1.2-1. “AAI” Queue ................................................................................................................................ 6-14

Figure 6.1.2.1.1-1. “AAI” Messages Window ....................................................................................................... 6-16

Figure 6.1.2.1.2-1. “AAI” Error Window ............................................................................................................... 6-16

Figure 6.1.2.1.3-1. “AAI” Messages Correction Window ..................................................................................... 6-17

Figure 6.1.2.1.4-1. “AAI” Window ........................................................................................................................ 6-19

Figure 6.1.3-1. System Time and Date ............................................................................................................... 6-22

Figure 6.1.4-1. FDP down ................................................................................................................................... 6-22

Figure 6.2-1. Main Menu Area (MM_A) ............................................................................................................... 6-23

Figure 6.2.1-1. [FP Act.] Icon .............................................................................................................................. 6-24

Figure 6.2.1.1-1. FP Operation Window .............................................................................................................. 6-24

Figure 6.2.1.1.2.1-1. FP Operation Window: Error Detection .............................................................................. 6-29

Figure 6.2.1.1.2.2-1. Entry Error Detection in “Route” Field ................................................................................ 6-30

Figure 6.2.1.1.3.3-1. List of Synonyms Window .................................................................................................. 6-33

Figure 6.2.1.1.5-1. List of Synonyms ................................................................................................................... 6-42

Figure 6.2.1.1.6-1. Area Warnings Window ......................................................................................................... 6-43

Figure 6.2.2-1. [FP Rtr.] Icon ............................................................................................................................... 6-44

Figure 6.2.2.1-1. FP Retrieval Window ............................................................................................................... 6-44

Figure 6.2.2.1.4-1. Retrieved FP Window. List Elements .................................................................................... 6-47

Figure 6.2.3-1. [FP Min.] Icon .............................................................................................................................. 6-49

Figure 6.2.3.1-1. Minimal FP Window ................................................................................................................. 6-49

Figure 6.2.4-1. [RPL Act.] Icon ............................................................................................................................ 6-51

PRELIMINARY COPY


FDD-UM



XIII


Descripción Página Description Page Figure 6.2.4.1-1. RPL Operation Window ........................................................................................................... 6-51

Figure 6.2.5-1. [RPL Rtr.] Icon ............................................................................................................................ 6-56

Figure 6.2.5.1-1. RPLs Retrieval Windows ......................................................................................................... 6-56

Figure 6.2.6-1. [Runw] Icon ................................................................................................................................. 6-60

Figure 6.2.6.1-1. Airport Runways Window ......................................................................................................... 6-60

Figure 6.2.7-1. [AFTN TX] Icon ........................................................................................................................... 6-62

Figure 6.2.7.1-1. ICAO AFTN Transmission Window .......................................................................................... 6-62

Figure 6.2.7.2-1. ICAO ADEXP Transmission Window ....................................................................................... 6-70

Figure 6.2.7.3-1. Free AFTN Transmission Window ........................................................................................... 6-77

Figure 6.2.7.4-1. SVC Transmission Window ..................................................................................................... 6-81

Figure 6.2.8-1. [ARCHIVE] Icon .......................................................................................................................... 6-83

Figure 6.2.8.1-1. AFTN Retrieve Window ........................................................................................................... 6-83

Figure 6.2.8.2-1. Retrieve Multiple AFTN Window .............................................................................................. 6-87

Figure 6.2.8.3-1. AFTN Element Window ........................................................................................................... 6-88

Figure 6.2.9-1. [A.P.] Icon ................................................................................................................................... 6-92

Figure 6.2.9.1-1. Airport Pressure Window ......................................................................................................... 6-92

Figure 6.2.10-1. [WINDS] Icon ............................................................................................................................ 6-95

Figure 6.2.10.1-1. Winds Data Window .............................................................................................................. 6-95

Figure 6.2.11-1. [AREAS] Icon ............................................................................................................................ 6-98

Figure 6.2.11.1-1. Restricted Areas Window ...................................................................................................... 6-99

Figure 6.2.11.1.1-1. Restricted Areas Window. Element List Area ................................................................... 6-100

Figure 6.2.11.1.2-1. Restricted Areas Window. Description Area ..................................................................... 6-100

Figure 6.2.11.1.3-1. Restricted Areas Window. Activation/Validity Area ........................................................... 6-101

Figure 6.2.11.1.4-1. Restricted Areas Window. Layout Area ............................................................................ 6-103

Figure 6.2.11.1.5-1. Restricted Areas Window. Command Area ...................................................................... 6-104

Figure 6.2.12-1. [FLOW] Icon............................................................................................................................ 6-107

Figure 6.2.12-2. FPs Traffic Flow Options ........................................................................................................ 6-107

Figure 6.2.12.1-1. Flow FP Window .................................................................................................................. 6-108

Figure 6.2.12.2-1. FP Found for the given filter................................................................................................. 6-113



Figure 6.2.12.2.1-1. FP Operation Window from Flow List ............................................................................... 6-117

PRELIMINARY COPY


FDD-UM


XIV Doc.Nº: 0026700000002MA02



Descripción Página Description Page Figure 6.2.12.3-1. FPs Traffic Congestion List Graphic .................................................................................... 6-118

Figure 6.2.13-1. [METEO MSG] Icon ................................................................................................................ 6-120

Figure 6.2.13.1-1. Meteorological Information Window ..................................................................................... 6-122

Figure 6.2.14-1. [NOTAM] Icon ......................................................................................................................... 6-124

Figure 6.2.14.1-1. NOTAM Operation/Retrieval Window .................................................................................. 6-125

Figure 6.2.15-1. [T. Flow] icon ........................................................................................................................... 6-132

Figure 6.2.15-2. [T. Flow] icon. (Retrieve) Option ............................................................................................. 6-132

Figure 6.2.15.1-1. FP Flow Actions Window ..................................................................................................... 6-133

Figure 6.2.15.2-1. Flow Restrictions Window .................................................................................................... 6-137

Figure 6.2.15.3-1. Retrieve FP’s Flow Window ................................................................................................. 6-142

Figure 6.2.15.4-1. Retrieve Slots Flow Window ................................................................................................ 6-145

Figure 6.2.15.4.1-1. Rest. Slot Frame Window. Elements Window ................................................................... 6-146

Figure 6.2.16-1. [LINES] Icon ............................................................................................................................ 6-150

Figure 6.2.16-2. AFTN Lines Status Window .................................................................................................... 6-150

Figure 6.2.17-1. [PIP] Icon ................................................................................................................................ 6-151

Figure 6.2.17.1-1. PIP Window ......................................................................................................................... 6-151

Figure 6.2.18-1. [EST] Icon ............................................................................................................................... 6-152

Figure 6.2.18-2. EST Window ........................................................................................................................... 6-152

Figure 6.2.18.1-1. EST Window ........................................................................................................................ 6-152

Figure 6.2.19-1. Printer Selection ...................................................................................................................... 6-155

Figure 6.2.20-1. [LOGOUT] Icon ....................................................................................................................... 6-156

Figure 6.2.20-2. Login Window ......................................................................................................................... 6-156

Figure F.3-1. Transitions of AIDC coordination messages .................................................................................... F-8

ÍNDICE TABLAS Tables index

Descripción Página Description Page

Table 3.5-1. Mouse Button Functions ................................................................................................................... 3-7

Table 3.5-2. Key Functions ................................................................................................................................... 3-9

PRELIMINARY COPY


FDD-UM



XV


Descripción Página Description Page Table 6.1-1. General Information Area (GI_A). Elements ..................................................................................... 6-2

Table 6.1.1.4-1. AFTN-FP Messages Window (“Q”). Filters ................................................................................. 6-8

Table 6.1.1.4.1.1-1. AFTN-FP Messages Correction Window. Command Area ................................................. 6-10

Table 6.1.1.4.1.2-1. AFTN-FP Text Window. Command Area ............................................................................ 6-11

Table 6.1.1.4.2-1. AFTN-NOTAM Messages Correction Window. Command Area ............................................ 6-14

Table 6.1.2.1.3-1. “AAI” Messages Correction Window. Command Area ........................................................... 6-18

Table 6.1.2.1.4-1. “AAI” Window. Command Area .............................................................................................. 6-19

Table 6.1.3-1. System Time and Date. Items Description ................................................................................... 6-22

Table 6.2-1. FDD Main Menu Area. Commands Icon Row ................................................................................. 6-23

Table 6.2.1.1.2-1. FP Operation Window. Edition Area ...................................................................................... 6-25

Table 6.2.1.1.3-1. FP Operation Window (action mode). Command Area .......................................................... 6-31

Table 6.2.1.1.6-1. Area Warnings Window ......................................................................................................... 6-43

Table 6.2.2.1.1-1. FP Retrieval Window. Edition Area ........................................................................................ 6-45

Table 6.2.2.1.4-1. Retrieved Flight Plan(s) Window. List Element ...................................................................... 6-48

Table 6.2.3.1.1-1. Minimal FP Window. Edition Area .......................................................................................... 6-49

Table 6.2.3.1.2-1. Minimal FP Window. Command Area .................................................................................... 6-50

Table 6.2.4.1.1-1. RPL Operation Window. Edition/Activation Area.................................................................... 6-52

Table 6.2.4.1.2-1. RPL Operation Window. Command Area .............................................................................. 6-53

Table 6.2.5.1.2-1. RPLs Retrieval Window. Command Area .............................................................................. 6-57

Table 6.2.5.2-1. Retrieved RPLs Window. List Element ..................................................................................... 6-59

Table 6.2.6.1.1-1. Airport Runways Window. Edition Area ................................................................................. 6-60

Table 6.2.6.1.2-1. Airport Runways Window. Command Area ............................................................................ 6-61

Table 6.2.7.1.1-1. ICAO AFTN Transmission Window. Edition Area .................................................................. 6-63

Table 6.2.7.1.2-1. ICAO AFTN Transmission Window. Command Area ............................................................. 6-68

Table 6.2.7.2.1-1. ICAO ADEXP Transmission Window. Edition Area ................................................................ 6-70

Table 6.2.7.2.2-1. ICAO AFTN Transmission Window. Command Area ............................................................. 6-75

Table 6.2.7.3.1-1. Free AFTN Transmission Window. Edition Area .................................................................... 6-78

Table 6.2.7.3.2-1. Free AFTN Transmission Window. Command Area .............................................................. 6-78

Table 6.2.7.4.1-1. SVC Transmission Window. Edition Area .............................................................................. 6-81

Table 6.2.7.4.2-1. SVC Transmission Window. Command Area......................................................................... 6-81

Table 6.2.8.1.1-1. AFTN Retrieve Window. Edition Area .................................................................................... 6-84

Table 6.2.8.1.2-1. AFTN Retrieve Window. Command Area .............................................................................. 6-84

PRELIMINARY COPY


FDD-UM


XVI Doc.Nº: 0026700000002MA02



Descripción Página Description Page Table 6.2.8.3.1-1. AFTN Element Window. Edition Area .................................................................................... 6-88

Table 6.2.8.3.3-1. AFTN Element Window. Command Area ............................................................................... 6-89

Table 6.2.8.4.1-1. OLDI Retrieve Window. Edition Area ..................................................................................... 6-90

Table 6.2.8.4.3-1. AFTN Element Window. Command Area ............................................................................... 6-91

Table 6.2.9.1.2-1. Airport Pressure Window. Edition Area .................................................................................. 6-93

Table 6.2.9.1.3-1. Airport Pressure Window. Command Area ............................................................................. 6-93

Table 6.2.10.1.1-1. Winds Data Window. Edition Area ....................................................................................... 6-96

Table 6.2.10.1.2-1. Winds Data Window. Command Area .................................................................................. 6-96

Table 6.2.11.1.1-1. Restricted Areas Window. Element List Area ..................................................................... 6-100

Table 6.2.11.1.2-1. Restricted Areas Window. Description Area ....................................................................... 6-101

Table 6.2.11.1.3-1. Restricted Areas Window. Activation/Validity Area ............................................................ 6-101

Table 6.2.11.1.4-1. Restricted Areas Window. Layout Area .............................................................................. 6-103

Table 6.2.11.1.5-1. Restricted Areas Window. Command Area ........................................................................ 6-104

Table 6.2.12.1.1-1. Flow FP Window. Filters Edition Area ................................................................................ 6-109

Table 6.2.12.1.2-1. Flow FP Window. Command Area ..................................................................................... 6-109

Table 6.2.12.2-1. FPs Traffic Flow List. Aerodrome .......................................................................................... 6-114

Table 6.2.12.2-2. FPs Traffic Flow List. Fix ....................................................................................................... 6-115

Table 6.2.12.2-3. FPs Traffic Flow List. Sector ................................................................................................. 6-116

Table 6.2.12.2.1-1. FPs Traffic Flow List. Command Area ................................................................................ 6-117

Table 6.2.12.3-1. FPs Traffic Congestion List Graphic. Edition Area ................................................................ 6-118

Table 6.2.12.3-2. FPs Traffic Congestion List Graphic. Graphical Area ............................................................ 6-118

Table 6.2.12.3-3. FPs Traffic Congestion List Graphic. Command Area ........................................................... 6-119

Table 6.2.13.1.3-1. Meteorological Information Window. Edition Area .............................................................. 6-122

Table 6.2.13.1.4-1. Meteorological Information Window. Command Area ........................................................ 6-123

Table 6.2.14.2-1. NOTAM Operation/Retrieval Window. Edition Area .............................................................. 6-125

Table 6.2.14.3-1. NOTAM Operation/ Retrieval Window. Command Area ........................................................ 6-127

Table 6.2.15.1.1-1. FP Flow Actions Window. Edition Area .............................................................................. 6-133

Table 6.2.15.1.2-1. FP Flow Actions Window. Command Area ......................................................................... 6-133

Table 6.2.15.2.1-1. Flow Restrictions Window. Edition Area ............................................................................. 6-137

Table 6.2.15.2.2-1. Flow Restrictions Window. Command Area ....................................................................... 6-137

Table 6.2.15.3.2-1. Retrieve FP’s Flow Window. Command Area .................................................................... 6-143

Table 6.2.15.4.2-1. Retrieve Slots Flow Window. Command Area .................................................................... 6-146

PRELIMINARY COPY


FDD-UM



XVII


Descripción Página Description Page Table 6.2.17.1.1-1. PIP Window. Command Area ............................................................................................ 6-151

Table 6.2.18.1.1-1. EST Window. Edition Area ................................................................................................. 6-153

Table 6.2.18.1.2-1. EST Window. Command Area ........................................................................................... 6-153

No se encuentran elementos de tabla de ilustraciones.

PRELIMINARY COPY


PRELIMINARY COPY


FDD-UM



Capítulo / Chapter 1 Página / Page 1 de / of 2

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 strategic planning phase. That is, the controller of this position manages future flight plans (Flight plans received trough AFTN, OLDI and Repetitive Flight Plans (RPL)).

PRELIMINARY COPY


FDD-UM



Doc.Nº: 0026700000002MA02 Edic./Rev.: A/0

Fecha / Date: 04/05/2010

"Página dejada en blanco intencionadamente" "This page intentionally left blank"

PRELIMINARY COPY


FDD-UM




2. PURPOSE

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010


PRELIMINARY COPY


FDD-UM




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

3.1 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 4 UPDATE 4 X86_64.

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

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

Figure 3.1-1. 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).

Main components:

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.

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.

PRELIMINARY COPY


FDD-UM




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

Auxiliary equipment:

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.

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

Simulator environment:

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 (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)

3.2 FLIGHT DATA DISPLAY (FDD) POSITION OVERVIEW

From this unit simulation, exercises are managed.

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

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

Modification

Retrieval

Deletion

RPL handling:

Creation

Visualization

Modification

Retrieval

Deletion

AFTN/OLDI messages handling:

AFTN/OLDI messages reception and correction

AFTN/OLDI 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

3.3 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 Purpose

Chapter 3 Scope

PRELIMINARY COPY


FDD-UM




Chapter 4 Documents

It present the reference document related with this manual.

Chapter 5 Definitions and Acronyms

It presents the glossary of terms used in the manual as well as the abbreviation dictionary.

Chapter 6 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 and OLDI messages handling and Meteorological Data functions.

Appendix A FP Route

The characters string is.

Appendix B Error Display

It present an erroneous elements were detected.

Appendix C Route Field Messange

It present the different “MESSAGE” of the Information Area.

Appendix D Error Message of Route Field

It present the a Morphological error.

Appendix E Local Functions Error Messages

It present the definition of error messages.

Appendix F

3.4 CONVENTIONS USED IN THIS DOCUMENT

Coordination Messages

It present the three-phase process.

“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

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

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

Figure 3.4-1. 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.

PRELIMINARY COPY


FDD-UM




Figure 3.4-2. Conventions Used in this Document

3.5 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:

Table 3.5-1. Mouse Button Functions

Button 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

Left button (LB)

Paste data field Central button (CB)

Without a defined use Right button (RB)

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

Pull-down menus:

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.

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:

Windows: They are displayed by clicking with the mouse LB on the pull-down menu options or directly on icons. The window keeps its display until the operator closes it by means of the [CLOSE] icon or the “X” icon (situated on the upper right corner). The window is composed of following items:

Title, situated at the top of the window, indicates the 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 <Enter> on the keyboard

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:

Icons to validate or cancel the action

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 <Enter> key to validate the input data and to close the pop-up window.

Icons: These are elements, which allow a fast access of certain functions by clicking the corresponding symbol. Usually, when clicking on an icon, a window displays.

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:

PRELIMINARY COPY


FDD-UM




Table 3.5-2. Key Functions

Key Function

Move the cursor position from one field to the following one. <Tab>

Move the cursor position back from one field to the previous one. <Shift> + <Tab>

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

Delete the character after the cursor position (within a field). <Del> (Or <Del>)

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

<Arrows>

3.5.1

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.

Rules to Enter or Delete Data

Figure 3.5.1-1. 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 <Tab> on the keyboard, moves the cursor to the next field. Alternatively, use the input cursor.

Pressing <Shift> + <Tab> on the keyboard, moves the input marker backward to the previous field.

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 <Back Space> in the keyboard after the character is erased. It also is done by double

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

click with the cursor in the data to erase for selecting it, and then enter the new characters.

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

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

Only for resizable windows, which have a resize button in the top right hand corner

Resize window

. For resizing:

Click and keep clicked the resize button with LB.

Drag the frame to the new position.

Drop the LB.

Only for windows with this capacity, transfer between FDD and SDD. With a transfer icon in the top right hand corner

Transfer window

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

Click in bi-state icon. The text colour will turn from WHITE or BACKGROUND colour to YELLOW.

Active

PRELIMINARY COPY


FDD-UM




3.7 PROCEDURES TO CLOSE ACTIONS IN WINDOWS

Date format

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

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

RESULT

1.1. Clicking in [OK] icon

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 [CLOSE] icon The FP Operation Window is closed, validating the action.

2. Closing without validation

2.1. Click in [CLOSE] icon

The FP Operation Window is closed, without validating the action.

3. Data erasing

3.1. [CLEAR] icon

Data entered are erased from FP Operation Window.

3.2. Click in [CLOSE] icon FP Operation Window is closed validating the action.

4. FP print

4.1. Click in [PRINT] icon

The displayed Flight Plan is printed.

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010


PRELIMINARY COPY


FDD-UM




4. DOCUMENTS

4.1 APPLICABLE DOCUMENTS

N/A

4.2 REFERENCE DOCUMENTS

The next table shows all main references from standards, rules and procedures for Air Traffic Management referred in this document.

REFERENCE TITTLE AND CODE ORIGIN

Ref. [1]

DATE

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

ICAO 14th Edition

01/ 11/ 2001

Ref. [2] Originating Region SSR Code Assignment Method

(ORCAM) Improvement Study

EUROCONTROL 1.0

30/09/2004

Ref. [2] EUR REGIONAL AIR NAVIGATION PLAN

Supplement to EUR ANP FASID

ICAO CAL Ed 2

May 2006

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010


PRELIMINARY COPY


FDD-UM




5. DEFINITIONS AND ACRONYMS

5.1 DEFINITIONS

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.

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.

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

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.

Fixpoint Reference point specified either by geographic coordinates (latitude, longitude), a name, or as a distance and bearing from a navigational aid.

Data related to real or foreseen movements of an aircraft, usually displayed in abbreviated or in code

Flight Data

PRELIMINARY COPY


FDD-UM




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.

Level A generic term relating to the vertical position of an aircraft in flight, which indistinctly means, height, altitude, or flight level.

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

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 mono-radar tracks that represent the above referenced aircraft.

• Information previously recorded

Play Back (Reproduction) This process recovers and presents:

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

PRELIMINARY COPY


FDD-UM




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.

It is an action to alter the current existing configuration when changing the allocation of some or all

Sectorization

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

sectors with respect to the working positions.

Short Term Conflict Alert (STCA) It is a predictive function, which involves the monitoring of all aircraft pairs, which are equipped with Mode C transponders. Conflict Alert warns the controller of potential collisions due to airspace violations.

Situation Data Display (SDD) The computer display where Air Traffic Controllers view targets (aircraft) and radar returns.

Special Position Identification (SPI) Feature of aircraft transponder equipment that, when it is enabled, causes the 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 <Take Off> command). A SID connects an airway to an airport and it is defined by a series of fixpoints/level pairs that begin at or near the departure runway and end at or near the airway.

Synthetic Track Type of track generated by the System upon 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.

PRELIMINARY COPY


FDD-UM




Transit Flights passing through the working area (FIR).

Transition Level Altitude at which, or below, the vertical position of an aircraft is controlled by altitudes reference.

Transponder L-band radar receiver/transmitter carried aboard certain aircraft. It transmits a beacon code and Mode C altitude (if so equipped), in response to an interrogation from Secondary Surveillance Radar. The data provided by a transponder can be in any of the following forms: Mode 3/A, Mode 2, or Mode C.

Variable System Parameter (VSP) It is a system parameter, which can be modified on line.

Working Position Terminals group specially built which are included in a single cabinet structure.

5.2 ACRONYMS

Workstation It is the computer and application software. Workstations are grouped together in various combinations to form a working position.

A

AAI FDD Message Queue

ABI Advanced Boundary Information Message (OLDI)

A/C Aircraft

ACC Area/Airspace Control Centre

ACID Aircraft Identification

ACK Acknowledge(ment)

ACP Accept message (OLDI)

ACT Activation Message (OLDI)

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

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

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

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

PRELIMINARY COPY


FDD-UM




CFL Cleared Flight Level

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 Destination Aerodrome

DF Directional Finder

DL Data Link/Downlink

DLA Delay

DLS Data link Service

DRF Data Recording Facility

E

EET Estimated Elapsed Time

ENSI Expected Sorted Number Input

ENSO Expected Sorted Number Output

EOBD Estimated Off-Block Date

EOBT Estimated Off-Block Time

EST Estimate

ETA Estimated Time of Arrival

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

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

I

ICAO International Civil Aviation Organization

PRELIMINARY COPY


FDD-UM




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

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

METAR Meteorological Aviation Routine Weather Report

MHz Megahertz

MM Millimeters

MON Monoradar Mode of Operation

ms millisecond

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

PRELIMINARY COPY


FDD-UM




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 Requested Flight Level

RIE Route Insertion Error

RISC Reduced Instruction Set

RMCDE Radar Message Conversion and Distribution Equipment

ROC Rate of Climb

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

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

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

UUP 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 Standard Protocol In Telecommunications

PRELIMINARY COPY


FDD-UM




6. 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 6-1. FDD Screen

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.1 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 6.1-1. 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:

Table 6.1-1. General Information Area (GI_A). Elements

Item Type Description

Information Box “Q” AFTN Messages Counter Queue identifier and display of the number of stored AFTN/OLDI messages

Icon SUMMARY Access to the AFTN and OLDI list filtered in the “Q” queue. If it is an OLDI message or if the AFTN message is FP type, it is visualized in the AFTN-FP Correction Window (see 6.1.1.4.1) If the AFTN message is NOTAM type, it is visualized in AFTN-NOTAM Correction Window (see 6.1.1.4.2)

Information Box “AAI” AFTN Messages Counter 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

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

Information Box Time and Date Display the System time and date

PRELIMINARY COPY


FDD-UM




6.1.1

It is composed of several items:

“Q” Queue: AFTN-FP Messages Area (FPM)

“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 6.1.1-1. 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).

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)

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)

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

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)

The System checks whether a message is conflicting with an existing flight plan in the FDP database. If so, the received message and the existing flight plan are both sent to the FPM queue for validation. Likewise, if the message cannot be uniquely identified with a flight plan, it is sent to the FPM queue.

Upon receiving ABI/ ACT/ EST/ POS messages the System creates a Minimal Flight Plan, if the corresponding flight plan does not exist.

The incomplete SFPL and the message are sent to the corresponding Sector Planner FPM queue for insertion of missing data.

All NOTAM messages, with their extracted fields, are placed in the FPM queue for manual confirmation.

MET messages (METAR, SPECI, TAF, SIGMET, ATIS, AIRMET) without errors update the MET database.

Other messages, regarded as “unknown”, including meteorological messages, are directly sent to the FPM queue.

6.1.1.1 AFTN-FP Messages Validation

Regardless of the Flight Plan source, either received from AFTN / IFPS, OLDI, or entered manually, all flight plans are checked for:

Format errors

All flight plans are processed according to a common format, in which the existence or absence of each field will be accordingly marked.

PRELIMINARY COPY


FDD-UM




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.

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

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

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

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 “Passive” 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.

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

PRELIMINARY COPY


FDD-UM




Figure 6.1.1.4-1. 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:

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

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

Icon Description

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.

FP

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.

NOTAM

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.

TACT

Filter for coordination messages (AFTN/OLDI) 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.

COORD

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.

UNKNOWN

This icon is automatically displayed when some queue information has changed: new messages reception, messages deletion, etc. Likewise, it is automatically hidden when the displayed data are the current one.

UPDATE

Close the window. CLOSE

NOTE

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:

: After performing the filter selection, click on the [UPDATE] icon to trigger the filtering.

AFTN-FP Correction Windows

In case the message type is OLDI or 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

PRELIMINARY COPY


FDD-UM




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.

6.1.1.4.1

If receiving a correct AFTN message of “FP” type or a correct OLDI message (FPL, CNL, ABI, etc.) 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 CORRECTION 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.

Figure 6.1.1.4.1-1. AFTN-FP Correction Windows

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.1.1.4.1.1 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 (or OLDI) 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.

Figure 6.1.1.4.1.1-1. AFTN-FP Message Correction Window. Error

Command Area:

It is composed by a set of icons that are described in the following table:

Table 6.1.1.4.1.1-1. AFTN-FP Messages Correction Window. Command Area

Icon Description

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

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

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

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

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

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”).

Rqp

PRELIMINARY COPY


FDD-UM




6.1.1.4.1.2 AFTN-FP TEXT WINDOW

It displays the AFTN-FP (or OLDI) 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:

Table 6.1.1.4.1.2-1. AFTN-FP Text Window. Command Area

Icon Description

Print the text of the AFTN/OLDI message. PRINT

6.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 6.2.2.1.4) plus the “FREE TEXT” field of the FP.

6.1.1.4.1.4 ACTION: AFTN MESSAGE DE-QUEUE (FP MESSAGES)

ACTION

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

RESULT

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

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

ACTION

2. When clicking twice on any entry to correct the message.

RESULT

The System displays the AFTN-FP Messages Correction 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. Click with the LB on the [DELETE] icon The displayed AFTN message is deleted from the queue (the 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 [OK] icon. (Only when the error message is ”FP not exist”).

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

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

b) Click with the LB on the [OK] 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.

6.1.1.4.2

When receiving an AFTN message, which type is “NOTAM”, either correct or incorrect, the system queues the message in the “Q” Queue.

AFTN-NOTAM MESSAGES CORRECTION WINDOW

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

PRELIMINARY COPY


FDD-UM




Figure 6.1.1.4.2-1. 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

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:

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

Table 6.1.1.4.2-1. AFTN-NOTAM Messages Correction Window. Command Area

Icon Description

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

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

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

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

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

6.1.2

It is composed of following elements:

“AAI” Queue: Erroneous AFTN Header Area (EAH)

“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 6.1.2-1. “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.

The received message sequence number is compared with the expected one, and if a discontinuity is

PRELIMINARY COPY


FDD-UM




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.

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

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.1.2.1.1

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:

“AAI” MESSAGES WINDOW

[Update]: Display the new messages that are going to enter in “AAI” Queue.

[Close]: Close the window.

Figure 6.1.2.1.1-1. “AAI” Messages Window

6.1.2.1.2

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

“AAI” ERROR WINDOW

Figure 6.1.2.1.2-1. “AAI” Error Window

PRELIMINARY COPY


FDD-UM




6.1.2.1.3

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

“AAI” MESSAGES CORRECTION WINDOW

Figure 6.1.2.1.3-1. “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:

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

Table 6.1.2.1.3-1. “AAI” Messages Correction Window. Command Area

Icon Description

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

PREV

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

NEXT

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

Trigger the modification action performed in the message. OK

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

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

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

Message repetition query with Filling Day Time and Originator:

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.

SVC QTA RPT ddhhmm address, where

ddhhmm

is the Filling Day Time, and

address

is the Originator

PRELIMINARY COPY


FDD-UM




In both cases the header will display:

Destination: value defined in adaptation.

Originator: value defined in adaptation.

6.1.2.1.4

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:

“AAI” WINDOW

Figure 6.1.2.1.4-1. “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 6.1.2.1.4-1. “AAI” Window. Command Area

Icon Description

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

PREV

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

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

Table 6.1.2.1.4-1. “AAI” Window. Command Area

Icon Description

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

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

Print the current message. PRINT

6.1.2.1.4.1 ACTION: AFTN MESSAGES DE-QUEUE (ERRONEOUS AFTN MESSAGE HEADER)

ACTION

1. Click with the LB on the [SUMMARY] icon, situated in the GI_A.

RESULT

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

2. Click twice on any message entry to visualize or correct it. The System displays the “AAI” Error Window and the “AAI” Messages Correction Window.

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

PRELIMINARY COPY


FDD-UM




ACTION

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

RESULT

4.1. Click with the LB on the [DELETE] 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 is kept in the message queue.

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

4.4. Click with the LB on the [OK] icon (it is only possible in the “AAI” Messages Correction 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..

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

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

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.1.3

The information box presents the system time and date at the top right of the GI_A.

System Time and Date

Figure 6.1.3-1. System Time and Date

Table 6.1.3-1. System Time and Date. Items Description

Item Format

HH: MM (HH = Hour; MM = Minutes) Time

Week day (space) day number (space) month “ of ” AAAA AAAA= four digits of the year

Date

Note

6.1.4

: When the System is not connected to a GPS clock or it is not working, the FDD hour will be synchronized with the CMD hour.

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

FDP Failure

Figure 6.1.4-1. FDP down

PRELIMINARY COPY


FDD-UM




6.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 6.2-1. Main Menu Area (MM_A)

The icons, included in the MM_A, are described in following figure.

Table 6.2-1. FDD Main Menu Area. Commands Icon Row

Icon Description

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

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

Display the Minimal FP Window to create a minimal FP. FP min.

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

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

Display the Airport Runways Window. RUNW

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

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

ARCHIVE

Display the Airport Pressure Window. A.P.

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

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

AREAS

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

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

METEO MSG

Display the NOTAM Operation/Retrieval Window. NOTAM

Display a menu to select the different traffic flow options. T.Flow

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

LINES

Display the window that visualizes the application help. PIP

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

Lock the position and display the Log-In Window LOGOUT

Display the window that allow selection among available printers. PRINTER1

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.1

This icon triggers all procedures related to FP actions.

By clicking on the [FP Act.] icon, the FP Operation Window is displayed.

Icon [FP Act.] Actions on Flight Plans

Figure 6.2.1-1. [FP Act.] Icon

6.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 6.2.1.1-1. FP Operation Window

6.2.1.1.1

Depending on the actions performed on the Flight Plan and the System current time, the Flight Plan can follow these statuses:

FLIGHT PLAN STATUS

PASSIVE

Departure Flight Plan with EOBT 20 minutes (configurable parameter) later than the current time.

Flight Plan entering into the FIR not yet under centre control.

RPL just becomes a Flight Plan.

NOTIFIED

Departure Flight Plan with EOBT 20 minutes (configurable parameter) earlier than current time.

Departure Flight Plan on which a Notification action has been performed.

A “NOTIFIED” FP has SSR code assigned and SID procedure if it exists.

PRELIMINARY COPY


FDD-UM




ACTIVE

Flight Plan, coming from another sector, which is not under that sector control yet.

Departure Flight Plan on which an ATD action has been performed.

Flight Plan on which an EST action has been performed.

TERMINATED

Arrival Flight Plan, which has exceeded the ATA or ETA.

Departure Flight Plan, which has exceeded the FIR exit time.

Flight Plan on which a Cancellation action has been performed.

If a Flight Plan is “TERMINATED”, it is stored in the FDP database and it is deleted from the FP Lists. The FP SSR Code is free and can be used by another FP. No action can be performed on it, except recovery, view, history recovery or copy.

6.2.1.1.2

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.

EDITION AREA

Table 6.2.1.1.2-1. FP Operation Window. Edition Area

Field Description Valid Data

Aircraft Identification or ACID Callsign 3 to 7 alphanumeric characters

SSR Equipment. O 1 alphabetical character: N=> None. (The aircraft do not carry transponder equipment). It is not allowed this value if an SSR Code is assigned. A=> Mode A (Transponder equipment can send positional

information but without altitude information) C=> Mode C (Transponder equipment can send both positional

and altitude information) X=> Mode S (nor aircraft identification transmission neither

pressure altitude information) P=> Mode S (Transponder equipment can send pressure

altitude transmission but it cannot sent aircraft identification transmission)

I=> Mode C (Transponder can send aircraft identification transmission but it cannot send pressure altitude transmission)

S=> Mode S (Transponder can send both aircraft identification and pressure altitude transmission)

Blank = C

ICAO SSR Code CSSR 4 numerical characters (octal 0-7) Blank = It allows the FDP to automatically assign an SSR Code

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010



Flight Rules R 1 alphabetical character: I = IFR V = VFR Y = IFR followed by VFR Z = VFR followed by IFR SP = IFR (single pilot) NV = IFR (night) Blank = I

Flight Type FT 1 alphabetical character: S = scheduled N = non-scheduled G = general aviation M = military X = other Blank = general aviation

Number of Aircrafts N Up to 2 numeric characters (1-99)

Type of Aircraft TYPE 2 to 4 alphanumeric characters. The first one will be an alphabetic character. It must be known by the system.

Wake Turbulence Category W 1 alphabetical character: L = light M = medium H = heavy

RVSM RV 2 alphabetical characters: EQ = equipped with RVSM NO = no-equipped with RVSM UN = unknown EX = exempt

PRELIMINARY COPY


FDD-UM






Navigational/Communications Equipment N.E Up to 8 alphabetical characters: N = Non 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 W = RVSM Y = 8.33 Mz Frequency

Departure Aerodrome ORIG 4 alphabetic characters. If unknown, then enter the “ZZZZ” keyword. If created while aircraft is airborne, then enter the “AFIL” keyword.

Estimated Of Block Date EOBD 6 numerical characters: YYMMDD (00 to 99 and 01 to 12 and 01 to 31) date of departure.

Estimated Off-Block Time EOBT 4 numerical characters: HHMM (00 to 23 and 00 to 59)

Calculated Take-off Time CTOT 4 numerical characters: HHMM (00 to 23 and 00 to 59)

Actual Time of Departure ATD 4 numerical characters: HHMM (00 to 23 and 00 to 59)

Cruising Speed SPEED 5 alphanumeric characters: Kxxxx: 4 numerical characters (Km/h) Nxxxx: 4 numerical characters (Knots) Mxxx: 3 numerical characters (Mach number)

Requested Flight Level RFL 4 alphanumerical characters: Fxxx: 3 numerical characters (hundreds of feet)

Standard Instrumental Departure Procedure

SID 2 to 7 alphanumeric characters. It must be defined in the DBM.

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010



FP Route ROUTE Up to 160 characters. See following NOTE on “Route Field Validation Rules” (see 6.2.1.1.2.2)

Standard Terminal Arrival Route Procedure STAR 2 to 7 alphanumeric characters. It must be defined in the DBM.

Destination Aerodrome DEST 4 alphabetic characters.

Estimated Time Arrival ETA 4 numerical characters: HHMM (00 to 23 and 00 to 59)

Entry Point (for ACT or EST) FIXPOINT Up to 5 alphabetic characters. It must be known by the System.

Estimated time over a significant point (for ACT or EST)

ETO 4 numerical characters: HHMM (00 to 23 and 00 to 59)

Cleared Flight Level (for ACT or EST) CFL 3 numerical characters (hundreds of feet)

Cruising Speed associated al Fixpoint. R SPD 5 alphanumeric characters: Kxxxx: 4 numerical characters (Km/h) Nxxxx: 4 numerical characters (Knots) Mxxx: 3 numerical characters (Mach number)

Next FIX, Future FIX NEXT FIX Up to 5 alphabetic characters. It must be defined in the DBM.

Estimated time over a next point. N ETO 4 numerical characters: HHMM (00 to 23 and 00 to 59).

Sector (for FP strips) S FIR Sector initials.

Alternative aircraft identification. REG 5 alphanumeric characters.

Alternative Aerodromes ALTERN 1 or 2 strings of 4 characters (separated by space).

Notes FREE TEXT Free text.

Aircraft Identification ADDRESS 6 hexadecimals characters (0-9, A-F)

Flight Plan Current Status STATUS FP Statuses: “PASS”. PASSIVE “NOTIF”. NOTIFIED “ACTIV”. ACTIVE “TERM”. TERMINATED

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

PRELIMINARY COPY


FDD-UM




Figure 6.2.1.1.2.1-1. 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:

Click with the mouse LB on the field name and a toggle between the field name and the valid format is performed. These fields are: EOBD, EOBT, CTOT, ATD, ETA, ETO, N. ETO.

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

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]

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

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.

Figure 6.2.1.1.2.2-1. Entry Error Detection in “Route” Field

PRELIMINARY COPY


FDD-UM




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.

C:

It is the route calculated by the system. It marks the point where the error is found.

S:

For detailed information on the “Route” field, see

It is a Standard Route. It is only displayed when there is a standard route defined in the DBM.

APÉNDICE / APPENDIX A.

6.2.1.1.3

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.

COMMAND AREA

Table 6.2.1.1.3-1. FP Operation Window (action mode). Command Area

Icon/Switch Command

Display an existing FP data View

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.

Hist.

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.

Crea.

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

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

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.

Cancel

It allows changing a FP from “PASSIVE” 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.

Notif

Cancel a previous Notification action. The FP returns to “PASSIVE” status, if the entered hour is earlier than the current one in a defined parameter.

C.Notif

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.

ATD

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

C.ATD

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

EST

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

POS

Inform the System on the FPL actual time of arrival. ATA

Print the Flight Plan strip. Strips

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

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

Table 6.2.1.1.3-1. FP Operation Window (action mode). Command Area

Icon/Switch Command

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

CLOSE

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

Print the historical information of a FP. PRINT

This point includes all the procedures to perform on the FP Operation Window.

A common step to all actions is following described:

6.2.1.1.3.1 ACTION: COMMON STEP TO ACTIONS ON FPS

ACTION

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

RESULT

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

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. If there are no accessible fields, only the compulsory ones can be modified. The “S”, “CTOT” and “ADDRESS” fields are not applicable.

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

RESULT

The switch changes to YELLOW.

2. Enter data on the corresponding fields to retrieve the FP.

3. Finish the operation by performing a close action (see 3.7)

Compulsory Fields: CALLSIGN.

PRELIMINARY COPY


FDD-UM




6.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 6.2.2.1.4) plus the field “FREE TEXT” of the FP.

Figure 6.2.1.1.3.3-1. List of Synonyms Window

6.2.1.1.3.4 ACTION: FPL HISTORY ACTION

1. Perform the FP View action (see

RESULT

6.2.1.1.3.2)

2. Click with the LB on the [Hist.] switch. 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.


Compulsory Fields: CALLSIGN only if the FP View action has not been previously performed. Accessible Fields: NONE

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.1.1.3.5 ACTION: CREATE FPL ACTION

1. Click with the LB on the [Crea] switch.

RESULT


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 “PASSIVE” or “NOTIFIED” status. If they are incorrect, the System displays a message corresponding to the erroneous data.


Compulsory Fields: CALLSIGN, TYPE, ORIG, EOBT, RFL, DEST and ROUTE.

NOTE

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

6.2.1.1.3.6 ACTION: CREATE A CURRENT FPL (CPL) ACTION

1. Click with LB on the [CPL Create] switch.

RESULT


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 “ACTIVE” status. If they are incorrect, the System displays a message corresponding to the erroneous data.


Compulsory Fields: CALLSIGN, TYPE, ORIG, EOBT, RFL, DEST, ROUTE, FIXPOINT, 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.

PRELIMINARY COPY


FDD-UM




6.2.1.1.3.7 ACTION: MODIFY FPL ACTION


RESULT

6.2.1.1.3.2)

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


Compulsory Fields: CALLSIGN, TYPE, ORIG, DEST, EOBT, SPEED, RFL and ROUTE only if the visualization action has not been previously performed. Accessible Fields: All of them, except: FIXPOINT, ETO, CFL, S, SD, SOURCE and STATUS.

NOTE

6.2.1.1.3.8 ACTION: CANCEL FPL

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

ACTION


RESULT

6.2.1.1.3.2)

2. Click with the LB on the [Cancel] switch. The switch changes to YELLOW.


Compulsory Fields: CALLSIGN and ORIG 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.

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.1.1.3.9 ACTION: STATUS CHANGE FROM “PASSIVE” TO “NOTIFIED”

ACTION


RESULT

6.2.1.1.3.2)

2. Click with the LB on the [NOTIF] switch. The switch changes to YELLOW.

3. Enter data into the “CSSR” field, if needed. Click on [OK] 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.


Compulsory Fields: None Accessible Fields: CSSR

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.

6.2.1.1.3.10 ACTION: STATUS CHANGE FROM “NOTIFIED” TO “PASSIVE” ACTION


RESULT

6.2.1.1.3.2)

2. Click with the LB on the [C.NOTIF] switch. The switch changes to YELLOW.

PRELIMINARY COPY


FDD-UM




ACTION

3. Click on the [OK] icon

RESULT

The FP status changes to “Passive”.


NOTE

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

6.2.1.1.3.11 ACTION: CONFIRM/MODIFY ATD ACTION


RESULT

6.2.1.1.3.2)

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 “ATD” field.

3. Confirm or modify the data displayed on the “CSSR” field. The FP status changes to “Active”.


Compulsory Fields: CALLSIGN and ORIG only if the FP visualization action has not been previously performed. Accessible Fields: CSSR, RFL, and SID.

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.

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.1.1.3.12 ACTION: CANCEL ATD ACTION


RESULT

6.2.1.1.3.2)

2. Click with the LB on the [C. ATD] switch. The switch changes to YELLOW.

3. Click with the LB on the [OK] 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 “Passive”. The FP Operation Window is displayed on view mode ([View] switch is activated). All fields are inaccessible.


NOTE

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

6.2.1.1.3.13 ACTION: ESTIMATE ACTIONS ACTION


RESULT

6.2.1.1.3.2)

2. Click with the LB on the [EST] switch. 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.

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.

PRELIMINARY COPY


FDD-UM




4. Click with the LB on the [OK] icon 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 “FixPoint” and “CFL” fields are mandatory. Accessible Fields: CALLSIGN, CSSR, RIG, SPEED, RFL, ROUTE, STAR, ETO and R SPD.

6.2.1.1.3.14 ACTION: PASSING OVER FIXPOINT ACTION


RESULT

6.2.1.1.3.2)

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 “ETO” as well as the next route fixpoint “NEXT FIX” and the estimated time for the FP to overfly that fixpoint “N.ETO”. Click with the LB on the [OK] icon.

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


Compulsory Fields: If the FP visualization action has not been previously performed, the “FixPoint” and “CFL” fields are mandatory. Accessible Fields: CALLSIGN, CSSR, ORIG, RFL, ROUTE, STAR, ETO, R.SPD, Next Fix and N. ETO.

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.1.1.3.15 ACTION: CONFIRM/MODIFY ATA ACTION


RESULT

6.2.1.1.3.2)

2. Click with the LB on the [ATA] switch. 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.

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


Compulsory Fields: Callsign, ORIG, 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.

6.2.1.1.3.16 ACTION: REQUEST FLIGHT PLAN STRIPS PRINTING

ACTION

1. Perform the FP visualization action (see

RESULT

6.2.1.1.3.2).

2. Click on the [Strips] switch with the LB. The switch becomes YELLOW, and the accessible fields for the action are WHITE background.

3. Enter the “FIXPOINT” data or the “S” sector data for which the strip is going to be printed.

A FP strip is printing in the SDD where the request is. It the printer is available, the strip is printed in the one defined by default. It the strip cannot be printed, the SDD receives a message in the [SYS MSG] indicating the event.

4. Finish the action performing a close procedure (see 3.7)

Compulsory Fields: FIXPOINT and S

PRELIMINARY COPY


FDD-UM




6.2.1.1.3.17 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 (“CALLSIGN” is mandatory) to retrieve the desired FP.

3. Click on the [Mod] switch. The switch becomes YELLOW, and the accessible fields for the action are WHITE background.

4. Modify the “ROUTE” field to enter the desired route and click with the LB on the [OK] icon.

5. Finish the action performing a close procedure (see 3.7)

6.2.1.1.4

It displays the error associated to the field where the mouse is focused on.

ERROR MESSAGE AREA

A list of error messages is provided in Appendix E.

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.1.1.5

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.

LIST OF SYNONYMS

Figure 6.2.1.1.5-1. 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.

6.2.1.1.6

This window is automatically displayed on top of the FP Operation Window. It allows warning the controller on the following cases:

AREA WARNINGS WINDOW

When the flight is about to cross a restricted area.

When the flight has already crossed the restricted area.

PRELIMINARY COPY


FDD-UM




Figure 6.2.1.1.6-1. Area Warnings Window

Following table describes the information included in the Area Warnings Window:

Table 6.2.1.1.6-1. Area Warnings Window

Name of the restricted area.

Field

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.

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.2

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.

Icon [FP Rtr.] Actions on Retrieved FP

Figure 6.2.2-1. [FP Rtr.] Icon

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

Figure 6.2.2.1-1. FP Retrieval Window

PRELIMINARY COPY


FDD-UM




6.2.2.1.1

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.

EDITION AREA

Table 6.2.2.1.1-1. FP Retrieval Window. Edition Area


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

ROUTE Name of fixes known by the System

Time determining the start of a temporal filter for FPL retrieval FROM HHMM (00 to 23 and 00 to 59)

Time determining the end of a temporal filter for FPL retrieval UNTIL HHMM (00 to 23 and 00 to 59)

6.2.2.1.2

Following table shows the different commands included in the FP Retrieval Window.

COMMAND AREA

Table 6.2.2.1.2-1. FP Retrieval Window. Command Area

Icon/Switch Description

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

Trigger the actions performed in the current window. OK

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

CLOSE

Delete the data displayed on the fields of the window. CLEAR

Print all the Retrieved FP. Pr All

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.2.1.2.1 ACTION: RETRIEVE MULTIPLE FPL

ACTION

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

RESULT

The FP Retrieval Window is displayed.

2. To display the FPs:

2.1. If input parameters are known, enter the data in the corresponding fields and click on the [OK] 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 [OK] icon.

The Retrieved Flight Plan(s) Window is displayed with all flight plans.

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

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

PRELIMINARY COPY


FDD-UM




ACTION

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

RESULT

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


Compulsory Fields: None.

6.2.2.1.3


ERROR MESSAGE AREA


6.2.2.1.4

This window is displayed when clicking on the [OK] 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.

RETRIEVED FLIGHT PLAN(S) WINDOW

Figure 6.2.2.1.4-1. Retrieved FP Window. List Elements

Each line included in this window contains the following information:

Callsign - R - N - Type - Orig - EOBT - Speed - RFL - Dest - ETA - SSRC/C - Route - Status

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

Table 6.2.2.1.4-1. Retrieved Flight Plan(s) Window. List Element

Element Description

Aircraft Identifier Callsign

Flight Rules R

Number of Aircrafts N

Aircraft Type Type

Departure Aerodrome Orig

Estimated Off-Block Date EOBD

Estimated Off-Block Time EOBT

Cruising Speed Speed

Requested Flight Level RFL

Destination Aerodrome Dest

Estimated Time of Arrival ETA

SSR Code SSRC/C

FP Route Route

FP Status Status

PRELIMINARY COPY


FDD-UM




6.2.3

This icon triggers the creation of a Minimal FP.

Icon [FP MIN.] Minimal Flight Plan

Figure 6.2.3-1. [FP Min.] Icon

6.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 6.2.3.1-1. Minimal FP Window

6.2.3.1.1

All the fields in this window are compulsory and have to be filled out.

EDITION AREA

Table 6.2.3.1.1-1. Minimal FP Window. Edition Area


Aircraft identification CALLSIGN 1 to 8 alphanumeric characters

SSR code CSSR 4 digits

Departure Aerodrome ORIG 4 alphanumeric characters

Destination Aerodrome DEST 4 alphanumeric characters

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.3.1.2

Following table shows the different commands included in the Minimal FP Window.

COMMAND AREA

Table 6.2.3.1.2-1. Minimal FP Window. Command Area

Icon Description

Create a FP with the minimum fields. OK

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

CLOSE


6.2.3.1.2.1 ACTION: CREATE A MINIMAL FP ACTION

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

RESULT

The Minimal FP Window is displayed.

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

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


Compulsory Fields: All.

6.2.3.1.3


ERROR MESSAGE AREA


PRELIMINARY COPY


FDD-UM




6.2.4

This icon triggers all procedures related to RPL actions. When clicking on the [RPL Act.] icon, the RPL Operation Window is displayed.

Icon [RPL Act.] Actions on Repetitive Flight Plan

Figure 6.2.4-1. [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

6.2.4.1 RPL Operation Window

: The off-line RPL management facility is not available in the system. Nevertheless, the on-line functionality related to RPLs is allowed

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 6.2.4.1-1. RPL Operation Window

6.2.4.1.1

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

EDITION/ACTIVATION AREA

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

Table 6.2.4.1.1-1. RPL Operation Window. Edition/Activation Area

Field / Switch Description Valid Data

Aircraft Identification Callsign 1 to 8 alphanumeric characters

Flight Rules R I = IFR V = VFR Y = IFR followed by VFR Z = VFR followed by IFR SP = IFR (single pilot) NV = IFR (night) Blank = I

Number of Aircrafts N Up to 2 numeric characters (1-99)

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

Wake Turbulence Category W L = light M = medium H = heavy

Navigation Equipment EQ Not more than 3 alphabetic characters.

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

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

ETD HHMM (00 to 23 and 00 to 59)

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

Requested Flight Level RFL 3 numerical characters (hundreds of feet)

Destination Aerodrome DEST Four alphabetic characters.

Elapsed Estimated Time EET HHMM (00 to 23 and 00 to 59)

FP Route ROUTE Up to 160 characters. See the NOTE on “Route Field Validation Rules” included in section 6.2.1.1.2.2.

Notes FREE TEXT

VALID PERIOD

Time defining the start of the validity period for the RPL. FROM YYMMDD (00 to 99, 01 to 12 and 01 to 31)

Time defining the end of the validity period for the RPL. UNTIL YYMMDD (00 to 99, 01 to 12 and 01 to 31)

OPERATION DAYS

Indicate the days of the week when the RPL is scheduled. MTWTFSS From Monday to Sunday

PRELIMINARY COPY


FDD-UM




6.2.4.1.2

Following table shows the different commands, which are included in the RPL Operation Window.

COMMAND AREA

Table 6.2.4.1.2-1. RPL Operation Window. Command Area

Icon / Switch Command

Display the RPL data. View

Create a new RPL. Create

Modify an RPL. Modify

Terminate an RPL. Cancel

Trigger all actions performed in current window. OK

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

CLOSE


Print all the retrieved FP Pr All

6.2.4.1.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).

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

6.2.4.1.2.2 ACTION: VISUALIZE RPL ACTION

1. Click with the LB on the [View] switch.

RESULT


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

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

ACTION

3. Finish the operation by performing a close action (see

RESULT

3.7)

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.

6.2.4.1.2.3 ACTION: CREATE RPL ACTION

1. Click with the LB on the [Create] switch.

RESULT

NOTE6.2.4.1.2.2

: This action may start from a previous visualization action (see ).


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.


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.

6.2.4.1.2.4 ACTION: MODIFY RPL ACTION

1. Perform the Visualization action

RESULT

6.2.4.1.2.2.

2. Click with the LB on the [Modify] switch. The switch becomes YELLOW and the accessible fields for the action are displayed in WHITE background.

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

PRELIMINARY COPY


FDD-UM




ACTION


RESULT

3.7)

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.

6.2.4.1.2.5 ACTION: CANCEL RPL ACTION

1. Perform the Visualization action

RESULT

6.2.4.1.2.2.

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

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.

6.2.4.1.3


ERROR MESSAGE AREA


PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.5

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.

Icon [RPL Rtr.] Repetitive Flight Plans Retrieval

Figure 6.2.5-1. [RPL Rtr.] Icon

NOTE

6.2.5.1 RPLs Retrieval Window

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

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 6.2.5.1-1. RPLs Retrieval Windows

PRELIMINARY COPY


FDD-UM




6.2.5.1.1

Fields included in this area are the same as for the RPL Operation Window (see section

EDITION/ACTIVATION AREA

6.2.4.1.1).

6.2.5.1.2

Following table shows the different commands, which are included in the RPLs Retrieval Window.

COMMAND AREA

Table 6.2.5.1.2-1. RPLs Retrieval Window. Command Area


Not available Summary Retrieve

Trigger the actions performed in current window. OK

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

CLOSE


Print all the retrieved FP. Pr All

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.5.1.2.1 ACTION: RETRIEVE MULTIPLE RPLS ACTION

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

RESULT

The RPLs Retrieval Window is displayed.

2. To display the RPLs:

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

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

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

The Retrieved RPLs Window is displayed with all RPLs.

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

3.1. Click twice on the corresponding RPL. 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.

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



6.2.5.1.3


ERROR MESSAGE AREA


PRELIMINARY COPY


FDD-UM




6.2.5.2 Retrieved RPLs Window

This window is displayed when clicking on the [OK] 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 6.2.5.2-1. Retrieved RPLs Window. List Element

Element Description

Aircraft Identification Callsign

Flight Rules R

Number of Aircrafts N

Aircraft Type Type

Destination Aerodrome Orig

Estimated Time of Departure ETD

Cruising Speed Speed

Requested Flight Level RFL

Destination Aerodrome Dest

Estimated Time of Arrival ETA

SSR Code SSRC/C

FP Route Route

Start and end time for the RPL Valid Period (From-Until)

Days of the week Operat. Days (MTWTFSS)

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.6

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

Icon [Runw] Airport Runways Actions

Figure 6.2.6-1. [Runw] Icon

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

Figure 6.2.6.1-1. Airport Runways Window

6.2.6.1.1

Following table describes the fields included in the Airport Runways Window:

EDITION AREA

Table 6.2.6.1.1-1. Airport Runways Window. Edition Area

Field Description

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

AIRPORT

Runway Identification. Runways

Configure the runway use (arrivals, departures or both) Dep / Arr (switches)

PRELIMINARY COPY


FDD-UM




6.2.6.1.2

Following table explains the commands included in the Airport Runways Window:

COMMAND AREA

Table 6.2.6.1.2-1. Airport Runways Window. Command Area

Icon/Switch Command

Display of the runways configuration for the selected airport. View

Perform modifications over an airport runway. Modify


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


6.2.6.1.2.1 ACTION: VISUALIZATION OF AIRPORT RUNWAYS ACTION

1. Click with the LB on the [RUNW] icon.

RESULT

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.

3.7)

Compulsory Fields: AIRPORT.

6.2.6.1.2.2 ACTION: MODIFY AIRPORT RUNWAYS ACTION

1. Perform the visualization action.

RESULT

2. Click with the LB on the [Modify] switch. The switch changes to YELLOW.

3. Modify the required runways.


Compulsory Fields: AIRPORT.

6.2.6.1.3

It displays the error associated to the field. A list of error messages is provided in Appendix

ERROR MESSAGE AREA

E.

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.7

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:

Icon [AFTN TX] AFTN Transmission

Figure 6.2.7-1. [AFTN TX] Icon

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

Figure 6.2.7.1-1. ICAO AFTN Transmission Window

6.2.7.1.1

Following table lists, for each field included in the ICAO AFTN Transmission Window, a description with the valid data.

EDITION AREA

Error Message Area Command Area

Edition Area

PRELIMINARY COPY


FDD-UM




Table 6.2.7.1.1-1. ICAO AFTN Transmission Window. Edition Area


AFTN priority indicator Priority Follow ICAO rules

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

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

Filling Time 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 Indicator Originator A sequence of 8 letters. If not filled in, the Local Address defined in adaptation will be automatically entered.

Type of message Message Type 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) Aircraft Identification 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

ICAO SSR Code 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 SP = IFR (single pilot) NV = IFR (night) Left Blank = I

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010



Aircraft Type Type Flight S = scheduled N = non-scheduled G = general aviation M = military X = other Left blank = general aviation

Number of Aircrafts Number Up to 2 numeric characters (1-99)

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

Wake Turbulence Category Wake Turb. Cat L = light M = medium H = heavy

Navigation/Communication Equipment Equipment 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.

PRELIMINARY COPY


FDD-UM






SSR Equipment Field 1 character. It is one of the followings: N=> None. (Aircraft does not carry transponder

equipment). 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




Blank = C

Aerodrome of departure Departure Aerodrome

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

EOBT (for known departure aerodrome) Or Estimated or actual arrival time (EET/ETA) to the first route fix-point referenced in the flight plan.

EOBT HHMM (00 to 23 and 00 to 59)

Point with an associated information for a FP.

Reference Point Alphanumeric characters (2 to 5).

Time at the reference point Time HHMM (00 to 23 and 00 to 59)

Cleared Level at the reference point. Auth. 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.

Supplementary Level at the reference point.

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

Crossing Condition Cross C. A= Above B= Below

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

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010



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

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

Flight Plan Route Route Names of fix points known by the System.

Destination Aerodrome Destination Aero. 4 alphabetic characters. If unknown ZZZZ.

Total Estimated Elapsed Time (Estimated flight duration)

Total EET HHMM (00 to 23 and 00 to 59)

Alternative Aerodrome Altn Aerodrome ICAO aerodrome indicator. 4 alphabetic characters. If unknown ZZZZ.

Second Alternative Aerodrome 2nd. Altn Aerodrome ICAO aerodrome indicator. 4 alphabetic characters. If unknown ZZZZ.

PRELIMINARY COPY


FDD-UM






Statement of any other necessary information.

Other 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 “Aircraft Identification” field.

STS/ Reason for special handling by ATS (e.g. hospital aircraft)

TYP/ Type(s) of aircraft, preceded, if necessary, by number of aircraft and if “ZZZZ” is used in the “Aircraft Type” field.

PER/ Aircraft performance data, if so, prescribed by the appropriate ATS authority.

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 Emergency Description

Free Text

Additional Information Supplementary information

Free Text

Alert Information Alert Information Free Text

Communication Information Communication Information

Free Text

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.7.1.2

Following table describes commands included in the ICAO AFTN Transmission Window.

COMMAND AREA

Table 6.2.7.1.2-1. ICAO AFTN Transmission Window. Command Area

Icon/Switch Command

Information visualization. VIEW

Send the information. TRANS

Insert the message into the System. AUTO SEND

Trigger the performed actions in the window. OK

Close the ICAO AFTN Transmission Window. CLOSE

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

6.2.7.1.2.1 ACTION: EDIT/TRANSMIT ICAO AFTN MESSAGES

ACTION

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

RESULT

The ICAO AFTN Transmission Window is displayed.

PRELIMINARY COPY


FDD-UM




ACTION

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

RESULT

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.

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.


Compulsory Fields: It depends on the type of message.

6.2.7.1.3


ERROR MESSAGE AREA


PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

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


Figure 6.2.7.2-1. ICAO ADEXP Transmission Window

6.2.7.2.1

Following table lists, for each field included in the ICAO ADEXP Transmission Window, a description with the valid data.

EDITION AREA

Table 6.2.7.2.1-1. ICAO ADEXP Transmission Window. Edition Area


ADEXP priority indicator Priority Follow ICAO rules

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

PRELIMINARY COPY


FDD-UM






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

Filling Time 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.


Message Type Type of message 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) Aircraft Identification 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

ICAO SSR Code 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 SP = IFR (single pilot) NV = IFR (night) Left Blank = I

Aircraft Type Type Flight S = scheduled N = non-scheduled G = general aviation M = military X = other Left blank = general aviation

Number of Aircrafts Number Up to 2 numeric characters (1-99)

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

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010



Wake Turbulence Category Wake Turb. Cat L = light M = medium H = heavy

Navigation/Communication Equipment Equipment 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.

SSR Equipment Field 1 character. It is one of the followings: N=> None. (Aircraft does not carry transponder equipment). 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




Blank = C

Aerodrome of departure Departure Aerodrome

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

PRELIMINARY COPY


FDD-UM






EOBT (for known departure aerodrome) Or Estimated or actual arrival time (EET/ETA) to the first route fix-point referenced in the flight plan.

EOBT HHMM (00 to 23 and 00 to 59)

Point with an associated information for a FP.

Reference Point Alphanumeric characters (2 to 5).

Time at the reference point Time HHMM (00 to 23 and 00 to 59)

Cleared Level at the reference point. Auth. 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.

Supplementary Level at the reference point.

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

Crossing Condition Cross C. A= Above B= Below

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

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

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

Flight Plan Route Route Names of fix points known by the System.

Destination Aerodrome Destination Aero. 4 alphabetic characters. If unknown ZZZZ.

Total Estimated Elapsed Time (Estimated flight duration)

Total EET HHMM (00 to 23 and 00 to 59)

Alternative Aerodrome Altn Aerodrome ICAO aerodrome indicator. 4 alphabetic characters. If unknown ZZZZ.

Second Alternative Aerodrome 2nd. Altn Aerodrome ICAO aerodrome indicator. 4 alphabetic characters. If unknown ZZZZ.

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010



Statement of any other necessary information.

Other 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 “Aircraft Identification” field.

STS/ Reason for special handling by ATS (e.g. hospital aircraft)

TYP/ Type(s) of aircraft, preceded, if necessary, by number of aircraft and if “ZZZZ” is used in the “Aircraft Type” field.

PER/ Aircraft performance data, if so, prescribed by the appropriate ATS authority.

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 Emergency Description

Free Text

Additional Information Supplementary information

Free Text

Alert Information Alert Information Free Text

Communication Information Communication Information

Free Text

PRELIMINARY COPY


FDD-UM




6.2.7.2.2

Following table describes commands included in the ICAO ADEXP Transmission Window.

COMMAND AREA

Table 6.2.7.2.2-1. ICAO AFTN Transmission Window. Command Area

Icon/Switch Command

Information visualization. VIEW

Send the information. TRANS

Insert the message into the System. AUTO SEND

Trigger the performed actions in the window. OK

Close the ICAO ADEXP Transmission Window. CLOSE

Delete the information included in the ICAO ADEXP Transmission Window. CLEAR

6.2.7.2.2.1 ACTION: EDIT/TRANSMIT ICAO ADEXP MESSAGES

ACTION

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

RESULT

The ICAO ADEXP Transmission Window is displayed.

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

ACTION

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

RESULT


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.

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.



Compulsory Fields: It depends on the type of message.

6.2.7.2.3


ERROR MESSAGE AREA


PRELIMINARY COPY


FDD-UM




6.2.7.3 Free AFTN Transmission Window

When selecting from the [AFTN TX] menu the (FREE AFTN) option, the Free AFTN Transmission Window is displayed.


Figure 6.2.7.3-1. Free AFTN Transmission Window

Command Area Error Message Area

Edition Area

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.7.3.1

Following table lists for each field included in the Free AFTN Transmission Window a description with the valid data.

EDITION AREA

Table 6.2.7.3.1-1. Free AFTN Transmission Window. Edition Area


AFTN priority indicator Priority Follow ICAO rules

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

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

Filling Time 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.


Any text Free Text Text

6.2.7.3.2

Following table describes the commands included in the "FREE AFTN Transmission” Window.

COMMAND AREA

Table 6.2.7.3.2-1. Free AFTN Transmission Window. Command Area

Icon/Switch Command

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

Not available. PRINT

Send the AFTN message. TRANS

Close the Free AFTN Transmission Window. CLOSE

Delete the information displayed in the Free AFTN Transmission Window. CLEAR

PRELIMINARY COPY


FDD-UM




6.2.7.3.2.1 ACTION: EDIT/TRANSMIT TEXT AFTN MESSAGES

ACTION

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

RESULT

The Free AFTN Transmission Window is displayed.

2. Enter data into the corresponding fields.


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

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

ACTION

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

RESULT

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.



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

6.2.7.3.3


ERROR MESSAGE AREA


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


PRELIMINARY COPY


FDD-UM




Figure 6.2.7.4-1. SVC Transmission Window

6.2.7.4.1

Following table lists a description for each field included in the SVC Transmission Window.

EDITION AREA

Table 6.2.7.4.1-1. SVC Transmission Window. Edition Area

Field Description

AFTN line through which the messages are sent. Line 1 / Line 2

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 (Lower)

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

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.

6.2.7.4.2

Following table lists the different commands included in the SVC Transmission Window.

COMMAND AREA

Table 6.2.7.4.2-1. SVC Transmission Window. Command Area

Icon Command

Send the selected service AFTN message or group of messages. OK

Close the SVC Transmission Window. CANCEL

Delete the information displayed on the SVC Transmission Window. CLEAR

Edition Area

Command Area

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.7.4.2.1 ACTION: TRANSMIT SVC MESSAGES

ACTION

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

RESULT

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.

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.

PRELIMINARY COPY


FDD-UM




6.2.8

This icon allows retrieving all sent and received AFTN messages. When clicking on the [ARCHIVE] icon, the AFTN Retrieve Window is displayed.

Icon [ARCHIVE] AFTN Messages Retrieval

Figure 6.2.8-1. [ARCHIVE] Icon

6.2.8.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 6.2.8.1-1. AFTN Retrieve Window

Error Messages Area Command Area

Edition Area

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.8.1.1

Following table lists the fields and their corresponding description:

EDITION AREA

Table 6.2.8.1.1-1. AFTN Retrieve Window. Edition Area


Sending or reception date of the AFTN messages to be retrieved. Date 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.

AFTN message sending or reception time. Tx Time Interval

Temporal filter starting time for AFTN message retrieval. From HHMM (00 to 23 and 00 to 59)

Temporal filter final time for AFTN message retrieval. To HHMM (00 to 23 and 00 to 59)

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

Sequence number filter starting number. From (000-999)

Sequence number filter starting number. To (000-999)

AFTN priority indicator. Prior Follow ICAO rules

Transmission Address Destiny 8 characters sequence

Originator Indicator Originator 8 characters sequence

Text Free Search

6.2.8.1.2

Following table lists the different commands included in the AFTN Retrieve Window.

COMMAND AREA

Table 6.2.8.1.2-1. AFTN Retrieve Window. Command Area

Icon Description


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

Delete the data displayed on the window. CLEAR

PRELIMINARY COPY


FDD-UM




6.2.8.1.2.1 ACTION: RETRIEVE MULTIPLE AFTN MESSAGES ACTION

1. Click with the LB on the [ARCHIVE] icon.

RESULT

The AFTN Retrieve Window is displayed.

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 [OK] icon.

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:

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

ACTION

3.1. By clicking twice on the corresponding message.

RESULT

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

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

6.2.8.1.3


ERROR MESSAGE AREA


PRELIMINARY COPY


FDD-UM




6.2.8.2 Retrieve Multiple AFTN Window

This window is displayed when clicking on the [OK] 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.

Figure 6.2.8.2-1. Retrieve Multiple AFTN Window

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

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

Figure 6.2.8.3-1. AFTN Element Window


6.2.8.3.1

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.

EDITION AREA

Table 6.2.8.3.1-1. AFTN Element Window. Edition Area


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.

Sequence number of the retrieved message. Sort Number (0000 – 9999)

AFTN message sending or reception time. Tx Day Time HHMM (00 to 23 and 00 to 59)

AFTN priority indicator. Prior Follow ICAO rules

Transmission Address. Dest 8 characters sequence

Command Area

Message Test Area

Edition Area

PRELIMINARY COPY


FDD-UM




Table 6.2.8.3.1-1. AFTN Element Window. Edition Area


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

Filling Day Time DDHHMM (00 to 31, 00 to 23 and 00 to 59)

Originator Indicator. Originator 8 characters sequence

Text. Text

6.2.8.3.2


ERROR MESSAGE AREA

6.2.8.3.3

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

COMMAND AREA

Table 6.2.8.3.3-1. AFTN Element Window. Command Area

Icon Description

Transmit a previously transmitted message. The sending message is the same as the one formerly sent except for:

TRANSMIT

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.

Transmit a previously transmitted message. The sending message is the same as the one formerly sent except for:

RETRANSMIT

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.


CLOSE

Print the message. PRINT

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.8.4 OLDI Retrieve Window

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


6.2.8.4.1

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.

EDITION AREA

Table 6.2.8.4.1-1. OLDI Retrieve Window. Edition Area


Sending/ reception messages data. DATE DDMMYY

External control center. CTRL CENTER Up to 4 characters.

OLDI message sending or reception time interval. TX DAY TIME FROM: HHMM (00 to 23 and 00 to 59) TO: HHMM (00 to 23 and 00 to 59)

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

6.2.8.4.2


ERROR MESSAGE AREA

PRELIMINARY COPY


FDD-UM




6.2.8.4.3

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

COMMAND AREA

Table 6.2.8.4.3-1. AFTN Element Window. Command Area

Icon Description

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


CLOSE

Erase all data entered in every window edition field. CLEAR

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.9

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

Icon [A.P.] Airport Pressure

Figure 6.2.9-1. [A.P.] Icon

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

Figure 6.2.9.1-1. Airport Pressure Window

6.2.9.1.1

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.

ELEMENT LIST AREA

6.2.9.1.2

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.

EDITION AREA

PRELIMINARY COPY


FDD-UM




Table 6.2.9.1.2-1. Airport Pressure Window. Edition Area

Field Description

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

Display and allow modifications on the QNH. QNH

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

6.2.9.1.3

Following table describes the commands included in the window:

COMMAND AREA

Table 6.2.9.1.3-1. Airport Pressure Window. Command Area

Icon/Switch Command

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

Modify the information related to the QNH. Modify

Trigger the actions performed in the Airport Pressure Window. OK

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

CLOSE

Delete the information displayed on the Airport Pressure Window. CLEAR

6.2.9.1.3.1 ACTION: QNH AND TRANSITION LEVEL VISUALIZATION ACTION

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

RESULT

The Airport Pressure Window is displayed.

2. The visualization action can be performed by: 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.


Compulsory Fields: Zone

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.9.1.3.2 ACTION: MODIFY QNH AND TRANSITION LEVEL ACTION

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

RESULT

The Airport Pressure Window is displayed.

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

3. Click with the LB on the [OK] icon The data presented on the upper list are displayed on the corresponding fields.

4. Modify the desired data.


Compulsory Fields: Zone, QNH and Transition Level.

6.2.9.1.4


ERROR MESSAGE AREA


PRELIMINARY COPY


FDD-UM




6.2.10

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.

Icon [WINDS] Wind Data

Figure 6.2.10-1. [WINDS] Icon

6.2.10.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 6.2.10.1-1. Winds Data Window

6.2.10.1.1

Following table lists fields included in the Winds Data Window and a description of those fields with their valid data.

EDITION AREA

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

Table 6.2.10.1.1-1. Winds Data Window. Edition Area


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

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

Display the identification of geographic areas. Zone Defined by adaptation

Relevant levels defined for each geographic area. Layer Up to eight

Winds direction in the associated area/level. Wind Direction In degrees from true north

Speed of the wind in the associated area/level. Speed From 0 to 250 kilometres per hour.

6.2.10.1.2

Following table describes the commands included in the Winds Data Window.

COMMAND AREA

Table 6.2.10.1.2-1. Winds Data Window. Command Area


Display the wind information. View

Modify the wind information. Modify


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

6.2.10.1.2.1 ACTION: VISUALIZATION OF WIND DATA ACTION

1. Click with the LB on the [WINDS] icon.

RESULT

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

2. Enter data in the corresponding fields.


PRELIMINARY COPY


FDD-UM




6.2.10.1.2.2 ACTION: MODIFY WIND DATA ACTION

1. Click with the LB on the [WINDS] icon.

RESULT

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.


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

6.2.10.1.3


ERROR MESSAGE AREA


PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.11

Restricted Areas are elements, which are created on-line and have two associated characteristics:

Icon [AREAS] Restricted Areas

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.

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 6.2.11-1. [AREAS] Icon

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

PRELIMINARY COPY


FDD-UM




Figure 6.2.11.1-1. 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.

6.2.11.1.1

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.

ELEMENT LIST AREA

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

Figure 6.2.11.1.1-1. 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 6.2.11.1.1-1. Restricted Areas Window. Element List Area

Element Description

Display the restricted area identification. AREA ID

Display the restricted area type. TYPE

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

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

Display the restricted area validity period. VALIDITY

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

6.2.11.1.2

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

DESCRIPTION AREA

Figure 6.2.11.1.2-1. Restricted Areas Window. Description Area

This area is composed of the following items:

PRELIMINARY COPY


FDD-UM




Table 6.2.11.1.2-1. Restricted Areas Window. Description Area

Item/Switch Description

Display the number of restricted areas. TOTAL

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

AREA ID

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

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

Brief description of the restricted area. DESCRIPTION

Describe the assigned class to the restricted area. CLASS

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

6.2.11.1.3 ACTIVATION/VALIDITY AREA

Figure 6.2.11.1.3-1. 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 6.2.11.1.3-1. Restricted Areas Window. Activation/Validity Area

Field/Switch Description Valid Data

Validity Period 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.

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

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

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

Table 6.2.11.1.3-1. Restricted Areas Window. Activation/Validity Area


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

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

Enter Activity Range 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. Daily The switch colour code indicates the selection status. YELLOW = Selected Background = Not selected

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

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

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

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

Select a weekly activation mode for the restricted area.

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

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

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

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

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

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

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

Select the activation mode by events. Dates On The switch colour code indicates the selection status. YELLOW = Selected Background = Not selected

The system allows the definition of up to 4 activation periods for the restricted area. In this mode of activation, the activation limits (starting and ending) are defined by time and date, not only time as in previous cases.

YYMMDD/HHMM – YYMMDD/HHMM, 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)

PRELIMINARY COPY


FDD-UM




6.2.11.1.4

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

LAYOUT AREA

Figure 6.2.11.1.4-1. Restricted Areas Window. Layout Area

Table 6.2.11.1.4-1. Restricted Areas Window. Layout Area


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

Upper vertical limit of the restricted area. UPPER From lower vertical limit to 999.

Lower vertical limit of the restricted area. LOWER From 000 to upper vertical limit.

Select the shape of the restricted area as a circle. Circle The switch colour code indicates the selection status. YELLOW = Selected Background = Not selected

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

Circle radius. RADIUS Up to three numeric characters. The entered value is considered as Km.

Select the shape of the restricted area as a polygon.

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

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

Points GGGMMSSLggmmssl where: GGG: from 000 to 180 MM: from 00 to 59 SS: from 00 to 59

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

Table 6.2.11.1.4-1. Restricted Areas Window. Layout Area


L: N or S gg: from 00 to 90 mm: from 00 to 59 ss: from 00 to 59 l:

6.2.11.1.5

E or W or Up to 7 alphanumeric characters

COMMAND AREA

Figure 6.2.11.1.5-1. Restricted Areas Window. Command Area

Commands included in this area are described in following table:

Table 6.2.11.1.5-1. Restricted Areas Window. Command Area

Icon/Switch Command

Display the data of the selected restricted area. View

Create a new restricted area. Create

Modify a restricted area. Modify

Delete a restricted area. Cancel


Request the existing restricted area list. LIST SUMMARY


CLOSE

Delete the data displayed on the window fields. CLEAR

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

PRELIMINARY COPY


FDD-UM




6.2.11.1.5.2 ACTION: CREATE RESTRICTED AREA ACTION

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

RESULT

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

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


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

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.11.1.5.3 ACTION: MODIFY RESTRICTED AREA ACTION

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

RESULT


2. Modify the required fields.


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

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

RESULT



Compulsory Fields: Area ID.

6.2.11.1.6


ERROR MESSAGE AREA


PRELIMINARY COPY


FDD-UM




6.2.12

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

Icon [FLOW] Air Traffic Flow

Figure 6.2.12-1. [FLOW] Icon

When selection the (F. FP) option, 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 6.2.12-2. FPs Traffic Flow Options

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

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

Figure 6.2.12.1-1. Flow FP Window

Command Area

Filters Edition Area

Command Area

Filters Edition Area

PRELIMINARY COPY


FDD-UM




6.2.12.1.1

Following table lists for each field included in the Flow FP Window, a description with their valid data.

FILTERS EDITION AREA

Table 6.2.12.1.1-1. Flow FP Window. Filters Edition Area


Airport identification / Fix point identification / Sector identification.

Aerodrome / Fix / Sector Known by the System

Lower temporal limit (time) for filtering the FPLs (FROM) FROM HHMM, where HH = hour (00 to 23) MM = minutes (00 to 59)

Upper temporal limit (time) for filtering the FPLs (TO) UNTIL HHMM, where HH = hour (00 to 23) MM

= minutes (00 to 59)

6.2.12.1.2

Following table shows the different commands included in the Flow FP Window.

COMMAND AREA

Table 6.2.12.1.2-1. Flow FP Window. Command Area

Icon Command

Display the FPs Traffic Flow List. F.LIST

Displays the FPs Congestion Chart C. CHART

Close the Flow FP Window. CLOSE

Delete the information displayed on the Flow FP Window. CLEAR

6.2.12.1.2.1 ACTION: FPLS FLOW ACTION

1. Click with the LB on the [FLOW] icon.

RESULT

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

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

ACTION

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

RESULT

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:

PRELIMINARY COPY


FDD-UM




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

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

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.

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

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 [CLOSE] icon. For detailed information see 6.2.12.3.

Compulsory Fields: For the Aerodrome Element: the “Aerodrome” field For the Fix Element: the “FixPoint” field. For the Sector Element: the “Sector” field.

PRELIMINARY COPY


FDD-UM




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

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:

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

List by Aerodrome

Figure 6.2.12.2-1. FP Found for the given filter

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

Table 6.2.12.2-1. FPs Traffic Flow List. Aerodrome

Element Description

Arrival FPs ARRIVALS

Departure FPs DEPARTURES

Departure Aerodrome ORIGIN

Aircraft Identification CALLSIGN



Aircraft Type TYPE

Estimated Time of Arrival / Estimated Time of Departure ETA/ETD

Destination Aerodrome DESTINY




Aircraft Type TYPE

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

List by Fix


PRELIMINARY COPY


FDD-UM




Table 6.2.12.2-2. FPs Traffic Flow List. Fix

Element Description

Arrival FPs ARRIVALS

Departure FPs DEPARTURES






Aircraft Type TYPE

Flight Level LEVEL

Estimated Time Over a significant point ETO






Aircraft Type TYPE

Flight Level LEVEL

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.

List by Sector

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010


Table 6.2.12.2-3. FPs Traffic Flow List. Sector

Element Description






Aircraft Type TYPE

Flight Level LEVEL

Flight Plan Route ROUTE

PRELIMINARY COPY


FDD-UM




6.2.12.2.1

Table 6.2.12.2.1-1. FPs Traffic Flow List. Command Area

COMMAND AREA

Icon Description

Close the FPs Traffic Flow List CLOSE

Print the FPs Traffic Flow List PRINT

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

Figure 6.2.12.2.1-1. FP Operation Window from Flow List

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

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

Figure 6.2.12.3-1. FPs Traffic Congestion List Graphic

Table 6.2.12.3-1. FPs Traffic Congestion List Graphic. Edition Area

Element Description

Starting time for filter application. From

Ending time for filter application. To

Table 6.2.12.3-2. FPs Traffic Congestion List Graphic. Graphical Area

Element Description

Number of flights (different or repetitive), which passed within the predefined interval by the sector/ fix/ aerodrome.

Sector/ Fixpoint/ Aerodrome Overpasses

Application time in the graphic. Time

Tittle

Edition Area

Graphical Area

Command Area

PRELIMINARY COPY


FDD-UM




Table 6.2.12.3-3. FPs Traffic Congestion List Graphic. Command Area

Element Description

Time interval longitude to perform the graphic. Interval length

Close the FPs Traffic Congestion List. CLOSE

Not applicable. PRINT

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.13

Following meteorological messages are received from the AFTN and AIS and are automatically processed by the System:

Icon [METEO MSG] Meteorological Data

METAR;

SPECI;

TAF;

SIGMET;

ATIS;

AIRMET;

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 6.2.13-1. [METEO MSG] 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

PRELIMINARY COPY


FDD-UM




issued are severe or greater turbulence over a 3000 square mile area or severe or greater icing over a 3000 sq mile area or IMC conditions over a 3000 sq mile area due to dust, sand, or volcanic ash.

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 or Special Meteorological Aeronautical Report.

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.13.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 6.2.13.1-1. Meteorological Information Window

6.2.13.1.1

The window title depends on the selected message when clicking on the [METEO MSG] icon.

SELECTED MESSAGE

6.2.13.1.2

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.

AIRPORT SELECTION

6.2.13.1.3

It is formed by three fields, which are described in following table:

EDITION AREA

Table 6.2.13.1.3-1. Meteorological Information Window. Edition Area

Field Description

Define the starting date DDHHMM (DD – Day, HH – Hour, MM – Minutes)

From

Define the ending date DDHHMM (DD – Day, HH – Hour, MM – Minutes)

To

Free Text Text

PRELIMINARY COPY


FDD-UM




The vertical and horizontal scroll bars allow the visualization of the text not in view due to window size.

6.2.13.1.4

Following table shows the different commands included in the Meteorological Information Window.

COMMAND AREA

Table 6.2.13.1.4-1. Meteorological Information Window. Command Area

Icon/Switch Command

Allow the data input within the corresponding fields. Edit

Send the edited message, but the window remains displayed. OK

Close the Meteorological Information Window. CLOSE

Delete the information displayed in the Meteorological Information Window. CLEAR

Print the data included in the Meteorological Information Window. PRINT

6.2.13.1.4.1 ACTION: EDIT METEOROLOGICAL PAGE ACTION

1. Click with the LB on the [METEO MSG] icon.

RESULT

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.


PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.14

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.

[NOTAM] Icon

Figure 6.2.14-1. [NOTAM] Icon

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

PRELIMINARY COPY


FDD-UM




Figure 6.2.14.1-1. NOTAM Operation/Retrieval Window

6.2.14.2 Edition Area

Following table describes the fields included in the NOTAM Operation/Retrieval Window and the correct values:

Table 6.2.14.2-1. NOTAM Operation/Retrieval Window. Edition Area


NOTAM identification type ID A or B plus 4 numeric characters plus “/” plus YY, where YY = year (00 to 99)

Airport Field A) ICAO airport indicator. 4 alphabetic characters.

Level Field F) Hundreds of feet: Fxxx where xxx 000 to 999 Tens of meters: Sxxxx where xxx 0000 to 9999

Level Field G) 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.

Following string: REMAINDER

“/”

Edition Area

Command Area

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

Table 6.2.14.2-1. NOTAM Operation/Retrieval Window. Edition Area

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)

Free text Field E) TEXT Up to 2100 characters.

PRELIMINARY COPY


FDD-UM




6.2.14.3 Command Area

Following table shows the commands included in the NOTAM Operation/ Retrieval Window.

Table 6.2.14.3-1. NOTAM Operation/ Retrieval Window. Command Area

Icon/Switch Command

Display the NOTAM data. View

Create a new NOTAM. Creation

Modify an existing NOTAM. Modify

Delete an existing NOTAM. Cancel

Display all NOTAM included in the database. Retrieve Multiple

Print the single NOTAMs. PRINT

Trigger all input data. OK

Close the NOTAM Operation/Retrieval Window. CLOSE

Delete the data displayed on the NOTAM Operation/Retrieval Window. CLEAR

6.2.14.3.1 ACTION: COMMON ACTION TO NOTAM PROCEDURES

ACTION

1. Click with the LB on the [NOTAM] icon.

RESULT

The System displays the NOTAM Operation/Retrieval Window in visualization mode ([View] switch selected). All fields are accessible except “ID” field.

From this point on, actions are described according to command procedure.

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.14.3.2 ACTION: CREATE A NEW NOTAM ACTION

1. Click with the LB on the [Crea.] switch

RESULT

The switch becomes YELLOW. All fields are accessible to input data.

2. Enter the data.


Compulsory Fields: ID, FIR, Code, Stat, From and Until.

PRELIMINARY COPY


FDD-UM




6.2.14.3.3 ACTION: MODIFY NOTAM ACTION

1. Perform the visualize NOTAM action (see

RESULT

6.2.14.3.1).

2. Click with the LB on the [Mod.] switch. The switch becomes YELLOW. All fields are accessible.

3. Modify the required fields. Some of them do not allow to be changed. Some others are mandatory.


Compulsory Fields: ID but only if the NOTAM visualization action was not previously performed.

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.14.3.4 ACTION: CANCEL NOTAM ACTION


RESULT

6.2.14.3.1).

2. Click with the LB on the [Can.] switch. 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.

PRELIMINARY COPY


FDD-UM




6.2.14.3.5 ACTION: RETRIEVE MULTIPLE NOTAM ACTION


RESULT

6.2.14.3.1).

2. Click with the LB on the [Mul.] switch The switch becomes YELLOW.

3. Click with the LB on the [OK] icon The NOTAM Multiple Window is automatically displayed on top.



6.2.14.4 Error Message Area


A list of error messages is provided in Appendix E

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.15

This icon allows performing all actions related to the traffic flow.

When clicking on it, a menu is displayed as shown in following figure:

Icon [T. Flow] Traffic Flow

Figure 6.2.15-1. [T. Flow] icon

This 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/Slot Ret)

(FPs) Displays the Retrieve FP’s Flow Window.

– When clicking on this option, a pull-down submenu is displayed to select the FP or Slots retrieval filters. The displayed options are:

(Slots) Displays the Retrieve Slots Flow Window.

Figure 6.2.15-2. [T. Flow] icon. (Retrieve) Option

6.2.15.1 FP Flow Actions Window

This window is displayed when selecting the (FP Act.) option from the menu displayed by clicking on the [T. Flow].

This window allows the FPs traffic distribution for crossing the defined element (fix point), either automatically or manually.

PRELIMINARY COPY


FDD-UM




Figure 6.2.15.1-1. FP Flow Actions Window

6.2.15.1.1

This area includes fields, which are described in following table:

EDITION AREA

Table 6.2.15.1.1-1. FP Flow Actions Window. Edition Area

Field Description

Fix point F.ELEMENT

Aircraft identification CALLSIGN

Departure Aerodrome DEPARTURE

FP1 FP 1

FP2 FP 2



Destination Aerodrome DEST

Slot starting time (not editable) SLOT START

Time when the slot is overflown (not editable) OVF. TIME

FP allocation time. If the value is not introduced, it is automatically filled in. ALLOC. TIME

6.2.15.1.2

The commands included in this area are described in following table:

COMMAND AREA

Table 6.2.15.1.2-1. FP Flow Actions Window. Command Area

Icon/Switch Command

Allocate a FP (passive) to an element (fix) Allocate

Exchange between FPs (FP1-FP2) Exchange

Delete the FP Release

Command Area Edition Area

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

Table 6.2.15.1.2-1. FP Flow Actions Window. Command Area

Icon/Switch Command

Trigger the actions performed in current window OK

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


6.2.15.1.2.1 ACTION: ALLOCATE FP TO AN ELEMENT (FIX POINT)

ACTION

1. Click with the LB on the [T.Flow] icon.

RESULT

A menu is displayed.

2. Select the [FP Act.] option. The FP Flow Actions window is displayed with the edit fields accessible.

The [Allocate] switch is activated.

3. Input the data in the correspondent fields.

4. The operative is ended with an ending action procedure. (3.7).

PRELIMINARY COPY


FDD-UM




6.2.15.1.2.2 ACTION: EXCHANGE THE FP DISTRIBUTION

ACTION

1. Click with LB on the [T.Flow] icon.

RESULT


2. Select the [FP Act.] option. The FP Flow Actions Window is displayed with the editing fields accessible.



4. Click with the LB on the [Exchange] switch. The FP 2 correspondent fields are activated (turn WHITE).

5. Input the data in the second FP correspondent fields

6. The operative is ended with an ending action procedure (3.7).

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.15.1.2.3 ACTION: CANCEL AN FP DISTRIBUTION

ACTION


RESULT


2. Select the [FP Act.] option. The FP Flow Actions Window is displayed with the edition fields accessible.


3. Input data in the correspondent fields.

4. Click with the LB on the [Release] switch.

5. The operative is ended with an ending action procedure 3.7).

6.2.15.2 Flow Restrictions Window

This window is displayed when selecting the (Slot Act.) option from the menu displayed when clicking on the [T. Flow] icon.

This window defines the flow restrictions for a flow element (fix point).

PRELIMINARY COPY


FDD-UM




Figure 6.2.15.2-1. 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.

6.2.15.2.1

This area is formed by fields, which are described in following table:

EDITION AREA

Table 6.2.15.2.1-1. Flow Restrictions Window. Edition Area

Field Description

Fix Point F.ELEMENT

Slot starting time (fix) HHMM (HH – hour, MM – minutes)

FROM

Slot ending time (element-fix) HHMM (HH – hour, MM – minutes)

TO

2 numeric characters (FPs per hour) RANGE

Number of slots by element that can be created. 1, 2, 3

6.2.15.2.2


COMMAND AREA

Table 6.2.15.2.2-1. Flow Restrictions Window. Command Area

Icon/Switch Command

Display the FP Flow Actions Window. FP Act.

Display the Retrieve FP’s Flow Window. Ret. FP’s

Display the Retrieve FP’s Flow Window. Ret. Slots

Command Area

Edition Area

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

Table 6.2.15.2.2-1. Flow Restrictions Window. Command Area

Icon/Switch Command

Display the flow restriction data for the selected flow element (fix). View

Define the flow restrictions for a new flow element. Create

Modify the flow restrictions for the retrieved flow element. Modify

Delete the flow restrictions for the retrieved flow element. Cancel


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


6.2.15.2.2.1 ACTION: SLOT VISUALIZATION

ACTION


RESULT


2. Select the (Slot Act.) option. The Flow Restrictions Window is displayed.

3. Input data in the “F. Element” field.

4. The operative is ended by an ending action procedure (3.7).

PRELIMINARY COPY


FDD-UM




6.2.15.2.2.2 ACTION: SLOT CREATION

ACTION


RESULT



3. Click with the LB on the [Create] switch.


5. The operative is ended by an ending action procedure. (3.7).

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.15.2.2.3 ACTION: SLOTS MODIFYING

ACTION


RESULT



3. Execute the visualization action for the element (see point 6.2.15.2.2.1).

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

5. Modify data in the correspondent fields.

6. The operative is ended by an ending action procedure. (3.7).

PRELIMINARY COPY


FDD-UM




6.2.15.2.2.4 ACTION: CANCEL SLOTS

ACTION


RESULT


2. Select the (Slot Act.) option. The Flow Restrictions window is displayed.

3. Execute the visualization action for the selected element (see point 6.2.15.2.2.1)

4. Click with the LB on the [Cancel] switch.

5. The operative is concluded with an ending action procedure (3.7).

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.15.3 Retrieve FP’s Flow Window

This window is displayed when selecting the (FPs) option from the menu displayed when clicking on the (FPs/Slot Ret.) option from the [T. Flow] icon.

This window allows the retrieval of FPs overflying a selected flow element.

Figure 6.2.15.3-1. 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.

6.2.15.3.1

This area only includes the “F_ELEMENT” (fix) field. This field is the filter to retrieve the FPs overflying the selected flow element (fix).

EDITION AREA

6.2.15.3.2


COMMAND AREA

Edition Area

Command Area

Retrieved FP List

PRELIMINARY COPY


FDD-UM




Table 6.2.15.3.2-1. Retrieve FP’s Flow Window. Command Area

Icon/Switch Command

Retrieve and display all FPs allocated to the flow element (fix). Alloc

Retrieve and display all FPs, which are not allocated to the flow element (fix). Not Alloc


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


6.2.15.3.3

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:

RETRIEVED FPS LIST

ACID – Aircraft identification

DEP – Departure aerodrome

EOBT – Estimated off-block time

ADT – 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”.

6.2.15.3.3.1 ACTION: FPS DISTRIBUTION MULTIPLE RECOVERY

ACTION

1. Select the (Retrieve) option.

RESULT


PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

2. Select the (FP) option. The Retrieve FP’s Flow Window is displayed.

3. Input the selection (element) values.

4. Click with the LB on the [OK] icon. The Retrieved FPs List is displayed including the distributed Flight Plans for the selected element.

The [Alloc] switch is activated and all Flight Plans assigned to the element are displayed.

To visualize the unassigned Flight Plans, click with the LB on the [Not Alloc] switch and repeat the procedure.

5. End the action by pressing on [CANCEL] icon. The window is closed.

6.2.15.4 Retrieve Slots Flow Window

This window is displayed when selecting the (Slots) option from the menu displayed when clicking on the (FPs/Slot Ret.) option from the [T. Flow] icon.

PRELIMINARY COPY


FDD-UM




This window allows the retrieval of the defined slots for a flow element.

Figure 6.2.15.4-1. 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.

6.2.15.4.1

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 [OK] 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.

EDITION AREA

Retrieved Slots List

Command Area

Edition Area

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

Figure 6.2.15.4.1-1. Rest. Slot Frame Window. Elements Window

6.2.15.4.2


COMMAND AREA

Table 6.2.15.4.2-1. Retrieve Slots Flow Window. Command Area

Icon/Switch Command

Display all Slots allocated to the fix. Alloc

Display all Slots not allocated to the fix. Not Alloc


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


PRELIMINARY COPY


FDD-UM




6.2.15.4.3

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:

RETRIEVED SLOTS LIST

Slot START Time – Slot starting time

Slot END Time – Slot final time

6.2.15.4.3.1 ACTION: RETRIEVE MULTIPLE SLOTS DISTRIBUTION ACTION


RESULT


2. Select the (Retrieve) option. A submenu is displayed.

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

ACTION

3. Select the (Slot) option.

RESULT

The Retrieve Slots Flow Window is displayed.

4. Enter the selection values (element).

5. Click with the LB on the [OK] icon. The Retrieved Slots List is displayed including the Slots distributed by the selected element.

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.

PRELIMINARY COPY


FDD-UM




ACTION

6. If clicking on the [OK] icon without entered any element.

RESULT

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.

7. Finish the action by clicking on the [CANCEL] icon The window is closed.

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.16

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.

Icon [LINES] AFTN Lines Status

Figure 6.2.16-1. [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 6.2.16-2. 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.

PRELIMINARY COPY


FDD-UM




6.2.17

This icon displays the PIP Windows that shows the AIP (Aeronautical Information Publication).

[PIP] Icon

Figure 6.2.17-1. [PIP] Icon

6.2.17.1 PIP Window

The PIP Windows 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 6.2.17.1-1. PIP Window

This Window shows hyperlinks to every necessary document. Selecting a hyperlink, the user has the possibility to show the document.

6.2.17.1.1

Table 6.2.17.1.1-1. PIP Window. Command Area

COMMAND AREA

Icon/Switch Command

Shows the last selected document. Back

Go up to the main menu of the “PIP Window” Home

Close the “PIP Window”. Exit

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.18 Icon [EST] Estimate

Figure 6.2.18-1. [EST] Icon

This icon displays the EST Window that performs a quick estimate without having to access to the FP Operation Window.

Figure 6.2.18-2. 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.

6.2.18.1 EST Window

This window allows performing a quick EST operation.

Figure 6.2.18.1-1. 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.

PRELIMINARY COPY


FDD-UM




6.2.18.1.1

Following table presents for each field included in the EST Window, a description.

EDITION AREA

Table 6.2.18.1.1-1. EST Window. Edition Area

Field Description

Aircraft identification CALLSIGN

Fix name FIX

Aircraft speed SPEED

Estimated time over fix. ETO

Flight level of the aircraft when fly over the fix. CFL

SSR code CSSR

6.2.18.1.2

Following table describes the different commands included in the EST Window.

COMMAND AREA

Table 6.2.18.1.2-1. EST Window. Command Area

Icon/Switch Command

Perform the EST action over the entered fix (if data are correct). OK

Delete the data displayed on the EST Window. CLEAR

6.2.18.1.2.1 ACTION: QUICK ESTIMATE PROCEDURE ACTION

1. Click on the [EST] icon

RESULT

A window to edit the Fixpoint, ETO, Level and Speed is displayed.

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

ACTION

2. Enter the callsign value in the corresponding field and press <Enter> key.

RESULT

Some fields are filled out automatically.

3. Fill out the fields and click [OK] The window is closed and the estimated time over the entered fix point is performed.

4. To cancel the action: 4.1. Click with the LB the [EST] icon again.

The window is closed without validating the entered data.

PRELIMINARY COPY


FDD-UM




6.2.19

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.

[PRINTER1]

Figure 6.2.19-1. Printer Selection

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

6.2.20

By selecting this icon, the position is blocked, so it is not possible to perform any action.

[LOGOUT] Icon

Figure 6.2.20-1. [LOGOUT] Icon

At the same time, it displays the Login Window to unlock the position.

Figure 6.2.20-2. 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 <Enter>.

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.

6.2.20.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 <Enter> key. The position is unfrozen.

PRELIMINARY COPY


FDD-UM





PRELIMINARY COPY


PRELIMINARY COPY


FDD-UM



Apéndice / Appendix A Página / Page 1 de / of 22

A.APÉNDICE / APPENDIX A

FP ROUTE

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

A. FP ROUTE

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

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

PRELIMINARY COPY


FDD-UM




First time the Routes List is displayed, after the FP analysis process, the Purged Route is automatically selected. If an error was detected in that field analysis, all characters will be displayed in reverse video mode; if no error is detected, they will be displayed in normal video mode.

The operator may modify the selected route in that moment or may select another one from the Routes List.

A.3 ROUTE FIELD ANALYSIS

Route Morphology

It is a field composed of characters. Its number will be different according to the field source. The maximum number of characters for a message coming from the AFTN network will be 320 and the maximum number or characters in a screen format will be 156.

The filed will consist of following characters:

Alphabetical: Capital letters within the range A..Z

Numerical: Digits within the range 0..9

Special: (,), *, y /.

Blank character

One or more blank characters will separate elements forming the field.

Elements with more than 30 characters will not be allowed. If there is an element with more than 30, it will be divided into two or more elements, having the first element the first 20 characters and the second one the remaining ones, taking into account these elements as morphological error.

Elements with characters different from the aforementioned ones will not be allowed.

Elements with just one character will not be allowed.

Elements exclusively including digits will not be allowed.

Elements exclusively including alphabetical characters will have a length between 2 and 7 characters.

Elements including alphanumerical characters, with or without special ones, will have a length between 2 and 29 characters.

Elements including special characters will have to fulfil following conditions, too:

1 Only two asterisks or none may be displayed within an element.

2 Only one parenthesis may be displayed within an element and always the open parenthesis, “(“, has to be previous to the close one, “)”.

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

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

TIME expresses the estimated time of point crossing level. It is a string of five characters in the form:

T c1 c2 c3 c4

where c1 is a digit. The two first digits, c1 c2, express the day absolute time, forming a number between 00 and 23, both inclusively. The two remaining digits, c3 c4, express the hour minutes, forming a number between 00 and 59, both inclusively.

LEVEL expresses the included level or the one is desired to reach when crossing a point. It is a string of four or five characters, depending on the units it is expressed. The first character will be a letter indicating the measurement unit it is being used.

a) Altitude in hundredths of feet:

A c1 c2 c3.

Where ci is a digit.

b) Flight Level:

F c1 c2 c3.


c) Altitude in tenths of meters:

M c1 c2 c3 c4.


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.


b) Speed in knots.

N c1 c2 c3 c4.


PRELIMINARY COPY


FDD-UM




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.

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.

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

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.


Expression of a point in Bearing and Range with respect to a navigational aid

String of 8 to 11 characters as follows:

a1 a2 c1 c2 c3 c4 c5 c6

a1 a2 a3 c1 c2 c3 c4 c5 c6

a1 a2 a3 a4 c1 c2 c3 c4 c5 c6

a1 a2 a3 a4 a5 c1 c2 c3 c4 c5 c6

Being ci a digit and ai a letter.

The characters set (ai) identify a POINT. The three first characters show the bearing from the navaid, giving the magnetic degrees. They will consist of a number between 0 and 359, both inclusively.

The three last digits show the range from the navaid, giving the nautical miles. They will consist of a number between 0 and 999, both inclusively.


FICTITIOUS POINT

It expresses a point over the line joining other two Route points.


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.

PRELIMINARY COPY


FDD-UM




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.

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

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010


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.

SPEED AND LEVEL ELEMENT

Speed and Level Element associated with a point with hour.


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:

PRELIMINARY COPY


FDD-UM




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) means that they are as much elements COORD_KEYWORDS followed as desired.

FICTITIOUS POINTS SEQUENCE


POINTFICTITIOUS.POINT (/FICTITIOUS.POINT)POINT_KEYWORDS Where FICTITIOUS POINT is a fictitious point.

It will be checked that both POINT and POINT_KEYWORDS are not within the external airspace to the one controlled by the System.

It will be checked that all fictitious points are internal to the airspace controlled by the System.

The sum of all distances between each fictitious point and the previous one has to be lower than the distance between POINT and POINT_KEYWORDS. The number of fictitious points followed by a sequence is optional. If within any of the checks last condition is not fulfilled, all the sequence fictitious points will be marked with SYNTAX_ERROR.

DR SEQUENCE


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


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


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

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

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

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.

PRELIMINARY COPY


FDD-UM




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.

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.

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

The Purged Route length, as Algorithm output, is fixed. If there are more than 156 characters in the Purged Route, only first 156 will be displayed. Only whole elements, none will be split; if when displaying 156 characters, the last element is split, it will be completely deleted and the characters will be fulfilled with blank characters.

Calculated Route

If the departure aerodrome belongs to the System controlled airspace and the first Route element is not a procedure designator, the System will try to recognize a departure procedure from the information included in the Route field.

A departure procedure will consist of a points’ succession making up a departure runway from an aerodrome. It will allow linking the aerodrome, if it belongs to the System controlled airspace, with an airway. Through the last point of the departure procedure sequence, one airway, at least, will cross; that point will be defined as Transition Fix Point.

The System will try to recognize a departure procedure from the Route field elements in following cases:

a. First element is an airway:

If that airway crosses a Transition Fix Point of that aerodrome, the point will be inserted and a procedure will be recognized.

If the airway crosses more than one Transition Fix Point of that aerodrome, a fix point will be selected and a procedure will be recognized if:

a.1 The element subsequent to the airway is a point belonging to the airway.

a.2 The selected Fix Point, without being identical to the point subsequent to the airway, is the one with lower number of intermediate points in the airway to go to the subsequent point.

b. First Route elements make up a points sequence not linked by DCT keywords:

The system will select that departure procedure containing the sequence points and in the expressed order. If no procedure is found fulfilling the conditions, no procedure will be considered.

If the destination aerodrome belongs to the System controlled airspace and the last Route element is not the procedure designator, the System will try to recognize an arrival procedure from the information included in the Route field.

An arrival procedure will consist in a points’ succession making up an arrival runway to an aerodrome. It will allow linking the aerodrome, if it belongs to the System controlled airspace, with an airway. Through the first point of the arrival procedure sequence, one airway, at least, will cross; that point will be defined as Transition Fix Point.

The System will try to recognize an arrival procedure from the Route Field elements in following cases:

a. Last element is an airway:

If that airway crosses a Transition Fix Point of that aerodrome, the point will be inserted and a procedure will be recognized. If the airway crosses more than one Transition Fix Point of that aerodrome, a Fix Point will be selected and a procedure will be recognized if:

a.1 The element before the airway is a point belonging to the airway.

PRELIMINARY COPY


FDD-UM




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} DCT BOUNDARY_point_BOUNDARY_coordinate {Non_SACTA Destination}

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

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.

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

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

PRELIMINARY COPY


FDD-UM




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 AWY_1 will be marked with DISCONTINUITY_ERROR.

Remaining situations will cause POINT and AWY_1 to be marked with DISCONTINUITY_ERROR.

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.

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

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

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.

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.

PRELIMINARY COPY


FDD-UM




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:



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:



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:



c.) It is a FIX POINT or a COORDINATE.

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.

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:

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

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.

PRELIMINARY COPY


FDD-UM




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


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


Finally, boundary points in the extremes of the different obtained sections will be calculated.

For the left section extreme, following cases will be presented:

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

1 Sequence:

Boundary_pointRemaining_elements

The boundary point is presented and there is no need of calculation.

2 Sequence:

Internal_point_with_IFR_keyword Remaining_elements

The boundary point is not calculated.

3 Sequences:

Point_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:

1 Sequence:

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

PRELIMINARY COPY


FDD-UM




Continuity between Point_1 and Point_2. With Point_1 point external to the System and Point_2 point internal to the System; an intermediate point matching the border will be calculated. The calculated point will replace Point_1 and the VALIDATE_BOUNDARY_POINT error will mark it.

9 Sequences:

Remaining_elementsPoints_2 Points_1

With Point_1 and Point_2 points internal to the System and being continuous the route defined by those points, both belong to one airway crossing through them and fulfilling direction and level conditions. That airway will be travelled in the direction (Point_2 => Point_1); if a boundary point is found subsequent to Point_1, the points belonging to the airway will be inserted into the Route elements:

Point_subsequent_to_Point_1 ... Point_to Boundary_point

These last points will be marked to validate them with VALIDATE_BOUNDARY_POINT error.

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 Departure} BOUNDARY_point/BOUNDARY_coordinate DCT {Non_Sacta Destination}

{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:

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

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.

PRELIMINARY COPY


FDD-UM



Apéndice / Appendix B Página / Page 1 de / of 2

B.APÉNDICE / APPENDIX B

ERRORS DISPLAY

PRELIMINARY COPY


FDD-UM


Apéndice / Appendix B Página / Page 2 de / of 2


Fecha / Date: 04/05/2010

B. 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, …

PRELIMINARY COPY


FDD-UM



Apéndice / Appendix C Página / Page 1 de / of 2

C.APÉNDICE / APPENDIX C

ROUTE FIELD MESSAGES

PRELIMINARY COPY


FDD-UM


Apéndice / Appendix C Página / Page 2 de / of 2


Fecha / Date: 04/05/2010

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

PRELIMINARY COPY


FDD-UM



Apéndice / Appendix D Página / Page 1 de / of 4

D.APÉNDICE / APPENDIX D

ERROR MESSAGE OF ROUTE FIELD

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

D. ERROR MESSAGE OF ROUTE FIELD

D.1 INCORRECT EDITION

Description

A Morphological error has been detected in the analysis; the erroneous element is underlined when displayed.

Erroneous field correction.

User Options

There are two options for the user:

Rejection of the function in process.

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


Rejection of the function in process.

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

PRELIMINARY COPY


FDD-UM






Current function rejection.

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

Discontinuity deletion by following the continuity criteria as established in point 3 of this annex.

User Options


Function rejection.

D.5 VALIDATE BOUNDARY POINT

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.

Description

This message may happen in some of the following circumstances:

When a boundary point is calculated by going through an airway until reaching the border. All inserted points are underlined.

Change the current route for the calculated one and click to validate the boundary point.

User Options

As follows:

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010


PRELIMINARY COPY


FDD-UM



Apéndice / Appendix E Página / Page 1 de / of 12

E.APÉNDICE / APPENDIX E

LOCAL FUNCTIONS ERROR MESSAGES

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

E. LOCAL FUNCTIONS ERROR MESSAGES

MESSAGE DESCRIPTION

Correct

Compulsory

Syntactic

New call sign in use

Rank error

PRELIMINARY COPY


FDD-UM




Unknown element

Error field

Element not accessible

Incoherence

Discontinuity

FIR time not computable

External point expected

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

Validate boundary point

Impossible modify ETD

Too segments

Too points

Extraction error

Too sectors

Message not allowed

Incoherent FP date

Incoherent PPL date

Already in use

Area not found

Area already existing

PRELIMINARY COPY


FDD-UM




Correct analysis

Flight plan already exists

Full file

Inaccessible FP

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

FDD not allowed

Different shape to adapted

Illegal modif. of operative area

PRELIMINARY COPY


FDD-UM




Line is offline

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

Success

Impossible Trans Received Msg

Queuing not allowed

Queue is full

None found

No response

Unknown message type

Illegal shape

PRELIMINARY COPY


FDD-UM




Printer unavailable

No data available

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

Exceeded capacity

Illegal modif. of active area

PRELIMINARY COPY


FDD-UM




No FPs for this filter

Timeout error

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010


PRELIMINARY COPY


FDD-UM



Apéndice / Appendix F Página / Page 1 de / of 26

F.APÉNDICE / APPENDIX F

COORDINATION MESSAGES

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

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 (OLDI). In either case, it is possible to proceed with the coordination phases in different ways:

Fully automatic (either OLDI notification or OLDI coordination): the System proceeds on a planned schedule;

Semi-automatic (either OLDI notification or coordination): the transferring controller manually initiates the automatic procedure;

Manual (OLDI coordination): the transferring controller enters into communication with his counterpart at the receiving sector, and agrees on the coordination phase data.

The flight to be coordinated for exit from the Upstream sector is presented in the Flight Plan list, in the Active section. The XCOORD fields are affected by the coordination process.

The System implements the following coordination basic procedure mandatory messages using OLDI: ABI, ACT, REV, PAC, MAC and LAM, in ICAO format.

The System implements the following coordination basic procedure complementary messages using OLDI: COD, in ICAO format.

The System also implements the coordination dialogue procedure messages in ICAO format. The capacity to upgrade the dialogue procedure for the transfer phase is performed using ICAO and ADEXP format messages if necessary.

If a controller performs a manual coordination, following automatic steps are inhibited.

The reception of messages at either sector (Uperstream or Downstream) is reflected in the FP history of the corresponding flight plan (except LAM message).

When sending out coordination messages, the System provides the adjacent centre with COP, exit flight level (XFL) and ETO data.

If no XFL is entered, the System uses the entered CFL, if any, or the adapted XFL.

The System provides the controller with the capability of updating coordination level and time prior to the automatic message sending, for OLDI.

PRELIMINARY COPY


FDD-UM




F.2 ONLINE DATA INTERCHANGE (OLDI) COORDINATION

Notification Phase

Upstream Sector

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 a LAM 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 LAM message is not received, the “Status” field displays “ABI LTO” (ABI LAM time-out) for the corresponding flight plan.

The System sends a MAC message to indicate to the Downstream sector that the notification previously effected for a flight is being abrogated.

If a LAM 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 LAM message is not received, the “Status” field displays “MAC LTO” (MAC LAM 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 ACT message transmission time parameters.

If a LAM 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 LAM message is not received, the “Status” field displays “PAC LTO” (PAC LAM time-out) for the corresponding flight plan.

If the Upstream sector receives a COD message, which has no errors, it sends back a LAM message to the Downstream sector.

Downstream sector

If received messages are correct, the Downstream sector sends back a LAM 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 then are re-processed 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 or terminated status (depending on INICAN field). 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. The Downstream sector sends a COD message, in response to a PAC message, to inform the transferring sector of the requested Mode A SSR code.

Coordination Phase

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

Upstream sector

An adapted time before COP (but after ABI message time), the Upstream sector sends an ACT message (this is a mandatory action for the coordination process) to initiate coordination with the Downstream sector. The controller may also initiate a semi-automatic notification phase. If the controller starts a SEND ACT command, the Upstream sector sends an ACT message to initiate coordination with the Downstream sector.

In either case, if a LAM message is received in return, the “Status” field displays “ACT RCV” (ACT received) for the corresponding flight in the Flight Plan list. If after an adapted timeout the LAM message is not received, the “Status” field displays “ACT LTO” (ACT LAM time-out) for the corresponding flight plan, with ‘LTO’ in RED.

In any case, the Upstream controller may manually coordinate with the Downstream controller. Then upon clicking COORD-OK 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 REV message to modify coordination data with the Downstream sector (not for manual coordination).

If a LAM message is received in return, the “Status” field displays “REV RCV” (REV received) for the corresponding flight in the Flight Plan list. If after an adapted timeout the LAM message is not received, the “Status” field displays “REV LTO” (REV LAM time-out) for the corresponding flight plan, with ‘LTO’ in RED.

In this case, the Upstream controller may initiate a verbal revision with the Downstream controller. Then upon clicking COORD-OK 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 a LAM 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 LAM message is not received, the “Status” field displays “MAC LTO” (MAC LAM time-out) for the corresponding flight plan, with ‘LTO’ in RED.

Downstream sector

If received messages are correct, the Downstream sector sends back a LAM message to the Upstream sector. If ACT or REV messages contains errors, the Downstream sector sends them to the FPM queue. The corresponding operator may retrieve these messages from the FPM queue for editing and correction. If messages are corrected, they is 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 ACT 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 it is possible).

PRELIMINARY COPY


FDD-UM




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 or terminated status (depending on INICAN field). If a MAC message is received for an assumed flight, it is not updated.

Dialogue Procedure

Upstream sector

Prior to sending a coordination message to partners with which a dialogue procedure is configured, the System checks whether the transfer conditions comply with defined standard conditions. If the transfer conditions comply with the standard conditions and the Upstream controller does not require the flight to be referred to the Downstream sector for acceptance, the System proceeds as specified for the basic procedure (sending ACT/ REV messages). Otherwise, the System presents the coordination data to the controller before the coordination takes place, and highlights the non-standard conditions. If the transfer conditions do not comply with the standard conditions, the System sends RAP or RRV messages (instead of ACT or REV, respectively) to the Downstream sector.

If an SBY message is received in return, the “Status” field displays “RAP RCV”/ “RRP RCV” (RAP/ RRP received) for the corresponding flight in the Flight Plan list. If after an adapted timeout the SBY message is not received, the “Status” field displays “RAP STO”/ “RRP STO” (RAP/ RRP SBY time-out) for the corresponding flight plan, with ‘STO’ in RED.

After receiving an standby (SBY) message, the Upstream sector expects to receive either an acceptance, a rejection or a counter-proposal from the Downstream sector. The System is capable of sending an ACP or a RJC, to accept or to reject a proposed coordination or counter-coordination (CDN message) from the Downstream sector, upon manual command. Likewise, if the System receives an ACP or a RJC message, it sends back a LAM message to the Downstream sector.

Downstream sector

When the System receives a coordination message from a partner with which the dialogue procedure is configured, it checks whether transfer conditions comply with defined standard conditions. Upon dialogue initiation (with an RAP message), the FP Status at the Downstream sector changes to active. If the transfer conditions comply with the standard conditions, and the message was not a RAP/ RRV, the System sends back a LAM message to the Upstream sector. If the transfer conditions do not comply with the standard conditions, or the message was a RAP/ RRP, the System sends a SBY. When the System has replied with a SBY is referred to the sector at which the co-ordination is taking place. After sending an SBY, the System is capable of sending an ACP, a RJC or a CDN, either to accept or reject the transfer conditions, or to counter-propose new ones, upon manual command.

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

Likewise, the System sends back a LAM message to the Upstream sector upon receiving an ACP or a RJC (in response to the Down stream’s CDN message). The coordination is considered completed upon receipt or transmission of a LAM or ACP. If new transfer conditions are agreed, the Downstream sector updates its flight plans with the data extracted from these messages. Otherwise, the FP Status is reverted to notified.

Transfer Phase

The transfer phase is, on its part, divided in three sub-phases: initiation, revision and execution.

The System at all stages distributes the current stage of transfer, as well as the corresponding clearances or constraints, to the sectors involved in the transfer.

The Upperstream sector automatically sending a TIM message;

Initiation

The System provides the capacity to initiate the transfer phase in three ways:

The Downstream sector manually sending a ROF message, automatically responded by an Upperstream TIM message;

The Upperstream manually sending an SDM message.

The System provides the Upstream controller with the capacity of sending a HOP message in order to initiate a transfer to any sector, regardless of its presence on the route of flight.

The System permits to enable and disable the automatic HOP sending at the transferring sector.

The System provides the Downstream sector with the capacity of entering a “Skip” command so as to pass the transfer initiation to the next sector on the trajectory.

The Upperstream sector automatically sending an SDM message;

Revision

If there are transfer data to be modified, the System provides the capacity to perform the revision in two ways:

The Downstream sector manually sending a ROF message.

The Upperstream sector manually sending a COF message;

Execution

In order to complete the transfer, the System provides the capacity for:

The Downstream sector manually sending a MAS message.

F.3 AIDC COORDINATION MESSAGES

ABI (ADVANCE BOUNDARY INFORMATION)

PRELIMINARY COPY


FDD-UM




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)

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)

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

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.

ACP

REJ

Pre-Notifying Notifying Negotiating

Coordinating

Transferred Transferring Coordinated

Backward

Re-negotiating

ABI

ABI

CPL

MAC

MAC

Re-negotiating

ESTPAC

CDN

AOC TOC

ACP

ACP

CDN

CDN

CDN

ACP

CDN

REJ

MSG

MSG

MSG

LEGEND

MSG transmitted by the controlling ATS unit

MSG transmitted by the downstream ATS unit

MSG transmitted by either the controlling or

the downstream ATS unit

Figure F.3-1. Transitions of AIDC coordination messages

The system implements an AIDC messages management policy.

PRELIMINARY COPY


FDD-UM




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

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.

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

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 re-processed 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. 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-OK 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-OK 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.

PRELIMINARY COPY


FDD-UM




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

F.4 COORDINATION MESSAGES WINDOWS

1 ABI (Advanced Boundary Information)

a ABI Correction

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

b ABI in “Q” QUEUE

PRELIMINARY COPY


FDD-UM




2 ACP (Accept message)

3 CDN (Coordination message)

4 ACT (Activation Message)

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

5 AIDC (Air Traffic Services Interfacility Data Communications)

6 ARR (Arrival Message)

PRELIMINARY COPY


FDD-UM




7 CHG (Change Message)

8 CNL (Cancellation Message)

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

9 CPL Correction (Current Flight Plan)

10 DEP (Departure Message/List)

PRELIMINARY COPY


FDD-UM




11 DES (Data Exchange System)

12 DLA (ATS Message indicator for delay)

13 EST (Estimated)

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

14 FLS (Flight Suspension Message)

15 IFPL (Individual Flight Plan Message)

16 LAM (Logical Acknowledgement Message)

PRELIMINARY COPY


FDD-UM




17 LRM (Logical Rejection Message)

18 MAC (Message for the Abrogation of Coordination)

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

19 NOTAMC (Notice To Airmen Cancellation)

20 NOTAMN (Notice To Airmen N)

PRELIMINARY COPY


FDD-UM




21 NOTAMR (Notice To Airmen R)

22 PFL (Planned Flight Level)

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

23 REJ (Rejection Message)

24 REV (Revision Message)

25 RQP (Request Plan Message)

PRELIMINARY COPY


FDD-UM




26 SAM (Slot Allocation Message)

27 SLC (Side Lobe Cancellation)

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

28 SRM (Sector Revision Message)

29 SVC (Service)

PRELIMINARY COPY


FDD-UM




30 SVC RFP (Service for Repetitive Flight Plans)

PRELIMINARY COPY


FDD-UM




Fecha / Date: 04/05/2010

"Última página del documento" "The last page of the document"