Category: Compliance

Posted on

Flying in Controlled Airspace Without an Internet Connection: How FlightDeck’s Airspace Checker Works

Cloud-based airspace tools work well when you have a connection. At a rural tower site with marginal or absent cell signal, they don’t work at all. The question of whether you’re authorized to fly at a given location needs an answer before you set up equipment — not after you’ve driven two hours and discovered the app won’t load.

FlightDeck’s Airspace Checker runs against locally stored FAA data files. It answers the authorization question with no internet connection required.

What Gets Checked

The Airspace Checker evaluates each site against five categories of FAA data.

Airspace classification uses FAA polygon data to determine whether a site falls in Class B, C, D, E, or G airspace and whether Part 107.41 authorization is required. The classification drives the authorization pathway — LAANC, DroneZone COA, or no authorization required.

UASFM grid lookup reads the FAA’s UAS Facility Map data to determine the LAANC ceiling altitude available at each site. This is the number that determines how high you can fly via instant LAANC authorization and whether your operating altitude requires Further Coordination or a manual COA.

LAANC eligibility is evaluated automatically based on the airspace class and grid altitude. Sites where LAANC is sufficient get one determination. Sites in zero-grid Class B or Class C airspace — where the LAANC ceiling is 0 feet — are flagged as requiring a manual FAA DroneZone COA.

Special Use Airspace checks identify any restricted areas, Military Operations Areas, prohibited areas, and TFR-equivalent restrictions within 0.5 nautical miles of the site. Proximity to special use airspace doesn’t automatically prevent operations, but it’s information your pre-flight risk assessment needs.

Nearest airport analysis identifies the closest airport by Haversine distance, with ICAO identifier, airport type, airspace class, and cardinal bearing. The check also flags sites where the operating altitude exceeds 400 feet AGL and is more than 400 feet above the structure, which indicates a Section 107.51(b) waiver may be required.

The Results Grid

Results are displayed in a color-coded grid. Deep green indicates LAANC-authorized — the site can be flown with standard LAANC auto-approval or 72-hour coordination. Deep red indicates a COA or waiver is required — LAANC is not sufficient. Other indicators appear for Class G sites and sites with special use airspace conflicts.

The Complete Workflow button runs all four analysis steps in sequence — Load FAA Data, Load Sites, Check All Sites, and TFR Check — without stepping through each action manually. For daily project analysis, this is the standard approach.

Keeping FAA Data Current

The offline check requires that local FAA data files be current. The built-in FAA Data Updater fetches the latest UASFM grids, class airspace boundaries, SUA polygons, and airport data on demand. Running the updater periodically — before a new project starts, or whenever the FAA publishes updates — keeps the offline database current.

The TFR check is a separate online step. TFRs are too dynamic for a static local database — they’re issued and cancelled on short notice. The Airspace Checker’s primary analysis runs offline; the TFR overlay is the one component that requires connectivity when it’s available.

PDF Export

The Airspace Checker generates a professionally formatted PDF report of results, ready for signature and submission as part of a COA application or project compliance record. The report includes the authorization determination for each site, the nearest airport data, and any special use airspace conflicts — the information that typically needs to be documented in a pre-flight record or formal authorization package.

For operators managing projects with COA requirements, having a printable authorization summary per site is the difference between a documented compliance record and a verbal account of what the app said.

Try FlightDeck free for 30 days.

Posted on

Operations Over People: What Part 107 Actually Allows and How to Stay Compliant

The ability to fly a drone over people is one of the most commercially valuable — and most frequently misunderstood — capabilities in the Part 107 rulebook. Events, real estate, construction sites, public spaces, urban environments: a significant portion of high-value commercial UAS work involves operating in proximity to people. The rules that govern this are specific, tiered, and carry meaningful compliance consequences when they’re violated.

Here’s the complete practical guide to Part 107 operations over people.

The Four-Category Framework

The FAA established a four-category framework for operations over people based on the risk posed by the aircraft. The categories are defined primarily by aircraft weight, kinetic energy on impact, and the presence of exposed rotating parts. Each category has distinct requirements for the aircraft, the pilot, and the operation.

Category 1 — Lowest Risk

Aircraft requirement: 0.55 pounds (250 grams) or less. No exposed rotating parts that could lacerate human skin.

Pilot requirement: Standard Part 107 certification. No additional approval needed.

