Flying near airports: the 3 nautical miles around a controlled aerodrome

Same distance, different starting points

CASA’s “Flying near airports” page also measures from the runway: “We measure these distances from the centreline of the runway.” The Manual of Standards defines “movement area” only by pointing to the Part 139 Manual of Standards, which this guide has not read, so it states no distance between the two starting points.

Height, the aerodrome itself, and the pilot’s licence

Near any aerodrome (r 101.075)

Flying above 400 feet AGL within 3 nautical miles of an aerodrome, or over a movement area, runway, or approach or departure path, needs another Part 101 provision or a permission under r 101.080; and no one may obstruct an aircraft taking off or landing. Each is a strict liability offence of up to 25 penalty units.

Who gives permission (r 101.080)

For a controlled aerodrome, “the air traffic control service for the aerodrome”; for any other aerodrome, CASA. Breaching a condition it sets is a strict liability offence of up to 50 penalty units.

The licence (r 101.300(3))

A remote pilot licence holder must not fly “above 400 ft AGL in controlled airspace, or within 3 nautical miles of the movement area of a controlled aerodrome”, without at least one of: an aeronautical radio operator certificate, a flight crew licence, an ATC licence, an equivalent military qualification, or a flight service licence.

The no-fly zone and every way into it

The zone covers the area below 400 ft within 3 NM of the measurement point of any runway, and the approach and departure paths “whether or not they extend beyond 3 NM” (s 4.02). Section 4.05 draws those paths up to 400 ft: from the ground up over the runway and its strip and over the black-shaded paths to 7 km from the end of the runway strip; from 300 ft (90 m) between 7 km and 8.5 km; and from 150 ft (45 m) in the grey-shaded area, which extends 3 NM in all directions from the measurement point.

Section 4.03 forbids RPA operations in the zone, then lists the cases that are allowed:

• a tethered operation by a certified RPA operator or its remote pilot, on the terms of s 4.04, among them a tether no longer than 150 ft and notice to ATC before take-off;
• a flight that is exclusively indoors;
• a micro RPA, if it does not enter the approach and departure paths or the aerodrome boundary;
• a model aircraft of no more than 250 g, on the same terms (one over 250 g must not fly in the zone);
• a “defined unmanned aircraft”: one flown under an approved area under r 101.030, or under a r 101.075 permission for the zone.

The approved area, and its eighteen directions

CASA 40/26 approves, as an area for RPA operation, the area below 400 ft AGL within 3 nautical miles of the measurement point of any runway of a controlled aerodrome that is not a military aerodrome. It was made on 23 September 2026, commences the day after its registration, repeals CASA 66/24 and is itself repealed at the end of 20 September 2029. Its pilot must be a remote pilot licence holder who is, or works for, a certified RPA operator, and must follow all of s 5’s directions:

1. 1Fly only in an operating area described on a CASA-verified app.
2. 2Be registered on the app, or have the operator registered, for the area and period.
3. 3Follow any operating limitations the app notifies.
4. 4Fly only a very small or small RPA.
5. 5Fly only as an aerial work operation.
6. 6–7Not at night, even for an operator approved under CASA 01/17.
7. 8Take reasonable steps for VHF coverage and a listening watch on the ATC frequency from 15 minutes before a flight until landing, and for mobile phone coverage; follow any ATC direction.
8. 9The VHF steps do not apply “within 100 metres laterally from, and below, an obstacle, other than an aircraft”.
9. 10–11Not beyond visual line of sight, even with a BVLOS approval, the EX63/26 exemption or the r 101.300(4) requirements met.
10. 12–13Not more than one RPA at a time, even with an approval for more.
11. 14Tell ATC immediately if the RPA leaves the operating area.
12. 15Not transmit on the ATC frequency unless ATC directs it, or to make that report.
13. 16Use an active fail-safe mode that, if the data link is lost, adjusts altitude to the minimum safe level, goes to a pre-defined safe landing or flight termination area, and lands or ends the flight.
14. 17Not switch on a transponder or ADS-B position broadcast unless ATC directs it.
15. 18Where the operator’s documented procedures and a direction differ, follow the direction.

How CASA describes the app route

CASA offers automated airspace authorisations to operator’s certificate holders at ten airports (Adelaide, Broome, Cairns, Canberra, Coffs Harbour, Essendon, Hobart, Melbourne, Perth and Sydney) and over Sydney Harbour’s restricted areas R407 A/B. It lists five requirements: a current ReOC; a valid RePL for the remote pilot; a valid aeronautical radio operator certificate for the remote pilot; a registered drone weighing less than 25 kg; and a flight in daylight hours. The request goes through a participating CASA-verified app, no more than 30 days ahead.

Why the line matters at all: the standard operating conditions · Past sight: beyond visual line of sight · All five waypoints