Author: Jeremy Yates

Posted on

Using 5-Day Forecasts to Schedule Multi-Day Drone Campaigns

Scheduling a multi-day UAS campaign around weather isn’t just a forecasting problem — it’s a resource allocation problem. You have a finite number of flying days, sites spread across a geographic area, some with time-sensitive authorizations, and weather that doesn’t care about your project deadline.

The operators who manage this well aren’t just checking whether tomorrow looks good. They’re looking at the next five days across the full project scope and sequencing work to stay ahead of conditions.

Weather at Every Site, Not Just the Next One

FlightDeck pulls a 5-day weather forecast for every remaining unflown site in your project during the 3-Phase Update. That’s not a regional summary — it’s site-specific data pulled by GPS coordinates for each location.

What gets recorded for each site: current temperature in Fahrenheit, wind speed and gust in mph, wind direction as a cardinal bearing, cloud cover percentage, visibility, probability of precipitation, and rain or snow accumulation values. The forecast also captures 3-hour interval data for the operational window around midday, giving you a picture of conditions during the hours you’re actually likely to be flying.

Weather data is cached with a 4-hour freshness window. If you run the update again within four hours, FlightDeck skips the weather fetch for sites that are still current — the data doesn’t get stale, and you’re not burning API calls on information you already have.

Reading the Forecast Across a Region

When you’re looking at 50 remaining sites across a 200-mile project corridor, the weather picture is often uneven. One end of the corridor might be clear for three days while the other end has persistent wind and afternoon storm risk. The FlightDeck forecast data lets you sequence work toward the favorable end while the unfavorable end improves — rather than trying to push through marginal conditions because the schedule doesn’t account for the weather gradient.

The Forecast Scheduler map displays your remaining sites as color-coded pins by airspace authorization status, with the weather and scheduling data available in each pin’s popup. Green pins are scheduled. The other colors — dark red for COA-required sites, orange for sites needing 72-hour LAANC coordination, light blue for instant LAANC, light green for Class G — tell you the authorization picture at each location so you can prioritize work that’s ready to fly and use weather windows efficiently.

When Weather Forces a Delay

Sometimes the forecast isn’t marginal — a system rolls through and a week of planned work has to slide. FlightDeck’s Weather Delay tool handles this in one step: specify the number of days to add, and every unflown site’s forecast date moves forward.

The tool automatically skips sites with active LAANC authorizations. LAANC windows are time-bound, and blindly pushing the forecast date on an authorized site doesn’t extend the authorization — it creates a conflict. The Weather Delay tool protects those records so you can address them individually, while everything else shifts in one operation.

The Scheduling Edge

Weather-aware campaign scheduling isn’t about having better forecasts than your competitors. It’s about having the workflow to act on what the forecasts tell you — to sequence work intelligently, push delays cleanly, and show clients that schedule disruptions are being managed rather than simply absorbed.

The operators who consistently deliver projects on time in regions with volatile weather aren’t operating on luck. They’re making better daily decisions with better information.

Try FlightDeck free for 30 days.

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

Managing a 200-Site UAS Project Without Losing Your Mind

A 200-site tower inspection project isn’t 200 flights. It’s 200 individual planning decisions — airspace classification, authorization status, weather windows, scheduling, folder structure, data collection, upload, QC, reporting, and invoicing — multiplied by 200 and run in parallel across a project timeline that usually has a fixed end date.

The operators who manage this well aren’t necessarily smarter or more experienced. They’re using better tools for the parts that don’t require their expertise.

Starting a Large Project: Batch Import

Most large commercial UAS projects start with a client-provided spreadsheet — a list of tower locations, site IDs, and whatever project-specific fields the client includes. The column names vary by client, by carrier, by year, and by whoever built the original template.

FlightDeck normalizes this automatically. When you place your data file as UpdatedFlightData.xlsx in the data folder and run the processor, FlightDeck maps more than 50 common column name variations to its standard set. “Node” becomes Site ID. “Lat” becomes Latitude. “CDD” becomes Due Date. “Scan_Type” becomes MOP Type. Dozens of variations that would otherwise require manual column renaming are handled before the data ever enters your working file.

