Tag: Part 107

Posted on

Building a UAS Operations Manual: Why Every Part 107 Pilot Needs One

The FAA doesn’t require most Part 107 operators to maintain a formal operations manual. That’s the wrong reason not to have one.

A UAS operations manual is three things simultaneously: your operational bible (the definitive reference for how your operation works), your legal protection (documented evidence that you operate to defined standards), and your credibility document (what enterprise clients and insurers ask for before they’ll hire or cover you).

Here’s what a professional UAS operations manual contains and why each section matters.

Organizational Information

Who operates this UAS program. Contact information. Certificate numbers for all pilots. Your operating entity if separate from your personal certificate. Emergency contacts.

This section exists so that anyone — a client, an insurer, a responding authority — can quickly identify who is responsible for the operation and how to reach them.

Aircraft Inventory and Configuration

Every aircraft you operate should be documented: make, model, serial number, FAA registration number, payloads, maximum takeoff weight, operating limitations, and maintenance history reference. Configuration changes — adding a new payload, replacing a flight controller — should be logged.

This documentation is what your insurer uses when you file a claim and what the FAA reviews if your aircraft is involved in an incident.

Standard Operating Procedures

This is the heart of the manual. SOPs define how every type of operation your company conducts is performed — step by step, to the same standard, every time.

At minimum, SOPs should cover:

  • Pre-flight inspection procedure
  • Site survey procedure
  • Launch and recovery procedure
  • In-flight monitoring protocol
  • Abort criteria and emergency procedures
  • Post-flight documentation procedure
  • Battery management and storage
  • Equipment maintenance schedule

SOPs are living documents. When you encounter a situation your SOP didn’t cover, you update the SOP. When you find a better way to do something, you update the SOP. The manual reflects your current best practice, always.

Emergency Procedures

What happens when the link fails? When the aircraft starts to fly-away? When there’s a medical emergency on site? When the aircraft goes into a water obstacle? When there’s an airspace intrusion?

Emergency procedures must be defined in advance, briefed before every operation, and practiced. The time to figure out what you’d do in a fly-away scenario is not during a fly-away.

Crew Roles and Responsibilities

Define every position in your operation: Remote Pilot in Command, Visual Observer, Crew Coordinator, Ground Safety Officer. Who has authority to call a stop. How communication flows. What each person monitors and reports.

For solo operators, this section may seem unnecessary — but when you add a second person to any operation, undefined roles are a safety hazard.

Airspace Authorization Procedures

How does your operation obtain, document, and manage airspace authorizations? What’s the process for LAANC requests? For COA applications? For TFR checks? This section should reference your specific tools and workflows.

Incident and Accident Response

Exactly what to do, in what order, if something goes wrong. NTSB reporting thresholds and timeline. Insurer notification procedure. Client notification procedure. Documentation requirements. Evidence preservation.

How FlightDeck Supports Your Operations Manual

FlightDeck operationalizes your SOPs by providing the structured data capture, airspace analysis, and documentation tools that your manual describes. Your pre-flight checklist procedure references FlightDeck’s logging workflow. Your airspace authorization SOP references the Airspace Checker and LAANC Tracker. Your post-flight documentation SOP references the flight record and report generation.

The manual defines the standard. FlightDeck executes it.

FlightDeck’s Compliance Manager also generates FAA-compliant COA application narrative content — the Operations Description, CONOPS, Emergency Procedures, and waiver guidance sections that form the core of a nationwide blanket COA application. Much of that content can be adapted directly into your operations manual.

Download the free 30-day trial and start building the operational infrastructure that makes your UAS business enterprise-ready.

Posted on

LAANC Authorization: A Complete Guide for Part 107 Commercial Pilots

LAANC — the Low Altitude Authorization and Notification Capability — transformed airspace authorization for commercial UAS pilots when it launched. What used to require weeks of manual coordination with FAA facilities now happens in seconds through an app. But LAANC has limits that many pilots don’t fully understand, and those limits become operationally significant at scale.

Here’s a complete guide to LAANC for commercial Part 107 operators: how it works, when it’s enough, when it isn’t, and how to manage authorizations across a large site portfolio.

How LAANC Works

LAANC operates through FAA-approved UAS Service Suppliers (USS) — apps like Aloft (formerly Kittyhawk), AirMap, and others. The system works by dividing controlled airspace into a grid of UAS Facility Map (UASFM) cells, each with an assigned altitude ceiling. These ceilings represent the maximum altitude at which the FAA has determined that drone operations can be safely accommodated without posing risk to manned aircraft at that location.

