Air Law: The Regulatory Framework for RPAS
Air law for remotely piloted aircraft systems is built on a layered structure. At the top sit international standards and recommended practices; beneath them, national regulations translate those standards into binding rules for operators, remote pilots and manufacturers. A candidate must understand the difference between binding regulation (what you must do), acceptable means of compliance (ways of showing you comply) and guidance material (advisory only). Questions often test this hierarchy: guidance material is not law, and following it does not guarantee compliance.
Know the core concepts: the operator (the legal entity responsible for the flight) versus the remote pilot (the person manipulating the controls); registration and identification requirements; the certificate or authorisation that permits a specific operation; and the categories of operation, which typically range from low-risk (no authorisation, but with limitations on distance, height and people) through to higher-risk operations requiring a safety assessment and explicit approval.
Traps to watch:
- Confusing the operator's responsibilities with the pilot's. The operator holds accountability for the organisation, maintenance and record-keeping; the pilot is responsible for the conduct of the flight.
- Assuming a permission granted for one category covers another. Authorisations are operation-specific.
- Forgetting that record-keeping (flight logs, maintenance records, training records) is a legal obligation, not good practice.
Worked example / rule of thumb: A question asks whether a remote pilot may fly closer to people because the manufacturer's manual says the aircraft is 'safe'. The manual is guidance from the manufacturer, not an authorisation. The answer is no: the applicable regulation and any operational authorisation set the limits. Remember: the manual describes the aircraft; the regulation defines the operation.