Safety

What to report?

MANDATORY:

• Flight safety episodes such as accidental collisions with aircraft and near-miss incidents where you yourselv are involved in, witness or hear about
• Significant failure, malfunction or defect of aerodrome equipment
• Occurrence related to human performance
• See the full list here

VOLUNTARY:

• Flight safety concerns and suggestions improving flight safety

In order to report, click here.

Handling your report and your anonymity

SSO (Safety Services Office) collects, records, stores, analyses, and monitors all safety reports, actively using them to improve flight safety at Copenhagen (Kastrup) and Roskilde airports.

The reports will not be used to assign blame or responsibility, or for any purpose other than maintaining or improving flight safety.

Note:
 All personal data is processed and protected with appropriate confidentiality in accordance with applicable legislation.
If you, as a reporter, are unsure about your anonymity and concerned about the consequences of your report, you still have the option of reporting incidents or safety-compromising conditions in a system outside of CPH's safety reporting system.
On the Danish Transport Authority's website, you can access incident reporting directly to the authorities (link).  

Aerodrome Manual Copenhagen Airports A/S (CPH)

B.2.2.8) Reporting and analysis of safety events

Safety incidents, concerns, and improvement suggestions are reported in accordance with EU 376/2014 via CPH's reporting system.
These can also be divided into mandatory and voluntary reports.  Voluntary reporting is often concerns and/or improvement opportunities.

Through structured and systematic collection, registration, and analysis of safety reports, a basis is formed for learning and knowledge sharing with relevant organisations, functions, and individuals, so that specific risk areas and undesirable trends can be identified and improved.

Reports will be used to analysing the course of events, and based on this, initiating necessary measures to maintain or improve flight safety at the airport.

All received personal information is protected with necessary confidentiality and deleted after use in accordance with applicable Danish legislation.

Reporting obligation to SSO

All safety events must be reported and then registered, analysed, and followed up internally at CPH in a timely manner. Identified corrective and/or preventive measures based on identified causes must be communicated to relevant stakeholders and implemented in a timely manner.

What needs to be reported to SSO?

A safety event is an incident that has, or could have, brought an aircraft or its occupants in danger.

The following is examples of events. Note: this is not an exhaustive list:

• Unauthorised entry onto runway/taxiway or restricted area of the airfield (e.g. runway/taxiway incursions)
• Driving/movement in front/behind aircrafts in motion, causing inconvenience, for the aircraft
• Aircraft damage or unintended contact with aircraft or its contents (e.g. cargo)
• Behaviour, procedures or installations and equipment that may cause or be a danger to aircraft
• Use of defective infrastructure or equipment that may cause or be a danger to aircraft
• Mis-operation of equipment that may cause a danger to aircraft
• Failure in radio communication with air traffic control/tower
• Deviation from air traffic controller instructions or clearances
• Aircraft entering the wrong stand or parking incorrectly at the stand
• Unintended inconvenience due to jet blast from aircraft engines
• Violation of Local Regulations related to flight safety
• Discovery of foreign object debris (FOD) on runways or taxiways
• Runway/taxiway excursion
• Fire, explosion, or smoke development in buildings, equipment, and installations airside
• Missing or incorrect, false, incomplete, or misleading information from a support service such as automatic terminal information service (ATIS), weather services, navigation databases, maps, charts, aeronautical information service, or manuals
• Failure in communication services, surveillance services, navigation services, or in the meteorological observation service
• Failure in data processing and distribution functions or services
• Safety failure in ATM/CNS system, which have or could have had a direct negative impact on the safe provision of services
• Security-related incidents, including illegal entry, sabotage, bomb threat, etc.

The full list can be found here: EU 376/2014 under the chapter: "Commission Delegated Regulation (EU) 2015/1018 annex IV"

Note:
 A safety event also includes near-miss situations where human or organizational factors potentially can have a significant negative impact on flight safety. For example:

• Critical lack of resources
• Performance of ATM/CNS-related tasks where the employee's physical or mental condition has made the person unsuitable for this, such as fatigue, stress, etc.
• Cases where a decision has compromised flight safety
• Performance of safety work under circumstances where the involved employee does not feel fully competent/qualified.

If there is any doubt as to whether an event should be reported to SSO, please contact safety@cph.dk.

Roles and responsibilities - Who should make safety reports to SSO?

Generally, the person who first discovers a safety event with real or potential impact on flight safety is responsible for reporting it to the CPH Safety Services Office (SSO).

The following organisations, functions, and employees are covered by this reporting obligation:

• All companies/persons who have access to Airside or are residing within the airport premises, including:
• Air navigation services (Naviair)
• Airlines/pilots
• Ground handling companies
• Flight schools
• Maintenance facilities
• CPH employees who provide flight safety services for flight operations such as MET, Marshaller, Fire and Rescue, Wildlife Control, etc.
• CPH employees who directly or indirectly through a third party perform work (design, test, installation, operation, or maintenance) related to the airport's infrastructure, installations, and equipment, such as ATM/CNS systems, CPH O/P network, power supplies, etc., which can affect flight safety.

How should reporting to SSO be done, and when?

Safety reporting is done by filling in a form on CPHNOW. When a safety event is discovered, reporting should be done as soon as possible, and no later than within 72 hours.

Exceptions: The following types of reports may be made outside of CPHNOW.

• Wildlife/bird strikes should preferably be reported directly to CPH Wildlife Control
• FOD must be reported in accordance with Appendix 22, Local Regulations
• Naviair and airlines may send safety reports to SSO via email: safety@cph.dk
• Navilog according to Naviair's delivery contracts with CPH, is sent directly to the CPH ATM office.

Obligation to notify others.

Reporting a safety event to SSO does not exempt the person concerned from their responsibility to communicate and collaborate with their manager or other companies, functions, and departments, in order to gain control over the issue that was reported as a safety event.

Obligation to notify others beyond SSO includes, for example:

• Reporting and involving the design-responsible supplier when an event may have an impact on flight safety. This applies, for example, to technical faults, exceeding technical limitations, or other irregular circumstances where flight safety may be or is compromised.
• Registration in error reporting systems