When you request a LAANC authorization in an app, the system checks your proposed altitude against the UASFM ceiling for your grid cell. If your altitude is at or below the ceiling, authorization is typically instantaneous. If you need to fly above the ceiling — even by one foot — you cannot use LAANC and must apply through FAADroneZone.

When LAANC Is Sufficient

LAANC works well for:

  • Operations in Class B, C, D, or E surface airspace at or below the published UASFM ceiling for your grid
  • Operations where altitudes are moderate and the site is away from airport runways and approach paths
  • Time-sensitive operations where waiting days for a COA is not practical
  • Sites with ceilings of 100–400 ft — the sweet spot for most commercial inspection and data collection work

When LAANC Is Not Sufficient

LAANC cannot be used when:

  • Your required altitude exceeds the UASFM ceiling for the grid cell — common near major airports where many cells show 0 ft ceilings
  • The site is in a zero-ceiling grid requiring manual FAADroneZone COA coordination
  • You need to fly above 400 ft AGL for any reason (requires a §107.51 waiver)
  • The operation is in Class B airspace in a zero-grid area near a major hub
  • The operation involves special circumstances not covered by LAANC’s automated approval scope

For communications tower inspection specifically — a primary market for commercial UAS operators — towers frequently require flight above the LAANC ceiling to reach the top of the structure. This is where the manual COA and altitude waiver process becomes essential, and where having pre-prepared COA narrative documentation saves significant time.

Managing LAANC Authorizations at Scale

Managing LAANC for a single site is easy. Managing it across 50, 100, or 300 sites on an active project is a different challenge entirely. Authorization windows expire. Primary authorizations get denied. Backup authorizations sit unused while you’re chasing a manual re-approval. Sites move dates. New sites get added mid-project.

FlightDeck’s LAANC Tracker was built specifically for this problem. Every controlled-airspace site in your project gets a tracker entry with a primary and backup LAANC reference number. When you export your authorization CSV from Aloft, FlightDeck reads it automatically — matching reference numbers to sites, writing authorization metadata, updating forecast dates, and applying color-coded status indicators.

The standout feature: when a primary authorization is denied or deauthorized, FlightDeck automatically promotes the backup reference number and re-runs the import. No manual intervention. No missed windows while you’re in the field.

Documenting Your Authorizations

Your LAANC reference number is your legal authorization to fly in controlled airspace. Carry it. Log it. Keep it associated with the mission record. If the FAA asks whether you were authorized — and they can ask — a reference number in a structured flight record is a professional answer. “I think I got a LAANC, I’d have to check the app” is not.

FlightDeck writes your authorization reference directly to the mission record alongside your flight data, weather, and site details. It’s all in one place, in a local database you control.

Download the free 30-day trial and manage your LAANC authorizations the way professionals do — systematically, at scale, with automatic backup promotion when approvals fail.

Posted on

The UAS Pilot’s Go/No-Go Decision: A Systematic Pre-Flight Risk Framework

The most dangerous moment in any commercial UAS operation isn’t in the air. It’s on the ground, when conditions are marginal, a client is waiting, you drove two hours to get here, and the temptation to press on is strong.

This is where most UAS incidents originate — not from technical failure, but from a go/no-go decision made under pressure, without a structured framework, by a pilot who overrode their own judgment because the external pressure to fly was stronger than the internal signal to stop.

A systematic pre-flight risk assessment changes that dynamic. The decision gets made before the pressure builds.

Why Structure Beats Judgment Under Pressure

Human judgment degrades under stress and workload. When you’re on a site with a client watching, equipment staged, and weather that’s “probably fine,” your risk assessment will be optimistic. This is called plan continuation bias — the tendency to continue a plan even when new information suggests you should stop.

A structured framework removes the decision from the moment of pressure. You defined your limits in advance. You either meet them or you don’t. The checklist decides, not your mood at the time.

The Five-Factor Risk Assessment

Before every mission, assess these five factors against pre-established thresholds:

1. Weather
Define specific limits — not vague ones. Not “acceptable conditions,” but: wind gusts below 15 kts, visibility above 3 SM, no precipitation, cloud ceiling above 500 ft AGL for the planned operating altitude. These are examples — your limits should match your platform and payload. Write them down. Apply them every time.

2. Airspace & Authorization
Is your airspace authorization confirmed and current? Has a TFR been issued since you last checked? Are there any active SUA restrictions overlapping your site? Every one of these is a binary check. If the answer to any is no or unknown, you’re not ready to fly.

3. Aircraft & Equipment
Is the aircraft airworthy? When was the last inspection? Battery health within limits? Props inspected for damage or delamination? Payload mounted and confirmed secure? This isn’t a mental walkthrough — it’s a checklist item by item.

