{"id":"F2024L01461","name":"CASA 67/24 — Operation of RPA in Sydney Harbour Restricted Areas, R405A and R405B (CASA-Verified Drone Safety App) Instrument 2024","slug":"casa-67-24-operation-of-rpa-in-sydney-harbour-restricted-areas-r405a-and-r405b-casa-verified-drone-s","collection":"legislative_instrument","jurisdiction":"commonwealth","status":"in_force","isInForce":true,"actNumber":null,"makingDate":null,"administeringDepartment":null,"currentVersion":{"id":105461,"registerId":"commonwealth-F2024L01461-current","compilationNumber":null,"startDate":"2026-04-03","status":"InForce","reasons":null,"registeredAt":null},"sections":[{"sectionNumber":"1","sectionType":"section","heading":"CASA 67/24 — Operation of RPA in Sydney Harbour Restricted Areas, R405A and R405B (CASA-Verified Drone Safety App) Instrument 2024","content":"Instrument number CASA 67/24\n\nI, PAUL HIBBERD, National Manager, Emerging Technologies & Regulatory Change, National Operations and Standards Division, a delegate of CASA, make this instrument under regulations 11.245 and 101.065 of the Civil Aviation Safety Regulations 1998.\n\n\\[Signed P. Hibberd\\]\n\nPaul Hibberd  \nNational Manager, Emerging Technologies & Regulatory Change  \nNational Operations and Standards Division\n\n15 November 2024\n\nCASA 67/24 — Operation of RPA in Sydney Harbour Restricted Areas, R405A and R405B (CASA-Verified Drone Safety App) Instrument 2024\n\n1 Name\n\nThis instrument is CASA 67/24 — Operation of RPA in Sydney Harbour Restricted Areas, R405A and R405B (CASA-Verified Drone Safety App) Instrument 2024.\n\n2 Duration\n\nThis instrument:\n\n(a) commences on 16 November 2024; and\n\n(b) is repealed at the end of 11 November 2026.\n\n> Note For regulation 11.250 of CASR, the directions stated in section 5 cease to be in force at the end of 11 November 2026.\n\n3 Definitions\n\n> Note In this instrument, certain terms and expressions have the same meaning as they have in the Civil Aviation Act 1988 and the regulations. These include aerial work operation, Australian territory, remote pilot licence, restricted area, RPA and RPAS.\n\nIn this instrument:\n\n> CASA RPAS digital platform means the CASA digital platform, accessible on the internet by third party app developers, which provides data in relation to aeronautical information relevant to RPA operations.\n\n> CASA-verified drone safety app means a software application, connected to the CASA RPAS digital platform, which is listed as a verified app on the CASA website on the internet.\n\n> Note The relevant CASA website address on the internet is <https://www.casa.gov.au/drones/safety-apps>.\n\n> documented practices and procedures has the meaning given by subsection 1.04(2) of the Part 101 Manual of Standards.\n\n> operating area means the segment of airspace described on a CASA-verified drone safety app, defined by reference to horizontal and vertical limits within the relevant restricted areas, in which an RPA may be operated.\n\n> R405A means the area of Australian territory declared as a restricted area, and designated as “YMMM/R405A Sydney”, under instrument number CASA OAR 068/24.\n\n> R405B means the area of Australian territory declared as a restricted area, and designated as “YMMM/R405B Sydney”, under instrument number CASA OAR 068/24.\n\n> Note On the making of this instrument, R405A and R405B are declared to be restricted areas under CASA OAR 068/24 – Declarations and Directions in relation to Prohibited, Restricted and Danger Areas, Etc. – Permanent Instrument 2024.\n\n> relevant restricted area means a restricted area approved under subsection 4(1).\n\n> remote pilot means:\n\n(a) the holder of a remote pilot licence; or\n\n(b) a person who is taken to hold a remote pilot licence under subregulation 202.461(3) of CASR.\n\n> RPA operator means a person who is certified as an RPA operator under regulation 101.335 of CASR.\n\n4 Permission\n\n1.  On application made by AUSTRALIAN ASSOCIATION FOR UNCREWED SYSTEMS INCORPORATED, ASIC Registration Number A39728, under subregulation 101.065 of CASR, CASA approves R405A and R405B as restricted areas in, or over, which a remote pilot is permitted to operate an RPA.\n2.  The operation of an RPA by a remote pilot in, or over, a relevant restricted area is subject to the directions stated in section 5.\n\n5 Directions\n\n(1) A remote pilot (the pilot) operating an RPA in an operating area must:\n\n(a) if the pilot is an RPA operator — be registered, using a CASA-verified drone safety app, to be authorised to operate the RPA in the operating area during a period notified to the pilot on the app; or\n\n(b) be a member of the personnel of an RPA operator that has registered, using a CASA-verified drone safety app, to be authorised to operate the RPA in the operating area during a period notified to the pilot on the app.\n\n(2) The pilot must, during the RPA operation, comply with any operating limitations, relevant to the operation, which are notified to the pilot on the CASA-verified drone safety app in relation to the registration mentioned in subsection (1).\n\n(3) The pilot must conduct the RPA operation only as an aerial work operation.\n\n(4) The pilot must, during the RPA operation:\n\n(a) not operate any other RPA; and\n\n(b) take reasonable steps to ensure a listening watch is maintained on frequency 120.8 MHz, from 15 minutes before the start of a flight of the RPA until the RPA has landed at the end of the flight; and\n\n(c) take reasonable steps to ensure that reliable mobile phone coverage exists in the operating area.\n\n(5) The pilot must, during the RPA operation, ensure the RPA is equipped and operated with an active fail-safe mode that will ensure, in the event of a data link loss between the RPA and its associated remote pilot station during a flight of the RPA, the RPA will:\n\n(a) adjust altitude to the minimum safe level, to provide obstacle clearance and the minimum potential for collision with other aircraft; and\n\n(b) transit to a pre-defined safe landing, or flight termination, area; and\n\n(c) land or otherwise end the flight.\n\n(6) If there is an inconsistency between a requirement of the relevant RPA operator’s documented practices and procedures and a direction in this section, the pilot must comply with the direction.","sortOrder":0}],"analysis":{"flash_summary_failed":{"failed":true,"reason":"Unauthenticated. Configure AI_GATEWAY_API_KEY or use a provider module. Learn more: https://ai-sdk.dev/unauthenticated-ai-gateway","source":"analysis-cron"},"flash_summary":{"complexity_score":5,"scope_assessment":{"changed":true,"description":"This instrument changes scope by not only confirming R405A and R405B as restricted areas but by authorising conditional RPA operations within them subject to app-based registration and specified operational/technical requirements (s4(1), s5). Compared with the area declaration in CASA OAR 068/24, it expands permitted activity into the restricted areas under tightly defined procedural and equipment conditions and is time-limited to 11 November 2026 (s2)."},"complexity_factors":["App-based authorisation workflow: requirement that operators or their personnel register using a CASA-verified app to be authorised for a notified period (s5(1))","Operational constraints communicated via app: pilots must comply with operating limitations notified on the CASA-verified app (s5(2))","Use-case restriction: operations must be conducted only as aerial work operations, narrowing permitted activity (s5(3))","Technical and safety obligations: fail-safe mode requirements for data-link loss including altitude adjustment, transit to safe landing/termination area, and landing (s5(5))","Communications and coverage duties: listening watch on frequency 120.8 MHz and ensuring reliable mobile phone coverage in the operating area (s5(4)(b),(c))","Single-RPA operation and personnel conditions: prohibition on operating any other RPA during the operation and registration-by-operator membership alternative (s5(4)(a), s5(1)(b))","Priority of directions over operator procedures: where inconsistent, the instrument's directions prevail over the operator’s documented practices and procedures (s5(6))","Temporal and inter-instrument linkage: the instrument is time-limited (commences 16 Nov 2024, repealed 11 Nov 2026) and relies on definitions and area declarations in other instruments/standards (s2, s3; CASA OAR 068/24; Part 101 MOS cross-reference)"],"plain_english_summary":"This instrument authorises remotely piloted aircraft (drones) to be operated in two specific Sydney Harbour restricted areas (R405A and R405B) only if the pilot or their certified RPA operator registers via a CASA‑verified drone safety app and follows limits shown on that app. It applies to remote pilots and certified RPA operators and matters because access to these restricted airspaces is conditional on app-based authorisation and specified operational and technical requirements, for a limited period to 11 November 2026."},"kimi_summary":{"content_quality":"ok","complexity_score":4,"scope_assessment":{"changed":false,"description":"This instrument appears to serve its original intended purpose: creating a specific exemption for commercial drone operations in Sydney Harbour restricted areas using verified safety apps. The scope is tightly constrained to R405A/R405B, aerial work operations only, and a two-year duration. No evidence of scope creep beyond the original regulatory intent."},"complexity_factors":["Moderate cross-referencing: references CASR regulations 11.245, 101.065, 101.335, subregulation 202.461(3), and external instrument CASA OAR 068/24","8 defined terms in section 3, including nested definitions (e.g., 'relevant restricted area' depends on subsection 4(1))","Conditional logic in section 5: alternative compliance paths for RPA operators vs. their personnel (subsection 5(1)(a) vs (b))","Hierarchy of compliance: subsection 5(6) creates a conflict-resolution rule between this instrument and operator documentation","Technical operational requirements: specific radio frequency (120.8 MHz), fail-safe mode specifications with three sub-requirements","External dependencies: relies on CASA-verified apps and digital platform infrastructure not defined within the instrument itself"],"plain_english_summary":"This instrument grants a limited exemption allowing certain commercial drone operators (AUS members with a remote pilot licence) to fly in Sydney Harbour’s restricted R405A/B zones, provided they use an approved CASA-linked safety app that registers and authorises flights and enforces strict operational limits.\n\nIt opens the harbour to commercial filming, inspections and surveys under tight safety controls (radio monitoring, fail-safes, single-drone operations, reliable phone coverage) and expires after two years, signalling a trial/interim regime."}},"importantCases":[],"_links":{"self":"/api/acts/casa-67-24-operation-of-rpa-in-sydney-harbour-restricted-areas-r405a-and-r405b-casa-verified-drone-s","history":"/api/acts/casa-67-24-operation-of-rpa-in-sydney-harbour-restricted-areas-r405a-and-r405b-casa-verified-drone-s/history","analysis":"/api/acts/casa-67-24-operation-of-rpa-in-sydney-harbour-restricted-areas-r405a-and-r405b-casa-verified-drone-s/analysis","conflicts":"/api/acts/casa-67-24-operation-of-rpa-in-sydney-harbour-restricted-areas-r405a-and-r405b-casa-verified-drone-s/conflicts","importantCases":"/api/acts/casa-67-24-operation-of-rpa-in-sydney-harbour-restricted-areas-r405a-and-r405b-casa-verified-drone-s/important-cases","documents":"/api/acts/casa-67-24-operation-of-rpa-in-sydney-harbour-restricted-areas-r405a-and-r405b-casa-verified-drone-s/documents"}}