Aucun titre de diapositive

1
SRC
2
Safety Regulation Commission

• EIGHTH MEETING
• Brussels, 30 May, 2000

3
Agenda Item 1 -Welcome Approval of draft agenda
WP SRC8.1
4
Agenda Item 2 -Minutes of SRC7 Review of
Actions
WP SRC8.2
5
Agenda Item 3 -Revised SRC Work Programme
WP SRC8.3
6
SRC WORK PROGRAMME

• SRC7 amendments incorporated
• Further changes - clarification of
  work-breakdown for Safety data
  handling/analysis
• Definition of EATMP Interfaces
• Appendix - allocation of tasks - regulatory
  urgency
• Task descriptions reviewed
• Time scales resources to be included

7
RECOMMENDATIONS

• The SRC is invited to -
• note the current state of progress on development
  of the SRC Work Programme document
• approve the changes incorporated into Version 1.1
  in order that the Work Programme document may be
  kept fully up-to-date.

8
Agenda Item 4 -SRU Staffing

9
Agenda Item 5 -Safety Measurement Improvement
WP SRC8.4 ESARR2 Implementation
10
Agenda Item 5 -Safety Measurement Improvement
Safety Data Collection Process
11
OBJECTIVES

• To monitor safety levels and trends in ATM

• To improve overall aviation safety

• To assess and monitor changes in ATM

12
1-ATM Safety Levels and Trends
2-Safety Improvement Measures
3- Assessment, monitoring and approval of
Changes in ATM
13
SAFETY MEASUREMENT
14
SAFETY MONITORING
15
SAFETY IMPROVEMENT
16
RECOMMENDATIONS

• SRC8 to contribute name of national experts to a
  joint SRC/SAFETY GROUP Drafting Group tasked with
  the development of a safety data collection
  scheme between States and EUROCONTROL (by no
  later than June, 15th, 2000)
• ...

17
Agenda Item 5 - Safety Measurement Improvement
Input to PRC
18
SRC INPUTS TO PRC

• Formal SRC input to PRC
• PRR 3 does not include the SRC input as such-
• PRR3 Safety sections developed by PRC/PRU
• PRR3 Safety sections commented by SRU
• Timing difficulties to be resolved-
• States provide safety summaries (AST) by end of
  March
• Analysis not complete for previous year
• End of March deadline not met
• SRU develops draft SRC input in April
• SRC reviews draft SRC input by early May
• PRC develops PRR draft safety sections in March

19
RESULTS OF THE FIRST SURVEY

• Proposal for inclusion in PRR3, already
  circulated and approved by SRC
• The collection of the safety data is an ongoing
  process and further refinements should be
  available in late 2000. These effects will be
  an unavoidable part of any annual summary report
• The feasibility of populating reliable safety
  indicators at a European level is also dependent
  upon the implementation of a no-blame culture
  across Europe, encouraging comprehensive
  reporting.

20
RESULTS OF THE PUBLIC REVIEW

• Proposal for inclusion in PRR3, already
  circulated and approved by SRC
• The review of public sources will be updated as
  long as SRC believes the annual national survey
  to provide too limited and inconsistent results

21
RESULTS OF THE PUBLIC REVIEW
22
CONCLUSIONS
?States do not meet the ICAO recommendations for
occurrence reporting as specified in Annex 13,
even though they have not filed deviations from
Annex 13 . ?No firm conclusions on ATM safety
levels for 1999 could be drawn from the user
community source ?Looking at the AIRPROXs filed
by IATA airlines, and even given due
considerations to the slightly higher number of
airline shaving contributed data to IATA, an
increase in AIRPROXs can be identified since 1997.
23
RECOMMENDATIONS-1
?States should be requested to report to ICAO as
per Annex 13. ?Airlines are encouraged to fill
in the field location in the BASIS system ?BA
and EUROCONTROL are encouraged to draw an action
plan towards the use of compatible ATM taxonomies
in their reporting schemes ./.
24
RECOMMENDATIONS-2

• Action should be taken to encourage airline staff
  to report more categories of safety occurrences,
  which are potentially ATM related, such as runway
  incursions.
• Increases in reported absolute figures for
  AIRPROXs shall be monitored at both ECAC and
  national levels, associated causes identified and
  remedial actions developed and implemented

25
SAFETY DATA FROMECAC STATES

• 19 ECAC States and one multinational ATS service
  provider contributed data to EUROCONTROL within
  the 1999 Annual Summary review, compared to 14
  responses for 1998