4. Site & Hazards
Have you physically surveyed the launch and landing zone? Are there obstacles, wires, or people not visible on satellite imagery? Is the site consistent with your briefing, or has something changed? Surface conditions for multi-rotor launch?

5. Pilot Readiness
This one gets skipped. Don’t skip it. Are you current on your Part 107 knowledge? Are you rested? Are you under medication, stress, or any physical condition that affects your alertness? IMSAFE — Illness, Medication, Stress, Alcohol, Fatigue, Emotion — applies to UAS pilots just as it does to manned aviators.

Quantifying Risk: The Risk Score Approach

For operations where individual factors are marginal but not individually disqualifying, a numerical risk score helps. Assign each factor a score from 1–5 based on severity. Set a mission total threshold — if the combined score exceeds it, the mission is a no-go regardless of any individual factor being acceptable.

This prevents “death by a thousand cuts” — where five factors each rated “slightly elevated” combine into a mission that’s actually high risk.

Documenting the Decision

Log your go/no-go decision and the risk assessment that supported it. If you go: what were the conditions you accepted? If you scrub: what was the specific trigger? This documentation serves multiple purposes — it supports insurance claims, demonstrates professionalism to clients, and builds your own operational pattern recognition over time.

FlightDeck’s pre-flight logging captures conditions, authorization status, and pre-flight notes in the same record as your flight data. Your risk assessment and your flight outcome live together — which is exactly how you learn from your own operation.

Download the free 30-day trial and start building the structured pre-flight discipline that keeps your operation safe and your record clean.

Posted on

Crew Resource Management for UAS Pilots: Lessons from Manned Aviation

Crew Resource Management — CRM — is one of the most important concepts in manned aviation safety. It emerged from accident investigations that revealed most crashes weren’t caused by mechanical failure or bad weather. They were caused by human factors: poor communication, unchallenged errors, fixation on one problem while missing another, and captains who didn’t listen to co-pilots who saw the problem first.

Commercial UAS pilots can learn a great deal from CRM, even when flying solo. And for multi-pilot operations with a visual observer, crew coordinator, or remote pilot team, CRM isn’t optional — it’s the difference between a safe operation and an incident waiting to happen.

What CRM Actually Is

CRM is the effective use of all available resources — people, information, equipment — to achieve safe and efficient flight operations. It encompasses:

  • Situational awareness — knowing where you are, what’s around you, and what’s coming next
  • Decision-making — structured go/no-go processes rather than gut feel under pressure
  • Communication — clear, unambiguous information sharing between everyone on the operation
  • Workload management — distributing tasks so no one person is saturated while others are idle
  • Error management — catching mistakes before they become incidents, and managing them when they occur

CRM for the Solo UAS Pilot

Even flying solo, CRM principles apply. You are still managing multiple information streams simultaneously: aircraft telemetry, airspace, weather, battery state, site hazards, and client communication. Saturation of any one of these leads to the others being ignored.

Solo CRM practices that matter most:

Checklists over memory. Standardized pre-flight, in-flight, and post-flight checklists exist because human memory is unreliable under workload. Use them every time, without exception. Skipping a checklist because “you always do it this way” is exactly when you miss something.

Decision points set in advance. Establish go/no-go criteria before you arrive on site. Wind limits, visibility minimums, battery thresholds for return. Decisions made on the ground before pressure builds are better decisions than ones made while the aircraft is airborne and conditions are deteriorating.

Self-briefing. Talk yourself through the mission before launch. Hazards, contingencies, abort criteria. Saying it out loud — even alone — forces a completeness that mental review doesn’t.

CRM for Multi-Pilot Operations

When you add a visual observer, second pilot, or ground crew, the communication layer becomes critical. Accidents in multi-person UAS operations often involve someone who saw the problem but didn’t speak up, or did speak up and wasn’t heard.

Briefings are mandatory. Every person on the operation needs to know the mission profile, their specific role, the communication protocol, and the abort criteria before any aircraft is powered on.

Standard phraseology. “Traffic” means something specific. “Clear” means something specific. Establish shared language for your operation and use it consistently. Ambiguous communication in a fast-moving situation produces the wrong action.

Challenge and response. Critical actions — launch, altitude changes, approach to obstacles — should be called and confirmed. “Launching” / “Clear to launch.” Not assumed.

Authority gradient awareness. In manned aviation, junior crew members sometimes fail to challenge a captain’s bad decision. In UAS operations, a visual observer may not challenge a pilot who’s pressing on into unsafe conditions. Build a culture where every person on the team has both the authority and the expectation to call a stop when something isn’t right.

Managing Automation Bias

Modern UAS platforms are highly automated — return-to-home, obstacle avoidance, altitude hold. This is a safety asset, but it creates its own risk: automation bias, the tendency to trust automated systems without monitoring them critically.

