Language Selection

English French German Italian Portuguese Spanish

Robotic aid arrives in rush to rescue 7 from Russian sub

Filed under
Sci/Tech

U.S. and British planes carrying robotic undersea vehicles landed in Russia's far east Saturday to help rescue seven sailors trapped in a mini-submarine 600 feet below the Pacific.

Both the U.S. Navy and Britain's military sent so-called Super Scorpios, and workers labored to deploy the vehicles as concerns rose over how much oxygen remained for the seven trapped men.

The Scorpios and their equipment will have to be loaded aboard a vessel and taken to the stricken mini-sub's location.

Moscow asked for outside assistance within hours of news breaking about the sub's plight--a speedy request that was a marked change since the Kursk nuclear submarine disaster in 2000, when Russian officials waited until hope was all but exhausted. All 118 died aboard the Kursk.

The mini-sub snagged on an underwater antenna on Thursday and was the subject of desperate rescue efforts and widely varying estimates of how much oxygen remained on board.

The commander of the Russian Pacific Fleet, Adm. Viktor Fyodorov, said early Saturday that there was oxygen for "at least 18 hours," a distinctly less optimistic statement than his earlier assertion that the air would last into Monday. Later Saturday, however, news agencies quoted him as saying there was air for "more than 24 hours."

The confusion over the air supply darkly echoed the sinking of the Kursk almost exactly five years ago. That disaster shocked Russians and deeply embarrassed the country by demonstrating how Russia's once-mighty navy had deteriorated as funding dried up following the 1991 Soviet collapse.

The new crisis is also highly embarrassing for Russia, which will hold an unprecedented joint military exercise with China later this month, including the use of submarines to settle an imaginary conflict in a foreign land. In the exercise, Russia is to field a naval squadron and 17 long-haul aircraft.

No comment from Putin

Navy spokesman Capt. Igor Dygalo told The Associated Press that rescuers had managed to move the sub about 60 yards toward shore with the help of a Russian remote vehicle that was transmitting pictures. Fyodotov, however, was quoted by Russian news agencies as saying that the process was taking too long and rescuers would try to attach a tow line.

The rescue effort underscores that promises by President Vladimir Putin to improve the navy's equipment have apparently had little effect. Authorities initially said a mini-sub would be sent to try to aid the stranded one, but the navy later said it was not equipped to go that deep.

Putin was criticized for his slow response to the Kursk crisis and reluctance to accept foreign assistance. By early Saturday, Putin had made no public comment on the latest sinking.

Too deep to escape

The sailors were in contact with authorities and were not hurt initially, Pacific Fleet spokesman Capt. Alexander Kosolapov said. Their mini-submarine was trapped in Beryozovaya Bay, about 45 miles south of Petropavlovsk-Kamchatsky, the capital of the peninsular region in Russia's far east.

The mini-sub, which became disabled after it was launched from a ship in a combat training exercise, was too deep to allow the sailors to swim to the surface on their own or for divers to reach it, Russian officials said.

Although the Russian navy reportedly ended its deep-sea diving training programs a decade ago because of funding shortages, it does have a device called the Kolokolchik, essentially an updated diving bell, that can be used for some underwater rescues.

However, the mini-sub lies so deep that the device apparently would be useless.

U.S. divers, presumably with better equipment, rushed to the scene to help if necessary. In Belle Chasse, La., a marine services company sent sophisticated deep sea diving suits and a diving crew on board a military plane.

The Japanese ships were not expected to arrive until early next week.

