Buntar Aerospace has implemented Remote Control, a feature of the Buntar Copilot platform that allows for full remote control of the Buntar-3 strike drone during combat missions.
Buntar Aerospace has implemented Remote Control, a feature of the Buntar Copilot platform that allows for full remote control of the Buntar-3 strike drone during combat missions.
The company announced this on LinkedIn.
The technical team travels to the launch site, deploys the antenna, laptop, and Starlink terminal, prepares the vehicle for takeoff, launches it, and then leaves the position. This point then acts as a relay station through which the pilot and payload operator can connect to the vehicle from anywhere with Internet access. The technical staff is at the site only as long as necessary to deploy the equipment, launch, land, and deploy — after which the pilot and operator conduct the mission from deep in the rear, hundreds or even thousands of kilometers from the front line.
Unlike typical market solutions that rely on third-party remote access software (remote desktop, screen sharing), Remote Control is built directly into the Buntar Copilot platform. Camera video, aircraft telemetry, antenna telemetry, and log files are transmitted in separate independent streams — according to the company, this increases the reliability of control in combat conditions: if one stream is interrupted, the others continue to work.
Buntar Aerospace co-founder Bohdan Sas explains the logic of the decision with concern for the safety of the military: «We are convinced that the war of the future is a war of technology, where it is the iron that is at risk, not the pilots,» he says, adding that the entire civilized world is moving in the same direction — to remove crews from direct fire, leaving the role of the «brains» of the operation to the operators.
The head of the Buntar Copilot team, who introduced himself as Props, said that there are already several remote control solutions on the market, but the question is how reliably they work in combat conditions: «We deliberately abandoned ready-made remote access solutions in order to make this function right inside Buntar Copilot,» he explains.
Ivan Kaunov from the Buntar team added that the obvious «fast» way — to add a remote desktop on top of the existing software and rely on a single communication channel — was deliberately rejected by the team, as this is the wrong architecture for a product that works under real combat load: in the field, the communication channel is the weakest link in any system, and if video, device telemetry, antenna telemetry and logs are all sent in one stream through the remote screen, one connection failure collapses the entire control system. The solution required more engineering work, but in return the system does not fail completely at once.
