Study guide
11.6 Threat and Error Management
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
11.6 Threat and Error Management
Key Takeaways Explain This Topic AI
A threat is a condition outside the pilot's influence that increases risk; an error is an action or inaction by the crew that deviates from intention or expectation.
An undesired aircraft state is the outcome when a threat or error is not managed, and recovering from one is the last line of defence.
Threats are managed by anticipating them in planning; errors are managed by trapping them with checklists, standard procedures and crew cross-checks.
Strategic risk management happens before the flight and tactical risk management happens during it — both are required and neither substitutes for the other.
Last updated: August 2026
The TEM Model
Threat and Error Management (TEM) is the safety framework most of modern aviation training is built on, and Schedule 4 codes it priority B for RPA. It uses three terms precisely.
Term Definition RPA example
Threat A condition outside the influence of the crew that increases operational complexity and must be managed Gusty wind, a nearby aerodrome, low sun, powerlines, an impatient client, an unfamiliar site
Error An action or inaction by the crew that leads to a deviation from intentions or expectations Failing to set the RTH altitude, launching from a steel surface, misreading the chart, skipping the site walk
Undesired aircraft state A position, configuration or condition that clearly reduces safety margin The aircraft inside controlled airspace, over a person, below reserve battery at range, orientation lost
The chain runs left to right: an unmanaged threat invites an error , and an unmanaged error produces an undesired aircraft state . Every link is an opportunity to intervene, and intervening early is cheaper than intervening late.
Managing threats
Threats are managed by anticipation , which is why they belong in planning rather than in flight. The site survey, the weather brief, the NOTAM check and the job safety assessment are all threat-identification exercises. For each identified threat, the question is: what will I do when this happens?
Threat: gusty afternoon wind. Management: fly in the morning, or set an abort wind figure and brief it.
Threat: powerlines crossing the site. Management: trace them during the walk, mark the crossing points, plan a route that avoids them, and brief the observer.
Threat: client wants the shot regardless. Management: state the go/no-go criteria before starting, with the client present.
Managing errors
Errors are managed by trapping them before they have consequences. Three mechanisms do most of the work:
Checklists. A written checklist moves memory items onto paper. Schedule 4 names checklists explicitly as an error-prevention tool. The value is in using it as a check — reading and confirming — not reciting it from memory while doing something else.
Standard operating procedures. Doing the same thing the same way every time makes a deviation visible. An operator whose pilots each have their own launch routine has no baseline against which anything looks wrong.
Crew cross-check. A second person who is expected to speak up catches what one person misses. This only works if the crew has been briefed that speaking up is required, and if the pilot demonstrably accepts it.
Recovering an Undesired Aircraft State
If a threat and an error both get through, the pilot is left managing the state itself — the last line of defence, with the least margin. The priorities are:
Stabilise. Stop the aircraft. Hover if safe, or climb clear of obstacles.
Assess. Height, position, battery, link quality, what is beneath the aircraft.
Decide. The safest recovery is usually the shortest path to a safe landing, not the one that saves the mission.
Act, then report. Recover the aircraft, then record what happened in the log and — if it is reportable — to the ATSB.
The most common error at this point is trying to save the job. An undesired aircraft state is where mission goals and safety diverge, and the pilot's job is to abandon the mission.
Risk Perception When Remote from the Aircraft
Schedule 4 topic 5(e) names something specific to remote piloting: risk perception when remote from the location of the RPA operation .
A crewed pilot shares the aircraft's fate. A remote pilot does not, and that changes risk perception in measurable ways. Research and accident experience both show that people accept greater risk when they are not personally exposed to the consequences. A pilot standing safely on the ground watching a $30,000 aircraft over a busy road is making a decision whose worst outcome falls entirely on other people.
Three defences:
Make the consequence concrete. Ask explicitly: if the aircraft failed right now, what would it hit and who would be hurt? The question converts an abstract risk into a specific one.
Use the hierarchy of controls. Eliminating the overflight is always better than mitigating it, and the hierarchy forces the question of whether the exposure was necessary at all.
Fly it as though you were in it. A useful discipline: if you would not be comfortable being underneath the aircraft, do not fly it over anyone else.
The effect is stronger still when the pilot is physically distant from the operating area — an EVLOS or BVLOS operation, or a large site where the aircraft is working several hundred metres away. The further the pilot is from the risk, the more deliberately it must be assessed.
Strategic Versus Tactical Risk Management
Schedule 4 topic 5(f) draws a distinction worth being precise about.
- Strategic Tactical
- When Before the flight During the flight
Tools Site survey, JSA, weather brief, NOTAM check, hierarchy of controls, DPP Continuous scan, telemetry monitoring, crew callouts, abort criteria
Question What could go wrong, and what will I do about it? What is going wrong now, and what do I do?
Timeframe Hours or days ahead Seconds
Both are required. Strategic risk management without tactical management produces a beautifully documented flight that flies into an unforecast squall. Tactical without strategic produces a pilot improvising continuously, who will eventually be surprised by something that a five-minute walk of the site would have revealed.
The relationship between them is that good strategic work reduces the tactical load . Every hazard identified and controlled before launch is one less thing competing for attention in flight — which matters enormously, because attention in flight is the scarcest resource a remote pilot has.
Crew Resource Management
CRM is TEM's practical delivery mechanism when more than one person is involved. Schedule 4 names it under threat and error management as well as under crew coordination. The core elements for an RPA crew:
Brief roles before launch — who flies, who maintains VLOS, who manages bystanders, who handles the payload.
Define the callouts — the exact words for "aircraft approaching", "person entering the area", "battery at 30 per cent", "abort".
Make assertion explicit. The observer must be told that raising a concern is required, and the pilot must visibly act on it. A crew that only speaks when spoken to provides no error trapping at all.
Debrief afterwards. What was the threat we did not anticipate? What error did we trap, and how? What will we change? A two-minute debrief after each job is the mechanism by which an operation actually improves.