New entries are geocoded using their address or coordinates. Sites already in the system are updated without overwriting completed records. The merge is non-destructive.

The Progress Scoreboard

The FlightDeck dashboard shows three numbers at all times: R for remaining flights, F for flights flown and logged, and T for total historical flight records. These update automatically as flight status changes.

Each site in the project moves through six status stages: Not Scheduled (0%), Scheduled (10%), Flown (40%), Forms Needed (50%), Submitted (90%), and Complete (100%). These stages drive the progress calculation and tell you and any supervisor reviewing the project exactly where every site stands — not whether the data file was updated, but what stage of completion each site has reached.

For a 200-site project, being able to answer “how many sites are at Forms Needed stage?” or “how many are complete and invoiced?” without manually counting rows is the kind of visibility that makes a project manageable.

Folder Structure Automation

Before flying, you need a directory structure ready to receive data — a sub-folder for each site, organized consistently so photos, KML files, and reports all land in the right place. On a 200-site project, creating those folders manually is an hour of tedious work that doesn’t require your judgment.

FlightDeck’s Create Folders tool reads your site list and generates the full directory structure automatically. Every site in your project gets a folder, named exactly to match the Site ID, with all required sub-directories created. Run it once at project start, and your folder structure is ready for the entire project.

Daily Reports

The 3-Phase Update generates daily reports automatically as part of its output. Supervisors and project managers who need to know current status don’t need to interrupt your field operations to ask — the report reflects the state of the project as of the last update run, and it’s available without any manual data extraction.

The Compounding Advantage

The productivity argument for this kind of automation isn’t just time saved on individual tasks. It’s the compounding effect of not having to context-switch between flying and administrative work. Every minute spent updating a spreadsheet manually, creating folders, or chasing down a site’s authorization status is a minute not spent on the work that actually requires your expertise.

On a 200-site project, the administrative overhead is substantial. FlightDeck doesn’t eliminate all of it — there’s still judgment required at every stage. But it handles the parts that don’t require your judgment, which is most of the data management.

That’s the difference between a project that feels manageable and one that doesn’t.

Try FlightDeck free for 30 days on your next project.

Posted on

KML Files for Drone Inspections: Why Google Earth Still Matters to Your Clients

A KML file is more than a deliverable artifact. It’s a spatially organized quality record — every photo placed at the GPS coordinates where it was captured, with the camera’s orientation shown, with the coverage overlap calculated for each frame. When it’s done right, a client or project manager can open it in Google Earth and immediately see exactly what was captured, where the gaps are, and whether the data quality is acceptable.

FlightDeck builds this automatically for every flight sub-folder in your project, using the EXIF and XMP metadata embedded in your photos by the drone.

What Goes Into Each KML

Phase 2 of the QC Uploader workflow is KML generation. For each photo in the dataset, the KML generator reads GPS coordinates, absolute altitude, and gimbal orientation data — pitch, roll, and yaw — and places a camera icon at the exact position where the photo was taken, pointing in the direction the camera was aimed.

Each camera icon has a view frustum that visualizes the gimbal direction. You can see at a glance whether the cameras were consistently pointed at the structure or drifting, and whether the angular coverage around a tower is complete.

The icons are color-coded by overlap percentage:

Green indicates 80% or higher sequential overlap — sufficient for photogrammetry deliverables and structural documentation. Yellow indicates 60–79% overlap — marginal, worth reviewing before delivery. Red indicates below 60% overlap — a gap in coverage that should be flagged for a potential re-fly.

The Extended Data Balloon

Clicking any camera icon in Google Earth opens a data balloon with the complete record for that photo: site ID, camera make and model, aperture, ISO, shutter speed, focal length, GPS coordinates, absolute altitude, AGL altitude, gimbal angles, aircraft orientation, overlap percentage, and QC pass/fail status for aperture and ISO.

This extended data is what your QC report, your client review, and any formal documentation can reference. Every measurement is directly from the drone’s embedded metadata — not derived or estimated.

Altitude Display Correction

KML files use absolute altitude mode, which means camera icons are placed at their GPS-recorded altitude relative to the WGS84 ellipsoid. Google Earth renders its terrain surface using SRTM data, which uses a different altitude reference. Without correction, camera icons may appear several meters above or below the actual terrain surface in Google Earth.

