FDPS

Flight Data Processing
Systems (FDPS)
Networks:
• SITA Primary Systems
• ARINC Communication Core Data Processing Data Processing VCS
and Distribution Voice
• RAPNET, RENAR, Communication
CAPSIN STCA Systems
Short-Term Conflict
• AFTN/CIDIN FDPS Alert
Man-Machine
• PENS Flight Data
Interfaces
Processing CWP
Data Gateways Controller Working
System
• Surveillance Position
• Flight Data
• ATFCM Technical Monitoring
and Control
• Datalink SDPS Centre Services
• … Surveillance • UPS
Operational
Data • Building
Monitoring and
• Diesel
Processing Control
Generators
System • …
(e.g: ARTAS)
ATFCM/ASM systems
• Flight Plan messages

• OLDI messages Support systems
• Radar data (ASTERIX) Support LAN
• MET messages
• Datalink
Primary LAN
Protocols: Firewall
• AFTN/CIDIN
Fallback Systems
• AMHS Fallback Data Fallback - Fallback -
• TCP/IP Gateways FDPS CWP
• VOIP • Surveillance
• Flight Data Fallback - Fallback - Fallback -
• … SDPS STCA VCS
Direct radars Fallback LAN

The Flight Data Processing System (FDPS)
The FDPS primary tasks are:
 to manage and provide access to the flight data

 to process flight plan related messages and inputs, and create, update or delete the
corresponding flight data
 to calculate the sectors that will be in charge of the flight
 to distribute the appropriate flight data at the right time to the correct Controller Working
Positions, other internal subsystems and external partners
 to manage the pool of SSR codes and to assign them to incoming flights as necessary
 to perform the correlation of track data and flight data
 to support automated co-ordination and transfer – internal as well as with adjacent centres
 to calculate the trajectory of the flight
 to monitor the flight’s adherence to the expected trajectory, and to provide a warning to the
appropriate Controller in case of deviations
 to support sectorisation changes
 to support Air-Ground Data Link applications
 to predict future separation infringements between aircraft and propose
FDP Architecture
FDP Logical Decomposition
ASP MET CONF

Airspace Data Meteorological Data Configuration
Manager Manager Manager
ATC Environment Configuration

Cluster Cluster
FDM TM CORD SSRM CORR

Flight Data Trajectory Coordination and SSR Code Correlation
Manager Manager Transfer Manager
Flight Manager
Cluster
MTCM FPM AGDL

Medium Term
Flight Path Air Ground
Conflict
Monitoring Data Link
Manager
ATC Tools Interoperability

Cluster Cluster
4
The Flight Data Manger (FDM)
Initial Flight Plan Processing

Initial Flight Plan Data Processing
Flight Plan Data Sources
Adjacent Air AFTN

NMOC AIS/ARO
Centres Defence Users
ATS messages, Coordination, System Tracks, Aeronautical Info, AFTN / AMHS

Slot Messages, FP Info Flight Data ATS Messages Messages
Flight Activation
Communication Networks
Internal Sources
CWP
FDP Data Display >
System < Inputs
FDO
 ICAO
 ADEXP
Formats  IDL
 ASN1
 Proprietary formats
11
Flight Plan Information
 SFPL (System Flight Plan)

Internal flight (at least ACID, reference time, route, TAS/aircraft
plan types and RFL)
 ASPL (Abbreviated System Flight Plan)
 External
 ACID
 ADEP
Flight plan  ADES
identification  EOBT
 EOBD
 Internal unique identifier for internal unequivocal

identification
12
Flight Plan creation
SFPM RTE CSTM TP SCM COO SSRM

