What Ukraine proposed

The request was broader than permission to fly drones. Kyiv wanted Starlink connectivity to remain available as long-range drones crossed into Russia, allowing operators to guide the aircraft toward missile launchers and the systems that support them. The reported target set included launch infrastructure, command centers and other military assets.

The proposed operating area extended as far as 200 km from Ukraine’s internationally recognized border. Reports identified Bryansk, Kursk, Belgorod, Voronezh, Rostov-on-Don and Krasnodar among the major Russian cities within the described zone.

Why Kyiv was pursuing the plan

Ukraine’s immediate concern was the availability of Patriot interceptor missiles, which it relies on to defend against Russian ballistic-missile attacks. Kyiv presented Starlink-enabled drone operations as a way to reduce that dependence by attacking missile launch systems before they could fire, rather than relying only on interceptors after launch.

That would shift part of Ukraine’s defense from interception to what military analysts often describe as a “left-of-launch” approach: find and disable the source of the attack before a missile is in the air. The proposal was not described as a replacement for air defense, but as an additional way to reduce the number of threats Ukrainian systems would have to engage.

What Starlink would add to the drones

Starlink’s relevance was its communications role. Satellite connectivity could help operators maintain control of drones over much greater distances than many conventional links, including during missions that crossed into Russian territory. Reuters reported that Ukrainian drone commanders and pilots already use Starlink-linked systems in mid-strike operations, while Russian forces have installed powerful electronic-warfare equipment to interfere with those connections.

This does not make the drones immune to disruption. The reported Russian jamming effort shows that Starlink is part of an ongoing electronic-warfare contest, not a guaranteed solution. The requested authorization therefore concerned both geographic coverage and permission to use the network for a particularly sensitive military mission.

The roles of Zelenskyy, Trump, Musk and Fedorov

• Volodymyr Zelenskyy: Put the proposal to Trump and sought U.S. help in obtaining permission to use Starlink for drone strikes inside Russia.
• Donald Trump: Was asked to speak with Musk. Accounts of the meeting said Trump was noncommittal or promised only to consider the request, without offering a specific commitment.
• Elon Musk and SpaceX: Controlled the Starlink access decision. Previous reporting has shown that SpaceX can restrict or deactivate service in particular areas, making the proposal dependent on company-controlled geographic and usage rules.
• Mykhailo Fedorov: The former Ukrainian defense minister remained in contact with Musk about using Starlink to counter Russian ballistic-missile systems. Fedorov said in August that the discussions were continuing but that reaching the desired outcome remained difficult.

Fedorov had also previously sought restrictions on Russian use of Starlink. Ukrainian officials said the deactivation of Russian-linked terminals disrupted Russian assault operations, underscoring why access controls mattered to both sides.

What is known about the outcome

There was no confirmed approval in the provided reporting. The accounts are not fully consistent: some August reports said Musk had refused the request, while later coverage described Ukraine as still seeking approval or said there was “no positive decision.” The clearest conclusion is that Starlink access for the proposed deep strikes had not been confirmed.

That uncertainty is strategically important. Because SpaceX controls where and how Starlink service operates, Ukraine could not treat possession of compatible drones as sufficient. The network’s availability, its rules of use and its exposure to Russian jamming all remained constraints.

The strategic idea in one sentence

Kyiv was asking to use a privately controlled satellite network to help destroy Russian missile launchers and their support systems before attacks occurred—an effort to conserve scarce Patriot interceptors and add a proactive layer to Ukraine’s missile defense, not a confirmed new strike capability.

What Ukraine proposed

The request was broader than permission to fly drones. Kyiv wanted Starlink connectivity to remain available as long-range drones crossed into Russia, allowing operators to guide the aircraft toward missile launchers and the systems that support them. The reported target set included launch infrastructure, command centers and other military assets.

The proposed operating area extended as far as 200 km from Ukraine’s internationally recognized border. Reports identified Bryansk, Kursk, Belgorod, Voronezh, Rostov-on-Don and Krasnodar among the major Russian cities within the described zone.

Why Kyiv was pursuing the plan

Ukraine’s immediate concern was the availability of Patriot interceptor missiles, which it relies on to defend against Russian ballistic-missile attacks. Kyiv presented Starlink-enabled drone operations as a way to reduce that dependence by attacking missile launch systems before they could fire, rather than relying only on interceptors after launch.

That would shift part of Ukraine’s defense from interception to what military analysts often describe as a “left-of-launch” approach: find and disable the source of the attack before a missile is in the air. The proposal was not described as a replacement for air defense, but as an additional way to reduce the number of threats Ukrainian systems would have to engage.

What Starlink would add to the drones

Starlink’s relevance was its communications role. Satellite connectivity could help operators maintain control of drones over much greater distances than many conventional links, including during missions that crossed into Russian territory. Reuters reported that Ukrainian drone commanders and pilots already use Starlink-linked systems in mid-strike operations, while Russian forces have installed powerful electronic-warfare equipment to interfere with those connections.

This does not make the drones immune to disruption. The reported Russian jamming effort shows that Starlink is part of an ongoing electronic-warfare contest, not a guaranteed solution. The requested authorization therefore concerned both geographic coverage and permission to use the network for a particularly sensitive military mission.

The roles of Zelenskyy, Trump, Musk and Fedorov

• Volodymyr Zelenskyy: Put the proposal to Trump and sought U.S. help in obtaining permission to use Starlink for drone strikes inside Russia.
• Donald Trump: Was asked to speak with Musk. Accounts of the meeting said Trump was noncommittal or promised only to consider the request, without offering a specific commitment.
• Elon Musk and SpaceX: Controlled the Starlink access decision. Previous reporting has shown that SpaceX can restrict or deactivate service in particular areas, making the proposal dependent on company-controlled geographic and usage rules.
• Mykhailo Fedorov: The former Ukrainian defense minister remained in contact with Musk about using Starlink to counter Russian ballistic-missile systems. Fedorov said in August that the discussions were continuing but that reaching the desired outcome remained difficult.

Fedorov had also previously sought restrictions on Russian use of Starlink. Ukrainian officials said the deactivation of Russian-linked terminals disrupted Russian assault operations, underscoring why access controls mattered to both sides.

What is known about the outcome

There was no confirmed approval in the provided reporting. The accounts are not fully consistent: some August reports said Musk had refused the request, while later coverage described Ukraine as still seeking approval or said there was “no positive decision.” The clearest conclusion is that Starlink access for the proposed deep strikes had not been confirmed.

That uncertainty is strategically important. Because SpaceX controls where and how Starlink service operates, Ukraine could not treat possession of compatible drones as sufficient. The network’s availability, its rules of use and its exposure to Russian jamming all remained constraints.

The strategic idea in one sentence

Kyiv was asking to use a privately controlled satellite network to help destroy Russian missile launchers and their support systems before attacks occurred—an effort to conserve scarce Patriot interceptors and add a proactive layer to Ukraine’s missile defense, not a confirmed new strike capability.