Drone service providers

Drone service providers

How independent Part 107 pilots and drone service companies use Omniris to find work, prove they are qualified, plan and check the flight, process what they captured, deliver it, and get paid — all from one account.

Summary

Most of the money in commercial drones is spent on flying, not on aircraft or software. One industry analyst puts services at 78.5% of the civil drone market in 2026, against 17% for hardware and 4.5% for software [1]. The people who do that flying — independent remote pilots and drone service companies — are the supply side of the industry. In the United States the FAA had issued more than 493,000 Remote Pilot certifications by December 2025, an increase of more than 70,000 in a single year [3].

Ask service providers what holds them back and the answers are consistent: regulation first, then finding clients and closing contracts, then funding to grow [2]. Around those sit the everyday chores of the job: proving a certificate is current, meeting each client's insurance and aircraft requirements, checking airspace and weather, paying for processing software, handing over large files, chasing deadlines and getting paid.

Omniris is a drone operations marketplace with a processing stack and an evidence vault behind it. For a pilot, it covers the whole job in one account:

The sections below go through each part of a service provider's work, what the industry expects, and how Omniris handles it; the remote pilot in command stays in charge of the aircraft and the flight. The marketplace, invoicing and payouts run in the Omniris cloud (Microsoft Azure and Google Cloud) and the Omniris data center edition; on-premises installations have no marketplace, but every planning, processing and delivery tool described here still applies.

How drone service providers work today

A services market

Drone Industry Insights forecasts the civil drone market growing from US$44.4 billion in 2026 to US$83.0 billion by 2035, a compound annual growth rate of 7.2%. Services — flying and the work around it — account for 78.5% of the 2026 market, hardware 17% and software 4.5%. Construction is the largest industry using drones, and mapping and surveying is the leading type of work [1].

The same firm's annual survey of the industry drew 768 responses from 87 countries, 68% of them from service companies. By share of respondents, the most common work was mapping and surveying (35%), inspection (26%) and photography and filming (18%) [2].

In the United States, the FAA issued more than 59,000 Remote Pilot certificates in the first year of Part 107, and more than 493,000 Remote Pilot certifications had been issued by December 2025 [3].

The work they fly

A service provider usually flies for several industries with the same few aircraft. The table groups the work by the categories the industry survey uses [2] and names the deliverable each normally ends in.

How work is won

Finding clients and closing contracts ranks as the second-biggest challenge in the industry survey, behind regulatory obstacles such as the certification process and being unable to fly beyond visual line of sight or at night [2].

The rules that govern the work

Commercial small-drone flight in the United States is governed by 14 CFR Part 107 [4]. A pilot needs a Remote Pilot certificate to fly for pay [4]. The rules a service provider meets on almost every job:

Beyond visual line of sight: Part 108

Executive Order 14307 of June 6, 2025 directed the FAA to propose a rule enabling routine flight beyond visual line of sight (BVLOS) [13]. The FAA published the proposal — new Parts 108 and 146 — on August 7, 2025. It would replace case-by-case waivers with operating permits for lower-risk operations and operating certificates for larger or more complex ones, and would make an operations supervisor, rather than a certificated remote pilot, responsible for safety. Comments closed on October 6, 2025, and a reopened comment period on electronic conspicuity and right-of-way closed on February 11, 2026 [12]. The final rule is under review at the White House Office of Information and Regulatory Affairs: in late October 2026 meetings on it were still being scheduled, the latest for October 29, 2026, and only the proposal and its comment-period notices had been published in the Federal Register [14]. Until a final rule is published and in force, BVLOS work still needs existing FAA approval, commonly a waiver of §107.31 [6].

Fleets: the FCC Covered List, Blue UAS and Green UAS

On December 22, 2025 the FCC added uncrewed aircraft and their critical components produced in foreign countries to its Covered List, which bars new equipment authorizations for them [15][16]. Drones already purchased, and models that already hold FCC authorization, are unaffected and can still be bought and flown [16]. In January 2026 the FCC exempted drones and components on the Defense Contract Management Agency's Blue UAS list and items that qualify as domestic end products under the Buy American standard, originally until January 1, 2027; on July 21, 2026 it extended both exemptions to January 1, 2028, and drones granted a Conditional Approval by the Department of War or the Department of Homeland Security stay exempt for as long as the holder keeps to the onshoring plan in its application [17].