• The increased number of responses has inevitably
  meant that absolute figures for 1999 are higher
  than those for 1998. It has therefore been
  necessary to find a meaningful basis for
  comparison between the two years
• Accordingly, it was decided to normalise the
  absolute figures for ATM related incidents with
  respect to the total number of movements, and to
  the total number of flight hours, for both 1998
  and 1999

26
ESARR 2 IMPLEMENTATION
27
ACCIDENT REPORTING

• The EUROCONTROL Survey captured 409 accidents, of
  which 50 were fatal, but these also included VFR
  non-commercial flights
• Out of total accidents reported in the Annual
  Summaries for 1999, only 1 accident, not fatal,
  was identified as having an ATM contribution

28
ACCIDENT CATEGORISATION
29
ATM RELATED INCIDENTS
30
Normalised Aggregated Safety Data - ECAC wide 99
versus 98 1
AIRPROXs
31
Normalised Aggregated Safety Data - ECAC wide 99
versus 98 2
Near CFIT
32
Normalised Aggregated Safety Data - ECAC wide 99
versus 98 2
RWY Incursions
33
CATEGORISATION OF INCIDENTS REPORTED

• The data for further classification e.g. by Class
  of airspace, Phase of Flight, Type of Operations
  and Severity, is not of sufficient quality to be
  presented
• Other type of Incidents Include ATC Sector
  Overloads, STCA Alerts, potential CFIT due to
  ILS/GS malfunctioning, wake turbulence, sighting
  weather balloons, GPWS Activation, etc.

34
CONCLUSIONS-1

• ?An increasing but still partial coverage of the
  ECAC area has been achieved .
• ?Only a limited number of specific ATM
  occurrences are generally declared as being
  reported
• ?The absolute figures of AIRPROXs reported have
  increased, but have decreased when normalised
  with number of movements and flight hour duration
• ?The absolute figures and the normalised figures
  for Near CFITs have decreased in 1999 in
  comparison with 1998

35
CONCLUSIONS-2

• ? There is a slight increase in absolute and in
  normalised figures for RWY Incursions in 1999 in
  comparison with 1998
• ? From the information made available by the ECAC
  States, it is not possible to form a
  statistically meaningful picture of safety
  performance in the ECAC Area
• ? No Safety Trends can be identified yet

36
RECOMMENDATIONS

• ?States are requested to urgently implement ESARR
  2 and related guidance
• ?EUROCONTROL is requested to monitor the
  implementation of the Safety Improvement and
  Measurement programme
• ?States are requested to implement a no-blame
  culture across Europe, encouraging reporting
• ?The EUROCONTROL Agency is requested to implement
  these provisions in respect of the operational
  ATM services it provides

37
REMINDER
Complete report of the Performance Review
CommissionPRR3 can be found on the web-site
http//www.eurocontrol.be/dgs/prc/en/index.html
Chapter 5 - dealing with Safety

38
Agenda Item 5 -Safety Measurement Improvement
AST Template UPDATE
39
Problems encountered during the first year of AST
completion 1
Problems with monochrome version - difficult to
read and impossible to photocopy

• Possible solutions
• To distribute an electronic version now
  available on the web site too
• Printed on a black white printer still looking
  fine
• Instead of photocopying pages better to print new
  ones
• When photocopying, use the original to read the
  guidance material

40
Problems encountered during the first year of AST
completion 2
The period given for incident classification
being short, many investigations and analyses are
not yet complete

• Possible solutions
• AST is seeking data only from those completed
  investigations
• The AST gathering exercise could be rescheduled
  at the end of the year
• In the next year AST could be indicated those
  safety occurrences for the earlier years

41
Problems encountered during the first year of AST
completion 3
When completing AST for 1999 HEIDI was in draft
and not widely circulated

• Possible solutions
• HEIDI status is presently released 1.0 (SAF11)
• HEIDI EUROCONTROL widely circulated
• HEIDI is now available on the web

42
Problems encountered during the first year of AST
completion 4
ESARR2 Phases are not included in detail

• Possible solutions
• Foot note indication on where ESARR2 Phases are
  described
• AST published on the web near to ESARR2
• Direct inclusion in the AST and GUI of the ESARR2
  phases details

43
Problems encountered during the first year of AST
completion 5
Difficulties in gathering traffic volume
figures, and for Flight hours duration, ACAS
reports etc

• Possible solutions
• IFR Commercial traffic volume and flight hours
  duration could be collected from CFMU