Operations: May operate over people, but not over moving vehicles or open-air assemblies.

The practical reality: very few commercial platforms that carry useful payloads weigh 250 grams or less. Category 1 primarily applies to micro drones. Most commercial inspection, mapping, and media production platforms are significantly heavier.

Category 2 — Moderate Risk

Aircraft requirement: Must meet FAA-accepted means of compliance demonstrating that impact with a human would not cause injury at or above the threshold of serious injury. No exposed rotating parts that could lacerate. Aircraft must carry an FAA-accepted declaration of compliance (DoC).

Pilot requirement: Standard Part 107 certification.

Operations: May operate over people and moving vehicles. May operate over open-air assemblies.

The DoC requirement is critical: the manufacturer must have filed an FAA-accepted declaration of compliance, and the aircraft must be identified on the FAA’s accepted DoC list. You cannot self-certify your aircraft as Category 2. Check the FAA website for the current accepted DoC list.

Category 3 — Higher Risk, Restricted

Aircraft requirement: Same DoC requirement as Category 2. The kinetic energy threshold is higher, but the operational restrictions are correspondingly tighter.

Pilot requirement: Standard Part 107 certification.

Operations: May operate over people only within a restricted-access site where all people in the area are on notice that a drone may fly over them. May NOT operate over open-air assemblies.

The restricted-access and notice requirements for Category 3 make it most applicable to controlled work environments: secured construction sites, private property operations with a controlled perimeter, and similar scenarios where the operator can ensure bystander notification.

Category 4 — Airworthiness Certificate

Aircraft requirement: Must hold an FAA airworthiness certificate (like a manned aircraft). This is a significant certification undertaking.

Pilot requirement: Standard Part 107 certification.

Operations: Must comply with the operating limitations specified in the aircraft’s FAA-approved flight manual. May operate over people and moving vehicles if the flight manual permits it.

Category 4 is currently relevant to a small number of highly specialized UAS platforms and is not a practical path for most commercial operators.

What “Open-Air Assembly” Means

The FAA defines an open-air assembly as a gathering of people that is open to the public. Concerts, sporting events, street fairs, parades — these are open-air assemblies. Only Category 2 aircraft (with accepted DoC) may operate over them. This is one of the most important practical limits for event photography pilots to understand.

What You Cannot Do Under Any Category

  • Operate over moving vehicles on public roads (unless the aircraft meets Category 2 or higher requirements and the specific operation permits it)
  • Operate over a person not involved in the operation unless you meet the category requirements for that scenario
  • Override weight or DoC requirements by assessing the risk yourself — the categories are the framework, not a suggestion

Documentation and Pre-Flight Planning

For operations involving people, documentation of your aircraft’s category compliance — the DoC reference, the aircraft serial number, and a record of the operation type — belongs in your mission record. If an incident occurs involving a person, your compliance documentation is the first thing the FAA will review.

FlightDeck’s structured mission logging captures the full pre-flight record including aircraft configuration, site conditions, and operational notes. Building the habit of logging operations-over-people compliance details into every relevant mission record is the mark of a professional operation.

Download the free 30-day trial and maintain the operational record that demonstrates your compliance — mission by mission, site by site.

Posted on

Night Time UAS Operations Under Part 107: Rules, Requirements, and Real-World Tips

Night UAS operations under Part 107 changed significantly with the FAA’s 2021 regulatory update. What previously required a specific waiver is now permitted for certificated Part 107 pilots — but with requirements that many pilots still don’t fully understand or consistently meet. Flying at night without complying with those requirements isn’t just a legal risk; it’s a genuine safety risk in an environment where your visual reference margin is already reduced.

Here’s the complete practical guide to night UAS operations under Part 107.

What Changed in 2021

Prior to the 2021 rule update, night operations required a Part 107 waiver — a lengthy application process with no guarantee of approval. The update removed the waiver requirement for night operations, replacing it with a mandatory equipment requirement and recurrent training obligation.

Night operations are now permitted for Part 107 pilots who:

  • Have completed the updated recurrent knowledge test (which covers night operations content)
  • Have an aircraft equipped with anti-collision lighting visible for at least 3 statute miles
  • Comply with all other applicable Part 107 requirements including airspace authorization

When Does “Night” Begin?

Under Part 107, night is defined as the period between the end of evening civil twilight and the beginning of morning civil twilight. Civil twilight ends 30 minutes after official sunset at your location. This is not the same as full dark — it’s when the sun is 6 degrees below the horizon and ambient light has dropped to a defined threshold.