The Blue UAS list is the Department of War's catalog of secure, NDAA-compliant drones and components; its management moved from the Defense Innovation Unit to DCMA on December 3, 2025 [18]. Green UAS is an industry certification launched by AUVSI in February 2023 that mirrors Blue UAS and verifies commercial drones against the NDAA's supply-chain requirements and cybersecurity standards [19]. When a client's contract names one of these lists, only an aircraft on it can fly the job, so a provider's fleet decides which of those jobs it can bid on.

Insurance clients ask for

Insurers that serve drone operators report that $1 million of liability cover suits many smaller jobs, while utility, large construction, government and infrastructure contracts regularly specify $2 million and some $5 million or $10 million. Clients typically also want to be named as additional insured, often want a waiver of subrogation, and ask for a certificate of insurance before work starts (vendor-reported) [20][21].

Where the time and money go

• Winning work and the paperwork around it — client acquisition is the industry's second-ranked challenge [2], and every new client brings its own insurance requirements [20][21].
• Regulation — ranked first [2]: airspace authorizations, waivers, recurrent training and Remote ID all sit with the pilot.
• Getting paid — with a direct client, payment follows the provider's own invoicing.

Use case by use case: what Omniris does

Each row is something a service provider has to do, and what Omniris gives you for it. Every row is explained in the sections that follow.

Winning work: the marketplace

On the Omniris cloud and the data center edition, clients post drone jobs and pilots apply for them. The marketplace is built around the two things the industry survey says matter most to providers after regulation: being found, and turning a lead into a contract [2].

Getting set up

A new pilot account works straight away: the vault, uploads, processing and every tool are available from the first sign-in. To be found by clients and to apply for jobs, an independent pilot completes a profile — phone number, a verified address, at least one aircraft and at least one certification — and submits it for review. Once approved, the Apply buttons appear and the pilot can be found on the pilot map. A Before you can be considered for jobs panel on the job board lists anything still missing, each item linked to the place that fixes it. Approved pilots also qualify for a free pilot plan with storage and a monthly processing allowance.

Finding jobs

• A job board with a map. The Available Jobs tab shows your home location, a circle for your travel radius (miles by default, adjustable on the map) and a pin for each open job, with the jobs inside the radius listed beside it.
• Alerts that respect your rates. An optional email tells you about new jobs within your travel radius, and a minimum-pay box suppresses jobs paying you less than the figure you set.
• Enough to decide, nothing more. Before you are assigned you see the job's specifications, deliverables, window, aircraft requirements, the insurance cover the client requires, your pay and a city-level location. The exact address, site boundaries, access instructions and the client's contact details appear the moment you are assigned, which protects the client's site without hiding what the job involves.
• Ask first. "Ask For More Information" opens a conversation with the client before you apply, and "Get Flyable Dates" jumps to the weather forecast for the job's location and window.

Being found

• The pilot map. Clients see approved pilots on a map with their aircraft, their average rating and Blue UAS / Green UAS badges. A U.S. pilot whose Part 107 is not current does not appear, and nor does a pilot who works only inside an organization.
• Ratings. When a client accepts results, they can rate the pilot from 1 to 5 with a comment. A pilot's average shows on the map and profile, and the pilot sees every rating on their account.
• A portfolio. Mark one folder in your vault as your portfolio and anyone signed in to Omniris who opens your profile sees a thumbnail grid and can browse it read-only — maps, 3D, photos and video. Treat it as public within Omniris.

Applying, offers and repeat work