• No availability of VFR traffic at EUROCONTROL
  level
• Safety Data Flow/Data Collection Process to be
  agreed

44
Problems encountered during the first year of AST
completion 6
Some States experienced difficulties with the
Severity Classification Scheme

• Possible solutions
• Severity Classification Scheme is a companion
  document to ESARR2 adopted by PC
• To map severity schemes applied by different
  States with the EUROCONTROL one
• Workshop with States to explain the AST and its
  content

45
Problems encountered during the first year of AST
completion 7
Difficulties introduced by the definition of RWY
incursion ...

• Possible solutions
• The clarify definition of RWY incursion with its
  possible sub-classification
• RWY incursion where avoiding action was necessary
• NO avoiding action was necessary

46
Problems encountered during the first year of AST
completion 8
Difficulties introduced by the existence of two
similar categories, i.e. a/c deviation from ATM
applicable procedures and a/c deviation from
applicable published ATM procedures

• Possible solutions
• To be kept only a/c deviation from applicable
  published ATM procedures
• To amend ESARR2, AST and GUI
• HEIDI Taxonomy already amended

47
Problems encountered during the first year of AST
completion 9
The category of incidents unauthorised
penetration of airspace may be considered
sub-part of the category aircraft deviation
from published ATM applicable procedure/regulatio
n

• Clarification
• To be kept separate seeing the number of
  unauthorised penetration of airspacereported
  separately
• Might be sub-classified in HEIDI for retrieval
  purposes

48
Problems encountered during the first year of AST
completion 10
Difficulties by misunderstanding what to report
on the item Total number of accidents..

• Clarification
• By Total No of accidents we mean TOTAL including
  those non-ATM related
• Using the sub-classification we then collect
  those with ATM contribution (direct or indirect)

49
Problems encountered during the first year of AST
completion 11
The shopping list of the AST does not provide
any indication for accidents which are not CFIT
or collisions, but which may however occur

• Possible solutions
• The above mentioned accidents could be recorded
  under a new item Other type if so wish
• Could stay under Total no. without being
  discriminated, taken the total amount of such
  accidents
• The ATM contribution still possible to be recorded

50
Problems encountered during the first year of AST
completion 12
The AST should be limited only to ATC maters

• Clarification
• If so wish the ATM contribution to aviation
  safety cannot be detected or measured
• AST should not be limited to ATC maters in order
  to produce quantitative safety objectives

51
Problems encountered during the first year of AST
completion 13
Presently there is no sub-classification of ACAS
reports to discriminate between TA and RA

• Possible solution
• If so wish the AST could be updated, but already
  exists requirements to reduce the number of items
  to be reported to SRC/SRU

52
Data Quality Problems encountered during the
first year of AST completion 1

• Not always understood what GAT, OAT, GA,etc.
  means
• Not always used the sub-classifications
• Flight Rules
• Type of flight
• Type of operations
• Phase of flight
• Class of airspace
• Confusions on how the pages should be filled in
• etc..

53
PROPOSALS to Solve the Remaining Issues

• ACTIONS
• To re-issue refined GUI and AST
• To maintain direct contacts with focal points
• To extend if possible the data base with focal
  points presently missing
• To organise a meeting with all focal point

54
QUESTIONS ?
55
Agenda Item 6 - ATM Safety Minima
WP SRC8.6
56
REMINDER

• SRC TORs include the task to-
• define target levels of safety, standards of
  safety performance
• SRC 7 agreed that overall quantitative ATM
  overall safety minima would be provided at ECAC
  level and that further quantitative refinement be
  undertaken at national level (Decision 7/8/6)

57
ATM Safety Minima

• Maximum ATM direct contribution to accidents of
  Commercial Air Transport aircraft in the ECAC
  region
• Rationale SRC/Study DOC OO1
• SAFETY MINIMA STUDY
• Review Of Existing
• Standards Practices

58
RATIONALE/LIMITATIONS

• Historical and geographical baseline-
• ICAO ADREP
• CFMU statistics
• ECAC region
• Commercial Air Transport
• 1988-1999
• Projection-
• Traffic growth 6,7
• Period till 2010

59
ATM Safety Minima

• Probabilities of ATM contributing directly to an
  accident of a Commercial Air Transport aircraft
  in the ECAC region
• 2, 5 10 -8 accidents per flight hour
• 3,5 10-8 accidents per movement
• WITH traceability of assumptions and limitations-
  Monitoring/re-validation on a regular basis for
  potential revision of the ATM safety Minima

