{"id":"F2024L01450","name":"CASA 66/24 — Operation of RPA Within 3 Nautical Miles of a Controlled Aerodrome (CASA-Verified Drone Safety App) Instrument 2024","slug":"casa-66-24-operation-of-rpa-within-3-nautical-miles-of-a-controlled-aerodrome-casa-verified-drone-sa","collection":"legislative_instrument","jurisdiction":"commonwealth","status":"in_force","isInForce":true,"actNumber":null,"makingDate":null,"administeringDepartment":null,"currentVersion":{"id":105442,"registerId":"commonwealth-F2024L01450-current","compilationNumber":null,"startDate":"2026-04-03","status":"InForce","reasons":null,"registeredAt":null},"sections":[{"sectionNumber":"1","sectionType":"section","heading":"CASA 66/24 — Operation of RPA Within 3 Nautical Miles of a Controlled Aerodrome (CASA-Verified Drone Safety App) Instrument 2024","content":"Instrument number CASA 66/24\n\nI, PAUL HIBBERD, National Manager, Emerging Technologies & Regulatory Change, National Operations & Standards Division, a delegate of CASA, make this instrument under regulations 11.245 and 101.030 of the Civil Aviation Safety Regulations 1998, and subsection 4.03 (7) of the Part 101 Manual of Standards.\n\n\\[Signed P. Hibberd\\]\n\nPaul Hibberd  \nNational Manager, Emerging Technologies & Regulatory Change  \nNational Operations & Standards Division\n\n13 November 2024\n\nCASA 66/24 — Operation of RPA Within 3 Nautical Miles of a Controlled Aerodrome (CASA-Verified Drone Safety App) Instrument 2024\n\n1 Name\n\nThis instrument is CASA 66/24 — Operation of RPA Within 3 Nautical Miles of a Controlled Aerodrome (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 30 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 30 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, AGL, air traffic control, controlled aerodrome, military aerodrome, Part 101 Manual of Standards, remote pilot licence, RPA and RPAS.\n\nIn this instrument:\n\n> ADS-B means automatic dependent surveillance – broadcast.\n\n> approved area has the meaning given by regulation 101.236 of CASR.\n\n> ATC means air traffic control.\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> measurement point 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 a relevant approved area, in which an RPA may be operated under subsection 4.03 (7) of the Part 101 Manual of Standards.\n\n> relevant approved area means an area approved under section 4.\n\n> relevant controlled aerodrome means a controlled aerodrome that is not a military aerodrome.\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 Approval\n\n1.  On application made by Airservices Australia, ARN 202210, under subregulation 101.030(1) of CASR, CASA approves each area described in subsection (2) as an area for the operation of RPA.\n2.  For subsection (1), the area consists of any areas and airspace that are:\n\n(a) below 400 ft AGL; and\n\n(b) within 3 nautical miles, in any direction, from the measurement point of any runway of a relevant controlled aerodrome.\n\n> Note The areas and airspace described in subsection (2) accord with the areas and airspace described in paragraph (a) of the definition of no-fly zone of a controlled aerodrome in section 4.02 of the Part 101 Manual of Standards.\n\n1.  The operation of an RPA by a remote pilot in a relevant approved 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) subject to subsection (5), take reasonable steps to ensure that:\n\n(i) reliable VHF coverage exists in the operating area, which would allow the pilot to communicate with ATC; and\n\n(ii) a listening watch is maintained on the relevant ATC frequency for the operating area, 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; and\n\n(d) comply with any ATC direction in relation to the operation.\n\n> Note: Examples For paragraph (d), the direction could be to temporarily move the location of the operation within the operating area or temporarily cease the operation.\n\n(5) Paragraph (4)(b) does not apply if the pilot is operating the RPA within 100 metres laterally from, and below, an obstacle, other than an aircraft.\n\n(6) If during the RPA operation, the RPA leaves the operating area, whether or not under the pilot’s control, the pilot must notify ATC of the event immediately after the happening of the event.\n\n(7) The pilot must not transmit on the relevant ATC frequency for the operating area, during the RPA operation, unless:\n\n(a) directed by ATC to do so; or\n\n(b) the pilot does so to give a notification to ATC under subsection (6).\n\n(8) 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(9) Unless directed by ATC to do so, the pilot must not, during the RPA operation, activate:\n\n(a) any transponder fitted to the RPA; or\n\n(b) the transmission of ADS-B position information by the RPA.\n\n(10) 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":{"kimi_summary":{"content_quality":"ok","complexity_score":5,"scope_assessment":{"changed":false,"description":"This instrument appears tightly scoped to its original purpose. It creates a specific exemption mechanism for drone operations near controlled aerodromes using verified apps, which aligns with CASA's broader regulatory trajectory toward risk-based and technology-enabled aviation safety. The scope has not expanded beyond the stated purpose of enabling app-verified operations within 3NM of airports under subsection 4.03(7) of the Part 101 MOS."},"complexity_factors":["Multiple nested definitions referencing external documents (Part 101 Manual of Standards, CASR regulations)","Conditional logic in operating requirements (e.g., subsection 5 creates an exception to the radio contact requirement in subsection 4(b))","Cross-references to 5 separate regulatory instruments (Civil Aviation Act 1988, CASR, Part 101 MOS, plus specific regulations 11.245, 101.030, 101.236, 101.335, 202.461)","Dual pathways for compliance (operator registration vs. personnel membership in subsection 5(1))","Technology-dependent compliance (requires specific app ecosystem, mobile coverage, ADS-B, VHF radio, fail-safe modes)","Temporal limitation with automatic sunset clause (ceases 30 November 2026)","Hierarchy of compliance conflict resolution (section 5(10) establishes precedence of instrument directions over operator procedures)"],"plain_english_summary":"This instrument lets licensed commercial drone pilots operate below 400 ft within 3 nautical miles of civilian airport runways — normally banned — but only when registered and authorised through a CASA‑verified drone safety app linked to CASA’s platform and under strict ATC coordination and operational limits.  \n\nIt affects commercial RPA operators, Airservices Australia, and app developers, and serves as a time‑limited (to Nov 2026) trial in digital, dynamic airspace management."},"flash_summary":{"complexity_score":7,"scope_assessment":{"changed":true,"description":"Yes. The instrument conditionally authorises RPA operations within airspace described in s4(2) (below 400 ft AGL and within 3 nautical miles of measurement points of runways at relevant controlled aerodromes), which the instrument notes correspond to areas described as a controlled-aerodrome no‑fly zone in the Part 101 Manual of Standards. It therefore converts that previously described no‑fly area into a relevant approved area for conditional use (s4(2) and accompanying note), limited in time (s2) and subject to the registration and operational conditions in section 5."},"complexity_factors":["Time-limited, temporary instrument (commencement and automatic repeal dates) creates a fixed compliance window (s2).","Approves operation inside areas that the instrument notes accord with the 'no-fly zone' definition in the Part 101 Manual of Standards — effectively converting a prohibited area into a conditionally authorised area (s4(2) and accompanying note referencing Part 101 MOS s4.02).","Requires use of a CASA-verified drone safety app and registration through that app to obtain authorisation; ties legal permission to a specific digital platform and listed apps (s3 definitions; s5(1)(a)).","Operating limits are those notified on the app and are binding during the operation, creating variable, app-driven constraints per flight/registration (s5(2)).","Restricts permitted activity to aerial work operations only, narrowing operational scope (s5(3)).","Multiple technical and operational duties: ensure reliable VHF and mobile coverage, maintain a listening watch on ATC frequency, comply with ATC directions, with an exception near obstacles (s5(4)–(5), (4)(d)).","Immediate ATC notification if the RPA leaves the operating area; limited transmission rights on ATC frequency except as directed or for that notification (s5(6)–(7)).","Detailed fail-safe requirement specifying altitude adjustment, transit to pre-defined safe landing/termination area, and landing/end of flight on data-link loss — imposes technical design/operational obligations (s5(8)).","Prohibits activating transponders or ADS-B transmission unless directed by ATC, affecting equipment use and detection modalities (s5(9)).","Express override: where an RPA operator’s documented practices and procedures conflict with these directions, the directions prevail, shifting decision authority to CASA’s instrument (s5(10)).","Cross-references multiple instruments and standards (CASR regs, Part 101 Manual of Standards) so compliance depends on interpreting interlocking texts (instrument preamble, s3 definitions)."],"plain_english_summary":"This instrument temporarily authorises remotely piloted aircraft (drones/RPA) to operate below 400 ft AGL within 3 nautical miles of non‑military controlled aerodromes, subject to specified conditions and use of a CASA‑verified drone safety app. It runs from 16 November 2024 until 30 November 2026.\n\nRemote pilots and certified RPA operators must register via the verified app, follow app‑notified operating limits, maintain required communications and fail‑safe capability, and notify air traffic control if the RPA leaves the authorised area."},"flash_summary_failed":{"failed":true,"reason":"A positive credit balance is required for all requests, including BYOK, so fallback providers remain available. Add credits at https://vercel.com/d?to=%2F%5Bteam%5D%2F%7E%2Fai%3Fmodal%3Dtop-up to continue.","source":"analysis-cron"}},"importantCases":[],"_links":{"self":"/api/acts/casa-66-24-operation-of-rpa-within-3-nautical-miles-of-a-controlled-aerodrome-casa-verified-drone-sa","history":"/api/acts/casa-66-24-operation-of-rpa-within-3-nautical-miles-of-a-controlled-aerodrome-casa-verified-drone-sa/history","analysis":"/api/acts/casa-66-24-operation-of-rpa-within-3-nautical-miles-of-a-controlled-aerodrome-casa-verified-drone-sa/analysis","conflicts":"/api/acts/casa-66-24-operation-of-rpa-within-3-nautical-miles-of-a-controlled-aerodrome-casa-verified-drone-sa/conflicts","importantCases":"/api/acts/casa-66-24-operation-of-rpa-within-3-nautical-miles-of-a-controlled-aerodrome-casa-verified-drone-sa/important-cases","documents":"/api/acts/casa-66-24-operation-of-rpa-within-3-nautical-miles-of-a-controlled-aerodrome-casa-verified-drone-sa/documents"}}