Adelaide Airport Curfew Regulations 2018

The instrument relies on a small set of interlocking regulatory concepts drawn from the Act and implemented through schedules and numerical limits. These concepts are (with the sections in this instrument that invoke them):

• curfew period and curfew shoulder period, terms defined in the Act, with movement caps attached here for particular classes of aircraft during those periods (ss 5, 6, 7);
• Annex and Chapter 4 noise levels, referenced as the technical noise standard which determines whether particular types remain specified or are removed from specification (ss 5, 9(3));
• week, a defined temporal unit in the Act that is the basis for weekly movement caps (s 5 and the caps in ss 6-7);
• types of aircraft as established by type certificate data sheet numbers and revision numbers, used to specify which jet models are exempt from curfew restrictions (s 9(2));
• low noise heavy freight aircraft, a statutory category for which the instrument provides that each type is “specified” for the purposes of making applications under s 11(1) of the Act (s 8); and
• administrative compliance steps, including giving a return when an aircraft lands on a runway other than runway 05 during a curfew period, with a prescribed postal address (s 10).

The instrument uses “for the purposes of” language repeatedly. Section 6 begins “For the purposes of section 8 of the Act” before prescribing the weekly maxima for international aircraft during curfew shoulder periods. Section 7 begins “For the purposes of paragraph 10(a) of the Act” before prescribing the weekly maxima for low noise heavy freight aircraft. Section 8 operates “for the purposes of subsection 11(1) of the Act” in specifying that each type of low noise heavy freight aircraft is specified. Section 9 is framed “For the purposes of subsection 13(2) of the Act” in listing jet types that may take off or land during a curfew period. Section 10 addresses subsection 15(3) of the Act by identifying the address for giving a return. Those cross‑references show that the mechanics of exemption, application and reporting are anchored in the Act; the regulations give specific numeric and administrative detail to activate the Act’s framework.

The instrument adopts an administratively discrete method for identifying types of aircraft exempt from curfew restrictions. Instead of listing make and model names as the sole identifier, s 9(2)(b) ties specification to a type certificate data sheet number and a revision number “as existing at the commencement of this instrument”. That makes the exemption contingent on the aircraft being the same as the model as defined against a fixed snapshot of the FAA certificate data system at commencement.

Noise compliance is expressed in relation to the Annex, a document defined in the Act. Section 9(3) introduces a temporal trigger, 1 January 2023, after which certain listed business jet types will not be treated as specified if they do not comply with the Annex maximum noise levels in Chapter 4. The instrument therefore links administrative exemption to technical noise limits and creates a future deregulatory trigger tied to measured noise performance.

Finally, the instrument contains an express postal point of contact for a specific compliance act, giving a return when a landing occurs on any runway other than runway 05 during a curfew period (s 10). The mechanics therefore create a recordkeeping/reporting obligation of postally-delivered returns to a named General Manager in the Aviation Environment Branch.

Primary affected parties are operators of international aircraft and operators of heavy freight aircraft at Adelaide Airport, owners and operators of the jet types identified by type certificate data sheet numbers, and persons required to give returns under the Act for landings on runways other than runway 05 during a curfew period.

• International aircraft operators: Section 6 prescribes that, during curfew shoulder periods, the maximum weekly permitted take‑offs is zero and maximum landings is eight. That directly binds operators of international services into a numerical cap on movements during those shoulder periods (s 6). The term international aircraft is defined in the Act, according to s 5 of this instrument which states defined terms are in the Act. Those operators must therefore plan routing and scheduling so as not to exceed the weekly maxima.
• Low noise heavy freight aircraft operators: Section 7 prescribes weekly maxima for take‑offs (15) and landings (25) during curfew periods for low noise heavy freight aircraft. The instrument also specifies that “each type of low noise heavy freight aircraft is specified” for the purposes of making applications under subsection 11(1) of the Act (s 8). That signals a pathway for operators of these aircraft to seek operational permissions or to be treated under the statutory scheme.
• Owners/operators of certain jet types: Section 9 provides the administrative list of jet types that may take off or land during a curfew period by citing type certificate data sheet numbers and revision numbers. If an aircraft is matched to a listed data sheet number and revision as it existed at commencement, that type is specified and is not affected by curfew periods for the statutory purposes cited (s 9(2)). Conversely, owners/operators of the specific models listed in s 9(3) will be affected after 1 January 2023, unless those models comply with the maximum noise levels in Chapter 4 of the Annex; if they do not comply they “are not specified” after that date (s 9(3)).
• Adelaide Airport and air traffic planners: The caps and the specification of exempt types impose constraints on slot allocation, flight scheduling and airfield operations during curfew and curfew shoulder periods. Those actors must ensure runway assignments and slot distributions do not cause the caps to be exceeded. The instrument also requires returns when landings occur on runways other than runway 05 during curfew periods, which allocates an administrative reporting burden to the entity responsible for giving the return (s 10).
• Departmental administration: The instrument designates the General Manager, Aviation Environment Branch, Department of Infrastructure, Regional Development and Cities, at a Canberra GPO address, as the recipient of returns (s 10). That creates a direct operational reporting stream into the Department.

