Skip to content
 

Form

Form - RPAS Flight and Battery Log

Document FSSMS-FRM-53Stage 2Revision 4Version 0.3.3

Topic pages open on your jurisdiction, and requirements tables show its line. You can change this on any page.

Purpose

One record per flight and one line per battery event, so the department can show every flight was lawful and every battery was fit, and so an occurrence can be traced to the aircraft, battery, pilot and conditions involved. The owner of the aircraft must keep a record of the pilots and crew and the time of every flight for 12 months, and records of maintenance, modification and repair for 24 months (Canadian Aviation Regulations [CA], 2026, s. 901.48); the department keeps both for the period in 05 Document Control and Records, longer when imagery is evidence. The published copy of any log identifies members by role and member number, not name.

Part A: Flight log (one per flight)

Field Entry
Flight number (year-sequence)
Date and local time of launch and landing
Incident number or training event
Location (address or coordinates)
Aircraft registration mark and department ID
Remote pilot in command (member number) and certificate type
Visual observer (member number)
Sensor operator (member number), if any
Tasking by (role) and purpose of flight
Airspace class; aerodromes or heliports within 3 NM; NOTAMs checked (Y/N)
NAV Drone authorization number (controlled airspace) or “not required”
SFOC or RPOC reference, if applicable
Manned aircraft expected or present; deconfliction confirmed with (role or agency); air-to-ground channel used
Weather at launch: wind and gusts, precipitation, temperature, visibility
Night flight (Y/N); lights confirmed
Pre-flight checklist completed: full or emergency column; abnormal items
Battery serial(s) used; start and landing percent for each
Maximum altitude AGL; maximum distance from pilot; VLOS maintained (Y/N)
Flight time (minutes)
Operation near or over people (Y/N); basis (certificate and aircraft declaration)
Data recorded (Y/N); file reference; downloaded to {{Records system}} by (member number) and time; chain of custody started (Y/N)
Privacy limits applied (what was not recorded)
Occurrence or anomaly (lost link, RTH triggered, hard landing, warning, intrusion, “Land now” call); occurrence report number
No-go or aborted flight: reason
Post-flight inspection: aircraft serviceable (Y/N); defects
Pilot signature or electronic sign-off
Chief pilot review date and initials

Part B: Battery log (one line per event per battery)

Battery serial / dept ID Date and time Event (charge, flight, storage discharge, inspection, retirement) Pre-event inspection pass/fail (swelling, damage, connector, heat) Percent before / after Cycle count after event Charger and location; bag or cabinet used; attended by (member number) Health or cell balance reading Anomaly Action (continue, quarantine, retire at manufacturer cycle limit or on any swelling, damage or heat; see RPAS Program element 5.10) Initials

Fields

Field Type Required Who completes
Flight number Text (year-sequence) Yes Pilot
Date, launch and landing times Date and time Yes Pilot
Incident number or training event Text Yes Pilot
Location Text or coordinates Yes Pilot
Aircraft registration mark and department ID Text Yes Pilot
Pilot, observer, sensor operator member numbers; certificate type Text Pilot yes; others when present Pilot
Tasking by and purpose Text Yes Pilot
Airspace class, aerodromes, NOTAMs checked Text and yes/no Yes Pilot
NAV Drone authorization number Text Yes in controlled airspace Pilot
SFOC or RPOC reference Text When applicable Pilot
Deconfliction details and air-to-ground channel Text Yes when any manned aircraft possible Pilot
Weather at launch Text and numbers Yes Pilot
Night flight and lights Yes/no Yes Pilot
Pre-flight checklist column and abnormal items Text Yes Pilot
Battery serials and percentages Text and numbers Yes Pilot
Maximum altitude, distance, VLOS Numbers and yes/no Yes Pilot
Near or over people and basis Yes/no and text Yes Pilot
Data recorded, file reference, download, chain of custody Text, time, yes/no Yes when recording Pilot or sensor operator
Privacy limits applied Text Yes when recording Sensor operator or pilot
Occurrence or anomaly and report number Text Yes when any occurred Pilot
No-go reason Text Yes for a declined or aborted flight Pilot
Post-flight inspection result Yes/no and text Yes Pilot
Pilot sign-off Signature or electronic Yes Pilot
Chief pilot review Date and initials Yes, monthly Chief pilot
Battery event line (all columns in Part B) Mixed Yes for every charge, flight, inspection and retirement Member handling the battery

References

Canadian Aviation Regulations, SOR/96-433 (Canada; consolidated to 2026-09-30; Subparts 302 and 303, airports and aircraft fire fighting, and Part IX, remotely piloted aircraft systems). https://laws-lois.justice.gc.ca/eng/regulations/SOR-96-433/

© 2026 The Human Factor · Licensed under CC BY-NC-SA 4.0 with the Adopting Agency Grant

General information only, not legal, medical or other professional advice. Verify every requirement against the current official text of the law, standards and manufacturer instructions that apply to you. Obtain your own legal review and consult your joint health and safety committee before adopting anything. You adopt, adapt, implement and rely on this material entirely at your own risk and on your own responsibility. Full terms: Terms of Use, thehumanfactor.ca.

Copyright, licence and legal notices

Connections

Pages linked to and from this page.