REPCON – Aviation Confidential Reporting Scheme

What is REPCON?

REPCON is a voluntary and confidential reporting scheme. REPCON allows any person who has an aviation safety concern to report it to the ATSB confidentially. Protection of the reporter's identity and any individual referred to in the report is a primary element of the scheme.

Who can make a REPCON report?

Anyone can report a safety concern confidentially to the ATSB. This means members of the travelling public or people involved in aviation.

Some examples of who has made a REPCON report in the past include:

  • an employee or contractor of an aviation transport operator who reported a matter under the operator’s Safety Management System (SMS) but does not believe it will be properly dealt with. 
  • a person who has not reported under the SMS because they believe they will suffer retribution. (When submitting a report please ensure that you cannot be identified within your organisation by not copying any other person into the report).

What may be reported with REPCON?

Each of the following concerns (reportable safety concerns) in relation to the safety of aircraft operations to which the Regulations apply are examples of what may be reported under REPCON.  The list is not exhaustive:

a) an incident or circumstance that affects or might affect the safety of aircraft operations;

b) a procedure, practice or condition that a reasonable person would consider endangers, or, if not corrected, would endanger, the safety of air navigation or aircraft operations, for example:

(i) poor training, behaviour or attitude displayed by an aircraft operator, airport operator or air traffic control service provider; or
(ii) insufficient qualifications or experience of employees of the aircraft operator, airport operator or air traffic control service provider; or
(iii) scheduling or rostering that contributes to the fatigue of employees of the aircraft operator, airport operator or air traffic control service provider; or
(iv) an aircraft operator, airport operator or air traffic control service provider bypassing safety procedures because of operational or commercial pressures; or
(v) inadequate airport facilities for safe operations; or
(vi) unsafe passenger, baggage or cargo management; or
(vii) inadequate traffic or weather information;

c) any other matter that affects, or might affect the safety of or aircraft operations not reportable under a mandatory reporting scheme.

If you are in any doubt whether the matter you wish to report is covered by the REPCON scheme or a mandatory reporting scheme please call us.

What is not a reportable safety concern?

To avoid doubt, the following matters are not reportable safety concerns and are not guaranteed confidentiality

  • matters relating to a serious and imminent threat to a person’s health or life
  • industrial relations matters
  • conduct that constitutes a criminal offence
  • terrorist acts. If you wish to provide information about terrorist activity you should call the National Security Hotline on 1800 123 400.

Matters which must be reported under a mandatory reporting scheme should not be reported under REPCON. This will not discharge your reporting obligations under a mandatory reporting scheme.

If you believe it would be necessary to act on information about an individual referred to in your report then you should report this directly to the Civil Aviation Safety Authority (CASA) on 1800 074 737 or the aircraft operator

What is confidential?

Personal information about the reporter and any person referred to in the report is confidential. Even if you are not concerned about keeping your identity confidential, do not copy in personnel from within or outside your organisation to the report. The integrity of the confidentiality of the reporter is the main concern of the REPCON system. If this occurs, we cannot process the report within the REPCON framework.

If you think it’s necessary to act on information about a person referred to in your report, you should report this directly to the Civil Aviation Safety Authority on 1800 074 737.

Is an anonymous report via REPCON acceptable?

REPCON does not accept anonymous reports. REPCON staff cannot contact an anonymous reporter to verify the report or to seek additional information. Further, REPCON staff must be satisfied that the reporter's motivation for reporting is aviation safety promotion, and that the reporter is not attempting to damage a rival or pursue an industrial agenda.

How are REPCON reports processed?

REPCON staff will assess reports for clarity, completeness and significance for aviation safety and to ensure it meets the requirements of a Reportable Safety Concern (RSC) for aviation.

The report will be de-identified to remove all personal details of the reporter and any individual named in the report. This will be passed to the reporter who must authorise the content before the REPCON can proceed further.

The de-identified text is then forwarded to the relevant organisation that is best placed to address the RSC. The organisation’s response will then be forwarded to the regulatory bodies, such as CASA, for further action as deemed necessary.

REPCON may use the de-identified version of the report to issue an information-brief or alert bulletin to a person or organisation, including CASA, which is in a position to take safety action in response to the safety concern.

What are the possible outcomes from a REPCON report?