60
RECOMMENDATIONS

• SRC8 to-
• reaffirm the need to establish ATM target levels
  of safety
• approve the contents of Attachment 1 of WP SRC
  8.6 as a basis for defining quantified ATM safety
  minima
• approve the development of an ESARR along the
  aligns presented above

61
Agenda Item 7 - ESARR Development

62
ESARR 2

• Agreement on military application
• New version (1.1) to the Provisional Council
  Commission
• Distribution after approval
• Action Support Implementation

63
ESARR 3

• Two rounds of EUROCONTROL Consultation (ending
  early June)
• Assessment of Means of Compliance as issue
• Next step to Provisional Council / Commission for
  approval
• Further implementation actions

64
ESARR 4

• Second SRC-wide Consultation
• Comments indicate - Principles secure - Some
  detailed issues to address - Some ESARR-wide
  issues
• RTF meeting - then a further version

65
ESARR 5

• Two rounds of SRC/HRT Consultation
• EUROCONTROL consultation, except
• Military views not available until late June
• Thereafter to Provisional Council
• ATS Services Personnel Workgroup

66
ESARR 6

• WG review of inputs to form the basis of ESARR
  development
• WG activity to now continue

ESARR 7

• GAASR input a basis for ESARR, but
• Significant re-work and review under way

67
RECOMMENDATIONS

• SRC are asked to -
• note the progress report covering the development
  of requirements for ATM Safety Regulations in
  EUROCONTROL
• agree the future direction of requirements work
  as indicated through the next steps identified
• to undertake the SRC actions where identified
  inthe paper.

68
Agenda Item 7 - ESARR Development
SRC8 - Flimsy 1 ESARR - Acceptable Means of
Compliance
69
ESARR - ACCEPTABLE MEANS OF COMPLIANCE

• SRC can define acceptable means of
  compliance for ESARRs including them into the
  requirements structure

70
ESARR - ACCEPTABLE MEANS OF COMPLIANCE
ESARR Template
Section 5 - Safety Requirement
Section 8 - Additional Material
Acceptable Means of Compliance
Guidance Material
Other Material
71
ESARR - ACCEPTABLE MEANS OF COMPLIANCE

• Correspondence between proposed means of
  compliance and ESARRs has to be specifically
  addressed in each case
• Proposed means of compliance could cover all
  requirements or only part of them

72
ESARR - ACCEPTABLE MEANS OF COMPLIANCE

• Identification of requirements effectively
  covered by each proposed approach

• Section 5 - Safety Requirement
• ...

Proposed Means of Compliance
REVIEW
REVIEW
Identified Acceptable Means to Compliance
73
ESARR - ACCEPTABLE MEANS OF COMPLIANCE

• Before including proposed approaches as
  acceptable means of compliance

TO REVIEW CORRESPONDENCE BETWEEN THEM AND EACH
ONE OF THE MANDATORY PROVISIONS INCLUDED IN
SECTION 5
TO REFER THE PROPOSED APPROACHES AS GUIDANCE
MATERIAL UNTIL REACHING CONCLUSIONS ON THE
REQUIREMENTS COVERED
74
ESARR - ACCEPTABLE MEANS OF COMPLIANCE
ESARR Template
Section 5 - Safety Requirement
Section 8 - Additional Material
Acceptable Means of Compliance
Guidance Material
Other Material
75
RECOMMENDATIONS

• SRC8 is invited to
• Consider the need to address correspondence
  between ESARRs and proposed means of compliance
  before deciding their inclusion as identified
  acceptable means of compliance

76
RECOMMENDATIONS

• SRC8 is invited to
• Endorse modifications in current drafts for ESARR
  3, 4 and 5 in order to allocate the already
  proposed means of compliance as guidance
  material, until reaching a conclusion of the
  requirements covered by each proposed approach

77
Agenda Item 7 - ESARR Development
WP SRC8.8 ESARR 3 - Guidance Material
78
ESARR 3 GUIDANCE MATERIALIntroduction

• Not much information can be found to guide an
  adaptation process of regulatory organisations to
  the new scenario
• Guidance Material may provide support to ATM
  safety regulators

79
ESARR 3 GUIDANCE MATERIALDevelopment

• Update of initial drafts second version
• Information about needs for guidance has been
  obtained from different sources
• Distribution to SRC for comment is expected
  after SRC8

80
ESARR 3 GUIDANCE MATERIALContent - Initially
Identified Aspects