This matters because civil twilight varies by location and date. On a summer evening in Alaska, civil twilight ends very late. In December in the southern states, it ends earlier. Always calculate civil twilight for your specific location and date, not a general approximation.

Anti-Collision Lighting Requirements

The anti-collision lighting requirement is specific: the light must be visible for at least 3 statute miles. This is a distance requirement, not a brightness specification. The practical implication is that not all factory-installed lighting on consumer and prosumer drones meets this threshold — particularly older platforms designed before the rule change.

Verify that your specific aircraft’s lighting configuration meets the 3-mile visibility standard. If it doesn’t, aftermarket anti-collision lighting solutions are available for most platforms. This is not optional — operating at night without compliant lighting is a violation regardless of how visible you think the aircraft is.

The lighting must also function properly. Pre-flight verification of anti-collision light operation should be part of your night operations checklist, not assumed.

Airspace Authorization Still Required

Night operations do not change airspace requirements. If your planned operation is in controlled airspace, you still need LAANC authorization or a COA. Many pilots conflate the waiver removal with a general relaxation of night rules — it isn’t. Airspace authorization is independent of the time-of-day operating rules.

Practical Night Operations Safety

Site survey during daylight. Always survey your operating area before the light drops. Hazards visible in daylight — wires, antennas, trees — may be invisible at night even with good ambient lighting. Know your environment before you need to navigate it in reduced visibility.

Fly conservatively at reduced speed. Your reaction time to emerging hazards is reduced at night. Obstacle avoidance systems on many platforms are camera-based and perform poorly or are disabled in low light. Fly slower, with wider margins, than you would in daylight.

Orientation awareness. Maintaining visual orientation of an aircraft at night is cognitively more demanding than in daylight. Know your aircraft’s lighting orientation — which lights are on the front, which are on the rear — so you can read attitude and heading from the lights alone. Practice this in a controlled environment before a client job.

Battery temperature. Cooler night air affects LiPo performance, particularly in late summer and fall when temperatures drop significantly after sunset. Use fresh, warm batteries and plan for reduced flight times compared to your daytime performance baseline.

Ground lighting. Mark your launch and landing zone with ground lighting visible from operating altitude. This gives you a positional reference and makes safe landing execution faster and more reliable in the dark.

Logging Night Operations

Night operations should be logged distinctly in your flight records — noting civil twilight time, lighting configuration confirmed, and any conditions specific to the night environment. This documentation supports your operational history for waiver applications (if you pursue BVLOS or other advanced operations) and demonstrates professionalism to enterprise clients who review your safety records.

FlightDeck captures the full pre-flight and post-flight record for every mission, with fields for conditions, notes, and authorization status — building the structured night operations log that matters when clients ask about your experience.

Download the free 30-day trial and start logging your night operations with the same professional standard you apply to every other mission in your portfolio.

Posted on

4th of July & the 250th: What Drone Pilots Need to Know Before Flying at Dusk

July 4, 2026 isn’t just Independence Day — it’s the 250th anniversary of the United States. The Semiquincentennial. Every major city, countless small towns, and millions of people will be outside, looking up, celebrating with fireworks displays, parades, and public gatherings unlike anything seen in recent memory.

For commercial and recreational drone pilots, this creates one of the most complex and restricted flying environments of the entire year. Here’s everything you need to know before you even think about launching on or around July 4th.

TFRs Will Be Everywhere — and They’ll Change Right Up Until Launch

Temporary Flight Restrictions around fireworks displays and major public gatherings are standard FAA practice on July 4th. In a typical year, TFRs cover dozens of major display sites. For the 250th, expect significantly broader coverage, including:

  • Pyrotechnic TFRs extending to 3 nautical miles radius and 3,000 ft AGL around major displays
  • Security TFRs around presidential and governmental events that may cover entire metro areas
  • Stadium and venue TFRs for large organized celebrations
  • Temporary no-drone zones in high-traffic public areas issued by local authorities

The critical issue: TFRs for July 4th events are often not published until a day or two beforehand, and they frequently update or expand right up to the event. A site that was clear when you checked Monday may have a TFR by Wednesday afternoon.

This is exactly why FlightDeck’s live TFR checking tool matters. It monitors every site in your project queue against active TFRs in real time and alerts you when a TFR overlaps any of your planned sites — including new TFRs issued after your last manual check.

