Study guide
14.2 Operational, Remote Pilot and Technical Logs
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
14.2 Operational, Remote Pilot and Technical Logs
Key Takeaways Explain This Topic AI
A RePL holder operating under a ReOC must keep a remote pilot log recording accumulated flight time.
The Part 101 MOS requires the log to record RPA details, the date, location and duration of each flight, and separate accumulated times for night, VLOS, EVLOS, BVLOS and simulated operations.
Traditional and RPA flight hours may be recorded in the same logbook but must not be aggregated into a single total.
The technical log is the aircraft's record: defects, rectifications, component changes, firmware versions and maintenance actions.
Last updated: August 2026
Three Logs, Three Purposes
Record keeping is not administrative decoration. Chapter 10 of the Part 101 MOS prescribes the records a ReOC holder must maintain, and Schedule 4 makes keeping them a named responsibility of the remote pilot.
Log Belongs to Records Answers the question
Operational log The operation Each flight: date, location, aircraft, pilot, purpose, duration, occurrences What flights did this operator conduct?
Remote pilot log The pilot The pilot's accumulated flight time, broken down by operation type What experience does this pilot have?
Technical log The aircraft Defects, rectifications, component changes, firmware versions, maintenance Is this aircraft serviceable?
The Remote Pilot Log
AC 101-01 states the requirement directly: a RePL holder operating under a ReOC must keep a remote pilot log to record their accumulated flight time operating RPA. The Part 101 MOS prescribes what the log records:
RPA details — the aircraft flown.
Date, location and duration of each flight.
Separate accumulated flight times for operations conducted:
- at night
- within VLOS
- within EVLOS
- beyond VLOS
Accumulated flight time in simulated operation of the RPAS, including details of the type of operations simulated.
The separation matters because the categories carry different privileges. An operator applying for a BVLOS approval, or a pilot being signed off for night work, must be able to demonstrate relevant experience — and only a log that separates those totals can do it.
Electronic and traditional logbooks
Both are acceptable, with conditions:
An electronic logbook may be used , but AC 101-01 requires it to include an auditing function that ensures the veracity and accuracy of the data entered. A spreadsheet anyone can retrospectively edit does not meet that bar.
A traditional pilot's logbook may be used and can be purchased from an aviation store. RPA hours may be recorded in a separate column — but traditional and RPA hours must not be aggregated . A pilot with 400 hours in a Cessna and 200 hours on a multirotor has two separate totals, not 600 hours.
Why the log matters to the pilot personally
Beyond compliance, the remote pilot log is the pilot's professional record. It is the evidence for the 5-hour minimum experience required for an initial RePL, for a type or category addition, for a ReOC's recency requirements, and for an insurer's or a client's due diligence. Backfilling it from memory months later produces a document that is worth very little to anyone.
The Technical Log
The technical log travels with the aircraft rather than the pilot, and it is the document that answers whether the aircraft is fit to fly. It should record:
Flight hours or cycles accumulated on the airframe and on life-limited components.
Defects — every one, including the ones that did not stop the flight. "Motor 3 warm after landing." "Intermittent telemetry dropout at 400 m." "Small nick in propeller 2, replaced."
Rectifications — what was done about each defect, by whom, and when.
Component changes — motors, ESCs, propellers, batteries, GNSS modules, with part identification.
Firmware versions — aircraft, controller and smart battery, and the date of each update.
Scheduled maintenance carried out against the manufacturer's schedule.
Any occurrence that damaged or may have damaged the aircraft, including hard landings.
Why "minor" entries are the valuable ones
A single "motor 3 warm" entry is noise. The same entry on three consecutive flights is a trend , and a trend is what allows a bearing to be replaced on the bench rather than fail 300 m downrange. The whole value of a technical log is that it turns individual observations into a pattern that no one's memory would have assembled.
This is also the mechanism by which the maintenance controller does their job. Under a ReOC the MC is responsible for ensuring the aircraft are serviceable, that maintenance is done by competent personnel, that records are kept, and that defects are investigated. The MC cannot investigate a defect that was never written down.
The Legal Backdrop
Section 20AA(4) of the Civil Aviation Act 1988 applies to all aircraft, RPA included. It provides that an owner, operator, hirer or pilot must not commence a flight, or permit one to commence , if:
- there is an outstanding maintenance requirement imposed by or under the regulations;
- the aircraft will require maintenance before the flight can end ; or
there is a defect or damage that may endanger the safety of the aircraft, or any person or property.
Read that against the technical log and the connection is obvious: the log is how you know whether any of those three conditions applies. A pilot who does not consult the technical log before flight has no basis for the declaration that the aircraft is fit to fly.
Retention and Access
Practical rules:
Keep records for the period the operator's DPP and the MOS require , and longer if an insurer or client demands it.
Make them accessible — a technical log locked in an office is no use to a pilot deciding whether to launch at a remote site. Digital records with offline access solve this.
Make entries at the time , not at the end of the week. A defect written down two days later loses the detail that would have identified the cause.
Never backdate or amend an entry silently. If a correction is needed, add a new dated entry explaining it. An audit trail that can be quietly rewritten is worth nothing to CASA, to an insurer, or to an investigation.
Treat the three logs as the operation's memory. Everything else — competency, airworthiness, approvals, insurance claims and accident investigation — depends on them being complete and honest.