Recommended Posts

In a secret project recently discovered, the United States planned to blow up the moon with a nuclear bomb in the 1950s as a display of the country?s strength during the Cold War space race.

The secret project, called ?A Study of Lunar Research Flights?, as well as ?Project A119? was never carried out but initially intended to intimidate the Soviet Union after their launch of the first artificial satellite, Sputnik 1, which demonstrated their technological power, the Daily Mail reports.

The sight of a magnificent nuclear flash from Earth was meant to terrify the Soviet Union and boost US confidence, physicist Leonard Reiffel, 85, told the Associated Press. The nuclear device would have been launched from a missile from an unknown location. It would have ignited upon impact with the moon, causing a massive explosion that was visible from Earth.

th?id=I.4601177794217335&pid=15.1&W=160&H=150

The detonation would have been the result of an atom bomb, since a hydrogen bomb was too heavy for a missile to carry the 238,000 miles to the moon.

Astronomer Carl Sagan was responsible for some of the calculations that could cause the nuclear detonation. Sagan, who later became a famous author of popular science, was a young graduate student at the time. He worked as a NASA advisor from the 1950s onward and died in 1996.

One of Sagan?s biographers claims he may have committed a security breach by revealing the classified project in 1959 in his application for an academic fellowship. Reiffel, who once served as deputy director at NASA and was responsible for the nuclear research at the Armour Research Foundation in 1958, confirmed this claim.

In his interview with AP, which took place in the year 2000, Reiffel said the nuclear detonation could have occurred by 1959, which is when the US Air Force deployed intercontinental ballistic missiles. The project documents were kept secret for nearly 45 years and the US government has never formally confirmed its involvement in the study.

But in the end, the mission was abandoned due to safety concerns about the radioactive material that would contaminate space. The scientists were also worried about the bomb detonating prematurely, thereby endangering the people on Earth.

Rather than blow up the moon, the US continued the space race, sending its first satellite, Explorer 1, into orbit on Jan. 31, 1958. The project was officially canceled by the Air Force in Jan. 1959, and the US instead focused on sending a man to the moon.

source

Link to comment
https://www.neowin.net/forum/topic/1122898-usa-planned-to-nuke-the-moon/
Share on other sites

Would have been darkly amusing, if the Moon had broke apart, and big chunks hit Earth. :shifty:

What would have been amusing if the explosion had changed the orbit of the moon, just enough that over the years its created what we think of as global warming. We already know the moon accounts for things like tide and that controls a lot of the earths continental drift's thermodynamics, it'd be funny if it all turned out that the moon landing caused the changes in weather on earth, killing us humans off in less then 200 years. right?

The Daily Mail...yeah. BLOW UP THE MOON to scare the USSR? Sure....Hum you need new meds, I can share :rofl:

Ever think to do some Searching before you make instant judgements ?

http://en.wikipedia....ki/Project_A119

http://www.smh.com.a...1128-2aejm.html

Physicist Leonard Reiffel, who was involved with the project, said it would have intimidated the Soviet Union and given the US a morale boost after the Russians successfully launched Sputnik in 1957. Reiffel went on to serve as deputy director at NASA.

Like the revelation this week that Project A119, otherwise known as ''A Study of Lunar Research Flights'', actually existed, and actually got a fair way down the path to implementation. Various respectable news agencies are reporting the great science nerd Carl Sagan, a young science nerd at the time, was involved in the calculations regarding winds, and the projected distribution of dust and gas after the blast.

Leonard Reiffel

Dr. Len Reiffel currently heads three Chicago-based start-ups--Exelar Medical Corporation (www.exelarmedical.com), Luxelar Corporation (www.luxelar.com) and Iron Mount Corporation. His previous entrepreneurial activities have included both privately financed ventures as well as taking one of his companies (Interand Corp.) through the full gamut of development stages to a successful IPO.