• New regulatory approach in association with the
  SMS operated by providers
• Specific regulatory processes
• Organisational aspects
• Adoption of a risk-based approach
• Partnership with ATM service-providers
• Explanatory material to illustrate requirements

81
ESARR 3 GUIDANCE MATERIALContent - Additional
Identified Aspects

• Applicability and scope of ESARR 3
• Acceptable Means of Compliance
• Relation between SMS and QMS

82
ESARR 3 GUIDANCE MATERIALContent - Top-Down
Approach
Re-examining roles and responsibilities for
Regulator and Providers

• Focussing regulation on Safety Management
  Systems
• Adopting a risk-based approach
• Partnership with providers as an essential factor

REGULATORYPOLICY
REGULATIONS
REGULATORY PROCESSES
Organisational issues
83
ESARR 3 GUIDANCE MATERIALRegulatory Processes

• Focus on processes rather that products

ACCEPTANCE OF SAFETY MANAGEMENT SYSTEMS
OVERSIGHT OF SAFETY MANAGEMENT SYSTEMS
ACCEPTANCE OF NEW SYSTEMS AND SIGNIFICANT CHANGES
84
ESARR 3 GUIDANCE MATERIALThree Regulatory
Processes
REGULATOR
PROVIDER
ACCEPTANCE OF SAFETY MANAGEMENT SYSTEMS
THE PROVIDER DEFINES AND IMPLEMENTS ITS SMS
REGULATION
REGULATORY OVERSIGHT OF SMS
THE PROVIDER OPERATES ITS SMS
REGULATION
ACCEPTANCE OF NEW SYSTEMS AND SIGNIFICANT CHANGES
85
ESARR 3 GUIDANCE MATERIALRegulatory Processes
REGULATORY OVERSIGHT OF SAFETY MANAGEMENT SYSTEMS
ACCEPTANCE OF NEW SYSTEMS AND SIGNIFICANT CHANGES
Significant Change
Steady State
ROUTINE OPERATIONS
PROJECTS MODIFICATIONS NEW DEVELOPMENTS
ATM SERVICE-PROVIDER OPERATION
86
ESARR 3 GUIDANCE MATERIALProcesses - Acceptance
of SMS
Regulator
Provider
Safety Policy Level

• Define senior managers safety responsibilities
• Define safety policy and management principles

ACCEPTANCE
AND
Safety Implementation Level

• Start safety management training programmes
• Implement a set of procedures including
  surveys/auditing
• Implement other different procedures
• Issue 1st edition of a safety management manual

• Start safety management training programmes
• Implement a set of procedures including
  surveys/auditing
• Implement other different procedures
• Issue 1st edition of a safety management manual

• Implement a set of procedures including lesson
  dissemination
• and internal investigation of occurrences
• Issue edition of the safety management manual

• Implement a set of procedures including lesson
  dissemination
• and internal investigation of occurrences
• Issue edition of the safety management manual

• Implement procedures for risk assessment and
  mitigation
• Issue edition of the safety management manual

• Implement procedures for risk assessment and
  mitigation
• Issue edition of the safety management manual

Formal Acceptance of the Implemented SMS
87
ESARR 3 GUIDANCE MATERIALProcesses - Acceptance
of significant changes
PROVIDER
PROJECT
REQUIREMENTS DETERMINATION
DESIGN AND DEVELOPMENT
INSTALLATION AND TRANSITION
OPERATION
RISK ASSESSMENT AND MITIGATION ACTIVITIES
RISK ASSESSMENT AND MITIGATION DOCUMENTATION
Risk Assessment and Mitigation Deliverables
Risk Assessment and Mitigation Deliverables
Risk Assessment and Mitigation Deliverables
REGULATOR
FORMAL ACCEPTANCE
FOLLOW UP OF THE RISK ASSESSMENT AND MITIGATION
DOCUMENTATION
88
ESARR 3 GUIDANCE MATERIALRegulatory Processes
Regulatory Policy
Regulations
Regulatory Processes
ACCEPTANCE OF SAFETY MANAGEMENT SYSTEMS
OVERSIGHT OF SAFETY MANAGEMENT SYSTEMS
ACCEPTANCE OF NEW SYSTEMS AND SIGNIFICANT CHANGES
89
RECOMMENDATIONS

• SRC8 to note the status of guidance material
  developed to support ESARR 3
• After its next distribution to SRC, provide
  comment and review by the date to be specified

