Reporting air safety concerns

Military Aviation Authority (MAA) guidance to personnel from across the defence air environment on how to report air safety concerns.

Reporting air safety concerns

The proactive reporting of air safety concerns by personnel from across the defence air environment (DAE) is fundamental in maintaining continual awareness of the risks facing our people. To enable and facilitate such reporting, the MOD provides a standardised reporting format and management system for DAE personnel to use.

Air safety information management system (ASIMS)

ASIMS is an internal MOD tool used for the reporting, management and exploitation of air safety occurrence and investigation information. ASIMS is a dynamic system allowing the most up to date information to be recorded as it becomes available.

To log into ASIMS, MOD users can navigate to ASIMS in your browser.

For access to ASIMS, contact your local flight safety point of contact.

ASIMS training and reference material

ASIMS users should undertake the appropriate training packages for their role/requirements prior to using the system.

ASIMS user training courses are available through ASIMS with further guidance and information available in the ASIMS user manual.

Defence air safety occurrence report (DASOR)

In accordance with Regulatory Article (RA) 1410, the DASOR is to be used to report all air safety related occurrences, be it notification of an event which has already occurred or identification of a potential air safety hazard i.e. a hazard / observation. In addition to the standard DASOR, complementary forms are available for specific specialist occurrences which require further information from the reporter i.e. the airprox report, birdstrike report, air traffic management report, malfunctioned drop (MALDROP) report and the parachuting report.

The primary method for submitting a DASOR is through ASIMS. This application is available from any device connected to the internet and on internal MOD networks by navigating to the following URL:

If you are unable to access ASIMS, then PDF versions of the DASOR document suite are available below. Once complete, send the PDF documents to your home unit for submission onto ASIMS directly.

The ASIMS user manual provides guidance on how to complete a DASOR.

Error reporting

Error management systems will also use the DASOR to record air safety information; however, individual ships / stations / establishments may have their own local management procedures in place, which will include options for individuals to report non-air safety hazard / observations.

There may also be occasions when an individual is unable or unwilling to complete a DASOR and where a readily available, paper form option would be advantageous in capturing errors, observations, risks or hazards. The In-Form is the approved reporting form and should replace any legacy DAEMS forms within all ships / stations / establishments. Typical examples of when the In-Form may be used are detailed below and completion instructions are detailed on the form;

  • any safety related issues
  • near misses of any type whether air or functional safety
  • any safety hazards such as those affecting flight safety, airworthiness or health and safety
  • any quality concerns
  • any continuous improvement ideas
  • any organisational failings
  • any issues that make human error more likely

For further information, contact your local ship / station error management systems coordinator.

Defence confidential occurrence reporting scheme (DCORS)

This process covers all military, civilian and contracted personnel and allows the anonymous reporting of air safety occurrences which fall outside the normal reporting parameters. For further information see RA 1410.

The defence confidential occurence reporting scheme (DCORS) form is available below.


Published 14 November 2014
Last updated 14 July 2016 + show all updates
  1. ASIMS training course information updated.

  2. The Significant Occurrence Notifications (SON) form has been added.

  3. ASIMS is experiencing accessibility difficulties through the Internet Explorer web browser on Windows XP.

  4. First published.