• Applications. Apply with an optional message. When the client picks a pilot, every other application is declined automatically and those pilots are emailed that the client chose another pilot — no waiting on a job that has gone. If the client later unassigns that pilot, the declined applications return to pending.
• Proposing your pay. When a client asks pilots to propose a price, the phone app adds a Your pay field: you enter what you want to be paid, and if you are chosen that is what you are paid.
• Direct offers. A client can offer a job straight to a pilot who has already completed work for them, skipping the open board. You get a set number of business days to respond (three by default), counted on your own calendar so weekends and your country's public holidays don't count. While the offer is open, nobody else can see or apply for the job. An offer is withdrawn automatically if the job's location, schedule or pay changes.
• Recurring jobs. A client can set a job to repeat weekly, every two weeks, monthly, quarterly or on a custom interval. Each visit arrives as its own job with its own window, due date and payout.
• Returning a job. If you can no longer fly an assigned job, Return Job hands it back with a reason.

Your pay, never the client's price

Every job card, job page, offer, invoice, email and answer from Orion, the Omniris assistant, shows a pilot only what they earn: their total pay and their pay for each service line. The client's price, the platform's fee and the pilot's share as a percentage are removed on the server before anything reaches the pilot's screen, phone or desktop app. The figure shown on a job is worked out the same way the invoice will be, so the pay you see is the pay you receive.

Service companies and teams

A drone service company can run as an organization in Omniris, with one shared vault and members as managers, pilots or viewers. A job can be assigned to the whole organization rather than one pilot: every active pilot in the organization can upload to its delivery folder, and a manager submits the results. The payout for an organization job goes to the organization's owner, who pays the team in the company's own way. An organization's pilots see only its own jobs; Part 107 checks are left to the organization, which manages its pilots' certification itself.

Your own clients, in the same place

Not every job comes through a marketplace. Pilot Initiated Jobs let you log work for your own clients in Omniris with the same site boundary, flight details and scheduling as a marketplace job. These jobs are private: never posted, never seen by another pilot. You record your fee, Omniris takes no cut, and you bill the client yourself. When the work is ready, Submit to Client makes a link to the delivery folder — view only or view and download, an optional password, an expiry of never, 7, 30 or 90 days, and an optional view limit — and drafts an email in your own mail program, so it comes from your address. Each new send switches the previous link off.

Credentials, insurance and aircraft

Clients ask for proof of adequate insurance [20][21]; flying for pay takes a Part 107 certificate kept current [4][5]; and where a contract names the Blue UAS or Green UAS list, only a qualifying aircraft can fly the job. Omniris keeps that proof on the pilot's account, checks the Part 107 certificate against the FAA's own record, and uses your aircraft records to match you to jobs that name the Blue UAS or Green UAS list.

Part 107, checked with the FAA

• Verified, not typed in. Drop a photo or scan of your Part 107 card; Omniris reads the name, certificate number and date of issue from it and looks them up in the FAA's public Airmen Inquiry. Or enter your last name and certificate number and run the same lookup. A successful check shows the certificate number, the name as the FAA has it and the date granted.
• Recurrent training tracked. The FAA lookup does not show recurrent training, so Omniris tracks it separately. Once your certificate is more than 24 months old, upload your recurrent-training completion certificate and Omniris reads the completion date from it. A certificate it cannot read is refused with a message rather than accepted on trust.
• What "current" means. FAA-verified, a certificate image on file, and either the date of issue or the recurrent training within the last 730 days — the 24 months of §107.65 [5]. Your account shows a CURRENT or EXPIRED pill.
• What it is used for. In the marketplace, a U.S. pilot needs a current Part 107 to apply for jobs and to appear on the pilot map. Pilots outside the United States are not held to the FAA check.

Insurance, read and shown

Upload your policy or certificate of insurance as a PDF or image and Omniris reads it with AI, listing the insurer, policy number, policy holder, effective and expiry dates, per-occurrence and aggregate limits, and whether aviation liability, bodily injury and property damage cover appear. The extracted details are labelled as parsed: the reading is a summary of the document, not a verification of it. The account page states the platform's minimum expectation — UAS liability cover of $1,000,000 per occurrence and $2,000,000 aggregate — and a client's job form states the same standard. A client who needs more for a particular job can set its own per-occurrence and aggregate limits. Every job page, on the web and on the phone, shows you the cover that job requires — the platform standard when the client set no figures of its own — and a job with its own figures also carries an insurance chip on its card on the web's job board, so you can see it before you apply. Whether your cover meets a job's requirement is your call, as it is in clients' own vendor checks [20][21].