Indirectly affected parties include passengers and freight customers who may face constraints on flights at certain hours, and third parties interested in environmental compliance because the instrument links exemptions and future disqualification to noise levels in the Annex (s 9(3)). The instrument does not itself create licensing fees or new penalty regimes; enforcement and penalties, if any, are matters for the Act (see the repeated “for the purposes of” phrasing in ss 6-10, and s 3).

Geographically the instrument applies to Adelaide Airport and to aircraft movements there; the regulatory definitions that govern terms such as curfew period and Annex are located in the Act, which the regulations reference (s 5). The list in s 9(2) depends on the state of specific FAA type certificate data sheets “as existing at the commencement of this instrument”, so aircraft certified to later revisions are not automatically included by this instrument’s snapshot method.

This instrument creates administrative duties and clarifies certain rights by reference to the Act. The regulations themselves are largely prescriptive numerically and administratively rather than being self-contained duties with new sanctions. Key duties and rights as established or implicated by the instrument are:

Duties:

• Observe the movement caps: operators must ensure weekly take‑offs and landings do not exceed the maxima the instrument prescribes for particular aircraft classes and periods. For international aircraft during curfew shoulder periods the duty is to limit take‑offs to zero and landings to no more than eight per week (s 6). For low noise heavy freight aircraft during curfew periods the duty is to limit take‑offs to 15 and landings to 25 per week (s 7). The instrument frames these figures as “the maximum number … that are permitted” (ss 6(a)-(b), 7(a)-(b)), which operationally constrains permitted movements.
• Use specified application pathways: by specifying that each type of low noise heavy freight aircraft is specified for the purposes of subsection 11(1) of the Act (s 8), the instrument requires any applications that the Act contemplates to proceed against that statutory framework. The Act’s subsection 11(1) governs the application process; the regulations make clear which types fall within that application pathway.
• Provide returns for landings on runways other than runway 05 during curfew periods: s 10 prescribes the address and the official to whom the return must be given. The requirement to give a return is set out in subsection 15(3) of the Act, and the regulations fix the form of the postal address and the Departmental recipient for that return (s 10). That is an administrative duty that produces a record with the Department.
• Verify model identification against the specified type certificate data sheet numbers and revision numbers: because s 9(2)(b) specifies exemption by reference to a data sheet number and revision “as existing at the commencement of this instrument”, duty-bearing parties must verify that an aircraft’s type certificate matches the cited number and revision in order to claim the exemption.

Rights:

• Right to take off or land during curfew period if aircraft is of a specified jet type: under s 9 a type of jet aircraft is “specified” and may take off or land during a curfew period if it satisfies the statutory requirements in paragraphs 13(2)(a)-(c) of the Act and if it is covered by a type certificate data sheet number and revision in s 9(2) as it existed at commencement (s 9(1)-(2)). The instrument therefore recognises a conditional right for identified types to operate during curfew periods within the Act’s limits.
• Right to apply under the Act for low noise heavy freight aircraft: by specifying each type for the purposes of subsection 11(1), the instrument gives operators of such types the procedural right to make applications that the Act contemplates (s 8).

The regulations do not themselves create penalty provisions or an enforcement schedule; those will be found in the Act. Consequently, some duties depend on the Act for their legal consequences and enforcement mechanisms. The instrument also creates a temporal duty for affected older business jet types: from 1 January 2023, if the listed types do not comply with the Annex Chapter 4 noise limits they are no longer specified, and thereby lose the operational right to take off or land during curfew periods under the specification framework in s 9(3).

Operational duties require co‑ordination with airport operations, record keeping to evidence weekly movement counts against the caps, and the maintenance of evidence that an aircraft corresponds to the specified type certificate data sheet and revision number cited in s 9(2)(b). The instrument places administrative processing and record receipt functions with the Department, by specifying the recipient for returns (s 10).

