PRELIMINARY COPY FOR TRAINING PURPOSE ONLY
advertisement
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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
RY
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Nombre
Name
Preparado
Prepared
Revisado
Revised
Aprobado
Approved
Autorizado
Authorized
C
Y
P
O
Carlos Martínez Ramos
Firma
Signature
INDRA
SE
Fecha
Date
Y
L
N
O
Cargo
Responsibility
Enginnering
Systems
Ana Isabel Moreno
Alcántara
Quality Manager
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.
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
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
II
SE
Y
L
N
O
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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
Edic./Rev.
Capítulo
Edic./Rev.
Capítulo
Edic./Rev.
Chapter
Edit./Rev.
Chapter
Edit./Rev.
Chapter
Edit./Rev.
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
Capítulo
Chapter
Edic./Rev.
Edit./Rev.
REGISTRO DE CAMBIOS EN EL DOCUMENTO
Document changes record
Edic./Rev.
Edit./Rev.
A/0
Fecha
Date
04/05/2010
Capítulos
Chapters
1-6, A-F
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Razón del Cambio
Reason for change
New Document
SE
Y
L
N
O
HOJA DE DISTRIBUCIÓN
Distribution sheet
Nº Copia
Copy no.
Empresa / Organismo
Company / Organization
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Departamento
Department
Nombre y Apellidos
Name and surname
III
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
ÍNDICE GENERAL
Table of contents
Capítulo
Chapter
Descripción
Página
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
Y
L
N
3.6
COMMON ACTIONS IN ALL FDD WINDOWS .................................................................................... 3-10
3.7
PROCEDURES TO CLOSE ACTIONS IN WINDOWS ......................................................................... 3-11
4.
RY
C
SE
O
DOCUMENTS ............................................................................................................................... 4-1
4.1
4.2
5.
5.1
5.2
6.
6.1
O
NA
I
P
R
IM
DEFINITIONS AND ACRONYMSL
................................................................................................
5-1
U
E
P
R
G
P
N
FUNCTIONAL AND OPERATIONAL DESCRIPTION
NI ................................................................. 6-1
I
A
R
T
R
O
F
APPLICABLE DOCUMENTS ................................................................................................................. 4-1
REFERENCE DOCUMENTS .................................................................................................................. 4-1
DEFINITIONS ......................................................................................................................................... 5-1
ACRONYMS ........................................................................................................................................... 5-7
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
6.1.2
6.1.2.1
IV
Y
P
O
Rules to Enter or Delete Data ......................................................................................................... 3-9
AFTN-NOTAM Messages Correction Window ........................................................................................ 6-12
“AAI” Queue: Erroneous AFTN Header Area (EAH) ................................................................... 6-14
“AAI” Messages De-queue .......................................................................................................................... 6-15
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
ÍNDICE GENERAL
Table of contents
Capítulo
Chapter
Descripción
Página
Description
Page
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
Y
P
O
Y
L
N
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
6.2.1.1.2.2
6.2.1.1.3
6.2.1.1.3.1
6.2.1.1.3.2
6.2.1.1.3.3
6.2.1.1.3.4
6.2.1.1.3.5
6.2.1.1.3.6
6.2.1.1.3.7
6.2.1.1.3.8
6.2.1.1.3.9
RY
C
SE
O
Rules for Entering Data ..................................................................................................................... 6-28
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
“Route” Field Validation Rules ........................................................................................................... 6-29
Command Area ........................................................................................................................................ 6-31
Action: Common Step to Actions on FPs .......................................................................................... 6-32
Action: Visualize FPL ......................................................................................................................... 6-32
Action: View List of FP Synonyms ..................................................................................................... 6-33
Action: FPL History ............................................................................................................................ 6-33
Action: Create FPL ............................................................................................................................ 6-34
Action: Create a Current FPL (CPL) .................................................................................................. 6-34
Action: Modify FPL ............................................................................................................................ 6-35
Action: Cancel FPL ............................................................................................................................ 6-35
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
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
V
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
ÍNDICE GENERAL
Table of contents
Capítulo
Chapter
Descripción
6.2.1.1.6
6.2.2
Page
Area Warnings Window ........................................................................................................................... 6-42
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.3
Error Message Area ................................................................................................................................. 6-47
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
Y
P
O
Minimal FP Window ..................................................................................................................................... 6-49
Y
L
N
6.2.3.1.1
Edition Area ............................................................................................................................................. 6-49
6.2.3.1.2
Command Area ........................................................................................................................................ 6-50
6.2.3.1.2.1
6.2.3.1.3
6.2.4
RY
C
SE
O
Action: Create a Minimal FP.............................................................................................................. 6-50
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Error Message Area ................................................................................................................................. 6-50
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.4.1.3
6.2.5
Error Message Area ................................................................................................................................. 6-55
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
6.2.5.1.3
6.2.5.2
6.2.6
Action: Retrieve Multiple RPLs .......................................................................................................... 6-58
Error Message Area ................................................................................................................................. 6-58
Retrieved RPLs Window .............................................................................................................................. 6-59
Icon [Runw] Airport Runways Actions ........................................................................................ 6-60
6.2.6.1
6.2.6.1.1
VI
Página
Description
Airport Runways Window ............................................................................................................................ 6-60
Edition Area ............................................................................................................................................. 6-60
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
ÍNDICE GENERAL
Table of contents
Capítulo
Chapter
Descripción
Página
Description
6.2.6.1.2
Page
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.6.1.3
6.2.7
Error Message Area ................................................................................................................................. 6-61
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
6.2.7.1.3
6.2.7.2
Action: Edit/Transmit ICAO AFTN Messages .................................................................................... 6-68
Y
P
O
Error Message Area ................................................................................................................................. 6-69
Y
L
N
ICAO ADEXP Transmission Window .......................................................................................................... 6-70
C
6.2.7.2.1
Edition Area ............................................................................................................................................. 6-70
6.2.7.2.2
Command Area ........................................................................................................................................ 6-75
6.2.7.2.2.1
6.2.7.2.3
6.2.7.3
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
O
Action: Edit/Transmit ICAO ADEXP Messages ................................................................................. 6-75
Error Message Area ................................................................................................................................. 6-76
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
6.2.7.3.3
6.2.7.4
Action: Edit/Transmit Text AFTN Messages...................................................................................... 6-79
Error Message Area ................................................................................................................................. 6-80
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
6.2.8
RY
Action: Transmit SVC Messages ....................................................................................................... 6-82
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
6.2.8.1.3
Action: Retrieve Multiple AFTN Messages ........................................................................................ 6-85
Error Message Area ................................................................................................................................. 6-86
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.2
Error Message Area ................................................................................................................................. 6-89
6.2.8.3.3
Command Area ........................................................................................................................................ 6-89
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
VII
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
ÍNDICE GENERAL
Table of contents
Capítulo
Descripción
Chapter
6.2.8.4
Page
OLDI Retrieve Window ................................................................................................................................. 6-90
6.2.8.4.1
Edition Area ............................................................................................................................................. 6-90
6.2.8.4.2
Error Message 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
Y
P
O
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.9.1.4
6.2.10
C
Y
L
N
Error Message Area ................................................................................................................................. 6-94
RY
SE
O
Icon [WINDS] Wind Data ............................................................................................................... 6-95
6.2.10.1
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
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.10.1.3
6.2.11
Error Message Area ................................................................................................................................. 6-97
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
6.2.12
Error Message Area ............................................................................................................................... 6-106
Icon [FLOW] Air Traffic Flow ...................................................................................................... 6-107
6.2.12.1
Flow FP Window ......................................................................................................................................... 6-107
6.2.12.1.1
VIII
Página
Description
Filters Edition Area ................................................................................................................................ 6-109
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
ÍNDICE GENERAL
Table of contents
Capítulo
Chapter
Descripción
6.2.12.1.2
6.2.12.2
Action: FPLs Flow ............................................................................................................................ 6-109
FPs Traffic Flow List .................................................................................................................................. 6-113
6.2.12.2.1
6.2.12.3
Page
Command Area ...................................................................................................................................... 6-109
6.2.12.1.2.1
6.2.13
Página
Description
Command Area ...................................................................................................................................... 6-117
FPs Traffic Congestion List ....................................................................................................................... 6-118
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
6.2.14
C
Y
P
O
Y
L
N
Action: Edit Meteorological Page..................................................................................................... 6-123
RY
SE
O
[NOTAM] Icon .............................................................................................................................. 6-124
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
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
6.2.14.3.2
6.2.14.3.3
6.2.14.3.4
6.2.14.3.5
6.2.14.4
6.2.15
Action: Common Action to NOTAM Procedures .................................................................................... 6-127
Action: Create a New NOTAM ............................................................................................................... 6-128
Action: Modify NOTAM .......................................................................................................................... 6-129
Action: Cancel NOTAM .......................................................................................................................... 6-130
Action: Retrieve Multiple NOTAM .......................................................................................................... 6-131
Error Message Area ................................................................................................................................... 6-131
Icon [T. Flow] Traffic Flow .......................................................................................................... 6-132
6.2.15.1
FP Flow Actions Window ........................................................................................................................... 6-132
6.2.15.1.1
6.2.15.1.2
Edition Area ........................................................................................................................................... 6-133
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
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
IX
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
ÍNDICE GENERAL
Table of contents
Capítulo
Chapter
Descripción
Description
Página
Page
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
6.2.15.4
Action: FPs Distribution Multiple Recovery ..................................................................................... 6-143
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
C
Y
P
O
Y
L
N
Action: Retrieve Multiple Slots Distribution...................................................................................... 6-147
RY
SE
O
6.2.16
Icon [LINES] AFTN Lines Status ................................................................................................ 6-150
6.2.17
[PIP] Icon ...................................................................................................................................... 6-151
6.2.17.1
6.2.17.1.1
6.2.18
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
PIP Window ................................................................................................................................................. 6-151
Command Area ...................................................................................................................................... 6-151
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
A.
Freeze Position ........................................................................................................................................... 6-156
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
X
INCORRECT EDITION .......................................................................................................................... D-2
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
ÍNDICE GENERAL
Table of contents
Capítulo
Descripción
Página
Chapter
D.2
Description
Page
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
RY
C
No se encontraron elementos de tabla de contenido.
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
SE
Y
L
N
O
XI
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
ÍNDICE FIGURAS
Figures index
Descripción
Description
Página
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
Y
P
O
Figure 6.1.1.4.1-1. AFTN-FP Correction Windows ................................................................................................ 6-9
Y
L
N
Figure 6.1.1.4.1.1-1. AFTN-FP Message Correction Window. Error ................................................................... 6-10
C
O
Figure 6.1.1.4.2-1. AFTN-NOTAM Messages Correction Window ...................................................................... 6-13
RY
SE
Figure 6.1.2-1. “AAI” Queue ................................................................................................................................ 6-14
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
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
XII
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
ÍNDICE FIGURAS
Figures index
Descripción
Description
Página
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
Y
P
O
Y
L
N
Figure 6.2.7.4-1. SVC Transmission Window ..................................................................................................... 6-81
C
Figure 6.2.8-1. [ARCHIVE] Icon .......................................................................................................................... 6-83
RY
O
Figure 6.2.8.1-1. AFTN Retrieve Window ........................................................................................................... 6-83
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
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-2. FP Found for the given filter................................................................................................. 6-114
Figure 6.2.12.2-3. FP Found for the given filter................................................................................................. 6-116
Figure 6.2.12.2.1-1. FP Operation Window from Flow List ............................................................................... 6-117
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
XIII
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
ÍNDICE FIGURAS
Figures index
Descripción
Description
Página
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
Y
P
O
Y
L
N
Figure 6.2.15.3-1. Retrieve FP’s Flow Window ................................................................................................. 6-142
C
Figure 6.2.15.4-1. Retrieve Slots Flow Window ................................................................................................ 6-145
RY
O
Figure 6.2.15.4.1-1. Rest. Slot Frame Window. Elements Window ................................................................... 6-146
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
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
Description
Página
Page
Table 3.5-1. Mouse Button Functions ................................................................................................................... 3-7
Table 3.5-2. Key Functions ................................................................................................................................... 3-9
XIV
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
ÍNDICE TABLAS
Tables index
Descripción
Description
Página
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
Y
P
O
Y
L
N
Table 6.2.1.1.2-1. FP Operation Window. Edition Area ...................................................................................... 6-25
C
Table 6.2.1.1.3-1. FP Operation Window (action mode). Command Area .......................................................... 6-31
RY
O
Table 6.2.1.1.6-1. Area Warnings Window ......................................................................................................... 6-43
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
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
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
XV
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
ÍNDICE TABLAS
Tables index
Descripción
Description
Página
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
Y
P
O
Y
L
N
Table 6.2.11.1.2-1. Restricted Areas Window. Description Area....................................................................... 6-101
C
Table 6.2.11.1.3-1. Restricted Areas Window. Activation/Validity Area ............................................................ 6-101
RY
O
Table 6.2.11.1.4-1. Restricted Areas Window. Layout Area .............................................................................. 6-103
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
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
XVI
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
ÍNDICE TABLAS
Tables index
Descripción
Description
Página
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.
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
SE
Y
L
N
O
XVII
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
O
Y
L
N
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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)).
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
SE
Y
L
N
O
Capítulo / Chapter 1
Página / Page 1 de / of 2
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
"Página dejada en blanco intencionadamente"
"This page intentionally left blank"
Capítulo / Chapter 1
Página / Page 2 de / of 2
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
2.
PURPOSE
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
SE
Y
L
N
O
Capítulo / Chapter 2
Página / Page 1 de / of 2
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
"Página dejada en blanco intencionadamente"
"This page intentionally left blank"
Capítulo / Chapter 2
Página / Page 2 de / of 2
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
Y
P
O
Y
L
The system modularity and distribution determines the software architecture, N
which uses distributed
C
discrete processes for the different subsystems for its organization. At the
same
time, the system
O
makes use of communication by messages, bothY
for intercommunications
between
tasks and for its
E
R
synchronicity. In order to assure a maximum
level
of
maintenance,
communications
and application
S
A
O
tasks have been isolated.
N
I
Pextensively in different emplacements
M
The software running in the systemI has been tested and proved
R
L Indra can P
U that no additional developments of any
and during longs periods and, therefore,
guarantee
E
kind are required for its correct
and
stable
operation.
R
G LINUX 4 UPDATE 4 X86_64.
P
The Operating System used is RED HAT ENTERPRISE
N
NI
I
A architecture for the AIRCON 2100 System:
Following figure shows a full-featured
R
T
R
O
F
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 3
Página / Page 1 de / of 12
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
C
Y
P
O
Y
L
N
O
E
AIRCON 2100 includes all the necessary functionality
modern
S ATC system. Its main
A required in a O
elements are following described:
N
I
P
M
The integration of all its subsystemsIis performed via:
R
LA redundant five P(5)Ucategory with a 1-Gigabyte bandwidth
Local Area Network (LAN).
E
R and, therefore, future
capacity LAN is used
updates of the system can be easily
G
P
implemented making use of standard communication
protocols.
N
I
N
Main components:
I
AIt is based on RISC redundant computers. It manages the
Flight Data Processing (FDP).
R
T the System or coming from external sources, including the
flight plans generated within
Repetitive Flight Plans
R (RPLs). It confirms all flight data inputs, calculates the flights’
progression and O
keeps all controllers inform by means of screen displays and flight plan
F
RY
Figure 3.1-1. System Architecture
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.
Capítulo / Chapter 3
Página / Page 2 de / of 12
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Controlling positions:
Situation Data Display (SDD). It is based on powerful workstations that receive data
processed by both the SDP and the FDP. Later on, it manages all these information for a
coherent displaying at the controllers screens (SDD). At the same time, it displays additional
relevant information such as geographic maps, meteorological data, etc.
Flight Data Display (FDD). It displays information concerning flight plans not supplying data
display of data on air situation. It allows controllers to perform adjustments on flight plans
and other significant data.
Control and Monitoring Display (CMD). It performs a continuous real time supervision of
the System. It also allows monitoring and System elements’ status change, sectorization
modification, management of certain configurable parameters, etc.
Auxiliary equipment:
Commom Timing Facility (CTF). It receives the GPS time, which is spread to all the
subsystem (via LAN) and all clocks (via Terminals) with NTP protocol.
Y
P
O
Y
L
Data Base Management (DBM). It provides
N the creation and
C the necessary facilities
modification of the adaptation databasesY
to supply the system withO
the precise knowledge of
its geographical environment to achieve
this database, all
E From
R the required efficiency.
S
necessary data to define the A
control centre characteristics
are defined (fixpoints,
O QNH zones, etc.)
N adjacent controlPcentres,
aerodromes, airways, sectorization,
I
R
IM
Simulator environment:
L
U
E
Simulator (SIM). (OPTIONAL)
It providesP
to the controllers an operational replica of the real
R
scenario for P
training purposes. It is aG
multiple exercise simulator system and allows the use
of several exercises, simultaneously
independently. It allows the analysis of new
IasNtheandmanagement
operational procedures as Iwell
and maintenance of the full set of
N
sessions and exercises recorded
in
the
Simulation
Library.
allows the creation of new
Aof training scenarios and providesIt also
R
exercises, the selection
a complete set of interactive
capacities in order T
to guarantee full control and management.
R
InstructorO
Pilot Position (PILOT SM). (OPTIONAL) It allows the training scenarios
Fsession
selection,
control and control of aircraft simulated interactively in such a way that
Data Recording Facilities (DRF). It performs the continuous recording of tracks, flight plans
data and controller actions to allow a later reproduction and analysis.
from this position the communication answer to the control positions is generated.
3.2
Exercise Manager (ATG/EPP). (OPTIONAL) From this unit simulation, exercises are
managed.
FLIGHT DATA DISPLAY (FDD) POSITION OVERVIEW
The FDD Position is based in a workstation that allows managing all information related with flight
plans, AFTN messages, restricted areas, etc. The main functions of the FDD position are:
FPL handling:
Creation
Visualization
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 3
Página / Page 3 de / of 12
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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:
3.3
RY
C
Y
P
O
A
O
N
I
Visualization
P
R
IM
Modification
L
U
E
P
Retrieval
R
G
P
Deletion
N
NI
Flow Planning (FPLs)
I
A
AFTN Lines Configuration R
T
NOTAM and Meteorological messages handling
R
O
ORGANIZATIONF
OF THIS MANUAL
Creation
SE
Y
L
N
O
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
Capítulo / Chapter 3
Página / Page 4 de / of 12
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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
RY
C
Y
P
O
It present the different “MESSAGE” of the Information Area.
SE
Y
L
N
O
A
O
N
I
It present the a Morphological error.
P
R
IM
Appendix E
Local Functions
Error Messages
L
U
E
P
It present the definition ofR
error messages.
G
P
Appendix F
Coordination Messages N
I
It present the three-phase process. IN
A
R
3.4 CONVENTIONS USED
TIN THIS DOCUMENT
R
“Select X” means to
move the mouse so that the screen cursor is at the top of the X, and
O
press
Fand release left mouse button.
Appendix D
Error Message of Route Field
“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.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 3
Página / Page 5 de / of 12
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
RY
C
Y
P
O
SE
Y
L
N
O
O
NA
I
P
R
IM
The icons and switches are listed inLbrackets; the menu U
options between parenthesis, edition
E listed between quotation
P marks.
fields and windows are
R
G
P the followingIN
Description of windows includes
parts:
Window’s layout figure
N
I
A
Window’s description
R
T
Edition fields’ description
R and operational behaviour
Window commands’ description
O
F
Next figure illustrates some of the conventions used when making selections and editing data in the
Figure 3.4-1. Operative Description Example
fields of the FDD windows.
Capítulo / Chapter 3
Página / Page 6 de / of 12
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
RY
C
Y
P
O
SE
Y
L
N
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
AAND FIELD TEXT ENTERING
3.5 SELECTING MENUS, ICONS
R
T
Menus, menus options, icons and switches access windows, commands, and options. These actions
Rwhere the FDD functions initiate.
cause windows to display
O
The mouse is theF
main device for controller inputs although, in specific cases, the controller may use
Figure 3.4-2. Conventions Used in this Document
the keyboard for that end. Following table describes the logical functions of the mouse buttons:
Table 3.5-1. Mouse Button Functions
Button
Function
Left button (LB)
Data entering, display pull-down menus
Drag a window by “pressing and hold” the mouse central button on the window title
Copy data field
Central button (CB)
Paste data field
Right button (RB)
Without a defined use
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 3
Página / Page 7 de / of 12
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Pull-down menus: This menu is displayed upon clicking once on the icon. The menu display is kept
after button release, and pointing and clicking perform the selection. To close the pull-down menu
(with no changes) click on it with the mouse CB. A pull-down menu comprises:
An available options list for the icon. An option can be selected by clicking on it with
the LB, which causes the menu to disappear. The corresponding window is displayed
on the screen.
Windows: They are displayed by clicking with the mouse LB on the pull-down menu options or directly
on icons. The window keeps its display until the operator closes it by means of the [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
Icons to validate or cancel the action
RY
C
Y
P
O
SE
Y
L
N
O
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:
O
NA
I
P
R
IM
L
U
Title, with the type ofE
field to be modified (CFL, upper altitude level filter, etc.)
P
R
An available options list for the field. This
may include a horizontal or vertical slide
P
NinGview.listInitially,
to allow selection of those options Inot
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
N
I
and at the same time, the pop-up
window
is
closed.
A
R
An edition field where
to input valid values even thought the value is not
T it isthepossible
included in the list.
Before
edition,
the cursor must be focused on the corresponding
R
field. Click on
the
<Enter>
key
to
validate
the input data and to close the pop-up
O
window. F
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:
Capítulo / Chapter 3
Página / Page 8 de / of 12
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Table 3.5-2. Key Functions
Key
3.5.1
Function
<Tab>
Move the cursor position from one field to the following one.
<Shift> + <Tab>
Move the cursor position back from one field to the previous one.
<Backspace>
Delete the character before the cursor position (within a field).
<Del> (Or <Del>)
Delete the character after the cursor position (within a field).
<Arrows>
Left arrow: moves backward the cursor, character by character, within a field.
Right arrow: moves forward the cursor, character by character, within a field.
Rules to Enter or Delete Data
Windows contain “fields” where data can be input, (sometimes it is even compulsory). The following
rules for entering data apply to all FDD windows.
Y
P
O
Y
L
N
Input can only be made into a window if the “focus” is in that window (screen cursor is inside
the window area).
C
O
E
S or modification Fields in
Fields that are shaded in dark GREY do A
not accept data entering
O
N
WHITE accept data entering
modification. Fields in RED contents erroneous
I orfields.
P
information or are compulsory
M
R
I
L
U
E
P
G
PR
N
NI
I
A
R
T
R
O
F
RY
The field displaying the blinking input cursor is ready to accept inputs.
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
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 3
Página / Page 9 de / of 12
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
RY
C
Y
P
O
SE
Y
L
N
O
O
NA
I
P
IM
Only for resizable windows, which
have a resize buttonR
in the top right hand corner
.
L
U
For resizing:
E
P
R
Click and keepP
clicked the resize buttonG
with LB.
N
Drag the frame to the new position.I
N
I
Drop the LB.
A
R
Transfer window
T
R capacity, transfer between FDD and SDD. With a transfer icon
Only for windows with this
O
in the top right hand
F corner . For transfer window:
Drop the LB and the operation is completed.
Resize window
Click in transfer button with LB.
The window appears in the last position where was in SDD and disappears in FDD.
To return FDD, click in the transfer icon with LB since SDD.
The window appears in the last position where was in FDD and disappears in SDD.
It is also possible to do the same action dragging the window since FDD to SDD and vice versa,
keeping clicked LB over the window title and move it to the final position in the other window.
Inhibit
Click in bi-state icon. The text colour will turn from YELLOW to WHITE or to BACKGROUND colour.
Active
Click in bi-state icon. The text colour will turn from WHITE or BACKGROUND colour to YELLOW.
Capítulo / Chapter 3
Página / Page 10 de / of 12
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Date format
Click in labels which associated data are date, shows the appropriate format for data introduction.
3.7
PROCEDURES TO CLOSE ACTIONS IN WINDOWS
Every action to be done have an ending by Windows/lists icons. The ending may be:
Validation and closing
Closing without validation
Data erase
Print
Closing procedures will be explained by an example with the FP Operation Window example:
ACTION
1.
Validation and closing
1.1.
RESULT
Clicking in [OK] icon
RY
Y
P
O
C
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
1.2.
2.
Closing without validation
2.1.
3.
4.
Click in [CLOSE] icon
SE
O
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.
The FP Operation Window is closed, validating the action.
The FP Operation Window is closed, without validating the action.
Click in [CLOSE] icon
Data erasing
3.1.
[CLEAR] icon
3.2.
Click in [CLOSE] icon
FP print
4.1.
Y
L
N
If data entered are right, the FP Operation Window shows the FP
that coincides with selection criteria.
Data entered are erased from FP Operation Window.
FP Operation Window is closed validating the action.
The displayed Flight Plan is printed.
Click in [PRINT] icon
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 3
Página / Page 11 de / of 12
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
"Página dejada en blanco intencionadamente"
"This page intentionally left blank"
Capítulo / Chapter 3
Página / Page 12 de / of 12
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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
Ref. [1]
Ref. [2]
TITTLE AND CODE
Air Traffic Management - Procedures for Air Navigation
Services (Doc. 4444)
RY
Supplement to EUR ANP FASID
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
14th Edition
01/ 11/ 2001
Y
L
N
EUROCONTROL
E
S
A
O
N
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
EUR REGIONAL AIR NAVIGATION PLAN
DATE
ICAO
PY
CO
Originating Region SSR Code Assignment Method
(ORCAM) Improvement Study
Ref. [2]
ORIGIN
ICAO
O
1.0
30/09/2004
CAL Ed 2
May 2006
Capítulo / Chapter 4
Página / Page 1 de / of 2
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
"Página dejada en blanco intencionadamente"
"This page intentionally left blank"
Capítulo / Chapter 4
Página / Page 2 de / of 2
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
5.
5.1
DEFINITIONS AND ACRONYMS
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
Y
P
O
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
RY
C
Y
L
N
O
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.
SE
O
NA
I
P
R
IM
Aerodrome
L
U
Defined area (including any E
buildings, installations, P
and equipment) intended to be used either wholly
R
or in part for arrival, departure
and surface movement
of aircraft and operational vehicles.
G
P
IN
Aircraft
N
I
A either craft flies in the air fixed orA
rotary wing.
Airway
TR
It is a corridor for air traffic
Rthat is equipped with radio navigational aids, which is used by the aircraft to
maintain its position O
within the corridor. An airway is defined by a series of fixpoints.
F
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.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 5
Página / Page 1 de / of 14
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
Y
P
O
Y
L
Airspace of defined dimensions, which supplies air traffic control
service for flightsN
controlled by a
C
controller.
O
Y
E
R
Controller
S
A
O
N
Person authorized to provide air traffic control Iservice.
P
M
R
I
Coordination Process
L
U
Procedure to reach an agreementE
on clearances, controlP
transference, advice or information to be
communicated to aircraft by R
means of information
interchange between air traffic services
G
P
dependencies or between controller working positions
IN within those dependencies.
N
I
Correlation
A
Assignment process (manually or automatically)
of radar track and a flight plan based on predefined
TR
criteria.
R
Cruising Level
O
F
Controlled Airspace
A level maintained during a significant portion of a flight.
CTOT
Departure estimated time of a FP controlled by CFMU.
Current Flight Plan (CPL)
Flight plan, including changes, if any, brought about by subsequent clearances.
Fixpoint
Reference point specified either by geographic coordinates (latitude, longitude), a name, or as a
distance and bearing from a navigational aid.
Flight Data
Data related to real or foreseen movements of an aircraft, usually displayed in abbreviated or in code
Capítulo / Chapter 5
Página / Page 2 de / of 14
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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
Y
P
O
Y
L
N
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.
C
O
E
With the FUA (Flexible Use of Airspace Concept) application, the airspace is not divided into “civil” and
Sairspace taking into account the
A
“military” but it is considered as a unique
continuous and assigned
O
N
I
user requirements.
P
M
R
I
The FUA Concept allows the L
maximum-shared use U
of the airspace by improving the civil/military
E
P
coordination. The FUA Concept
application guarantees
that any airspace segregation is temporal and
R
based on a real use during
a specific period. G
P
IN
Hand-Over Procedure
N
I
Process to transfer flights betweenA
controllers.
Heading
TR
R longitudinal axis is pointed, usually expressed in degrees from North
Direction to which the aircraft
O
(true, magnetic, compass
F or grid). The grid north is an imaginary direction parallel to the Greenwich
FUA
RY
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.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 5
Página / Page 3 de / of 14
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
Y
P
O
Y
L
Setting on the aircraft transponder equipment that sends pulses
N altitude.
Csituating the aircraftOpressure
Y
Mono-radar Track
E received from a
R
S
Information set, evolving in time, related to an aircraft,
based upon radar information
A
O
unique radar site and used by the computer forIN
tracking purposes.
P
R
IM
Multi-radar Track
L
U
E to an aircraft andPobtained from the synthesis of all monoInformation set, evolving in time, related
R
radar tracks that represent the above
G
P referenced Iaircraft.
N
Play Back (Reproduction)
N
I
This process recovers and presents:
A
R
Trecorded
•
Information previously
Rbeen displayed to the Positions Controllers (SDD)
•
Data, which have
O
F
Mode C
•
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.
Capítulo / Chapter 5
Página / Page 4 de / of 14
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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
Y
P
O
Y
L
N
System common information and local information (each SDD) methodically gathered in a specific
period.
C
O
E
Sthe operational environment of
Within the airspace it represents a changeA
of significant meaning to
O
N
involved sectors and centres. STCA RVSM
MTCA RVSM are STCA and MTCA with calculus
IwhereandRVSM
P
taking into account the RVSM in sectors
applies.
M
R
I
L
U
Restricted Area
E
P
R where the flightsGare restricted under certain conditions, or where,
Defined airspace volume,
P
dangerous activities for flights are performed.
IN
N
I
Runway
A
A defined rectangular area on aR
land aerodrome prepared for the aircraft landing and take-off.
T
Secondary Surveillance
Radar (SSR)
R
Radar sensor used O
F to interrogate aircraft transponder equipment to receive SSR Codes, barometric
RY
Reduced Vertical Separation Minimum (RVSM)
pressure information, and/or the SPI.
The Mode 3/A SSR Codes are used to identify individual flights in ATS. When the SSR detects a flight,
its SSR Code is used to correlate the flight with the corresponding Flight Plan.
SSR Codes assignment and management is a fundamental part of the civil ATS systems. As SSR
Codes are based on 4 octal-digits, there are only 4096 available codes to use around the world.
Sector
Designated control area subdivision, which belongs to a controller or to a small group of controllers.
The entire sector must belong to one controller jurisdiction at a time. In addition, sectors composing a
controller jurisdiction must be adjacent.
Sectorization
It is an action to alter the current existing configuration when changing the allocation of some or all
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 5
Página / Page 5 de / of 14
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
Y
P
Y A SID
L
It is a special route overflown by an aircraft during its take-off (using
the <Take Off> command).
O
Nthat begin at or
Cof fixpoints/level pairs
connects an airway to an airport and it is defined by a series
O
near the departure runway and end at or near the airway.Y
E
R
S
A
Synthetic Track
O
N request. A P
I
Type of track generated by the System upon controller’s
special track symbol distinguishes
R
IM
these tracks from the real ones.
L
U
E
P
Terminal
R
Gare grouped together in various combinations to
P software. Terminals
It is the computer and application
N
I
form a working position.
N
I
Test Plot
RA
It is radar information that respondsT
to a fixed transponder.
R
Track
O
It is the projection on F
the earth surface of the aircraft route. The route direction at any point is
expressed in degrees (magnetic North).
Standard Instrument Departure (SID)
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.
Capítulo / Chapter 5
Página / Page 6 de / of 14
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Transit
Flights passing through the working area (FIR).
Transition Level
Altitude at which, or below, the vertical position of an aircraft is controlled by altitudes reference.
Transponder
L-band radar receiver/transmitter carried aboard certain aircraft. It transmits a beacon code and Mode
C altitude (if so equipped), in response to an interrogation from Secondary Surveillance Radar. The
data provided by a transponder can be in any of the following forms: Mode 3/A, Mode 2, or Mode C.
Variable System Parameter (VSP)
It is a system parameter, which can be modified on line.
Working Position
Terminals group specially built which are included in a single cabinet structure.
Workstation
Y
P
O
Y
L
N
It is the computer and application software. Workstations are grouped together in various
combinations to form a working position.
5.2
AAI
ABI
A/C
ACC
ACID
ACK
ACP
ACT
A/D
C
SE
O
NA
I
P
M
R
FDD Message IQueue
L
U
AdvancedE
Boundary InformationP
Message (OLDI)
R
G
Aircraft
P
N
I
Area/Airspace Control Centre
N
I
Aircraft Identification
A
R
Acknowledge(ment)
T
Rmessage (OLDI)
Accept
O
FActivation Message (OLDI)
ACRONYMS
A
RY
O
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
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 5
Página / Page 7 de / of 14
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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
RY
C
Y
P
O
C
A
O
N
I
Air Traffic Flow Management
P
IMSystem UR
Airport Traffic Information
L
E
P
Air Traffic Management
R
G
Air TrafficP
Services
N
Airspace Usage Plan
NI
I
A
Auxiliary
R
T
R
By-Pass Mode of Operation
O
F
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
ATD
ATFM
ATIS
ATM
ATS
AUP
AUX
B
BYP
Capítulo / Chapter 5
Página / Page 8 de / of 14
Actual Time of Departure
SE
Y
L
N
O
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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
DCT
DEP
DEP
DEST
DF
DL
DLA
DLS
DRF
RY
C
Y
P
O
A
O
N
I
Data Base Management
P
R
IM
Direct RouteL
Qualifier
U
EMessage
P
Departure
R
P Aerodrome ING
Departure
Destination Aerodrome
N
I
A
Directional Finder
R
T
Data Link/Downlink
R
Delay
O
FData link Service
SE
Y
L
N
O
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
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 5
Página / Page 9 de / of 14
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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
RY
C
Y
P
O
H
A
O
N
I
Flexible Use of Airspace
P
R
IM
L
U
E
P
General Air Traffic
R
G
GigabyteP
N
Gigahertz
NI
I
A
Global Positioning System
R
T Message
Wind Meteorological
R
Graphical User Interface
O
F
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
FPL
FUA
G
GAT
GByte
GHz
GPS
GRIB
GUI
Flight Plan
SE
Y
L
N
O
I
ICAO
International Civil Aviation Organization
Capítulo / Chapter 5
Página / Page 10 de / of 14
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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
Km
KPS
Kt
KW
L
LAM
LAN
LAT
LB
RY
C
Y
P
O
A
O
N
I
Kilometer
P
R
IM
KB per second
L
U
E
P
KnotsR
(NM/ hour)
G
P
Kilowatts
N
NI
I
A
Logical Acknowledgement
Message
R
TNetwork
Local Area
R
Latitude
O
FMouse Left Button
Knots Indicated Airspeed
LCD
Liquid Crystal Display
LMG
Local Maps Generation
LONG
Longitude
SE
Y
L
N
O
M
M
Match/Meter
Mb
Millibars
Mbar
Milibar
MET
Meteorological Information
METEO
Meteorological
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 5
Página / Page 11 de / of 14
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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
PSR T
A
O
N
I
On-Line Data Interchange
P
R
IM
Originating RegionL
Code Assignment Method
U
E
P
R
P Message ING
Pre-activation
Prior Coordination Airspace
N
I
A
Pilot
R
Position ReportT
R
Primary Surveillance Radar
O
F Surveillance Radar Track
Primary
PTS
Panoramic Tower Simulator
OAT
OLDI
ORCAM
P
PAC
PCA
PLT
POS
PSR
Operational Air Traffic
RY
C
Y
P
O
SE
Y
L
N
O
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
Capítulo / Chapter 5
Página / Page 12 de / of 14
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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
SAR
SBY
SDD
SDP
SFPL
SID
SIGMET
SIM
RY
C
Y
P
O
A
O
N
I
Slot Allocation Message (CFMU Message)P
R
IM
Search and Rescue
L
U
E
P
Standby
R
P Data Display ING
Situation
Surveillance Data I
Processing
N
A
System Flight Plan
R
StandardT
Instrument Departure
R
Significant Meteorological Information
O System
FSimulator
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
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
SE
Y
L
N
O
Capítulo / Chapter 5
Página / Page 13 de / of 14
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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
RY
C
Y
P
O
WAN
A
O
N
I
Upper Airspace Control Centre
P
R
IM
Universal Time Coordinated
L
U
EUsage Plan P
Updated Airspace
R
G
P
N
I
Vertical Future Situation IN
Visual Flight Rules A
R
Variable SystemTParameter
R
O
WideF
Area Network
Wi-Fi
Wireless Fidelity
WWW
World Wide Web
U
UAC
UTC
UUP
V
VFS
VFR
VSP
W
SE
Y
L
N
O
X
X.25
Standard Protocol In Telecommunications
Capítulo / Chapter 5
Página / Page 14 de / of 14
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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)
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
Figure 6-1. FDD Screen
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 1 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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:
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Table 6.1-1. General Information Area (GI_A). Elements
Item
“Q” AFTN Messages Counter
Type
SE
Y
L
N
O
Description
Information Box
Queue identifier and display of the number of stored AFTN/OLDI
messages
Icon
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 AFTNNOTAM Correction Window (see 6.1.1.4.2)
“AAI” AFTN Messages Counter
Information Box
Queue identifier and display of the number of AFTN messages with
erroneous header or SVC (non-repetition) messages, which are
stored in the queue until they are processed
SUMMARY
Icon
Access to the AFTN message list with erroneous head, and to SVC
message non-repetitive
User can select one of them and visualize it.
Time and Date
Information Box
Display the System time and date
SUMMARY
Capítulo / Chapter 6
Página / Page 2 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.1.1
“Q” Queue: AFTN-FP Messages Area (FPM)
It is composed of several items:
“Q” Queue identifier and AFTN Messages Counter
[SUMMARY] icon to de-queue the messages. If clicked it on, a new window is displayed with
the queued messages.
Figure 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:
Y
P
O
Y
L
N
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
RY
C
SE
O
A
O
N
I
Correct and erroneous NOTAM messages (always).P
R validation. If there is no error, the
IMhave no automaticUfields’
FP messages following described
L
Ethe FP updating. If anyP field (not the ones marked as optional) cannot
modification messages cause
R
be detected nor has errors,
P the message isIsent
NGto the “Q” Queue for manual correction.
Nthe IFPS or any other source), in ICAO format:
I
Following messages are received (from
A
R
FPL (Filed Flight Plan
T message)
R Plan message)
CPL (Current Flight
O
F message)
CHG (Change
FP status non suitable for automatic processing
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)
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 3 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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)
C
Y
P
O
Y
L
N
O
E
The System checks whether a message is conflicting
with an existing flightS
plan in the FDP database.
A
O
N
If so, the received message and the existing flight
FPM queue for validation.
I plan are both sentPtoittheis sent
Likewise, if the message cannot be uniquely
identified with a flight plan,
to the FPM queue.
M
R
I
L
Ucreates a Minimal Flight Plan, if the
Upon receiving ABI/ ACT/ EST/ POS messages the System
E
P
corresponding flight plan does not
Rexist.
G
P
The incomplete SFPL and the message are sent to
the corresponding Sector Planner FPM queue for
N
insertion of missing data.
NI
I
A
R
Textracted fields, are placed in the FPM queue for manual
All NOTAM messages, with their
confirmation.
R
O
MET messages (METAR,
F SPECI, TAF, SIGMET, ATIS, AIRMET) without errors update the MET
IAPL (ATC Flight Plan message)
RY
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.
Capítulo / Chapter 6
Página / Page 4 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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
Y
P
O
Y
L
N
The flight plan status and the flight plan source establish if the proposed action on the flight plan can
be performed.
C
O
Y
It is also verified that, for an SFPL in “ACTIVE”
status, the source of the
input is either the currently
E
R
assigned sector, or a sector/unit involved inA
the future control of theS
flight, and a change to the SFPL
O
N
at a sector work position does not affect
the SFPL at a point upstream
from the point at which the
I
P
sector is responsible for the SFPL. M
R
I
L
U
Validity checks conform to ICAO
E and EUROCONTROL
P regulations, as well as to domestic specific
practices.
R
G
P
Erroneous messages received from AFTNI/N
IFPS are sent to the FPM queue. The original text of the
message, the flight plan data extractedN
from the message and the routes list (if the message included
I
the route field) are sent to the queue
management
function.
A
R
Erroneous messages from an
FDD are returned to the operator. Any error detected during the validity
Twarn
checks will be highlighted
to
the control position where the data was entered. Along with the
R
highlighted field, a message
reports
the type of error.
O
F
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.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 5 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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;
Y
P
O
Y
L
A CNL/ ICNL cancels the flight plan, provided it is not in “Notified” or “Active”N
status;
C
Oretrieving and reThe System provides the capacity to undo
a cancellation, through
Y
E
R
creating the same flight plan;
S
A
After undoing a cancellation, theIN
flight plan is reverted to O
its initial status;
Pplan to “Active” status;
M
An EST updates the flight plan I
ETOs
and change the flight
R
LETOs and changePtheUflight plan to “Active” status;
A POS updates the flight plan
E
R
G
A NOTAMN createsP
a new NOTAM in the database;
N
A NOTAMR updates an existing NOTAM;
NI
I
A NOTAMC cancels the referredA
NOTAM;
R
METAR, SPECI, TAF, ATIS,
and SIGMET messages update the MET database for
T AIRMET,
the corresponding aerodrome
or
FIR.
R
O
F
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;
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.
Capítulo / Chapter 6
Página / Page 6 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
RY
C
Y
P
O
SE
Y
L
N
O
O
NA
I
P
R
IM
L
U
E
P
The AFTN-FP Messages R
Window (“Q”) has two main areas:
G
P
N
Visualization Area:
I
N
I
The “Q” Queue messages list is displayed in this area. The user may display the whole information of
Athe LB on the corresponding one.
any message by clicking twice with
R
T
Command Area:
R
The user may filter O
the messages by clicking with the LB on the corresponding message type icon.
Fmessages are not displayed, if the icon is activated (RED). The selected type
The selected type
Figure 6.1.1.4-1. AFTN-FP Messages Window (“Q”)
messages are displayed, if it is inhibited (GREEN).
Following table displays the different filters to perform:
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 7 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Table 6.1.1.4-1. AFTN-FP Messages Window (“Q”). Filters
Icon
Description
FP
Filter for AFTN-FP messages in the “Q” Queue. If it is selected, the FP messages are not
displayed on the “Q” Queue but when the icon is released, they are visualized.
NOTAM
Filter for AFTN-NOTAM messages in the “Q” Queue. If it is selected, the NOTAM messages are
not displayed on the “Q” Queue but when the icon is released, they are visualized.
TACT
Filter for AFTN-TACT messages in the “Q” Queue. If it is selected, the TACT messages are not
displayed on the “Q” Queue but when the icon is released, they are visualized.
COORD
Filter for coordination messages (AFTN/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.
UNKNOWN
Filter for unknown messages in the “Q” Queue. If it is selected, the unknown messages are not
displayed on the “Q” Queue but when the icon is released, they are visualized.
UPDATE
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.
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
CLOSE
SE
Y
L
N
O
Close the window.
NOTE: After performing the filter selection, click on the [UPDATE] icon to trigger the filtering.
The user may visualize one of these messages by clicking twice on any of them. The message is then
displayed in any of the following windows:
AFTN-FP Correction Windows
In case the message type is 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
Capítulo / Chapter 6
Página / Page 8 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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
AFTN-FP CORRECTION WINDOWS
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 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.
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
Figure 6.1.1.4.1-1. AFTN-FP Correction Windows
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 9 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
RY
C
Y
P
O
SE
Y
L
N
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
Command Area: T
R
It is composedO
by a set of icons that are described in the following table:
F
Figure 6.1.1.4.1.1-1. AFTN-FP Message Correction Window. Error
Table 6.1.1.4.1.1-1. AFTN-FP Messages Correction Window. Command Area
Icon
Description
PREV
Force the display of the previous AFTN/OLDI message. If there is no previous message, the windows are closed.
NEXT
Force the display of the next AFTN/OLDI message. If there is no next message, the windows are closed.
DELETE
Delete the current displayed message. The AFTN Message Counter is decreased one value (1).
OK
Trigger the modification process performed on the message, if any, and process the message, if it is correct.
CANCEL
Close the windows and cancel any modification, if it was not previously triggered.
Rqp
Request the FP corresponding to the received message that has been sent to the “Q” Queue. (Only when the
error in the received message is “FP no exist”).
Capítulo / Chapter 6
Página / Page 10 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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
PRINT
Description
Print the text of the AFTN/OLDI message.
6.1.1.4.1.3
ASSOCIATED FPS LIST
Y
P
O
Y
L
N
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
1.
C
O
Y
ACTION: AFTN MESSAGE DE-QUEUE
(FP MESSAGES)E
R
S
A
O
N
I
P
M
R
I
L
U
E
P
G
PR
N
NI
I
A
R
T
R
O
F
RESULT
Click with the LB on the [SUMMARY] icon to request the
queued AFTN message.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
The System displays the “Q” Queue. The user filter the
corresponding message, updates the messages in the queue or
close the window.
Capítulo / Chapter 6
Página / Page 11 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
ACTION
RESULT
2.
When clicking twice on any entry to correct the message.
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
4.2.
Click with the LB on the [CANCEL] icon
4.3.
Select the [Rqp] switch and click with the LB on the
[OK] icon.
(Only when the error message is ”FP not exist”).
C
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).
SE
Y
L
N
O
The displayed AFTN message is deleted from the queue (the
counter decreases in one unit).
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
a)
6.1.1.4.2
RY
Y
P
O
The displayed AFTN message is deleted from the window but it
remains in the messages queue.
A request message is sent and the previous message is kept in the
message queue.
The AFTN message is printed.
AFTN-NOTAM MESSAGES CORRECTION WINDOW
When receiving an AFTN message, which type is “NOTAM”, either correct or incorrect, the system
queues the message in the “Q” Queue.
When clicking on the [SUMMARY] icon, the FP Messages Window is displayed to filter the messages
by type: FP, NOTAM, TACT (tactical), COORD (coordination) and UNKNOWN being selectable one or
more filters (see point 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.
Capítulo / Chapter 6
Página / Page 12 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
RY
C
Y
P
O
SE
Figure 6.1.1.4.2-1. AFTN-NOTAM Messages Correction Window
O
O
NA
I
P
Window Title
M
R
I
L
U
It changes depending on the type of AFTN-NOTAM
message.
E
P
R
Message Text Area
G
P
It contains the AFTN messageIN
text of NOTAM type displayed on the screen.
Nicon, the message text printing is performed.
By clicking on the [PRINT]
I
A
Edition Area
R
T
It is composed by a set of fields where the system displays the data extracted from the
R text message. The system indicates the erroneous fields for operator
AFTN-NOTAM
O
modification.
F Only WHITE and RED fields (compulsory and erroneous fields) are
accessible to the operator.
This window is composed of the following areas:
Y
L
N
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:
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 13 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Table 6.1.1.4.2-1. AFTN-NOTAM Messages Correction Window. Command Area
Icon
Description
PREV
Force the display of the previous AFTN message. If there is no previous message, the window is closed.
NEXT
Force the display of the next AFTN message. If there is no next message, the window is closed.
DELETE
Delete the current displayed message. The AFTN message counter is decreased one unit (1).
OK
Trigger the modification process performed on the message, if any, and process the message, if it is correct.
CANCEL
Close the window and cancel any modification, if it was not previously triggered.
6.1.2
“AAI” Queue: Erroneous AFTN Header Area (EAH)
It is composed of following elements:
Y
P
O
Y
L
N
“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.
RY
C
SE
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NIthe FDP validates all data contained in the AFTN
Prior to the processing of the message text,
I
A
message header:
R
T
Addresses
R
Filing time
O
F
Originator indicator
Figure 6.1.2-1. “AAI” Queue
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
Capítulo / Chapter 6
Página / Page 14 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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
Y
P
O
Y
L
N
The “AAI” Queue attends the messages that have some error in the header and service messages
(SVC) other than "repetition".
RY
C
O
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).
SE
O
NA
I
P
R
IM
L
U
E
P
R
G Number and the expected one is less or equal
In case the differenceP
between the received Sorting
N
than 10, then the message is processed. That
is, it is not queued in the “AAI” Queue and a message
NINumber
I
indicating this event is sent (the Sorting
of the next sending message is increased in one
A
unit).
TR icon, a set of messages (up to ten) is displayed on a window. If
When clicking on the [SUMMARY]
user clicks twice on oneR
of these entries and the message has any error in the header, it is displayed
O
on the “AAI” Messages
Correction Window. The messages counter does not change the number until
F
the message is processed or deleted.
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).
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
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 15 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.1.2.1.1
“AAI” MESSAGES WINDOW
When receiving an erroneous message or it is a SVC message (but not “repetition”), it is queued on
the “AAI” Queue.
The messages sent to the “AAI” Queue are displayed in the messages window. Up to 30 messages
are displayed. The user can visualize any of them with double-click on the message.
There are two possible actions:
[Update]: Display the new messages that are going to enter in “AAI” Queue.
[Close]: Close the window.
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
FWINDOW
“AAI” ERROR
SE
Y
L
N
O
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.
Figure 6.1.2.1.2-1. “AAI” Error Window
Capítulo / Chapter 6
Página / Page 16 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.1.2.1.3
“AAI” MESSAGES CORRECTION WINDOW
The “AAI” Messages Correction Window displays the data message within their corresponding fields
when double-clicking on any entry of the messages window.
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F following areas:
This window has the
SE
Y
L
N
O
Figure 6.1.2.1.3-1. “AAI” Messages Correction Window
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:
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 17 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Table 6.1.2.1.3-1. “AAI” Messages Correction Window. Command Area
Icon
Description
PREV
Force the display of the previous AFTN message whose header is erroneous. If there is no previous message, the
window is closed.
NEXT
Force the display of the next AFTN message whose header is erroneous. If there is no message, the window is
closed.
DELETE
Delete the current message in the window. The “AAI” Message Counter decreases by one (1).
OK
Trigger the modification action performed in the message.
EXIT
Close the window and cancel the modification process, if it was not previously validated ([OK]).
When clicking on the [OK] icon, one of the following situations is initiated:
Y
P
O
Y
L
If the message is not a FPL and it is not corrected,
the message will remain
in the queue
N
C
with another special window (“AAI” Window) where the message onlyO
can be printed or
Y
deleted.
E
R
Sit will be processed. There
A
If the message is an SVC of repetition
(RPT) and it is corrected,
O
N
I by the FDP: P
are two messages of repetition processed
M
R Number or a Sorting Number
I with Circuit Id andUa Sorting
Message repetition request
L
E
P
range:
R
G
P
N
NI
I
A
R
T
R
O
F
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.
SVC QTA RPT xxxn-m where,
xxx is the Circuit Id,
n is the message Sorting Number to be repeated, or lower Sorting Number of the range of
messages to be repeated.
m is the Sorting Number or the range of messages to be repeated. If only a message is going to
be repeated, it is not necessary.
Message repetition query with Filling Day Time and Originator:
SVC QTA RPT ddhhmm address, where
ddhhmm is the Filling Day Time, and
address is the Originator
Capítulo / Chapter 6
Página / Page 18 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
In both cases the header will display:
Destination: value defined in adaptation.
Originator: value defined in adaptation.
6.1.2.1.4
“AAI” WINDOW
The “AAI” Window displays all the SVC messages other than “repetition” and the messages which are
not FPL and whose header is not corrected in the “AAI” Messages Correction Window. This window
consists of the following areas:
RY
C
Y
P
O
SE
Y
L
N
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
Message Text Area
T
R the SVC AFTN message of repetition (RPT) whose header has some
This area displays
O
errorF
or the SVC AFTN message, which are not of repetition. The text cannot be
modified.
Figure 6.1.2.1.4-1. “AAI” Window
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
PREV
Force the display of the previous message in the “AAI” Queue. If there is no previous message, the window is
closed.
NEXT
Force the display of the next message in the “AAI” Queue. If there is no following message, the window is closed.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 19 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Table 6.1.2.1.4-1. “AAI” Window. Command Area
Icon
Description
DELETE
Delete the current message in the window. The “AAI” Queue Messages Counter decreases by one.
CANCEL
Close the windows and cancel the modification process, if it was not previously validated.
PRINT
Print the current message.
6.1.2.1.4.1 ACTION: AFTN
HEADER)
MESSAGES
DE-QUEUE
ACTION
1.
(ERRONEOUS
AFTN
MESSAGE
RESULT
Click with the LB on the [SUMMARY] icon, situated in the
GI_A.
Y
P
O
The “AAI” Messages Window is displayed. The user may update the
messages coming into the queue or cancel the action, by closing the
window.
RY
C
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
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.
Capítulo / Chapter 6
Página / Page 20 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
ACTION
4.
RESULT
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 (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.
Y
P
O
Y
L
N
In both cases, the counter decreases one unit.
N
I
LIM
RE
P
R
O
F
N
I
RA
Y
R
A
G
N
I
C
PU
O
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].
O
P
R
SE
T
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.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 21 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.1.3
System Time and Date
The information box presents the system time and date at the top right of the GI_A.
Figure 6.1.3-1. System Time and Date
Table 6.1.3-1. System Time and Date. Items Description
Format
Item
Time
HH: MM (HH = Hour; MM = Minutes)
Date
Week day (space) day number (space) month “ of ” AAAA
AAAA= four digits of the year
RY
C
Y
P
O
SE
Y
L
N
O
Note: 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.
O
NA
I
P
6.1.4 FDP Failure
M
R
I
L
When no FDP is available, a warning window will be displayedU
in FDD to warn about the failure.
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Figure 6.1.4-1. FDP down
Capítulo / Chapter 6
Página / Page 22 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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
Y
P
O
FP Act.
Display the FP Operation Window (action mode) to view, create, modify, cancel, etc., a FP.
FP Rtr.
Display the FP Retrieval Window to allow the retrieval of the specified FP(s).
FP min.
Display the Minimal FP Window to create a minimal FP.
RPL Act.
Display the RPL Operation Window to view, modify, cancel, etc. a RPL.
RPL Rtr.
Display the RPL’s Retrieval Window to allow the retrieval of the specified RPL(s).
RUNW
Display the Airport Runways Window.
AFTN TX
Display a menu to select the AFTN messages type (ICAO, FREE text or of Service) to be edited.
ARCHIVE
Display the AFTN Retrieve Window that includes the sent and received messages that match the operator
searching criteria.
A.P.
Display the Airport Pressure Window.
WINDS
Display the Winds Data Window to view and/or modify the wind data.
AREAS
Display the Restricted Areas Window to perform several actions (view, creation, modification, etc) on restricted
areas.
FLOW
Display a menu to choose the traffic type to be analyzed.
METEO MSG
Display the Meteorological Information Window to obtain, by previous meteorological message selection, the
corresponding information.
NOTAM
Display the NOTAM Operation/Retrieval Window.
T.Flow
Display a menu to select the different traffic flow options.
LINES
Display the window that visualizes the status, SIN, SON, of the AFTN lines. It also allows access to the
modification window of those parameters.
PIP
Display the window that visualizes the application help.
EST
Display the window to perform a quick Estimate operation without accessing the FP template.
LOGOUT
Lock the position and display the Log-In Window
PRINTER1
Display the window that allow selection among available printers.
RY
C
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
SE
Y
L
N
O
Capítulo / Chapter 6
Página / Page 23 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.1
Icon [FP Act.] Actions on Flight Plans
This icon triggers all procedures related to FP actions.
By clicking on the [FP Act.] icon, the FP Operation Window is displayed.
Figure 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.
RY
C
Y
P
O
SE
Y
L
N
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
6.2.1.1.1 FLIGHT PLAN STATUS
NI
I
Depending on the actions performed on A
the Flight Plan and the System current time, the Flight Plan
R
can follow these statuses:
T
PASSIVE
R
O
DepartureFFlight Plan with EOBT 20 minutes (configurable parameter) later than the
current time.
Figure 6.2.1.1-1. FP Operation Window
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.
Capítulo / Chapter 6
Página / Page 24 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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
EDITION AREA
Y
P
O
Y
L
N
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.
RY
C
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
O
Table 6.2.1.1.2-1. FP Operation Window. Edition Area
Field
Description
Valid Data
Callsign
Aircraft Identification or ACID
3 to 7 alphanumeric characters
O
SSR Equipment.
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
CSSR
ICAO SSR Code
4 numerical characters (octal 0-7)
Blank = It allows the FDP to automatically assign an SSR Code
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 25 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Table 6.2.1.1.2-1. FP Operation Window. Edition Area
Field
Description
Valid Data
R
Flight Rules
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
FT
Flight Type
1 alphabetical character:
S=
scheduled
N=
non-scheduled
G=
general aviation
M=
military
X=
other
Blank = general aviation
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
N
Number of Aircrafts
Up to 2 numeric characters (1-99)
TYPE
Type of Aircraft
2 to 4 alphanumeric characters. The first one will be an alphabetic
character.
It must be known by the system.
W
Wake Turbulence Category
1 alphabetical character:
L=
light
M=
medium
H=
heavy
RV
RVSM
2 alphabetical characters:
EQ = equipped with RVSM
NO = no-equipped with RVSM
UN = unknown
EX = exempt
Capítulo / Chapter 6
Página / Page 26 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Table 6.2.1.1.2-1. FP Operation Window. Edition Area
Field
N.E
Description
Valid Data
Navigational/Communications Equipment
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
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
ORIG
Departure Aerodrome
4 alphabetic characters.
If unknown, then enter the “ZZZZ” keyword.
If created while aircraft is airborne, then enter the “AFIL” keyword.
EOBD
Estimated Of Block Date
6 numerical characters:
YYMMDD (00 to 99 and 01 to 12 and 01 to 31) date of departure.
EOBT
Estimated Off-Block Time
4 numerical characters:
HHMM (00 to 23 and 00 to 59)
CTOT
Calculated Take-off Time
4 numerical characters:
HHMM (00 to 23 and 00 to 59)
ATD
Actual Time of Departure
4 numerical characters:
HHMM (00 to 23 and 00 to 59)
SPEED
Cruising Speed
5 alphanumeric characters:
Kxxxx: 4 numerical characters (Km/h)
Nxxxx: 4 numerical characters (Knots)
Mxxx: 3 numerical characters (Mach number)
RFL
Requested Flight Level
4 alphanumerical characters:
Fxxx: 3 numerical characters (hundreds of feet)
SID
Standard
Procedure
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Instrumental
Departure
2 to 7 alphanumeric characters. It must be defined in the DBM.
Capítulo / Chapter 6
Página / Page 27 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Table 6.2.1.1.2-1. FP Operation Window. Edition Area
Field
Description
Valid Data
ROUTE
FP Route
Up to 160 characters.
See following NOTE on “Route Field Validation Rules” (see
6.2.1.1.2.2)
STAR
Standard Terminal Arrival Route Procedure
2 to 7 alphanumeric characters. It must be defined in the DBM.
DEST
Destination Aerodrome
4 alphabetic characters.
ETA
Estimated Time Arrival
4 numerical characters:
HHMM (00 to 23 and 00 to 59)
FIXPOINT
Entry Point (for ACT or EST)
Up to 5 alphabetic characters.
It must be known by the System.
ETO
Estimated time over a significant point (for
ACT or EST)
4 numerical characters:
HHMM (00 to 23 and 00 to 59)
CFL
Cleared Flight Level (for ACT or EST)
3 numerical characters (hundreds of feet)
R SPD
Cruising Speed associated al Fixpoint.
5 alphanumeric characters:
Kxxxx: 4 numerical characters (Km/h)
Nxxxx: 4 numerical characters (Knots)
Mxxx: 3 numerical characters (Mach number)
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
NEXT FIX
Next FIX, Future FIX
Up to 5 alphabetic characters. It must be defined in the DBM.
N ETO
Estimated time over a next point.
4 numerical characters:
HHMM (00 to 23 and 00 to 59).
S
Sector (for FP strips)
FIR Sector initials.
REG
Alternative aircraft identification.
5 alphanumeric characters.
ALTERN
Alternative Aerodromes
1 or 2 strings of 4 characters (separated by space).
FREE TEXT
Notes
Free text.
ADDRESS
Aircraft Identification
6 hexadecimals characters (0-9, A-F)
STATUS
Flight Plan Current 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.
Capítulo / Chapter 6
Página / Page 28 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
Y
P
O
Y
L
N
Some fields allow knowing the data valid format within
C the FP OperationOWindow:
Yand a toggle betweenE the field name and the valid
Click with the mouse LB on the field name
R
format is performed. These fields are:
SATD, ETA, ETO, N. ETO.
A EOBD, EOBT, CTOT,
O
N
I
P
6.2.1.1.2.2
“ROUTE” FIELD VALIDATION RULES
M
R
I
Following requirements must beL
fulfilled when editing the
U“Route” field in the FP Operation Window.
E
P
Elements are separated
R by a single space.
G but less than (30).
P
N
Elements consists of more than (1)
character
I
Nroute
I
More than (40) elements in the
are not allowed.
A
R elements.
Only digits cannot compose
T
If only alphabetical
characters form elements, the maximum longitude is 2 to 7 characters.
R
Points canO
F be fixpoint or LAT_LON coordinated.
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.
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]
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 29 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
C
Y
P
O
Y
L
N
O
E
Sconnected by an airway,
Route made up of two FIXES connected
by DCT, two FIXES
A
O
N
or two FIXES connected by more
I than one airway. P
M
Route made up of several Iairways as long as thereR
is a single crossing point for the two
L
U
airways.
E
P
Modifications in routeR
elements, which have
already
been over-flown, are not allowed as
G
P
they cause a route error.
IN
N
I
A
TR
R
O
F
RY
Figure 6.2.1.1.2.2-1. Entry Error Detection in “Route” Field
Capítulo / Chapter 6
Página / Page 30 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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: It is a Standard Route. It is only displayed when there is a standard route defined in the
DBM.
For detailed information on the “Route” field, see APÉNDICE / APPENDIX A.
6.2.1.1.3
COMMAND AREA
Following table shows the different commands, which are included in the FP Operation Window. All
the operations involving flight plan management are described in following sections.
Y
P
O
Table 6.2.1.1.3-1. FP Operation Window (action mode). Command Area
Icon/Switch
RY
C
Command
Y
L
N
O
View
Display an existing FP data
Hist.
Display the history of a FP already created or received. The System presents a report containing the FP information
plus all the actions performed on it with the date and time of all modifications and positions which performed the
changes.
Crea.
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.
CPL
Create a Current Flight Plan for an aircraft that is already flying. This action creates the FP in “ACTIVE” status.
Mod
Modify an existing FP. If modification is correct, the FP keeps the change permanently.
Cancel
Terminate an existing FP. The status changes to “TERMINATED”. Once the FP is cancelled, no modifications can be
performed on it, except retrieval, view, history display or copy by means of the [Create] switch.
Notif
It allows changing a FP from “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.
C.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.
ATD
Mark a flight as having taken off and it allows the controller to change or confirm the ATD time proposed by the
System. The FP is in “ACTIVE” status.
C.ATD
Cancel a previous ATD action. The flight turns to the status previous to the Activation action: “NOTIFIED” or
“PASSIVE”. This action is only possible if the ATD was previously activated.
EST
Perform the time estimate action on a reporting point of the flight plan route. The rest of the fields are calculated by
the System.
POS
Send a position report including the last fixpoint overflown by the aircraft and the passing time, the next fixpoint and
the estimated time.
ATA
Inform the System on the FPL actual time of arrival.
Strips
Print the Flight Plan strip.
OK
Trigger the validation process of the current action performed on the selected window.
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
SE
Capítulo / Chapter 6
Página / Page 31 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Table 6.2.1.1.3-1. FP Operation Window (action mode). Command Area
Icon/Switch
Command
CLOSE
Close the selected window. If the actions performed were not validated previously ([OK]), they will not be taken into
account by the system.
CLEAR
Delete the data displayed on all the fields of the selected window.
PRINT
Print the historical information of a FP.
This point includes all the procedures to perform on the FP Operation Window.
A common step to all actions is following described:
6.2.1.1.3.1
ACTION: COMMON STEP TO ACTIONS ON FPS
ACTION
1.
RESULT
Click with the LB on the [FP Act.] icon, situated in the MM_A.
Y
P
O
Y
L
N
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).
RY
C
SE
O
O
NA
I
P
R
IM
L
U
From this point on, the actions areEdescribed according to operations performed from the switches
P
(commands).
R
GThe compulsory fields are always accessible. If
P
N
Each command has compulsory and accessible fields.
I ones can be modified. The “S”, “CTOT” and
there are no accessible fields, only the compulsory
N
I
“ADDRESS” fields are not applicable.
A
R
T FPL
6.2.1.1.3.2
ACTION: VISUALIZE
R
NOTE: This action is alsoO
used as a starting step to perform any FPL action available from the FP
Operation Window. ThatFis, when performing any action, it is necessary to display the corresponding
FP in order to carry out the operational function.
ACTION
1.
Click on the [View] switch.
2.
Enter data on the corresponding fields to retrieve the FP.
3.
Finish the operation by performing a close action (see 3.7)
RESULT
The switch changes to YELLOW.
Compulsory Fields: CALLSIGN.
Capítulo / Chapter 6
Página / Page 32 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
1.
Perform the FP View action (see 6.2.1.1.3.2)
2.
Click with the LB on the [Hist.] switch.
SE
Y
L
N
O
RESULT
The switch becomes YELLOW, and the FP History Window is
displayed including all actions performed in the FP. If the information
is bigger than the window size, a scroll bar is displayed to allow
visualization. This window allows resizing.
The FP Operation Window automatically changes to View mode
([View] switch activated) and all fields are inaccessible.
3.
Finish the operation by performing a close action (see 3.7)
Compulsory Fields: CALLSIGN only if the FP View action has not been previously performed.
Accessible Fields: NONE
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 33 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.1.1.3.5
ACTION: CREATE FPL
ACTION
RESULT
1.
Click with the LB on the [Crea] switch.
The switch changes to YELLOW.
2.
Enter data in the corresponding fields.
The System checks if entered data are correct.
If they are correct, the new FP is stored in the Flight Plans database
in “PASSIVE” or “NOTIFIED” status.
If they are incorrect, the System displays a message corresponding
to the erroneous data.
3.
Finish the operation by performing a close action (see 3.7)
Y
P
O
Y
L
N
Compulsory Fields: CALLSIGN, TYPE, ORIG, EOBT, RFL, DEST and ROUTE.
RY
C
SE
O
NOTE: It is also possible to create and FPL from an existing one. The action is speeded up.
6.2.1.1.3.6
A
O
N
I
P
ACTION: CREATE A CURRENT FPL (CPL)
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
ACTION
RESULT
1.
Click with LB on the [CPL Create] switch.
The switch changes to YELLOW.
2.
Enter data in the corresponding fields.
The System checks if entered data are correct.
If they are correct, the new FP is stored in the Flight Plans database
in “ACTIVE” status.
If they are incorrect, the System displays a message corresponding
to the erroneous data.
3.
Finish the operation by performing a close action (see 3.7)
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.
Capítulo / Chapter 6
Página / Page 34 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.1.1.3.7
ACTION: MODIFY FPL
ACTION
RESULT
1.
Perform the FP View action (see 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.
Y
P
O
Y
L
NROUTE only if the
Compulsory Fields: CALLSIGN, TYPE, ORIG, DEST, EOBT,
C SPEED, RFL and
O
visualization action has not been previously performed.
Y
E and STATUS.
Accessible Fields: All of them, except: FIXPOINT,
ETO, CFL, S, SD, SOURCE
R
S
A
Ois not allowed.
Nexisting data. Deletion
NOTE: It is only possible to modify already
I
P
M
R
I
L
U
6.2.1.1.3.8
ACTION: CANCEL FPL
E
P
R
G
P
N
1.
NI
I
A
2.
R
T
R
O
F
4.
Finish the operation by performing a close action (see 3.7)
ACTION
RESULT
Perform the FP View action (see 6.2.1.1.3.2)
Click with the LB on the [Cancel] switch.
3.
The switch changes to YELLOW.
Finish the operation by performing a close action (see 3.7)
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.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 35 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.1.1.3.9
ACTION: STATUS CHANGE FROM “PASSIVE” TO “NOTIFIED”
ACTION
RESULT
1.
Perform the FP View action (see 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.
RY
C
Y
P
O
Y
L
N
If no SSR Code, a SSR Code is automatically assigned.
SE
O
O
NA
I
P
R
IM
L
U
E
P
4.
R
G
P
N
Compulsory Fields: None
NI
Accessible Fields: CSSR
I
A
NOTE: This action is allowed once. For re-performing
the action, the operator must perform a Cancel
R
Notification [C.NOTIF] action. The T
Notification action is not allowed when an ATD action has been
previously performed.
R
O
F
Finish the operation by performing a close action (see 3.7)
6.2.1.1.3.10
ACTION: STATUS CHANGE FROM “NOTIFIED” TO “PASSIVE”
ACTION
1.
Perform the FP View action (see 6.2.1.1.3.2)
2.
Click with the LB on the [C.NOTIF] switch.
Capítulo / Chapter 6
Página / Page 36 de / of 157
RESULT
The switch changes to YELLOW.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
ACTION
RESULT
3.
Click on the [OK] icon
4.
Finish the operation by performing a close action (see 3.7)
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
PY
ACTION
1.
Perform the FP View action (see 6.2.1.1.3.2)
2.
Click with the LB on the [ATD] switch.
3.
4.
N
I
LIM
RE
P
Y
R
A
G
N
I
Confirm or modify the data displayed on the “CSSR” field.
R
O
F
N
I
RA
CO
RESULT
Y
L
N
O
The switch becomes YELLOW. The accessible fields are WHITE
background and a BLUE frame surrounds the “ATD” field.
PU
O
P
R
SE
The FP status changes to “Active”.
T
Finish the operation by performing a close action (see 3.7)
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.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 37 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.1.1.3.12
ACTION: CANCEL ATD
ACTION
RESULT
1.
Perform the FP View action (see 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.
4.
Finish the operation by performing a close action (see 3.7)
RY
C
Y
P
O
SE
NOTE: This action can be performed only if a previous ATD action was executed.
6.2.1.1.3.13
A
O
N
I
P
ACTION: ESTIMATE ACTIONS
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
ACTION
1.
Perform the FP View action (see 6.2.1.1.3.2)
2.
Click with the LB on the [EST] switch.
3.
Enter the future fix point (“FixPoint” field) of the flight plan
route, if not displayed, and confirm or modify the values for
the “ETO” and “CFL” fields. The ETO field, although
accessible, is not mandatory due to the system automatically
calculation.
Capítulo / Chapter 6
Página / Page 38 de / of 157
Y
L
N
O
RESULT
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.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
4.
Click with the LB on the [OK] icon
5.
Finish the operation by performing a close action (see 3.7)
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
1.
Perform the FP View action (see 6.2.1.1.3.2)
2.
Click with the LB on the [POS] switch.
RY
C
Y
P
O
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.
4.
Finish the operation by performing a close action
(see 3.7)
O
The switch changes to YELLOW and the accessible fields for the
action are displayed in WHITE background.
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
3.
Y
L
N
RESULT
SE
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.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 39 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.1.1.3.15
ACTION: CONFIRM/MODIFY ATA
ACTION
1.
Perform the FP View action (see 6.2.1.1.3.2)
2.
Click with the LB on the [ATA] switch.
3.
Confirm or modify the estimated time of arrival in the
“ETA” field.
4.
Finish the operation by performing a close action (see
3.7)
RESULT
The switch changes to YELLOW and the accessible fields for the
action are displayed in WHITE background. A BLUE frame is
displayed around the “ETA” field.
Y
P
O
Y
L
N
Compulsory Fields: Callsign, ORIG, ETD and ETA only if the FP visualization action has not been
previously performed.
C
O
Y
E
once the ATA action
has been executed.
NOTE: It is impossible to perform the EST or ACT actions
R
S
A
O
N
I
P
M
R
I
6.2.1.1.3.16 ACTION: REQUEST FLIGHT
PRINTING
L PLAN STRIPS P
U
E
G
PR
N
NI
I
A
R
T
R
O
F
ACTION
RESULT
1. Perform the FP visualization action (see 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
Capítulo / Chapter 6
Página / Page 40 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
The switch becomes YELLOW, and the accessible fields for the
action are WHITE background.
3. Click on the [Mod] switch.
RY
C
Y
P
O
SE
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
I
6.2.1.1.4 ERROR MESSAGE AREAIN
A
It displays the error associated R
to the field where the mouse is focused on.
T
A list of error messages is provided in Appendix E.
R
O
F
Y
L
N
O
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)
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 41 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.1.1.5
LIST OF SYNONYMS
When two or more Flight Plans have the same Callsign and the Controller performs a view operation
([View] switch), the System displays the List of Synonyms over the FP Operation Window.
This List of Synonyms includes all flight plans that have the same Callsign.
RY
C
Y
P
O
SE
Y
L
N
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
I
N
I
Click twice on a Flight Plan within the List of Synonyms to present all FP data within their
corresponding fields in the FP Operation A
Window.
TR
R
O
6.2.1.1.6 AREA WARNINGS WINDOW
F
This window is automatically displayed on top of the FP Operation Window. It allows warning the
Figure 6.2.1.1.5-1. List of Synonyms
controller on the following cases:
When the flight is about to cross a restricted area.
When the flight has already crossed the restricted area.
Capítulo / Chapter 6
Página / Page 42 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Y
P
O
Figure 6.2.1.1.6-1. Area Warnings Window
RY
C
SE
Y
L
N
O
Following table describes the information included in the Area Warnings Window:
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Table 6.2.1.1.6-1. Area Warnings Window
Field
Name of the restricted area.
Entry fixpoint before the restricted area. If the flight is about to cross the restricted area, the displayed fixpoint is the first fix of the flight
plan route within the restricted area.
Fix point next to the restricted area.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 43 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.2
Icon [FP Rtr.] Actions on Retrieved FP
This icon triggers all procedures related to the FPs data retrieval for subsequent actions. When
clicking on the [FP Rtr.] icon, the FP Retrieval Window is displayed.
Figure 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:
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
Figure 6.2.2.1-1. FP Retrieval Window
Capítulo / Chapter 6
Página / Page 44 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.2.1.1
EDITION AREA
Most of the fields are the same as for the FP Operation Window. Following table shows those fields,
which are different including a description with their valid data.
Table 6.2.2.1.1-1. FP Retrieval Window. Edition Area
Field
Description
Valid Data
ROUTE
One or more fixes. If there is more than one, they are separated by
the AND (+) or OR (|) operators
Name of fixes known by the System
FROM
Time determining the start of a temporal filter for FPL retrieval
HHMM (00 to 23 and 00 to 59)
UNTIL
Time determining the end of a temporal filter for FPL retrieval
HHMM (00 to 23 and 00 to 59)
6.2.2.1.2
COMMAND AREA
Y
P
O
Y
L
N
Following table shows the different commands included in the FP Retrieval Window.
RY
C
Table 6.2.2.1.2-1. FP Retrieval Window. Command Area
Icon/Switch
Summary Retrieve
OK
CLOSE
CLEAR
Pr All
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Description
SE
O
Display the number of FPs matching the criteria (filters).
Trigger the actions performed in the current window.
Close the window. If actions were not previously validated ([OK]), they will not be taken into account by the
system.
Delete the data displayed on the fields of the window.
Print all the Retrieved FP.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 45 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.2.1.2.1
ACTION: RETRIEVE MULTIPLE FPL
ACTION
1.
Click with the LB on the [FP Rtr.] icon.
2.
To display the FPs:
2.1.
2.2.
3.
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.
RESULT
The FP Retrieval Window is displayed.
The Retrieved Flight Plan(s) Window is displayed with the flight plan(s)
matching the specific parameters.
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
If input parameters are unknown, click on
the [OK] icon.
SE
Y
L
N
O
The Retrieved Flight Plan(s) Window is displayed with all flight plans.
Once the Retrieved Flight Plan(s) Window is
displayed, it is possible to select one of the FPs:
3.1.
By clicking twice on the corresponding FP.
3.1.1.
The selected FP is displayed on the FP Operation Window (action
mode). That is, the FP Retrieval Window is closed and the FP
Operation Window (action mode) is displayed.
From this point on, all possible FP
actions can be performed on the
selected FP (see 6.2.1.1.3)
Capítulo / Chapter 6
Página / Page 46 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
ACTION
3.2.
4.
RESULT
By clicking on the [Summary Retrieve]
switch and then on the [OK] icon.
An indication of the number of FPs that matches the selection criteria is
displayed.
Finish the operation by performing a close action
(see 3.7)
Compulsory Fields: None.
C
Y
P
O
Y
L
N
O
E
It displays the error associated to the field where
Son.
A the mouse is focused
O
N
I E.
A list of error messages is provided in Appendix
P
M
R
I
L
U
E
P
R PLAN(S) WINDOW
6.2.2.1.4 RETRIEVED FLIGHT
G icon of the FP Retrieval Window.
P
N[OK]
This window is displayed when clicking on Ithe
N
The FPs not in view can be visualizedI by means of the vertical scroll bar available in the window right
A
side.
R
T
R
O
F
6.2.2.1.3
ERROR MESSAGE AREA
RY
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
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 47 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Table 6.2.2.1.4-1. Retrieved Flight Plan(s) Window. List Element
Element
Description
Callsign
Aircraft Identifier
R
Flight Rules
N
Number of Aircrafts
Type
Aircraft Type
Orig
Departure Aerodrome
EOBD
Estimated Off-Block Date
EOBT
Estimated Off-Block Time
Speed
Cruising Speed
RFL
Requested Flight Level
Dest
Destination Aerodrome
ETA
Estimated Time of Arrival
SSRC/C
SSR Code
Route
FP Route
Status
FP Status
Capítulo / Chapter 6
Página / Page 48 de / of 157
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.3
Icon [FP MIN.] Minimal Flight Plan
This icon triggers the creation of a Minimal FP.
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:
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
I
N
I
6.2.3.1.1 EDITION AREA
A
R
All the fields in this window are
compulsory
and have to be filled out.
T
R
O
F
SE
Y
L
N
O
Figure 6.2.3.1-1. Minimal FP Window
Table 6.2.3.1.1-1. Minimal FP Window. Edition Area
Field
Description
Valid Data
CALLSIGN
Aircraft identification
1 to 8 alphanumeric characters
CSSR
SSR code
4 digits
ORIG
Departure Aerodrome
4 alphanumeric characters
DEST
Destination Aerodrome
4 alphanumeric characters
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 49 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.3.1.2
COMMAND AREA
Following table shows the different commands included in the Minimal FP Window.
Table 6.2.3.1.2-1. Minimal FP Window. Command Area
Icon
Description
OK
Create a FP with the minimum fields.
CLOSE
Close the window. If actions were not previously validated, they will not be taken into account by the
system.
CLEAR
Delete the data displayed on the fields of the window.
6.2.3.1.2.1
ACTION: CREATE A MINIMAL FP
PY
ACTION
1.
RESULT
N
I
LIM
RE
P
N
I
RA
T
Fill out all the fields in the Minimal FP Window and click
[OK].
3.
Finish the operation by performing a close action (see 3.7)
Compulsory Fields: All.
6.2.3.1.3
Y
R
A
G
N
I
2.
R
O
F
Y
L
N
The Minimal FP Window is displayed.
Click with the LB on the [FP Min.] icon,
CO
PU
O
P
R
SE
O
If data are correct, then the FP is created, else the error is
displayed at the window and the action is not performed.
ERROR MESSAGE AREA
It displays the error associated to the field where the mouse is focused on.
A list of error messages is provided in Appendix E.
Capítulo / Chapter 6
Página / Page 50 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.4
Icon [RPL Act.] Actions on Repetitive Flight Plan
This icon triggers all procedures related to RPL actions. When clicking on the [RPL Act.] icon, the RPL
Operation Window is displayed.
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
Y
P
O
Y
L
N
Where file_rpls must include all rpls to be loaded in Eurocontrol standard format
(Document IFPS User Manual).
C
O
Y
E
NOTE: The off-line RPL management facility isR
not available in the system.
Nevertheless, the on-line
S
A
functionality related to RPLs is allowed
O
N
I
P
M
R
6.2.4.1 RPL Operation WindowI
L
U
P fields to be filled in by the operator (edition
The RPL Operation WindowE
consists of a form including
area), a command area atR
the bottom of the window
and an error message area.
G
P
IN
N
I
A
TR
R
O
F
Figure 6.2.4.1-1. RPL Operation Window
6.2.4.1.1
EDITION/ACTIVATION AREA
Following table shows for each field included in the "RPL Operation” Window, a description of those
fields with their valid data.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 51 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Table 6.2.4.1.1-1. RPL Operation Window. Edition/Activation Area
Field / Switch
Description
Valid Data
Callsign
Aircraft Identification
1 to 8 alphanumeric characters
R
Flight Rules
I=
V=
Y=
Z=
SP =
NV =
Blank =
N
Number of Aircrafts
Up to 2 numeric characters (1-99)
TYPE
Type of Aircraft
2 to 4 alphanumeric characters The first one is an
alphabetic character.
It must be known by the system.
W
Wake Turbulence Category
L=
M=
H=
RY
C
IFR
VFR
IFR followed by VFR
VFR followed by IFR
IFR (single pilot)
IFR (night)
I
Y
P
O
light
medium
heavy
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
EQ
Navigation Equipment
ORIG
Departure Aerodrome
Four alphabetic characters.
If unknown, then the “ZZZZ” keyword.
If created while aircraft is airborne, then the “AFIL”
keyword.
ETD
Estimated Time of Departure/ Revised Estimated Time of
Departure or Actual Time of Departure (depending on the
FP status)
HHMM (00 to 23 and 00 to 59)
SPEED
Cruising Speed
Kxxxx: 4 numerical characters (Km/h)
Nxxxx: 4 numerical characters (Knots)
Mxxx: 3 numerical characters (Number of Mach)
RFL
Requested Flight Level
3 numerical characters (hundreds of feet)
DEST
Destination Aerodrome
Four alphabetic characters.
EET
Elapsed Estimated Time
HHMM (00 to 23 and 00 to 59)
ROUTE
FP Route
Up to 160 characters.
See the NOTE on “Route Field Validation Rules”
included in section 6.2.1.1.2.2.
FREE TEXT
Notes
Not more than 3 alphabetic characters.
VALID PERIOD
FROM
Time defining the start of the validity period for the RPL.
YYMMDD (00 to 99, 01 to 12 and 01 to 31)
UNTIL
Time defining the end of the validity period for the RPL.
YYMMDD (00 to 99, 01 to 12 and 01 to 31)
OPERATION DAYS
MTWTFSS
Indicate the days of the week when the RPL is scheduled.
Capítulo / Chapter 6
Página / Page 52 de / of 157
From Monday to Sunday
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.4.1.2
COMMAND AREA
Following table shows the different commands, which are included in the RPL Operation Window.
Table 6.2.4.1.2-1. RPL Operation Window. Command Area
Icon / Switch
Command
View
Display the RPL data.
Create
Create a new RPL.
Modify
Modify an RPL.
Cancel
Terminate an RPL.
OK
Trigger all actions performed in current window.
CLOSE
Close the window. If the actions were not previously validated, ([OK]) they will not be taken into account by the
system.
CLEAR
Delete the data displayed on the fields of the window.
Pr All
Print all the retrieved FP
C
Y
P
O
Y
L
N
O
E
6.2.4.1.2.1
ACTION: COMMON STEPSA
IN ACTIONS ON RPLSS
O
N
I
P
1.
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
NOTE: AccordingF
to 6.2.4, the “off-line” facility of RPL management is not available in the System.
RY
ACTION
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).
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.
2.
Enter the specific data in the corresponding fields to
retrieve the RPL.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
RESULT
The switch changes to YELLOW.
Capítulo / Chapter 6
Página / Page 53 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
ACTION
3.
RESULT
Finish the operation by performing a close action (see
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.
NOTE: This action may start from a previous visualization
action (see 6.2.4.1.2.2).
2.
Input data in the corresponding fields.
The [Operation Days] switches are activated
(YELLOW) when the window is displayed. To inhibit
them, click, with the mouse LB, on the corresponding
day of the week switch.
RESULT
The switch changes to YELLOW.
RY
C
Y
P
O
SE
Y
L
N
O
O
NA
I
P
R
IM
L
U
E
P
3.
R
G
P
N
Compulsory Fields: CALLSIGN, ORIG, VALIDITY
(FROM and UNTIL), and OPERATION
NIthePERIOD
DAYS (the days of the week are activated when
RPL Operation Window is displayed. To inhibit
I
them, click on the corresponding day). A
Rif the visualization action was not previously performed.
The mandatory fields are displayedT
only
Accessible Fields: All of them.R
FO
Finish the operation by performing a close action (see
3.7)
6.2.4.1.2.4
ACTION: MODIFY RPL
ACTION
1.
Perform the Visualization action 6.2.4.1.2.2.
2.
Click with the LB on the [Modify] switch.
3.
Modify the required fields. Some of them do not allow
modifications and some others are mandatory.
Capítulo / Chapter 6
Página / Page 54 de / of 157
RESULT
The switch becomes YELLOW and the accessible fields for the action
are displayed in WHITE background.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
ACTION
4.
RESULT
Finish the operation by performing a close action (see
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 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.
RESULT
Y
P
O
Y
L
N
The switch becomes YELLOW and the accessible fields for the action
are displayed in WHITE background.
RY
C
SE
O
O
NA
I
P
R
IM
3.
L
U
E
P
R
Compulsory Fields: CALLSIGN,
ORIG, VALIDITY
PERIOD
(FROM and UNTIL), and OPERATION
G
P
DAYS (the days of the week are activated when
the
RPL
Operation
Window is displayed. To inhibit
IN
them, click on the corresponding day). N
I
The mandatory fields are displayedA
only if the RPL visualization action was not previously performed.
Accessible Fields: All of them. R
T
R
O
6.2.4.1.3 ERROR
FMESSAGE AREA
Finish the operation by performing a close action (see
3.7)
It displays the error associated to the field where the mouse is focused on.
A list of error messages is provided in Appendix E.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 55 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.5
Icon [RPL Rtr.] Repetitive Flight Plans Retrieval
This icon is related to all the RPL data retrieval procedures for subsequent actions.
When clicking on the [RPL Rtr.] icon, the RPL’s Retrieval Window is displayed.
Figure 6.2.5-1. [RPL Rtr.] Icon
NOTE: If the FDD is associated to an SDD, this option can be not available.
6.2.5.1
RPLs Retrieval Window
This window allows defining the filters for the RPLs retrieval and displaying those data matching the
set of specific parameters entered by the operator.
Y
P
O
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.
RY
C
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
Figure 6.2.5.1-1. RPLs Retrieval Windows
Capítulo / Chapter 6
Página / Page 56 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.5.1.1
EDITION/ACTIVATION AREA
Fields included in this area are the same as for the RPL Operation Window (see section 6.2.4.1.1).
6.2.5.1.2
COMMAND AREA
Following table shows the different commands, which are included in the RPLs Retrieval Window.
Table 6.2.5.1.2-1. RPLs Retrieval Window. Command Area
Icon/Switch
Description
Summary Retrieve
Not available
OK
Trigger the actions performed in current window.
CLOSE
Close the window. If the actions were not previously validated, they will not be taken into account by the
system.
CLEAR
Delete the data displayed on the fields of the window.
Pr All
Print all the retrieved FP.
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
SE
Y
L
N
O
Capítulo / Chapter 6
Página / Page 57 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.5.1.2.1
ACTION: RETRIEVE MULTIPLE RPLS
ACTION
1.
Click with the LB on the [RPL Rtr.] icon.
2.
To display the RPLs:
2.1.
2.2.
3.
4.
If input parameters are known, enter the data
in the corresponding fields and click on the
[OK] icon.
RESULT
The RPLs Retrieval Window is displayed.
The Retrieved RPLs Window is displayed with the RPLs matching the
specific parameters.
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
If input parameters are unknown, click on the
[OK] icon.
SE
Y
L
N
O
The Retrieved RPLs Window is displayed with all RPLs.
Once the Retrieved RPLs Window is displayed, it is
possible to select one of the RPLs:
3.1.
Click twice on the corresponding RPL.
3.2.
From this point on, all possible RPLs actions
can be performed on the selected RPL (see
6.2.4.1.2.1)
The selected RPL is displayed on the RPL Operation Window. That is,
the RPLs Retrieval Window is closed and the RPL Operation Window
is displayed instead of.
Finish the operation by performing a close action (see
3.7)
Compulsory Fields: None.
6.2.5.1.3
ERROR MESSAGE AREA
It displays the error associated to the field where the mouse is focused on.
A list of error messages is provided in Appendix E.
Capítulo / Chapter 6
Página / Page 58 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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
Callsign
Aircraft Identification
R
Flight Rules
N
Number of Aircrafts
Type
Aircraft Type
Orig
Destination Aerodrome
ETD
Estimated Time of Departure
Speed
Cruising Speed
RFL
Dest
ETA
SSRC/C
Route
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Requested Flight Level
Destination Aerodrome
O
Estimated Time of Arrival
SSR Code
FP Route
Valid Period (From-Until)
Start and end time for the RPL
Operat. Days (MTWTFSS)
Days of the week
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
SE
Y
L
N
Capítulo / Chapter 6
Página / Page 59 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.6
Icon [Runw] Airport Runways Actions
This icon allows performing actions on the airport runways. When clicking on the [Runw] icon, the
Airport Runways Window is displayed.
Figure 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.
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
EDITION AREAO
F
SE
Y
L
N
O
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:
Table 6.2.6.1.1-1. Airport Runways Window. Edition Area
Field
Description
AIRPORT
The desired airport name whose runways are to be viewed and/or
modify.
Runways
Runway Identification.
Dep / Arr (switches)
Configure the runway use (arrivals, departures or both)
Capítulo / Chapter 6
Página / Page 60 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.6.1.2
COMMAND AREA
Following table explains the commands included in the Airport Runways Window:
Table 6.2.6.1.2-1. Airport Runways Window. Command Area
Icon/Switch
Command
View
Display of the runways configuration for the selected airport.
Modify
Perform modifications over an airport runway.
OK
Trigger the actions performed in current window.
CLOSE
Close the window. If the actions were not previously validated, they will not be taken into account.
CLEAR
Delete the data displayed on the fields of the window.
6.2.6.1.2.1
ACTION: VISUALIZATION OF AIRPORT RUNWAYS
ACTION
1.
Click with the LB on the [RUNW] icon.
2.
Enter the corresponding airport (“Airport” field) and click on the
[View] switch.
3.
Finish the operation by performing a close action (see 3.7)
ACTION
1.
Perform the visualization action.
2.
Click with the LB on the [Modify] switch.
3.
Modify the required runways.
4.
Finish the operation by performing a close action (see
3.7)
Y
L
N
RESULT
The Airport Runways Window is displayed.
O
The switch changes to YELLOW and the data are
displayed on their corresponding fields.
O
N
I
P
M
R
I
L
ACTION: MODIFY AIRPORT RUNWAYS
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Compulsory Fields: AIRPORT.
6.2.6.1.2.2
Y
R
A
C
Y
P
O
SE
RESULT
The switch changes to YELLOW.
Compulsory Fields: AIRPORT.
6.2.6.1.3
ERROR MESSAGE AREA
It displays the error associated to the field. A list of error messages is provided in Appendix E.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 61 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.7
Icon [AFTN TX] AFTN Transmission
The [AFTN TX] icon allows the operator to edit and transmit AFTN messages.
When clicking on this icon, a menu is displayed to select the type of AFTN message. There are three
options included in the menu as shown in following figure:
Figure 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:
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Error Message Area
SE
Y
L
N
O
Edition
Area
Command Area
Figure 6.2.7.1-1. ICAO AFTN Transmission Window
6.2.7.1.1
EDITION AREA
Following table lists, for each field included in the ICAO AFTN Transmission Window, a description
with the valid data.
Capítulo / Chapter 6
Página / Page 62 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Table 6.2.7.1.1-1. ICAO AFTN Transmission Window. Edition Area
Field
Description
Valid Data
Priority
AFTN priority indicator
Follow ICAO rules
Addresses
Transmission Addresses
Up to 22 AFTN addresses separated by blanks.
Each AFTN address must be a sequence of 8 letters
Filling Time
Time when the flight plan was filed out at
the Flight Service Office. The filing time is
extracted from all AFTN messages.
DDHHMM (00 to 31, 00 to 23 and 00 to 59)
The time is a future time. If the field is not filled in, the current
time (DDHHMM) will be automatically filled in.
Originator
Originator Indicator
A sequence of 8 letters. If not filled in, the Local Address
defined in adaptation will be automatically entered.
Message Type
Type of message
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
RY
Aircraft Identification
SSR Mode
SSR Code
Flight Rules
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
Aircraft Identification (ACID or Callsign)
Alphanumeric characters (1 to 7).
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
4 octal digits
Left blank = it allows FDP to automatically assign an SSR
Code.
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
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 63 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Table 6.2.7.1.1-1. ICAO AFTN Transmission Window. Edition Area
Field
Description
Valid Data
Type Flight
Aircraft Type
S=
scheduled
N=
non-scheduled
G=
general aviation
M=
military
X=
other
Left blank = general aviation
Number
Number of Aircrafts
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 Turb. Cat
Wake Turbulence Category
L=
M=
H=
Equipment
Navigation/Communication Equipment
RY
Y
P
O
light
medium
heavy
C
O
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.
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Capítulo / Chapter 6
Página / Page 64 de / of 157
Y
L
N
SE
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Table 6.2.7.1.1-1. ICAO AFTN Transmission Window. Edition Area
Field
Field
Description
Valid Data
SSR Equipment
RY
Departure
Aerodrome
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
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
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
Aerodrome of departure
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.
HHMM (00 to 23 and 00 to 59)
Point with an associated information for a
FP.
Alphanumeric characters (2 to 5).
Time at the reference point
HHMM (00 to 23 and 00 to 59)
Auth. Level
Cleared Level at the reference point.
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.
Supl. Level
Supplementary Level at the reference
point.
See format/valid data for the “Auth. Level” field.
Cross C.
Crossing Condition
A= Above
B= Below
Cruising Speed
Cruising Speed
Knots: Nxxxx or xxx(x)
Kilometres per hour: Kxxx(x)
Mach number: Mxxx
EOBT
Reference Point
Time
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 65 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Table 6.2.7.1.1-1. ICAO AFTN Transmission Window. Edition Area
Field
Description
Valid Data
Level
Planned level for the first step or the whole
route to be flown.
See format/valid data for the “Auth. Level” field.
Route
Flight Plan Route
Names of fix points known by the System.
Destination Aero.
Destination Aerodrome
4 alphabetic characters.
If unknown ZZZZ.
Total EET
Total Estimated Elapsed Time (Estimated
flight duration)
HHMM (00 to 23 and 00 to 59)
Altn Aerodrome
Alternative Aerodrome
ICAO aerodrome indicator.
4 alphabetic characters.
If unknown ZZZZ.
2nd. Altn Aerodrome
Second Alternative Aerodrome
ICAO aerodrome indicator.
4 alphabetic characters.
If unknown ZZZZ.
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Capítulo / Chapter 6
Página / Page 66 de / of 157
SE
Y
L
N
O
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Table 6.2.7.1.1-1. ICAO AFTN Transmission Window. Edition Area
Field
Other Information
Description
Statement of
information.
any
other
Valid Data
necessary
RY
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 fourletter 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.
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Emergency
Description
Emergency Description
Free Text
Supplementary
information
Additional Information
Free Text
Alert Information
Alert Information
Free Text
Communication
Information
Communication Information
Free Text
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
SE
Y
L
N
O
Capítulo / Chapter 6
Página / Page 67 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.7.1.2
COMMAND AREA
Following table describes commands included in the ICAO AFTN Transmission Window.
Table 6.2.7.1.2-1. ICAO AFTN Transmission Window. Command Area
Icon/Switch
Command
VIEW
Information visualization.
TRANS
Send the information.
AUTO SEND
Insert the message into the System.
OK
Trigger the performed actions in the window.
CLOSE
Close the ICAO AFTN Transmission Window.
CLEAR
Delete the information included in the ICAO AFTN Transmission Window.
6.2.7.1.2.1
Y
P
Y
ACTION: EDIT/TRANSMIT ICAO AFTN MESSAGES
L
O
N
C
O
Y
E
R
S
A
O
N
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
ACTION
1.
Select form the [AFTN TX] icon the (ICAO AFTN)
option. Click on TRANS bi-state button.
Capítulo / Chapter 6
Página / Page 68 de / of 157
RESULT
The ICAO AFTN Transmission Window is displayed.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
ACTION
2.
Fill in the fields. The mandatory fields depend on the
type of message being edited.
3.
The data transmission depends on the addressee:
3.1.
To the ATC System which is generating the
message– click on the [Auto Send] switch.
3.2.
To the addresses edited in the associated
field – click on the [Trans] icon.
RESULT
RY
C
Y
P
O
SE
Y
L
N
O
In all cases, the ICAO AFTN message is transmitted when the data
entered are correct.
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
If the data entered are erroneous, an error message is displayed.
If mandatory fields are not filled in, an error message is displayed.
4.
Finish the operation by performing a close action
(see 3.7)
Compulsory Fields: It depends on the type of message.
6.2.7.1.3
ERROR MESSAGE AREA
It displays the error associated to the field where the mouse is focused on.
A list of error messages is provided in Appendix E.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 69 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
The layout of this window is shown if figure below:
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
Figure 6.2.7.2-1. ICAO ADEXP Transmission Window
6.2.7.2.1
EDITION AREA
Following table lists, for each field included in the ICAO ADEXP Transmission Window, a description
with the valid data.
Table 6.2.7.2.1-1. ICAO ADEXP Transmission Window. Edition Area
Field
Description
Valid Data
Priority
ADEXP priority indicator
Follow ICAO rules
Addresses
Transmission Addresses
Up to 22 addresses separated by blanks.
Each address must be a sequence of 8 letters
Capítulo / Chapter 6
Página / Page 70 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Table 6.2.7.2.1-1. ICAO ADEXP Transmission Window. Edition Area
Field
Description
Valid Data
Filling Time
Time when the flight plan was filed out
at the Flight Service Office. The filing
time is extracted from all ADEXP
messages.
DDHHMM (00 to 31, 00 to 23 and 00 to 59)
The time is a future time. If the field is not filled in, the current
time (DDHHMM) will be automatically filled in.
Originator
Originator Indicator
A sequence of 8 letters. If not filled in, the Local Address
defined in adaptation will be automatically entered.
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
SSR Mode
SSR Code
RY
C
Y
P
O
SE
Y
L
N
O
Aircraft Identification (ACID or Callsign)
Alphanumeric characters (1 to 7).
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
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
ICAO SSR Code
4 octal digits
Left blank = it allows FDP to automatically assign an SSR Code.
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
Type Flight
Aircraft Type
S=
scheduled
N=
non-scheduled
G=
general aviation
M=
military
X=
other
Left blank = general aviation
Number
Number of Aircrafts
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.
Flight Rules
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 71 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Table 6.2.7.2.1-1. ICAO ADEXP Transmission Window. Edition Area
Field
Description
Valid Data
Wake Turb. Cat
Wake Turbulence Category
L=
M=
H=
Equipment
Navigation/Communication 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.
RY
light
medium
heavy
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
Field
SSR Equipment
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
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)
Mode S (Transponder can send both aircraft
S=>
identification and pressure altitude transmission)
Blank = C
Departure
Aerodrome
Aerodrome of departure
4 alphabetic characters.
If unknown, then the “ZZZZ” Word.
If created while aircraft is airborne, then the “AFIL” Word.
Capítulo / Chapter 6
Página / Page 72 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Table 6.2.7.2.1-1. ICAO ADEXP Transmission Window. Edition Area
Field
Description
Valid Data
EOBT
EOBT (for known departure aerodrome)
Or
Estimated or actual arrival time
(EET/ETA) to the first route fix-point
referenced in the flight plan.
HHMM (00 to 23 and 00 to 59)
Reference Point
Point with an associated information for
a FP.
Alphanumeric characters (2 to 5).
Time
Time at the reference point
HHMM (00 to 23 and 00 to 59)
Auth. Level
Cleared Level at the reference point.
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.
Supl. Level
Supplementary Level at the reference
point.
See format/valid data for the “Auth. Level” field.
Cross C.
Crossing Condition
A= Above
B= Below
Cruising Speed
Level
Route
Destination Aero.
Total EET
Altn Aerodrome
2nd. Altn Aerodrome
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Cruising Speed
SE
Y
L
N
O
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.
See format/valid data for the “Auth. Level” field.
Flight Plan Route
Names of fix points known by the System.
Destination Aerodrome
4 alphabetic characters.
If unknown ZZZZ.
Total Estimated Elapsed
(Estimated flight duration)
Time
HHMM (00 to 23 and 00 to 59)
Alternative Aerodrome
ICAO aerodrome indicator.
4 alphabetic characters.
If unknown ZZZZ.
Second Alternative Aerodrome
ICAO aerodrome indicator.
4 alphabetic characters.
If unknown ZZZZ.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 73 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Table 6.2.7.2.1-1. ICAO ADEXP Transmission Window. Edition Area
Field
Other Information
Description
Valid Data
Statement of any other necessary
information.
Up to 67 characters, digits, slashes “/”, dots “.” or blank spaces,
with the appropriate abbreviation followed by a slash and the
information to be recorded.
EET/ Significant points or FIR boundary designators and EET
over such points or FIR boundaries.
RIF/
The route details the revised destination aerodrome
followed by the ICAO location indicator of the
aerodrome (4 ICAO letters).
REG/ Aircraft registration, only if necessary and if different
from the aircraft identification in the “Aircraft
Identification” field.
SEL/ SELCAL code, prescribed by the appropriate ATS
authority.
OPR/ Operator name, if it is not clear in the “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.
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Emergency
Description
Emergency Description
Free Text
Supplementary
information
Additional Information
Free Text
Alert Information
Alert Information
Free Text
Communication
Information
Communication Information
Free Text
Capítulo / Chapter 6
Página / Page 74 de / of 157
SE
Y
L
N
O
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.7.2.2
COMMAND AREA
Following table describes commands included in the ICAO ADEXP Transmission Window.
Table 6.2.7.2.2-1. ICAO AFTN Transmission Window. Command Area
Icon/Switch
Command
VIEW
Information visualization.
TRANS
Send the information.
AUTO SEND
Insert the message into the System.
OK
Trigger the performed actions in the window.
CLOSE
Close the ICAO ADEXP Transmission Window.
CLEAR
Delete the information included in the ICAO ADEXP Transmission Window.
6.2.7.2.2.1
Y
P
Y
ACTION: EDIT/TRANSMIT ICAO ADEXP MESSAGES
L
O
N
C
O
Y
E
R
S
A
O
N
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
ACTION
1.
Select form the [AFTN TX] icon the (ICAO ADEXP)
option.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
RESULT
The ICAO ADEXP Transmission Window is displayed.
Capítulo / Chapter 6
Página / Page 75 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
ACTION
2.
Fill in the fields. The mandatory fields depend on the
type of message being edited.
3.
The data transmission depends on the addressee:
3.1.
To the ATC System which is generating the
message– click on the [Auto Send] switch.
3.2.
To the addresses edited in the associated
field – click on the [Trans] icon.
RESULT
RY
C
Y
P
O
SE
Y
L
N
O
In all cases, the ICAO ADEXP message is transmitted when the data
entered are correct.
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
If the data entered are erroneous, an error message is displayed.
If mandatory fields are not filled in, an error message is displayed.
4.
Finish the operation by performing a close action
(see 3.7)
Compulsory Fields: It depends on the type of message.
6.2.7.2.3
ERROR MESSAGE AREA
It displays the error associated to the field where the mouse is focused on.
A list of error messages is provided in Appendix E.
Capítulo / Chapter 6
Página / Page 76 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
The layout of this window is shown if figure below:
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
Error Message
Area
Command Area
R
FO
Y
L
N
Edition Area
SE
O
Figure 6.2.7.3-1. Free AFTN Transmission Window
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 77 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.7.3.1
EDITION AREA
Following table lists for each field included in the Free AFTN Transmission Window a description with
the valid data.
Table 6.2.7.3.1-1. Free AFTN Transmission Window. Edition Area
Field
Description
Valid Data
Priority
AFTN priority indicator
Follow ICAO rules
Addresses
Transmission Addresses
Up to 22 addresses separated by blank spaces.
Each AFTN address must be a sequence of 8 characters.
Filling Time
Time when the flight plan was filled in at the
Flight Service Office. The filling time is
extracted from all AFTN messages.
DDHHMM (00 to 31, 00 to 23 and 00 to 59)
The time will be a future time. If the field is not filled in, the
current time (DDHHMM) will be automatically filled in.
Originator
Originator Indicator
A sequence of 8 letters. If not filled in, the Local Address
defined in adaptation will be automatically entered.
Free Text
Any text
Text
Y
P
O
Y
L
N
C
O
Y
E
R
Following table describes the commands included in the "FREE AFTN Transmission” Window.
S
A
O
N
I
P
M
R
I
L
U
E
P
G
PR
N
NI
I
A
R
T
R
O
F
6.2.7.3.2
COMMAND AREA
Table 6.2.7.3.2-1. Free AFTN Transmission Window. Command Area
Icon/Switch
Command
AUTO SEND
Message self-sending. That is, the message is sent to the message originator.
PRINT
Not available.
TRANS
Send the AFTN message.
CLOSE
Close the Free AFTN Transmission Window.
CLEAR
Delete the information displayed in the Free AFTN Transmission Window.
Capítulo / Chapter 6
Página / Page 78 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.7.3.2.1
ACTION: EDIT/TRANSMIT TEXT AFTN MESSAGES
ACTION
RESULT
1.
The Free AFTN Transmission Window is displayed.
Click on the [AFTN TX] icon and in the (FREE AFTN)
option.
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
2.
Enter data into the corresponding fields.
3.
The data transmission depends on the addressee:
3.1
SE
Y
L
N
O
To the ATC System which is generating the
message– click on the [Auto Send] switch.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 79 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
ACTION
RESULT
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.
RY
C
Y
P
O
SE
Y
L
N
O
O
NA
I
P
R
IM
L
U
E
P
4.
R
G
P
N
Compulsory Fields: At least one of the three “Addresses”
NI fields must be completed.
I
6.2.7.3.3 ERROR MESSAGE AREA A
R where the mouse is focused on.
Tfield
It displays the error associated to the
R
A list of error messages is provided in Appendix E.
O
F
6.2.7.4 SVC Transmission Window
If mandatory fields are not filled in, an error message is displayed.
Finish the operation by performing a close action (see 3.7)
When selecting from the [AFTN TX] icon the (SVC) option, the SVC Transmission Window is
displayed.
The SVC Transmission Window consists of an edition area including fields to be filled in by the
operator and a command area at the bottom of the window.
The layout of this window is shown if figure below:
Capítulo / Chapter 6
Página / Page 80 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Edition Area
Command Area
Figure 6.2.7.4-1. SVC Transmission Window
6.2.7.4.1
EDITION AREA
Following table lists a description for each field included in the SVC Transmission Window.
Table 6.2.7.4.1-1. SVC Transmission Window. Edition Area
Field
Line 1 / Line 2
RY
C
Y
P
O
Description
AFTN line through which the messages are sent.
SE
Y
L
N
O
O
NA
I
P
R
IM
L
U
E field is empty, onlyP the message corresponding to the sequence
If the “Sorting Number (higher)”
R
G field will be sent. If both fields have data, the
P“Sorting NumberIN
number entered in the
(lower)”
messages, whose sequence number is among the values entered in those fields, will be sent.
Nbe simultaneously transmitted is 10.
I
The maximum message number that
can
A
R
T
6.2.7.4.2 COMMAND AREA
R
Following table lists O
the different commands included in the SVC Transmission Window.
F
Sorting Number (Lower)
Editable field. Sequence number of the service AFTN message to transmit, or minimum
sequence number of the group of messages to be transmitted (000-999).
Sorting Number (Higher)
Editable field. Maximum sequence number of the group of messages to transmit (000-999).
Table 6.2.7.4.2-1. SVC Transmission Window. Command Area
Icon
Command
OK
Send the selected service AFTN message or group of messages.
CANCEL
Close the SVC Transmission Window.
CLEAR
Delete the information displayed on the SVC Transmission Window.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 81 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.7.4.2.1
ACTION: TRANSMIT SVC MESSAGES
ACTION
RESULT
1.
Click on the [AFTN TX] icon and select the (SVC)
option.
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)
The SVC Transmission Window is displayed.
If only a message is transmitted, only first
number must be completed.
RY
C
Y
P
O
A
O
N
I
b)
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
4.
T
R of the AFTN message.
Compulsory Fields: First “number”
O
F
SE
Y
L
N
O
If a group of message is going to be transmitted
(maximum 10 messages), both numbers must
be completed.
Finish the operation by performing a close action (see
3.7)
Capítulo / Chapter 6
Página / Page 82 de / of 157
If all data are correct, the SVC AFTN message is always sent.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.8
Icon [ARCHIVE] AFTN Messages Retrieval
This icon allows retrieving all sent and received AFTN messages. When clicking on the [ARCHIVE]
icon, the AFTN Retrieve Window is displayed.
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.
Y
P
O
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:
RY
C
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Error Messages Area
SE
Y
L
N
O
Edition
Area
Command Area
Figure 6.2.8.1-1. AFTN Retrieve Window
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 83 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.8.1.1
EDITION AREA
Following table lists the fields and their corresponding description:
Table 6.2.8.1.1-1. AFTN Retrieve Window. Edition Area
Field
Description
Valid Data
Date
Sending or reception date of the AFTN messages to be retrieved.
AAMMDD, where
AA = year (00 to 99)
MM = month (01 to 12)
DD = day (01 to 31)
Circuit Id
Circuit Indicator. Line through which the AFTN messages to be
retrieved where sent or received.
XXX.- Line 1 Sending
XXX.- Line 2 Sending
XXX.- Line 1 Reception
XXX.- Line 2 Reception
XXX: These values are defined in
adaptation.
C
Y
P
O
Y
L
N
Tx Time Interval
AFTN message sending or reception time.
From
Temporal filter starting time for AFTN message retrieval.
To
Temporal filter final time for AFTN message retrieval.
Sort Number
Sequence number of the message(s) to be retrieved.
From
Sequence number filter starting number.
(000-999)
To
Sequence number filter starting number.
(000-999)
Prior
AFTN priority indicator.
Follow ICAO rules
Destiny
Transmission Address
8 characters sequence
Originator
Originator Indicator
8 characters sequence
Free Search
Text
RY
O
HHMM (00 to 23 and 00 to 59)
SE
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
6.2.8.1.2 COMMAND AREA R
O
Following table lists the F
different commands included in the AFTN Retrieve Window.
HHMM (00 to 23 and 00 to 59)
Table 6.2.8.1.2-1. AFTN Retrieve Window. Command Area
Icon
Description
OK
Trigger the actions performed in current window.
CANCEL
Close the window. If the actions were not previously validated, they will not be taken into account by the system.
CLEAR
Delete the data displayed on the window.
Capítulo / Chapter 6
Página / Page 84 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.8.1.2.1
ACTION: RETRIEVE MULTIPLE AFTN MESSAGES
ACTION
1.
Click with the LB on the [ARCHIVE] icon.
2.
To display the sent or received AFTN messages:
2.1.
If input parameters are known, enter the data
in the corresponding fields and click on the
[OK] icon.
RESULT
The AFTN Retrieve Window is displayed.
Y
P
O
Y
L
N
If data are erroneous, an error message is displayed.
RY
C
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
O
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:
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 85 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
ACTION
3.1.
4.
By clicking twice on the corresponding
message.
RESULT
The selected message is automatically displayed on the AFTN
Element Window.
Finish the action by clicking with the LB on any of the
following icons:
4.1.
[TRANSMIT] icon
C
Y
P
O
Y
L
N
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.
RY
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
O
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
It displays the error associated to the field where the mouse is focused on.
A list of error messages is provided in Appendix E.
Capítulo / Chapter 6
Página / Page 86 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
RY
C
Y
P
O
SE
Y
L
N
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
I
N
I
6.2.8.3 AFTN Element Window A
R twice, with the mouse LB, on a selected message included in the
This window is displayed by clicking
T
Retrieve Multiple AFTN Window.
R displays the data of the message within the corresponding fields.
O
The AFTN Element Window
F
Figure 6.2.8.2-1. Retrieve Multiple AFTN Window
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 87 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Edition Area
Message
Area
RY
C
Y
P
O
Figure 6.2.8.3-1. AFTN Element Window
Test
Y
L
N
Command
Area
SE
O
O
NA
I
P
R
IM
6.2.8.3.1 EDITION AREA
L
U
E the system displays
It is composed of a set of fields where
the AFTN message header data. The
Pfields
system highlights the erroneousR
fields for modification.
Only
in WHITE and RED (compulsory or
G
P
erroneous) are accessible to the operator.
IN
N
Following table lists for each field included in
I the AFTN Element Window a description with the valid
A
data.
TR
R
O
F
This window has the following areas:
Table 6.2.8.3.1-1. AFTN Element Window. Edition Area
Field
Description
Valid Data
Circuit Id
Circuit Indicator. Line through which the AFTN messages to be
retrieved where sent or received.
XXX.- Line 1 Sending
XXX.- Line 2 Sending
XXX.- Line 1 Reception
XXX.- Line 2 Reception
XXX: These values are defined in
adaptation.
Sort Number
Sequence number of the retrieved message.
(0000 – 9999)
Tx Day Time
AFTN message sending or reception time.
HHMM (00 to 23 and 00 to 59)
Prior
AFTN priority indicator.
Follow ICAO rules
Dest
Transmission Address.
8 characters sequence
Capítulo / Chapter 6
Página / Page 88 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Table 6.2.8.3.1-1. AFTN Element Window. Edition Area
Field
Description
Valid Data
Filling Day Time
Time when the AFTN message was filled in at the Flight Service
Office.
DDHHMM (00 to 31, 00 to 23 and 00
to 59)
Originator
Originator Indicator.
8 characters sequence
Text
Text.
6.2.8.3.2
ERROR MESSAGE AREA
It is where the system displays any error message to warn the operator of the erroneous fields.
6.2.8.3.3
COMMAND AREA
Y
P
O
Y
L
N
It is formed by a set of icons, which are described in following table:
C
Table 6.2.8.3.3-1. AFTN Element Window. Command Area
Icon
TRANSMIT
RY
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Description
SE
O
Transmit a previously transmitted message.
The sending message is the same as the one formerly sent except for:
The “Circuit Id” field that will be the one corresponding to the line through which the message is
sent.
The “Sort Number” field that will be the corresponding one.
If there is an attempt of transmitting a received message (“Circuit Id” field = XXX or YYY), the error “Impossible
Trans Received Msg” will be generated.
RETRANSMIT
Transmit a previously transmitted message.
The sending message is the same as the one formerly sent except for:
The “Sort Number” field that will be the one corresponding and
The “DUPE” key that will be added at the end of the message.
If there is an attempt of transmitting a received message (“Circuit Id” field = XXX or YYY), the error “Impossible
Trans Received Msg” will be generated. In addition, if the line, through which the retransmission is being
attempted, is not available, the error “ERROR: Line is offline” will be generated.
CLOSE
Close the window. If the actions were not previously validated, they will not be taken into account by the
system.
PRINT
Print the message.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 89 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
RY
This window has the following areas:
C
Y
P
O
SE
Y
L
N
O
A
OOLDI messages by a pattern
N
I
It is composed of a set of fields that can be completed in order to filter
P
entered in one o some fields.
R
IM
L
U
Following table lists for each field included
E in the OLDI retrieve
P window.
R
G
P
N
NI
I
A
R
T
R
O
F
6.2.8.4.1
EDITION AREA
Table 6.2.8.4.1-1. OLDI Retrieve Window. Edition Area
Field
Description
Valid Data
DATE
Sending/ reception messages data.
DDMMYY
CTRL CENTER
External control center.
Up to 4 characters.
TX DAY TIME
OLDI message sending or reception time interval.
FROM: HHMM (00 to 23 and 00 to 59)
TO: HHMM (00 to 23 and 00 to 59)
FREE SEARCH
Entered data is a partner for filter by any part of the message.
6.2.8.4.2
ERROR MESSAGE AREA
It is where the system displays any error message to warn the operator of the erroneous fields.
Capítulo / Chapter 6
Página / Page 90 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.8.4.3
COMMAND AREA
It is formed by a set of icons, which are described in following table:
Table 6.2.8.4.3-1. AFTN Element Window. Command Area
Icon
Description
OK
Apply the filtering and displays a retrieve of OLDI messages that fulfil it.
CLOSE
Close the window. If the actions were not previously validated, they will not be taken into account by the
system.
CLEAR
Erase all data entered in every window edition field.
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
SE
Y
L
N
O
Capítulo / Chapter 6
Página / Page 91 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.9
Icon [A.P.] Airport Pressure
This icon triggers the procedures related to QNH. By clicking on the [A.P.] icon, the Airport Pressure
Window is displayed.
Figure 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.
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F AREA
ELEMENT LIST
SE
Y
L
N
O
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.
6.2.9.1.2
EDITION AREA
Only the “Zone” field is editable. Using the keyboard or clicking twice on the corresponding row of the
Element List Area can fill in this field.
Following table describes the different fields included in the Airport Pressure Window.
Capítulo / Chapter 6
Página / Page 92 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Table 6.2.9.1.2-1. Airport Pressure Window. Edition Area
Field
6.2.9.1.3
Description
Zone
Display the previously selected airport. Do not allow entering modifications.
QNH
Display and allow modifications on the QNH.
TRANS LEVEL
Display the Transition Level for the selected zone and allow modifications.
COMMAND AREA
Following table describes the commands included in the window:
Table 6.2.9.1.3-1. Airport Pressure Window. Command Area
Icon/Switch
Y
P
O
Command
View
Display the QNH information of a selected zone (airport).
Modify
Modify the information related to the QNH.
OK
Trigger the actions performed in the Airport Pressure Window.
RY
CLOSE
C
SE
Y
L
N
O
O
NA
I
P
R
IM
L
U
E
P
R
G LEVEL VISUALIZATION
P QNH AND TRANSITION
ACTION:
N
NI
I
A
R
T
R
O
F
Close the Airport Pressure Window. If the actions were not previously validated, they will not be taken into
account by the System.
CLEAR
Delete the information displayed on the Airport Pressure Window.
6.2.9.1.3.1
ACTION
1.
Click with the LB on the [A.P.] icon.
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.
3.
Finish the operation by performing a close action (see
3.7)
RESULT
The Airport Pressure Window is displayed.
Compulsory Fields: Zone
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 93 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.9.1.3.2
ACTION: MODIFY QNH AND TRANSITION LEVEL
ACTION
1.
Click with the LB on the [A.P.] icon.
2.
Enter the name of the required airport in the “Zone”
field.
3.
Click with the LB on the [OK] icon
RESULT
The Airport Pressure Window is displayed.
Y
P
O
Y
L
N
The data presented on the upper list are displayed on the
corresponding fields.
RY
C
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
4.
A
R
5.
T
R
O
Compulsory Fields: Zone,
F QNH and Transition Level.
SE
O
Modify the desired data.
Finish the operation by performing a close action (see
3.7)
6.2.9.1.4
ERROR MESSAGE AREA
It displays the error associated to the field where the mouse is focused on.
A list of error messages is provided in Appendix E.
Capítulo / Chapter 6
Página / Page 94 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.10 Icon [WINDS] Wind Data
Winds data are used to calculate the flight profile trajectory. The current and foreseen wind speeds (if
available) together with the direction values are stored for each defined area and level.
The [WINDS] icon allows performing actions on winds. When clicking on this icon, the Winds Data
Window is displayed.
Figure 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).
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
Figure 6.2.10.1-1. Winds Data Window
6.2.10.1.1 EDITION AREA
Following table lists fields included in the Winds Data Window and a description of those fields with
their valid data.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 95 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Table 6.2.10.1.1-1. Winds Data Window. Edition Area
Field
Description
Valid Data
TO
Display the end of the validation period of the data
presented on the window.
DD/HH:MM (00 to 31, 00 to 23 and 00 to 59)
Zone
Display the identification of geographic areas.
Defined by adaptation
Layer
Relevant levels defined for each geographic area.
Up to eight
Wind Direction
Winds direction in the associated area/level.
In degrees from true north
Speed
Speed of the wind in the associated area/level.
From 0 to 250 kilometres per hour.
6.2.10.1.2 COMMAND AREA
Y
P
O
Following table describes the commands included in the Winds Data Window.
C
Table 6.2.10.1.2-1. Winds Data Window. Command Area
Icon/Switch
View
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
AOF WIND DATA
ACTION: VISUALIZATION
R
T
R
O
F
Description
Display the wind information.
Modify
RY
SE
Y
L
N
O
Modify the wind information.
OK
Trigger the actions performed in current window.
CLOSE
Close the window. If the actions were not previously validates, they will not be taken into account.
6.2.10.1.2.1
ACTION
1.
Click with the LB on the [WINDS] icon.
2.
Enter data in the corresponding fields.
3.
Finish the operation by performing a close action (see
3.7)
Capítulo / Chapter 6
Página / Page 96 de / of 157
RESULT
The Winds Data Window is displayed in view mode ([View] switch
activated).
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.10.1.2.2
ACTION: MODIFY WIND DATA
ACTION
RESULT
1.
Click with the LB on the [WINDS] icon.
The Winds Data Window is displayed in view mode ([View] switch
activated).
2.
Click with the LB on the [Modify] switch with the mouse
LB.
The switch turns to YELLOW.
3.
Modify the desired fields. If wind’s direction is entered, it
is compulsory to introduce the speed and vice versa.
RY
C
Y
P
O
SE
Y
L
N
O
O
NA
I
P
Compulsory Fields: If entering new M
compulsory to enter the corresponding speed
R
I wind direction, it is U
and vice versa.
L
E
P
R
G
P
6.2.10.1.3 ERROR MESSAGE AREA
N
NIwhere the mouse is focused on.
It displays the error associated to the field
I
Ain Appendix E.
A list of error messages is provided
R
T
R
O
F
4.
Finish the operation by performing a close action (see
3.7)
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 97 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.11 Icon [AREAS] Restricted Areas
Restricted Areas are elements, which are created on-line and have two associated characteristics:
Geography: the operator may define up to 3 dimensional areas for the restricted airspace.
Planning: the operator may provide a schedule for the restricted airspace activation or
inhibition.
The Restricted Areas can be created/modified/cancelled from the FDD. Up to 64 restricted areas can
be created in the ATC working area.
A Restricted Area can be a circle or a zone being defined in both cases the minimum and maximum
area.
To create a circle, it is necessary to establish the centre and radius.
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.
Y
P
O
Defining the validity period, operation days and activation hours, may perform the Restricted Area
planning.
Y
L
When the Restricted Area is activated, the FDP distributes the information throughout
the whole
N
C
System and displays a presentation and deletion message when the activation period
ends.
O The FDP
Y
deletes the restricted Areas when the validation periodR
expires.
E
S
A
Within the restricted area it is possible to select/de-select the STCA detection.
O
N
I
P
The Restricted Areas are displayed on the
while they are activated and they are used to warn
Rand APW (Area Proximity Warning)
IMSDDs
about the RAW (Restricted Area Intrusion
Detection Warning)
L
U
alerts which are performed from theE
FDP and SDP, respectively.
P
R
G
P
N
I
The [AREAS] icon allows performing actions on
restricted areas visualization, edition, modification and
N
I
cancellation.
A
R
When clicking on the icon, the Restricted
T Areas Window is displayed.
R
O
F
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
Capítulo / Chapter 6
Página / Page 98 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
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 ELEMENT LIST AREA
This list contains all the existing restricted areas. The restricted areas are automatically included in the
list once they have been created and they are automatically deleted when the validity period is over.
The vertical scroll bar allows the visualization of the restricted areas not in view due to list size.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 99 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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:
RY
C
Y
P
O
Table 6.2.11.1.1-1. Restricted Areas Window. Element List Area
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
6.2.11.1.2 DESCRIPTIONO
AREA
F
Element
Description
SE
Y
L
N
O
AREA ID
Display the restricted area identification.
TYPE
Display the restricted area type.
ACTIVITY
Display the activity type description that is undergone in the restricted area.
STATUS
Display the restricted area status. It depends on the restricted area activation periods.
VALIDITY
Display the restricted area validity period.
CLASS
Display the class of the Restricted Area. It could be Active (A), Inactive (I), or Scheduled (S)
It is the area located under the restricted area list. It is where the description of a restricted area is
displayed.
Figure 6.2.11.1.2-1. Restricted Areas Window. Description Area
This area is composed of the following items:
Capítulo / Chapter 6
Página / Page 100 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Table 6.2.11.1.2-1. Restricted Areas Window. Description Area
Item/Switch
Description
TOTAL
Display the number of restricted areas.
AREA ID
Display the restricted area identification (view mode).
Enter the restricted area name (creation/retrieval mode).
TYPE
Type of restricted area (dangerous, forbidden, etc.)
ACTIVITY
Description of the activity type that is performed in the restricted area (military operation, etc)
DESCRIPTION
Brief description of the restricted area.
CLASS
Describe the assigned class to the restricted area.
Stca Alert Display
Switch that allows activate/inhibit the STCA alert function within the restricted area.
6.2.11.1.3 ACTIVATION/VALIDITY AREA
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
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
Validity Period
FROM
Valid Data
Switch. When it is activated (YELLOW) the “From” and “Until” fields are accessible. It marks the relation
with the validity period for the restricted area.
Define the starting date for the validity period of the
restricted area.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
YYMMDD, where
YY = year (00 to 99)
MM = month (01 to 12)
DD = day (01 to 31)
Capítulo / Chapter 6
Página / Page 101 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Table 6.2.11.1.3-1. Restricted Areas Window. Activation/Validity Area
Field/Switch
UNTIL
Description
Valid Data
Define the ending date for the validity period of the
restricted area.
Enter Activity Range
YYMMDD, where
YY = year (00 to 99)
MM = month (01 to 12)
DD = day (01 to 31)
Legend that indicates that the fields are used to introduce the activity period of the area or dates when
the area is active.
Daily
Select a daily activation mode for the restricted area.
The switch colour code indicates the selection status.
YELLOW = Selected
Background = Not selected
FROM
Define the starting time of the day for the activation
period of the restricted area.
HHMM, where
HH = hour (00 to 23)
MM = minutes (00 to 59)
TO
Define the ending time of the day for the activation
period of the restricted area.
HHMM, where
HH = hour (00 to 23)
MM = minutes (00 to 59)
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
Week
Select a weekly activation mode for the restricted
area.
The switch colour code indicates the selection status.
YELLOW = Selected
Background = Not selected
MTWTFSS
Select the day of the week when the restricted area
is activated (from Monday to Sunday).
The switch colour code indicates the selection status.
YELLOW = Selected
Background = Not selected
FROM
Define the starting time of the selected days of week,
for the activation period of the restricted area.
HHMM, where
HH = hour (00 to 23)
MM = minutes (00 to 59)
TO
Define the ending time of the selected days of week,
for the activation period of the restricted area.
HHMM, where
HH = hour (00 to 23)
MM = minutes (00 to 59)
Dates On
Select the activation mode by events.
The 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)
Capítulo / Chapter 6
Página / Page 102 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.11.1.4 LAYOUT AREA
This area is used to define the 3-D shape of the restricted area. The operator enters the vertical limits
(upper and lower) and the type of shape for the restricted area (circle or polygon).
When creating a circle, the centre point and the radius must be entered. When zones are being
created, a set of points must be entered (up to 25).
C
Y
P
O
Figure 6.2.11.1.4-1. Restricted Areas Window. Layout Area
RY
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
Table 6.2.11.1.4-1. Restricted Areas Window. Layout Area
Field/Switch
VERTICAL LIMITS
Description
Valid Data
Legend that indicates that the fields are related to the vertical limits definition for the restricted areas.
UPPER
Upper vertical limit of the restricted area.
From lower vertical limit to 999.
LOWER
Lower vertical limit of the restricted area.
From 000 to upper vertical limit.
Circle
Select the shape of the restricted area as a circle.
The switch colour code indicates the selection status.
YELLOW = Selected
Background = Not selected
CENTER
Circle centre point.
A fix point known by the system or geodesic coordinates of a
point within the system working area.
RADIUS
Circle radius.
Up to three numeric characters.
The entered value is considered as Km.
Polygon
Select the shape of the restricted area as a
polygon.
The switch colour code indicates the selection status.
YELLOW = Selected
Background = Not selected
Points
Geodesic coordinates (latitude / longitude) of each
point forming the polygon or the name of a fix if it
is known by the system.
GGGMMSSLggmmssl where:
GGG:
from 000 to 180
MM:
from 00 to 59
from 00 to 59
SS:
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 103 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Table 6.2.11.1.4-1. Restricted Areas Window. Layout Area
Field/Switch
Description
Valid Data
L:
gg:
mm:
ss:
l:
N or S
from 00 to 90
from 00 to 59
from 00 to 59
E or W
or
Up to 7 alphanumeric characters
6.2.11.1.5 COMMAND AREA
C
Y
P
O
Figure 6.2.11.1.5-1. Restricted Areas Window. Command Area
RY
Commands included in this area are described in following table:
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Table 6.2.11.1.5-1. Restricted Areas Window. Command Area
Icon/Switch
SE
Y
L
N
O
Command
View
Display the data of the selected restricted area.
Create
Create a new restricted area.
Modify
Modify a restricted area.
Cancel
Delete a restricted area.
OK
Trigger the actions performed in current window.
LIST SUMMARY
Request the existing restricted area list.
CLOSE
Close the window. If the actions were not previously validated, they will not be taken into account by the
system.
CLEAR
Delete the data displayed on the window fields.
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.
Capítulo / Chapter 6
Página / Page 104 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.11.1.5.2
ACTION: CREATE RESTRICTED AREA
ACTION
1.
RESULT
Once the Restricted Areas Window is displayed, click on
the [Create] switch with the LB.
The switch becomes YELLOW and the accessible fields are
displayed in WHITE background.
RY
2.
Input data in the corresponding fields (description,
validity, and layout).
3.
Finish the operation by performing a close action (see
3.7)
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
Compulsory Fields: Area ID, Type, Activity, Description, Validity (From and Until), Range of Dates,
Vertical Limits and Lateral Bounds (Circle or Polygon).
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 105 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
2.
Modify the required fields.
3.
Finish the operation by performing a close action (see 3.7)
RESULT
The switch changes to YELLOW.
RY
C
Y
P
O
SE
Y
L
N
O
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
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
ACTION: CANCEL RESTRICTED AREA
ACTION
1.
Once the Restricted Areas Window is displayed, click with the
LB on the [Cancel] switch, at the bottom of the "Restricted
Areas" window, with the LB.
2.
Finish the operation by performing a close action (see 3.7)
RESULT
The switch changes to YELLOW.
Compulsory Fields: Area ID.
6.2.11.1.6 ERROR MESSAGE AREA
It displays the error associated to the field where the mouse is focused on.
A list of error messages is provided in Appendix E.
Capítulo / Chapter 6
Página / Page 106 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.12 Icon [FLOW] Air Traffic Flow
This functionality allows analyzing in advance, the future air traffic flow in order to warn the positions
on the future air traffic congestions and complex air traffic situations.
By means of this icon all actions related to the air traffic flow are performed. By clicking on the [FLOW]
icon, a menu is displayed to select the type of flight plans to be analyzed (FPL).
Figure 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.
Y
P
O
Y
L
N
This functionality allows displaying the traffic volume of adjacent route sectors and displaying the
traffic volume of adjacent route sectors in adjacent FIRs.
RY
C
O
The operator receives a warning if the current or future traffic flow of an element exceeds a defined
limit for that element.
SE
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
6.2.12.1 Flow FP Window
R
T
The Flow FP Window allows the operator to restrict the query to flight plans database by a set of
Rflow element identification (Aerodrome/Fix/Sector) and FP time).
defined parameters (traffic
O
The layout of the F
Flow FP Window is the same for any of the traffic flow elements previously selected.
Figure 6.2.12-2. FPs Traffic Flow Options
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.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 107 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Filters Edition Area
Command
Area
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
Figure 6.2.12.1-1. Flow FP Window
Capítulo / Chapter 6
Página / Page 108 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.12.1.1 FILTERS EDITION AREA
Following table lists for each field included in the Flow FP Window, a description with their valid data.
Table 6.2.12.1.1-1. Flow FP Window. Filters Edition Area
Field/Switch
Description
Valid Data
Aerodrome / Fix / Sector
Airport identification / Fix point identification / Sector
identification.
Known by the System
FROM
Lower temporal limit (time) for filtering the FPLs (FROM)
HHMM, where
HH = hour (00 to 23)
MM = minutes (00 to 59)
UNTIL
Upper temporal limit (time) for filtering the FPLs (TO)
HHMM, where
HH = hour (00 to 23)
MM = minutes (00 to 59)
6.2.12.1.2 COMMAND AREA
RY
C
Y
P
O
SE
Y
L
N
O
Following table shows the different commands included in the Flow FP Window.
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Table 6.2.12.1.2-1. Flow FP Window. Command Area
Icon
Command
F.LIST
Display the FPs Traffic Flow List.
C. CHART
Displays the FPs Congestion Chart
CLOSE
Close the Flow FP Window.
CLEAR
Delete the information displayed on the Flow FP Window.
6.2.12.1.2.1
ACTION: FPLS FLOW
ACTION
1.
Click with the LB on the [FLOW] icon.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
RESULT
A menu is displayed to select the type of flow element.
Capítulo / Chapter 6
Página / Page 109 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
RY
4.
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
Finish the action according to following icons:
Capítulo / Chapter 6
Página / Page 110 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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)
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
The layout of the FPs Traffic Flow List depends on the type of flow
element selected (step 2). So that, the information displayed in the
list is the following:
If Aerodrome,
The list displays the FPLs departing or arriving from/to the selected
aerodrome.
If Fix,
The list displays the FPLs that include the fix in their route. The list
distinguishes flights plan going to or from the fix.
If sector,
The list displays the FPLs (without distinction between arrivals and
departures) whose route fix belong to the sector.
From this list, the operator may click on the [CANCEL] icon, and all
windows are closed.
4.2.
Click twice on any line of the FPs Traffic Flow
List.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 111 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
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.
Capítulo / Chapter 6
Página / Page 112 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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:
List by Aerodrome
It includes the FPs arriving or departing to/from the selected aerodrome with the
ETA/ETD within the selected range. The list is ordered by ETD (departures) and ETA
(arrivals).
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
Figure 6.2.12.2-1. FP Found for the given filter
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 113 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Table 6.2.12.2-1. FPs Traffic Flow List. Aerodrome
Element
ARRIVALS
Arrival FPs
DEPARTURES
Departure FPs
ORIGIN
Departure Aerodrome
CALLSIGN
Aircraft Identification
EOBD
Estimated Off-Block Date
EOBT
Estimated Off-Block Time
TYPE
Aircraft Type
ETA/ETD
Estimated Time of Arrival / Estimated Time of Departure
DESTINY
Destination Aerodrome
CALLSIGN
Aircraft Identification
EOBD
Estimated Off-Block Date
EOBT
Estimated Off-Block Time
RY
C
Y
P
O
SE
Y
L
N
O
O
NA
I
P
M or departing whichRcontain the selected fix point in their
It includes the FPs either arriving
I
L
routes. ETO orders this list.
U
E
P
G
PR
N
NI
I
A
R
T
R
O
F
TYPE
Description
Aircraft Type
List by Fix
Figure 6.2.12.2-2. FP Found for the given filter
Capítulo / Chapter 6
Página / Page 114 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Table 6.2.12.2-2. FPs Traffic Flow List. Fix
Element
Description
ARRIVALS
Arrival FPs
DEPARTURES
Departure FPs
ORIGIN
Departure Aerodrome
DESTINY
Destination Aerodrome
CALLSIGN
Aircraft Identification
EOBD
Estimated Off-Block Date
EOBT
Estimated Off-Block Time
TYPE
Aircraft Type
LEVEL
Flight Level
ETO
Estimated Time Over a significant point
ORIGIN
Departure Aerodrome
DESTINY
Destination Aerodrome
RY
C
Y
P
O
SE
Y
L
N
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
I
N
I
List by Sector
A
It does not includeR
a distinction between arrivals and departures. Displayed flights are
those whose fixT
points belong to the sector. It is ordered by sector entry time.
R
FO
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
CALLSIGN
Aircraft Identification
EOBD
Estimated Off-Block Date
EOBT
Estimated Off-Block Time
TYPE
Aircraft Type
LEVEL
Flight Level
Capítulo / Chapter 6
Página / Page 115 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
Figure 6.2.12.2-3. FP Found for the given filter
Table 6.2.12.2-3. FPs Traffic Flow List. Sector
Element
Capítulo / Chapter 6
Página / Page 116 de / of 157
Description
ORIGIN
Departure Aerodrome
DESTINY
Destination Aerodrome
CALLSIGN
Aircraft Identification
EOBD
Estimated Off-Block Date
EOBT
Estimated Off-Block Time
TYPE
Aircraft Type
LEVEL
Flight Level
ROUTE
Flight Plan Route
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.12.2.1 COMMAND AREA
Table 6.2.12.2.1-1. FPs Traffic Flow List. Command Area
Icon
Description
CLOSE
Close the FPs Traffic Flow List
PRINT
Print the FPs Traffic Flow List
If double click is performed on an entry of List flow, user can access to FP Operation Window.
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
Figure 6.2.12.2.1-1. FP Operation Window from Flow List
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 117 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
Tittle
Edition Area
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Graphical Area
SE
Figure 6.2.12.3-1. FPs Traffic Congestion List Graphic
Y
L
N
O
Command Area
Table 6.2.12.3-1. FPs Traffic Congestion List Graphic. Edition
Area
Element
Description
From
Starting time for filter application.
To
Ending time for filter application.
Table 6.2.12.3-2. FPs Traffic Congestion List Graphic. Graphical Area
Element
Description
Sector/ Fixpoint/ Aerodrome
Overpasses
Number of flights (different or repetitive), which passed within the predefined interval by the sector/
fix/ aerodrome.
Time
Application time in the graphic.
Capítulo / Chapter 6
Página / Page 118 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Table 6.2.12.3-3. FPs Traffic Congestion List Graphic. Command Area
Element
Description
Interval length
Time interval longitude to perform the graphic.
CLOSE
Close the FPs Traffic Congestion List.
PRINT
Not applicable.
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
SE
Y
L
N
O
Capítulo / Chapter 6
Página / Page 119 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.13 Icon [METEO MSG] Meteorological Data
Following meteorological messages are received from the AFTN and AIS and are automatically
processed by the System:
METAR;
SPECI;
TAF;
SIGMET;
ATIS;
AIRMET;
These messages are stored in the FDPS disc.
Y
P
O
The FIR aerodrome of these messages is extracted and used as key for a posterior access from the
controller positions.
Y
L
The validity period of these messages is taken into account for automatic deletion of messages
which
N
C
are expired. The operator receives a warning when the validity period of the meteorological
data
has
O
Y
expired.
E
R
S
A
The QNH value for specific zones, defined in adaptation, is extracted from the METAR and SPECI
O
N
I
messages.
P
R have been defined:
IbeMentered once theUusers
Following meteorological information can
L
E
P
R
G
P
Meteorological Reports-Aviation
RoutineN
Weather Report (METAR);
I (SPECI);
NReport
Special Meteorological Aeronautical
I
A
Terminal Area Forecast (TAF).
R
T
R
This icon allows performing
O
F 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
Capítulo / Chapter 6
Página / Page 120 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
Y
P
O
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.
Y
L
N
C
OReport is a format for
Y
METAR: or Meteorological Reports-Aviation
Routine Weather
E
R
Spredominantly used by pilots in
reporting weather information. A METAR
weather report is
A
O
N
fulfilment of a part of a pre-flight
briefing, and by meteorologists, who use
I to assistweather
aggregated METAR information
in weather P
forecasting.
M
R
I
L
U or permanent weather observation
METAR reports E
typically come from airports
P
stations. Reports
generated once an hour; however, if conditions
PR aretheytypically
change significantly,
may beG
in special reports called SPECI's. Some
N updatedairport
I
reports are encoded by an automated
station located at airports,
N Some locationsweather
military bases and other Isites.
still use-augmented observations,
which are recorded byA
digital sensors and encoded via software, but are reviewed
Robservers
by certified weather
or forecasters prior to being transmitted. Trained
T
observers or R
forecasters, who manually observe and encode their observations prior
to their being
FO 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.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 121 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
RY
C
Y
P
O
SE
Y
L
N
O
O
NA
I
P
R
IM
L
U
E
P
R
G
6.2.13.1.1 SELECTED MESSAGE
P
N
The window title depends on the selected message
NI when clicking on the [METEO MSG] icon.
I
A
6.2.13.1.2 AIRPORT SELECTION R
By clicking on the icon situated atT
the top right corner of the Meteorological Information Window, a
menu is displayed to select theR
airport from which the meteorological information is obtained.
O
F
6.2.13.1.3 EDITION AREA
Figure 6.2.13.1-1. Meteorological Information Window
It is formed by three fields, which are described in following table:
Table 6.2.13.1.3-1. Meteorological Information Window. Edition Area
Field
Capítulo / Chapter 6
Página / Page 122 de / of 157
Description
From
Define the starting date
DDHHMM (DD – Day, HH – Hour, MM – Minutes)
To
Define the ending date
DDHHMM (DD – Day, HH – Hour, MM – Minutes)
Text
Free Text
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
The vertical and horizontal scroll bars allow the visualization of the text not in view due to window size.
6.2.13.1.4 COMMAND AREA
Following table shows the different commands included in the Meteorological Information Window.
Table 6.2.13.1.4-1. Meteorological Information Window. Command Area
Icon/Switch
6.2.13.1.4.1
Command
Edit
Allow the data input within the corresponding fields.
OK
Send the edited message, but the window remains displayed.
CLOSE
Close the Meteorological Information Window.
CLEAR
Delete the information displayed in the Meteorological Information Window.
PRINT
Print the data included in the Meteorological Information Window.
C
Y
P
O
ACTION: EDIT METEOROLOGICAL PAGE
ACTION
RY
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
1.
Click with the LB on the [METEO MSG] icon.
2.
Select one of the options from the menu.
3.
Enter data in the “Edition” field. The airport is selected
by clicking on the icon situated in the top right of the
window.
4.
Finish the operation by performing a close action (see
3.7)
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
SE
Y
L
N
O
RESULT
A pull-down menu for selecting the desired meteorological page is
displayed.
The Meteorological Information Window is displayed.
Capítulo / Chapter 6
Página / Page 123 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.14 [NOTAM] Icon
This icon allows performing different actions related to the NOTAM information.
The FDPS manages the NOTAMs received from the AFTN or those entered manually from the
positions.
The NOTAM messages are sent to the “Q” Queue for operator validation. If the operator validates the
NOTAM message, it is included into the NOTAMs database.
When clicking on the icon, the NOTAM Operation/Retrieval Window is displayed.
Figure 6.2.14-1. [NOTAM] Icon
6.2.14.1 NOTAM Operation/Retrieval Window
Y
P
O
Y
L
N
The System maintains a NOTAMs database. The FDD operator can perform the following functions on
that database:
Query (display) a NOTAM;
RY
C
SE
O
O
NA
I
P
Cancel a NOTAM;
R
IM
L
U
Print a NOTAM;
E
P
R
Retrieve several NOTAMs byP
means of searching criteria:
G
N
NOTAM identifier
NI
I
Validity period starting dateA
(campo B)
R
Validity period ending
Tdate (campo C)
R(QCODE).
NOTAM category
O
F from the database automatically when the validity period has expired.
Obsolete NOTAM are deleted
Create a new NOTAM;
Modify a NOTAM;
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.
Capítulo / Chapter 6
Página / Page 124 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Edition Area
Command
Area
Y
P
O
Y
L
N
Figure 6.2.14.1-1. NOTAM Operation/Retrieval Window
6.2.14.2 Edition Area
RY
C
SE
O
Following table describes the fields included in the NOTAM Operation/Retrieval Window and the
correct values:
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Table 6.2.14.2-1. NOTAM Operation/Retrieval Window. Edition Area
Field
ID
Field A)
Field F)
Description
Field G)
Valid Data
NOTAM identification type
A or B plus
4 numeric characters plus
“/” plus
YY, where YY = year (00 to 99)
Airport
ICAO airport indicator.
4 alphabetic characters.
Level
Hundreds of feet: Fxxx where xxx 000 to 999
Tens of meters: Sxxxx where xxx 0000 to 9999
Level
Hundreds of feet: Fxxx where xxx 000 to 999
Tens of meters: Sxxxx where xxx 0000 to 9999
Field Q)
FIR
4 characters (ICAO indicator)
CODE
Two characters.
STAT
Two characters. NOTAM code meaning.
REMAINDER
Following string:
“/”
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 125 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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
RY
C
Y
P
O
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
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Field B) From
O
YYMMDDHHMM, where
YY = year (00 to 99)
MM = month (01 to 12)
DD = day (01 to 31)
HH = hour (00 to 23)
MM = minutes (00 to 59)
Field C) Until
YYMMDDHHMM, where
YY = year (00 to 99)
MM = month (01 to 12)
DD = day (01 to 31)
HH = hour (00 to 23)
MM = minutes (00 to 59)
Field D) Schedule
D/D/D/ HHMM/HHMM, where
D = day (1 to 31)
HH = hour (00 to 23)
MM = minutes (00 to 59)
Field E) TEXT
SE
Y
L
N
Free text
Capítulo / Chapter 6
Página / Page 126 de / of 157
Up to 2100 characters.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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
View
Display the NOTAM data.
Creation
Create a new NOTAM.
Modify
Modify an existing NOTAM.
Cancel
Delete an existing NOTAM.
Retrieve Multiple
Display all NOTAM included in the database.
PRINT
Print the single NOTAMs.
OK
Trigger all input data.
CLOSE
Close the NOTAM Operation/Retrieval Window.
CLEAR
Delete the data displayed on the NOTAM Operation/Retrieval Window.
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
6.2.14.3.1 ACTION: COMMON ACTION TO NOTAM PROCEDURES
ACTION
1.
RESULT
Click with the LB on the [NOTAM] icon.
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.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 127 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.14.3.2 ACTION: CREATE A NEW NOTAM
ACTION
1.
Click with the LB on the [Crea.] switch
2.
Enter the data.
3.
Finish the operation by performing a close action (see 3.7)
RESULT
The switch becomes YELLOW. All fields are accessible to input
data.
RY
Compulsory Fields: ID, FIR, Code, Stat, From and Until.
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Capítulo / Chapter 6
Página / Page 128 de / of 157
SE
Y
L
N
O
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.14.3.3 ACTION: MODIFY NOTAM
ACTION
1.
Perform the visualize NOTAM action (see 6.2.14.3.1).
2.
Click with the LB on the [Mod.] switch.
3.
4.
RESULT
The switch becomes YELLOW. All fields are accessible.
Modify the required fields. Some of them do not allow
to be changed. Some others are mandatory.
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
Finish the operation by performing a close action (see
3.7)
Compulsory Fields: ID but only if the NOTAM visualization action was not previously performed.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 129 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.14.3.4 ACTION: CANCEL NOTAM
ACTION
1.
Perform the visualize NOTAM action (see 6.2.14.3.1).
2.
Click with the LB on the [Can.] switch.
RESULT
The switch becomes YELLOW. All fields related to the action are
accessible.
Y
P
O
Y
L
N
C
O
Y
E
R
Compulsory Fields: ID but only if the NOTAM visualization action was not previously performed.
S
A
O
N
I
P
M
R
I
L
U
E
P
G
PR
N
NI
I
A
R
T
R
O
F
3.
Finish the operation by performing a close action (see 3.7)
Capítulo / Chapter 6
Página / Page 130 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.14.3.5 ACTION: RETRIEVE MULTIPLE NOTAM
ACTION
RESULT
1.
Perform the visualize NOTAM action (see 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.
RY
C
Y
P
O
SE
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
4.
A
R
Compulsory Fields: None.
T
RArea
6.2.14.4 Error Message
O
It displays the error
Fassociated to the field where the mouse is focused on.
Y
L
N
O
Finish the operation by performing a close action (see 3.7)
A list of error messages is provided in Appendix E
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 131 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.15 Icon [T. Flow] Traffic Flow
This icon allows performing all actions related to the traffic flow.
When clicking on it, a menu is displayed as shown in following figure:
Figure 6.2.15-1. [T. Flow] icon
This menu presents the following options:
Y
P
O
(FP Act.) – When clicking on this option, the FP Flow Actions Window is displayed.
Y
L
(FPs/Slot Ret) – When clicking on this option, a pull-down
submenu is displayed
to select
N
C
the FP or Slots retrieval filters. The displayed options are:
O
Y
E
R
(FPs) Displays the Retrieve FP’s Flow Window.
S
A
O
N
(Slots) Displays the Retrieve Slots
I Flow Window. P
M
R
I
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
(Slot Act.) – When clicking on this option, the Flow Restrictions Window is displayed
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.
Capítulo / Chapter 6
Página / Page 132 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Command Area
Edition Area
Figure 6.2.15.1-1. FP Flow Actions Window
6.2.15.1.1 EDITION AREA
This area includes fields, which are described in following table:
Y
P
O
Y
L
N
Table 6.2.15.1.1-1. FP Flow Actions Window. Edition Area
Field
F.ELEMENT
Fix point
N
I
LIM
CALLSIGN
Description
Aircraft identification
DEPARTURE
EOBD
Y
R
A
C
Departure Aerodrome
RE
P
R
O
F
SLOT START
OVF. TIME
FP 1
FP2
FP 2
G
N
I
PU
O
Estimated Off-Block Date
N
I
RA
EOBT
DEST
FP1
O
P
R
SE
Estimated Off-Block Time
T
ALLOC. TIME
Destination Aerodrome
Slot starting time (not editable)
Time when the slot is overflown (not editable)
FP allocation time. If the value is not introduced, it is automatically filled in.
6.2.15.1.2 COMMAND AREA
The commands included in this area are described in following table:
Table 6.2.15.1.2-1. FP Flow Actions Window. Command Area
Icon/Switch
Command
Allocate
Allocate a FP (passive) to an element (fix)
Exchange
Exchange between FPs (FP1-FP2)
Release
Delete the FP
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 133 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Table 6.2.15.1.2-1. FP Flow Actions Window. Command Area
Icon/Switch
Command
OK
Trigger the actions performed in current window
CLOSE
Close the window. If the actions were previously validated, they will not be taken into account by the system.
CLEAR
Delete the data displayed on the window fields.
6.2.15.1.2.1
ACTION: ALLOCATE FP TO AN ELEMENT (FIX POINT)
ACTION
RESULT
1.
A menu is displayed.
Click with the LB on the [T.Flow] icon.
RY
2.
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Select the [FP Act.] option.
SE
Y
L
N
O
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).
Capítulo / Chapter 6
Página / Page 134 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.15.1.2.2
ACTION: EXCHANGE THE FP DISTRIBUTION
ACTION
RESULT
1.
Click with LB on the [T.Flow] icon.
A menu is displayed.
2.
Select the [FP Act.] option.
The FP Flow Actions Window is displayed with the editing fields
accessible.
The [Allocate] switch is activated.
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
3.
Input the data in the correspondent fields.
4.
Click with the LB on the [Exchange] switch.
5.
Input the data in the second FP correspondent fields
6.
The operative is ended with an ending action procedure
(3.7).
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
SE
Y
L
N
O
The FP 2 correspondent fields are activated (turn WHITE).
Capítulo / Chapter 6
Página / Page 135 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.15.1.2.3
ACTION: CANCEL AN FP DISTRIBUTION
ACTION
RESULT
1.
Click with the LB on the [T.Flow] icon.
A menu is displayed.
2.
Select the [FP Act.] option.
The FP Flow Actions Window is displayed with the edition fields
accessible.
The [Allocate] switch is activated.
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
4.
I
A
R
5.
T
R
O
6.2.15.2 Flow Restrictions
F Window
3.
Input data in the correspondent fields.
SE
Y
L
N
O
Click with the LB on the [Release] switch.
The operative is ended with an ending action procedure
3.7).
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).
Capítulo / Chapter 6
Página / Page 136 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Edition
Area
Command Area
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 EDITION AREA
RY
C
Y
P
O
This area is formed by fields, which are described in following table:
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
Table 6.2.15.2.1-1. Flow Restrictions Window. Edition Area
Field
Description
F.ELEMENT
Fix Point
FROM
Slot starting time (fix)
HHMM (HH – hour, MM – minutes)
TO
Slot ending time (element-fix)
HHMM (HH – hour, MM – minutes)
RANGE
2 numeric characters (FPs per hour)
1, 2, 3
Number of slots by element that can be created.
6.2.15.2.2 COMMAND AREA
The commands included in this area are described in following table:
Table 6.2.15.2.2-1. Flow Restrictions Window. Command Area
Icon/Switch
Command
FP Act.
Display the FP Flow Actions Window.
Ret. FP’s
Display the Retrieve FP’s Flow Window.
Ret. Slots
Display the Retrieve FP’s Flow Window.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 137 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Table 6.2.15.2.2-1. Flow Restrictions Window. Command Area
Icon/Switch
Command
View
Display the flow restriction data for the selected flow element (fix).
Create
Define the flow restrictions for a new flow element.
Modify
Modify the flow restrictions for the retrieved flow element.
Cancel
Delete the flow restrictions for the retrieved flow element.
OK
Trigger all actions performed in current window.
CLOSE
Close the window. If the actions were not previously validated, they will not be taken into account by the system.
CLEAR
Delete the data displayed on the window fields.
6.2.15.2.2.1
ACTION: SLOT VISUALIZATION
C
Y
P
O
ACTION
RESULT
1. Click with the LB on the [T.Flow] icon.
A menu is displayed.
2. Select the (Slot Act.) option.
The Flow Restrictions Window is displayed.
RY
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
3. Input data in the “F. Element” field.
4. The operative is ended by an ending action procedure
(3.7).
Capítulo / Chapter 6
Página / Page 138 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.15.2.2.2
ACTION: SLOT CREATION
ACTION
RESULT
1. Click with the LB on the [T.Flow] icon.
A menu is displayed.
2. Select the (Slot Act.) option.
The Flow Restrictions Window is displayed.
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
3. Click with the LB on the [Create] switch.
SE
Y
L
N
O
4. Input the data in the correspondent fields.
5. The operative is ended by an ending action procedure.
(3.7).
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 139 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.15.2.2.3
ACTION: SLOTS MODIFYING
ACTION
RESULT
1. Click with the LB on the [T.Flow] icon.
A menu is displayed.
2. Select the (Slot Act.) option.
The Flow Restrictions Window is displayed.
RY
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
3. Execute the visualization action for the element (see point
6.2.15.2.2.1).
C
Y
P
O
SE
Y
L
N
O
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).
Capítulo / Chapter 6
Página / Page 140 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.15.2.2.4
ACTION: CANCEL SLOTS
ACTION
RESULT
1.
Click with the LB on the [T.Flow] icon.
A menu is displayed.
2.
Select the (Slot Act.) option.
The Flow Restrictions window is displayed.
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
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).
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
SE
Y
L
N
O
Capítulo / Chapter 6
Página / Page 141 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
Edition
Area
RY
C
Y
P
O
SE
Y
L
N
O
O
NA
I
Command
P
M
Area
R
I
L
U
E
P
R
G
P
N
NI
I
A
Retrieved FP List
R
T
R
O
F
The Retrieve FP’s Flow Window consists of a form including fields to be filled in by the operator
Figure 6.2.15.3-1. Retrieve FP’s Flow Window
(edition area), a command area at the bottom of the window, and a list of retrieved FPs.
6.2.15.3.1 EDITION AREA
This area only includes the “F_ELEMENT” (fix) field. This field is the filter to retrieve the FPs overflying
the selected flow element (fix).
6.2.15.3.2 COMMAND AREA
The commands included in this area are described in following table:
Capítulo / Chapter 6
Página / Page 142 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Table 6.2.15.3.2-1. Retrieve FP’s Flow Window. Command Area
Icon/Switch
Command
Alloc
Retrieve and display all FPs allocated to the flow element (fix).
Not Alloc
Retrieve and display all FPs, which are not allocated to the flow element (fix).
OK
Trigger all actions performed in current window.
CLOSE
Close the window. If the actions were not previously validated, they will not be taken into account by the system.
CLEAR
Delete the data displayed on the window fields.
6.2.15.3.3 RETRIEVED FPS LIST
This list presents all FPs (allocated or not allocated, depending on the selection) that overflown the
selected element.
The data included in the list are the following ones:
ACID – Aircraft identification
DEP – Departure aerodrome
EOBT – Estimated off-block time
RY
C
Y
P
O
SE
Y
L
N
O
A
O when the previous selection was
N
I
P
ADT – Actual Departure Time. This field is not displayed
R
IM
“Not Allocated”.
L
U
Estarting time. This field
P is not displayed when the previous selection
SLOT START – Slot
R
G
was “Not Allocated”.
P
N
SLOT END – Slot final time. ThisIfield is not displayed when the previous selection was “Not
N
I
Allocated”.
A
R
6.2.15.3.3.1
ACTION: FPS
TDISTRIBUTION MULTIPLE RECOVERY
R
O
F
ACTION
RESULT
1.
A menu is displayed.
Select the (Retrieve) option.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 143 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
2.
Select the (FP) option.
3.
Input the selection (element) values.
4.
Click with the LB on the [OK] icon.
The Retrieve FP’s Flow Window is displayed.
Y
P
O
The Retrieved FPs List is displayed including the distributed Flight
Plans for the selected element.
RY
C
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
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.
Capítulo / Chapter 6
Página / Page 144 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
This window allows the retrieval of the defined slots for a flow element.
Edition Area
RY
C
Y
P
O
Y
L
N
OCommand
Area
E
S
A
O
N
I
P
R
IM
L
U
E
P
R
G
P
N
Retrieved Slots List
NI
I
A
R
T
RWindow consists of a form including fields to be filled in by the operator
The Retrieve Slots Flow
O
(edition area), a command
F area at the bottom of the window, and a list of retrieved Slots.
Figure 6.2.15.4-1. Retrieve Slots Flow Window
6.2.15.4.1 EDITION AREA
This area only includes the “F_ELEMENT” (fix) field. This field is the filter to retrieve the Slots defined
for the flow element (fix).
When clicking on the [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.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 145 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
I
6.2.15.4.2 COMMAND AREA
N
I
The commands included in this area are described in following table:
A
R
T
R
O
F
SE
Y
L
N
O
Figure 6.2.15.4.1-1. Rest. Slot Frame Window. Elements Window
Table 6.2.15.4.2-1. Retrieve Slots Flow Window. Command Area
Icon/Switch
Command
Alloc
Display all Slots allocated to the fix.
Not Alloc
Display all Slots not allocated to the fix.
OK
Trigger all actions performed in current window.
CLOSE
Close the window. If the actions were not previously validated, they will not be taken into account by the System.
CLEAR
Delete the data displayed on the window fields.
Capítulo / Chapter 6
Página / Page 146 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.15.4.3 RETRIEVED SLOTS LIST
This list presents all Slots (allocated or not allocated, depending on the selection) that overflow the
selected element.
The data included in the list are the following ones:
Slot START Time – Slot starting time
Slot END Time – Slot final time
6.2.15.4.3.1
ACTION: RETRIEVE MULTIPLE SLOTS DISTRIBUTION
ACTION
1.
2.
Click with the LB on the [T.Flow] icon.
RESULT
A menu is displayed.
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Select the (Retrieve) option.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
A submenu is displayed.
SE
Y
L
N
O
Capítulo / Chapter 6
Página / Page 147 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
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.
Capítulo / Chapter 6
Página / Page 148 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
ACTION
6.
If clicking on the [OK] icon without entered any
element.
RESULT
Following window is displayed.
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
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
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
The window is closed.
Capítulo / Chapter 6
Página / Page 149 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.16 Icon [LINES] AFTN Lines Status
This icon visualizes the AFTN Lines Window to inform about the status, the ESNI (Expected Sorted
Number Input) and ESNO (Expected Sorted Number Output) of AFTN lines.
Figure 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.
RY
C
Y
P
O
SE
Y
L
N
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
Ta CH (Channel Check) through the lines and waits for receiving
The FDP sends, every 20 seconds,
R2 seconds, the FDP does not receive an answer, the corresponding
another CH as answer. If, within
line turns to “FAIL” status. O
F
Figure 6.2.16-2. AFTN Lines Status Window
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.
One of the lines is in ON status and the other one is in OFF or FAIL status.
Messages will be transmitted alternating both lines.
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.
Capítulo / Chapter 6
Página / Page 150 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.17 [PIP] Icon
This icon displays the PIP Windows that shows the AIP (Aeronautical Information Publication).
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.
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
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 COMMAND AREA
Table 6.2.17.1.1-1. PIP Window. Command Area
Icon/Switch
Command
Back
Shows the last selected document.
Home
Go up to the main menu of the “PIP Window”
Exit
Close the “PIP Window”.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 151 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
C
Figure 6.2.18-2. EST Window
RY
Y
P
O
SE
Y
L
N
O
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.
O
NA
I
P
R
IM
6.2.18.1 EST Window
L
U
E
P
This window allows performing aR
quick EST operation.
G
P
N
NI
I
A
R
T
R
O
F
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.
Capítulo / Chapter 6
Página / Page 152 de / of 157
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.18.1.1 EDITION AREA
Following table presents for each field included in the EST Window, a description.
Table 6.2.18.1.1-1. EST Window. Edition Area
Field
Description
CALLSIGN
Aircraft identification
FIX
Fix name
SPEED
Aircraft speed
ETO
Estimated time over fix.
CFL
Flight level of the aircraft when fly over the fix.
CSSR
SSR code
6.2.18.1.2 COMMAND AREA
RY
C
Y
P
O
O
Following table describes the different commands included in the EST Window.
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
ACTION: QUICK
ESTIMATE PROCEDURE
T
R
O
F
SE
Y
L
N
Table 6.2.18.1.2-1. EST Window. Command Area
Icon/Switch
6.2.18.1.2.1
OK
Perform the EST action over the entered fix (if data are correct).
CLEAR
Delete the data displayed on the EST Window.
ACTION
1.
Command
Click on the [EST] icon
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
RESULT
A window to edit the Fixpoint, ETO, Level and Speed is
displayed.
Capítulo / Chapter 6
Página / Page 153 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
ACTION
RESULT
2.
Enter the callsign value in the corresponding field and
press <Enter> key.
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.
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Capítulo / Chapter 6
Página / Page 154 de / of 157
SE
Y
L
N
O
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.19 [PRINTER1]
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.
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
Figure 6.2.19-1. Printer Selection
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 155 de / of 157
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
6.2.20 [LOGOUT] Icon
By selecting this icon, the position is blocked, so it is not possible to perform any action.
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
Y
P
O
Y
L
N
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>.
RY
C
O
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.
O
NA
I
P
6.2.20.1 Freeze Position
R
IM
L
U
E
P
R
1.
G
P
N
NI
I
A
R
T
R
O
F
ACTION
Click on the [LOGOUT] icon.
SE
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.
Capítulo / Chapter 6
Página / Page 156 de / of 157
The position is unfrozen.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
"Página dejada en blanco intencionadamente"
"This page intentionally left blank"
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Capítulo / Chapter 6
Página / Page 157 de / of 157
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
O
Y
L
N
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
RY
C
Y
P
O
APÉNDICE
OA
NA/ APPENDIX
I
P
M
R
I
L FP ROUTE
U
E
P
G
PR
N
NI
I
A
R
T
R
O
F
A.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
SE
Y
L
N
O
Apéndice / Appendix A
Página / Page 1 de / of 22
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
A.
A.1
FP ROUTE
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.
Y
P
O
Y
L
Each route consists of a points sequence defining a way, interval to the System controlled
airspace,
N
C
between the FP aerodromes pair, which is extracted by the Route Automatic Calculation
Algorithm.
O first point andIt
Y
is obtained from the information of the departure aerodrome,
destination
aerodrome,
E
R
S
last point of the analyzed Route.
A
O
N
The Standard Routes set is not fixed. They areI only displayed whenP
errors are detected in the Original
R
Route analysis.
IM
L
U
Ebetween 0 and 5; depending
The number of Standard Routes is
on if there are Standard Routes,
PData Base.
which are valid for the FP beingR
analyzed, in the Adaptation
G
P
N
A.2 PRESENTATION OF OBTAINED ROUTES
NI WHEN FP ANALYZING
I
A
The Routes List is displayed over the
FP Operation Window. This consists of different characters
R
Tan output route of the Route Automatic Calculation Algorithm.
strings, each one corresponding to
Alongside each one of the routes,
R a letter to identify the route is displayed on the left side:
O
F
Standard Route
`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.
Apéndice / Appendix A
Página / Page 2 de / of 22
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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 /.
C
Y
P
O
Y
L
N
O
E
S
One or more blank characters will separate elements
field.
A forming theO
N
Elements with more than 30 charactersIwill not be allowed. If P
there is an element with more than 30, it
M
R
will be divided into two or more elements,
having the first
element the first 20 characters and the
I
Uelements as morphological error.
second one the remaining ones,L
taking into account these
E
P
Elements with charactersR
different from the aforementioned
ones will not be allowed.
G
P
N
Elements with just one character will not beI allowed.
N
I
Elements exclusively including digits
will not be allowed.
A
R
Elements exclusively including
characters will have a length between 2 and 7 characters.
Talphabetical
Elements including alphanumerical
characters, with or without special ones, will have a length
R
O
between 2 and 29 characters.
F
Blank character
RY
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.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Apéndice / Appendix A
Página / Page 3 de / of 22
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
TIME expresses the estimated time of point crossing level. It is a string of five characters in the form:
T c1 c2 c3 c4
where c1 is a digit. The two first digits, c1 c2, express the day absolute time, forming a number
between 00 and 23, both inclusively. The two remaining digits, c3 c4, express the hour minutes,
forming a number between 00 and 59, both inclusively.
LEVEL expresses the included level or the one is desired to reach when crossing a point. It is a string
of four or five characters, depending on the units it is expressed. The first character will be a letter
indicating the measurement unit it is being used.
a) Altitude in hundredths of feet:
A c1 c2 c3.
Where ci is a digit.
b) Flight Level:
F c1 c2 c3.
Where ci is a digit.
RY
C
Y
P
O
SE
Y
L
N
O
O
NA
I
P
R
IM
Where ci is a digit.
L
U
E
P
R
G
d) Standard metrical
Plevel in tenths of meters:
N
S c1 c2 c3 c4.
NI
I
A
Where ci is a digit.
R
T by the System and given by Adaptation, the element will be
If the values exceed the limits allowed
considered as SEMANTIC_ERROR.
R
O
SPEED expresses the F
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
c) Altitude in tenths of meters:
M c1 c2 c3 c4.
measurement unit it is being used.
a) Speed in kilometres/hour.
K c1 c2 c3 c4.
Where ci is a digit.
b) Speed in knots.
N c1 c2 c3 c4.
Where ci is a digit.
Apéndice / Appendix A
Página / Page 4 de / of 22
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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
Y
P
O
Y
L
String of 2 to 6 characters. The string
has to be acknowledged
as a point
N
C
designator by the System, given byY
Adaptation.
O
E
R
If it is not so, the string will be considered as meaningless.
S
A
O
N
Expression of a point in geodesic coordinates
I
P
M
R
Only degrees
I
L as:
U
E
P
String of 7 characters
Pc2R c4 c5 L2. ING
c1 c2 L1
where ci is a digit and LiN
is a letter.
I
A in degrees, expressing a number between 0 and 89, both
The two first digits show the Latitude
R
inclusively. Letter L1 may take
the
T values “N” for North or “S” for South.
Following are three digits
Rshowing the Longitude in degrees, expressing a number between 0 and 179,
O
both inclusively.
F
Point encoded designator. (FIX POINT)
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.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Apéndice / Appendix A
Página / Page 5 de / of 22
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Following are five digits expressing the Longitude in degrees and tenths and units of minutes, the
three first ones express a number between 0 and 179, both inclusively, and the remaining ones
express a number between 0 and 59, both inclusively.
Letter L2 may take the values “E” for East or “W” for West.
The correct number of digits is completed, when it is necessary, by inserting zeros.
Expression of a point in Bearing and Range with respect to a navigational aid
String of 8 to 11 characters as follows:
a1 a2 c1 c2 c3 c4 c5 c6
a1 a2 a3 c1 c2 c3 c4 c5 c6
a1 a2 a3 a4 c1 c2 c3 c4 c5 c6
a1 a2 a3 a4 a5 c1 c2 c3 c4 c5 c6
Being ci a digit and ai a letter.
The characters set (ai) identify a POINT.
Y
P
O
Y
L
N
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.
RY
C
SE
O
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.
O
NA
I
P
R
FICTITIOUS POINT
IM
L
U
E other two Route points.
It expresses a point over the line joining
P
R
G
Pcharacters as follows:
String of 5 to 16
N
DISTANCE (POINT)
NI
I
Being DISTANCE a string of 1 to 3 digitsA
expressing a distance in nautical miles between the current
Rroute.
point and the previous one withinTthe
They will form a number between 0 and 999, both
inclusively.
R
O
AIRWAY
F
The ATS route encoded designator is a string of 2 to 6 characters. The string has to be acknowledged
The correct number of digits is completed, when it is necessary, by inserting zeros.
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.
Apéndice / Appendix A
Página / Page 6 de / of 22
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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
RY
C
Y
P
O
Y
L
N
O
Strings of 3 or 4 characters. They define departure or arrival standard procedures. The System does
not consider them.
SE
A
O
N
I
String of 2 characters. It defines route sections predefined in the
Adaptation Data Tables, formed by a
P
M
R
I
series of points, pertaining to airways, linking two route points. For that pair of Route points, it will be
L
searched within the Adaptation
Data Tables, if a sectionU
E
P that linked them has been defined.
R
SECTIONS
P SEPARATOR ING
String of 2 characters: “*”. It defines the sections separation where the FP crosses the System
Ninstrumental.
I
controlled airspace and the FP rules are
A
NON-FIX POINT DESIGNATOR
KEYWORDS
R
T
SRXXX R
String of 5 characters.
FOThe two first are the letters ‘S’ and ‘R’. The remaining ones are digits identifying
SR
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
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Apéndice / Appendix A
Página / Page 7 de / of 22
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
String of 8 to 17 characters as follows:
POINT/HOUR
POINT WITH SPEED AND LEVEL CHANGE
String of 11 to 22 characters as follows:
POINT/SPEED LEVEL
POINT WITH CRUISE CLIMB
String of 17 to 29 characters as follows:
C / POINT / SPEED INITIAL LEVEL FINAL LEVEL
C / POINT / SPEED INITIAL LEVEL PLUS
Where PLUS is the word “Plus”.
All these cases may be considered once acknowledged, as POINTS.
SPEED AND LEVEL ELEMENT
Speed and Level Element associated with a point with hour.
C
Y
P
O
Y
L
N
O
E
S hour.
This element will be always related to a previous point
A that is a point withOassociated
N
I
Route Syntax
P
M
R
I
This subchapter will try to identify the elements
L relations withPtheir
U neighbours:
E
Syntactic sequence is defined as
the elements set related with each other by syntactic rules. Following
R
G
sequence are acknowledged:P
N
POINT WITH KEYWORDS
NI
I
A
Form sequence:
R
T
POINT (keyword1) (keyword2)
Where POINT isR
any expression of geographic point as previously defined.
O
Where (keyword1)
F is one of the following keywords: GA (OAT), OMA (GAT), IFR
String of 8 to 10 characters as follows:
SPEED LEVEL.
RY
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:
Apéndice / Appendix A
Página / Page 8 de / of 22
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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
Sequence as follows:
POINTFICTITIOUS.POINT (/FICTITIOUS.POINT)POINT_KEYWORDS
Where FICTITIOUS POINT is a fictitious point.
Y
P
O
It will be checked that both POINT and POINT_KEYWORDS are not within the external airspace to the
one controlled by the System.
Y
L
It will be checked that all fictitious points are internal to the airspace controlled by the System.
N
C
O
The sum of all distances between each fictitious point
and
the
previous
one
has
to be lower than the
Y The number of Efictitious points
distance between POINT and POINT_KEYWORDS.
followed by a
R
A
sequence is optional. If within any of the checks
last condition is not S
fulfilled, all the sequence fictitious
O
N
I
points will be marked with SYNTAX_ERROR.
P
R
IM
DR SEQUENCE
L
U
E
P
Sequence as follows:
R
G
P
POINTDRPOINT_KEYWORDS
N
NI POINT and POINT_KEYWORDS. That section will be
It defines a fictitious points section between
I
searched within the Adaptation Data
Tables from the designators of previous and subsequent point to
A
R
keyword. The proposed route section must exist within the System. If it is not exist, the keyword will be
T
marked with SYNTAX_ERROR.
R
SR SEQUENCE
O
F
Sequence as follows:
FIXPOINT_KEYWORDSSRFIXPOINTS_KEYWORDS
It defines a points’ section between FIXPOINT_KEYWORDS and FIXPOINT_KEYWORDS. That
section will be searched within the Adaptation Data Tables from the designators of previous and
subsequent point to keyword. The proposed section must exist within the System. If it is not exist, the
keyword will be marked with SYNTAX_ERROR.
POINT WITH SPEED LEVEL AND HOUR SEQUENCE
Sequence as follows:
POINT/HOURSPEEDLEVEL
Where POINT/HOUR is the expression of a point with associated hour. Where SPEEDLEVEL is an
element consisting of the expression of associated speed followed by associated level. If the point has
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Apéndice / Appendix A
Página / Page 9 de / of 22
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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
POINT_KEYWORDS
nothing
POINT_KEYWORDS
DCT
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
RY
C
Y
P
O
Y
L
N
O
A sections separator keyword will be considered as syntactically correct, if it is displayed on one of the
following sequences:
SE
O
NA
I
P
R
IM
L
U
E
P
R
Where SECTION.SEQUENCE is
the sections separator
keyword.
G
P
N
I
SPEED AND LEVEL VALIDATION
N
I
In an element with associated speed andA
level, it will be checked if the indicated values are compatible
with the characteristics of the aircraft, R
which will perform the flight, and given by Adaptation.
T
If values exceed the ones allowed to the aircraft, the element will be marked with SYNTAX_ERROR.
R
AIRWAYS VALIDATION O
F
If an element is an airway, it will be analyzed, if it belongs to the upper or lower airspace. If the FP
SECTION.SEQUENCEPOINTRemaining Route
POINTS_KEYWORDS_ASSIGNATION.SECTIONPOINT_KEYWORDS_BRemai
ning
RemainingPOINT_KEYWORDS_ASSIGNATION.SECTION
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.
Apéndice / Appendix A
Página / Page 10 de / of 22
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
Y
P
O
Y
L
N
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.
C
O
E
If a SID keyword is the first Route element, it will be deleted. If it S
is not the first element, it will be
A
marked with SYNTAX_ERROR.
O
N
I
P
If a STAR keyword is the last Route
R If it is not the last element, it will be
IMelement, it will beUdeleted.
marked with SYNTAX_ERROR.L
Eelement and it is Pa SID/STAR keyword, it will be marked with
If there is only one Route
R
G
SYNTAX_ERROR. P
N
Purged Route
NI
I
The Purged Route is extracted A
from the Original Route once the morphological, semantic and
R
syntactic analysis has been performed.
T
R is correct and it is not an aerodrome internal to the System controlled
If the departure aerodrome
airspace, this will tryO
to find the first internal or boundary point when going through the Route from left
F
SID/STAR KEYWORDS VALIDATION
RY
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.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Apéndice / Appendix A
Página / Page 11 de / of 22
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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:
Y
P
O
Y
L
N
If that airway crosses a Transition Fix Point of that aerodrome, the point will be inserted and a
procedure will be recognized.
RY
C
SE
O
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:
O
NA
I
P
a.2 The selected Fix Point, without
to the R
point subsequent to the airway, is the
IMbeing identical
one with lower number of intermediate
points in the
airway
L
U to go to the subsequent point.
E
P
b. First Route elements make R
up a points sequence not linked by DCT keywords:
Gprocedure containing the sequence points
P
The system will select that departure
N
I
and in the expressed order. IfN
no procedure is found fulfilling the conditions, no
I
procedure will be considered.
A
R
If the destination aerodrome belongs
to
the
T System controlled airspace and the last Route element is
not the procedure designator, the System will try to recognize an arrival procedure from the
R
information included in the O
Route field.
F
a.1 The element subsequent to the airway is a point belonging to the airway.
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.
Apéndice / Appendix A
Página / Page 12 de / of 22
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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}
Y
P
O
{Non_Sacta Departure} BOUNDARY_point/ BOUNDARY_coordinate DCT {Sacta Destination}
Y
L
N
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.
C
O
Y
Before proceeding with the Route elements continuity, it is necessary
to make clear the airway
E
R
concept fulfilling level and direction conditions
S rules between the set crossing
Aand the airway selection
O
N
two points.
I
P
M
An airway crossing between two points
fulfils direction andR
level conditions when:
I
L
Uthan the maximum allowed to the airway and
a. The FP level in the firstE
considered point is lower
P
higher or equal to theR
minimum allowed to G
the airway.
P
b. The Adaptation Data Table gives theIN
N airway direction when the message is received from the
AFTN string.
I
A
c. The airway direction within R
the remaining cases is considered as a return one.
T two given points will be the following ones:
Airways selection rules crossing
Rand direction conditions will be selected.
a. Those fulfilling level
O
F
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.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Apéndice / Appendix A
Página / Page 13 de / of 22
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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
RY
C
Y
P
O
SE
Y
L
N
O
O
NA
I
P
If more than one airway is found, the airways
R in previous paragraph will be
IM selection rulesUdescribed
applied.
L
E
P
e.3 They do not belongR
to the same airway, but POINT_1 is crossed by one airway, AWY_1,
G too. Both of them will intersect in a unique
and POINT_2 is P
crossed by one airway AWY_2
N
point INTERSECTION_POINT. Thus,
only one, AWY_1 is found
NI just one airway,andandfulfilling
crossing a POINT_1 and INTERSECTION_POINT
direction and levels
I
conditions, and just airway,
and
only
one,
AWY_2
is
found crossing
A
INTERSECTION_POINT R
and POINT_2 and fulfilling direction and level conditions.
T
The Route will be completed, firstly by inserting INTERSECTION_POINT between POINT_1 and
R
POINT_2, secondly withOthe AWY_1 points, which are intermediate to POINT_1 and
Finserting them between those points, and finally, with the AWY_2 points
INTERSECTION_POINT
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.
Apéndice / Appendix A
Página / Page 14 de / of 22
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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:
Y
P
O
Y
L
g.2.2. The Route will be completedC
with the airway intermediate
points between
N
POINT and INTERSECTION_POINT.
O
Y
E
R
g.2.3. INTERSECTION_POINT
and
AWY_1
will
be
marked
with
S
A
DISCONTINUITY_ERROR.
N cause POINT PandO AWY_1 to be marked with
I
Remaining situations
will
R
IM
DISCONTINUITY_ERROR.
L
U
Eand an airway in between.
P
h. Sequences with two points
R
G
Being the sequence: P
N
NI
POINT_1AIRWAYPOINT_2
I
A
Following cases will be given: R
T
h.1 Points belong to the airway. If airway fulfils direction and levels conditions, the
intermediateR
AIRWAY points to POINT_1 and POINT_2 will replace this.
O
If airway doesFnot fulfil those conditions, the three elements will be marked with
g.2.1. INTERSECTION_POINT will be inserted between POINT and AWY_1.
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
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Route
will
be
completed
between
POINT_1
and
Apéndice / Appendix A
Página / Page 15 de / of 22
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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
POINT_2.
will
RY
be
C
Y
P
O
inserted
Y
L
N
between
SE
AIRWAY
and
O
b.) The Route will be completed between INTERSECTION_POINT and
POINT_2 with the points intermediate to AWY_2, between both points.
O
NA
I
P
d.) The
RouteM will
be
completed
R between POINT_1 and
I
INTERSECTION_POINT
with U
the intermediate points belonging to
L
E between both points.P
AIRWAY,
R
P are not fulfilled inIN
If direction and level conditions
anyG
of the steps for some of the airways or there is
ambiguity in the appropriate airway searching, the three elements will be marked with
N
I
DISCONTINUITY_ERROR.
A
R
h.3 Points do not belong to the
airway.
Tare fulfilled:
If following conditions
R
O
a.) If one airway,
and only one, AWY_1, is found crossing POINT_1 and intersecting
F
AIRWAY in just one point, POINT_C1, and fulfilling direction and level conditions
c.)
AIRWAY will be deleted.
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.
Apéndice / Appendix A
Página / Page 16 de / of 22
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
Y
P
Y First element
L
i.2 If the aerodrome does not belong to the System
internal controlled airspace.
O
N
is continuous when there is no error and: C
O
Y
a.) It is a sections separator keyword.
E
R
S
A
b.) It is a DCT keyword.
O
N
I
P
c.) It is a Fix Point or Coordinate.
M
R
I
L
U
Continuity Destination Aerodrome and Last Route Point.
Ebelongs to the System
P internal controlled airspace. Last element is
R
j.1 If the aerodrome
G
continuousP
when there is no error
and:
N
a.) It is a sections separator
NIkeyword.
I
A
b.) It is a DCT keyword.
R
c.) It is a pointT
of the arrival procedure sequence.
R
j.2 If the aerodrome
to the System internal controlled airspace. Last element
FO whendoestherenotisbelong
is continuous
no error and:
c.)
j.
It is a point of the departure procedure sequence.
a.) It is a sections separator keyword.
b.) It is a DCT keyword.
c.)
It is a FIX POINT or a COORDINATE.
ROUTE SEPARATION INTO SECTIONS
A section will be defined as a points sequence defining a route controlled by the System. Those points
have to belong to the System controlled airspace and the flight rules have to be IFR. It is necessary to
distinguish within each section:
a. Entry point. That one where the route starts. It can be a Departure Aerodrome (internal
aerodrome and IFR flight rules), boundary point or internal point with flight rules change into IFR.
Except for the first section, an entry point will have associated a crossing time.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Apéndice / Appendix A
Página / Page 17 de / of 22
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
Y
P
O
Y
L
N
C
O
Y
The System will try to separate the Route into different sections.
E
R
A criteria. OS
Firstly, it will try to separate them by means of geographical
N
I
PFP and the geographical point
The geographical point, where the System will take contact with the
M
R
I
where the contact will finish, will be searched.
L
U
E
P
The section entry is defined with one of the following sequences:
R
G
P
a. Departure aerodrome belonging to the System
controlled airspace, providing that the first Route
N
element is not a sections separator keyword.I
N
I
b. Boundary point to the System controlled
airspace.
A
R
c. Internal point to System controlled
T airspace. Whenever one of the following circumstances is
given:
R
O
c.1 It is the first Route
F 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.
Apéndice / Appendix A
Página / Page 18 de / of 22
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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:
Y
P
O
Y
L
N
C
O rules:
Y
b. Sequence where flight starts with visual rules
and changes into instrumental
E
R
S
A
elem_1 elem_2 ... elem_i IFR elem_j ... elem_n
O
N
I
P
It will remain as:
M
R
I
U
elem_i IFR elem_j ... elem_n L
E
P
R keyword is found
Whenever no erroneous IFR/VFR
in the deleted sequence.
G
P
IN rules and changes to visual rules:
c. Sequence where flight starts with instrumental
N
I ... elem_n
elem_1 elem_2 ... elem_i VFR elem_j
A
R
It will remain as:
T
elem_1 elem_2 ... elem_i
VFR
R
Whenever no erroneous
FO IFR/VFR keyword is found in the deleted sequence.
a. Sequence without flight rules change. The resulting sequence will be identical to the original one.
d. Sequence where the points with visual rules are in between.
elem_1 elem_2 ... elem_i VFR elem_j ... elem_i IFR elem_m ... elem_n
It will be divided into two sections:
elem_1 elem_2 ... elem_i VFR
elem_i IFR elem_m ... elem_n
Whenever no erroneous IFR/VFR keyword is found in the deleted sequence.
Finally, boundary points in the extremes of the different obtained sections will be calculated.
For the left section extreme, following cases will be presented:
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Apéndice / Appendix A
Página / Page 19 de / of 22
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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
Point_1
Sequences:
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
Y
P
O
Y
L
N
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:
RY
C
SE
O
O
NA
I
P
These last points will be marked to validateM
them with VALIDATE_BOUNDARY_POINT error.
R
I
L
U
5
Sequence:
E
P
R
{Near external aerodrome} Internal_Point
G
P
N
A point of the line joining both points that is in Ithe border to the System controlled airspace will be
N Internal_Point and will be marked with
calculated. It will be inserted before
I
VALIDATE_BOUNDARY_POINT error. A
R
6
Remaining cases. It is not T
calculated. If first section element is correct, it will be marked with
R error.
VALIDATE_BOUNDARY_POINT
O
For the right section extreme,
F following cases will be presented:
Boundary_point Point_to ... Point_previous_to_Point_1
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
Apéndice / Appendix A
Página / Page 20 de / of 22
Point_2
Point_1
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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}
Y
P
O
Y
L
N
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.
C
O
Y
11
Remaining cases. It is not calculated. If
last section element isE
correct, it will be marked with
R
S
A
VALIDATE_BOUNDARY_POINT error.
O
N
I
P
M
R
I
Special cases where section is considered
correct.
L
U
E
P
{Sacta Departure} DCT R
POINT_COORDINATE DCT {Sacta Destination}
G
P
{Sacta Departure} DCT BOUNDARY_point/BOUNDARY_coordinate
{Non_Sacta Destination}
N
I
N
I
{Non_Sacta Departure} BOUNDARY_point/BOUNDARY_coordinate
DCT {Non_Sacta Destination}
A
{Sacta Departure} DCT POINT/COORDINATE
DCT {Near_Non_Sacta_Destination}
R
T
{Near_Non_Sacta_Departure} DCT POINT/COORDINATE DCT {Sacta Destination}
R
In this case, there O
is section once the followed trajectory is known, this is within the controlled
F
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:
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Apéndice / Appendix A
Página / Page 21 de / of 22
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Apéndice / Appendix A
Página / Page 22 de / of 22
SE
Y
L
N
O
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
RY
C
Y
P
O
APÉNDICE
OB
NA/ APPENDIX
I
P
M
R
I
L
U
ERRORS
DISPLAY
E
P
G
PR
N
NI
I
A
R
T
R
O
F
B.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
SE
Y
L
N
O
Apéndice / Appendix B
Página / Page 1 de / of 2
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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, …
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Apéndice / Appendix B
Página / Page 2 de / of 2
SE
Y
L
N
O
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
C.
C
Y
P
O
APÉNDICE / APPENDIX
C
Y
AR
SE
Y
L
N
O
O
N MESSAGES
I
ROUTE FIELD
P
M
I
L
E
PR
R
O
F
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
N
I
RA
G
N
I
R
U
P
T
Apéndice / Appendix C
Página / Page 1 de / of 2
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Apéndice / Appendix C
Página / Page 2 de / of 2
SE
Y
L
N
O
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
C
Y
P
O
Y
L
N
O
E
S
APÉNDICE /AAPPENDIX D
O
N
I
P
M
R
I
L
ERROR MESSAGE
OF ROUTE
FIELD
U
E
P
G
PR
N
NI
I
A
R
T
R
O
F
RY
D.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Apéndice / Appendix D
Página / Page 1 de / of 4
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
D.
D.1
ERROR MESSAGE OF ROUTE FIELD
INCORRECT EDITION
Description
A Morphological error has been detected in the analysis; the erroneous element is underlined when
displayed.
User Options
There are two options for the user:
Erroneous field correction.
Rejection of the function in process.
D.2
UNKNOWN ELEMENT
Y
P
Yelement is
An error has been detected while analyzing, the element is unknown
by the System and
L
O
N
underlined when displayed.
C
O
Y
User Options
E
R
S
A
There are two options for the user:
O
N
I
P
Erroneous field correction.
M
R
I
L
U
Rejection of the function in process.
E
P
R
G
D.3 FIELDS INCOHERENCE
P
N
NI
Description
I
A circumstances:
An error may happen in some of the following
R
T
When validating a determined element position within the characters string and its relation with
R is underlined.
neighbouring elements. That element
O
When a Fictitious PointsF
sequence is not properly defined. The sequence is underlined.
Description
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
Apéndice / Appendix D
Página / Page 2 de / of 4
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
There are two options for the user:
Erroneous field correction.
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.
User Options
There are two options for the user:
Discontinuity deletion by following the continuity criteria as established in point 3 of this annex.
Function rejection.
D.5
VALIDATE BOUNDARY POINT
C
Y
P
O
Y
L
N
O
E
When a point is calculated, between one
external point and another
internal one, which belongs
Selement
A
O
to the border. Only the calculated point
that
replaces
the
external
is underlined.
N
I
P
M by going through
When a boundary point is calculated
R an airway until reaching the border. All
I
L
U
inserted points are underlined.
E
P
R
User Options
G
P
N
I
As follows:
N
I
Change the current route for the calculated one and click to validate the boundary point.
A
R
T
R
O
F
Description
RY
This message may happen in some of the following circumstances:
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Apéndice / Appendix D
Página / Page 3 de / of 4
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
"Página dejada en blanco intencionadamente"
"This page intentionally left blank"
Apéndice / Appendix D
Página / Page 4 de / of 4
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
RY
C
Y
P
O
SE
APÉNDICE
OE
NA/ APPENDIX
Y
L
N
O
I
P
M
R
I
LOCAL FUNCTIONS
ERROR
L
U MESSAGES
E
P
G
PR
N
NI
I
A
R
T
R
O
F
E.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Apéndice / Appendix E
Página / Page 1 de / of 12
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
E.
LOCAL FUNCTIONS ERROR MESSAGES
MESSAGE
DESCRIPTION
Correct
Compulsory
Syntactic
New call sign in use
Rank error
Apéndice / Appendix E
Página / Page 2 de / of 12
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
Unknown element
Error field
Element not accessible
Incoherence
RY
Discontinuity
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
FIR time not computable
External point expected
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Apéndice / Appendix E
Página / Page 3 de / of 12
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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
Apéndice / Appendix E
Página / Page 4 de / of 12
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
Correct analysis
Flight plan already exists
Full file
Inaccessible FP
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Apéndice / Appendix E
Página / Page 5 de / of 12
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
FDD not allowed
Different shape to adapted
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
Illegal modif. of operative area
Apéndice / Appendix E
Página / Page 6 de / of 12
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
Line is offline
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Apéndice / Appendix E
Página / Page 7 de / of 12
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
RY
C
Y
P
O
O
NA
I
P
Success
R
IM
L
U
P
Impossible Trans Received Msg E
R
G
P
N
Queuing not allowed
I
N
I
Queue is full
A
R
T
None found
R
O
F
SE
Y
L
N
O
No response
Unknown message type
Illegal shape
Apéndice / Appendix E
Página / Page 8 de / of 12
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
Printer unavailable
No data available
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Apéndice / Appendix E
Página / Page 9 de / of 12
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
Exceeded capacity
Illegal modif. of active area
Apéndice / Appendix E
Página / Page 10 de / of 12
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
No FPs for this filter
R
O
F
SE
Y
L
N
O
Timeout error
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Apéndice / Appendix E
Página / Page 11 de / of 12
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
"Página dejada en blanco intencionadamente"
"This page intentionally left blank"
Apéndice / Appendix E
Página / Page 12 de / of 12
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
RY
C
Y
P
O
E
APÉNDICE /AAPPENDIX FS
O
N
I
P
R
IM
COORDINATION
MESSAGES
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
F.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Y
L
N
O
Apéndice / Appendix F
Página / Page 1 de / of 26
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
Y
P
O
Y
L
The flight to be coordinated for exit from the Upstream sector is presented in the Flight
Plan list, in the
N
C
Active section. The XCOORD fields are affected by the coordination process.
O
Y
E
R
The System implements the following coordination basic procedure mandatory messages using OLDI:
S
A
ABI, ACT, REV, PAC, MAC and LAM, in ICAO format.
O
N
I basic procedurePcomplementary messages using
The System implements the following coordination
M
R
I
OLDI: COD, in ICAO format.
L
U
E
P
R
G procedure messages in ICAO format. The
P
The System also implements the coordination Idialogue
N
capacity to upgrade the dialogue procedureN
I for the transfer phase is performed using ICAO and
ADEXP format messages if necessary. A
TR
Rcoordination, following automatic steps are inhibited.
If a controller performs a manual
O
The reception of messages
F 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.
Apéndice / Appendix F
Página / Page 2 de / of 26
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
RY
C
Y
P
O
SE
Y
L
N
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
Downstream sector
R
If received
are correct, the Downstream sector sends back a LAM message to
O
F messages
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
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Apéndice / Appendix F
Página / Page 3 de / of 26
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
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).
Apéndice / Appendix F
Página / Page 4 de / of 26
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
RY
C
Y
P
O
SE
Y
L
N
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
Downstream sector
T
Rthe System receives a coordination message from a partner with which the
When
O
dialogue
procedure is configured, it checks whether transfer conditions comply with
Fdefined 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 coordination 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.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Apéndice / Appendix F
Página / Page 5 de / of 26
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
Initiation
The System provides the capacity to initiate the transfer phase in three ways:
Y
P
Y by
L
The Downstream sector manually sending a ROF message,
automatically responded
O
N
C
an Upperstream TIM message;
O
Y
The Upperstream manually sending an SDM message.
E
R
S
A
O
N
I
P
The System provides the Upstream controller
with the capacity of sending a HOP message in order to
R
IM
initiate a transfer to any sector, regardless
of its presence on the
route of flight.
L
U
E
P
The System permits to enable and
disable the automatic HOP sending at the transferring sector.
R
P sector withINtheGcapacity of entering a “Skip” command so as to
The System provides the Downstream
pass the transfer initiation to the next sector on
Nthe trajectory.
I
A
R
T
Revision
R
If there are transfer data to be modified, the System provides the capacity to perform the revision in
O
two ways:
F
The Upperstream sector automatically sending a TIM message;
The Upperstream sector automatically sending an SDM message;
The Downstream sector manually sending a ROF message.
Execution
In order to complete the transfer, the System provides the capacity for:
F.3
The Upperstream sector manually sending a COF message;
The Downstream sector manually sending a MAS message.
AIDC COORDINATION MESSAGES
ABI (ADVANCE BOUNDARY INFORMATION)
Apéndice / Appendix F
Página / Page 6 de / of 26
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
Y
P
O
Y
L
The System uses the CDN message to propose changes
to the coordination conditions
agreed to in a
N
C
previously transmitted CPL, EST, PAC or CDN message. The System receives
ACP message to
Oa REJanmessage,
Yif the System receives
terminate the initial coordination dialogue; otherwise,
it leaves
E
R
S
A
the coordination conditions as previously agreed.
O
N
I
P
R
IM
CPL (CURRENT FLIGHT PLAN)L
U
E
P
The System uses the CPL
message to initiate initial coordination dialogue with another automated
R
G
P flight.
ATS system for a specific
N
I
EST (COORDINATION ESTIMATE) N
I
Ato inform the receiving centre of the crossing conditions for a flight
The System uses the EST message
R
and to indicate that the conditions
in compliance with agreements between both parties. The
T toarecomplete
System receives an ACP
message
the coordination process.
R
FO
CDN (COORDINATION)
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)
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Apéndice / Appendix F
Página / Page 7 de / of 26
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
Y
P
O
TOC (TRANSFER OF CONTROL)
Y
L
N
The System uses the TOC message to offer the receiving centre executive control of a flight.
C
Oupon reception of
Y
The following diagram depicts the possible flight stateR
transitions within the System
E
S
AIDC coordination messages.
A
O
N
I
P
M
R
I
L
U
E
P
G
PR
N
NI
I
A
R
T
R
O
F
CDN
ABI
CPL
ABI
Pre-Notifying
Notifying
Negotiating
MAC
EST
PAC
ACP
Coordinating
MAC
ACP
CDN
CDN
Transferred
Transferring
AOC
Coordinated
Re-negotiating
TOC
ACP
REJ
ACP
CDN
LEGEND
REJ
Backward
Re-negotiating
MSG
MSG transmitted by the controlling ATS unit
MSG
MSG transmitted by the downstream ATS unit
CDN
MSG
MSG transmitted by either the controlling or
the downstream ATS unit
Figure F.3-1. Transitions of AIDC coordination messages
The system implements an AIDC messages management policy.
Apéndice / Appendix F
Página / Page 8 de / of 26
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
Y
P
O
All data transferred is controlled by Surveillance messages.
The System supports abbreviated AIDC dialogue.
RY
C
SE
Y
L
N
O
A
O will have the possibility to check
N
I
AIDC workstation keeps all messages sent or received. Operators
P
R
IM
this historical information.
L
U
E
P
1st Phase: Notification
R
G
Psector
Upstream
N
I COP, the Upstream sector sends an ABI message (not a
An adapted time before
N
I
mandatory action)
to notify the Downstream sector of the coming coordination.
A
The controller
also initiate a semi-automatic notification phase. If the controller
TRmay
starts a SEND
ABI command, the Upstream sector sends an ABI message to notify
the Downstream
sector.
R
O
The
System sends revised ABI messages if changes affecting notification data
F
The System supports up to 15 different AIDC dialogues.
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.
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Apéndice / Appendix F
Página / Page 9 de / of 26
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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.
C
SE
Y
L
N
O
O
NA
I
P
Upstream sector
R
IM
L
U
An adapted timeE
before COP, the Upstream sector sends an EST message (this is
P
a mandatoryR
action for the coordination process) to initiate coordination with the
G
Downstream
P sector.
N
If an ACP message isIreceived in return, the “Status” field displays “EST
N flight in the Flight Plan list.
RCV” for the corresponding
I
A timeout the ACP message is not received, the “Status”
If after an adapted
R
field displays
“EST
TO” (EST ACP time-out) for the corresponding flight plan.
T
In any case,
the Upstream controller may manually coordinate with the
R
Downstream
controller.
Then upon clicking COORD-OK in the FP Template, the
Ofield displays “MAN”
“Status”
(Manual) for the corresponding flight plan, to indicate
F
that manual coordination has taken place.
2nd Phase: Coordination
RY
Y
P
O
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.
Apéndice / Appendix F
Página / Page 10 de / of 26
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
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 resubmitted 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.
F.4
1
a
C
Y
P
O
Y
L
N
O
E
S phase with the Upperstream
The System provides the capacity
to initiate the transfer
Asending
O
sector automatically or manually
a
TOC
message.
N
I of accepting the transfer
P by sending an AOC message.
The Downstream is capable
M
R
I
L capability of initiating
Both parties has the
a backward re-negotiation by sending CDN
U
E
P
messages, which
may be accepted (ACP)
or rejected (REJ).
R
G
P
N
COORDINATION MESSAGES WINDOWS
I
N
I
ABI (Advanced Boundary Information)
A
R
T
R
O
F
3rd Phase: Transfer
RY
ABI Correction
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
Apéndice / Appendix F
Página / Page 11 de / of 26
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
b
ABI in “Q” QUEUE
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Apéndice / Appendix F
Página / Page 12 de / of 26
SE
Y
L
N
O
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
2
ACP (Accept message)
3
CDN (Coordination message)
RY
4
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
ACT (Activation R
Message)
O
F
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
SE
Y
L
N
O
Apéndice / Appendix F
Página / Page 13 de / of 26
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
5
AIDC (Air Traffic Services Interfacility Data Communications)
RY
6
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
I
N
I
ARR (Arrival Message)
A
R
T
R
O
F
Apéndice / Appendix F
Página / Page 14 de / of 26
SE
Y
L
N
O
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
7
CHG (Change Message)
RY
8
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
I
CNL (Cancellation Message) IN
A
R
T
R
O
F
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
SE
Y
L
N
O
Apéndice / Appendix F
Página / Page 15 de / of 26
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
9
10
CPL Correction (Current Flight Plan)
DEP (Departure Message/List)
Apéndice / Appendix F
Página / Page 16 de / of 26
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
11
DES (Data Exchange System)
12
DLA (ATS Message indicator for delay)
RY
13
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
EST (Estimated)
R
O
F
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
SE
Y
L
N
O
Apéndice / Appendix F
Página / Page 17 de / of 26
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
14
FLS (Flight Suspension Message)
15
IFPL (Individual Flight Plan Message)
RY
16
C
Y
P
O
A
O
N
I
LAM (Logical Acknowledgement Message)
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Apéndice / Appendix F
Página / Page 18 de / of 26
SE
Y
L
N
O
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
17
LRM (Logical Rejection Message)
RY
18
C
Y
P
O
O
NA
I
P
M
R
I
L
MAC (Message for the Abrogation of Coordination)
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
SE
Y
L
N
O
Apéndice / Appendix F
Página / Page 19 de / of 26
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
19
NOTAMC (Notice To Airmen Cancellation)
RY
20
C
Y
P
O
O
NA
I
P
R
IM
NOTAMN (Notice To Airmen N)
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Apéndice / Appendix F
Página / Page 20 de / of 26
SE
Y
L
N
O
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
21
NOTAMR (Notice To Airmen R)
RY
22
C
Y
P
O
O
NA
I
P
R
IM
L
U
PFL (Planned Flight Level)
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
SE
Y
L
N
O
Apéndice / Appendix F
Página / Page 21 de / of 26
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
23
REJ (Rejection Message)
RY
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
24
REV (Revision Message)
25
RQP (Request Plan Message)
Apéndice / Appendix F
Página / Page 22 de / of 26
C
Y
P
O
SE
Y
L
N
O
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
26
27
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
SLC (SideF
Lobe Cancellation)
SAM (Slot Allocation Message)
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
SE
Y
L
N
O
Apéndice / Appendix F
Página / Page 23 de / of 26
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
28
SRM (Sector Revision Message)
29
SVC (Service)
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Apéndice / Appendix F
Página / Page 24 de / of 26
SE
Y
L
N
O
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
30
SVC RFP (Service for Repetitive Flight Plans)
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
SE
Y
L
N
O
Apéndice / Appendix F
Página / Page 25 de / of 26
FDD-UM
Procurement of the Renovation of Existing Radar and Additional Requirements / Turkey
RY
C
Y
P
O
O
NA
I
P
R
IM
L
U
E
P
R
G
P
N
NI
I
A
R
T
R
O
F
SE
Y
L
N
O
"Última página del documento"
"The last page of the document"
Apéndice / Appendix F
Página / Page 26 de / of 26
Doc.Nº: 0026700000002MA02
Edic./Rev.: A/0
Fecha / Date: 04/05/2010
