Skydio Dock for X10 remote operations: dock hives, remote pilots and BVLOS procedures

The Skydio Dock for X10 is a weatherproof box that stores, charges and launches an X10, gets it airborne in about 20 seconds and syncs its data when it lands. It is on the Blue UAS Cleared List, which is why US agencies and utilities that cannot buy foreign-made docks look at it early. A dock does not fly itself into a useful program, though. Someone still has to approve each launch, watch the airspace, handle the call that changes mid-flight, and make sure the footage reaches the people who need it.

What the dock does, and what the remote pilot still does

Dock-based flights are flown through Remote Flight Deck, the browser application included in Ops Center and in DFR, Asset and Security Command. The pilot sees live video, telemetry, the dock's weather readings and the airspace picture in one place.

Dock hives: coverage and continuity

Skydio calls a group of 2 to 6 docks at one site a hive. The point is not more drones in the air at once. It is continuity: while one X10 recharges, another is ready, and a long incident can be covered by launching a replacement before the active aircraft returns. Skydio's DFR FAQ describes exactly that swap, plus retasking one or several drones as a situation evolves.

One pilot, several docks: what the rules allow today

Skydio is direct about this. Its dock FAQ says the software has no limit on how many docks you can monitor and one operator can oversee several, but "FAA rules currently allow a remote pilot to control only one drone at a time", while pilots can prepare missions across docks in parallel. That matches 14 CFR 107.35, which bars one person from acting as remote pilot for more than one aircraft at once unless a waiver says otherwise.

So a remote operations center running Skydio docks today works like this. One pilot monitors a set of docks: health, weather, scheduled missions and alarms. When a launch happens, that aircraft has a pilot in command until it lands. A second launch elsewhere goes to a second pilot. The supervision ratio rises only when your approvals say it can. Staffing a 24/7 dock network is therefore a question of peak simultaneous flights, not of dock count.

Mission planning for docked flights

Docked flights come in three kinds, and each needs its own plan. Scheduled missions (a nightly perimeter patrol, a weekly substation thermal pass) are built once in the browser as Waypoint or Map Capture missions, with geofences and airspace boundaries set before takeoff. Triggered missions launch from an alarm, a dispatch system or a 911 call through Skydio's integrations, so the plan is a response template: where to fly first, what altitude, what to look at, and when to hand off to a human decision. On-demand flights are the pilot's own, launched to look at something specific. Programs can also schedule missions through the Cloud API, including running a template immediately on an online aircraft. Whatever the kind, every template should name its site, asset and expected outputs, because that is what the data will be filed under.

Weather and the go/no-go call

The dock and the aircraft have different limits, and the pilot has to know both. The technical specs list a launch and land wind limit of 27 mph and an X10 rain limit of 0.25 in/hr (light to moderate), while the dock itself tolerates heavy rain on standby and withstands winds up to 100 mph when bolted down. A dock that survives a storm is not a dock that can launch into one. The integrated weather sensors feed Ops Center or Skydio Command for exactly this decision. Good practice is a written go/no-go table per site, checked before each launch rather than judged from the video.

Connectivity: the dock's backhaul is the pilot's link

Skydio asks for at least 20 Mbps upload at each dock, 100 Mbps for faster media sync, over Cat6, 5G backhaul or Starlink. In flight, the X10 talks to the dock over Skydio Connect, and an External Radio placed up to 300 ft from the dock can extend coverage. With Connect Fusion, the aircraft blends point-to-point and 5G. For a remote pilot, every one of those hops adds delay and a point of failure, so the onboard autonomy handles close obstacles and the pilot works at the level of where to go and what to look at. Our latency guide covers why supervised control survives a delayed link when direct stick control does not.

Data delivery from a docked X10

Dock or field-launched X10?

The same X10 can be flown remotely without a dock: a field crew launches it, and a remote pilot flies it through Ops Center. The dock earns its cost where flights repeat at one place (a substation, a campus, a city sector), where response time matters, and where nobody can be on site at 3 a.m. Field launches suit linear assets, one-off surveys and sites without power and network. Many programs run both. The dock's site work is real: 100–240V power, a Cat6 run in conduit, a level mount, and an installation Skydio says typically takes 1 to 3 days with a field technician on site, plus two days of training.

Regulation and the Blue UAS angle

As of October 2026, the facts we could verify:

The waiver sets the procedures: altitude limits, whether a visual observer is needed, how traffic is detected and what the pilot does about it. Some agencies, per Skydio, hold waivers that allow flight without visual observers. Where yours does not, the visual observer's position, radio protocol and handoff to the remote pilot belong in the site plan. None of this is legal advice.

What a good dock pilot does

How RoboPilots staffs Skydio docks

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

For the aircraft itself, see the Skydio X10 page. For the role, see remote drone pilot careers.