The desired outcomes are any actions taken to improve aviation safety in response to the identified concern. This can include variations to standards, orders, practices, procedures or an education campaign.

Why is REPCON important?

REPCON reports can serve as a powerful reminder that, despite the best of intentions, well-trained and well-meaning people are still capable of making mistakes. The de-identified stories arising from these reports may serve to reinforce the message that we must remain vigilant to ensure the ongoing safety of ourselves and others.

ASRS or REPCON?

REPCON is a separate scheme to the Aviation Self Reporting Scheme (ASRS). The ASRS allows for self-reports of unintentional regulatory breaches by pilots who are seeking to claim protection from administrative action by CASA. A reporter seeking protection from administrative action by CASA should consider reporting under the ASRS and whether they meet its criteria.

REPCON is a much broader reporting scheme designed to capture a wide range of aviation safety concerns from a large pool of potential reporters.

How can I make a REPCON report?

REPCON reports can be submitted by: Online REPCON form

Mail:
Reply Paid 600
PO Box 600
Civic Square, ACT 2608

Telephone: 1800 020 505
Overseas: +61 2 6230 5135

Email: repcon@atsb.gov.au

If you require assistance, advice or further information, please call REPCON on 1800 020 505 (International: +61 2 6230 5135).

________

Submission of information known by the reporter to be false or misleading is a serious offence under section 137.1 of the Criminal Code. Aiding, abetting, counseling, procuring or urging the submission of false or misleading information is also a serious offence.

2000 Flight Safety Australia

ATSB supplements

November-December

  • Chieftain investigation leads to safety recommendations
  • Safety Briefs
  • Mate, I take pressurisation more seriously now!
  • Confidential aviation incident reports
  • Download ATSB supplement (Nov-Dec 00) [
    PDF: 1.22MB (1.22 MB)
    ]

September-October

  • Fatigue
  • Recent investigations
  • Confidential aviation incident reports
  • Download ATSB supplement (Sep-Oct 00) [
    PDF: 730KB (730.4 KB)
    ]

May-June

  • Safety Briefs
  • Helicopter crash in bad weather
  • Analysing runway incursions
  • Confidential aviation incident reports
  • Download ATSB supplement (May-Jun 00) [
    PDF: 851KB (851.14 KB)
    ]

March-April

  • Aviation Safety Occurrence Statistics
  • Safety Snippets
  • Maintenance 'error' Lessons from the ATSB survey
  • Confidential aviation incident reports
  • Download ATSB supplement (Mar-Apr 00) [
    PDF: 662KB (662.58 KB)
    ]

2004 Flight Safety Australia

ATSB supplements

November-December

  • Drive shaft failure Robinson R22
  • Winning research grants
  • Safety briefs
  • Download ATSB supplement (Nov-Dec 04) [
    PDF: 361KB (361.51 KB)
    ]

September-October

  • Circuit airprox
  • Toowoomba accident claims four lives
  • Safety briefs
  • Download ATSB supplement (Sep-Oct 04) [
    PDF: 269KB (269.17 KB)
    ]

July-August

  • Dynamic helicopter rollover
  • Moorabbin airport fatal accident
  • Safety briefs
  • Download ATSB supplement (Jul-Aug 04) [
    PDF: 240KB (240.18 KB)
    ]

May-June

  • ATSB funding boost
  • Air Safety Occurrence reporting requirements
  • Safety briefs��
  • Download ATSB supplement (May-Jun 04) [
    PDF: 143KB (143.6 KB)
    ]

March-April

  • Near crash from icing prompts call for better stall warning
  • Aviation Self Reporting Scheme
  • Safety brief
  • Download ATSB supplement (Mar-Apr 04) [
    PDF: 329KB (329.27 KB)
    ]

January-February

  • ATSB wins international award
  • Safety briefs
  • Download ATSB supplement (Jan-Feb 04) [
    PDF: 2.35MB (2.35 MB)
    ]

2003 Flight Safety Australia

ATSB supplements

November-December

  • The ATSB gets a new Act
  • Safety briefs.
  • Confidential aviation incident reports.
  • Download ATSB supplement (Nov-Dec 03) [
    PDF: 2.23MB (2.23 MB)
    ]