FP
Creation
Route
extraction
Build
Strategic
Calculate
trajectory
Calculate
Progression
Coordination
Data
SSR code
assignment
Flight Plan Messages
 Creation Messages:
 FPL and APL (ICAO)
 IFPL and IAPL (ADEXP)
 OLDI: ABI, PAC, ACT, RAP (ICAO/ADEXP): if the
 SFPL/ASPL manual creation
 Modification Messages:
 CHG, DLA, DEP, ACH, ARR and CNL (ICAO)
 ICHG, IDLA, IDEP, IACH, IARR and ICNL (ADEXP)
 OLDI: ABI, PAC, ACT, RAP, REV, RRV, LAM, SBY, ACP, RJC, CDN, MAC, TIM,
SDP, HOP, ROF, COF, MAS (ICAO/ADEXP)
 Manual modification (FP update, XFL…) input
 SAM, SRM, SLC, FLS and DES
14
Correlation (CORR)
INDEX
01 Introduction
02 Aircraft Identification:
 SSR Code Management
 SSR Code Assignment/Retention
 SSR Code Release
03 Correlation
 Correlation Generalities
 Automatic Correlation
 Manual Correlation
 Correlation Maintenance
 De-Correlation
20
Aircraft Identification and SSR Code Management
Introduction
Definitions:
 Code Management:
Assessment, assignment and notification of SSR codes to flights to allow their use for
flight track identification
 Code Assignment:
Distribution of discrete SSR codes to aircraft according to ORCAM rules
 Correlation:
Process of binding a flight plan to a track
 PSSR Code (Present SSR code):

SSR code that the flight should be squawking
 ASSR Code (Assigned SSR code) :

Code that a controller will request the pilot to use
21
INDEX
01 Introduction
02 SSR Code Management:
03 Correlation
 De-Correlation
22
SSR Code Management (I)
 SSR code classification defined in adaptation data
 Organised into pools according to the ORCAM allotment plan

All Codes
4096
Classes Assignable Non-assignable

code list code list
2 subclasses 2 subclasses
Subclasses Automatically Assignable Manually Assignable

Code Pools code list Special Codes SUCs
7700,7600,7500 e.g 0021
LDC 1
rules, e.g. destination lists
LDC 2
Pools rules
GDC
rules
TC
rules
Mode S
1 SSR Code
SDC 1
SDC 2
etc. 23
SSR Code Management (II)

Exit conditions for SSR codes
Assignment
COORD. Destination Pool
Partner list
EDMM 1 A1
Destination Lists
Nº Region
EDMM
.
2
.
A2
. Pool
1 A,B,C,D . . .
2
3
F,G,M,S
EE,EP,EY
.
.
.
.
.
. A1
EDUU 8 B5 0201-0257
. .
. . 0401-0477
. .
. . Exit conditions for SSR codes Alternative
. . Retainment Pools
.
.
.
.
COORD.
Partner
Destination
list
Pool C8
0501-0577
. . EDMM 1,7,9 D2
. . EDFF 2,8 C3
. . . . .
. . .
. . . . .
40 EDDM,ETS,EDN . . .
EDUU 4 C1 B12
0677 Basic
Code
Entry conditions for SSR
codes Retainment
COORD. Pool
Partner
EDMM C1
LFEE B2
. . .
. . .
. . .
. . .
LSA2 C3
24
SSR Code Retention
 Inbound Flights:
 Code assigned by upstream  PSSR
 PSSR = Mode A:
 PSSR retainable and not assigned to a flight
exiting into same FIR within a time parameter
 PSSR = Conspicuous (Mode S): no further
assignment
 Flight doesn't leave Mode S coverage, or
 Time to exit Mode S coverage bigger than
a defined parameter
automatic
 If PSSR can not be retained: assignment
25
SSR Code Assignment
 Departing Flights or Flights with PSSR No Retainable:
 System automatically assigns a code to the flight

 ASSR
 Code Assignment Priority:

 Conspicuous code (if Mode S switch is enabled)
 Mode A code from preferred Pool
 Mode A code from alternate Pool
 Mode A code from basic Pool  Notification to CWP
 Code assignment reviewed upon FP route modifications:

 ADES Changes
 Exit into a different partner
