110 likes | 207 Views
Ground System implication for ASAS implementation. Pre par ed by Patrick Souchu STNA/3E p atrick.souchu@aviation - civile.gouv.fr. Agenda. ADS-B Package 1 G round S urveillance A pplication A irborne Surveillance Application ATSAW : PO-ASAS level 1 application
E N D
Ground System implication for ASAS implementation Prepared by Patrick Souchu STNA/3E patrick.souchu@aviation-civile.gouv.fr
Agenda • ADS-B Package 1 • Ground Surveillance Application • Airborne Surveillance Application • ATSAW : PO-ASAS level 1 application • ASAS : PO-ASAS level 2 application • Sequencing and merging application • Global architecture • Arrival and departure manager • FDPS • HMI • Data-link CPDLC • ADS-B network • Training tools • Recording • Preliminary conclusion ASAS-TN
ADS-B package 1 GSA • Non radar area surveillance • Ground ADS-B station • Should not be very expensive compared to a radar • Installation cost can be the most significant (e.g. access road) • Controller HMI • Not really different from radar surveillance • Airport surface surveillance • Complement an existing SMGCS • Enable SMGCS on medium or small airport • Complement radar surveillance • Integration with Mode S radar stations • Additional ADS-B infrastructure ASAS-TN
ADS-B package 1 ASA • ATSAW • A priori no impact on ground ATM system • If no difference in operational procedure • ASA • In trail procedures • Oceanic environment • Passing and Crossing application • Difficult to assess real impact on ATM system and responsibility sharing between pilot and controller • Sequencing and merging • Co-Space demonstration • Potential benefit for extended terminal area • Operational concept to be further defined • preliminary impact assessment on ground system ASAS-TN
Sequencing and merging application • Arrival and departure manager • Takes into account aircraft capability • Provides the controller with a proposed sequence and prepares instruction for sequencing • Time or distance separation • Impact on trajectory prediction • FDPS • Aircraft capability indicated in flight plan ? • Trajectory prediction ASAS-TN
Sequencing and merging application • Controller HMI • Display of aircraft capabilities • ADS-B out for target aircraft • ASAS capability for trailer aircraft • Display of linked aircraft • Designation of target and trailer aircraft • Allocation of a separation • Integrated with arrival departure manager specific function • Monitoring of separation • Appropriate new warning tools • Between MTCD and STCA • Recovery function • Termination of the ASAS separation ASAS-TN
Sequencing and merging application • Need for data-link • Enhanced CPDLC is probably the best solution to give sequencing and merging clearance • Unambiguous identification of aircraft • Easy integration of data into airborne systems • Ensure consistency between air and ground views • Need for new messages to be defined by ICAO • Enhance ATN CPDLC communication stack • Upgrade of communication systems (eg Air server) • Additional CPDLC functions in controller HMI ASAS-TN
Sequencing and merging application • ADS-B network • Reception of ADS-B data on ground is needed • Confidence in ADS-B current capabilities of each aircraft • Improvement of radar surveillance with ADS-B may be necessary • Specific ADS-B ground stations or • Enhancement of Mode S radar capabilities • Omni directional 1090 MHz reception capabilities • Enhance radar tracking with ADS-B • Integrity monitoring with radar data • Combination of ADS-B and radar for enhanced tracking • ARTAS • Radar networks impact ASAS-TN
Sequencing and merging application • Other tools • Training simulator • All previous capabilities must be available in controller training tools • Pseudo pilot new tool to manage sequencing • Simulation of new trajectories • Monitoring of ADS-B ground stations • Recording • ADS-B data • Sequencing and merging specific events ASAS-TN
Conclusion • A very preliminary analysis • new concept and new procedures always impact the ATM system • Too early for any Cost assessment • Safety implications • Is a unique data-link sufficient ? • Development level of ATS system supporting ASAS • Transition to be considered • Need for TIS-B • Transition accommodation feasibility with TIS-B ? • ASAS capabilities to be integrated in ATS system development plan • Implementation timescale is difficult to assess ASAS-TN
Conclusion • From ASAS spacing to ASAS separation • Spacing is supposed not to change task responsibility sharing and separation minima • ASAS separation will impact both • Controller tasks to be defined • Strategic air traffic management • Monitoring • Airborne separation minima to be defined • Fixed or dynamic • Coordinated with ground ATM ? • Recovery procedures and tools • Spacing is a huge step, separation will be even bigger ASAS-TN