September-October

  • The ATSB gets a new Act
  • Safety briefs
  • Confidential aviation incident reports
  • Download ATSB supplement (Sep-Oct 03) [
    PDF: 113KB (113.06 KB)
    ]

July-August

  • Loss of control
  • Safety briefs
  • Confidential aviation incident reports
  • Download ATSB supplement (Jul-Aug 03) [
    PDF: 641KB (641.94 KB)
    ]

May-June*

* not produced

March-April

  • Engine flame-out - shoulder harness failed on impact
  • Safety briefs
  • Confidential aviation incident reports
  • Download ATSB supplement (Mar-Apr 03) [
    PDF: 249KB (249.6 KB)
    ]

January-February

  • Inflight engine fire
  • Safety briefs
  • Confidential aviation incident reports
  • Download ATSB supplement (Jan-Feb 03) [
    PDF: 312KB (312.51 KB)
    ]

2001 Flight Safety Australia

ATSB supplements

November-December

  • You might learn about flying from this
  • Safety Briefs
  • Safety first - aircrew, ground personnel and passengers
  • Download ATSB supplement (Nov-Dec 01) [
    PDF: 1.06MB (1.06 MB)
    ]

September-October

  • Safety Briefs
  • Got the right fuel system fitting in your balloon?
  • Confidential aviation incident reports
  • Download ATSB supplement (Sep-Oct 01) [
    PDF: 1.2MB (1.2 MB)
    ]

July-August 2001

  • How the ATSB investigates accidents.
  • New accident/incident forms.
  • Safety briefs.
  • Confidential aviation incident reporting.
  • Download ATSB supplement (Jul-Aug 01) [
    PDF: 1.01MB (1.01 MB)
    ]

May-June 2001

  • Fuel contamination
  • Behind the QF1 investigation
  • Safety briefs
  • Confidential aviation incident reporting
  • Download ATSB supplement (May-Jun 01) [
    PDF: 1.31MB (1.31 MB)
    ]

March-April

  • Fuel usage
  • Safety briefs
  • Monarch revisited
  • Confidential aviation incident reports
  • Download ATSB supplement (Mar-Apr 01) [
    PDF: 1.03MB (1.03 MB)
    ]

2002 Flight Safety Australia

ATSB supplements

November-December

  • Disorientation during night operations
  • Confidential Aviation Incident Reporting System
  • Safety briefs
  • Download ATSB supplement (Nov-Dec 02) [
    PDF: 1.84MB (1.84 MB)
    ]

September-October

  • Engines failure due fuel exhaustion
  • Safety briefs
  • Microburst effect on aircraft performance
  • Confidential aviation incident reports
  • Download ATSB supplement (Sep-Oct 02) [
    PDF: 731KB (731.83 KB)
    ]

July-August

  • Gear up!!!
  • Safety briefs
  • Safe Health - Hows your attitude?
  • Confidential aviation incident reports
  • Download ATSB supplement (Jul-Aug 02) [
    PDF: 1.72MB (1.72 MB)
    ]

May-June

  • What happens when a 737 pilot loses conciousness in flight?
  • Safety briefs
  • Confidential aviation incident reports
  • Download ATSB supplement (May-Jun 02) [
    PDF: 1.43MB (1.43 MB)
    ]

March-April

  • Panel hooks not engaged
  • Safety Briefs
  • Rotor blades can fail when hours exceeded
  • Confidential aviation incident reports
  • Download ATSB supplement (Mar-Apr 02) [
    PDF: 1.57MB (1.57 MB)
    ]

January-February

  • Twin mechanical failure linked to leaning
  • Helicopter accident highlights mountain wave dangers
  • Safety Briefs
  • Confidential aviation incident reports
  • Download ATSB supplement (Jan-Feb 02) [
    PDF: 812KB (812.63 KB)
    ]

Marine safety

Marine transport accounts for all bulk imports and exports and nearly three-quarters of the value of all imports and exports of cargo into Australia, and plays a primary role in coastal trade. In addition, a major offshore industry fleet supports oil and gas exploration off the Australian coast. A safe and efficient marine transport system is therefore an essential part of the Australian economy. The work of the ATSB investigation team assists in maintaining and improving the safety of marine transport.

