• DPR: All systems that process flight and surveillance data.
• Main Subsystems:
• SDPS: Surveillance Data Processing System
• FDPS: Flight Data Processing System

Data must be:

• Unambiguous: Clear, one meaning
• Accurate: Reflects real-world values
• Error-free: Validated and verified
• Timely: Delivered when needed

• Controlled airspace must be covered by at least 2 sensors.
• Coverage diagrams consider terrain and sensor location.

• Detects aircraft via reflected RF pulses.
• Azimuth bias is a major source of error.
• Dwell time: Time radar beam spends on target.

1. Analog → Digital conversion
2. Correlation (moving target?)
3. Generate Plot Message:

• Timestamp
• ID
• Azimuth & Range
• SSR info (Mode A = code, Mode C = flight level)

• Mono Radar Tracking: From one radar source
• Radar Track: Aircraft trajectory from sequence of plots
• Track Message includes:
• Timestamp
• ID
• Position
• SSR info
• Predicted position
• Speed vector
• Quality Factor (QF)

• Initiate: Create new track from unassociated plots
• Update: Refine prediction window
• Terminate: QF drops to 0 or missed detections

• Radar uses Polar (Range, Azimuth)
• Converted to Cartesian (x, y) for processing

• MOSAIC: Select best radar per segment
• Track Weighting: Use QF to calculate position
• True MRT: Uses multiple parameters (distance, accuracy, QF)

• Reduces blind spots
• Improves detection probability
• Enhances accuracy and continuity

• Eurocontrol tracker system
• Combines up to 48 input sources
• Features:
• False plot filtering
• Accuracy estimation
• Target type identification

• Converts and filters ASTERIX data
• Ensures safe distribution of surveillance data
• Performs static and dynamic filtering

• All Purpose Structured Eurocontrol Surveillance Information Exchange
• EUROCONTROL standard for surveillance data
• 256 categories:
• 000–127: Civil/military
• 128–240: Special military
• 241–255: Non-standard
• ASTERIX ensures that surveillance data from different sources (radars, trackers, sensors) can be shared and interpreted consistently across various systems and countries.

• Store, process, distribute, and update flight plans
• PMain output : electronic strips and code/callsign corelation

• ICAO
• ADEXP

• Match track with FPL using SSR code or call sign
• Mode-S uses aircraft ID
• SSR Code Management:
• CCAMS : A centralized system that dynamically assigns unique SSR codes across Europe to avoid duplication between regions.
• ORCAM : Assigns SSR codes based on the aircraft’s region of origin, but may cause duplication when flights cross into other regions.
• E-ORCAM : An enhanced version of ORCAM
• MODE-S : Uses the aircraft’s unique ICAO address for direct identification, reducing reliance on SSR codes.

• Manual (phone)
• Automatic via OLDI messages:
• ABI, ACT, PAC, REV, MAC
• Each message acknowledged by LAM

• Meteo, Airlines, Airports, NMOC, CWP, Adjacent Centers

• STCA: Short Term Conflict Alert
• APW: Area Proximity Warning
• MSAW: Minimum Safe Altitude Warning
• APM: Approach Path Monitoring

• ACAS II / TCAS II: Collision avoidance system

• MTCD: Medium Term Conflict Detection (20 min ahead)
• A-SMGCS: Surface Movement Guidance (SAMAX in Skyguide)
• AMAN: Arrival Manager
• DMAN: Departure Manager

• Hot standby systems
• Backup systems in separate locations
• Example: MRTS as ARTAS backup in case of emergency

• Multiple virtual instances on one server
• Benefits: Cost, scalability, recovery
• Challenges: Latency, security, compliance

• Remote CWP concept
• Decouples controller position from physical infrastructure

• Record:
• Voice communication
• Surveillance data
• Radar display info
• Retention: At least 30 days

• Active: Data replay from system
• Passive: Video capture from CWP

• SESAR, Coflight, iTEC
• Multisensor Tracking
• SWIM: System Wide Information Management
• AI & Predictive Analytics
• Remote/Digital Towers