Return-to-home doesn’t know about the crane that moved since you set it. Obstacle avoidance doesn’t see thin wires. Altitude hold doesn’t account for GPS drift near metal structures. Know your automation, know its limits, and never assume it’s covering something it may not be.

Logging as a CRM Tool

One underappreciated CRM function is the debrief. After every mission — especially ones where anything went differently than planned — document what happened, what the decision points were, and what you’d do differently. Over time, this builds a personal database of operational experience that improves every future flight.

FlightDeck’s structured flight logging captures the data that makes debriefs meaningful: conditions, authorization status, anomalies, post-flight notes. The data that helps you learn is only useful if it’s captured consistently.

Download the free 30-day trial and build the operational discipline that CRM demands into every mission from day one.

Posted on

Part 107 Renewal Is Coming — Is Your Operational History Ready?

Part 107 recurrent training and knowledge testing requirements mean that staying current as a commercial drone pilot is an ongoing obligation — not a one-time event. And while the FAA doesn’t currently require you to submit flight logs at renewal, your operational history matters more than pilots often realize.

Why Your Flight History Matters at Renewal

Your flight records tell the story of your professional development. When you’re bidding on contracts with larger clients, responding to RFPs from enterprise accounts, or applying for waivers that require demonstrated operational experience, your documented flight history is your evidence.

“I’ve been flying professionally for five years” is a statement. A structured record of 400+ logged commercial missions is proof.

Waiver Applications and Operational Records

Many Part 107 waivers — beyond visual line of sight, operations over people, night operations — require applicants to demonstrate relevant operational experience. The FAA’s waiver application process asks you to describe your mitigations and experience. Pilots with clean, detailed operational records are better positioned to make that case.

What to Have Organized Before Your Knowledge Test

Use your recurrency period as a trigger to audit your records:

  • Are all past missions logged with complete data?
  • Are your airspace authorizations filed and accessible?
  • Are your aircraft maintenance and inspection records current?
  • Is your certificate information and medical (if applicable) up to date?

The Difference Between Pilots Who Scale and Those Who Don’t

The commercial UAS operators who grow their businesses from solo gigs into real operations share a common trait: they treat record-keeping as a core function, not an afterthought. Clean records enable audits, support insurance claims, back up waiver applications, and signal professionalism to enterprise clients.

FlightDeck was built for exactly this — structured, local, field-ready flight operations management. Try it free for 30 days.

Posted on

The Real Cost of Disorganized UAS Flight Records (And How to Fix It)

Ask most solo commercial drone pilots how they manage their flight records and you’ll get a familiar answer: a spreadsheet, a folder of PDFs, maybe a notebook from the field. It works — until it doesn’t.

Here’s when disorganized flight records actually cost you.

The Client Audit

A client calls. They want documentation of every flight you conducted on their property over the past two years — locations, dates, weather conditions, crew, equipment serial numbers. How long does it take you to produce that?

If the answer is “more than an hour,” you have a records problem.

Professional clients — utilities, construction companies, insurance firms — increasingly require detailed operational records as a condition of hiring UAS contractors. If you can’t produce clean documentation quickly, you lose the contract. Or you keep it and spend a weekend reconstructing logs from memory.

The Insurance Claim

An incident happens. Your insurer wants a complete operational record: the preflight checklist, the flight time, the conditions, who was on site. Gaps in your records don’t just slow down the claim — they can affect coverage.

The FAA Inquiry

Under 14 CFR Part 107, you’re required to make your aircraft available for inspection and to provide records upon FAA request. Having a clean, organized record of your operations isn’t just good practice — it’s a regulatory obligation.

What Good UAS Flight Records Look Like

A properly maintained flight record for each mission should capture:

  • Date, time, and duration
  • Location (GPS coordinates, not just a description)
  • Aircraft make, model, and serial number
  • Pilot in command name and certificate number
  • Crew and visual observer information if applicable
  • Weather conditions at time of flight
  • Airspace authorization reference (LAANC or waiver number)
  • Preflight inspection completion
  • Any incidents or anomalies
  • Post-flight notes

That’s a lot of data to manage in a spreadsheet. It’s nothing for purpose-built software.

Moving to Structured Flight Logging

The shift from ad-hoc record keeping to structured flight logging is one of the highest-leverage improvements a solo commercial operator can make. You do the same work — you just capture it in a system that makes it retrievable, reportable, and professional.

FlightDeck stores all of this in a local SQL database. You log the mission, the data is structured, and when a client or auditor asks for records, you pull a report instead of digging through folders.

Download the free 30-day trial and log your next mission in FlightDeck.