Aircraft and sensors

• Your fleet from a catalogue. Add aircraft and attach sensors from the Omniris equipment catalogue, which shows each model's maximum wind, flight time, ingress rating, operating temperature and weight where known. If yours isn't listed, request it from the picker. The same records drive the mission planner's camera maths and the weather check's limits.
• Remote ID serial. Record the FAA Remote ID (ANSI/CTA-2063-A) serial of each physical aircraft. Omniris keeps it with the aircraft's record.
• RTK and PPK. Tick whether you have real-time or post-processed high-accuracy positioning. Jobs that require it are shown only to pilots who have it.
• Blue UAS and Green UAS. Catalogue models on the Blue UAS list or the Green UAS list carry blue and green shield badges in the picker, on your aircraft cards and on your dashboard. A job that requires either list shows a shield chip on its card, with a red warning when none of your aircraft qualifies, and an application without a qualifying aircraft is refused with a message saying which list it needs. A client's direct offer to a pilot is not checked against the list: the client confirms the aircraft itself. The badges reflect the catalogue's record of the model; whether a particular contract accepts your aircraft is between you and the client.
• Other certifications and documents. Add other certifications from a catalogue with issue and expiry dates (an expired date shows red) and an image of the certificate, and keep training records and other documents as attachments.

Planning and flying the mission

Once you are assigned, the job page shows the exact site, its work areas and any no-fly zones, and the tools to get the flight ready. The full detail is in the Mission planning paper; this is what matters to a provider.

Before you commit to a date

• Weather go / no-go. Flyability scores every hour up to 16 days ahead against your chosen aircraft's rated wind and temperature limits — rain, gusts, visibility, fog, thunderstorms, daylight, air quality and geomagnetic activity that can degrade GPS — and finds runs of flyable hours long enough for the job. Wind is also shown at heights up to about 660 ft (200 m), and you can ask for an email when a day's forecast changes.
• A planned flight date. Set the day you intend to fly. It goes on your Upcoming Flights calendar and posts a note in the job conversation, so the client isn't left guessing; a date outside the client's window gets a warning but is allowed. If you haven't set one, you get a reminder email about 4 days before the window opens.
• The site boundary in your own tools. Download the job's work areas as GeoJSON, KML, KMZ or a shapefile.

The mission planner

Pick the area, your aircraft and its camera, and choose a pattern: grid for maps, crosshatch for 3D, corridor for roads and lines, perimeter for facades and stockpiles, or orbit for a single structure. The planner works out height and ground detail from the real camera, sets photo spacing from the overlap, slows the aircraft when the camera can't keep up, estimates motion blur, and shows photos, flight time and batteries as you change anything. Terrain follow holds a steady height above sloping ground using a worldwide terrain model or your own earlier survey. No-fly zones drawn on the job are enforced with a standoff (25 ft (7.6 m) by default), and a mission planned before a zone was added cannot be exported until it is re-planned. Heights above 400 ft get a warning that cites §107.51.

Every export comes with a one-page parameter sheet of what the file can't carry, starting with where to take off. The mission file can also be saved to the job's folder with its own custody record, so which plan you were given is a recorded fact.

Airspace and LAANC

Every job shows an Airspace card for its location, and every saved mission gets a check of the whole route, as flown, against the FAA's published airspace data. The check is floor-aware: much controlled airspace starts well above the ground, and a Class B or C shelf that begins thousands of feet up does not apply to a flight beneath it, so it is listed as overhead rather than flagged. When authorization is needed, Omniris says whether LAANC can grant it (and the lowest ceiling on the route) or whether it needs further coordination or an application through the FAA's DroneZone.