26
SSR Code Release
Event Release code

 Code change (if no longer eligible for correlation) After VSP time
 Landing
 Terminated
 Manual Immediately
 Others: No
• Surveillance track drop,
• Unexpected code change
27
INDEX
01 Introduction
02 SSR Code Management :
03 Correlation
 De-Correlation
28
Correlation Generalities
 Associate surveillance data representing a track with a system flight

plan
 Several surveillances data trackers can provide track data to FDP
 Correlation will take into account potential switching of tracker
 Correlation function can have instances on remote sites (e.g:

Local/Regional Airports)
 Ensure correlation function using local trackers when connection to

central system is down.
29
Automatic Correlation
 Correlation of eligible FPs is sought every track update cycle
 Candidate tracks are selected from expectation volumes
 Correlation ambiguity:
 One uncorrelated track matches more than one uncorrelated flight
 One uncorrelated flight matches more than one uncorrelated track
 Correlation warnings for uncorrelated eligible flights after defined time

period.
30
Manual Correlation
 Solve correlation for flight plans with ambiguity indications
 Correlate a track with a flight plan where automatic correlation

conditions are not appropriate
 Create an abbreviated flight when requested flight plan doesn't

exist
 Abbreviated flight will contain the callsign and the SSR code
31
Correlation Maintenance (I)
 Correlation is maintained upon:
 Track code change to a special code

 Provide Info to generate Special Condition Report
 Track squawks ASSR code

 ASSR code becomes PSSR
 ASSR code is removed from flight
 Track becoming a primary surveillance radar track
32
Correlation Maintenance (II)
 Correlation is maintained upon:
 Unexpected code changes when:

 FP is already coordinated or assumed
 FP has already left the AoR
 Switching between tracker changes:
 Between ARTAS trackers

 From ARTAS to SFR
 From central correlation to regional trackers
Unexpected code changes are reported to CWPs
33
De-Correlation
 Flight is de-correlated upon:
 FP termination
 Track drop by the tracker
 Track loss of being updated in a time period
 Manual de-correlation
 Automatic correlation of flight plan with same track is inhibited
 Tracks drops of special codes and track loss are notified
34
OPERATIONAL CONFIGURATION MANAGER (CONF)
01 Introduction
02 Sectorisation Concepts
03 Position Management
04 Determination of Relevant Sectors
35
Operational Management of the System
Introduction
 The purpose of the sectorisation concept is:

 to allow the system to determine the
controllers who are 'interested' in a flight and
the nature of their interest,
Sectorisation
thereby
 supporting the distribution of data and the
adequate processing of controller inputs
36
INDEX
01 Introduction
37
Elemental Volume (EV)
 Statically defined in the adaptation database as

a volume of airspace bounded:
Elemental  by a polygon in the horizontal plane, and
Volume (EV)
 by upper and lower flight levels or altitudes, in
the vertical plane.
38
Functional Volume (FV) (II)
Responsibility Volume(s) (AoR)
FV
Interest Volume(s) (AoI)
Internal
FV •Type Contingency
External
39
Control Conditions
 To distribute the flights among different controller teams working

on the same airspace (FV) but interested in different types of
traffic.
 Control Conditions Aerodrome Regions about departure and arrival
aerodromes.
 Control Conditions Flight Types about the flight plan type letter (Military = OAT,
Civil = GAT).
 Control Condition Airways about the name of the airway.
 Control Condition Special Areas about the name of the special area, included in
the route field of flight plan.
40
Basic Sector (BS)
 Statically defined as the combination of:

 A Functional Volume, and
 A list of control conditions
 One main and up to two auxiliary Basic Sectors can be defined over
the same FV.
 The AoR of an ATSU shall be defined as the aggregate of AoRs of
BSs allocated to that ATSU.
 The AoI of an ATSU at any time shall be the aggregate of the AoIs of
