1. ASAS TN Session 4 summary Billy Josefsson, LFV Rob Ruigrok, NLR

2. Session STRATEGY and IMPLEMENTATION Martine Blaize, EUROPEAN Harmonisation in ATM safety regulation Jörg Steinleitner, Package I Requirements Focus Group (“Rapid Global Harmonisation”) DISCUSSION Jonathan Hammer, Aircraft Surveillance Applications (Extracts from ASA MASPS, DO-289) Tony Henley, ASAS TN Implementation Strategy DISCUSSION

3. EUROPEAN Harmonisation in ATM safety regulation EUROCONTROL SRC aims at ensuring a harmonised ATM safety regulatory framework across ECAC “TREND” ANSP separation from Regulator Binding requirements: -Eurocontrol SRC (ESARRs) -SES (regulations) -EASA (airworthiness)

4. ATM Safety codes Airport Safety codes Airworthiness codes Flight Operations Certification codes ICAO Annex 14 and associated doc ICAO Annex 11 and associated doc ICAO Annex 8 and associated doc ICAO Annex 6 ICAO Annex 6 and associated doc Total System Approach, valid for the ASAS case

5. ASAS implementations: -difficult to meet all safety regulations -difficult to get all actors involved approved by the authorities ESARR means of compliance: -ED78A /Do264 partial -Eurocae WG 53 complete SAF ASAS document is relevant Mathematical and operational proof needed EUROPEAN Harmonisation in ATM safety regulation

6. Package I Requirements Focus Group (RFG) (“Rapid Global Harmonisation”) The RFG was established in April 2003 to perform the “Co-ordinated Requirements Determination” of Package I –Involvement of all relevant stakeholder categories. The work of the group is a very important step towards world-wide interoperability, related to both the operational procedures and the technical infrastructure of Package I. In accordance with the rationale of the definition of Package I, the RFG supports a pragmatic approach towards the early and efficient implementation of Package I. –Taking benefit of the work already performed.

7. Package I Requirements Focus Group (“Rapid Global Harmonisation”) The RFG is a joint European/US activity : –Open to additional membership (e.g. Australia, Japan) OSED, SPR and INTEROP documents will be delivered : –Target date for final versions: December 2005; –Respecting pragmatic top-down and bottom-up relationships with other Package I deliverables; –Ownership is defined at regional level and is a key issue for acceptance (e.g. EUROCAE for SPR and INTEROP, EUROCONTROL for OSED)F

8. Package I Requirements Focus Group (“Rapid Global Harmonisation”) Use of RFG deliverables by : –States (to develop operational & technical ICAO standards); –Industry (to develop e.g. EUROCAE/RTCA standards); –Regulatory Authorities (to facilitate the end-to-end approval of the Package I applications). In this respect, the RFG supports but does not replace existing standardisation bodies and processes. In serving the needs of their “customers” with good material in an efficient way, the RFG has a huge responsibility for the early implementation of ‘Package I’.

9. Fast track applications: -Non Radar and Sequencing & Merging “Do not overload the fast track” OSED Harmonisation group = RFG Urgent need for educational effort towards stakeholders about ADS-B out and synergies with mode S update. (RFG should notify IATA) Package I Requirements Focus Group (“Rapid Global Harmonisation”), Issues

10. Overview of ASA MASPS – RTCA DO-289 ASA MASPS –Aircraft Surveillance Applications (ASA) Minimum Aviation System Performance Standards (MASPS) Provides system and sub-system performance requirements that to support ASA applications –Intended to provide framework for current and future applications ASA applications considered in MASPS –Detailed analyses Enhanced Visual Acquisition (EVAcq) Enhanced Visual Approach (EVApp) Airport Surface Situational Awareness (ASSA) Final Approach and Runway Occupancy Awareness (FARAO) Conflict Detection (CD) –‘Probing’ analyses (evaluation of future requirements) Approach Spacing for Instrument Approaches (ASIA) Independent Closely Parallel Approaches (ICSPA) Airborne Conflict Management (ACM)

11. Relationship between ASA MASPS and other RTCA Documents ASAS MOPS ASA MASPS (ASA System Requirements and appendices for descriptions and performance specifications for all initial ASA applications) ADS-B MASPS TIS-B MASPS Link MOPS (1090 ES, UAT, VDL-4) Surveillance Systems Other ASA Functions ASSAPCDTI MASPS MOPS SC186 Surveillance Systems Other Surveillance Systems Other Systems SC186 Systems FIS-B Navigation TISTCAS Weather Radar Terrain & Obstacles

12. Aircraft Surveillance Applications (ASA MASPS, DO-289) issues Mainly US involvement Applications categorized (ACL): -transmit –only -basic -intermediate -advanced 1 and 2 Allows for additional applications, backwards compatibility RFG to provide harmonised input to update ASA MASPS and MOPS

13. ASAS TN Implementation Strategy ASAS-TN WP3 Recommendations –Datalink –Applications –Implementation The Way Forward –Local implementations beneficial subsets of package 1 –Progressive introduction of package 2/3

14. Local Implementations Beneficial subsets of package 1 Non Radar area surveillance (ADS-B-NRA), Airport Surveillance (ADS-B-APT), Spacing (ASPA-S&M), (On Board Situation Awareness on airport surface (ATSA-SURF)) Small numbers of aircraft high local density retrofit avionics global interoperability

15. ASAS TN Implementation strategy,issues Minimal change to ground infrastructure How to be successful without 100% equipage Retrofit avionics should be affordable, ADS B in / out No change in separation responsibility Manoeuvre ‘advisor’ computation function required onboard Manual control of manoeuvres via autopilot No changes to ACAS Funding/ incentives

16. …so… What can be done? What will be done? What is allowed to be done?