{"id":"F2025L01653","name":"CASA EX108/25 — Operation of RPA Near People and BVLOS (Emergency Service Operations) Exemption 2025","slug":"casa-ex108-25-operation-of-rpa-near-people-and-bvlos-emergency-service-operations-exemption-2025","collection":"legislative_instrument","jurisdiction":"commonwealth","status":"in_force","isInForce":true,"actNumber":null,"makingDate":null,"administeringDepartment":null,"currentVersion":{"id":107588,"registerId":"commonwealth-F2025L01653-current","compilationNumber":null,"startDate":"2026-04-03","status":"InForce","reasons":null,"registeredAt":null},"sections":[{"sectionNumber":"1","sectionType":"section","heading":"CASA EX108/25 — Operation of RPA Near People and BVLOS (Emergency Service Operations) Exemption 2025","content":"Instrument number CASA EX108/25\n\nI, steven James campbell, Executive Manager, National Operations & Standards, a delegate of CASA, make this instrument under regulations 11.160 and 11.205 of the Civil Aviation Safety Regulations 1998.\n\n\\[Signed S. Campbell\\]\n\nSteven Campbell  \nExecutive Manager, National Operations & Standards\n\n23 December 2025\n\nCASA EX108/25 — Operation of RPA Near People and BVLOS (Emergency Service Operations) Exemption 2025\n\n1 Name of instrument\n\nThis instrument is CASA EX108/25 — Operation of RPA Near People and BVLOS (Emergency Service Operations) Exemption 2025.\n\n1A Duration\n\nThis instrument:\n\n(a) commences on the day after it is registered; and\n\n(b) is repealed at the end of 30 November 2028.\n\n2 Definitions, etc.\n\n(1) In this instrument, unless the contrary intention appears:\n\n> Annex B means the document titled Annex B: Integrity and assurance levels for the mitigations used to reduce the intrinsic Ground Risk Class, edition 2.5, published on 13 May 2024 by The Joint Authorities for Rulemaking on Unmanned Systems, as it exists from time to time.\n\n> approved parachute recovery system means:\n\n(a) a parachute recovery system mentioned in clause 6 of Schedule 1; or\n\n(b) another parachute recovery system approved by CASA for the purpose of this instrument.\n\n> BVLOS: see subsection (2).\n\n> CASR means the Civil Aviation Safety Regulations 1998.\n\n> documented practices and procedures has the meaning given by the Part 101 Manual of Standards.\n\n> Note Documented practices and procedures must be approved by CASA. If a further significant change is required after such an approval has been given, the documented practices and procedures must be reapproved if they are to comply with the definition.\n\n> emergency service RPA operation means an operation by an emergency service RPA operator involving an RPA that is for:\n\n(a) law enforcement purposes using the RPA; or\n\n(b) the purpose of saving or protecting persons, property or the environment using the RPA.\n\n> emergency service RPA operator means one of the following organisations, that is an RPA operator that may lawfully conduct an emergency service RPA operation:\n\n(a) a police force or service;\n\n(b) the Australian Defence Force;\n\n(c) the Australian Maritime Safety Authority;\n\n(d) the Australian Border Force;\n\n(e) a State or Territory fire service;\n\n(f) a State or Territory emergency service;\n\n(g) a State or Territory parks, wildlife, or forestry service;\n\n(h) a State, Territory or Commonwealth lifeguard service.\n\n> gathering, in relation to a group of people, means a group of people in close proximity, in circumstances where:\n\n(a) there is limited free or open ground between people; and\n\n(b) if an RPA flying over the group was to fail, the RPA would have a very high likelihood of impacting a person due to the density of people and their inability to freely move away from the RPA.\n\n> Note A gathering may include groups of people at a beach, park, local event, birthday party or wedding.\n\n> High M2, in relation to an approved parachute recovery system, means that CASA has approved the parachute recovery system, either in writing or by publication on its website, as suitable for use in mitigation measures classified in Annex B as “M2 High Integrity and Assurance”.\n\n> independent flight termination system, in respect of a relevant RPA, means a system fitted to the RPA that:\n\n(a) is independent to the RPA’s control system; and\n\n(b) can be activated through an independent control link; and\n\n(c) when activated, immediately activates a flight termination system that stops the RPA flight.\n\n> Note Flight termination can be achieved through a controlled descent, motor kill function, deep stall or other means.\n\n> major gathering or organised event means an organised or advertised event, generally with a high level of public interest, in circumstances where:\n\n(a) a significant number of people have assembled in a specific location for a common purpose; and\n\n(b) there is limited free or open ground between people; and\n\n(c) if an RPA flying over the event was to fail, it would have a very high likelihood of impacting a person at the event.\n\n> Example An outdoor concert, festival, sporting event and spontaneous public assemblies such as a large protest or rally.\n\n> Medium M2, in relation to an approved parachute recovery system, means that CASA has approved the parachute recovery system, either in writing or by publication on its website, as suitable for use in mitigation measures classified in Annex B as “M2 Medium Integrity and Assurance”.\n\n> police force or service means a police force or a police service, for the Commonwealth, a State or a Territory, that is:\n\n(a) established by or under an Act of the Commonwealth Parliament, the State Parliament or the Territory Legislative Assembly; and\n\n(b) the holder of a remotely piloted aircraft operator certificate under Part 101 of CASR.\n\n> relevant event has the meaning given by section 9.02 of the Part 101 Manual of Standards, as if the reference to a manned aircraft is a reference to an RPA.\n\n> relevant operation means the use of a relevant RPA for the purpose of an emergency service RPA operation.\n\n> relevant RPA means:\n\n(a) a Type A RPA;\n\n(b) a Type B RPA;\n\n(c) a Type C RPA;\n\n(d) a Type D RPA;\n\n(e) a Type E RPA;\n\n(f) a Type F RPA.\n\n> remote pilot means an employee or member of an emergency service RPA operator who:\n\n(a) is:\n\n(i) the holder of a remote pilot licence; or\n\n(ii) a person who is taken to hold a remote pilot licence under subregulation 202.461(3) of CASR; and\n\n(b) is the pilot in control of a relevant RPA; and\n\n(c) is acting at the direction of their RPA operator in a relevant operation; and\n\n(d) has such other qualifications and experience relevant to operating a relevant RPA as must be specified in the documented practice and procedures of the emergency service RPA operator.\n\n> RPA operator means an emergency service RPA operator that is the holder of a remotely piloted aircraft operator’s certificate issued by CASA.\n\n> shield means a solid physical barrier (other than a moving vehicle) that:\n\n(a) lies between a person and a relevant RPA in flight or in the hover under this instrument; and\n\n(b) is not moving or flexing in any direction; and\n\n(c) is of such dimensions, structure, strength and substance as to prevent:\n\n(i) the RPA from impacting any person; and\n\n(ii) any debris resulting from an impact of the RPA with the barrier from impacting any person; and\n\n(d) is not likely to lose any of the characteristics mentioned in paragraphs (a) to (c) during the course of an RPA operation.\n\n> Note The shield must be appropriate to withstand the particular impact of the RPA that is being operated in the relevant operation.\n\n> Type A RPA means a micro RPA.\n\n> Type B RPA means a multirotor, very small RPA with a maximum distance between rotor blade tips of 1 m.\n\n> Type C RPA means a multirotor, small RPA with a gross weight of no more than 5 kg and a maximum distance between rotor blade tips of 1.7 m.\n\n> Type D RPA means a multirotor, small RPA with a gross weight above 5 kg but no more than 10 kg and a maximum distance between rotor blade tips of 3 m.\n\n> Type E RPA means a multirotor, small RPA with a gross weight above 10 kg and a maximum distance between rotor blade tips of 3 m.\n\n> Type F RPA means a small RPA:\n\n(a) of the aeroplane or powered-lift category; and\n\n(b) with a maximum distance between rotor blade tips of 3 m; and\n\n(c) fitted with an independent flight termination system.\n\n(2) In this instrument, an RPA is operated beyond visual line of sight (BVLOS) of the person operating the RPA if it is not operated within the visual line of sight of the person.\n\n(3) In this instrument, unless the contrary intention appears, terms and expressions that are not otherwise defined in this section, have the same meaning as they have in or under the Civil Aviation Act 1988 and its regulations.\n\n3 Application\n\n(1) This instrument applies, according to its terms, to each of the following for a relevant operation:\n\n(a) an RPA operator;\n\n(b) the RPA operator’s remote pilot.\n\n(2) This instrument applies to training for a relevant operation as if the training were a relevant operation.\n\n4 Exemptions\n\n(1) When conducting a relevant operation, an RPA operator and the remote pilot are each exempted from compliance with the following provisions of Part 101 of CASR, as applicable:\n\n(a) regulation 101.073 (for BVLOS);\n\n(b) regulation 101.095 (for weather, and day only, limitations);\n\n(c) regulation 101.245 (for operations near people);\n\n(d) regulation 101.250 (in respect of very small or small RPAs operating near populous areas)\n\n(e) regulation 101.280 (for operations over a populous area);\n\n(f) paragraph 101.300(4)(b) (for certain remote pilot licence conditions);\n\n(g) subregulation 101.300(6), but only in respect of paragraph 101.300(4)(b) (concerning offences).\n\n(2) The exemptions in subsection (1) are subject to the conditions that are mentioned in Schedule 1.\n\n(3) The exemptions in subsection (1) cease to be in force at the end of the day that is 12 months after the day on which this instrument is registered.\n\nSchedule 1 Conditions\n\n1 General\n\nTo have the benefit of an exemption under this instrument, it is a condition that each requirement mentioned in this Schedule must be complied with for the relevant operation.\n\n2 Documented practices and procedures\n\n2.1 The RPA operator must not conduct an emergency service RPA operation unless CASA has approved the RPA operator’s documented practices and procedures in respect of the emergency services RPA operation.\n\n2.2 The RPA operator must ensure that the RPA operator’s documented practices and procedures include the following:\n\n(a) a schedule of the relevant RPA to be used for relevant operations, which includes details of the following:\n\n(i) the make and model of each relevant RPA;\n\n(ii) the configuration of each relevant RPA;\n\n(iii) confirmation of the gross weight of each relevant RPA;\n\n(b) equipment specifications and procedures for detecting crewed aircraft within 5 nautical miles of a relevant RPA, including procedures for evading the aircraft;\n\n(c) if a relevant RPA is to be operated around crewed aircraft, procedures regarding traffic coordination between the relevant RPA and crewed aircraft;\n\n(d) if a relevant RPA is to be operated from a remote operating centre, operating requirements and procedures for the remote operating centre;\n\n(e) procedures for operating a relevant RPA beyond visual line of sight that address:\n\n(i) specific requirements for the operating area; and\n\n(ii) flight planning and operational area assessment details, including procedures for operating a relevant RPA over a populous area, and criteria for when an area can be considered a controlled ground area; and\n\n(iii) operating procedures for normal and abnormal circumstances, including navigation, operating at night, operating in non-VMC conditions and procedures for ground observation;\n\n(f) procedures for the training and testing of relevant individuals in relation to conducting a relevant operation;\n\n(g) procedures for making and retaining records of the matters mentioned in paragraph (f);\n\n(h) how, for all for relevant operations, risk assessments are to be conducted, documented, made available to relevant individuals, and retained;\n\n(i) minimum requirements for the deployment of each type of relevant RPA;\n\n(j) a copy of this exemption instrument.\n\n2.3 The RPA operator must ensure that any relevant operation is conducted in accordance with the RPA operator’s documented practices and procedures.\n\n2.4 In the event of conflict or inconsistency between anything in this instrument and the documented practices and procedures, this instrument prevails.\n\n3 Altitude limits\n\nThe remote pilot of a relevant RPA must ensure that, during a relevant operation, the relevant RPA does not exceed the following altitudes:\n\n(a) in the case of a relevant RPA operated within visual line of sight, 400 ft AGL;\n\n(b) in the case of a relevant RPA operated beyond visual line of sight:\n\n(i) 300 ft AGL if the RPA is operated during the day; and\n\n(ii) 400 ft AGL if the RPA is operated at night.\n\n4 RPA Speed limits\n\nBefore using a relevant RPA mentioned in column 2 of Table 4 in a relevant operation, an RPA operator must ensure that the RPA is configured not to exceed the corresponding speed mentioned in column 3 of Table 4.\n\nTable 4 — Relevant RPA maximum speeds\n\n| Column 1Item | Column 2Type of RPA | Column 3Speed |\n| ------------ | ------------------- | ------------- |\n| 1            | Type A RPA          | 25 m/sec      |\n| 2            | Type B RPA          | 25 m/sec      |\n| 3            | Type C RPA          | 18.75 m/sec   |\n| 4            | Type D RPA          | 35 m/sec      |\n| 5            | Type E RPA          | 35 m/sec      |\n| 6            | Type F RPA          | 35 m/sec      |\n\n5 Operational limits based on population density of operating area\n\n5.1 A relevant RPA must not be operated in an area described in column 2 of Table 5 unless the RPA is mentioned in the corresponding column 3 or column 4 of Table 5.\n\n5.2 A relevant RPA mentioned in column 4 of Table 5 must not be operated in an area described in the corresponding column 2 of Table 5 unless the RPA operator has ensured that the conditions underneath the RPA mentioned in column 4 of Table 5 are complied with.\n\nTable 5 — Operating area density and the types of RPA that may be used\n\n| Column 1Item | Column 2Description of operating area                                                                                                                 | Column 3Type of RPA that may be used in the area             | Column 4Type of RPA that may be used in the area, subject to further conditions                                                                                                                                                                                                                                                                                                                 |\n| ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| 1            | A controlled ground area, including areas under an emergency services cordon or evacuation order                                                      | Type A RPAType B RPAType C RPAType D RPAType E RPAType F RPA |                                                                                                                                                                                                                                                                                                                                                                                                 |\n| 2            | An area over or within a forest, desert, or large farm parcel, with limited habitable dwellings (e.g. not more than 1 small building every square km) | Type A RPAType B RPAType C RPAType D RPAType E RPAType F RPA |                                                                                                                                                                                                                                                                                                                                                                                                 |\n| 3            | An area over or within 500 m of small farms and residential areas with very large lot sizes (approximately 4 acres or larger)                         | Type A RPAType B RPAType C RPA                               | Type D RPA(a) must not operate BVLOS unless fitted with a Medium M2 approved parachute recovery systemType E RPA(a) must not operate BVLOS; and(b) RPA must be fitted with a Medium M2 approved parachute recovery system; and(c) a visual observer must be used in respect of the area on the ground directly below the RPA to assist avoiding areas containing groups of people               |\n| 4            | An area over or within 500 m of a suburban area                                                                                                       | Type A RPA                                                   | Type B RPA, Type C RPA(a) must not operate BVLOS unless fitted with a Medium M2 approved parachute recovery systemType D RPA(a) must not operate BVLOS; and(b) RPA must be fitted with a Medium M2 approved parachute recovery system; and(c) a visual observer must be used in respect of the area on the ground directly below the RPA to assist avoiding areas containing groups of people   |\n| 5            | An area over or within 500 m of an urban area                                                                                                         | Type A RPA                                                   | Type B RPA, Type C RPA(a) must not operate BVLOS unless fitted with a High M2 approved parachute recovery system; and(b) must not operate within visual line of sight unless:(i) fitted with a Medium M2 approved parachute recovery system; and(ii) a visual observer is used in respect of the area on the ground directly below the RPA to assist avoiding areas containing groups of people |\n\n6 Approved parachute recovery systems\n\n6.1 Subject to subclause 6.2, a relevant RPA must be fitted with an approved parachute recovery system as follows:\n\n(a) for a Type B RPA that is a DJI Mavic, the applicable ParaZero SafeAir parachute recovery system;\n\n(b) for a Type C RPA that is a DJI M30/T, an AVSS PRS-M30 parachute recovery system;\n\n(c) for a Type D RPA that is a DJI Matrice 300 RTK:\n\n(i) a ParaZero SafeAir M-300 Pro parachute recovery system; or\n\n(ii) a ParaZero SafeAir M-350 Pro parachute recovery system.\n\n6.2 An approved parachute recovery system must not be fitted to a relevant RPA in relation to a relevant operation in an area described in column 2 of Table 5 unless the parachute recovery system has the Medium M2 or High M2 approval mentioned in the corresponding column 4 of Table 5.\n\n6.3 A relevant RPA may be fitted with an approved parachute recovery system that is not mentioned in subclause 6.1, if the system has been approved by CASA, either in writing or by publication on its website, in respect of the relevant RPA.\n\n7 Geofencing and independent flight termination system\n\n7.1 A relevant RPA that is not a Type A RPA must not be operated unless an electronic geofence is in place to restrict the RPA from exiting the operational area.\n\n7.2 A Type B, Type C or Type D RPA must not be operated within 1 km of an event or gathering with more than 40 000 people unless it is fitted with an independent flight termination system.\n\n> Note\n\n All Type F RPAs are required to be fitted with an independent flight termination system: see the definition of Type F RPA in section 2.\n\n8 Safe separation requirements\n\n8.1 A relevant RPA that is not a Type A RPA must not be operated within 15 m of a person unless:\n\n(a) the person has consented to the operation of the RPA within that distance; or\n\n(b) the RPA has no exposed rotors and is travelling at a speed that the remote pilot reasonably considers is low enough to minimise the risk of impact injuries; or\n\n(c) the person is shielded.\n\n8.2 A relevant RPA that is not a Type A RPA, or a Type B or Type C RPA fitted with a High M2 approved parachute recovery system, must not be operated over a gathering of people.\n\n8.3 A relevant RPA that is not a Type A RPA, or a Type B RPA fitted with a High M2 approved parachute recovery system, must not be operated over a crowd of people at a major gathering or organised event.\n\n8.4 A remote pilot who operates Type A RPA, or a Type B RPA fitted with a High M2 approved parachute recovery system, over a crowd of people at a major gathering or organised event must, as far as is practicable, avoid sustained overflight over the people.\n\n8.5 A relevant RPA must not be operated over a moving vehicle, except in circumstances where the RPA is:\n\n(a) a Type A or Type B RPA; or\n\n(b) a Type C RPA that is operating in a controlled ground area and the remote pilot reasonably considers that it is necessary in the context of the emergency operation.\n\n9 Airspace and traffic risk management\n\n9.1 A relevant RPA must not be operated beyond visual line of sight:\n\n(a) within 5 nautical miles of a controlled aerodrome; or\n\n(b) within 5 nautical miles of a non-controlled aerodrome during a relevant event; or\n\n(c) within the no-fly area of a non-controlled aerodrome, unless a requirement mentioned in subclause 9.2 is met.\n\n9.2 For paragraph 9.1(c), the requirements are one or more of the following:\n\n(a) the aerodrome is a “prior permission required” aerodrome, and the remote pilot has received confirmation from the aerodrome operator that no aircraft movements are expected;\n\n(b) the RPA operator has visually confirmed that no crewed aircraft are in the vicinity of the aerodrome;\n\n(c) the relevant operation occurs during the hours of night when ADS-B within 10 nautical miles of the aerodrome is monitored;\n\n(d) the relevant RPA is operated within a separation distance from crewed aircraft of 1 000 ft vertically or 1 500 m horizontally, unless a different separation distance has been coordinated with the aerodrome operator.\n\n9.3 A relevant RPA must not be operated beyond visual line of sight in the vicinity of published VFR routes, near aerodromes in areas where crewed aircraft movements below 500 ft AGL are expected unless a NOTAM has been published in respect of the operation of the relevant RPA.\n\n9.4 A relevant RPA must not be operated beyond visual line of sight at an altitude higher than 200 ft AGL unless:\n\n(a) the RPA operator is monitoring ADS-B and aeronautical radio in the relevant area; and\n\n(b) in the case of operations in non-controlled airspace, the remote pilot makes aeronautical radio broadcasts of the position of the RPA:\n\n(i) at the time of launching the RPA; and\n\n(ii) at any other time the remote pilot considers it necessary to facilitate separation from other aircraft.\n\n10 Data collection and reporting to CASA\n\n10.1 The RPA operator must retain records of the following in relation to a relevant operation:\n\n(a) flight logs;\n\n(b) telemetry data;\n\n(c) training records for the remote pilots;\n\n(d) maintenance details for the relevant RPA used in the operation;\n\n(e) reports of any incidents or accidents;\n\n(f) details of any parachute deployments;\n\n(g) details of any deviation from the RPA operator’s documented practices and procedures;\n\n(h) details of any NOTAMs caused to be published in respect of a relevant operation.\n\n10.2 If a serious incident or accident, involving damage to property or a person, occurs during a relevant operation, the RPA operator must provide a written report to CASA within 24 hours of the incident or accident.\n\n10.3 The RPA operator must submit written reports to CASA at regular intervals of no less than 3 months, starting from the commencement of this instrument and ending 3 months after the exemptions in subsection 4(1) cease to be in force, that contain the following details regarding relevant operations during the reporting period:\n\n(a) total number of flights;\n\n(b) any incidents that occurred;\n\n(c) parachute deployments;\n\n(d) any deviations from the RPA operator’s documented practices and procedures that occurred.\n\n10.4 The RPA operator must make the records mentioned in subclause 10.1 available for inspection by CASA on request.\n\n11 CASA observers\n\nAn RPA operator that has used, or that intends to use, this instrument must make arrangements, on written request by an Executive Manager of CASA, for a CASA officer to observe a relevant operation at CASA’s expense.","sortOrder":0}],"analysis":{"kimi_summary":{"content_quality":"ok","complexity_score":7,"scope_assessment":{"changed":false,"description":"The instrument appears tightly scoped to its original purpose. It specifically targets emergency service operations with defined operational parameters (law enforcement, saving life/property/environment) and applies only to certified emergency service RPA operators. The detailed technical requirements (Type A-F classifications, specific parachute models, density-based operational matrices) suggest a precision-targeted regulatory instrument rather than scope creep. There is no evidence of expansion into commercial, recreational, or non-emergency government operations."},"complexity_factors":["Extensive defined terms section with 18+ specific definitions including technical classifications (Type A through Type F RPA), integrity levels (High M2, Medium M2), and operational concepts (shield, gathering, controlled ground area)","Nested conditional logic throughout Schedule 1, particularly in Table 5 where operating area density determines permissible RPA types, which in turn trigger further equipment requirements (parachute systems) and operational conditions (visual observers)","Cross-references to external documents (Annex B from JARUS, Part 101 Manual of Standards, Civil Aviation Act 1988) and specific product models (DJI Mavic, M30/T, Matrice 300 RTK) with approved parachute systems","Multiple interacting limitation systems: altitude limits vary by VLOS/BVLOS and day/night; speed limits vary by RPA type; population density restrictions vary by area type and RPA type; separation requirements vary by RPA type and equipment fitted","Exception to exception structure in section 8 (safe separation) where general prohibitions have multiple conditional exceptions, and specific RPA types with specific equipment create further carve-outs","Temporal complexity with different expiry dates for the instrument itself (30 November 2028) versus the exemptions (12 months after registration)","Dual compliance framework requiring both adherence to this instrument AND approved 'documented practices and procedures' with hierarchy rules for conflicts"],"plain_english_summary":"**What this legislation does:**\n\nThis instrument grants emergency services special permission to fly drones (called **RPAs** — Remotely Piloted Aircraft) in situations that would normally be illegal under standard aviation rules. It lets police, fire services, ambulance, defence forces, and similar organisations fly drones **near people**, **over populated areas**, and **beyond what the pilot can see** (BVLOS — Beyond Visual Line of Sight), provided they follow strict safety conditions.\n\n**Who it affects:**\n\n*   **Emergency service organisations** listed in the instrument (police, fire, ambulance, defence, border force, lifeguards, etc.) who hold a drone operator certificate from CASA.\n*   **Remote pilots** working for these organisations who hold (or are deemed to hold) a remote pilot licence.\n*   **The general public** — because it allows drones to operate closer to people and property than usual, but only for emergency purposes like search and rescue, firefighting, or law enforcement.\n\n**Why it matters:**\n\nNormally, drone laws are very restrictive about flying near people or where the pilot can't see the drone. This exemption recognises that emergency services often need to operate in dangerous, crowded, or complex environments where normal rules would prevent them from doing their job. For example:\n\n*   Searching for a missing bushwalker in dense bushland (BVLOS).\n*   Monitoring a bushfire in a suburban area.\n*   Providing aerial surveillance during a large public event or natural disaster.\n\n**Key conditions and safeguards:**\n\nThe exemption comes with heavy strings attached:\n\n*   **Pre-approval required:** Emergency services must have their operating procedures approved by CASA before they can use these exemptions.\n*   **Equipment requirements:** Depending on the drone size and where it's flying, it may need **parachute recovery systems** (to safely land if something goes wrong), **geofencing** (electronic boundaries), and **independent flight termination systems** (a kill switch separate from the main controls).\n*   **Speed and altitude limits:** Strict caps apply — generally 400 feet above ground level, with lower limits for BVLOS operations during the day.\n*   **Population density rules:** The bigger the drone and the more crowded the area, the more safety equipment required. For example, flying over urban areas requires high-integrity parachute systems.\n*   **Separation from people:** Drones generally cannot fly within 15 metres of people unless the person consents, is shielded, or the drone has no exposed rotors and is moving slowly.\n*   **Airspace restrictions:** Cannot fly BVLOS near airports without specific safety measures, and must monitor aircraft traffic.\n*   **Record keeping and reporting:** Operators must keep detailed flight logs, maintenance records, and incident reports, and submit regular reports to CASA every 3 months.\n*   **Sunset clause:** The exemptions automatically expire 12 months after registration (though the instrument itself lasts until November 2028, the exemptions are shorter-term).\n\n**In short:** This is a controlled relaxation of drone safety rules specifically for emergency responders, balancing operational necessity against public safety through detailed technical requirements and oversight."},"summary":{"content_quality":"ok","complexity_score":4,"scope_assessment":{"changed":false,"description":"New exemption instrument granting conditional relief to emergency service RPA operators from certain CASR Part 101 requirements for operations near people and beyond visual line of sight."},"complexity_factors":["Multiple cross-references to CASR regulations, Manual of Standards and industry technical standards (Annex B)","Detailed tables linking RPA type, operating area density and required mitigation systems (Medium M2/High M2 parachute recovery)","Layered conditional requirements involving approved documented procedures, geofencing, independent flight termination, and observer use","Interaction between temporary exemption, instrument repeal date and annual expiry of the exemption provisions"],"plain_english_summary":"CASA EX108/25 is a temporary exemption for emergency service drone (RPA) operators. It allows police, fire, state emergency services, the Australian Defence Force, Australian Border Force, AMSA, parks and wildlife services, and Commonwealth/State lifeguard services to fly remotely piloted aircraft closer to people and beyond the pilot’s visual line of sight (BVLOS) when conducting law enforcement, life-saving or environmental protection operations. Without this instrument, certain provisions in Part 101 of the Civil Aviation Safety Regulations 1998 (CASR) would prohibit these flights.\n\nThe exemption starts the day after registration and the flight privileges end 12 months later, though the instrument itself is repealed on 30 November 2028. To rely on it, the operator must hold a remotely piloted aircraft operator’s certificate and have CASA-approved documented practices and procedures covering drone types, crewed aircraft detection, night operations, risk assessments and training.\n\nStrict conditions apply. Altitude is capped (400 ft AGL within visual line of sight, 300 ft AGL during day BVLOS, 400 ft AGL at night BVLOS). Speed limits range from 25 m/s for micro RPAs to 35 m/s for larger types. Where a drone may be flown depends on population density: in controlled ground areas (e.g., under an emergency cordon) and remote areas all listed drone types may operate; over suburban or urban areas only micro RPAs may fly freely, while small multirotor RPAs require an approved parachute recovery system (rated Medium M2 or High M2 integrity) and may need a visual observer. Safe separation rules include staying at least 15 m from a person unless shielded or consented, no overflight of gatherings without a high-integrity parachute, and no overflight of major events except by the smallest types. BVLOS operations are restricted near aerodromes unless certain conditions, such as air traffic monitoring or coordination, are met.\n\nOperators must keep records of flights, incidents, maintenance and training, report serious incidents to CASA within 24 hours, and submit quarterly summary reports. The instrument balances operational flexibility for emergency services with engineered and procedural safeguards to manage ground and air risks."},"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-ex108-25-operation-of-rpa-near-people-and-bvlos-emergency-service-operations-exemption-2025","history":"/api/acts/casa-ex108-25-operation-of-rpa-near-people-and-bvlos-emergency-service-operations-exemption-2025/history","analysis":"/api/acts/casa-ex108-25-operation-of-rpa-near-people-and-bvlos-emergency-service-operations-exemption-2025/analysis","conflicts":"/api/acts/casa-ex108-25-operation-of-rpa-near-people-and-bvlos-emergency-service-operations-exemption-2025/conflicts","importantCases":"/api/acts/casa-ex108-25-operation-of-rpa-near-people-and-bvlos-emergency-service-operations-exemption-2025/important-cases","documents":"/api/acts/casa-ex108-25-operation-of-rpa-near-people-and-bvlos-emergency-service-operations-exemption-2025/documents"}}