Module1 1
Module1 1
Module 1:
Data Enviroment
1.1 Background
Outline
• Data Driven Approach for Safety Improvement
• Applicable Regulations
ICAO Annex 19
EU Regulation 376/2014
• Eccairs/ADREP
CAST/ICAO Common Taxonomy Team (CICTT)
History, versions, languages…
• Eccairs Structure
Architecture
Repository
Installation
© SENASA 2023
Total or partial reproduction is not allowed Module 1. 1 – 2 / 22
SMS Documentation
Safety Legal Framework SMS Requirements for Safety Oversight Internal Training,
Providers Communication and
Awareness
State Responsibility and Data Capture, Analysis and
Accountability Agreement with Providers on Exchange
Safety Performance
External Training,
Accident/Incident Investigation Communication and
Prioritisation of Safety Means
Awareness
through Safety Data
Enforcement
© SENASA 2023
Total or partial reproduction is not allowed Module 1. 1 – 3 / 22
© SENASA 2023
Total or partial reproduction is not allowed Module 1. 1 – 4 / 22
Safety Audits
Safety Surveys
© SENASA 2023
Total or partial reproduction is not allowed Module 1. 1 – 5 / 22
STANDARD OPERATION
OPERATIONAL
OCCURRENCES ACCIDENT
DEVIATIONS
© SENASA 2023
Total or partial reproduction is not allowed Module 1. 1 – 6 / 22
Applicable regulations
• Legal framework
GLOBAL REGIONAL NATIONAL
CONVERSION INTO
NATIONAL LEGISLATION
STATE LEGAL
FRAMEWORK
© SENASA 2023
Total or partial reproduction is not allowed Module 1. 1 – 7 / 22
Applicable regulations
• Annex 19. Chapter 5. Safety Data Collection, Analysis & Exchange
5.1.1. STATE MANDATORY REPORTING SYSTEM TO FACILITATE COLLECTION OF INFORMATION ON SAFETY DEFICIENCIES
5.1.2. STATE VOLUNTARY REPORTING SYSTEM TO FACILITATE COLLECTION OF INFORMATION ON SAFETY DEFICIENCIES THAT
MAY NOT BE CAPTURED BY THE MANDATORY REPORTING SYSTEM
5.2.1. STATES ESTABLISH SAFETY DATABASE TO FACILITATE ANALYSIS OF INFORMATION ON SAFETY DEFICIENCIES
5.2.2. STATES ESTABLISH A PROCESS TO MONITOR IMPLEMENTATION AND EFFECTIVENESS OF PREVENTIVE ACTIONS
5.2.3. DATABASE SYSTEMS SHOULD USE STANDARDIZED FORMATS TO FACILITATE DATA EXCHANGE (ADREP COMPATIBLE)
5.3.1. VOLUNTARY REPORTING SYSTEM SHALL BE NON-PUNITIVE AND PROTECT THE SOURCES OF THE INFORMATION
5.4.1. EXCHANGE OF DATA WITH OTHER STATES IN CASE A DEFICIENCY OF INTEREST HAS BEEN DETECTED
5.4.2. ESTABLISHMENT OF SAFETY INFORMATION SHARING NETWORKS AMONG USERS OF THE AVIATION SYSTEM
Applicable Regulations
ICAO-EU RELATIONSHIP REQUIREMENT RECOMENDATION
ACCES TO INFORMATION ECCAIRS (STATES AND NAAS Y AIBS WILL HAVE ACCESS TO STATE
OF AUTHORITIES SSP EUROPEAN REPOSITORY) DATABASE
ACCESS/USE OF THE EUROPEAN CENTRAL REPOSITORY (ECR) ACCESS NAAS Y AIBS WILL HAVE ACCESS TO STATE
INFORMATION CONDITIONS DATABASE
© SENASA 2023
Total or partial reproduction is not allowed Module 1. 1 – 9 / 22
Eccairs/ADREP
• CAST/ICAO Common Taxonomy Team (CICTT)
Was established in1999 by the Commercial Aviation Safety Team (CAST) and the
International Civil Aviation Organization (ICAO) to remove constraints on aviation safety
analysis and sharing.
Objetives:
o To develop common terms, definitions and taxonomies for aviation safety reporting systems
o Also used to describe aviation safety risks and associated contributing factors.
o Widespread adoption of these standard descriptors will significantly enhance the value of aviation
safety information by facilitating the sharing and comparison of meaningful safety information.
© SENASA 2023
Total or partial reproduction is not allowed Module 1. 1 – 10 / 22
Eccairs/ADREP
• History
1992 – 1995
o Study to evaluate de feasibility of collecting and integrating EU wide incident data.
1998
o First production version of ECCAIRS 3 (ADREP)
2000
o First draft of the Directive on Occurrence Reporting
2002
o First production version of ECCAIRS 4 (ADREP 2000)
2003
o Adoption of the Directive 2003/42/EC – 13rd June
2004
o Expected to start the analysis capability
2005
o Member states shall comply with Directive
© SENASA 2023
Total or partial reproduction is not allowed Module 1. 1 – 11 / 22
Eccairs/ADREP
• History
2006
o Data integration Network test (DINER)
2007
o Practically all Member States declared to be collecting data (most using ECCAIRS) following
Directive 2003/42/EC
2008
o 6 Member States (out of 27) were formally integrating data, following Regulation (1321/2007),
resulting a total of 25.000 occurrences in the European Central Repository
2009
o 10 Member states were formally integrating data, resulting a total of 169.000 occurences in the ECR.
2010
o Beta releases ECCAIRS 5
2011
o Available the new version of ECCAIRS, ECCAIRS 5
© SENASA 2023
Total or partial reproduction is not allowed Module 1. 1 – 12 / 22
Eccairs/ADREP
• History
2012
o First draft on the New Occurrence Reporting Regulation (376/2014)
2013-2014
o Approval of New Regulation 376/2014
o Initial development of Implementing Regulation 2015/1018 laying down a list classifying occurrences
to be mandatorily reported.
2015
o Developement of Reduced Interface Taxonomy (RIT)
o New release of ECCAIRS Common Framework and Taxonomy 3.4.0.1
o Publication of Implementing Regulation 2015/1018 laying down a list classifying occurrences to be
mandatorily reported.
o Entry into force of New Regulation 376/2014.
2019
o Last version of ECCAIRS 5 Taxonomy 4.1.0.7
© SENASA 2023
Total or partial reproduction is not allowed Module 1. 1 – 13 / 22
Eccairs/ADREP
• Versions
ECCAIRS 3:
o ECCAIRS software started with version 3.
ECCAIRS 4:
o The JRC developed the version 4.
o ECCAIRS 4 is the most developed version of ECCAIRS.
o A lot of tools were developed for this version (AWB, Dexter, DINER, Targa, WebDas…)
o ECCAIRS 4 was adopted by several countries.
ECCAIRS 5:
o ECCAIRS 5 is the newest and actual version of this software.
o Most of the countries that worked in version 4 are migrating to this new version.
o The objetive is that all the organisations that using version 4 change and migrate to the ECCAIRS 5
© SENASA 2023
Total or partial reproduction is not allowed Module 1. 1 – 14 / 22
Eccairs/ADREP
ECCAIRS Taxonomy (ICAO CICTT) is complex and hugely extensive
Tailoring is needed
OCCURRENCE CATEGORY
GROUP TYPE
(ADREP)
7 82
36
© SENASA 2023
Total or partial reproduction is not allowed Module 1. 1 – 15 / 22
Eccairs Structure
• Glosary
Database
o Location that physically stores the data
Repository
o Location containing methods, rules, security, data
Server
o System offering data and functions to other computers
Client
o System that connects to a Server
ECCAIRS Repository Server
o Location that governs access to the occurrences
ECCAIRS Client
o Workstation connecting to an ECCAIRS Repository Server
Login by User ID and Password
o Action that connects a client to a server with the given credentials
© SENASA 2023
Total or partial reproduction is not allowed Module 1. 1 – 17 / 22
Eccairs Structure
• Session
State of a user logged on to repository. Offers connection and access to database, manages
security profiles, handles other profiles from server
• Connection
Connection to repository
Not a connection to database of repository
Important notice
o Client never directly connects to database
o Client connects to repository
o Only Repository Services connect to database
• Permissions
Provide information about access to occurrence data
Set per Organisation (read, write, export, remove)
Set per Attribute (read, write, export)
© SENASA 2023
Total or partial reproduction is not allowed Module 1. 1 – 18 / 22
Eccairs Structure
• IT Structure
Server
Workstations
Server
ECCAIRS
Database
ECCAIRS
Database
© SENASA 2023
Total or partial reproduction is not allowed Module 1. 1 – 19 / 22
Architecture
• ADREP Entities and Entity Structure
Aircraft Weather rep.
+
Aerodrome Runway Prop. Failures
Recordings Precipitation
ATS Unit
Occurrence Part Failures
Sector ATM Staff
Fire suppr.
Potential Ratings
Factors
Incapacitation
Endorsement
Engine Fail.
Descriptive Explanatory
Events
Factors Factors Other Pers.
Occurrence *
Failures
Aerodrome Runway(s)
History of flight
Recordings
Airspace(s)
Meteo
Survival
Recommendations ATM Personnel
Ditch
+
Separation(s)
Air Traffic Services
Occurrence *
Flight Crew
Events
590+ attributes most of which
are pick-lists Other personnel
Notes
Failures
RecordingsRunway(s)
– Occurrence
Precipitation
Aerodrome • Class, When, Where, Events, …
• Attributes
– Aircraft
ATS Unit • Model, Make, Type, … History of flight
Occurrence
– Flight
Part Failures
– Occurrence Sector ATM
– Other Staff
• Route, IFR, Meteo, …
Flight Crew
Events
700+ attributes most of
= Notes
which are pick-lists Other personnel
Installation
© SENASA 2023
Total or partial reproduction is not allowed Module 1. 1 – 21 / 22
Any Question?
© SENASA 2023
Total or partial reproduction is not allowed Module 1. 1 – 22 / 22