For LAANC, Omniris works out how many authorizations the route needs — one per ceiling, as the FAA requires — checks the request before you file it — a pilot name and a phone answered during the flight, an area no more than 10 nautical miles across, no more than 5 overlapping operations, a window between 5 minutes and 12 hours, and the 72-hour lead that further coordination needs [8] — and gives you a ready-to-paste block for each. You file it in a free LAANC app, then record the authorization number, height and window granted, with a screenshot if you like. Omniris compares what was granted with what the mission plans and says loudly if it falls short. A recorded authorization is marked pilot-attested: Omniris did not issue it and cannot see the FAA rescind it. Airspace data covers the United States and its territories and is advisory; it is not a NOTAM or TFR briefing.

On site

• A Part 107 pre-flight checklist. The built-in checklist has 22 items. Nine quote §107.49 word for word; seven more cite other Part 107 and Remote ID rules; six are practical checks. The 16 regulatory items cannot be removed from any copy you make. A recorded LAANC authorization shows against the airspace item. A completed checklist is frozen, kept with the job and visible to the client — evidence that the assessment §107.49 requires was made.
• The phone app. Omniris Pilot for iPhone and Android takes a job from brief to navigation, pre-flight, capture, quality check, upload and submission. The checklist works with no signal and captures the airspace check and weather at the moment it starts. See the Field app paper.
• Ground photo requests. Some clients pin the spots where they want ground-level photos. The pins come with notes, and once you deliver, each shows the photos matched to it.

Processing included

In Omniris, processing is part of the same account as the jobs: your photos go into your vault, and the processing runs on Omniris machines sized to the job. It is paid in credits from your plan — every pilot plan, including the free ones, comes with a monthly allowance, and very small runs can be free. Before anything starts, the dialog checks the photos and shows the price in credits; if your balance is short, the job does not start and nothing is charged.

Checked before you pay

Wasted processing is wasted money and a missed deadline, so each pipeline checks the photos first. The map dialog groups the photos into flights, reads the camera angle from every photo and refuses a map from photos shot too far from straight down — offering a 3D model of the same flight instead — and warns when a folder holds two or more separate clusters of photos too far apart to join, such as two flights merged by mistake. The 3D, splat and panorama pipelines run their own pre-flight checks on the photos before they start. Problems come with what to do about them, before anything is charged.

Processing can be started from the web, the desktop application or the phone's quick actions, and runs whether or not you stay connected; you are emailed when it finishes or fails. On a client's job, you can run it straight on the client's delivery folder.

Delivering the work

Handing over gigabytes of photos and processed products is where many jobs stall. On a marketplace job the files never leave Omniris: they move from the pilot's side to the client's inside the same system. The full detail is in the Sharing and delivery paper.

The delivery folder

Every assigned job has a Job Files card. Either the client has set a delivery folder in their own vault, which appears in yours under Active Jobs for as long as you are working the job, or you pick a folder in your own vault. Upload Results takes you there. Files uploaded into it are linked to the job automatically, each with a custody record. Large uploads resume after an interruption, and the phone app uploads as you work — on Wi-Fi only if you prefer.

Submitting and review

1. Submit Results, with an optional note to the client about the deliverables or the conditions on the day.
2. A read-only snapshot of the folder lands in the client's vault, and the client is told in Omniris and in the job conversation.
3. The client opens and reviews everything. Downloading is held back until they accept.
4. Accepted completes the job; the client can rate you. Rejected comes back with a note saying what is wrong and a Resubmit by date. Upload what is needed and submit again; the new delivery replaces the previous one.

Deadlines and reminders

Every assigned job has a Deliverables Due date. It is the client's deadline, or — if they set none — a standard number of days after the client's flight window ends, fixed when you are assigned. After a rejection, the Resubmit by date takes over. Omniris then reminds you by email until you submit:

Reminders stop the moment you submit, a missed reminder is never sent late in a pile, and an overdue job shows a red Overdue badge. If you can't make the date, say so in the job conversation.

Talking to the client

Each job gets a conversation when you are assigned, with file attachments, and system messages land in it when you accept an offer, set or change your flight date, or the deliverables become overdue. Job notes keep your submission notes and the client's rejection notes in order. If you are taken off a job, you keep read-only access to the conversation up to the moment you left.

