Skydio X10 remote operations: browser flight, Blue UAS fleets and clean mission data

The Skydio X10 is the aircraft most US agencies and utilities look at first when they need a drone they are allowed to fly: designed and assembled in the US, NDAA compliant, and on the Blue UAS Cleared List. It is also a drone designed around remote operation. Skydio's own page describes flying it from a browser and handing control to "an operator anywhere". That makes the X10 less about stick skills and more about who sits in the remote seat, how many aircraft they watch, and what they do in the seconds after something goes off plan.

X10 or X10D: two aircraft, two operating models

The two share an airframe and most specs: 45 mph top speed, IP55, a 15,000 ft service ceiling and the same VT300 sensor packages. They differ in how they connect, and that decides how you run them remotely.

For a remote operations center serving a city or a utility, the X10 is the usual choice. For an agency that needs its own ground control software or cannot route video through a commercial cloud, the X10D and its MAVLink interface are the starting point. Skydio's R10, added to the Blue UAS list at the same time as the X10, is a separate aircraft and not covered here.

How an X10 is flown remotely

There are four layers, and a remote program usually uses three of them. Knowing which one a pilot is working in at any moment is most of the training.

The link: what the remote pilot can and cannot do over it

Video from an X10 reaches a remote pilot either over a point-to-point radio and then the internet, or straight over cellular. Either way it is compressed, buffered and subject to coverage. That delay is the reason a remote X10 pilot does not fly close-quarters manual maneuvers by the video alone: the onboard obstacle avoidance closes that loop locally, at the aircraft. What works well over the link is supervised flight: waypoint and map missions, point-and-fly moves, camera and zoom control, holding a position on a subject, and deciding when to return.

Our latency guide explains why supervised control holds up over delayed links when direct manual control does not.

One pilot, many aircraft

Skydio's Ops Center page says "a single operator flies multiple missions, across different locations at the same time", and DFR Command adds the qualifier that matters: "with the required FAA approval". The ratio of pilots to aircraft is set by your FAA approvals, not by the software. In practice a remote operations center runs it in tiers:

Mission planning and takeover

Most X10 flights in a remote program start as a template: a Waypoint or Map Capture mission built in the browser, with geofences and operating rules set once and applied to every flight. A good planning standard for each site covers launch and landing points, altitude bands, no-fly geofences, which sensor package and camera settings to use, and what counts as a successful capture. Takeover is the other half. The pilot should be able to answer three questions at any point in a flight: who is in control right now, what the aircraft will do if I let go, and where it will land if the link drops.

Data from an X10: what comes back and how it is tagged

The step teams skip is the tagging. Every flight should land in your system with the site, asset or incident number, the mission template it ran, the pilot of record and the outcome. That is easy to set at planning time and painful to reconstruct from timestamps later.

What a good X10 remote pilot watches for

The allowed-fleet question

Much of the X10's demand comes from rules about which aircraft an agency may buy. As of October 2026, here is what the sources we checked say:

None of this is legal advice, and procurement rules vary by grant and agency. The practical point for an operations team: a fleet moving from DJI to Skydio changes software, link, data path and autonomy at once, so pilots need retraining on the X10 even if they have years on a Matrice.

BVLOS and airspace procedures

In the US, routine BVLOS flight still runs on case-by-case approvals. The FAA's Part 108 BVLOS final rule has been at OIRA since July 10, 2026 and, per PickDrones, had no firm publication date. Until it lands, programs fly under Part 107 waivers, public-agency COAs or Part 135. Skydio sells regulatory services for this and lists waivers it has helped with, including no-visual-observer DFR approvals with ADS-B at 200 ft. Each waiver carries its own conditions: altitude, shielding, whether a visual observer is required, and what the pilot must do when traffic appears. The remote pilot's procedures have to match those conditions exactly, flight after flight.

How RoboPilots runs X10 programs

Your aircraft, docks and Skydio accounts stay yours. We train a dedicated group of Part 107 certified remote pilots on your X10s, your sites and your waiver conditions before they fly a live mission, and the same group stays on your program.

If your X10s will live in docks, read the Skydio Dock for X10 page next. If you are hiring rather than outsourcing, our remote drone pilot careers page describes the role.