FlightDeck corrects for this with an Altitude Display Offset — an additive value in meters applied to every photo’s altitude when writing the KML coordinates. Set correctly, this makes camera icons appear at the right elevation relative to Google Earth’s terrain. The offset applies to both camera icon positions and any laser rangefinder target altitudes in the dataset, so the entire KML is consistent.

The Geoid Calculator tool in FlightDeck derives the correct offset for your specific survey area from Aeropoints GCP data — more on that in a separate post.

Single-Dataset Mode

On a large project, you may need to re-generate the KML for just one sub-folder — maybe a site was re-flown and you have new photos, or you’re adjusting the altitude offset for a specific location. The Dataset Selection filter in the QC Uploader limits KML generation to the selected sub-folder without touching the rest of the project. Clear the selection to process all folders again.

Why This Matters Beyond the Deliverable

The KML isn’t just for the client. It’s for your own QA before delivery. Opening the color-coded KML after a flight and before upload lets you verify coverage, spot the red icons that indicate gaps, and make the decision to re-fly before the job is closed out.

Catching a coverage gap from the Google Earth view is a quick conversation with a project manager and a targeted re-fly. Catching it after the client has reviewed the delivery is a different conversation entirely.

The KML generation in FlightDeck builds this review layer automatically, without requiring external GIS software or manual file preparation. It’s one of the outputs that tends to get noticed — clients who receive well-structured KML files alongside their photo deliverables understand that the data was reviewed and organized before it reached them.

FlightDeck’s KML generation is included in every license tier. Try it free for 30 days.

Posted on

Scaling Your UAS Business: From Solo Operator to Multi-Pilot Team

Two commercial drone pilots reviewing a job site map together before a multi-aircraft UAS inspection mission

The demand for commercial UAS services has outpaced the supply of organized, reliable operators in most specialized markets. Telecommunications inspection, power line survey, agricultural data collection — these markets are awarding larger contracts to operators who can demonstrate they can handle volume, consistency, and multi-site coordination at scale.

The problem is that most solo operators who try to scale hit the same wall: their operational systems — or lack thereof — don’t extend to a team. What worked for one pilot in a spreadsheet doesn’t work for four pilots across three states.

Here’s the operational infrastructure you need to build before you scale, not after.

Standardized Procedures Come First

The most common failure mode in scaling a UAS operation is adding people before adding systems. The result: every pilot does things slightly differently, data quality varies by operator, clients notice the inconsistency, and the reputation of the operation suffers from work that isn’t uniformly professional.

Before you bring on a second pilot, every core operational procedure needs to be documented, tested, and standardized. Pre-flight inspection. Site survey. Launch and recovery. Data capture. Upload and delivery. Post-flight documentation. Every step that happens on a job needs a defined standard that any qualified pilot can execute consistently.

This is your operations manual. It’s the foundation on which you build a scalable team.

Fleet Management and Equipment Tracking

A solo operation with one aircraft is relatively simple to track. A three-pilot operation with multiple aircraft, a library of batteries, and payload options by job type requires systematic fleet management.

Every aircraft needs documented maintenance history, current registration, and flight hour tracking. Every battery needs cycle count monitoring. When equipment goes out with a field team, you need to know which aircraft and which batteries went where, and what condition they came back in.

FlightDeck’s Drone Maintenance Log tracks maintenance events, battery cycles, motor hours, and repair history by serial number. Two editions are available — solo operator and fleet management — covering both stages of your operation’s growth.

Coordinating Multi-Pilot Schedules and Site Assignments

With multiple pilots, site assignment and scheduling become a coordination challenge. Who’s flying which sites on which days? Are authorization windows aligned with the pilot who’s actually going to that site? When sites get rescheduled due to weather, which pilot’s schedule is affected?

FlightDeck’s Forecast Scheduler reviews pending sites across the entire project and suggests an efficient fly schedule based on weather windows, site proximity, and project priority. Instead of manually balancing a multi-pilot calendar, you get a data-driven suggestion that accounts for conditions and location clustering.

