Stay up to date with notifications from The Independent

Notifications can be managed in browser preferences.

Russian radioactivity recorded 986 times higher than usual as toxic cloud sparks nuclear accident rumours

Russian officials had previously denied any knowledge of a nuclear accident – but now the country's meteorological service admits finding traces of an isotope only produced by splitting atoms in a reactor

Harriet Agerholm
Tuesday 21 November 2017 05:37 EST
Comments
Kalininskaya nuclear power plant, around 175 miles northwest of Moscow
Kalininskaya nuclear power plant, around 175 miles northwest of Moscow (REUTERS/Alexander Natruskin)

Your support helps us to tell the story

From reproductive rights to climate change to Big Tech, The Independent is on the ground when the story is developing. Whether it's investigating the financials of Elon Musk's pro-Trump PAC or producing our latest documentary, 'The A Word', which shines a light on the American women fighting for reproductive rights, we know how important it is to parse out the facts from the messaging.

At such a critical moment in US history, we need reporters on the ground. Your donation allows us to keep sending journalists to speak to both sides of the story.

The Independent is trusted by Americans across the entire political spectrum. And unlike many other quality news outlets, we choose not to lock Americans out of our reporting and analysis with paywalls. We believe quality journalism should be available to everyone, paid for by those who can afford it.

Your support makes all the difference.

Russia has said it found "extremely high" concentrations of a radioactive isotope in some parts of the country in September, amid reports of a nuclear accident.

The announcement confirmed findings earlier this month by a French nuclear safety institute, the IRSN, which detected a cloud of radioactivity above Europe.

Russian officials had previously denied any knowledge of a nuclear accident that could have caused the cloud.

In October, state nuclear company Rosatom said at the time of the proposed accident "radiation around all objects of Russian nuclear infrastructure is within the norm and at the level of background radiation”.

But on Monday Russia's meteorological service, Rosgidromet, said “probes of radioactive aerosols from monitoring stations Argayash and Novogorny were found to contain radioisotope Ru-106 [Ruthenium-106]” between 25 September and 1 October.

Ruthenium-106 is a product of splitting atoms in a reactor and does not occur naturally.

The isotope was found in Tatarstan and southern Russia and had reached "all European countries starting in Italy and toward the north of Europe” from 29 September, it said.

The service did not specify where the pollution originated, but a concentration 986 times the natural background level was found at Argayash, a village close to the Russian border with Kazakhstan and around 20 miles from the Mayak nuclear facility.

An explosion at Mayak in 1957 exposed at least 272,000 people to dangerous levels of radiation. Mayak now serves as a site for reprocessing nuclear fuels.

In its report on the nuclear cloud, France's IRSN said the source of the pollution was probably an accident somewhere between the Volga river and the Ural mountains.

It said the levels of pollution were so high that if the accident had happened in France, authorities would have evacuated the site and the surrounding areas. But the organisation said the concentrations measured in Europe did not pose a threat to public health.

The institute said a nuclear reactor could not have been the source of the pollution because other radioactive elements would also have been detected. Instead, it said the pollution could have been discharged from an installation linked to the nuclear fuel cycle.

Join our commenting forum

Join thought-provoking conversations, follow other Independent readers and see their replies

Comments

Thank you for registering

Please refresh the page or navigate to another page on the site to be automatically logged inPlease refresh your browser to be logged in