1. System Intro ECCAIRS End-User Course
Provided by the Joint Research Centre - Ispra (Italy)

2. Typical Workflow Taking a slide from a previous presentation
Initial Notification
Analysis
Recommendations
Legislation
Incident
Data entry
Investigation
Taking a slide from a previous presentation
Click. Speak about the Investigation (will blink) and the Data entry (will blink). It is a recursive process (arrow appears also)
Click. After data entry the Analysis phase can start (blink). In order to be able to do this, data must be retrieved from the database
Click. Question appears.

3. Reporting requirements in Annex 13
Initial Notifications
Preliminary reports
Data reports
ECCAIRS file (E4F)
Accidents MTOW > kg
Serious incidents MTOW> kg
AIB

4. BEA ECCAIRS users
Laboratory
+ FDR/CVR
Investigators
( + on-duty team)
All sharing the same information stored in the ECCAIRS Database
Objective : having ECCAIRS as a central tool for BEA investigations
Communication&
Report publication
WEB
Safety Analysts

5. Usage of ECCAIRS Accident Actions Database input Launch investigation
Preliminary Entry / Initial Notification
Data Entry
-facts
-technical parts
-events and factors
-recommendations
Link to database reports
Electronic ADREP reporting
Facilitation of data handling (Browser)
Enhancement of data presentation (Grapher)
Custom queries (Query builder)
Reporting and analytical tools (AWB, …)
Investigation phases
Permanent
quality
control
Safety recommendations
TIME SCALE
Final report
ADREP Report (ICAO)
Queries
Safety Studies
Statistics and Data

6. The occurrence tree
The editing window contains an occurrence tree, sections and attributes
The occurrence tree contains topics which depend on the selected view
Customization of user interface is recommended!

7. Preliminary View General Weather Conditions Administrative data Where
When
Severity
Events & Phases
Narrative

8. What kind of other information to collect ?
If the WEATHER was relevant, enter
Details on meteorological conditions
If there were INJURIES to persons
Complete the injury details
If the occurrence involved an AERODROME, enter
Aerodrome data
If the occurrence involved a RUNWAY, enter
Runway data
If the occurrence involved a RUNWAY EXCURSION, enter
Position where aircraft came to rest in relation to the runway used
If the occurrence involved an AIRPROX or SEPARATION issues
Provide basic data on all aircraft involved
Complete separation page with the details at hand (e.g. TCAS information)
If the occurrence involved EVACUATIONS
Provide evacuation details
If the occurrence involved a FIRE / SMOKE ON BOARD an aircraft
Provide information on aircraft fire warning and protection systems
If the occurrence involved a FIRE ON or close to an AERODROME
Provide information on aerodrome fire fighting efforts
If the occurrence involved an ATS UNIT, enter
Details on the ATS unit
Workload data only if workload issues are involved
Functioning of warning systems (e.g. STCA)

9. Example : wreckage and impact information
Position of the wreckage*
In relation to the aerodrome
Description of the terrain
For example mountainous, water, etc.
Details on the impact
Speed
Attitude
Impact angle
* Position of aircraft or of wreckage

10. Architecture ADREP Entities and Entity Structure +
ADREP Topics and Sections
Attributes =
Taxonomy Dictionary
Relational Database for storage
Repository for centralised occurrence management
ECCAIRS 4 Reporting System
Events, Narratives and Notes can be linked to any of the main entities (Occurrence, Air space, Aerodrome, ATS unit, Aircraft)
Narratives
Events
Notes
Recordings
Sector
ATM Staff
Other Pers.
Ratings
Descriptive
Factors
Endorsement
Flight crew
Licenses
Engine Fail.
Float. Devices
GPWS warn.
Incapacitation
Fire suppr.
Part Failures
Precipitation
Prop. Failures
Search Diff.
Separation
Runway
Weather rep.
Potential
Explanatory
Occurrence
Aircraft
Air space
Aerodrome
ATS Unit
Aircraft 1
Aircraft 2
Events, Narratives and Notes can be linked to any of the main entities (Occurrence, Air space, Aerodrome, ATS unit, Aircraft)
Narratives
Events
Notes
Recordings
Sector
ATM Staff
Other Pers.
Ratings
Descriptive
Factors
Endorsement
Flight crew
Licenses
Engine Fail.
Float. Devices
GPWS warn.
Incapacitation
Fire suppr.
Part Failures
Precipitation
Prop. Failures
Search Diff.
Separation
Runway
Weather rep.
Potential
Explanatory
Occurrence
Aircraft
Air space
Aerodrome
ATS Unit
Aircraft 1
Aircraft 2
Management *
590+ attributes most of which are pick-lists
Recommendations
Narratives
Events
Notes
Sector(s)
ATM Personnel
Runway(s)
Failures
History of flight
Medical
Recordings
Meteo
CFIT
Fire
Survival
Ditch
Air Traffic Services
Flight Crew
Separation(s)
Other personnel
Wreckage/Impact
Occurrence *
Aerodrome
Aircraft(s)
Airspace(s)
ATS Unit(s)
Management *
680+ attributes most of which are pick-lists
Recommendations
Narratives
Events
Notes
Sector(s)
ATM Personnel
Runway(s)
Failures
History of flight
Medical
Recordings
Meteo
CFIT
Fire
Survival
Ditch
Air Traffic Services
Flight Crew
Separation(s)
Other personnel
Wreckage/Impact
Occurrence *
Aerodrome
Aircraft(s)
Airspace(s)
ATS Unit(s)
Occurrence
Aircraft
Class, When, Where, Events, …
Flight
Model, Make, Type, …
Other
Route, IFR, Meteo, …
Other, …
Occurrence
Class, When, Where, Events, …
Aircraft
Model, Make, Type, …
Flight
Route, IFR, Meteo, …

11. Graph Examples – Simple Graphs