A record of the hand-over

Every file you deliver has a custody history: when it was uploaded, linked to the job, processed, delivered and downloaded. Completed pre-flight checklists and recorded LAANC authorizations sit with the job, and if the client puts the job under a legal hold, all of it is preserved together. When a delivery is questioned months later, what was handed over, and when, is a record rather than a recollection. See the Evidence integrity paper.

Getting paid

In Omniris, payment follows the client's approval of the work, with the steps written down and visible to the pilot at each stage. Invoicing and payouts exist on the Omniris cloud and the data center edition; on-premises installations do not invoice.

Setting up payouts

You set up a payout account once, from the account page. Choose the country of your bank account and tax residence — the United States, Canada, the United Kingdom, Switzerland or a European Economic Area country other than Iceland — and Stripe's own secure form collects your bank details, identity and the tax information it needs. Omniris never sees your bank account. The payout account shows as not set up, in review, or ready; Manage payouts opens your Stripe dashboard. If a client pays before you finish setting up, nothing is lost: the payout waits, you get one email with the link, and it is sent on the next pass after your account is ready. The phone app's Earnings screen shows your earnings for the last 30 days, pending and lifetime, each invoice with its status and your payout, and your payout account's status, with any pay waiting on your setup. You can set the account up, continue an unfinished setup or open your Stripe dashboard from the phone; Stripe's pages open in the phone's browser. Linking a Stripe payout account you already have is done on the web.

What you see, and what you don't

Your copy of an invoice — on screen, as a PDF, in emails, on the phone and in Orion's answers — shows each service with your pay for that line and how it is paid (a fixed amount or a share), your total payout and its status: pending, the hold's release date, or sent. It never shows the client's prices, the invoice total, what the client paid or the platform's fee; those are removed before your copy leaves the server. If something is wrong, Report a problem on the invoice records your note and raises it for follow-up.

Illustrative example values.

On a job assigned to a whole organization, the payout goes to the organization's owner, who pays the team. On a pilot-initiated job for your own client, Omniris records the fee you entered and takes no cut; you invoice that client yourself.

Records: logbook, equipment, custody

The FAA does not require a logbook, but its advisory material notes that recordkeeping can be beneficial [22]. Omniris keeps those records as a side effect of doing the work.

The pilot home page

Signing in lands a pilot on a home dashboard that pulls the day together: the flyability forecast for your address, the Upcoming Flights calendar, your active, applied and completed jobs, running processing jobs, recent folders and messages, your drones, and your plan, credits, storage and average rating. Sections can be reordered and hidden. Until your profile is complete, a checklist at the top shows what is left. Top-bar badges count new jobs posted since your last visit and the jobs assigned to you.

Cloud, data center and on-premises

Omniris runs in four ways: the Omniris cloud on Microsoft Azure, the Omniris cloud on Google Cloud, the Omniris data center edition, and on-premises installations. What a service provider gets differs in one respect:

The phone app's sign-in screen has a picker for which Omniris service it talks to, including the data center edition, so one app serves a pilot who works on more than one. An on-premises installation with Hybrid set up can choose, job by job, to run processing in the Omniris cloud instead of on its own machines.

What the product claims, and what it doesn't

Omniris organises the work, checks what can be checked and records what was done. These are the boundaries a provider should rely on:

• The pilot flies. Omniris writes a mission file that you import into your own flight app; it never connects to or controls the aircraft, and return-to-home, signal-loss and low-battery behaviour stay aircraft settings.
• Authorizations come from the FAA. LAANC filings are made by you in a LAANC app and recorded in Omniris as pilot-attested. Waivers, including BVLOS waivers, are applied for with the FAA; Part 108 is not yet final [14].
• The airspace check is advisory, not a briefing. It reads the FAA's published airspace data for the United States and its territories, without NOTAMs or TFRs, and outside FAA coverage it says so rather than calling the area clear. Visual line of sight, people on the ground and obstacles are on the checklist for you to assess.
• Insurance is read, not verified. Policy documents are summarised as parsed; whether your cover meets a job's requirement is yours to decide, and certificates of insurance and additional insureds come from your insurer.
• Records are not certifications. The Part 107 check is a lookup of the FAA's public record plus the training certificate you upload. Blue / Green UAS badges reflect the catalogue's record of a model, not a determination about your aircraft or a client's contract. Remote ID serials are stored as entered; the broadcast itself is the aircraft's.
• Commerce is a cloud and data center feature. Jobs, offers, invoicing and payouts exist on the Omniris cloud and the data center edition, not on-premises. Payouts go to Stripe payout accounts in the United States, Canada, the United Kingdom, Switzerland and the European Economic Area except Iceland. For your own clients' jobs, you bill the client yourself.
• A drone survey is not a licensed land survey. Processed maps and models report their accuracy; a licensed surveyor's certification remains outside Omniris.

Sources

Industry figures and rules in this paper come from the sources below. Insurance limits quoted from vendors are marked as such in the text.

1. Drone Industry Insights, "The US$83 billion drone market by 2035" (civil market forecast 2026–2035, segment shares). droneii.com/the-83-billion-drone-market-by-2035
2. Commercial UAV News, "Top findings from the Drone Industry Insights Global State of Drones report" (768 respondents, 87 countries; challenges; applications). commercialuavnews.com/top-findings-from-the-drone-industry-insights-global-state-of-drones-report
3. Commercial UAV News, "Ten years of Part 107: the regulation that created the U.S. drone industry" (citing the FAA aerospace forecast). commercialuavnews.com/ten-years-of-part-107-the-regulation-that-created-the-u-s-drone-industry
4. 14 CFR Part 107, Small Unmanned Aircraft Systems (Legal Information Institute). law.cornell.edu/cfr/text/14/part-107
5. 14 CFR §107.65, Aeronautical knowledge recency. law.cornell.edu/cfr/text/14/107.65
6. FAA, Part 107 Waivers. faa.gov/uas/commercial_operators/part_107_waivers
7. FAA, UAS Data Exchange (LAANC). faa.gov/uas/getting_started/laanc
8. FAA, Part 107 Airspace Authorizations. faa.gov/uas/commercial_operators/part_107_airspace_authorizations
9. FAA, Operations Over People General Overview (including night operations). faa.gov/uas/commercial_operators/operations_over_people
10. FAA, Remote Identification of Drones (who must comply; standard Remote ID, broadcast module or FRIA). faa.gov/uas/getting_started/remote_id; and 14 CFR Part 89, Remote Identification of Unmanned Aircraft (Legal Information Institute). law.cornell.edu/cfr/text/14/part-89
11. Academy of Model Aeronautics, "Remote ID Compliance and Resources" (the three ways to comply). amablog.modelaircraft.org/amagov/2024/01/17/remote-id-compliance-and-resources
12. Federal Register, "Normalizing Unmanned Aircraft Systems Beyond Visual Line of Sight Operations", proposed rule, August 7, 2025 (Docket FAA-2025-1908). federalregister.gov/documents/2025/08/07/2025-14992; and "… Reopening of Comment Period", January 28, 2026 (comments on electronic conspicuity and right-of-way due February 11, 2026). federalregister.gov/documents/2026/01/28/2026-01644
13. Federal Register, Executive Order 14307, "Unleashing American Drone Dominance", June 6, 2025. govinfo.gov/content/pkg/FR-2025-06-11/html/2025-10814.htm
14. Office of Information and Regulatory Affairs, EO 12866 meetings for RIN 2120-AL82, "Normalizing Unmanned Aircraft Systems Beyond Visual Line of Sight Operations", Final Rule Stage (meetings scheduled through October 29, 2026), reginfo.gov — RIN 2120-AL82 meetings; and Federal Register, documents in Docket FAA-2025-1908 (the proposed rule and its comment-period notices only), federalregister.gov/docket/FAA-2025-1908
15. FCC Public Safety and Homeland Security Bureau, Public Notice DA 25-1086, December 22, 2025 (foreign-produced UAS and critical components added to the Covered List). docs.fcc.gov/public/attachments/DA-25-1086A1.pdf
16. Commercial UAV News, "FCC adds UAS and drone components to the Covered List" (existing and authorized models unaffected). commercialuavnews.com/fcc-covered-list-uas-drone-components-dji-autel
17. Wiley, "FCC Issues Exemptions, Clarifications for Sweeping Prohibition of Foreign-Made Drones" (January 12, 2026, updated March 23, 2026). wiley.law/alert-FCC-Issues-Exemptions-Clarifications-for-Sweeping-Prohibition-of-Foreign-Made-Drones; and FCC Public Safety and Homeland Security Bureau, Public Notice DA 26-761, July 21, 2026 (Blue UAS and Buy American exemptions extended to January 1, 2028; Conditional Approvals exempt). docs.fcc.gov/public/attachments/DA-26-761A1.pdf
18. Defense Innovation Unit, "DIU's Blue UAS list to transition to DCMA". diu.mil/latest/dius-blue-uas-list-to-transition-to-dcma
19. Defense Innovation Unit, "AUVSI launches Green UAS cybersecurity certification program for commercial drones". diu.mil/latest/auvsi-launches-green-uas-cybersecurity-certification-program-for-commercial
20. SkyWatch (drone insurer), "Commercial drone liability limits: what your clients are actually requiring" (vendor). skywatch.ai/blog/commercial-drone-liability-limits-what-clients-require
21. SkyWatch (drone insurer), "What commercial drone clients actually require from your insurance" (vendor). skywatch.ai/blog/commercial-drone-insurance-client-requirements-enterprise
22. Pilot Institute, "Drone flight logs" (quoting FAA Advisory Circular 107-2 on recordkeeping). pilotinstitute.com/drone-flight-logs

