Radiocommunications (Exemption – Remotely Piloted Aircraft Disruption) Determination 2022

The endnotes are structured around four core concepts: identification and scope of the endnotes (Endnote 1), an abbreviation key (Endnote 2), a legislation-history table (Endnote 3), and an amendment-history table (Endnote 4). Each performs a distinct function in the legal-information workflow of a compiled instrument.

Identification and scope (Endnote 1): the endnotes set out what the compilation includes , information about the compilation and the compiled law. They explicitly state that the endnotes listed (1 to 4) are included in every compilation. This signals to users that the endnotes are intended to be a standardised accompaniment, not ad hoc commentary.

Abbreviation key (Endnote 2): the compilation provides a standardised shorthand for terms used in the endnotes. Examples in the provided key include ad = added or inserted, am = amended, amdt = amendment, rep = repealed, rs = repealed and substituted, F = Federal Register of Legislation, LA = Legislation Act 2003, Pt = Part(s), s = section(s)/subsection(s), and (md not incorp) = misdescribed amendment cannot be given effect. The presence of this key means readers must translate the shorthand to understand amendment-history entries and legislation-history annotations.

Legislation history (Endnote 3): this is a chronological list of amending instruments with registration ID, commencement date, and notes on application, saving and transitional provisions where applicable. In the supplied material, two instruments are recorded with their Federal Register identifiers and commencement dates. The legislation-history entry functions as the primary pointer for readers to follow up on the amending instruments in full, including any transitional or saving provisions omitted from the compilation.

Amendment history (Endnote 4): this provides provision-level detail, showing how specific sections have been affected (for example, rep. LA 48D against s.2). The compilation shows an HTML-formatted table listing affected provisions and how they were affected. The amendment-history table is the granular map for drafters and users who need to know whether particular sections were added, amended, repealed or otherwise modified, and by which instrument (referenced by an identifier).

A further concept running through the endnotes is the treatment of misdescribed amendments. The endnotes state the legal mechanism available: if the misdescription can be given effect as intended, the amendment can be incorporated by an editorial change under s 15V of the Legislation Act 2003; if not, the amendment is not incorporated and is labelled “(md not incorp)”. That rule is the compilation’s operational approach to reconciling drafting errors in amending instruments with the need for an accurate consolidated text.

Finally, the endnotes demonstrate that the compilation is not a standalone legal argument. They are metadata and signposts: they identify amending instruments by registration numbers and commencement dates, but they point readers to those instruments for substantive details omitted from the compilation (application, saving and transitional provisions).

These endnotes chiefly affect users of the compiled instrument and those who rely on compilation metadata to interpret or apply the compiled law. The immediate audience includes legal practitioners (lawyers and public lawyers), parliamentary drafters, legislative publishers, regulatory compliance officers, in-house counsel, courts referencing consolidated texts, and researchers or journalists checking the provenance of a provision. Because the endnotes identify amending instruments by registration and commencement dates, they are also relevant to administrative staff who maintain legal databases, and to technical implementers who convert legislative compilations into searchable databases or machine-readable formats.

Operationally, the parties that must pay attention are:

• Readers relying on the compiled instrument for the current law. The endnotes flag which instruments have amended the text and when those amendments commenced (e.g. Radiocommunications (Exemption - Remotely Piloted Aircraft Disruption) Determination 2022, registered 26 September 2022, commenced 27 September 2022; and Radiocommunications (Low Interference Potential Devices) (Consequential Amendments) Instrument 2025 (No. 1), registered 5 September 2025, commenced 1 October 2025). Users who need the detailed content of those amending instruments must consult them separately.

• Compilers and editors. The endnotes direct editorial practice on how to treat misdescribed amendments, by reference to s 15V of the Legislation Act 2003. Editors must decide whether a misdescribed amendment can be given effect; if so, they may incorporate it via an editorial change; if not, the endnote standard is to mark it “(md not incorp)”.

• Systems and database maintainers. The abbreviation key (Endnote 2) standardises shorthand; indexing and search algorithms need to map the abbreviations to the full meanings. The Federal Register identifiers (F2022L01255, F2025L01049) are critical for programmatic retrieval.