The Adelaide Airport Curfew Regulations 2018 do not themselves set out penalties or detailed enforcement mechanisms. Instead the regulations operate to give concrete detail to several provisions of the Adelaide Airport Curfew Act 2000 and therefore rely on the Act for enforcement powers, sanctions and remedial mechanisms. This pattern is evident from the repeated framing “For the purposes of” in ss 6, 7, 8, 9 and 10. Those sections tailor the Act’s operation by setting caps, specifying types and identifying administrative addresses, but they do not include standalone penalty clauses.

Consequently enforcement questions must be resolved by reference to the Act’s provisions that are invoked in the regulations. The instrument explicitly links s 6 to “section 8 of the Act”, s 7 to “paragraph 10(a) of the Act”, s 8 to “subsection 11(1) of the Act”, s 9 to “subsection 13(2) of the Act” and s 10 to “subsection 15(3) of the Act” (ss 6-10). Any breach of the caps or reporting duties created or given effect by these regulations will attract the Act’s enforcement regime rather than a new sanctions regime in the regulations.

Practically, the instrument creates enforcement touch points:

• numerical caps (ss 6-7) establish objective, countable limits against which compliance can be measured, and therefore create the factual predicate for any enforcement action under the Act;
• the specification-by-type approach in s 9 produces an administrative bright line for entitlement to operate during curfew periods, which enforcement officers can assess by comparing an aircraft’s type certificate to the indicated data sheet number and revision;
• the requirement to give a return when a landing occurs on a runway other than runway 05 during a curfew period (s 10) produces an administrative record that the Department can use to check compliance against permitted operations and to trigger investigative or enforcement steps under the Act.

The instrument also creates a future change in entitlement for certain business jets from 1 January 2023 (s 9(3)). If those jets do not comply with the Annex Chapter 4 noise levels after that date they are “not specified”, which changes their legal status under the Act and therefore may change the universe of enforceable actions that an enforcement body can take against an operator seeking to use the curfew‑period exemption.

Because the instrument fixes the address for returns and the person to whom returns are to be given (General Manager, Aviation Environment Branch, Department of Infrastructure, Regional Development and Cities), enforcement administrators have an identified repository for compliance records (s 10). The Act will determine how those returns are used in investigation or sanction processes.

If readers require the specific criminal or civil penalties and the procedures for enforcement, they must consult the Adelaide Airport Curfew Act 2000; those provisions are not included in this instrument. The regulations are evidence of how the Act’s discretionary and procedural mechanisms are to be exercised, but not of the sanctions that attach to non‑compliance.

The entire regulatory instrument is drafted to operate as a subordinate instrument to the Adelaide Airport Curfew Act 2000. Section 3 expressly states that the instrument is made under that Act, and multiple sections of the instrument operate “for the purposes of” specific sections and paragraphs of the Act (ss 6-10). Therefore the Adelaide Airport Curfew Regulations 2018 do not stand alone: their operative effect depends on the Act’s substantive definitions, powers, procedures and penalty regimes.

Specific interactions the instrument creates or presupposes include:

• dependence on statutory definitions in the Act: s 5 of the regulations states that a number of expressions used are defined in the Act, explicitly listing curfew period, curfew shoulder period, the Annex and week. The regulations therefore rely on the Act to fix the meaning of those key terms and on the Act’s definitions to determine the temporal and substantive scope of the caps and obligations set in the regulations.
• operationalising Act sections: each numerical or administrative prescription in the regulations refers to a corresponding Act provision for legal effect. Section 6 operates “for the purposes of section 8 of the Act”, s 7 for paragraph 10(a) of the Act, s 8 for subsection 11(1) of the Act, s 9 for subsection 13(2) of the Act and s 10 for subsection 15(3) of the Act. The regulations therefore provide the detailed content that the Act requires or authorises in those provisions.
• technical standard linkage through the Annex: s 9(3) conditions future specification status on compliance with “the maximum noise levels specified in Chapter 4 of the Annex.” The Annex is defined in the Act, so the regulations link operational exemptions to a technical noise standard set or incorporated through the Act. That ties the regulations to any processes or instruments the Act uses to define or update the Annex or to the Annex’s provisions themselves.
• reliance on external certification systems as evidentiary source: s 9(2)(b) ties specification to “a type certificate data sheet, as existing at the commencement of this instrument, with a number and revision number mentioned in an item in the following table, applies to that type of jet aircraft.” The note after the table, which is part of the instrument, states that in 2018 type certificate data sheets could be viewed on the United States Federal Aviation Administration’s website, indicating that the instrument expects external aviation certification documentation to serve as the reference standard for type identification. The instrument therefore interacts operationally with international civil aviation certification records; those records are used as the technical evidence base for regulatory classification.
• administrative interaction with Departmental structures: s 10 names the General Manager of the Aviation Environment Branch, Department of Infrastructure, Regional Development and Cities, as the recipient of returns for landings on runways other than runway 05 during a curfew period. This allocates administrative interaction between regulated parties and a specified Commonwealth departmental unit.