Len is a widely-recognized scientist, educator and technical administrator as well as an inventor/entrepreneur. As Deputy Director of NASA's Apollo Program Office (1965-1969), he was the Headquarters executive responsible for all manned lunar experiments and support equipment. He was also the NASA Headquarters person overseeing the lunar landing-site selection process, scientific aspects of astronaut activities, both in-flight and on the lunar surface, and matters of astronaut safety involving a science component such as solar-flare hazards, bio-contamination, lunar surface reactivity and many other such topics. Reiffel also served for several years as the Technical Director of the Interagency Manned Space Flight Experiments Board (NASA, DOD, USAF etc.). While carrying out his NASA responsibilities, Dr. Reiffel concurrently was science consultant and on-air Science Commentator for the CBS Network.

Still waiting on the denials from Carl Sagan's family, and the expected lawsuit ....

post-37120-0-45017000-1354480037.png

They wheren't blowing up the moon FFS. They where detonating an atom bomb on the moons surface to demonstrate technological superiority. It would just have resulted an a somewhat spectacular and very short lightshow.

And even then, sending a missile to the moon wouldn't really have impressed anyone at this point.

As for blowing up. Since the moon has no atmosphere, a nuke would have done very limited damage, especially a surface detonation.

There's a big difference between blowing up the moon and detonating an atomic bomb on the moon. In one of these scenarios, the moon is destroyed; that is not the scenario that would have ensued had this plan been executed.

You never know -- the Moon is very old -- it might have cracked up into several big asteroid-sized pieces, and came floating to Earth ...

