This Rules/Policy document is provided to you and your organization as a starting point or maturity checkpoint for existing rules/policies. It is brought to you on behalf of Jim McConnell, Principal Owner, and Ask McConnell, LLC — A Converged Security Services Provider. The content is not meant to cover every circumstance, industry, law, regulation, contractual requirement, threat, environment, or risk, but it provides an easy, defendable, highly accountable starting point for any organization. Please consult with your legal counsel and insurance provider about added requirements. If you know of peers that you think would find value in these resources, please have them contact us. These will be updated on our website regularly. We are not legally protecting these documents; we just ask for credit, shout-outs, and referrals if you find them helpful. If you have recommended updates, we are all ears. And if you need Converged Security Consulting and Training, please reach out, we would be honored to serve you and your organization.

Corporate Drone Flight and Maintenance Log Tool

Jim McConnell | info@askmcconnell.com | askmcconnell.com

Drone (UAS) Management Policy

Updated: June 2025 – Using USA centric terminology

Operating a drone (UAS) on behalf of our organization is a privilege that carries local, county, state, federal legal responsibility and significant liability. Every flight is a public act conducted under FAA authority — traceable to a specific pilot, a specific aircraft, and a specific organization.

Key Definitions:

Drone / UAS — An unmanned aircraft system; any aircraft operated without a human pilot onboard. “Drone” and “UAS” are used interchangeably in this policy.

Pilot-in-Command (PIC) — The FAA-certificated pilot legally responsible for the safe conduct of each flight.

Visual Observer (VO) — A designated person who maintains unaided visual contact with the aircraft and assists the PIC in scanning for hazards during flight.

Part 107 — 14 CFR Part 107, the FAA rule governing commercial and non-recreational small UAS operations. Applies to all organizational drone use.

BVLOS — Beyond Visual Line of Sight. Flight where the PIC cannot maintain direct, unaided visual contact with the aircraft. Requires an FAA waiver.

LAANC — Low Altitude Authorization and Notification Capability. The FAA’s near-real-time authorization system for controlled airspace. Required before entering Class B, C, D, or surface E airspace.

Remote ID — FAA-required broadcast of identifying information from the drone during flight, per 14 CFR Part 89 (effective March 2024).

Scope: These rules apply to all drone operations conducted by or on behalf of [Organization Name], including the use of personally-owned aircraft for organizational purposes. Off-duty personal recreational use with no organizational connection is outside this policy.

I will hold a current, valid FAA Part 107 Remote Pilot Certificate before acting as Pilot-in-Command on any organizational flight, and I will keep my certificate number on file with [HR / Administration / designee] before my first flight.
I will ensure every flight includes at least one designated Visual Observer (VO) from the organization — physically present at the flight location, briefed on the flight plan and hazards, and in continuous voice or radio communication with me throughout the flight.
I will register every organization-owned aircraft with the FAA before its first flight, affix the registration number permanently and legibly to the aircraft, and label the aircraft with the organization’s name and contact information.
I will complete and document a pre-flight inspection before EVERY flight, covering airframe, props, motors, batteries, Remote ID status, controller/firmware, weather conditions, and airspace — and I will not fly if any item fails inspection.
I will check airspace before every flight using FAA B4UFLY, Aloft, or equivalent; obtain LAANC or DroneZone authorization before flying in Class B, C, D, or surface E airspace; and retain the authorization record with the corresponding flight log entry.
I will maintain unaided visual line of sight (VLOS) with the aircraft at all times. I will not conduct Beyond Visual Line of Sight (BVLOS) operations without a specific FAA waiver and written approval from [Executive Director / Pastor / City Manager / designee].
I will not fly directly over unprotected people, moving vehicles, or crowds. I will not assume my aircraft qualifies for Part 107 Category operations over people unless I have verified its specific FAA category certification.
I will not exceed 400 feet AGL without a specific airspace authorization, and I will not conduct nighttime operations (more than 30 minutes after official sunset) without approved anti-collision lighting and prior written authorization.
I will complete a flight log entry for every flight — initiated before takeoff and finalized immediately after landing — including date, my name and certificate number, VO name, location, airspace class, authorization number (if applicable), takeoff/landing times, maximum altitude, weather summary, battery used, and any incidents.
I will maintain a maintenance log for every organization-owned aircraft, recording all inspections, firmware updates, propeller replacements, battery service, and repairs.
I will store LiPo and LiHV batteries at the manufacturer-recommended storage charge level when not in active use, and I will NEVER store lithium batteries in a vehicle, in extreme heat, or at full charge for extended periods.
I will store all aircraft and related equipment in a secure, locked location when not in use, and I will not allow organization equipment to leave authorized custody without documentation.
I will not capture imagery over private property without the property owner’s consent, will not publicly distribute organizational drone footage without authorization, and will immediately preserve any footage that captures a security or safety incident.
I will report any flight incident — collision, flyaway, unexpected landing, near-miss with a manned aircraft or person, or property damage — to [designated authority] immediately and document it fully in the flight log. I will provide a complete written account for any FAA-reportable accident (serious injury or property damage exceeding $500) to support timely FAA filing.
I understand that operating without a valid Part 107 certificate, flying without a VO, or falsifying a flight log are violations of this policy. FAA fines arising from uncertified or unauthorized operations are my personal liability — the organization will not indemnify them.
I will perform and document a training flight at least once a quarter using organization-owned aircraft
I will not fly inside of any organization facilities without senior leadership approval and two VOs

Signature Note: I am a huge fan of wet signatures on these types of documents for accountability and investigation reasons. You can add the signature lines below to each rule/policy document, or have a collective wet signature with references in the Security Commitment Agreement document available on the One-Pager library page. Organizational preference.

_________________________________
Print Full Legal Name

_________________________________
(Blue Ink) Full Legal Signature
Style of signature must closely match Driver’s License

_________________________________
Date