The shared Google Maps pin layer — generated automatically by the 3-Phase Update — gives every pilot on the team a current view of project status without anyone needing to call in for a status update.

Data Consistency Across Multiple Pilots

One of the hardest quality control challenges when scaling is ensuring that data delivered by Pilot A meets the same standard as data delivered by Pilot B. Different camera settings, different flight patterns, different upload habits — all of these create inconsistency that clients notice.

FlightDeck’s QC Uploader applies the same automated EXIF quality checks regardless of which pilot captured the data. Images below F/4 aperture or above ISO 400 are flagged before upload proceeds, for every pilot on every job. The quality standard is enforced by the tool, not by trusting individual compliance.

Client Reporting at Scale

Enterprise clients on large projects want progress updates without having to ask for them. FlightDeck’s TX Daily Report generates formatted daily operations reports from the project database — publishable on a schedule, even hourly, without interrupting flight operations. Supervisors and clients see current status automatically.

The Confirm Progress dashboard gives team leads a color-coded delivery status view across every flown site: what’s been uploaded, what forms have been submitted, what’s fully complete and what’s pending. Managing a team’s delivery pipeline from one screen, without chasing individual pilots for status.

The Financial Case for Building Systems Before Scaling

Building operational infrastructure before scaling feels like overhead. It is — but it’s the overhead that determines whether scaling creates profit or just creates more problems at larger scale.

Operators with documented procedures, systematic fleet management, and consistent data delivery command premium rates from enterprise clients and win repeat contracts. Operators who scale on informal systems tend to win more work than they can execute reliably, damage client relationships, and find that growth made profitability harder, not easier.

Build the infrastructure first. Then grow into it.

Download FlightDeck free for 30 days and build the operational foundation your business needs — whether you’re flying solo today or building toward a fleet. The $250 lifetime license is the last operations software investment you’ll make.

Posted on

Thunderstorm Season and Commercial Drone Ops: What the Forecast Apps Don’t Tell You

Thunderstorm season doesn’t just cancel individual flights. It scrambles project schedules across entire regions, sometimes for days at a time. A line of afternoon storms in the Gulf Coast or the Southeast can make an entire week’s worth of planned sites unflyable by early afternoon, and if you’re managing a multi-site project, the cascading schedule impact is its own problem to solve.

The apps that give you a good morning forecast — the ones that tell you whether today’s mission looks feasible — aren’t built to help you think about what to push, by how much, and which sites to protect. That’s a different problem.

The Weather Data Problem at Scale

On a single-site mission, weather is a go/no-go question. You check the forecast, you check conditions on arrival, you make a call.

On a 150-site tower inspection project, weather is a scheduling problem. You have sites in three states, some with LAANC authorizations that have fixed windows, some with COAs that have expiration dates, some with client deadlines that don’t move. When a weather system rolls through and makes a week of work unflyable, the question isn’t just “when can we fly?” — it’s “which sites do I push, by how much, and which ones do I have to protect?”

FlightDeck pulls a 5-day weather forecast for every remaining unflown site in your project from OpenWeatherMap — temperature, wind speed, gusts, wind direction, cloud cover, visibility, precipitation probability, and rain/snow accumulation. That’s not a single point check; it’s a weather picture across your entire project scope so you can see where the system is hitting hardest and plan around it.

The forecast data is cached with a 4-hour freshness window — if you run the update multiple times in a single day, FlightDeck won’t re-fetch data that’s still current, which keeps things fast and doesn’t burn through API calls unnecessarily.

The Weather Delay Tool

When a weather system forces a multi-day delay across your project, FlightDeck’s Weather Delay tool handles the rescheduling in one step. You specify the number of days to add, and FlightDeck pushes every unflown site’s forecast date forward by that amount.

The important detail: sites with LAANC authorizations on file are automatically skipped. LAANC authorization windows are time-specific — pushing a site’s forecast date forward doesn’t extend the authorization, it just creates a conflict between your schedule and your existing approval. The Weather Delay tool recognizes this and leaves LAANC-scheduled sites untouched so you can handle those manually.

Everything else — sites waiting to be scheduled, sites scheduled without LAANC — gets pushed in one operation. A week-long weather delay that would otherwise mean manually updating 80 rows takes about ten seconds.