Dusk Operations: The Light You’re Planning For Isn’t the Light You’ll Have

Most photographers and videographers want to fly at dusk on July 4th — the golden hour before dark, catching fireworks launches against a deepening sky. This creates specific operational challenges that are different from either daytime or full night operations.

Civil twilight vs. legal night. Under Part 107, night operations require either a waiver (under older rules) or compliance with the anti-collision lighting requirements that took effect after the 2021 rule update. Civil twilight — the period from sunset until 30 minutes after — is defined as the beginning of night for Part 107 purposes. You need to know exactly when civil twilight begins at your specific location and plan accordingly.

Visual acuity degrades faster than you expect. Your eyes adapt slowly to changing light. At dusk, the transition from “I can see fine” to “I can’t clearly determine orientation” happens faster than pilots anticipate. Know your aircraft’s lighting configuration and whether it meets the 3-statute-mile visibility requirement for night ops before the light drops.

Battery performance at night. Summer evenings can be warm, which helps battery performance, but if temperatures drop after sunset, expect reduced flight times. Plan conservative battery margins for dusk operations where a landing in reduced visibility takes longer to execute safely.

Crowd Density and the Operations Over People Rules

July 4th gatherings involve dense crowds — exactly the scenario that Part 107’s operations over people rules are designed to address. Unless you have the specific approvals for Category 2, 3, or 4 operations over people with appropriate aircraft certification, flying over or directly above crowds is prohibited.

For commercial operators with a legitimate mission adjacent to a 4th of July event, the crowd consideration requires careful site planning. Know where the crowd is, know its boundary, and maintain your operational footprint clear of it. Have an abort plan that accounts for crowd movement if people shift toward your operating area.

Local Restrictions Beyond Part 107

Many jurisdictions have local drone ordinances that add restrictions beyond federal rules, and local authorities often issue special event restrictions for major public gatherings. These may not appear in FAA systems. Check your local city and county regulations, and if flying near any permitted event, verify directly with the event organizer and local authority whether drone operations are permitted.

The 250th Anniversary Commercial Opportunity

For commercial UAS pilots with the right authorizations and a professional operation, the 250th anniversary is a genuine content opportunity. Municipal clients, media companies, event organizers, and tourism boards are commissioning aerial coverage of Semiquincentennial events nationwide. If you want to pursue this work, the time to get your authorizations, permits, and client agreements in place is now — not July 2nd.

FlightDeck’s Airspace Checker analyzes your specific site against the full FAA airspace database, identifies LAANC eligibility, and generates the authorization path documentation you need to support a client engagement or permit application. The Compliance Manager generates COA narrative content for controlled airspace operations that can’t use LAANC.

Download the free 30-day trial and have your airspace analysis and TFR monitoring running before July 1st. The 250th is a once-in-a-lifetime event — be the operator who was prepared for it.

Posted on

Pilot Currency, Drone Maintenance Logs, and the Compliance Blind Spot Most Operators Have

Most commercial UAS operators know when their Part 107 certificate expires. Fewer track pilot medical currency, insurance expiration, individual aircraft maintenance intervals, and battery health in a single system — and most don’t find out that’s a problem until an audit, an incident, or a client’s compliance questionnaire forces the issue.

These are the records that prove your operation was conducted safely and legally. They don’t need to be elaborate — but they need to exist, and they need to be current.

What Compliance Actually Requires You to Track

For a commercial UAS operation, the baseline compliance record set includes Part 107 certificate numbers and expiration dates for every pilot, medical certificate class and currency where applicable, insurance policy expiration, FAA registration numbers for every aircraft, and aircraft-specific maintenance records.

COA applications require you to list your RPIC roster with certificate numbers. Insurance certificates come up in client onboarding. Maintenance records matter if an incident occurs and the question becomes whether the aircraft was airworthy. These aren’t theoretical requirements — they’re documents that get requested, and “I didn’t keep that” is not an acceptable answer in any of those situations.

FlightDeck’s Compliance Manager

The Compliance Manager in FlightDeck tracks all of this in a structured database, organized into tabs that mirror how the information is actually used.

The RPIC Roster tab records each pilot’s full name, contact information, Part 107 certificate number and expiration, medical certificate class and expiration, and insurance expiration. Every expiration date gets a status indicator — green for current, yellow for approaching, red for expired or critically close. If any single expiration is red, the overall pilot status shows red. The status rolls up so you can see at a glance whether every pilot on your roster is current.