Glossary

Blue UAS

The U.S. Department of War's list of secure, NDAA-compliant drones and components, managed by the Defense Contract Management Agency.

BVLOS / VLOS

Beyond / within visual line of sight. Part 107 requires visual line of sight unless the FAA grants a waiver.

Certificate of insurance (COI)

A document from an insurer summarising a policy's cover, often naming the client as additional insured.

Covered List

The FCC's list of equipment that cannot receive new FCC equipment authorizations; foreign-produced drones and their critical components were added in December 2025.

Direct offer

A job offered straight to one pilot, with a business-day deadline to accept or decline, instead of being posted to the job board.

Further coordination

A LAANC request above the UAS Facility Map ceiling, reviewed by air traffic control; it must be filed at least 72 hours ahead.

Green UAS

AUVSI's certification of commercial drones against NDAA supply-chain and cybersecurity requirements, modelled on Blue UAS.

Hold period

The time between a client paying an invoice and the pilot's payout being released; 5 business days by default.

LAANC

Low Altitude Authorization and Notification Capability: the FAA system that authorizes flight in controlled airspace near airports in near real time, up to the UAS Facility Map ceiling.

Orthomosaic

One map-accurate image stitched from many overlapping drone photos, on which distances and areas can be measured.

Part 107

The FAA rules for commercial small-drone flight in the United States (14 CFR Part 107), and the Remote Pilot certificate they require.

Part 108

The FAA's proposed rule for routine BVLOS operations, published as a proposal in August 2025 and not yet final.

Pilot-attested

A record, such as a LAANC authorization, that the pilot obtained elsewhere and entered in Omniris. Omniris compares it with the plan but did not issue it.

Pilot Initiated Job

A private job a pilot logs in Omniris for their own off-platform client; called a Self-Initiated Job on-premises.

Recurring job

A job a client sets to repeat on a schedule; each visit arrives as its own job with its own due date and payout.

Remote ID

The FAA requirement (14 CFR Part 89) for a drone to broadcast its identity and location in flight.

Remote pilot in command

The certificated pilot responsible for a flight.

UAS Facility Map

The FAA's grid around airports showing the highest altitude LAANC can approve in each cell.