Why “Mostly Favorable” Isn’t a Go

One of the harder lessons in commercial UAS operations is learning to be skeptical of forecasts that look mostly good. Thunderstorm season in particular produces convective activity that forms fast and moves unpredictably — a clear morning can deteriorate to dangerous conditions by early afternoon, and those conditions often develop faster than a weather app refreshes.

The practical protocol for thunderstorm season is to front-load your flying. Start earlier, plan to be wheels-down by early afternoon, and treat any forecast that shows afternoon thunderstorm probability above around 30% as a real risk to your timeline rather than a number to rationalize around.

FlightDeck’s weather forecast data gives you the picture for tomorrow’s sites before you finalize today’s plan. That’s the decision point that matters — not the morning of, when you’re already in the truck.

Managing weather delays well is one of the things that separates operators who keep projects on track from those who find themselves constantly rescheduling and explaining slippage to clients. The tools that help you do that quickly and accurately are worth having ready before the first line of storms arrives.

Posted on

UAS Safety Culture: Building a Safety-First Operation as a Solo or Small Team

Safety culture is a term most commercial UAS pilots associate with large organizations — airlines, military units, corporate flight departments with dedicated safety officers and formal SMS programs. It sounds like something that doesn’t apply to the solo Part 107 operator flying inspection contracts in three states.

That’s a misconception that has ended more than a few commercial UAS careers.

Safety culture isn’t a program. It’s a set of habits, standards, and values that shape every operational decision you make — from how you conduct a pre-flight inspection to whether you fly in marginal conditions because the schedule says you should. And it matters for solo operators and small teams as much as it does for anyone else.

What Safety Culture Actually Means

A genuine safety culture has three characteristics:

Reported. When something goes wrong — or almost goes wrong — it gets documented and discussed, not buried. In an organization, this means a non-punitive reporting system. As a solo operator, it means writing up your own close calls honestly and using them to improve your procedures.

Learned. Information from incidents — yours and others’ — feeds back into how you operate. The UAS industry generates incident data through ASRS reports, FAA enforcement records, and pilot communities. Operators who read and learn from that data don’t repeat the same mistakes.

Consistent. Standards are applied every time, not just when conditions make it easy. A pre-flight checklist completed on every flight — including the short, familiar one you’ve done 50 times before — is a safety culture behavior. Skipping it because “you know this site” is not.

The Hidden Cost of Low Safety Standards

Beyond the obvious risk of incidents, low safety standards carry a business cost that isn’t always visible until it matters. Enterprise clients — utilities, carriers, construction companies, insurance firms — increasingly evaluate UAS vendors on safety credentials before awarding contracts. They ask for operations manuals, safety records, incident history, and evidence of structured operational procedures.

A pilot who can demonstrate consistent, documented safe operations commands better rates and more stable enterprise contracts than one who can’t. Safety culture is a competitive advantage, not just a moral obligation.

Practical Safety Culture Habits for Solo Operators

Pre-flight, every time. No exceptions. No abbreviated versions for familiar sites. The checklist exists because familiar sites are where complacency lives.

Personal weather minimums, written down. Limits you’ve committed to in advance are the ones you’ll actually hold to when conditions are marginal and pressure to fly is high.

An honest post-flight debrief. Even a two-minute mental review — what went as planned, what didn’t, what would you change — builds the pattern recognition that makes you a safer operator over time. Write it down when something is worth noting.

Equipment that’s ready to fly before it needs to fly. Battery health checked regularly. Props inspected after every flight. Firmware current. Maintenance intervals tracked. You find equipment issues during maintenance, not during a mission.

Currency. If you haven’t flown in a while, practice before taking a client job. Motor skills and pattern recognition erode. Solo proficiency flights aren’t wasted time — they’re maintenance on your most important piece of equipment, which is you.

How FlightDeck Supports a Safety Culture

Safety culture requires documentation — the evidence that standards are being applied consistently. FlightDeck’s structured logging captures pre-flight completion, conditions, authorization status, anomalies, and post-flight notes in a local database attached to every mission record.