This topic is now closed to further replies.
  • Posts

    • Display Driver Uninstaller (DDU) 18.1.5.5 by Razvan Serea Display Driver Uninstaller (DDU) is a utility for completely removing AMD/NVIDIA/INTEL graphics drivers and related packages from your system, attempting to eliminate all leftovers (including registry entries, folders and files, driver store). Though AMD/NVIDIA/INTEL drivers can usually be removed via the Windows Control Panel, this uninstaller tool was created for situations where standard uninstall fails, or when you need to fully remove NVIDIA or ATI graphics card drivers. After using this driver cleaner, your system will behave as though it’s the first time you’re installing a new driver—similar to a fresh Windows installation. As with all such tools, we recommend creating a restore point beforehand, allowing you to undo changes if issues arise. If you're having trouble installing an older or newer driver, try it—there are reports that it resolves such problems. Recommended usage: The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best. Make a backup or a system restore (but it should normally be pretty safe). It is best to exclude the DDU folder completely from any security software to avoid issues. You do NOT need to uninstall the driver prior using DDU. Requirements: .NET Framework 4.8 Compatible with Windows 7, 8, 8.1, 10, and 11 (32-bit or 64-bit) Note: Using on Insider Preview builds is at your own risk. Display Driver Uninstaller (DDU) 18.1.5.5 changelog: Added 'Reset to recommended' button for the Options. General fixes and improvements. Download: Display Driver Uninstaller (DDU) 18.1.5.5 | 1.7 MB (Freeware) Download: DDU Portable | 1.2 MB Links: Display Driver Uninstaller Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • WACUP 1.99.51.24568 Preview by Razvan Serea WACUP (WinAmp Community Update Project) is a modern, enhanced version of the classic Winamp music player, designed for better stability, performance, and compatibility. Built for Windows, WACUP retains the familiar Winamp interface while adding 64-bit support, bug fixes, and new features like improved audio format support, customizable skins, and optimized playlist management. Unlike bloated alternatives, WACUP focuses on lightweight performance and regular updates, making it the best choice for fans of the classic Winamp experience. Basically, if you miss the good old days of Winamp and want a modern upgrade that doesn’t mess things up, WACUP is for you! WACUP key features: Classic Winamp Feel – Keeps the familiar interface and functionality. Bug Fixes & Stability – Fixes old Winamp issues and improves performance. 64-Bit Support – Works better on modern systems. More Formats & Plugins – Supports additional audio formats and third-party plugins. Customizable UI – Skins and tweaks for a personalized look. Better Library Management – Improved playlists, media organization, and search. No Bloat – Focuses on performance without unnecessary extras. Regular Updates – Community-driven development with new features and fixes. WACUP 1.99.51.24568 Preview changelog: Fixed a deadlock seen from the recent crash reports when doing some of the drag + drop actions within the media library window Fixed a loading crash seen related to a problem with some of the artwork cache image files being restored which should now be better handled allowing for the bad image to be removed without it failing Fixed a deadlock seen from the recent crash reports when the internal metadata cache clearing is triggered which could block the main ui thread for too long with this now being moved to a background thread Fixed some performance issues with some of the methods related to determining artwork support which mainly affected the local library import / refresh (this is still slower for some compared to other players because there's more data & artwork aspects being checked for which means doing more processing on a single file despite the best of attempts to reduce duplicate / heavy processing where possible) Fixed a crash with the JTFE based missing files hotkey which no one seems to have used for an age for this to appear (maybe it's time to seriously consider stripping out features that aren't being used) Fixed how some of the file types which use extra information to reference their sub-songs is handled which was preventing some from being correctly resolved back to their base file (noticed fixing above) Fixed an issue with the handling of files with underscores in their filepath which wasn't being correctly handled causing some of the filename to be lost when shown as the title if title reading is delayed Fixed a few things that might be behind NotSoDirect not being stable for some setups though am still not certain that the changes done for this are going to fully resolve the problem from the crash reports Fixed the OS toast handling when there's no prior shortcut in the OS start menu to now create the shortcut (needed to allow the yes/no buttons for the new build / post-release toast) to be done as a hidden one so it's less likely to cause annoyance for those not wanting to see it whilst still allowing this less than ideal OS api implementation requirement to be met to avoid toasts without the needed buttons Fixed a regression when moving from taglib1 to taglib2 which broke some of the handling in place to allow for external programs to still access files when wacup has a held open cached instance of the file Everything else Updated cppwinrt (gen_win10shell.dll) to 3.0.260520.1 (26 May 2026) Updated libcurl (libcurl.dll) to 8.2.1 (24 Jun 2026) Updated Monkey's Audio (in_ape.dll) to 13.15 (28 Jun 2026) Updated mpg123 (mpg123.dll) to 1.33.6 (6 Jun 2026) Updated OpenSSL (libcurl.dll) to 3.5.7 (9 Jun 2026) Updated pugixml to 1.16 (16 Jun 2026) Updated taglib (tag2.dll) to 2.3.0 (11 May 2026) Updated vgmstream (in_vgmstream.dll) to the latest Git commit from 28 Jun 2026 Download: WACUP 64-bit | 9.6 MB (Freeware) Download: WACUP 32-bit View: WACUP Website | Screenshots Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • "over a thousand engineering hours" and started selling it but could not take a couple of minuets to send an AI email to ask permission. What an expensive lesson.
    • just tested it yesterday, a simple page with autoloading ADS takes 60mb....just 1 page for 60 megabytes.   poor people with a limited internet never will visit neolose
    • Tor Browser 15.0.17 by Razvan Serea Protect your privacy. Defend yourself against network surveillance and traffic analysis. Tor is a network of virtual tunnels that allows people and groups to improve their privacy and security on the Internet. The Tor software protects you by bouncing your communications around a distributed network of relays run by volunteers all around the world: it prevents somebody from watching your Internet connection and learning what sites you visit, it prevents the sites you visit from learning your physical location, and it lets you access sites which are blocked. The Tor Browser Bundle lets you use Tor on Windows, Mac OS X, or Linux without needing to install any software. It can run off a USB flash drive, comes with a pre-configured web browser to protect your anonymity, and is self-contained. Tor Browser 15.0.17 changelog: All Platforms Updated Tor to 0.4.9.11 Updated NoScript to 13.6.25.1984 Build System / All Platforms Bug tor-browser-build#41821: Update gpg subkeys for boklm Bug tor-browser-build#41827: Update morgan's keychain with renewed key Download: Tor Browser (64-bit) | Tor Browser (32-bit) | 109.0 MB (Open Source) View: Tor Browser Website | Other Operating Systems Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
    • Apprentice
      jahara21 went up a rank
      Apprentice
    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
    • Week One Done
      NovaEdgeX earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      526
    2. 2
      +Edouard
      265
    3. 3
      PsYcHoKiLLa
      146
    4. 4
      Steven P.
      99
    5. 5
      macoman
      55
  • Tell a friend

    Love Neowin? Tell a friend!