When ATSB investigates a marine accident or incident, investigators seek to determine its circumstances, contributing and other factors, including any safety issues, and encourage relevant safety action. The aim of all ATSB investigations is to prevent accidents and incidents - not to assign blame or liability. This approach helps ensure the continued free flow of safety information for the purposes of improving safety in the future.

The ATSB conducts 'no blame' marine safety investigations in accordance with the Transport Safety Investigation Act 2003 (TSI Act). The ATSB does not investigate for the purpose of taking administrative, regulatory or criminal action.

Marine safety investigations are carried out in accordance with international treaties and instruments. These include the Safety of Life at Sea (SOLAS) Convention (specifically the Casualty Investigation Code), relevant International Maritime Organization (IMO) resolutions and Article 94(7) of the United Nations Convention on the Law of the Sea (UNCLOS). The TSI Act recognises these international agreements and instruments.

The power to prosecute ships' masters and others for breaches of safety and pollution prevention legislation resides with the Australian Maritime Safety Authority(Opens in a new tab/window) (AMSA), the regulatory and administrative body responsible for marine safety in Australia.

 

---

Rail statistics

Rail safety occurrence data

Industry reports rail safety occurrences to the Office of the National Rail Safety Regulator (ONRSR)(Opens in a new tab/window).

ONRSR has responsibility for regulatory oversight of rail safety in every Australian state and territory.

ONRSR collects and reports on rail safety occurrence statistics, and these figures are available on the ONRSR website.

Historical rail safety occurrence data

Prior to the establishment of ONRSR, rail safety occurrence data was provided to the ATSB by state and territory government rail safety regulators for national publication.

Disclaimer: This data was supplied to the ATSB by state and NT rail safety regulators. The ATSB accepts no liability for any loss or damage suffered by any person or corporation resulting from the use of these data.

Definitions: Definitions for data provided in each of the categories were developed by rail safety regulators in collaboration with industry:

  • 1 January 2001 to 30 June 2008 were taken from Occurrence Notification Standard 1 (ON-S1, 2004 Rail Safety Regulators' Panel); and
  • From 1 July 2008 were taken from Occurrence Classification Guideline 1 (OC-G1, July 2008 Rail Safety Regulators' Panel).

ON-S1 occurrence definitions 

[PDF: 25KB] (20.95 KB)

OC-G1 occurrence definitions 

[PDF: 36KB] (36.82 KB)

Rail safety

From 1 July 2019, report Category A rail occurrences directly to the Office of the National Rail Safety Regulator (ONRSR) on 1800 430 888 (24 hrs / 7 days).

 

The ATSB is the single national rail safety investigator in Australia.

The ATSB’s rails safety investigation role occurs concurrently with the Office of the National Rail Safety Regulator (ONRSR) overseeing rail safety regulation in every Australian state and territory. 

The ATSB investigates selectively, as do many equivalent organisations overseas. The aim is to concentrate ATSB’s resources on those investigations considered most likely to enhance rail safety. Because many accidents are repetitive in nature, investigating these in any detail may not be justified, given the ATSB’s limited resources. In such cases, the ATSB will not necessarily attend the scene, conduct an in-depth investigation or produce an extensive report.

When the ATSB investigates an accident or incident, investigators will seek to determine its circumstances, identify any safety issues, and encourage relevant safety action. The aim of all ATSB investigations is to prevent the occurrence of other accidents and incidents, rather than to assign blame or liability. This approach helps ensure the continued free flow of safety information for the purposes of improving safety in the future.

As required under the Transport Safety Investigation Act 2003 (TSI Act), train operating crew, rail and track owners and operators must report accidents and serious incidents (Category A occurrences) that occur as soon as practicable and by the quickest means possible. All Category A occurrences need to directed to ONRSR by calling 1800 430 888 (24 hrs / 7 days).

Rail accident or incident notification

Train operating crew, rail and track owners and operators must report all notifiable occurrence (an accident or incident associated with railway operations - either Category A, Category B or Category C) to ONRSR (Opens in a new tab/window)by calling 1800 430 888 (24 hrs/7 days) or via the ONRSR Portal(Opens in a new tab/window).

Note: Following changes to the Rail Safety National Law (RSNL) in July 2019, a separate report to the ATSB is no longer required.

Further information on reporting obligations is available on the ONRSR website(Opens in a new tab/window).