Satellite-linked drones: Starlink, control and limits

A data link, not a navigation signal

Starlink’s engineering note describes the signal travelling from the user to a satellite and back down to the ground. The operator’s connection is therefore a network path, rather than a single direct beam from a person to an aircraft.[9]

Satellite communications and satellite navigation are different functions. IEEE Spectrum describes Starlink terminals and GPS separately on Magura boats. The first supplies a data connection; the second supplies navigation information. Mentioning GPS on a drone is therefore not evidence that someone can remotely steer it through Starlink.[9][10]

Beyond-visual-line-of-sight (BVLOS) control predates Starlink. The US Air Force describes the MQ-9’s split operations with a distant mission crew, and General Atomics markets MQ-9B SkyGuardian for over-the-horizon satellite operation. The latter’s endurance specification remains a manufacturer claim, not a measured figure for Ukrainian drones.[13][16]

A sourced timeline

1. 2022-09

   AP’s September 2023 reporting describes a Ukrainian request in September 2022 to enable Starlink support for an attack on Russian naval vessels near Crimea. It reports that the request was refused. The episode concerned an actual service-access decision, not whether satellites could physically pass over the area.[6]

2. 2023-09-11

   An early account said service was cut during the mission. A published correction instead said it had not been enabled near Crimea.[5]

3. 2024-02

   In February 2024, Ukrainian intelligence alleged Russian use of Starlink terminals in occupied Ukraine. Reuters reported the allegation that terminals came through third countries. SpaceX denied doing business with Russia’s government or military. A denial of authorised sales does not by itself resolve allegations of third-party diversion.[14][15]

4. 2026-01-29

   On 29 January 2026, Ukraine’s defence ministry said it had contacted SpaceX within hours of detecting Russian Starlink-connected drones over cities. This records the ministry’s statement and request for action; it is not an independently complete inventory of Russian satellite-linked UAVs.[8]

5. 2026-02-05

   On 5 February, the ministry said the first whitelisted terminals were operating and Russian terminals had been blocked. Its FAQ also said an unregistered stored terminal could be verified later. These statements describe a managed process, not proof that Russian access could never recur.[3][7]

6. 2026-10

   The access story did not end with the February whitelist. In October 2026, AP reported that SpaceX had throttled Starlink service in Ukraine, and later that Ukraine’s access to Starlink and Starshield links had been restored. These reports do not disclose every contract or restriction.[12]

What is established, and what is claimed?

Latency, bandwidth and the video delay

Starlink’s service specification gives typical land latency of 25–60 milliseconds and download speeds of 25–220 Mbps. Its engineering note treats the physical trip to the satellite and back as one part of that delay. These are network figures: they do not measure the complete camera-to-screen-to-command delay of a drone.[9][17]

Bandwidth and latency answer different questions: how much data moves, and how long a response takes. Starlink’s June 2025 US median latency claim of 25.7 ms is a useful example of a bounded network statistic. It is not a promise of that performance over every battlefield or on every moving terminal.[11][17]

Sea drones and airborne reports

IEEE Spectrum describes Magura V5 boats equipped with Starlink terminals and says Sea Baby is likely remotely controlled with Starlink and GPS. Keep that qualification: the article does not establish that every Magura, Sea Baby or later variant carries an identical communications package.[10]

AP reported in October 2026 that it was common for Ukrainian drones to be equipped with Starshield, the military version of SpaceX’s satellite service. The same report says it was not used on Russian territory. This is a reported airborne use case and a stated boundary; it does not disclose every aircraft’s communications fit.[18]

For Ukrainian long-range UAVs, CSIS describes Lyutyi combining autonomous route segments with a mainly manual final approach. Officials declined to explain that communications link. The report does not identify it as Starlink. We therefore do not label every long-range strike “satellite controlled”.[1]

A terminal at a ground position and a terminal carried by a drone are different pieces of evidence. The February 2024 reporting concerned Russian forces’ communications. Ukraine’s January 2026 ministry statement specifically concerned Russian drones using Starlink over Ukrainian cities. Do not silently substitute one claim for the other.[8][15]

The Crimea episode: event and correction

AP’s September 2023 reporting describes a Ukrainian request in September 2022 to enable Starlink support for an attack on Russian naval vessels near Crimea. It reports that the request was refused. The episode concerned an actual service-access decision, not whether satellites could physically pass over the area.[6]

An early account said service was cut during the mission. A published correction instead said it had not been enabled near Crimea.[5]

Whitelists, restrictions and export questions

On 2 February 2026, Ukraine’s ministry announced that only authorised Starlink terminals would be permitted to operate in Ukraine, under a whitelist coordinated with SpaceX. A whitelist is an access-control measure. It is different from radio jamming of an aircraft’s command link.[20]

On 5 February, the ministry said the first whitelisted terminals were operating and Russian terminals had been blocked. Its FAQ also said an unregistered stored terminal could be verified later. These statements describe a managed process, not proof that Russian access could never recur.[3][7]

Commercial availability is not blanket permission for weapon use. Starlink’s cited terms restrict weapon-related uses and refer to US export controls; its acceptable-use text makes remote drone control conditional on contractual permission. A March 2024 congressional letter questioned safeguards. A letter alleging compliance problems is not a court finding.[2][4][19]

Three different failure points should be kept separate: the radio path to a satellite, the network carrying the data, and the provider’s authorisation of a terminal. The whitelist and later speed restrictions demonstrate why access policy belongs in an explanation of capability alongside the hardware.[9][12][20]

▶Reuters: allegations of Russian terminal procurementWatch at the source · Reuters ↗

The video opens only when you follow this link. No third-party video resources load here.[14]

Original schematic by DroneLedger editorial team · not to scale

Continue with our records

• Sea Baby
• Magura V5
• Magura V7
• Molniya fixed-wing FPV family
• Russian drones found using Starlink terminals for control
• Ukraine introduces a Starlink whitelist to cut off Russian drones
• SpaceX · Starshield