The regulations repeal the prior Adelaide Airport Curfew Regulations 2000 in full (Schedule 1). That repeal changes the subordinate law landscape and requires affected parties to substitute compliance with the 2018 regulations for anything previously set by the 2000 regulations. The instrument’s commencement provision (s 2) and the snapshot reference to type certificate data sheets as they existed at commencement (s 9(2)(b)) create temporal interactions with administrative datasets and prior regulations.

This instrument does not reference other Commonwealth Acts or state laws beyond the Act it is made under, and it does not amend any other primary legislation. Any interaction with airport operating licences, air traffic management rules, international aviation treaties, or state environmental controls is not stated in the instrument; those linkages would need to be explored by comparing the Act and other instruments or laws outside the text of these regulations.

The text provided contains the original instrument text as made on 6 December 2018 and states the commencement date as 8 December 2018 (s 2). The instrument includes a Schedule that repeals the Adelaide Airport Curfew Regulations 2000 in their entirety (Schedule 1). There are no further amendment items listed within the instrument text provided; it does not itself record any subsequent amendments or variations.

Key dated events recorded in the instrument are:

• making and signing: the instrument is dated 06 December 2018 at the head and bears the signatures and attestation language customary to Commonwealth instruments; the public signing and authority are recorded (instrument header).
• commencement: the instrument provides a commencement table in s 2 showing that “the whole of this instrument” commences “The day after this instrument is registered. 8 December 2018” (s 2(1) and the commencement table). The table also includes the editorial note that it relates only to the instrument as originally made and will not be amended in the instrument text to reflect later amendments.
• repeal: Schedule 1 repeals the entire Adelaide Airport Curfew Regulations 2000.

The regulations specify in s 9(2) that the type certificate data sheet numbers and revisions apply “as existing at the commencement of this instrument”. That snapshot clause is an explicit temporal limiting device for the regulatory list, and therefore forms part of the instrument’s amendment architecture: the instrument does not create a mechanism for automatic update of those citation references to later revisions. That point implies that aircraft certified under later revisions will not be included by the regulation unless the instrument itself or the Act is amended.

Section 9(3) introduces a future‑dated change to the specification status of certain aircraft types: it states that certain types “are not specified on and after 1 January 2023” if they do not comply with Chapter 4 maximum noise levels in the Annex. That is a date-certain change embedded in the original instrument, and it functions like a prospective amendment to the scope of the exemptions absent compliance with the noise limit.

No textual record of subsequent amendments, modifications, or revocations after the original making is provided in the instrument text. If users require a current legal map, they must consult the Commonwealth’s federal register of instruments or the consolidated legislative database to verify whether this instrument has since been amended, repealed, or subject to interim variation. The instrument itself warns that the commencement table will not be updated in-text to show later amendments (s 2(2) note), which is standard drafting practice but indicates that the reader should confirm current status elsewhere.

The instrument text supplied contains no references to litigation, judicial decisions, administrative determinations, or any cases interpreting these regulations or the Act. It does not cite any precedent nor record any claims, disputes, or implementation litigation. Therefore, within the scope of the provided source there is no litigation history to summarise.

Practically, readers should note the following points arising from the absence of litigation material in the instrument itself:

• interpretative questions are likely to arise from the instrument’s reliance on external technical material and the Act, for example, what constitutes proof that an aircraft corresponds to the type certificate data sheet number and revision cited in s 9(2)(b), how “week” is to be counted in complex scheduling situations, and how the Department will administer the weekly caps in practice. Those are matters that could generate disputes. The instrument does not pre-empt any such litigation.
• the instrument’s reliance on the Act for enforcement and definitions means any legal challenge to enforcement measures, penalties or discretionary decisions under the statutory scheme would engage the Act’s processes and any delegated powers in the Act. The regulations themselves are narrow and technical; disputes about policy choices embedded in numerical caps would typically be framed under the Act.
• the instrument’s fixed‑snapshot approach to type certificate data sheets (s 9(2)(b)) and the 1 January 2023 trigger in s 9(3) may create factual disputes about compliance with the Annex’s noise levels and about whether a particular aircraft was correctly identified against a data sheet as it existed at commencement. Those disputes would likely be resolved through administrative process or judicial review of administrative decisions, but no instances are recorded in the text provided.