the BSs allocated to that ATSU.
41
Central Sectors (CS)
 BSs without assigned FVs, only consisting in control condition.
 The type is internal,
 They extend over the whole AoR of the local ATSU.
42
Sector (I)
 Statically defined as
 a name,
 a type (external, internal and contingency),
 for contingency and external sectors the ATSUs that can be allocated,
 up to two radio-frequencies (re-defined also dynamically).
 Dynamically defined as the combination of Basic Sectors and Central

Sectors respecting the type.
 The AoR and AoI of a sector shall be respectively the union of the
AoRs and AoIs of the BSs that are assigned to the Sector.
43
Sector (II)
Basic/Central
Sectors Sector
Combination
Voice
Frequency (1,2)
Type Type
Needs to be
Inherited from FVs Consistent
44
INDEX
01 Introduction
45
Internal Sector to CWPs
Internal Sector CWP (Executive)
CWP (Planner)
FDO (Flight Data Operator)
Repeat the process

for every Internal
Sector
•Consolidation
46
Sectorisation: Sectors to CWPs allocation
 Sector Planner and Executive roles

 The assignment of sectors roles to CWPs is dynamic.
 One sector role may only be assigned to one CWP at a time.
 All the internal Sectors that have basic or central sectors allocated
must be assigned to CWPs.
 Multi-Sector Planner: One planner for more than one Executive.
47
INDEX
01 Introduction
51
Determination of Relevant Sectors
 For each SFPL, two lists of relevant sectors are generated:
 Controlled BSs/CSs: basic/central sectors that are going to control

the flight.
 Informed BSs: basic sectors that are not going to control the flight
but they are interested in it due to one of the following reasons:
 The flight is going to enter the FV but the control responsibility

corresponds to other BS of the same FV or a CS.
 The flight is not going to enter the FV but it is going to enter the
AoI volume associated with the FV.
THE TRAJECTORY MANAGER
Trajectory Prediction
INDEX
01 Data Sources
02 Route Processing
03 Strategic Constraints
04 4D profile calculation
05 Levels Management
06 Route Modifications
07 Assigned Speed and Time Constraints
08 Holding
09 Sector Crossing
Data Sources
Track-Data Enviromental Data

