Study guide

6.1 GNSS, Compass, IMU and Geofencing

CASA Remote Pilot Licence RePL

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 About the RePL Exam 1.2 How to Use This Guide & Build a Study Plan

2 RPA Air Law: Regulatory Framework & Standard Operating Conditions

2.1 CASR Part 101 and the Manual of Standards 2.2 Standard Operating Conditions (SOC) 2.3 The 120 m (400 ft) AGL Height Limit 2.4 VLOS, Daylight, Visibility and the One-RPA Rule

3 RPA Air Law: Licensing, Categories & Approvals

3.1 RePL vs ReOC: Pilot Licence vs Operator Certificate 3.2 Excluded Categories and Operator Accreditation 3.3 RPA Weight Categories and Registration 3.4 Operating Beyond the SOC: Approvals and the ReB1

4 Basic Aviation Knowledge (RBAK)

4.1 Direction, Wind Velocity and Aviation Time 4.2 Units of Measurement: Height, Altitude and Elevation 4.3 Aerodynamics: Lift, Drag, Thrust, Weight and Energy 4.4 Weight and Balance: Terms and Limits 4.5 Propellers and Rotors 4.6 Axes, Attitude and Flight Control Principles 4.7 The Remote Pilot Station

5 RPAS Systems: Platforms, C2 Link & Power

5.1 Multirotor vs Fixed-Wing Characteristics 5.2 Command-and-Control Link and Failsafes 5.3 Lithium-Polymer Battery Management and Safety

6 RPAS Systems: Sensors, Payload & Preflight

6.1 GNSS, Compass, IMU and Geofencing 6.2 Payload, Centre of Gravity and Pre-Flight Checks 6.3 Automated Flight Management Systems (RAFM)

7 Electrical & Electronic Systems (REES)

7.1 Electrical Terms and RPAS Electrical Components 7.2 Electric Motors, Kv and Current Draw 7.3 Battery Types, Specifications and Dangerous Goods 7.4 Charging, Discharging, Balancing and Battery Limitations 7.5 Radio Waves, Frequency Bands and Propagation 7.6 GPS Components, Errors and Electromagnetic Hazards

8 Multirotor Aerodynamics & Performance (RBKM)

8.1 Multirotor Airframe and Component Layout 8.2 Rotor Aerodynamics: Blade Design, Thrust, Drag and Torque 8.3 Hovering: Ground Effect, Recirculation and Translational Lift 8.4 Multirotor Flight Controls, Stabilisation and GPS Hold 8.5 Motor Failure, Rotor Direction and Abnormal Aerodynamics 8.6 Weight, Power, Wind and Climb Performance 8.7 Descent, Vortex Ring State and Landing

9 Navigation & Charts

9.1 Chart Fundamentals: Latitude, Longitude, Variation and Distance 9.2 Visual Terminal Charts and Visual Navigation Charts 9.3 Airspace Classes, Control Zones and CTA Steps 9.4 Restricted, Danger and Prohibited Areas and Obstacles 9.5 NOTAMs, the AIP and Chart Currency

10 Meteorology

10.1 Wind, Sea Breezes and Local Effects 10.2 Turbulence, Orographic Effects and Terrain 10.3 Thunderstorms, Fronts and Fog 10.4 Density Altitude, METAR/TAF and BoM Forecasts 10.5 Weather Observations: Reading the Sky and the Site

11 Human Factors

11.1 IMSAFE, Fatigue and Complacency 11.2 Situational Awareness, Fixation and External Pressure 11.3 Alcohol, Drugs and Crew Resource Management 11.4 Vision, Visual Limitations and Illusions 11.5 Stress and Stress Management 11.6 Threat and Error Management

12 Radio & AROC

12.1 Phonetic Alphabet, Phraseology and CTAF 12.2 The 121.5 MHz Emergency Frequency, Transponder Codes and the AROC

13 Risk & Operational Procedures

13.1 Job Safety Assessment, Risk Assessment and the Hierarchy of Controls 13.2 Site Survey, Bystander Management, Emergencies and Giving Way

14 Operations, Airworthiness & Reporting (RKOP)

14.1 Remote Pilot Responsibilities, Crew Briefing and Ground Operations 14.2 Operational, Remote Pilot and Technical Logs 14.3 Airworthiness, Serviceability and Defect Reporting 14.4 Role Equipment, Sensors and Payload Implications 14.5 Accident and Incident Reporting to the ATSB 14.6 Abnormal Operations, Fail-Safes and Flight Termination 14.7 Operating Near Aerodromes and Above 400 ft AGL

6.1 GNSS, Compass, IMU and Geofencing

Key Takeaways Explain This Topic AI

A 3D GNSS fix generally needs at least 6-7 satellites with an HDOP below about 1.5; check both before takeoff.

Compass error from interference (rebar, powerlines, motors) can cause a flyaway during Return-to-Home because the controller steers on a wrong heading.

Excessive vibration contaminates IMU accelerometer data, causing drift, oscillations, or instability; balance props and calibrate the IMU on a level surface.

Geofencing is a safety layer that sets virtual height, radius, and no-fly boundaries, but it does not replace the pilot's legal responsibility under CASR Part 101.

Pre-flight sensor checks confirm GNSS fix, compass calibration and interference, IMU calibration, geofence settings, and current firmware before launch.

Last updated: August 2026

