The term air traffic occurrence is used for accidents and all categories of incidents as well as for defects or mal-functioning of an aircraft, its equipment and any element of the Air Navigation System which is used or intended to be used for the purpose or in connection with the operation of an aircraft or with the provision of an ATM service or navigational aid to an aircraft.
An occurrence associated with the operation of an aircraft which takes place between the time any person boards the aircraft with the intention of flight until such time as all such persons have disembarked, in which:
Note1: For statistical uniformity only, an injury resulting in death within thirty days of the date of the accident is classified as a fatal injury by ICAO.
Note2: An aircraft is considered to be missing when the official search has been terminated and the wreckage has not been located.
An occurrence involving military aircraft, missiles and/or UAS, associated with the operation of an aircraft which takes place between the time any person boards the aircraft with the intention of flight until such time as all such persons have disembarked, in which:
Note1: For statistical uniformity only, an injury resulting in death within thirty days of the date of the accident is classified as a fatal injury.
Note2: An aircraft is considered to be missing when the official search has been terminated and the wreckage has not been located.
A serious occurrence, other than an accident, associated with the operation of an aircraft, which affects or could affect the safety of operation.
A serious occurrence related to the provision of air traffic services, such as:
A situation in which, in the opinion of the pilot or the ATS personnel, the distance between aircraft, as well as their relative positions and speed, have been such that the safety of the aircraft involved may have been compromised.
The severity of an accident is to be expressed according to:
The level of damage to the aircraft:
destroyed/not economically repairable;
aircraft unavailability has major operational impact;
aircraft unavailability has moderate operational impact.
The type and number of injuries:
lethal;
major injury;
minor injury.
In Belgian Defence these three levels are called:
MISHAP category alpha;
MISHAP category bravo;
MISHAP category charlie.
ICAO Doc 4444: AIRPROX - Risk of collision (Eurocontrol ESARR2 category A) = The risk classification of aircraft proximity in which serious risk of collision has existed. Critical near collision between aircraft or between aircraft and obstacle(s). Separations lower than half the separation minima (e.g. 2 NM).
ICAO Annex 13 / attachment C:
ICAO Doc 4444: AIRPROX - Safety not assured (Eurocontrol ESARR2 category B) = The risk classification of an aircraft proximity in which the safety of the aircraft may have been compromised:
ICAO Doc 4444: AIRPROX - No risk of collision (Eurocontrol ESARR2 category C) = The risk classification of an aircraft proximity in which no risk of collision has existed:
ICAO Doc 4444: AIRPROX - Risk not determined (Eurocontrol ESARR2 category D) = The risk classification of an aircraft proximity in which insufficient information was available to determine the risk involved or inconclusive or conflicting evidence precluded such determination.
Eurocontrol ESARR2: An incident which has no safety significance (category E).
Air traffic incidents are designated and identified in reports as follows:
Type | Designation |
---|---|
Air traffic incident | Incident |
as point a (*) | AIRPROX |
as b1 and b2 (*) | Procedure |
as b3 (*) | Facility |
(*) defined above (§ 1.4) |
The Air Traffic Incident Report Form A is intended for use:
An example of this form is added below (§ 4.2).
The Air Traffic Incident Report Form B is intended for ATS personnel or air defence personnel to report an occurence caused by an aircraft or a vehicle, by your own or another ATS unit, an alleged violation of ATS provisions or clearances, equipment/ATC procedures shortcomings, etc.
An example of this form is added below (§ 4.2).
The items mentioned below shall be filled in, even if unknown (UNK) or not relevant (N/R).
Item | |
---|---|
A | aircraft identification of the aircraft, the ATS unit or air defence unit filing the report. |
B | An AIRPROX report should be filed immediately by radio. |
C1 | Date/time UTC and position in bearing and distance from a navigation aid or in LAT/LONG. |
C2 | Information regarding aircraft filing the report, tick as necessary. |
C2 c) | E.g. FL 350/1013 HPA or 2500 FT QNH / 1007 HPA or 1200 FT/QFE / 998 HPA. |
C3 | Information regarding the other aircraft involved. |
C4 | Passing distance (state units used). |
C5 | Weather conditions. |
C6 | Attach additional papers as required. The diagrams may be used to show aircraft's positions. |
D1 f) | State name of ATS unit and date/time in UTC. |
D1 g) | Date and time in UTC. |
D2 d) | Telephone number of pilot, or operating authority, as appropriate, to facilitate enquiries by investigating authority. |
E2 | Include details of ATS unit such as service provided, RTF frequency, SSR codes assigned and altimeter setting. Use diagram to show the aircraft’s position and attach additional papers as required. |
Use this form to report an occurrence involving an aircraft or vehicle, your own or another ATS unit, an alleged violation of ATS provisions or clearances, equipment and ATC procedures shortcomings.
Fill in this Form as soon as practicable after the occurrence.
Fill in as many boxes (1 to 19) as possible. Fill in relevant information. If not relevant, use “N/R”; or if not known, use “N/K”.
Box 1: Year (YY), Month (MM), Date (DD), hour (hh), minute (mm) of occurrence.
Box 2: Night: as defined nationally, or by ICAO.
Box 3: State location using LAT / LONG, a place name, AD, BRG / DIST from a navigation aid or significant point, etc . . .
Box 4: Use this box only if aircraft affected or involved. Provides for details regarding up to two aircraft involved. Use box 13 for additional aircraft.
Type: | Use ICAO aircraft designators |
ADEP/ADES | Use ICAO location indicators or plain language |
Flight level, altitude or height: | Specify flight level (FL), altitude (A), height (H) in feet. If metric, add “m”. Insert altimeter setting, if applicable. |
Mode C: | If level information from the aircraft is available from other sources (e.g. Mode S, ADS, etc...), specify in box 13. |
Relevant route segment: | e.g. SID/STAR/ATS route (specify), aerodrome traffic circuit (specify e.g. downwind), landing, take-off, taxiing, initial climb, etc... Mark flight rules. |
Box 5: To assist in retention of relevant RTF and surveillance recordings.
Box 6: Mark the class of ATS airspace (A, B, C, D, E, F, G) within which the occurrence took place.
Box 7: Indicate the type of service provided, e.g. Area/Approach/Aerodrome - Control/Advisory/Information - Procedural/Radar - etc. Use a combination of these for full description of service provided.
Box 8: Use this box only if aircraft affected or involved, or if near-controlled flight into terrain (CFIT) event, to indicate distance aircraft/aircraft or aircraft/terrain.
Box 9: Specify if automated warning system(s) was/were involved (e.g. conflict alert, ACAS). If applicable, specify type and contents of warning and/or alert.
Box 10: Mark “YES” or “NO”, if relevant.
Box 11: Self-explanatory.
Box 12: Mark “YES” or “NO”, if weather was considered relevant to the occurrence. Include details in box 13.
Box 13: Use free text to describe the occurrence, include a diagram if necessary. Include causes and factors believed to be relevant to the occurrence. Suggest changes and improvements, if appropriate (you may wish to indicate that the report reflects your subjective recollection of the facts). Include relevant weather information. If necessary, use box 13 of additional forms. Indicate sequential number of pages and total number of pages.
Box 14: Give your assessment of workload, taking into account complexity and other factors.
Box 15: Indicate the time period since your last rest break.
Box 16: Self-explanatory.
Box 17: Self-explanatory.
Box 18: Specify your duty position and/or responsibility at the time of the occurrence.
Box 19: Self-explanatory.
The military aviation has an own reporting system called Aviation Safety Reporting System (ASRS), which includes the same information as the Air Traffic Incident Report Form A/B in a different reporting format. Relevant reports and information will be shared with the civilian stakeholders.
The following are the procedures to be followed by a pilot who is or has been involved in an incident:
An initial report made by radio should contain the following information:
The confirmatory report on an incident of major significance initially reported by radio or the initial report on any other incident should be submitted to the Air Accidents and Incidents Investigation Unit of the Ministry of Communications and Infrastructure or to the ARO of the aerodrome of first landing for submission to the Investigation Unit and the appropriate ATS authorities. The pilot should complete the Air Traffic Incident Report Form A, supplementing the details of the initial reports as necessary. Where there is no ARO, the report may be submitted to another ATS Unit.
Incidents that occurred in Brussels FIR/UIR or are related to civil aircraft registered in Belgium:
Federal Public Service Mobility and Transport
Air Accidents and Incidents Investigation Unit
Atrium - 6th floor
Rue du Progrès / Vooruitgangstraat 56
1210 Brussels
BELGIUM
TEL: +32 (0) 2 277 44 22 or +32 (0) 2 277 44 33
TEL: +32 (0) 476 76 18 65
FAX: +32 (0) 2 277 45 52 and +32 (0) 2 277 45 53
Email: air-acc-incidents@mobilit.fgov.be and air-por-incidents@mobilit.fgov.be
Note: To make sure that the investigation procedure can start in due time, it is of high importance to inform the Air Accidents and Incidents Investigation Unit as promptly as possible and not later than seven days after the occurrence.
Incidents that occurred in the area of responsibility of skeyes:
skeyes
DGS&O
Tervuursesteenweg, 303
1820 Steenokkerzeel
BELGIUM
TEL: +32 (2) 206 20 40
FAX: +32 (2) 206 22 21
Incidents that occurred in the area of responsibility of ANA:
Administration de la navigation aérienne
Safety Unit
BP 273
L-2012 Luxembourg
LUXEMBOURG
TEL: +352 47 98 23 01 0
FAX: +352 47 98 23 09 0
Email: safety@airport.etat.lu
Incidents that occurred in BRUSSELS UIR above FL 245:
EUROCONTROL Agency Safety Regulation Unit (ASRU)
Rue de la Fusée / Raketstraat 96
1130 Brussels
BELGIUM
TEL: +32 (2) 729 90 11
FAX: +32 (2) 729 90 44
Telex: 21173 euroc b
Incidents that occurred in foreign countries and relate to civil aircraft registered in Luxembourg:
Direction de l'Aviation Civile
BP 283
L-2012 Luxembourg
LUXEMBOURG
TEL: +352 24 77 49 00
FAX: +352 46 77 90
Email: info@dac.public.lu
The following are the procedures to be followed by a pilot who is or has been involved in an incident:
An initial report made by radio should contain the following information:
ATS personnel or air defence personnel shall proceed as follows regarding an occurrence in which he has been involved. As promptly as possible after an occurrence took place, ATS personnel or air defence personnel shall submit a completed Air Traffic Occurrence Notification Report in accordance with ATM instruction 12 and the Air Traffic Occurrence Notification Report form.
Air Traffic Occurrence Notification Reports concerning air traffic occurrences that happened within the Brussels FIR/UIR or in other FIRs to a flight terminating in the Brussels FIR will be addressed to the relevant ATS unit.
Defence
Air Component
Aviation Safety Directorate/Safety Monitoring Office
Base Charles Roman
1320 Beauvechain
BELGIUM
TEL: +32 (0) 2 442 54 49
Email: asd-atm@mil.be
The purpose of the reporting of air traffic incidents and their investigation is to promote the safety of aircraft and to reduce the risk of mid-air collisions and to reduce the risk of accidents and incidents caused by faulty procedures or non-compliance with procedures, or failure of ground facilities. The sole objective of the safety investigation of an occurrence shall be the prevention of accidents and incidents. It is not the purpose of this activity to apportion blame or liability. Aircrew and Air Traffic Control/Air Defence personnel who are involved in air traffic occurrences, including those who have been reported as being involved, should cooperate in the investigation by providing complete and accurate information. The degree of risk involved, and the severity of the aircraft incidents should be determined in the incident investigation and classified as “serious incident”, “major incident”, “significant incident”, “not determined” or “no safety effect”.
The purpose of the forms is to provide investigatory authorities with as complete information on an air traffic incident as possible and to enable them to report back, with the least possible delay to the pilot or operator concerned, the result of the investigation of the incident and, if appropriate, the remedial action taken for safety improvement. Any information given in order to improve the investigation processes may be used by the receiving party exclusively for safety purposes. Those data may never be used for any other purpose. All the safety related data shall stay confidential.