Because the instrument contains no litigation record, readers seeking judicial interpretation or administrative determinations must consult court and tribunal databases, or Departmental records, to identify any post‑commencement cases or disputes. The regulations themselves do not supply that material.

The instrument is short and technical, and a number of specific drafting features can produce practical compliance traps if not noticed. The following items are concrete risk points grounded in the instrument text:

• snapshot‑dependence of the exemption list (s 9(2)(b)). The list of jet types not affected by curfew periods is tied to type certificate data sheet numbers and revision numbers “as existing at the commencement of this instrument.” That means an aircraft whose type certificate was later revised may not fall within the listed citation even if the make and model name appears familiar. Operators must validate the exact data sheet number and revision at the instrument’s commencement to determine entitlement, rather than relying on a rolling or current FAA record. The instrument’s note points to FAA records as the likely source in 2018, but the regulation fixes the snapshot in time.
• absence of a plain textual model list (s 9). The instrument does include notes mapping certain model names to data sheet numbers in s 9(3) note, but largely relies on administrative identifiers in s 9(2). That can complicate quick compliance checks for operators who track models by common model names; they will need to match those names to the specific data sheet numbers and revision numbers cited.
• silent on application content and assessment criteria (s 8). Section 8 states that “each type of low noise heavy freight aircraft is specified” for the purposes of subsection 11(1) of the Act, but it does not list those types or set out content or assessment criteria for applications. The Act’s subsection 11(1) therefore governs process, but the instrument does not list the types within the regulations text. If stakeholders expect an explicit listing of low noise heavy freight types in the regulations, they will not find it here. That may increase administrative interaction with the Department to clarify the practical list or application documents.
• 1 January 2023 disqualification trigger (s 9(3)). Certain older business jet types are expressly subject to removal from the specified list on and after 1 January 2023 unless they comply with Chapter 4 maximum noise levels in the Annex. Operators of those models must determine how noise compliance will be measured and proven in order to retain their specified status. The instrument does not set the measurement methodology in this text, it simply references the Annex, which is defined in the Act. The absence of measurement methodology in the regulations may cause uncertainty unless the Annex or the Department provides technical guidance.
• caps measured per week (ss 6-7). The movement limits are framed as weekly maxima, and the instrument says week is defined in the Act (s 5). If an operator or airport planner uses a different planning cycle they risk exceeding the statutory weekly caps. Misunderstanding of what constitutes the relevant “week” (for example whether it is a calendar week beginning on a particular day) could result in unintentional breach. Check the Act for the precise definition.
• reporting form and delivery method fixed to a postal address (s 10). The instrument prescribes a postal address for returns when a landing occurs on runways other than runway 05 during a curfew period. If an operator misunderstands whether an electronic delivery is acceptable, they may inadvertently fail to comply with the form and delivery method prescribed. The instrument does not say whether electronic submissions are acceptable, and it fixes a postal address to a specific General Manager. Parties should treat that address as the specified recipient unless the Department provides alternative instructions.
• repeal of previous regulations (Schedule 1). The instrument repeals the 2000 regulations in full. If operators or advisers assume the old regulations’ mechanisms or transitional arrangements remain in force, that assumption may be incorrect; the 2018 instrument is the operative subordinate instrument from commencement. Any transitional allocations under the 2000 regulations would need to be traced in the Act or in transitional provisions which are not present in this instrument.

Each of these “gotchas” arises directly from the wording of the regulations: snapshot references (s 9(2)(b)), future disqualification (s 9(3)), and postal address specificity (s 10) are all explicit. The instrument does not provide administrative forms, guidance notes, or an operational manual; these practical items must be sourced from the Department or derived from the Act.

Compliance under these regulations requires coordination with the Adelaide Airport Curfew Act 2000 because the regulations operate to give detail to Act provisions. The following practical steps, each tied to the relevant regulation text, set out a compliance workflow for operators, airport managers and departmental administrators.

1. Confirm the governing definitions in the Act (s 5). The instrument relies on definitions for curfew period, curfew shoulder period, the Annex and week. Step one is to consult the Adelaide Airport Curfew Act 2000 to confirm the temporal boundaries of curfew and curfew shoulder periods, and the Act’s definition of week, because the caps in ss 6-7 are weekly maxima. Without the Act’s definitions you cannot accurately count movements or determine when returns are required. (s 5)

