Skip to main contentSkip to navigationSkip to navigation
The Soyuz-2.1b rocket carrying Russia’s Meteor-M 2-1 weather satellite and other equipment lifts off from the launch pad at the Vostochny cosmodrome
A Soyuz-2.1b rocket carrying Russia’s Meteor-M 2-1 weather satellite and other equipment lifts off at the Vostochny cosmodrome. Photograph: Kirill Kudryavtsev/AFP/Getty Images
A Soyuz-2.1b rocket carrying Russia’s Meteor-M 2-1 weather satellite and other equipment lifts off at the Vostochny cosmodrome. Photograph: Kirill Kudryavtsev/AFP/Getty Images

Russian satellite lost after being set to launch from wrong spaceport

This article is more than 6 years old

Deputy prime minister admits programmers gave the $45m device coordinates for Baikonur rather than Vostochny cosmodrome

Russian deputy prime minister Dmitry Rogozin said on Wednesday the loss of a 2.6bn-rouble ($45m) satellite launched last month was due to an embarrassing programming error.

Russian space agency Roscosmos said last month it had lost contact with the newly launched weather satellite – the Meteor-M – after it blasted off from Russia’s new Vostochny cosmodrome in the country’s far east.

Speaking to Rossiya 24 state TV channel, Rogozin said the failure had been caused by human error. The rocket carrying the satellites had been programmed with the wrong coordinates, he said, saying it had been given bearings for take-off from a different cosmodrome – Baikonur – which Moscow leases from Kazakhstan.

“The rocket was really programmed as if it was taking off from Baikonur,” said Rogozin. “They didn’t get the coordinates right.”

The rocket was carrying 18 smaller satellites belonging to scientific, research and commercial companies from Russia, Norway, Sweden, the US, Japan, Canada and Germany.

The Vostochny spaceport, laid out in the thick taiga forest of the Amur region, is the first civilian rocket launch site in Russia.

In April last year, after delays and massive costs overruns, Russia launched its first rocket from Vostochny, a day after a technical glitch forced an embarrassing postponement of the event in the presence of the president, Vladimir Putin.

Comments (…)

Sign in or create your Guardian account to join the discussion

Most viewed

Most viewed