Sensors That Keep Your RPA Airborne

A remotely piloted aircraft (RPA) depends on a small suite of onboard sensors to know where it is, which way it points, and how it is oriented. Before every flight, a remote pilot must confirm these sensors are healthy, calibrated, and free from interference. This section covers the four sensor systems that most affect flight safety: GNSS (position), the compass/magnetometer (heading), the IMU (attitude), and geofencing (virtual boundaries enforced by the flight controller).

GNSS: Position, Satellites and HDOP

Global Navigation Satellite System (GNSS) is the umbrella term for satellite positioning constellations such as GPS (US), GLONASS (Russia), and Galileo (EU). The RPA's receiver uses signals from these satellites to compute its horizontal and vertical position. Two numbers matter most on the ground station before takeoff:

Satellite count — a 3D fix generally requires at least 6–7 satellites; more satellites give a more robust fix. A 2D fix (fewer satellites) lacks altitude accuracy and is not safe for automated flight.

HDOP (Horizontal Dilution of Precision) — a unitless measure of geometric satellite quality. Lower is better: an HDOP below about 1.5 is good; values above 2.0 indicate poor geometry and larger position error.

Check both numbers during your pre-flight. A strong satellite count with a low HDOP confirms the flight controller can safely compute position, hold a hover, and execute Return-to-Home ( RTH ) if the command-and-control ( C2 ) link is lost.

GPS Loss Behaviour

If GNSS signals drop out in flight — due to interference, jamming, or poor sky visibility near structures — the flight controller cannot maintain a stable position hold. Typical behaviours include:

The aircraft drifts with wind instead of holding station.

Some systems fall back to attitude mode (also called ATTI), where the autopilot holds level attitude and altitude but the pilot must manually correct position.

RTH may become unavailable or unreliable.

Anticipate this: know your aircraft's GPS-loss mode before you fly, keep it within visual line of sight, and be ready to take manual control. Do not launch if the fix is weak.

Compass/Magnetometer: Heading and Interference

The compass (magnetometer) provides heading — the direction the nose is pointing. It works by sensing Earth's magnetic field, which means it is vulnerable to local magnetic interference. Common interference sources near a drone include:

Ferrous metal in the airframe, launch surface, or a vehicle roof.

Electromagnetic fields from motors, ESCs, and power cables.

Reinforced concrete with rebar , and underground services.

Powerlines and metallic structures.

Compass error is dangerous because the flight controller uses heading to compute position-hold corrections and RTH bearing. A mismatch between true heading and sensed heading can cause the aircraft to fly in the wrong direction on RTH — the classic flyaway scenario.

Compass calibration teaches the flight controller the local magnetic environment. Calibrate:

After changing airframe components, motors, or battery type.

After travelling more than a few hundred kilometres from the last calibration site.

If the ground station reports a compass error or large interference value.

Always perform the compass interference check on the launch site before takeoff: rotate the aircraft through 360° and confirm the heading indication stays within tolerance and the interference value is below the manufacturer's limit.

IMU: Attitude, Vibration and Calibration

The Inertial Measurement Unit (IMU) combines accelerometers (which sense linear acceleration and gravity) and gyroscopes (which sense rotation rate) to determine the aircraft's attitude — pitch, roll, and yaw. The flight controller uses IMU data to keep the aircraft level and to respond to pilot inputs.

Vibration is the IMU's enemy. Excessive vibration from unbalanced props, worn motors, or loose mounts contaminates the accelerometer readings and can cause:

Drift in level hold.

"Toilet-bowl" oscillations in position hold.

In severe cases, the controller misinterprets vibration as attitude and over-corrects, destabilising the aircraft.

IMU calibration (a level calibration on a flat, stable surface) zeroes the accelerometers and gyros. Calibrate when the ground station prompts it, after firmware updates, or if the attitude indicator shows offset when the aircraft is level. Balance props and isolate the IMU board per the manufacturer's design to keep vibration within limits.

Geofencing: A Safety Layer, Not a Legal Substitute

Geofencing is a software feature that creates virtual boundaries the flight controller will not cross. Typical geofence parameters include:

A maximum height above ground level (AGL) — for example, 400 ft AGL.

A maximum radius from the recorded home point.

No-fly zones around controlled airspace, airports, or restricted areas.

Geofencing is a valuable safety net: if the pilot is distracted or the C2 link drops, the aircraft stops at the boundary rather than straying into controlled airspace. However, geofencing is not a substitute for legal compliance . The remote pilot remains responsible for obeying CASR Part 101, observing airspace restrictions, and holding any approvals required. Reasons you must not rely on geofencing alone:

Some systems allow the geofence to be overridden — know whether yours does.

Database no-fly zones can be out of date ; always check current airspace and NOTAM s.

A geofence height limit may not match the legal ceiling for your operation.

Treat geofencing as a backup safety layer, set it deliberately before takeoff, and never assume it replaces your own airspace and height checks.

Pre-Flight Sensor Checks (Summary)

Before takeoff, confirm the sensor stack is ready:

GNSS — satellite count sufficient for a 3D fix; HDOP low (about 1.5 or better).

Compass — calibrated recently; on-site interference check passed.

IMU — calibrated; no vibration warning; attitude indication level on the ground.

Geofence — set to the correct max height and radius for the operation; no-fly databases current.

Firmware — flight controller and battery firmware up to date.