The Aircraft Fleet tab records make, model, FAA registration number, airframe serial number, flight controller serial number, and Remote ID module — the fields that go into COA applications and appear on incident reports.

The Maintenance Log

The Maintenance Log tab is the flight-by-flight inspection record. Each entry records the date, the RPIC, the aircraft by FAA registration and model, flight hours, whether props were inspected, battery condition, whether any cracks or structural issues were found, screw tightness, firmware versions for both aircraft and remote, software version, and GPS/RTK status. There’s also a notes field for anything that doesn’t fit a checkbox.

These entries are written from the Drone Maintenance app and read by the Compliance Manager, which means the record is populated as part of normal pre- and post-flight operations rather than as a separate administrative task.

The entire maintenance history is filterable by RPIC, by aircraft, and by date range. When you need to pull records for a specific aircraft over a specific period — for an audit, an insurance claim, or a client requirement — the filter takes seconds.

Battery Pool

The Battery Pool tab tracks each battery in your fleet: serial number, model, type, assigned RPIC, current custody, status, cycle count, health percentage, and date last seen. Battery health degrades over cycles, and tracking this per-unit lets you catch batteries that are approaching end-of-service before they become a problem in the field.

The Record That Wasn’t There

Compliance records have a way of mattering at exactly the worst time — when something goes wrong, when a client’s procurement team runs a vendor audit, when a government contract requires documentation. The operators who fare best in those situations are the ones who’ve been keeping records all along, not the ones who have to reconstruct history from memory.

The Compliance Manager in FlightDeck doesn’t turn record-keeping into a project. It makes it part of the normal workflow so that when the records are needed, they’re already there.

Try FlightDeck free for 30 days.

Posted on

How COA Applications Actually Work — and How FlightDeck Helps You Prepare One

A Certificate of Authorization isn’t just a form. It’s a structured operational document that asks you to explain who will be flying, what aircraft they’ll use, how they’ll contain the operation, what happens if something goes wrong, and why the airspace risk is acceptable. The FAA reads these narratives — and how they’re written matters.

Understanding when a COA is required and what goes into one is foundational knowledge for commercial UAS operators working in controlled airspace.

When a COA Is Required

LAANC covers a large portion of controlled airspace authorizations for commercial UAS operations. But LAANC isn’t universal. Sites in zero-grid Class B or Class C airspace — where the LAANC ceiling is 0 feet — require a manual COA through FAA DroneZone. Sites where your required operating altitude exceeds the LAANC-available ceiling also require either a COA or a waiver for the portion that exceeds the limit.

FlightDeck’s Airspace Checker identifies which sites fall into each category automatically. Sites flagged as COA-required are marked in deep red in the results grid. Sites where LAANC is available are marked in deep green. That determination runs against locally stored FAA data — no internet connection required.

The FAA DroneZone Submission

COA applications are submitted through FAA DroneZone at faadronezone-access.faa.gov. The application is organized into numbered sections, and two of them — Section 7a (Operational Description) and Section 7b (Concept of Operations) — require narrative text that describes your specific operation.

The language in these sections needs to accurately describe your aircraft, your operating area, your lateral and vertical separation from the structure, and your contingency procedures. Generic boilerplate that doesn’t reflect your actual operation creates problems when the FAA reviews the application.

How FlightDeck’s COA Prep Tool Works

The Compliance Manager in FlightDeck includes a dedicated COA Prep tab with template narratives for the most common inspection operation types: communications tower, monopole, rooftop, billboard, and nationwide COA.

Each template uses token substitution — placeholders like the lateral separation distance and the altitude above the structure that get replaced with your actual values before the text is finalized. This means the narrative accurately reflects your specific operation rather than a generic description.

Section 7a is the operational description — what you’re doing, where, and with what aircraft. Section 7b is the concept of operations — how the flight is conducted, how you maintain VLOS, how you handle lost link, and how you respond to other aircraft. Both sections are pre-written with FAA-appropriate language and structured to address the specific questions the application asks.

A separate Site Authorization Prep tab covers the decision framework for individual site authorizations — walking through the airspace classification, what authorization pathway applies, and what the submission steps look like.

Tracking Your COA Status