90
Agenda Item 7 - ESARR Development
WP SRC8.9 ESARR 3 - Proposed Issue
91
ESARR 3 - PROPOSED ISSUE

• SRC 6 approved ESARR 3 (Edition0.1) for its
  subsequent consultation
• Extensive consultation activities
• The current version is a mature document and a
  Proposed Issue can be considered to be presented
  for PC approval

92
ESARR 3 - CONSULTATION
8 JUNE
MID DECEMBER
MID MARCH
MID APRIL
EUROCONTROL Consultation
SRC Review by Correspondence
EUROCONTROL Consultation
ESARR 3 Edition 0.1
FINAL VERSION
ESARR 3 Edition 0.2
ESARR 3 Edition 0.21
SRC6
PC
93
ESARR 3 - PROPOSED ISSUE

• ESARR 3 is expected to reach sufficient
  maturity to be submitted for approval at the next
  PC meeting

94
ESARR 3 - PROPOSED ISSUEDraft of SRC Proposal

• Safety Management Systems in ATM
• EUROCONTROL Work on SMS
• ESARR 3
• Development and Consultation Process
• Implementation Considerations
• Recommendation

95
RECOMMENDATIONS

• SRC8 is invited to
• Note the current status of ESARR 3
• Approve its presentation to the PC and
  EUROCONTROL Commission for their approval and
  endorsement
• Consider the draft SRC proposal to be submitted
  to the PC at its next meeting

96
Agenda Item 7 - ESARR Development

97
Agenda Item 8 - EATMP Issues
WP SRC8.11 GNSS
98
GNSS UPDATE

• EGNOS Design Safety Case
• Second Issue received in April
• Review Process goes on
• Comments have been requested from SRC
• A consolidated response would be sent out from
  SRU to SRC Members for validation

99
GNSS UPDATE

• Survey on GNSS use in ATM Operations
• 10 States provided information - Results
• GNSS widely used in en-route ATM operations
• TMA and NPA are the most considered areas of use
• No short-term planning seems to exist around
  precision approach/surface operations

100
CONCLUSIONS

• SRC8 is invited to
• Note the current status of activities concerning
  GNSS
• Continue SRC review of EGNOS Design Safety
  Case

101
Agenda Item 8 - EATMP Issues
RVSM Safety Planning
102
Agenda Item 9 - High Level Group
WP SRC8.12 Feedback
103
SRC INPUT TO EU HIGH LEVEL GROUP

• Measures for a Single European Sky
• Regulatory Framework Subgroup
• SRC Input accepted with additional support
• Action SRC to note

104
Agenda Item 10 - RelationshipRegulator /
Service Provider

105
Agenda Item 11 - SRC Monitoring Function

106
SRC/SRU TORs

• SRC shall
• establish procedures, where necessary, for the
  uniform national application of European ATM
  safety regulatory requirements for adoption by
  the Commission through the Provisional Council
• SRU shall
• ...
• prepare and monitor the implementation of
  procedures for ensuring the uniform application,
  by States, of safety regulatory requirements

107
Agenda Item 12 - Web site Developments

108
Agenda Item 13 - Any Other Business

109
Agenda Item 13 - Any Other Business
ESARR 2 Implementation Workshops
110
REMINDER
ESARR 2 Implementation Workshops - 2000
1st June 2728 Copenhagen 2nd
September 2728 Brussels EUROCONTROL 3rd
October 2425 Prague 4th November 67
Brussels EUROCONTROL

111
Agenda Item 13 - Any Other Business
ANAE - Colloquium
112
SAFETY IN ATMIncreasing capacity and safety in
European High Density Traffic
REMINDER

• Date 22/23 November 2000
• Location TOULOUSE-France
• Organisation A.N.A.E
• Target Public Aviation Professionals

113
RECOMMENDATIONS

• SRC Commissioners are invited to notify SRU if
  they want to benefit from a pre-paid registration
  to the ANAE colloquiumLimit date 31 July,
  2000. (vs. Actions SRC7 mentioned limit date
  1 September, 2000)

114
Agenda Item 13 - Any Other Business
SRC Workshop
115
2nd WORKSHOP ON SAFETY REGULATION
REMINDER

• Date Wednesday, 12 July - pm, 2000
• Location EUROCONTROL - Europa
• Organisation SRU

116
Agenda Item 13 - Any Other Business

117
Agenda Item 14 - Next Meeting

118
SRC9 Tuesday 26 September 2000EUROCONTROL HQ,
CASTOR Meeting Room