Tangled up in `coastal object'

Dygalo, the navy spokesman, initially said on state-run Rossiya Television that the sub got trapped when its propeller became entangled in a fishing net Thursday. But Fyodorov later said the sub was stuck on an antenna, and Dygalo described the antenna as a "Pacific Fleet coastal infrastructure object."

The trapped AS-28, which looks like a small submarine, was built in 1989. It is about 44 feet long and more than 18 feet high. A vessel of the same type was used in the rescue efforts that followed the Kursk disaster.

Since Soviet times, the Kamchatka Peninsula has housed several major submarine bases and numerous other military facilities, and large areas of it remain closed to outsiders.

Despite strong criticism for Putin's response to the Kursk disaster, he was re-elected in 2004 and his supporters command an overwhelming majority in parliament, making the political fallout of the latest sinking likely minimal.

By Vladimir Isachenkov
Associated Press

More in Tux Machines

Linux 4.18 RC2 Released From China

  • Linux 4.18-rc2
    Another week, another -rc. I'm still traveling - now in China - but at least I'm doing this rc Sunday _evening_ local time rather than _morning_. And next rc I'll be back home and over rmy jetlag (knock wood) so everything should be back to the traditional schedule. Anyway, it's early in the rc series yet, but things look fairly normal. About a third of the patch is drivers (drm and s390 stand out, but here's networking and block updates too, and misc noise all over). We also had some of the core dma files move from drivers/base/dma-* (and lib/dma-*) to kernel/dma/*. We sometimes do code movement (and other "renaming" things) after the merge window simply because it tends to be less disruptive that way. Another 20% is under "tools" - mainly due to some selftest updates for rseq, but there's some turbostat and perf tooling work too. We also had some noticeable filesystem updates, particularly to cifs. I'm going to point those out, because some of them probably shouldn't have been in rc2. They were "fixes" not in the "regressions" sense, but in the "missing features" sense. So please, people, the "fixes" during the rc series really should be things that are _regressions_. If it used to work, and it no longer does, then fixing that is a good and proper fix. Or if something oopses or has a security implication, then the fix for that is a real fix. But if it's something that has never worked, even if it "fixes" some behavior, then it's new development, and that should come in during the merge window. Just because you think it's a "fix" doesn't mean that it really is one, at least in the "during the rc series" sense. Anyway, with that small rant out of the way, the rest is mostly arch updates (x86, powerpc, arm64, mips), and core networking. Go forth and test. Things look fairly sane, it's not really all that scary. Shortlog appended for people who want to scan through what changed. Linus
  • Linux 4.18-rc2 Released With A Normal Week's Worth Of Changes
    Due to traveling in China, Linus Torvalds has released the Linux 4.18-rc2 kernel a half-day ahead of schedule, but overall things are looking good for Linux 4.18.

A GTK+ 3 update

  • A GTK+ 3 update
    When we started development towards GTK+ 4, we laid out a plan that said GTK+ 3.22 would be the final, stable branch of GTK+ 3. And we’ve stuck to this for a while. I has served us reasonably well — GTK+ 3 stopped changing in drastic ways, which was well-received, and we are finally seeing applications moving from GTK+ 2.
  • GTK+ 3.24 To Deliver Some New Features While Waiting For GTK4
    While the GNOME tool-kit developers have been hard at work on GTK4 roughly the past two years and have kept GTK3 frozen at GTK+ 3.22, a GTK+ 3.24 release is now being worked on to deliver some new features until GTK+ 4.0 is ready to be released. While GTK+ 4.0 is shaping up well and GTK+ 3.22 was planned to be the last GTK3 stable release, the developers have had second thoughts due to GTK+ 4 taking time to mature. Some limited new features are being offered up in the GTK+ 3.24 release to debut this September.

Finally: First stable release of KBibTeX for KDE Frameworks 5

After almost exactly two years of being work-in-progress, the first stable release of KBibTeX for KDE Frameworks 5 has been published! You can grab the sources at your local KDE mirror. Some distributions like ArchLinux already ship binary packages. After one beta and one release candidate, now comes the final release. You may wonder why this release gets version number 0.8.1 but not 0.8 as expected. This is simply due to the fact that I noticed a bug in CMakeLists.txt when computing version numbers which did not work if the version number just had two fields, i. e. no ‘patch’ version. As the code and the tag of 0.8 was already pushed, I had no alternative than to fix the problem and increase the version number. Otherwise, the ChangeLog (alternative view) is virtually unchanged compared to the last pre-release. Read more

Today in Techrights