Part 108 BVLOS Organizational Compliance SaaS for Commercial Drone Programs
The FAA has granted 284 BVLOS waivers against 424,516 registered commercial drones, fewer than 1 in 100 programs. The proposed Part 108 rule, which the FAA hopes to finalize before the end of 2026, would shift legal accountability from the pilot to the organization, creating an estimated $360 million a year in compliance paperwork. Every drone program in the country is about to need an airline's filing cabinet. Nobody sells it.
The Problem
Here is the strangest ratio in American aviation. According to the FAA Aerospace Forecast 2026-2046 compendium, 424,516 nonrecreational drones were active in the United States in 2025. Pilot Institute's tally of FAA waiver data counts 284 granted beyond-visual-line-of-sight (BVLOS) waivers under 14 CFR 107.31 as of September 2026. A Part 107 waiver is an organizational authorization, not a per-aircraft permit, so dividing one by the other mixes units. But even computed honestly at the program level, the picture is stark: against roughly 53,000 estimated commercial programs, 284 waivers cover about 0.54% of them. Fewer than 1 in 100 programs can legally fly beyond the pilot's line of sight. Long-range infrastructure inspection, drone-as-first-responder, agricultural survey, package delivery, the use cases that justify most enterprise drone investment, remain effectively out of reach for 99.5% of the market.
No queue can fix this because the queue barely moves. According to the Department of Transportation's Office of Inspector General, the FAA issued 6 BVLOS waivers in 2020 and 122 in 2023 (annual figures), reaching 190 cumulative by October 2024 (OIG report AV2025034). Pilot Institute's current tally of 284 implies roughly 94 more over the 23 months since, a recent run rate near 50 per year, roughly in line with the long-run average of about 40 per year since 2020. Meanwhile, in the FAA's own CY 2024 small UAS survey, 106 emergency response organizations alone said they intend to apply for a BVLOS waiver in 2025 (FAA CY 2024 sUAS Survey Report). One vertical's single year of stated intent consumes two full years of agency throughput at the current rate. Authorizing just 10% of the estimated 53,000 programs, about 5,300 authorizations, would take more than a century at 50 per year. This is not a backlog problem. It is a capacity problem measured in orders of magnitude.
Part 108 is the FAA's proposed answer, and as drafted it changes who is legally responsible for everything. Under Part 107, the remote pilot in command holds ultimate authority for each flight. The Part 108 notice of proposed rulemaking would move primary responsibility to the operating organization itself. As proposed, the organization must demonstrate that its personnel are qualified, its aircraft are airworthy, its operations follow approved procedures, its flight data is collected and maintained, and its personnel qualification and training records are kept current (UAS Weekly, August 2026).
Two new organizational roles come with the proposal: an operations supervisor with final authority over safety and compliance (the operator would have to notify the FAA within 10 days of any change in who holds that role), and a flight coordinator who monitors flights remotely (Part 108 NPRM text, Subpart C). Lower-risk operations would receive permits through a streamlined pathway with limits on fleet size and mission scope, while higher-risk operations would require certificates demanding formal safety management systems and FAA-approved training programs (DSLRPros Part 108 guide). All of this is proposed, not final. But the direction is unmistakable: the final rule has sat with the White House Office of Information and Regulatory Affairs since July 10, 2026 (UAV Coach, September 2026), the last major step before publication, and at the Commercial UAV Expo keynote on September 3, the FAA's acting Emerging Technologies division manager said the agency is "hoping" for a final rule before the end of the calendar year: "It feels like we're on the 10-yard line and we just got to get it in the end zone" (Commercial UAV News).
In practice, the proposal means five record categories every organization must maintain continuously and auditably: flight records, personnel qualification and training currency, maintenance and airworthiness logs, incident reports, and a version-controlled company operations manual. No system of record exists for this today. AirData has logged 65 million flights across 850,000 drones and 470,000 pilots and explicitly positions its platform around the rule's record categories, and Pacific Gas and Electric uses it to document BVLOS waiver operations across a 70,000-square-mile service area (UAS Weekly). Yet flight telemetry is not personnel records, and a flight log is not an operations manual. Making matters starker, the last generation of enterprise drone program management software is gone: Verizon shut down Skyward on June 30, 2022 (The Robot Report), and AirMap was acquired by a drone services startup (Light Reading). When compliance stops being optional, the organizational compliance seat will be empty.
Market Size
Base SAM calculation (2025 fleet figures): Start with 424,516 active nonrecreational aircraft in 2025 (FAA 2026-2046 compendium). At 8 aircraft per formal drone program, a reasonable figure for utility, public safety, and service-provider fleets, that implies roughly 53,000 programs. If 40% are formal enough to buy compliance software rather than track records in spreadsheets, about 21,200 organizations are addressable. Price them on a blended $6,600 per year of pure SaaS: roughly 73% of organizations on the $249/month tier, 22% on $899/month, and 5% enterprise at $3,500/month, which averages about $555/month, the $550 figure used throughout. 21,200 × $6,600 = $140 million in core SaaS SAM, growing toward roughly $170 million by 2029 as the fleet expands toward 515,000 aircraft at the FAA's 5.0% CAGR through 2030. (Note the 2025-to-2026 jump to 457,437 aircraft is 7.8%, faster than the 5-year CAGR; the SAM uses the 2025 base.)
Beyond the SaaS, insurers are the second revenue layer. Global Aerospace published detailed Part 108 guidance for operators in October 2025. Underwriters will need exactly the records this platform generates: personnel qualification, maintenance history, incident rates, safety management maturity. Licensing structured organizational safety data to 10 to 15 aviation insurers at $250,000 to $1 million per year in API access fees adds $2.5 to $15 million in high-margin data revenue. This layer carries a disclosed conflict worth stating plainly: the platform would sell operators' safety data to the insurers who price those same operators' coverage, which means operator consent and genuine anonymization have to be designed in from day one, not bolted on later. A utility with a single BVLOS incident in a region is trivially re-identifiable, so the data product needs opt-in architecture and aggregation minimums before any insurer sees it.
Permit application services form the third layer. In the first 24 months after a final rule, thousands of organizations will need Part 108 permits, each requiring an operations manual, training program documentation, and a safety case. A guided permit-application product at a $4,500 average fee, with 3,000 to 5,000 permits per year in the initial wave, brings $13.5 to $22.5 million in annual services revenue. Just as valuable, every permit engagement is a paid sales call for the SaaS that follows.
Total SAM across SaaS, insurance data licensing, and permit services: $155 to $180 million on current figures, approaching $200 million by 2029. (The permit-application layer is front-loaded to the first 24 months after a final rule and decays thereafter; the 2029 figure assumes the insurance data layer scales to offset it.) For the global TAM, assume compliance and program-management software spend runs about 1.2% of the commercial drone market ($38.56 billion in 2026, 13.54% CAGR to 2034, per Straits Research). That 1.2% is an assumption, not a measured benchmark, and it is the weakest link in this sizing. On 2026 figures it implies roughly $460 million; compounded at the market's 13.54% CAGR it reaches about $770 million by 2030. (For context, the broader drone market including consumer and defense is far larger, $83.8 billion in 2025 per Grand View Research, but this startup's TAM is the compliance software slice, not the aircraft.)
The Product
An FAA-audit-ready organizational compliance system of record for commercial drone programs. Not flight telemetry (AirData owns that) and not airspace authorization (Aloft owns that), but the five record categories the proposed rule demands of the organization. Six modules:
- Personnel Qualification Ledger: Every operations supervisor, flight coordinator, maintainer, and ground handler gets a qualification profile covering role assignments, training completions, and recency tracking against the organization's FAA-accepted training program, with automated alerts before currency lapses. As proposed, the operator must notify the FAA within 10 days of an operations supervisor change; the platform handles that filing automatically. No competitor offers this module.
- Operations Manual Builder: A structured authoring tool that generates the company operations manual the proposal requires, with version control, approval workflows, and change history. When an inspector asks what procedure the flight coordinator followed on a given date, the answer is a timestamped manual revision, not a PDF in someone's email.
- Airworthiness and Maintenance: Per-aircraft maintenance logs, inspection scheduling, alteration records, and battery lifecycle tracking, mapped to manufacturer maintenance instructions. Integrates with AirData telemetry for flight-hour-driven maintenance triggers.
- Flight Data Collection System: The proposal requires the organization to maintain a flight data collection system. This module ingests telemetry from AirData, DJI FlightHub, Aloft, and direct integrations, storing it in an inspectable format tied to personnel, aircraft, and mission records. Telemetry becomes evidence, not just data.
- Incident and Occurrence Reporting: Structured incident capture, root-cause workflow, corrective action tracking, and the reporting formats the FAA and insurers expect. Incident contents never leave the operator: the insurer dataset is built from aggregated process metrics only, by design.
- Permit and Certificate Application Workflow: Guided preparation of Part 108 permit applications (operations manual, training program, safety case, aircraft conformity documentation), with e-filing when the FAA opens the pathway. The wedge: every organization that wants BVLOS authority needs a permit on day one, and the application is the hardest document most programs will ever produce. Note the honest caveat: the FAA has announced no waiver-to-permit conversion mechanism, so early preparation is a bet on the rule's final shape.
Unit Economics
| Metric | Value |
|---|---|
| Blended ARPU (SaaS) | $550/month ($6,600/year) |
| Permit application service fee | $4,500 avg |
| Customer acquisition cost (organization) | $2,400 (estimated) |
| Average retention | 30 months |
| Expected LTV (30 mo × $550) | $16,500 |
| LTV:CAC ratio | 6.9:1 (5.5:1 at 24 mo, 8.2:1 at 36 mo) |
| Gross margin (SaaS) | 90% |
| Gross margin (blended) | 86% (at 80% SaaS / 20% permit-services mix; SaaS 90%, permit services ~70%) |
| Insurance data API license (annual) | $250K–$1M |
| Startup cost (18-month runway) | $3.4M |
| Break-even | Month 16 (~390 organizations) |
Methodology note: Estimated CAC of $2,400 reflects named-account SMB SaaS sales assisted by an unusual advantage: the lead list is public. The FAA publishes every granted Part 107 waiver with the company name on its public waivers-issued page, so every organization that has ever sought advanced operating authority is identifiable by name and use case. That CAC figure is unvalidated against drone-specific benchmarks and belongs in the limitations ledger below.
Retention of 30 months reflects the stickiness of compliance systems of record: once personnel records, the operations manual, and maintenance history live in the platform, migrating means re-creating the audit trail. The $3.4 million startup cost covers 18 months of a 12-person team (7 engineers, 2 aviation regulatory specialists, 2 sales, 1 CEO) plus SOC 2 Type II certification, which is non-negotiable for selling to utilities and public safety agencies, and a presence at Commercial UAV Expo. Break-even math: 390 organizations × $550/month = $214,500 MRR against roughly $189,000 in monthly burn, crossing inside the permit wave if the product ships within 6 months of the final rule.
Competitive Landscape
| Company | What It Does | Part 108 Org-Compliance Records? | Status |
|---|---|---|---|
| AirData | Flight telemetry logging and fleet management: 65M flights, 850K drones, 470K pilots | No. Flight data yes; personnel qualification, ops manuals, permit workflow no. | Private, dominant in telemetry |
| Aloft (formerly Kittyhawk) | Airspace authorization (LAANC), UTM, fleet management | No. Airspace access is a different problem from organizational records. | Private |
| DroneDeploy | Mapping, surveying, and reality-capture mission software | No. Mission output, not compliance infrastructure. | Private, venture-backed |
| ANRA Technologies | UTM and traffic management for UAS | No. Traffic layer, not records layer. | Private |
| FlytBase | Autonomous drone dock operations software | No. Dock automation, not compliance. | Private |
| Skyward (Verizon) | Was the enterprise drone program management platform | Would have been the closest competitor | Shut down June 30, 2022 |
| AirMap | Was the airspace intelligence platform | Never built org compliance | Acquired by a drone services startup |
| This startup | Organizational compliance system of record: personnel, manuals, airworthiness, incidents, permits | Core product | Seeking $3.4M Seed |
Data collection is not the gap. AirData collects more flight data than any ten competitors combined. Missing is the organizational record: the personnel qualification ledger, the version-controlled operations manual, the permit application, the incident safety case. None of the telemetry or airspace players built those, because under Part 107 legal responsibility sat with the individual pilot and no buyer existed for organizational compliance records. As proposed, Part 108 creates that buyer by regulation.
Candor requires naming the honest competitive risk: AirData extending downward. It holds the customer relationships (including PG&E-scale BVLOS programs), a decade of operational data, and explicitly positions its platform around the rule's record categories. An organizational compliance layer is a feature AirData could ship to its installed base faster than a startup can build that base from zero. What defends the startup is buyer separation. AirData sells to pilots and fleet managers; this product sells to the operations supervisor and the general counsel. Flight telemetry answers "what did the aircraft do." Compliance records answer "was the person qualified, was the procedure approved, was the aircraft airworthy, and can you prove all three to an inspector." Different question, different system, different budget line.
Go-to-Market
Phase 1 (months 1–6): Ship the permit application workflow first, because every organization that wants BVLOS authority needs a Part 108 permit on day one and the application is the single hardest document a drone program produces. Build the lead list from the FAA's public waiver pages: every 107.31 waiver holder by name, with use case. Target the 106 emergency response organizations that told the FAA they intend to seek BVLOS authority in 2025, plus recent waiver holders whose authorizations will face renewal decisions as the Part 108 era approaches. Price the permit product at $4,500 flat and convert permit customers to the $550/month SaaS at a target 60% rate.
Phase 2 (months 7–14): Move upmarket to utilities and infrastructure. The PG&E pattern (70,000 square miles under a BVLOS waiver, documented through AirData) repeats across every major utility, railroad, and pipeline operator, and these buyers combine the largest fleets with the strictest audit requirements, making them the highest-ACV segment. In parallel, launch the insurer data product: aviation underwriters are building BVLOS risk models now, and the first platform holding structured organizational safety data across hundreds of programs owns the dataset every underwriter needs, provided the opt-in and aggregation safeguards from the Market Size section are real.
Phase 3 (months 15–24): Serve the certificate tier: larger fleets and complex missions requiring formal safety management systems and FAA-approved training programs, where the training curriculum builder and SMS documentation modules command enterprise pricing ($3,500/month and up). Expand into public-safety drone-as-first-responder programs, which pair high flight tempo with municipal procurement budgets. Begin international expansion as EASA convergence discussions mature; the September 2026 Commercial UAV Expo keynote put FAA-EASA regulatory convergence on the agenda explicitly.
Why Now
Five forces are converging to make this market viable in 2026 and not before.
First, the rule is on the 10-yard line. Part 108 has been under OIRA review since July 10, 2026, the last major step before publication, with the FAA publicly hoping for a final rule before the end of the calendar year. That date is the agency's aspiration, not a commitment: OIRA's stakeholder meetings on the rule were booked through mid-September, and the standard review window runs to October 8 (DroneXL, September 2026). Regulatory software markets are won in the months after a final rule, when every affected organization discovers simultaneously that it needs something it does not have. Companies that ship in that window become the default.
Second, the FCC's December 2025 action against foreign-made drones forces a fleet refresh at the same moment. The Commission added all foreign-made UAS and critical components to its Covered List, blocking new equipment authorizations for DJI, Autel, and other foreign manufacturers in the US (Security Affairs; The Hacker News). Existing owners can keep flying what they own, but no new foreign-made models enter the market, and the only carve-outs so far cover toy drones and approved domestic products (Android Authority, June 2026). Be clear-eyed about what this is: a protectionist cost shock the startup monetizes, not a neutral market event. Compliant airframes cost multiples of a DJI, which punishes small operators most. But every organization that refreshes its fleet must re-establish airworthiness records, rewrite maintenance programs for new airframes, and re-train personnel, so the compliance burden spikes precisely at the buying moment.
Third, the waiver math is broken beyond repair. 284 organizational waivers against an estimated 53,000 programs, with 106 emergency response organizations intending to apply in a single year against a recent run rate near 50 per year. The proposed permit pathway is designed for faster issuance than waivers, converting a bespoke multi-month legal process into a standardized filing, though commenters including the DSP Alliance warned the permit review could prove even more cumbersome than the current waiver program. Demand does not need to be created. It needs to be processed.
Fourth, the last generation died before the market arrived. Skyward shut down in June 2022, when the enterprise drone market was still waiver-constrained and compliance software was a nice-to-have. AirMap was acquired and consolidated away. Nobody currently owns the organizational compliance seat, and the company that claims it now inherits a market with no incumbent.
Fifth, underwriters are already moving. When an insurer like Global Aerospace publishes detailed Part 108 guidance for operators, it is telegraphing that it is about to price a new risk class and needs the market to generate the data it will underwrite against. The platform holding the organizational safety records becomes the data supplier to the underwriters, an insurer second act closer to aggregated benchmark subscriptions than to per-record vehicle histories, since the dataset contains no incident contents, with the consent architecture disclosed above as the price of admission.
Original Contribution: The $360M Paperwork Burden and the Waiver Scarcity Proxy
A calculation nobody has published: What is the dollar value of the compliance paperwork the proposed Part 108 creates, and how badly does the waiver system ration BVLOS access? Both can be estimated from public data.
Start with the burden. As proposed, Part 108 requires each organization to maintain five record categories continuously: flight data, personnel qualification and training, maintenance and airworthiness, incidents, and the operations manual with approved procedures. Estimate the manual labor conservatively: 4 hours per week per program on compliance documentation (compiling training records, updating the manual, assembling safety cases, responding to internal audit requests), 50 working weeks per year, at an $85/hour loaded rate for an aviation operations manager. That comes to $17,000 per organization per year. Applied to the roughly 21,200 formal programs in the SAM calculation: 21,200 × $17,000 = $360 million per year in manual compliance labor across the US commercial drone sector.
If software absorbs a quarter of that burden, a plausible capture rate for a system of record, the displaced labor value is roughly $90 million a year. Present that alongside the pricing-based SAM ($140 million) not as two independent estimates, they share the same 21,200-organization assumption, but as two lenses on one assumption that point the same direction. One caveat honesty demands: the $360 million is not pure waste. Some of those 4 hours are a human reading a training record and noticing something wrong, judgment the software must replicate, not just delete.
The ratio above is a snapshot; velocity is the other half of the scarcity story: the OIG's 190 cumulative waivers by October 2024 and 284 as of September 2026 imply a recent run rate near 50 per year. Authorizing just 10% of programs, about 5,300 authorizations, would take more than a century at that pace. One more caveat on the ratio: the waiver count is a cumulative stock accumulated over roughly a decade, while the fleet figure is a 2025 snapshot. The permit pathway in the proposal is not an incremental improvement. It is the only mathematically possible way to clear the queue.
Limitations
Several structural weaknesses deserve direct statement. The 21,200-organization estimate rests on two untested assumptions: 8 aircraft per formal program and 40% of programs formal enough to buy software. FAA data covers aircraft registrations, not organization counts, so the true number of commercial drone programs is unknown. With 20 aircraft per program, a plausible figure for utilities, the count falls toward 8,500 organizations; with only 20% buying software, it halves again. Treat the $140 million SAM as a midpoint of a wide interval, not a precise figure.
Compliance costs land regressively, and the business model should not hide that. A $550/month subscription plus a $4,500 permit fee is rounding error for PG&E and a real burden for a two-person aerial photography outfit. If the proposed rule converts paperwork into a mandatory software purchase, it risks pricing small operators out of legal BVLOS entirely or into noncompliance, while rewarding capital-rich incumbents who file first. The 106 emergency response organizations in the target customer list face the same math as an unfunded mandate. Whether that concentration is a feature or a bug of the rule is a policy question this article cannot settle, but the distributional effect is real and the product benefits from it.
Three inputs are modeled or analogized, not measured. The $17,000-per-year paperwork figure (4 hours/week at $85/hour) comes from no published study of drone program compliance labor. Permit pricing ($4,500) and insurance data licensing ($250K-$1M/year) are analogized from adjacent verticals, because no Part 108 permit has ever been issued. The 25% labor-capture rate behind the $90 million cross-check is a judgment call, not a measured figure. Estimated CAC of $2,400 is unvalidated against drone-specific benchmarks. And the 1.2% software attach rate behind the global TAM is an assumption, stated as one, and the weakest link in the sizing.
Records are not safety. A system optimized to produce FAA-inspectable artifacts can substitute documentation for safety culture: version-controlled manuals and auto-filed supervisor notifications are excellent audit evidence, and audit evidence can be gamed. Every industry with compliance software has learned this. The product's defense is to tie as many records as possible to verifiable telemetry rather than self-attestation, but the checkbox-compliance hazard is structural and no vendor marketing dissolves it.
Two tensions inside the insurer-data model need naming, because the consent architecture above does not survive contact with the incentives elsewhere in this article. First, the underwriter advice in "What You Can Do" asks insurers to prefer operators who produce structured safety data, which would make opt-in economically coerced: an insurer that prices non-sharers worse has converted consent into a coverage surcharge. The honest resolution is a pricing firewall, contractually barring insurers from using participation status in underwriting, and delivering the dataset only in aggregated form where no single operator's records are visible. For small regional operators, re-identification may be infeasible to defeat entirely, and that has to be disclosed to participating operators. Candor also requires naming the firewall's limits: a contract written by a seed-stage vendor against a million-dollar-a-year customer has a leverage problem, and insurers can justify worse pricing for non-participants as unverifiable-risk surcharges that no participation-status clause fully overrides. The firewall is a design intent, not a guarantee. Second, the Incident module feeds the insurer dataset on an opt-in basis, which gives operators a financial motive to under-report incidents to the platform that must keep them FAA-audit-ready. The structural fix is to exclude incident reports from the insurer data product entirely: underwriters get process metrics, personnel qualification rates, maintenance compliance, manual currency, never incident contents. That separation is what makes the platform's audit records trustworthy in the first place.
Finally, everything about the rule's final shape is provisional. The NPRM is a proposal; the Simplified User Interaction requirement, detect-and-avoid provisions, and right-of-way rules were heavily contested in comments, and OIRA review can reshape the rule substantially. The FCC ban analysis assumes a gradual fleet refresh, since existing owners can keep flying their aircraft and the ban blocks new authorizations rather than existing operations. If operators sweat current fleets under Part 107 for years instead of buying compliant airframes at multiples of DJI prices, Part 108 adoption stretches and the near-term SAM shrinks.
Strongest Counterargument
The most compelling case against this startup is that the rule, as proposed, may strand the very fleet it is supposed to govern. DJI's public comment on the NPRM makes the point precisely: the proposed Simplified User Interaction (SUI) requirement effectively mandates highly automated aircraft and excludes drones flown with manual pilot control, which describes the majority of existing commercial fleets, including drone-as-first-responder programs, infrastructure inspections, and security patrols (DJI Viewpoints). Even dock-based automated solutions that keep a pilot in the loop would be excluded as drafted. If SUI survives OIRA review in anything like its proposed form, the day-one addressable market is not 424,516 aircraft. It is the far smaller population of net-new autonomous platforms built to the new standard, and the scarcity proxy above becomes an argument against near-term software demand: the organizations needing compliance records most urgently are the ones whose aircraft may not qualify.
Separate from market sizing, the safety case itself deserves scrutiny the business sections never quite give it. This startup profits from the paperwork of scaled BVLOS flight, which means its revenue depends on routine uncrewed flight beyond the pilot's sight over American communities being acceptably safe. Detect-and-avoid reliability against non-cooperative aircraft, midair collision risk with crewed aviation, cybersecurity of connected fleets, and the privacy implications of persistent overflight are the actual questions the rule exists to answer, and they are not settled by a compliance platform existing. SUI reads in this light not just as a market constraint but as the FAA's attempt to make the safety case close. A reader should hold both thoughts: the business opportunity is real whether or not the underlying safety judgment is correct, and those are different claims.
The FCC ban compounds the adoption risk. With no new foreign-made aircraft entering the US market and compliant domestic alternatives costing multiples of a DJI airframe, the rational move for most operators is to sweat existing fleets under Part 107 for as long as possible. Fleet refresh cycles are measured in years, not quarters. A compliance platform needing thousands of organizations on permits in its first 24 months could find itself selling into a market that is still overwhelmingly flying visual line of sight.
Then there is AirData. Sixty-five million flights, 850,000 drones, 470,000 pilots, entrenched at PG&E-scale BVLOS programs, explicitly positioning around the rule's record categories. The organizational compliance layer is a feature AirData could ship to its installed base faster than a startup can build that base from zero. Buyer separation (operations supervisor versus fleet manager) is a real defense but not an impregnable one: both often sit in the same office, and a single-vendor pitch beats a two-vendor pitch on procurement friction alone.
These objections have force. Against them: SUI is the most contested provision in the NPRM precisely because it strands existing fleets, which is why the final rule is widely expected to soften it; the FCC ban delays the market while deepening it, since every airframe replacement regenerates the full documentation burden; and AirData's decade of telemetry is flight data, not organizational data, which makes it the most likely acquirer rather than the executioner. For a $3.4 million seed, an acquisition by the telemetry incumbent is a fine outcome.
The Bottom Line
Fewer than 1 in 100 commercial drone programs holds BVLOS authority, because a waiver system processing roughly 50 applications a year cannot serve demand measured in the thousands. Sitting with OIRA since July 10, 2026, with the FAA hoping for publication before year's end, the proposed Part 108 rule would replace the waiver queue with permits and certificates and move legal accountability from the individual pilot to the organization. That single shift creates an estimated $360 million a year in compliance paperwork, against a $140 million core SaaS SAM and a total near-term opportunity of $155 to $180 million. No system of record exists to carry it. Enterprise drone program management has been tried before: the last company to own the seat shut down in 2022. Flight data, the telemetry leader owns; personnel records, it doesn't. Underwriters are already publishing guidance for the risk class they are about to price. Somebody is going to sell every drone program in America its filing cabinet. It might as well be you.
What You Can Do
If you run a commercial drone program today, audit yourself against the five record categories now, before any final rule: flight data, personnel qualification and training currency, maintenance and airworthiness logs, incident reports, and a version-controlled operations manual. Pull your organization's waiver history from the FAA's public waivers-issued page and check the expiration dates. The FAA has announced no waiver-to-permit conversion mechanism, so early manual preparation is a positioning bet, not a guaranteed transition path, but the organizations with manuals ready will file first either way.
If you lead a public safety drone program, coordinate with neighboring agencies on a shared training curriculum, because the certificate tier rewards formal training programs and a regional curriculum splits the cost. If you underwrite aviation risk, start specifying the data format you will require for BVLOS coverage now, and treat participation status as off-limits for pricing: the moment non-sharers pay more, consent becomes a coverage surcharge. Buy aggregated process metrics, never incident contents.
And if you are a founder: build the permit application workflow first, sell it to the named waiver holders on the FAA's public list, and let permit revenue fund the SaaS. Ship before it crosses.
Related
📰 DOT DQF + Clearinghouse Compliance Automation for Small Fleets: the same organizational-compliance-records playbook applied to trucking, driver qualification files the FMCSA demands and the software that keeps them audit-ready
📰 Small Fleet Backoffice Automation: the back-office burden that crushes small operators in regulated transport, and the automation layer that absorbs it
📰 Freight Identity Verification SaaS: identity and qualification verification for freight carriers, the personnel-ledger analog in logistics