Once a COA application is submitted, FlightDeck tracks its status in the COA Status column of your working data file. Status options range from application in progress through approved, with the COA Prep column recording the DroneZone application link for direct access from your spreadsheet.

Renewals need to be tracked as well. The general guidance is to apply for renewal at least 45 days before the current authorization expires — the FAA processing timeline can vary, and a lapse in authorization means work stops until the new one is issued.

What the COA Process Actually Takes

A well-prepared COA application with accurate narratives, a complete aircraft description, and a properly scoped operating area typically processes faster than a vague one that requires FAA clarification. The COA Prep tool in FlightDeck isn’t a shortcut — it’s a framework that helps you write an accurate, complete application the first time.

For operators doing regular work in controlled airspace, having template narratives ready to adapt to new sites is a significant time saver. The alternative is writing from scratch each time, which means either spending hours on a document you’ve written variations of before, or submitting something that isn’t quite right.

FlightDeck’s Compliance Manager and COA Prep tools are included in every license tier. Start your free 30-day trial.

Posted on

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

Commercial drone pilot reviewing a printed UAS operations manual binder with standard operating procedures and emergency protocols

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

UAS Incident Reporting: What to Do When Something Goes Wrong

Commercial drone pilot documenting a UAS incident with notes and photos at the scene of an unexpected drone landing

No commercial UAS pilot plans for an incident. But the ones who’ve thought through exactly what to do before one happens are the ones who handle them professionally when they occur — protecting themselves legally, maintaining client confidence, and contributing to the industry’s safety record.

Here’s what you need to know about UAS incident reporting as a commercial Part 107 operator.

What Triggers a Reporting Requirement

Under 49 CFR §830, the NTSB requires notification when a UAS operation results in:

  • Serious injury to any person (hospitalization required)
  • Loss of consciousness of any person
  • Property damage exceeding $500 (to property other than the aircraft itself)

Additionally, the FAA can request information and records from certificate holders at any time. Under Part 107, you’re required to make your aircraft available for inspection and to cooperate with FAA investigations.

Many incidents that don’t trigger mandatory NTSB reporting are still worth documenting formally — airspace deviations, close calls with manned aircraft, equipment malfunctions, or any operation that didn’t go as planned.

Immediate Response: The First 60 Minutes

Secure the scene. If the aircraft is down in a manner that poses ongoing risk — near people, traffic, or energized lines — manage that hazard first before doing anything else.

Document everything before it changes. Photograph the aircraft position, any damaged property, the launch and landing zone, and your equipment setup. Video the scene. Note the time, GPS coordinates, weather conditions, and who was present. Do this before anything is moved or removed.

Preserve flight data. Don’t clear logs. Don’t reset the aircraft. The flight controller log, video footage, and any telemetry data may be relevant to the investigation. Preserve it.

Notify your insurer. Most commercial UAS policies require prompt notification of potential claims. Don’t wait to see if a claim materializes — notify early.

Do not make admissions. Speak factually about what happened. Don’t speculate about cause or accept liability before facts are established. This applies in conversation with clients, bystanders, and especially with any responding authority.

NTSB Reporting Process

If the incident meets the reporting threshold, notify the NTSB as soon as practicable and no later than two days after the accident. Notification can be made through the NTSB’s online reporting form or by phone. A full written report may be required within 10 days.

Keep a copy of everything submitted. If the FAA opens a parallel investigation, your documentation and the timeline of your actions matter.

The Professional Response to Non-Reportable Incidents

For incidents that don’t trigger mandatory reporting — a hard landing, a minor equipment malfunction, an airspace confusion — the professional response is still documentation and analysis.

Write an internal incident report: what happened, what the chain of events was, what the contributing factors were, and what procedural or equipment changes you’re making in response. File it. Reference it in future planning.

Pilots who document and learn from their close calls have far fewer of them over time. The ones who don’t tend to repeat the same errors until one of them becomes a reportable event.

Maintaining the Record

Your operational history — the complete record of flights, conditions, authorizations, and incidents — is your professional evidence file. FlightDeck’s SQL-backed flight logging captures 87+ data points per mission in a local database that’s always there when you need it.

When an insurer, a client, or the FAA asks what happened and when, you pull a report. You don’t reconstruct from memory.

Download the free 30-day trial and start building the operational record that protects you when something doesn’t go according to plan.

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

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

FAA Part 107 drone pilot license card next to organized UAS flight logs and operational history documentation

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.