The National Aviation Occurrence Database allows you to search for accidents and incidents that have been reported to the ATSB since 1 July 2003. You can search the database using a time period, location, type of occurrence (i.e. what happened), and type of aircraft.

We regularly add new reported occurrences to ensure the database is up to date. However, depending on workload and volume of reports it may take some weeks to verify and include new occurrences.

How ATSB data is collected?

ATSB data is collected through the mandatory occurrence reporting requirements of the Transport Safety Investigation Act 2003 and associated Regulations from the aviation industry. It is provided publicly as a result of the cooperative efforts between the ATSB and the aviation industry as a whole. 

Taxonomy and terminology

The ATSB uses an occurrence category taxonomy to efficiently and consistently categorise and code transport safety occurrences. Read more here.

Limitations of the data

The data quality and consistency is largely dependent on the details reported to the ATSB. The information in the majority of non-investigated occurrence reports is not subject to verification.
This data is subject to change. The ATSB may need to update and improve the data as it receives additional information and validates the data already received.

ATSB data includes information obtained from all reports that meet the reporting requirements of the Transport Safety Investigation Regulations 2021. Not all notifications reported to the ATSB are classified as incidents, serious incidents or accidents. Those that are deemed to not be a transport safety matter are classified as ‘events’. Events are not included in this database.

Notifications that do not relate to aircraft safety are coded as events (such as cabin injuries not related to the operation of the aircraft, and airport infrastructure, navigation aids and air traffic control facilities failures that do not directly involve an aircraft). In addition, notifications of the following types of notifications when they occur without any other occurrence type event are generally coded as events:

  • consequential events (diversion/return, fuel dump/burn off, missed approach/go-around)
  • operational non-compliance with air traffic control verbal or published instruction
  • airspace infringement
  • breakdown of co-ordination between air navigation service providers.

Prior to October 2014, the ATSB online aviation occurrence database did include operational non-compliance, airspace infringement and breakdown of co-ordination notifications as incidents.

Disclaimer on data use

The ATSB collects aviation safety data and investigates air safety occurrences for the sole purpose of enhancing aviation safety.  Consequently, the ATSB material is confined to matters of safety significance and may be misleading if used for any other purpose.

The ATSB aims to publish occurrence data as soon as reasonably practicable after receiving reports from industry. However, depending on workload and the volume of reports received, it may take some weeks to input the data into the database from when we received the report. If you are seeking data or information on a specific recent occurrence that does not appear in search results, you should contact the ATSB via email:

When using this data, it is important to remember that occurrence data is provided to the ATSB by responsible persons as defined in the Transport Safety Investigation Regulations 2021.

The ATSB accepts no liability for any loss or damage suffered by any person or organisation resulting from the use of this data. The ATSB does not warrant the completeness, accuracy or suitability of the data and the database for your intended purpose.

User agreement

By clicking start I acknowledge that I have read, understood and agree with the above limitations and disclaimer on data use.

Getting started click here