Pilot Logbook Requirements for Australian Public Safety Flights
Public-safety drone flights can support police, fire and rescue, disaster response, and community policing across Australia, but every mission should leave a defensible record. The controlling rules come from the Civil Aviation Safety Authority (CASA) under the Civil Aviation Act 1988 and Civil Aviation Safety Regulations, particularly where flights rely on Part 101 or Part 132.
No universal Commonwealth form applies to every public-safety logbook. The legal minimum depends on the flight's operating basis, the operator's approval or certificate, the approved operations manual, and applicable state or territory records law. Agencies therefore need to connect mission data with incident handling while avoiding unnecessary collection of personal information.
Choose the Governing Operating Pathway
Classify the mission before selecting a form. Whether the agency owns the aircraft, engages a contractor, or relies on an emergency approval can change both the operator and the records that must be retained.
| Operating basis | When it commonly applies | Controlling record source |
|---|---|---|
| Part 101 ReOC | A non-commercial flight with an aircraft above 250 grams, or commercial activity within standard conditions | Part 101 and the ReOC holder's approved operations manual |
| Specific public-safety or emergency approval | A public authority conducting approved non-standard or emergency-response work | CASA approval conditions, the emergency operations manual, and task procedures |
| Part 132 commercial operation | A paid flight service provided by an authorised commercial operator | Part 132 and the authorisation holder's approved operations manual |
| Emergency provision relied upon | Urgent action to protect life or property where the applicable legal exception applies | The agency's procedure plus a record of the basis, conduct, and outcome |
An emergency does not automatically remove the duty to account for the flight. If a mission departs from standard conditions, identify the precise authorisation or emergency provision in the entry. If more than one operating basis could apply, the agency's authorised aviation lead should document the chosen pathway before deployment.
Record Every Mission as a Complete Entry
Make the entry while the facts are fresh. A controlled pilot logbook should identify the date, launch and landing times, aircraft registration or serial number, remote pilot and any controller, operating area, mission or incident number, purpose, approval reference, and abnormal events. Record precise launch and recovery points rather than only a suburb, because an incident review may need to establish who was present and what airspace applied.
Operational fields should show the line-of-sight check, airspace and authorisations, risk-assessment reference, people or overflight considerations, weather, battery and payload status, pre-flight and post-flight checks, defects, maintenance release, and imagery or other data captured. Where an approved manual makes these checks mandatory, an omission can be a compliance failure even when the flight itself was uneventful.
Corrections must preserve the original entry, author, date, and reason for change. Entries must never be backdated or reconstructed without an explicit late-entry notation. Australian record customs favour a 24-hour clock, unambiguous dates, local agency callsigns, and the relevant police, fire, or emergency-service incident number. Electronic entries are suitable when access controls, timestamps, backups, and an audit trail make them reliable and retrievable.
Apply Australian Operational Context
Australian geography makes precise location and communications records essential. Operations around Sydney, Melbourne, Brisbane, Perth, or Adelaide can encounter controlled airspace, high-rise obstruction, public-event restrictions, and significant radio-frequency congestion. The entry should therefore identify the airspace reference and any relevant CASA authorisation, rather than simply stating that the flight remained within visual line of sight.
In the Australian market, agencies commonly buy training, mapping, inspection, or emergency flight services from local suppliers. A contractor holding Part 132 may operate while the agency owns the aircraft, or a supplier may provide aircraft and pilots under a contract. The written arrangement should identify the legal operator, approval holder, pilot, records custodian, data controller, and party responsible for retaining and producing the log. An invoice alone does not settle those responsibilities.
Time and environmental details also need local discipline. Eastern Australia uses AEST or AEDT according to daylight-saving periods, while Perth uses AWST; recording UTC alongside local time prevents ambiguity in cross-agency reviews. For remote operations, include communications coverage, endurance, dust, rain, heat, and any GPS degradation. These details may explain a shortened flight, diverted landing, or missing data point.
Protect Privacy, Evidence and Retention
A log entry can contain personal information even when it omits names. A route, timestamp, serial number, or task reference may reveal a person's movements or link an aircraft to a police operation. Commonwealth agencies must consider the Privacy Act 1988 and Australian Privacy Principles, while police in New South Wales, Queensland, and Victoria work under their own privacy regimes and surveillance legislation. Use task numbers where practical, limit access to need-to-know staff, and align the log with the agency's privacy register and records schedule.
Some missions also capture health-related images or responder notes. A thermal image may not reveal a diagnosis, but associated material can be sensitive. If authorised personnel need clinical background, a reference such as lymph node metastasis guidance should remain in an approved clinical or briefing system rather than being attached to the flight log or included in a public release.
Treat the log as evidence, not merely administration. Under the Evidence Act 1995 and state equivalents, a contemporaneous digital record may help establish the time, place, participants, and sequence of an event, provided its integrity and provenance can be explained. Preserve metadata, export records in a stable format, maintain chain-of-custody notes, and record every correction or later annotation. CASA approval conditions commonly require operational records to be retained for at least three years; retain them longer when an evidentiary schedule, investigation, litigation, or legal hold applies.
Build a Controlled Recordkeeping Process
Implement the log as a controlled operational record. Assign a records custodian, use locked templates and sequential mission numbers, timestamp entries automatically where possible, reconcile flight logs with aircraft technical logs, and train pilots, controllers, supervisors, and evidence officers on the same minimum dataset. Close a mission only after its payload, imagery, defects, and handover are linked. Electronic logs should preserve version history and support prompt retrieval for CASA, an authorised investigator, or an evidence request.
Quality checks should compare a sample of missions with the flight authorisation, risk assessment, aircraft technical log, incident system, and access register. A discrepancy needs an explanation and auditable correction, not a silent overwrite. The manual should also state who may sign off an entry, when an incomplete emergency log is upgraded, and how retention exceptions are recorded.
Before the next public-safety flight, audit the most recent mission against the applicable CASA approval and operations manual, appoint a records owner, and circulate one retention and access rule to every operational team.