• Practitioners advising on transitional or saving matters. Endnote 3 explicitly states that the legislation history includes information on commencement and details of application, saving or transitional provisions that are not included in the compilation; this signals that advisory work must go to the underlying amending instrument to capture practical effect.

The endnotes do not impose obligations on regulated persons in the sense of operative regulatory duties. They instead affect legal-information workflows: who must verify the provenance of amendments, who must check for misdescribed amendments, and who must consult the cited amending instruments to understand application and transitional arrangements not reproduced in the compilation.

The endnotes themselves do not create substantive statutory duties or rights for regulated parties; they create duties for users of the compilation and for legal-information professionals in relation to verification, interpretation, and editorial treatment.

Duties for users and editors:

• Duty to verify amending instruments: Endnote 3 directs users to the legislation-history entries for information about amending laws, including commencement dates and details of any application, saving or transitional provisions not included in the compilation. Practitioners must therefore consult the instruments identified by their Federal Register identifiers (for example F2022L01255 and F2025L01049) to capture all operative content, as the compilation explicitly does not include some of those particulars.

• Duty to translate abbreviations correctly: Endnote 2 provides the abbreviation key. Users have the implicit duty to apply that key when interpreting shorthand in Endnote 4. For instance, rep. = repealed, am. = amended, (md not incorp) indicates a misdescribed amendment that could not be given effect.

• Duty to apply the misdescribed-amendment rule correctly: Endnote 1 explains that where an amending instrument is misdescribed, an editorial correction may be made under s 15V of the Legislation Act 2003 if the intended effect can be ascertained. Editors compiling or annotating statute must therefore assess whether the intended effect is ascertainable and, if so, can use the editorial power to incorporate the change.

Rights conferred or implied by the compilation process:

• Right to notice of amendment provenance and timing: The legislation-history table (Endnote 3) gives users the right, practically, to know which instruments amended the law and when. This enables users to trace amendment provenance and commencement timing, which is essential for determining the applicable law at particular dates.

• Right to clarity on editorial choices: The amendment-history (Endnote 4) indicates how provisions were affected and records the editorial outcome; where an amendment is misdescribed and not incorporated, it will be marked (md not incorp). This gives users a right to transparency about what editorial decisions were made in preparing the compiled text.

• Right to rely on standard abbreviations: The abbreviation key standardises the language of the endnotes; users can rely on that standardisation to interpret annotations across compilations.

What the endnotes do not provide as duties or rights:

• They do not create enforcement powers, penalties, or compliance obligations for third parties. They do not supersede the original instruments; if there is doubt about application, saving or transitional provisions, the endnotes instruct readers to consult the amending instruments themselves.

In short, the compilation places duties on information-users and editors to verify and apply amendments correctly, and it confers transparency-based rights to trace and understand the history and editorial treatment of amendments.

The endnotes themselves do not prescribe penalties or enforcement mechanisms concerning substantive conduct regulated by the compiled instrument. They are metadata. The material provided contains no sanctioning provisions, infringement regimes, enforcement powers, or penalty schedules. Instead, the endnotes perform an informational and editorial function: they signal which instruments amended the compiled law, provide shorthand to read the amendment-history, and explain the handling of misdescribed amendments. Consequently, any penalties or enforcement actions that apply to conduct regulated by the compiled instrument must be sought in the operative provisions of the compiled instrument or in the instruments listed in the legislation history; those substantive provisions and any penalty clauses are not reproduced in the supplied endnotes.

The endnotes do, however, record procedural choices that can affect legal certainty and hence enforcement practice indirectly. For example:

• Treatment of misdescribed amendments: The endnotes state that if a misdescribed amendment can be given effect, an editorial change under s 15V of the Legislation Act 2003 can incorporate it, otherwise it is marked “(md not incorp)”. This affects enforceability insofar as a compiled text that incorporates a misdescribed amendment by editorial change will present a different textual basis to courts, regulators or litigants than would a compilation that refuses to make the editorial correction. The endnote therefore informs users when to expect editorial alterations versus the retention of the literal amending text.

