CASA 17/26 — Operation of Remotely Piloted Aircraft Within No-Fly Zone of a Controlled Aerodrome Approval 2026

Administered by Department of Infrastructure, Transport, Regional Development, Communications, Sport and the Arts

Legislation au F2026N00277 In force Notifiable Instrument

Legislation content

Instrument number CASA 17/26

I, STEVEN JAMES CAMPBELL, Executive Manager, National Operations & Standards, a delegate of CASA, make this instrument under regulation 11.056 and paragraph 101.030(1)(a) of the Civil Aviation Safety Regulations 1998.

[Signed S. Campbell]

Steven Campbell
Executive Manager
National Operations & Standards

24 April 2026

CASA 17/26 — Operation of Remotely Piloted Aircraft Within No-Fly Zone of a Controlled Aerodrome Approval 2026

1 Name

  This instrument is CASA 17/26 — Operation of Remotely Piloted Aircraft Within No-Fly Zone of a Controlled Aerodrome Approval 2026.

2 Duration

  This instrument:

(a) commences on 1 May 2026; and

(b) is repealed at the end of 30 April 2029.

3 Definitions

Note   In this instrument, certain terms and expressions have the same meaning as they have in the Civil Aviation Act 1988, the regulations and the Part 101 MOS. These include chief remote pilot, controlled aerodrome, no-fly zone of a controlled aerodrome, NOTAM and RPA.

  In this instrument:

relevant ATC means the air traffic control service for a relevant controlled aerodrome.

relevant controlled aerodrome means a controlled aerodrome for which the Defence Force is the provider of air traffic services.

4 Application

  This instrument applies in relation to a certified RPA operator operating an RPA within the no-fly zone of a controlled aerodrome that is a relevant controlled aerodrome.

5 Approval

 (1) For regulation 101.030 of CASR, the no-fly zone of a controlled aerodrome that is a relevant controlled aerodrome is approved as an area for the operation of RPA.

 (2) The approval is subject to the conditions set out in section 6.

6 Conditions

 (1) The RPA operator must not operate the RPA unless it has made an agreement with the relevant ATC to operate the RPA.

 (2) The operator must comply with:

(a) any direction given by the relevant ATC; and

(b) any condition of the agreement made under subsection (1).

 (3) The operator must conduct operations in accordance with its documented practices and procedures.

 (4) If it is impossible for the operator to comply with a provision of its documented practices and procedures and a condition in this section, the operator must comply with the condition in this section.

 (5) The operator must:

(a) ensure that the agreement referred to in subsection (1) is made on its behalf by its chief remote pilot; and

(b) supply a copy of the operator’s current certification as an RPA operator to the relevant ATC.

 (6) The operator must not conduct operations unless:

(a) a NOTAM advising of RPA operations in the operating area (the relevant NOTAM) was raised before the operations commenced by:

 (i) CASA or Air Traffic Services; or

 (ii) the operator as an aeronautical data originator; and

(b) before any operations commence on any day, the operator has verified and validated the correctness and completeness of the relevant NOTAM (by ensuring the information is accurate, timely, relevant, and properly formatted); and

(c) the relevant NOTAM is current and active during the operations.

 (7) The operator must notify the relevant ATC of any “escape” event, where the RPA is not under the control of the remote pilot, as soon as is practicable after the event happens.

 (8) The operator must not activate any transponder fitted to the RPA or transmit ADS-B position information unless specifically directed to do so by the relevant ATC.

 (9) The operator must ensure that the RPA is equipped and operated with an active fail-safe mode that will ensure that, in the event of a data-link loss with the RPA, the RPA will:

(a) adjust altitude to the minimum safe level to provide obstacle clearance and minimum potential for collision with other aircraft; and

(b) move to a predefined safe landing or flight termination area; and

(c) land or otherwise terminate the flight.

 

Overview

