Occurrencereport
The purpose of reporting an incident is to ensure that deviations that negatively affect the business are taken care of so that they do not occur again or contribute to serious accidents.
Everyone who works at the airport
has an obligation to report incidents. This should be done as soon as possible - before the end of the work shift. Incident reporting should not be confused with Fault Reporting, which means that some technology or infrastructure has broken, such as lighting or escalators. This has a separate reporting path in the extranet under Fault report and report.
When incidents are investigated, it is first and foremost done with the aim of increasing security - not to investigate any question of guilt. The report may contribute to further business development and continuous improvements. Swedavia applies a culture of fairness – just culture – where individuals are not blamed for unintentional errors.
When should an incident report be written?
An incident report should be written when:
- Something may have affected, or could affect safety and/or functionality, or be a deviation from planned or ordered activities
- there is an environmental event or violation of environmental conditions
- a person acts inadequately or incorrectly
- Something else is disrupting the airport's operations
Reporting considerations
To facilitate the investigation, the following must be taken into account:
- Strive for one report per event
- no personal data in the event description (name, badge number, etc.)
- Give as much facts as you can – feel free to use the map function for positioning
Privacy
Your contact information will be protected by privacy and processed in accordance with the General Data Protection Regulation (GDPR).
More information about how we process your contact information can be found on Swedavia's management system.
Swedavia's management system Privacy policy
You have the option of being anonymous when reporting
More information and contact
Email:
occurrencereports@swedavia.se
For more information, see AR part 1, chapter 5 - Event management
If you have any questions, please contact occurrencereports