• Transparency of amendment provenance: The legislation history entries and provision-level amendment-history entries provide the identifiers and commencement dates of amending instruments (for example F2022L01255 and F2025L01049). Proper enforcement or compliance action will require reference to those instruments to determine the precise operative text and commencement details, including any transitional or saving provisions which might postpone or limit enforcement steps.

Because the endnotes do not contain specific penalty provisions, practitioners carrying out enforcement work should treat the endnotes as signposts to locate the substantive text that imposes penalties and enforcement powers. The endnotes’ substantive effect on enforcement is therefore indirect: they affect the reliability and traceability of the compiled text that an enforcement agency, a court, or a litigant will rely upon.

The endnotes are explicitly connected to other legislative instruments and to the Legislation Act 2003. They are designed to be read as an adjunct to the compiled law and to point readers to the amending instruments and to the rules that permit editorial corrections.

Direct interactions recorded in the supplied material:

• Legislation Act 2003 (s 15V): The endnotes reference section 15V of the Legislation Act 2003 as the statutory mechanism that allows editorial incorporation of misdescribed amendments where the intended effect can be given effect by editorial change. This is a procedural cross-reference that governs how compilers treat amending instruments that contain errors in their description of what they amend. The endnotes therefore interact with the Legislation Act 2003 by invoking its editorial correction power as part of the compilation process.

• Amending instruments: The legislation-history table (Endnote 3) lists specific instruments that interact with the compiled instrument. The Radiocommunications (Exemption - Remotely Piloted Aircraft Disruption) Determination 2022 (F2022L01255) and Radiocommunications (Low Interference Potential Devices) (Consequential Amendments) Instrument 2025 (No. 1) (F2025L01049) are recorded with registration and commencement data. Those instruments are the immediate legal authorities that actually change the text of the compiled instrument; the endnotes interact with them by providing identifiers and commencement dates and noting that application, saving or transitional provisions may not be reproduced.

• Federal Register identifiers and official gazetteing: The endnotes use Federal Register identifiers (F2022L01255, F2025L01049). Interaction with the administrative infrastructure of Commonwealth law is implied: users must consult the Federal Register or the published instruments to retrieve the full text of amending instruments and any associated registry metadata (such as commencement notices).

• Internal compilation conventions: The abbreviation key (Endnote 2) interacts with drafting and publication practices by standardising shorthand across compilations. It references common legislative vocabulary (ad, am, rep, rs, Pt, Sch, s, Div, etc.) and thereby aligns the compilation with other legislative publications that use the same conventions.

What the endnotes do not do in terms of interaction:

• They do not displace or modify the substantive content of other Acts or instruments. The endnotes do not themselves amend legislation; they document amendments and, subject to editorial correction rules, can alter the compiled presentation.

• They do not provide the content of saving or transitional provisions; instead they note that such matters are provided in the legislation history entry and must be consulted in the source amending instrument.

Practical implication: whenever a question arises about how a provision operates in relation to other laws, or about the timing of an amendment, the endnotes direct the user to the source instruments and to the Legislation Act’s editorial rules. The interaction is therefore documentary and procedural rather than substantive.

The amendment history is given in Endnote 4 and presents provision-level annotations showing how particular sections of the compiled instrument have been changed. The supplied amendment-history fragment is presented as an HTML table that lists affected provisions and how they were affected.

From the material provided:

• s.2 is recorded as “rep. LA 48D”. The shorthand “rep.” in the abbreviation key (Endnote 2) translates to “repealed” and “LA 48D” appears to be the instrument or amending reference that effected the repeal. The amendment-history thus records that section 2 was repealed by an amending instrument or schedule identified as LA 48D.

• s.4 is recorded as “rep. LA 48C”, indicating that section 4 was repealed by LA 48C. Again, “rep.” is declared in the key as “repealed”.

• s.6 is recorded as “am. F2025L01049”. The abbreviation “am.” maps to “amended” and the Federal Register identifier F2025L01049 is given. This matches the legislation-history entry in Endnote 3 that shows the Radiocommunications (Low Interference Potential Devices) (Consequential Amendments) Instrument 2025 (No. 1) registered 5 September 2025, commenced 1 October 2025, with identifier F2025L01049; the amendment-history indicates that s.6 was amended by that instrument.

