Several technical and legal features of the Determination are easy to overlook but have material effects on compliance, risk allocation and the calculation outcome. These are practical "gotchas" drawn directly from the instrument.
Start point for radial scanning (Schedule 1 item 1(1)). The radial scan uses m as integers from 2 through 1010 and evaluates the device boundary criterion at each m × 100 metre increment. That means the scanning grid begins at 200 metres from the transmitter location (m = 2) rather than at 0 or 100 metres. This is an explicit feature (Schedule 1 item 1(1)) and therefore the device boundary calculation does not examine points at 100 metres or within 200 metres under the specified procedure. Practitioners must not assume the Determination requires a near‑field assessment inside 200 metres.
Maximum radius and forced end point (Schedule 1 item 1(2)). If RP - MP never becomes ≤ 0 along a given radial, the end point is at m = 1010, i.e. at 101,000 metres (101 km) from the transmitter. That is the computational cap for each radial and is not open‑ended; registrants must therefore be prepared to report end points at the maximum radius where the inequality is not met.
Bandwidth reference per 5 MHz (Schedule 1 item 2). RP and MP are specified in dBm EIRP per 5 MHz. Applicants or registrants operating with non‑standard channel bandwidths must convert their emissions to the 5 MHz reference to apply the test accurately.
LOP differences for AAS versus non‑AAS (Schedule 1 item 2). The Determination assigns LOP = -91.5 dBm/5 MHz for AAS transmitters and LOP = -99.5 dBm/5 MHz for other transmitters. This 8 dB difference materially affects device boundary distance because MP includes LOP. A less negative LOP (e.g. -91.5) increases MP and therefore can shrink the device boundary (Schedule 1 item 2). The instrument also contains an operational assumption regarding AAS beam control (Schedule 1 item 2, Note 1) which must be demonstrable.
Receiver antenna gain (Gr) fixed to 0 dBi (Schedule 1 item 2). The Determination sets Gr, the nominal receiver antenna gain including feeder loss, to 0 dBi. Parties cannot substitute a different Gr; this fixed parameter will directly affect MP and therefore device boundary distances.
Propagation modelling choices require external documents (Schedule 1 item 3 and section 6). PL is to be calculated using specified sections of ITU‑R Recommendations P.525‑4, P.526‑15 and P.2108‑0 depending on antenna height (Schedule 1 item 3). Average ground height procedures are required per the Radiocommunications (Interpretation - Technical Framework) Determination 2024 (Schedule 1 item 3(2)-(3) notes). Practitioners must ensure they use the exact sections cited, at the correct revision, and that they follow the path profile and average ground height procedures set out in the referenced domestic instrument.
Path profile increments and averaging (Schedule 1 item 3(3)). Where P.526‑15 is used, the path profile must be developed at 100‑metre increments along each radial and average ground height worked out at each increment. This is a computational burden: 360 radials × up to 1,009 increments × path profile computations, including diffraction calculations, will be required in many cases.
P.2108‑0 corrective clamps (Schedule 1 item 3(4)). When P.2108‑0 is used for ≤6 m antenna height, the Determination fixes the percentage of locations at 0.08%, applies the correction at only one end of the path, and clamps the calculated loss between 0 dB and 8 dB. These clamps are non‑intuitive and will matter in short‑range clutter scenarios: if the P.2108 calculation yields less than 0 dB, it must be taken as 0 dB, and if it yields more than 8 dB it must be taken as 8 dB.
Accuracy/confidence requirement (section 9). Parameters in Schedule 1 must be estimated with at least 95% confidence that the true value will remain below the requirement. This is not a simple "best estimate" clause: it requires practitioners to specify and justify the statistical or modelling methodology that produces a 95% confidence bound for quantities such as RP and PL. The Determination does not prescribe particular statistical methods; parties must supply them and show the confidence level is met.
Exceptions for parts of device boundary outside the geographic area (section 8(2)). A part of the device boundary lying outside the geographic area is not unacceptable if it is connected to a radial that (a) is one of the radials used in Schedule 1 item 1, (b) does not cross land outside the geographic area that is permanently above the Australian territorial sea baseline, and (c) does not cross specific HCIS identifiers (IW3E, IW3I, IW3M, IW6A, IW6E, KX9, LX7, LX8, LX9) (section 8(2)). The HCIS list describes areas near Adelaide and in the Bass Strait (note to section 8). Practitioners must check whether their radials cross these identifiers, because crossing them removes the exception and may render a part of the device boundary unacceptable.
Transitional protection conditionality (section 10). The transitional preservation of the 2013 Determination for pre‑existing transmitters is conditional. If, after commencement, a recorded change results in the new device boundary distances being equal to or less than the old distances on each radial, then such a change does not render the transmitter unacceptable (section 10(3)). But if the new device boundary distances increase on any radial, the old protection may not apply. Attention to the exact definition of "change time", "new device boundary" and "old device boundary" in section 10(4) is important (section 10(4)).
Antenna height measurement tolerance (Schedule 1 item 4(1)). The phase centre height must be measured with an error of less than five parts in 100 relative to a specific reference point on the supporting structure. This requires precise surveying and documentation; failure to meet the tolerance could be a determinative compliance failure.
Reference versions of external standards. The Determination names specific ITU‑R Recommendations and particular sections within them (section 6; Schedule 1 item 3). Users must ensure they are using the exact editions listed (for example Recommendation ITU‑R P.526‑15, not a different revision) because the Determination ties its computational rules to those specified sections.
In short, the key gotchas are the particular starting point for radial scanning, the 101 km computational cap, the 5 MHz bandwidth reference, the LOP differences and their mechanical effect on device boundary, the 95% confidence requirement, exact path profile requirements, fixed Gr, measurement tolerances, and the specific HCIS identifiers that remove an otherwise available exception.