Posts belonging to Category NSWC Dahlgren



Sci-Fi Nerd Alert: Railgun tested at Dahlgren

From the AP via NBC4: Navy Puts ‘Railgun’ To Test In Va. Trial:

A futuristic weapon getting a trial run by the Navy demonstrated its destructive power at the Naval Surface Warfare Center in Dahlgren.

In the demonstration Thursday, engineers fired the electromagnetic railgun at what they said was a record power level: 10 megajoules.

Current Navy guns generate about 9 megajoules of muzzle energy.

Railguns use electromagnetic energy to launch projectiles long distances — more than 200 nautical miles.

Because the railgun uses electricity and not gunpowder to fire projectiles, it eliminates the possibility of explosions on ships.

The Navy hopes the railgun will eventually replace the standard 5-inch gun on its ships. The weapon isn’t expected to be deployed until at least 2020.

UPDATE #3: From the AP via FOXNews: Navy Tests High-Powered Electromagnetic Railgun:

[A joule is defined as the energy needed to produce one watt of electricity for one second.

The railgun tested Thursday actually has a capacity of 32 megajoules, but the Navy is slowly building up the energy level in a series of tests.

That’s a lot of power, but with a new series of electrically-powered ships coming on line, the Navy figures generating capacity will not be a problem.

According to the Navy, the railgun, when fully developed, will be able to launch solid projectiles at Mach 5, or about 3,700 mph.]

(H/t: Ace of Spades HQ) (one of the funniest blogs out there) for the FOXNews story.

UPDATE: Some video from Future Weapons (April 9, 2007) off of the Discovery Channel:

[youtube=http://www.youtube.com/watch?v=4OqlTXwLG40]

UPDATE #2: Some extended unclassified test footage from NSWC Dahlgren:

[youtube=http://www.youtube.com/watch?v=y54aLcC3G74]


Warning: Unknown: open(/home/content/36/5675336/tmp/sess_b8sfmj22tgitqp3lprp7ansas3, O_RDWR) failed: No such file or directory (2) in Unknown on line 0

Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct () in Unknown on line 0