The amendment-history table also includes empty rows and formatting blank cells, which suggests either that only a limited set of provision-level changes are recorded in this compilation extract or that additional entries appear elsewhere in the full compilation. The supplied HTML shows the structure used: the left column for provision affected; the right column for how affected, often with a shorthand annotation referencing the amending instrument.

The endnotes also include a separate section describing “Misdescribed amendments” and how they are incorporated. It records that where an amending instrument misdescribes the amendment but the intended effect can be given effect, the misdescribed amendment can be incorporated through an editorial change made under s 15V of the Legislation Act 2003; where it cannot be given effect, the amendment is not incorporated and “(md not incorp)” is added to the amendment history. This procedural rule is part of the amendment-history framework and affects the reading of provision-level changes.

Finally, the legislation-history entries in Endnote 3 function as the upstream source for the amendment-history. Endnote 3 lists the instruments and their Federal Register identifiers (F2022L01255 and F2025L01049), registration and commencement dates, and a note that application, saving and transitional provisions that are not included in this compilation are recorded there. The amendment-history therefore should be read alongside the legislation-history entries to fully understand the provenance, timing and scope of each amendment.

The supplied endnotes do not record any litigation history. There are no cases cited in the endnotes and no references to judicial decisions challenging, interpreting or applying the compiled instrument or any amending instrument. The endnotes are strictly descriptive of the compilation process, the abbreviation conventions, the legislation-history of amendments and the amendment-history at the provision level; they do not include any litigation annotations or links to court decisions.

Where judicial interpretation or challenge of an amending instrument exists, the endnotes provided would not, on their face, disclose that material. Endnote 3 specifically records amending laws and commencement/application details not included in the compilation; it does not expand to include case law. Endnote 4 is focused on provision-level amendment mapping and on the editorial treatment of misdescribed amendments. There is no mention of legal proceedings, declaratory relief, injunctions or judicial review in the text provided.

Practical consequence for researchers and advisers: when litigation history is relevant to the interpretation or application of provisions reflected in the compilation, the absence of case references in the endnotes means practitioners must independently search court and tribunal databases and decision repositories. The Federal Register identifiers given in the legislation-history (for example F2022L01255 and F2025L01049) are the correct starting points to retrieve the source instruments; any litigation will generally be recorded or discoverable in court databases, legal reporting services or the public registers relating to the subject matter of the amending instruments. The compilation’s endnotes do not substitute for that litigation research.

The endnotes contain a number of practical pitfalls and points of uncertainty that users should note when relying on a compiled instrument.

1. The endnotes are metadata not substantive law. The first potential gotcha is mistaking the endnotes for substantive provisions. They document amendments, but they do not set out the operative content of those amending instruments, nor do they reproduce application, saving or transitional provisions. Endnote 3 explicitly warns that the legislation history includes details of application, saving and transitional provisions that are not included in the compilation. Users must go to the source instrument for substantive detail.

2. Misdescribed amendments can lead to two different editorial outcomes. The endnotes explain the rule for misdescribed amendments: if the intended effect can be given effect, an editorial change under s 15V of the Legislation Act 2003 can incorporate the amendment; if not, the amendment is not incorporated and will be marked “(md not incorp)”. The practical implication is that identical-looking compilations might differ depending on editorial judgments about whether the intended effect could be ascertained. Users must check whether any relevant amendment was treated as “md not incorp” or incorporated by editorial change.

3. Abbreviation-key reliance. The amendment-history uses shorthand (for example, rep., am., F identifiers). If readers fail to consult the abbreviation key in Endnote 2, they may misinterpret the entries. For example, “rep. LA 48D” is shorthand for “repealed” by an instrument referenced as LA 48D; failing to map “rep.” correctly will lead to incorrect conclusions about whether a provision still exists.

4. Partial or empty entries in the amendment-history. The supplied HTML table contains blank rows and appears truncated in places. That suggests two practical hazards: (a) the extract may not show all provision-level changes and (b) formatting issues in the compiled material can obscure or omit entries. Always consult the full compilation or the original instruments when certainty is required.