ATC Flight Plan • SIDs, STARs, ATS Routes
• Route, Aircraft Type · GS, ROCD, AFL... • Letter of Agreements (LoAs)
• RFL, Speed, EOBT,… • Strategic Constraints (Level und
Speed Constraints)
• Sectorization
• Airports and RWY`s
Monitoring and
Planning Tools Weather Data
•Conformance Monitoring •Wind, Temperature, QNH
EDDF
•Medium Term Conflict Detection
•What if Probing
LKPR
OLDI Supported Aircraft Performance Data
Co-ordination (BADA)
• OLDI • 339 Aircraft Types
• Estimates and Crossing Conditions • Covers 90% of European Traffic
• Calculation based on „Total-Energy
Tactical Clearences Model“
• CFL, Heading, Holding, Direct Routing
• Speed Constraints, ROCD Contraints Airspace Availability
• Sector Crossing Conditions • CDRs, TRAs (Restricted Areas)
• ATC Constraints
55
INDEX
01 Data Sources
02 Route Processing
08 Holding
09 Sector Crossing
SID: DKB4K
Route Processing (I) SYSTEM ROUTE: DKB GUPIN TGO/N0431F350
NATOR RINLI OLBEN LUTIX/N0438F370 BENOT ++
UN869 NEMOS/N0444F390 UN869 RBT/N0434F380
 Route Validation and Expansion: DCT CAE DCT BRC DCT CSD/N0430F370 UR975
NAMIR R975 EKTAL **
(FPL-BER320S-IS RFL, TAS and link (Airway,

-B738/M-SGHIPRWXY/S DCT…) with the previous
-EDDN0705
-N0425F340 DKB UN869 TGO/N0431F350 UN869 LUTIX/N0438F370 UN869
and next route point
NEMOS/N0444F390 UN869 RBT/N0434F380 DCT CAE DCT BRC DCT
CSD/N0430F370 UR975 NAMIR R975 EKTAL
-GMAD0332 GMMX
-EET/EDGG0002 EDUU0010 LSAS0027 LFFF0041 LECM0128 GMMM0229
REG/DABKC
SEL/CEQR OPR/BER RMK/TCAS EQPD GBAS DOF/120417 RVR/200
ORGN/EDDTBERX) AoI
AoR
Validation of route field data Determination of the sequence

according to the rules laid of route points of the planned
down in ICAO DOC 4444. route.
DKB GUPIN TGO NATOR RINLI OLBEN LUTIX

BENOT NEMOS RBT CAE…
Determination of the
route segments (portion
Connection with the ADEP and within the AoI )
ADES (including SID and STAR SID: DKB4K
RWY: 010 57
assignment)
Route Processing (II)
 Assignment of Departure Procedures:
Transition
Runway + SID +
Route
 For IFR flights whose ADEP is within AoI

 The selected combination links the ADEP with the route and
is valid for the corresponding Aircraft Class and Aircraft
Operator.
 Active departure runways (Departure or Both) are
considered taking into account the schedule.
58
Route Processing (III)
 Assignment of Arrival Procedures:
Approach
STAR + + Runway
procedure
 For IFR/CVFR/VN flights whose ADES is within AoI.

 The selected combination links the route with the ADES and is
valid for the corresponding Aircraft Class and Aircraft Operator.
Schedule
Activation status Type of Operation
Optimum Arrival
Aircraft Type Type of Flight
Runway assignment
Route S TS 59
Route Processing (IV)
 Special Use Areas:

 Time to enter into TRA prior to the current time plus time parameter
→ The corresponding controller is notified.
 Otherwise → The shortest lateral TRA circumnavigation (following the
horizontal shape of the TRA) is implemented.
 If TRA is de-activated, the system will replace the lateral
circumnavigation by a DCT.
TRA
60
Route Processing (V)
 Use of Conditional Routes:
 CDRs are airway portions for which their availability is established by

predefined schedules that can be on-line modified.
 The change of a CDR status triggers the update of the affected FPs.
 Alternate routes are inserted when a filled CDR is not available. If not
alternate route is defined, a notification is provided to the controller.
61
INDEX
01 Data Sources
02 Route Processing
08 Holding
09 Sector Crossing
Strategic Constraints
 ADES
 ADEP
 SID, STAR and Route points
 TAS applicable to each route point (SID/STAR)
 Maximum RFL applicable to each route segment or point
(SID/STAR).
 Strategic level constraints (from SIDs, STARs and constraint
lines):
 At a specified level
 At or bellow specified level
 At or above specified level
Time Reference
 ATO, ATA, ATD, COP ETO, EOBT, Holding Exit time…
63
INDEX
01 Data Sources
02 Route Processing
08 Holding
4D Profile Computation (I)
 Trajectory creation:
For each route segment, a 4D trajectory (composed of
samples) is determined taking into account the following:
 Aircraft performances from EUROCONTROL BADA model is

used.
 QNH, wind and temperature data from meteorological data

model.
 Applicable constraints:
 Strategic constraints.
 Tactical constraints.
65
4D Profile Computation (II)
3D position Ground speed

Trajectory
Sample Vertical velocity
Estimated Time Heading
 This 4D trajectory is used for determination of:

 The crossing with all the defined volumes (FVs, volumes of
interest, TRAs, holding volumes, MTCD volumes, FPM volumes)
 Inbound coordination points.
 Outbound coordination points.
 Position of ToD(s) and BoD(s)
 Position of BoC(s) and ToC(s).
 Turning manoeuvre start, intermediate and final points. 66
4D Profile Computation (III)
 Using the obtained 4D trajectory, the relevant sectors are

obtained:
 Control Basic Sectors.
 Informed Basic Sectors.
 The entries into the AoR/AoI of the local and external centres.
 Only relevant trajectory samples (corresponding to entries into
basic sector, volumes, route points, manoeuvres…) are
maintained as 4D profile.
 CWPs are responsible for determining from the 4D profile if a

flight has to be presented as control or informed flight.
67
INDEX
01Data Sources
02 Route Processing
05 Levels Modifications
08 Holding
09 Sector Crossing
Levels Modifications (I)
 RFL: Requested Flight Level as derived from the filed

flight plan, possibly revised by assistant or controller
input on request of the pilot.
 ECL: En-route Cruising Level, the planned level used

within the local centre AoR.
 Based on manual input or coordination data received

from the upstream adjacent centre, or
 Automatically inserted on insufficient aircraft equipment
(e.g. non-RVSM capability), or
 Equal to the maximum RFL of the filled flight plan, if none
of the above conditions apply.
69
Levels Modifications
 ECL
Original ECL=RFL=F320
Sector N325 ECL input F360
Sector T660 ECL input F320
70
Levels Modifications (III)
 XFL (eXit Flight Level)

General rules:
 Departure: ASAP
 Arrival: ALAP
 En-route phase:
 XFL>NFL: ASAP
 XFL<NFL: ALAP
71
Levels Modifications
 XFL
Sector S660 inputs XFL F340
Sector T660 inputs XFL F380
Sector T660 inputs XFL F320
72
Levels Modifications (V)

 CFL: Cleared Flight Level, the level the aircraft is currently
authorised to climb to/descend to or maintain.
 Implemented in planned trajectory

 Implementation rules pending on flight phase
 Connection to the XFL
“Application” Menu
73
INDEX
01 Data Sources
02 Route Processing
08 Holding
Route Modifications (I)
 Heading/Track: Immediate (open and close)

and deferred (open).
 Cumulonimbus circumnavigation
 Route amendment:
 Direct routings (from current track or deferred)

 Graphical insertion of a new sequence of points.
 Textual route modification
 Offset
 Missed Approach
75
Route Modifications (II)
DCT in Label
Dynamic
Flight
LEG
Graphical
Route
Modification
76
INDEX
01 Data Sources
02 Route Processing
08 Holding
09 Sector Crossing
Assigned Speed
 Distributed to CWPs for display purposes and used

for external coordination data exchange.
 Not directly implemented in trajectory.
 Implemented through conformance monitoring
service.
78
Time Constraints
 Calculated constant CAS to achieve time constraint

provided to de ATCO.
 Additional approaches currently in development in
the SESAR context.
79
INDEX
01 Data Sources
02 Route Processing
08 Holding
09 Sector Crossing
Holding Instructions
 Holding:
 Holding input:
 holding fix,
 exit time, and
 entry and exit levels
(optional).
 The trajectory is adjusted taking
into account the entered entry and
exit conditions.
 360º:
 Implementation of a 360º
manoeuvre together, if received,
the applicable way of turning
(counterclockwise or clockwise) is
provided for display.
81
INDEX
01 Data Sources
02 Route Processing
08 Holding
09 Sector Crossing
SCM – Sector Crossing Manager
Example of an element in the Segments Sequence
AoI
Two segments
in the
Route
Turn computation
Three steps are follow to compute the TP-Leg trajectory:

First, the previous turn is finished, if any
Second, the trajectory is calculated from the last point to the target
Third, if there is a turn at the next point the start of turn is calculated
Example: TP-Leg from point 2 to point 3

Initial point: point 2, MOT
1. EOT: First sample computed
2. Calculates the samples between
EOT and next SOT, this one
included
Middle End 3. Calculates the next MOT (point 3)
Point 2
of turn of turn which is the next initial point for
the next TP_Leg
Start
MOT EOT
of turn
SOT
Point 3
Point 1 These are the points calculated for

This TP-Leg
TP – Trajectory Prediction
Integration of forward and backward computations
Intersection
Forward progression Backward progression
First ALAP constraint

Example of an element in the Maneuvers Sequence
TOC
Start Middle End

of turn of turn of turn
BOC
Example of an element in the Functional volumes Sequence
Volume 1 Volume 2 Volume 3 Volume 4

Example of an element in the Basic Sectors Sequence
Basic Sector 1 Basic Sector 2 Basic Sector 3

Example of an element in the Flight Sectors Sequence
Flight Sector 1 Flight Sector 2 Flight Sector 3 Flight Sector 4

Flight Sector 1 Flight Sector 2 Flight Sector 3
Basic sector 1 Basic sector 2 Basic sector 3 Basic sector 4
Route Route
Point 2 Point 3
SoT MoT EoT

Route
Point 1
Route
Point 3
The Flight Data Manger (FDM)
state definitions and transitions

State Definitions and Transitions
Introduction (I)
 Lifecycle of the System Flight Plan is described by a state model,

where each state represents a stage in the life of the flight.
 The state model of a flight plan is assigned in a hierarchical manner

with states defined at different layers:
 Flight Plan
 Flight Segment
 Sector
 Sector Boundary
92
State Definitions and Transitions
Introduction (II)
Flight Plan Passive Actual Supervised Alerted Terminated
Segment Pending Live Monitored Left
Under Control Not Under Control

Sector
Substate Normal Manual Hold
Boundary Not Coordinate Pre-Coordinate Proposed Coordinated Rejected Handed over
93

FDPS

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FDPS

Uploaded by

Copyright:

Available Formats

Flight Data Processing

• Flight Plan messages

Direct radars Fallback LAN

The FDPS primary tasks are:

 to manage and provide access to the flight data

FDP Logical Decomposition

ASP MET CONF

ATC Environment Configuration

FDM TM CORD SSRM CORR

MTCM FPM AGDL

ATC Tools Interoperability

Initial Flight Plan Processing

Flight Plan Data Sources

Adjacent Air AFTN

ATS messages, Coordination, System Tracks, Aeronautical Info, AFTN / AMHS

System < Inputs

Flight Plan Information

 SFPL (System Flight Plan)

 Internal unique identifier for internal unequivocal

Flight Plan creation

SFPM RTE CSTM TP SCM COO SSRM

Flight Plan Messages

 PSSR Code (Present SSR code):

 ASSR Code (Assigned SSR code) :

SSR Code Management (I)

 SSR code classification defined in adaptation data

 Organised into pools according to the ORCAM allotment plan

Classes Assignable Non-assignable

Subclasses Automatically Assignable Manually Assignable

SSR Code Management (II)

SSR Code Retention

 Code assigned by upstream  PSSR

SSR Code Assignment

 Departing Flights or Flights with PSSR No Retainable:

 System automatically assigns a code to the flight

 Code Assignment Priority:

 Code assignment reviewed upon FP route modifications:

SSR Code Release

Event Release code

• Surveillance track drop,

• Unexpected code change

 Associate surveillance data representing a track with a system flight

 Several surveillances data trackers can provide track data to FDP

 Correlation will take into account potential switching of tracker

 Correlation function can have instances on remote sites (e.g:

 Ensure correlation function using local trackers when connection to

 Correlation of eligible FPs is sought every track update cycle

 Candidate tracks are selected from expectation volumes

 Correlation warnings for uncorrelated eligible flights after defined time

 Solve correlation for flight plans with ambiguity indications

 Correlate a track with a flight plan where automatic correlation

 Create an abbreviated flight when requested flight plan doesn't

Correlation Maintenance (I)

 Correlation is maintained upon:

 Track code change to a special code

 Track squawks ASSR code

 Track becoming a primary surveillance radar track

Correlation Maintenance (II)

 Correlation is maintained upon:

 Unexpected code changes when:

 Switching between tracker changes:

 Between ARTAS trackers

Unexpected code changes are reported to CWPs