Study guide
6.3 Automated Flight Management Systems (RAFM)
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.3 Automated Flight Management Systems (RAFM)
Key Takeaways Explain This Topic AI
RAFM is a common Part 101 MOS unit: section 4 applies it to any RPA in any category "whether operated under a manual or an automated flight management system", so it cannot be skipped by pilots who hand-fly.
Automation never transfers legal responsibility - the remote pilot in command still owns visual line of sight, the 400 ft AGL limit and every other standard operating condition on an automated mission.
The most common AFMS trap is a return-to-home altitude set below an obstacle on the return path, or a home point captured before a stable GNSS fix.
Loss of GNSS degrades the aircraft to attitude (ATTI) mode: position hold and return-to-home stop working and the RPA drifts downwind until the pilot flies it manually by visual reference.
An IMU fault corrupts the attitude estimate itself, so the aircraft may pitch or roll away under its own control input - take manual control and land as soon as practicable rather than trusting a failsafe.
Last updated: August 2026
What an Automated Flight Management System Is
An automated flight management system (AFMS) is the combination of flight-controller firmware, navigation sensors and ground-station mission-planning software that lets an RPA fly a pre-programmed profile without continuous stick input. On a typical survey multirotor it is the autopilot plus the mission-planning app: you draw a route or a survey grid, set altitude, speed and camera triggers, upload the plan, and the aircraft flies the pattern itself.
RAFM is the Part 101 MOS knowledge unit covering this material, and it is a common unit . MOS section 4 applies it to any RPA in any category "whether operated under a manual or an automated flight management system" , and Schedule 2 lists it in Appendix 1 alongside RBAK, RACP, RBMO, REES, RHPF, RKOP and RORA. You cannot skip it on the grounds that you hand-fly everything. Its single Schedule 4 topic carries priority A , so expect it to be examined directly.
It helps to think of RPA automation as a ladder of levels rather than an on/off switch:
- Level What the pilot does What the system does Typical use
- Manual / rate Commands rotation rates continuously Motor mixing only Confined-space recovery, sport flying
Stabilised (ATTI) Commands attitude, corrects drift manually Holds level attitude and (usually) altitude GNSS-denied or GNSS-degraded flying
Position hold Commands position, monitors Holds a three-dimensional position using GNSS Hovering inspection, photography
Waypoint / mission Plans, monitors, intervenes Flies a programmed route and triggers the payload Survey, mapping, linear inspection
Return to home (RTH) Monitors, can override Climbs to a set altitude and returns to the recorded home point Link-loss and low-battery failsafe
Automation does not change your legal position. You remain the remote pilot in command , the RPA must stay within visual line of sight unless you hold a separate approval, and every standard operating condition applies to an automated mission exactly as it does to a hand-flown one. "The drone was flying its programmed mission" is not a defence.
Precautions When Programming a Mission
Most AFMS occurrences are planning errors rather than hardware failures, so work through a fixed pre-programming discipline every time:
Check Why it matters
Home point recorded and confirmed The aircraft may latch the home point at first GNSS fix. If that happens in a car park 300 m away, RTH flies there, not to you.
RTH altitude above the tallest obstacle on the return path RTH normally climbs to a set height then tracks straight home. A 40 m RTH altitude with a 55 m transmission tower on the direct line is a collision.
AGL versus AMSL, and terrain along the route A plan flown at constant altitude over rising ground closes on the terrain; over falling ground it can exceed 400 ft AGL even though the number never changed.
Every waypoint altitude against the 400 ft AGL limit The height limit applies at each point of the route, not to the launch point.
Geofence, airspace and approval boundaries Manufacturer geofence databases are advisory and can be stale. They are not a substitute for checking the VTC and NOTAMs.
Battery reserve for the whole route plus RTH Budget the return leg and a reserve, into wind, not just the survey grid.
Failsafe action on link loss Confirm whether the aircraft is set to hover, land or RTH, and that the choice suits the site.
Units and coordinate datum Feet versus metres, and a mismatched datum, both put the aircraft somewhere you did not intend.
Payload triggers and gimbal angles A mis-set trigger interval wastes the sortie and tempts a rushed, unplanned reflight.
After uploading, verify the plan on the aircraft, not just in the app . Read the uploaded route back, confirm the waypoint count and altitudes, and walk the first leg visually before you commit. Brief your observer on what the aircraft is about to do so that a deviation is obvious to both of you, and keep your hand on the controls with the manual-override mode selected and rehearsed.