CASA 17/26 — Operation of Remotely Piloted Aircraft Within No-Fly Zone of a Controlled Aerodrome Approval 2026 was enacted in 2026 by Steven James Campbell, Executive Manager of National Operations & Standards at the Civil Aviation Safety Authority (CASA), a delegate of CASA. This notifiable instrument addresses the problem of ensuring safe operation of remotely piloted aircraft (RPA) within the no-fly zones of controlled aerodromes where the Defence Force provides air traffic services. The policy objective is to maintain safety and order within these specific zones by setting conditions and requirements for RPA operations, including agreements with relevant air traffic control, compliance with air traffic control directions, and ensuring fail-safe operations in case of data-link loss. This instrument applies to certified RPA operators who wish to operate within the no-fly zones of relevant controlled aerodromes. It sets out conditions for these operations, such as making an agreement with the relevant air traffic control, adhering to any directions and conditions set by the air traffic control, and ensuring the RPA is equipped with an active fail-safe mode. The instrument also mandates that a Notice to Airmen (NOTAM) must be raised and verified before operations begin and requires operators to notify air traffic control of any loss of control over the RPA. The approval is effective from 1 May 2026 and will be repealed by the end of 30 April 2029.

Scope and Application

CASA 17/26, titled "Operation of Remotely Piloted Aircraft Within No-Fly Zone of a Controlled Aerodrome Approval 2026," applies to certified remotely piloted aircraft (RPA) operators who are engaged in operations within the no-fly zones of controlled aerodromes where the Defence Force provides air traffic services. This instrument is designed to ensure that RPA operations do not interfere with the safety and efficiency of the air traffic control services provided by the Defence Force. The instrument outlines specific conditions that must be met by RPA operators, including the requirement to make an agreement with the relevant air traffic control service, comply with their directions, and adhere to their documented practices and procedures. Moreover, the RPA operator must ensure that a Notice to Airmen (NOTAM) is raised and validated before operations commence, and must notify the air traffic control service of any "escape" events where the RPA is not under control. The instrument also specifies that the RPA must be equipped with a fail-safe mode to ensure safe operations in the event of a data-link loss. The instrument is in effect from 1 May 2026 until 30 April 2029, after which it will be repealed.

Key Provisions

This instrument, CASA 17/26 – Operation of Remotely Piloted Aircraft Within No-Fly Zone of a Controlled Aerodrome Approval 2026, sets specific rules and conditions for the operation of remotely piloted aircraft (RPA) within the no-fly zones of controlled aerodromes that are relevant controlled aerodromes. It commences on 1 May 2026 and is repealed at the end of 30 April 2029. The instrument defines certain terms and expressions that have the same meaning as they have in the Civil Aviation Act 1988, the Civil Aviation Safety Regulations 1998 (CASR), and the Part 101 Manual of Standards (MOS). The instrument applies to certified RPA operators who are operating an RPA within the no-fly zone of a controlled aerodrome that is a relevant controlled aerodrome. The no-fly zone of a relevant controlled aerodrome is approved as an area for the operation of RPA, subject to the conditions set out in section 6. The obligations and requirements imposed by the instrument on RPA operators include making an agreement with the relevant air traffic control (ATC) to operate the RPA, complying with any direction given by the relevant ATC, and adhering to any conditions of the agreement. The operator must also ensure that its chief remote pilot makes the agreement on its behalf and supply a copy of its current certification as an RPA operator to the relevant ATC. Operations must be conducted in accordance with documented practices and procedures, and if it is impossible to comply with a provision of those practices and procedures and a condition in this section, the operator must comply with the condition in this section. The operator must also notify the relevant ATC of any “escape” event, where the RPA is not under the control of the remote pilot, as soon as is practicable after the event happens. Additionally, the operator must not activate any transponder fitted to the RPA or transmit ADS-B position information unless specifically directed to do so by the relevant ATC. The instrument imposes specific conditions and obligations on RPA operators, and failure to comply with these requirements may result in civil or criminal penalties. Section 6 of the instrument outlines the conditions that must be met by RPA operators, including making an agreement with the relevant ATC, complying with any direction given by the relevant ATC, and adhering to any conditions of the agreement. Failure to comply with these conditions may result in civil penalties, such as fines or the suspension or revocation of the operator’s certification. Additionally, if an RPA operator fails to comply with the requirements of the instrument, it may be subject to criminal penalties, such as imprisonment or fines. The maximum penalties for civil and criminal offences are not specified in the instrument.

Legal classification tags

Area of Law
Aviation Law
Instrument
Notifiable instrument
Concepts
Definitions & Interpretation
Conditions
Compliance Obligations

Interactions

Authorises

All Versions

Sourced from the Federal Register of Legislation at 26 August 2026. For the latest information on Australian Government law please go to https://www.legislation.gov.au.