2. Count weekly movements against the caps (ss 6-7). For international aircraft during curfew shoulder periods, ensure take-offs are zero and landings do not exceed eight per week (s 6). For low noise heavy freight aircraft during curfew periods, ensure take-offs do not exceed 15 and landings do not exceed 25 per week (s 7). Put in place operational scheduling checks and reporting tools to monitor weekly cumulative movements in real time, and ensure slot allocation systems block additional movements when the caps are reached. Retain records showing the weekly counts and the calculation methodology tied to the Act’s definition of week.

3. Verify aircraft type status using type certificate data sheet numbers and revisions (s 9(2)(b)). If you intend to rely on the exemption in s 9 for a jet to operate during curfew periods, verify that the aircraft’s type certificate corresponds to one of the data sheet numbers and revision numbers listed in the regulation’s table, “as existing at the commencement of this instrument”. Document that evidence, including copies of the type certificate data sheet dated or archived as of commencement, to show the aircraft met the cited revision. Because the regulation fixes a snapshot, do not assume later revisions maintain the same citation. (s 9(2)(b))

4. Check for 1 January 2023 disqualification (s 9(3)). If you operate one of the business jet models listed in s 9(3) (for example, identified model families in paragraphs (a)-(f) of s 9(3)), determine whether the aircraft complies with the maximum noise levels specified in Chapter 4 of the Annex. If not, from 1 January 2023 it is “not specified” and therefore will not be treated as exempt under the specification regime. Arrange for noise measurement or certification evidence if you intend to preserve exemption status. The instrument references the Annex for the noise standard; check the Annex provisions in the Act for measurement methodology. (s 9(3))

5. For low noise heavy freight aircraft, follow the application process under the Act (s 8). Section 8 says that each type of low noise heavy freight aircraft is specified for the purposes of subsection 11(1) of the Act. Identify the application steps and forms required under s 11(1) of the Act, compile the technical evidence the Act requires, and submit applications to the Department as directed by the Act. The instrument does not reproduce the Act’s application content requirements, so follow the Act. (s 8)

6. Prepare to give returns when landings occur on runways other than runway 05 during curfew periods (s 10). The instrument prescribes the postal address and the recipient: General Manager, Aviation Environment Branch, Department of Infrastructure, Regional Development and Cities, GPO Box 594, Canberra ACT 2601. Ensure internal processes capture any such landing and produce the required return promptly, and use the address provided unless the Department advises an alternative method. Check the Act for required timing and content of the return (s 10).

7. Maintain documentation and audit trails. Because the regulations rely on counting and on type certification snapshots, preserve archived evidence that shows the basis for entitlement to operate during curfew or shoulder periods: weekly movement logs, type certificate data sheet copies as at commencement, noise measurement certificates showing compliance with the Annex if relevant, and copies of any returns sent to the Department. These documents will be the primary proof in any administrative review or enforcement action under the Act. (ss 6-10)

8. Coordinate with airport slot and air traffic management. The numerical caps will require slot discipline. Operators should coordinate with Adelaide Airport operators and any slot allocation authorities to ensure the caps are not exceeded. Develop internal escalation rules that prevent last‑minute scheduling that could breach weekly totals. The instrument does not provide for over‑booking of a cap; it prescribes maxima only (ss 6-7).

9. Seek Departmental clarification where the regulations are silent. The instrument is brief on procedural details: it does not set out how the Department will count movements in complex circumstances, how to evidence that an aircraft matches the listed data sheet snapshot, whether electronic returns are acceptable in addition to postal returns, or how noise compliance under the Annex will be measured. If any of these procedural details could affect operational plans, request written guidance from the Aviation Environment Branch or seek administrative directions under the Act. (s 10)

10. Monitor legislative changes. The instrument’s commencement table notes it will not be amended in the text to record later changes (s 2(2) note). Confirm whether the 2018 regulations have been subsequently amended or replaced by checking the federal register of legislation or the Department’s website. Also monitor any Departmental guidance or updated administrative practice notes that interpret how s 6-s 10 will be applied in practice.

By following these steps and grounding each action in the relevant regulation provision cited above, regulated parties can organise operational compliance and recordkeeping. Where the regulations rely on the Act for definitions, procedures or penalties, ensure those Act provisions are reviewed simultaneously, since the regulations do not operate in isolation (s 5).