ECCAIRS Coding Guidelines
DRAFT - November 2006
Always complete the following background data
Date and Time (local or UTC)
State of Occurrence and Location of Occurrence
State Reporting and Reporting Organisation
Report Source and Report Status
o Injury level
o Damage level
Occurrence class (accident, incident, etc.)
ATM contribution / effect on ATM service (required for EUROCONTROL reporting)
Narrative with indication of the language used
For the other attributes the following rules apply
Attributes left blank (no entry) indicate that the data was not entered. The
information may or may not be available.
Attributes with contents “Unknown” indicate that the information requested was not
available even though an effort may have been made to find it.
Coding of Events
Properly identify issues involved
Be as detailed as possible: if the nose gear collapsed enter event type “nose gear
collapse” and not “landing gear related event”.
If desired detail not at hand or do not fit the circumstances, use event at higher
In terms of systems involved, only provide information on what went wrong, where
there was a problem or an issue.
If there was a spurious fire warning in an engine, enter fire warning system related
event. If there was, however a fire, enter “fire” as event type as well as the related
For smoke/fire: if the smoke fire is known to relate to a system, provide an event
for the system involved first.
Events related to deficiencies on the aerodrome should be entered when
deficiencies of an aerodrome were noted independent of any aircraft operation, e.g.
as a result of inspections. When these deficiencies contributed or were causal to an
aircraft accident/incident, they should not be entered as events but should be
entered as descriptive factors instead.
Forced landing off an aerodrome: use as related phase “Emergency landing or off-
Collisions with obstacles versus collision with terrain: The “collision with obstacle”
event types should be used when the presence of the obstacle / its nature
contributed to the occurrence. Use “collision with terrain” when the nature of what
covers the terrain is immaterial and inconsequential to the occurrence.
Enter events in time sequence.
Consequential events (including diversions) must not be the first event in the
sequence. These events are meant to be entered as a consequence of something
happening before. Enter that “something” as first event.
If there are several consequential events, order them in time sequence
If something happened during a forced landing, e.g. the aircraft collided with a tree
then code the collision with the tree as event following the “forced landing”.
If an aircraft crashes after loss of control: enter the loss of control (deviation from
flight path) first followed by, as applicable, a collision with terrain.
After a “loss of control” the aircraft usually enters an “uncontrolled descent” flight
phase. This would be the applicable phase for any collision with terrain.
ECCAIRS Coding Guidelines page 1/3
Link events to the aircraft to which they relate.
In case of a runway incursion, link the incursion to the aircraft that is being
intruded and not the one who caused the incursion. Same methodology is applied
for the runway incursions with persons, vehicles and animals.
Code the descriptive factors under the first event where they appear. Do not repeat them
for subsequent events
Aerodrome and ATC events have no corresponding flight phase except if they directly
relate to the operation of an aircraft.
ECCAIRS Coding Guidelines page 2/3
What kind of information to collect
If there was an AIRCRAFT involved, enter
Number of engines
Landing gear type
Type of operation
At least top level (Commercial, GA, Aerial work, State flights)
For operation type GA / Aerial work also enter Operator Type
Weather relevant: Yes/No
General weather conditions
Note: you may wish to use the TARGA system to assist
If the WEATHER was relevant, enter
Details on meteorological conditions
If there were INJURIES to persons
Complete the injury details
If the occurrence involved ENGINES, enter
Make/model of the engine
If the occurrence involved an AERODROME, enter
If the occurrence involved a RUNWAY, enter
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)
ECCAIRS Coding Guidelines page 3/3