5. Multiple identifiers and cross-references. The legislation-history uses Federal Register identifiers (for example F2022L01255, F2025L01049). Users who attempt to locate instruments by name alone may retrieve multiple versions or drafts; the Federal Register identifier is the authoritative retrieval key. Mistaking registration for commencement date is also a risk; the table displays both and they differ, so check both fields.

6. Editorial changes may mask drafting errors. Where an editorial correction has been made under s 15V, the compiled text will reflect the corrected form. That is useful for readability but can cause disputes about intent if the original amending instrument’s text is ambiguous. If precise reliance on the original amending instrument is necessary (for litigation or compliance risk assessment), check both the original instrument and any records of editorial changes.

7. No litigation or interpretative guidance included. As noted above, the endnotes do not include case law. If the application of a repeal or amendment is contested, the endnotes provide no assistance; independent litigation research is required.

8. Shorthand like “LA 48C/48D” is not self-explanatory. The references such as LA 48C/48D refer to specific legislative amendments or schedules but the endnotes do not unpack those labels. Users must locate the amending instruments that correspond to those codes.

Being aware of these gotchas guards against treating the endnotes as a self-contained source of legal truth. They are navigational and editorial tools, not comprehensive legal authority.

Compliance in the context of these endnotes is compliance with good legal-information practice, not compliance with regulatory obligations found in the underlying substantive instrument. Practitioners and organisations should adopt the following steps to use the endnotes effectively and reduce legal risk arising from reliance on the compiled text.

1. Trace every material change to the source instrument. Use the Federal Register identifiers in Endnote 3 (for example F2022L01255 and F2025L01049) to retrieve the full text of each amending instrument, including any schedules, application, saving and transitional provisions that are not reproduced in the compilation. Endnote 3 explicitly states these details may not be included in the compilation.

2. Read the amendment-history annotations against the abbreviation key. Consult Endnote 2 to translate abbreviations (for example, rep. = repealed; am. = amended; (md not incorp) = misdescribed amendment cannot be given effect). Apply the key systematically so that provision-level notes (Endnote 4) are correctly understood.

3. Check editorial-change records when misdescribed amendments might be implicated. Where an amending instrument appears to misdescribe the amendment, check whether the compiler has applied the editorial power under s 15V of the Legislation Act 2003 to incorporate an intended effect. If the compilation marks an amendment “(md not incorp)”, the original amending instrument is likely to be ambiguous and should be scrutinised in its original form and in any explanatory materials that accompanied it.

4. Verify commencement dates and retrospective or transitional application. Endnote 3 provides registration and commencement dates for amending instruments; confirm those dates and any transitional or saving provisions that affect when and how the amendment operates. Do not assume registration date equals commencement date; the table lists both fields.

5. Maintain version control and archival copies. When relying on compiled material for compliance, keep contemporaneous copies of the relevant amending instruments (using the F identifiers), and record whether any editorial corrections were made in the compilation so that, if a dispute later arises, you can show the source document you relied upon at the relevant time.

6. When in doubt, prefer the primary instrument. The endnotes are signposts. For legal advice, enforcement, regulatory returns or contract compliance that depends on precise statutory wording, use the primary amending instruments and not only the compiled version.

7. Document reliance and queries about ambiguous amendments. If you encounter an amendment that appears misdescribed or where the intended effect is unclear, document your interpretative choices and the reasons you chose either to rely on the compiled text or the original amending instrument. This is especially important where compliance actions or operational changes will follow from the interpretation.

8. Train information staff on the abbreviations and compilation conventions. Because the endnotes rely on standard shorthand (set out in Endnote 2), staff tasked with legal compliance, database maintenance, or regulatory reporting should be familiar with that key so that automated or manual systems parse amendment-history entries correctly.

9. Check for incomplete compilation entries. The supplied amendment-history HTML shows blank rows and formatting fragments. If you find similar gaps in a compiled text, consult the Federal Register or official gazette entries to ensure nothing material has been omitted due to formatting or editorial truncation.

Following these steps reduces the risk that compliance action is founded on an incomplete or misinterpreted version of the law. The endnotes are useful tools for tracing changes but they are not a substitute for verifying and documenting the primary source instruments.