The Drone Maintenance Log tracks maintenance events, battery cycles, and repair history by aircraft serial number — exportable for insurance documentation and compliance records. The Airspace Checker ensures every site gets a proper authorization review before you fly, not after. The compliance documentation tools build the operational paper trail that enterprise clients and insurers require.

Safety culture produces the data. FlightDeck captures it.

Download the free 30-day trial and start building the operational record that proves your safety standards to clients, insurers, and the FAA — one documented flight at a time.

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

Photo QC and Data Delivery: Why Your Upload Process Is Costing You Clients

Flying the mission is half the job. Delivering data that meets client quality standards — every file, every time, with verified completeness — is the other half. And for many commercial UAS operators, the delivery half is where professionalism breaks down.

Blurry images passed to a client. Files missing geotag data. Incomplete uploads discovered only when the client opens the delivery. Upload interruptions on rural connections that result in partial datasets. These problems lose contracts. Here’s how to build a delivery workflow that catches problems before they reach the client.

Why Photo QC Matters More Than Pilots Think

For inspection, mapping, and data collection clients, your photos aren’t just documentation — they’re the deliverable. An image that fails to meet technical specifications doesn’t just look bad; it may be genuinely unusable for the client’s processing pipeline.

Tower inspection clients need images with sufficient depth of field to identify equipment defects. Photogrammetry clients need consistent exposure and overlap for point cloud generation. Agricultural clients need calibrated imagery for accurate NDVI analysis.

Every image that fails quality standards is a rework. Every rework is a return trip or a disputed invoice. Building QC into your workflow before upload — not after the client reviews the delivery — is the difference between a professional operation and an amateur one.

The Core Photo Quality Parameters

For most commercial UAS photography, the critical technical parameters are:

Aperture. Narrower than F/4 risks diffraction softening at common UAS camera sensor sizes. F/4 or wider is the standard for most platforms and is the threshold where image sharpness becomes reliably consistent across varied lighting.

ISO. Above ISO 400, digital noise becomes visible and may interfere with feature detection in photogrammetry and inspection analysis. ISO 100–400 is the clean window for most commercial work.

Shutter speed. Motion blur from a moving drone at the wrong shutter speed is one of the most common QC failures. Your minimum shutter speed should be fast enough to freeze drones motion at typical survey speeds.

EXIF/XMP metadata completeness. GPS coordinates, altitude, gimbal angle, and timestamp embedded in image metadata are critical for photogrammetric processing, KML generation, and data management. Files with incomplete or corrupt metadata may be rejected by client processing pipelines.

How FlightDeck’s QC Uploader Works

FlightDeck’s QC Uploader automates the quality check before any file is allowed into the upload queue. Every image in your upload folder is analyzed automatically against defined quality parameters. Images that fall outside thresholds — below F/4, above ISO 400, or with metadata issues — are flagged before upload begins. You review the flags, address the issues, and only qualified files proceed.

For survey and mapping operations using Propeller Aeropoints, the QC Uploader adds another layer: KML altitude correction using geoid undulation calculations from your ground control point data. The result is KML files where pins render at correct orthometric elevation in Google Earth — not at raw GPS altitude, which in most of North America sits above the actual ground surface.

AWS S3 Integration and Multi-Threaded Upload

For clients who receive data directly to cloud storage — increasingly common in enterprise inspection and data collection — FlightDeck connects directly to your AWS S3 bucket. Configure your credentials once and all qualified uploads go to S3 with multi-threaded processing running up to ten parallel threads.

This matters specifically for field operations on rural LTE or intermittent signal: the multi-threaded engine is built to handle interrupted connections. A SQLite manifest database tracks every file’s upload status — pending, uploading, uploaded, failed. When a connection drops, the upload resumes exactly where it left off. No duplicate uploads. No missed files. No manual retry.

Delivery Verification

After upload completes, FlightDeck runs file-size verification and completion checks to confirm every file arrived intact. A delivery that passes these checks is a delivery you can represent to your client as complete and verified — not just “I think it all went through.”

Your FlightDeck Confirm Progress dashboard shows every delivered site with color-coded status: uploaded, forms submitted, fully complete. At the end of every field day you know exactly where your project stands.

Download the free 30-day trial and build the QC and delivery workflow that keeps clients coming back because your data is always right the first time.

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.