Hubble Shows MilkyWay unavoidable Collision with Andromeda Galaxy


Recommended Posts

nasa.jpg

NASA astronomers announced Thursday they can now predict with certainty the next major cosmic event to affect our galaxy, Sun, and solar system: the titanic collision of our Milky Way galaxy with the neighboring Andromeda galaxy.

The Milky Way is destined to get a major makeover during the encounter, which is predicted to happen four billion years from now. It is likely the Sun will be flung into a new region of our galaxy, but our Earth and solar system are in no danger of being destroyed.

"Our findings are statistically consistent with a head-on collision between the Andromeda galaxy and our Milky Way galaxy," said Roeland van der Marel of the Space Telescope Science Institute (STScI) in Baltimore.

The solution came through painstaking NASA Hubble Space Telescope measurements of the motion of Andromeda, which also is known as M31. The galaxy is now 2.5 million light-years away, but it is inexorably falling toward the Milky Way under the mutual pull of gravity between the two galaxies and the invisible dark matter that surrounds them both.

"After nearly a century of speculation about the future destiny of Andromeda and our Milky Way, we at last have a clear picture of how events will unfold over the coming billions of years," said Sangmo Tony Sohn of STScI.

The scenario is like a baseball batter watching an oncoming fastball. Although Andromeda is approaching us more than two thousand times faster, it will take four billion years before the strike.

Computer simulations derived from Hubble's data show that it will take an additional two billion years after the encounter for the interacting galaxies to completely merge under the tug of gravity and reshape into a single elliptical galaxy similar to the kind commonly seen in the local universe.

Although the galaxies will plow into each other, stars inside each galaxy are so far apart that they will not collide with other stars during the encounter. However, the stars will be thrown into different orbits around the new galactic center. Simulations show that our solar system will probably be tossed much farther from the galactic core than it is today.

To make matters more complicated, M31's small companion, the Triangulum galaxy, M33, will join in the collision and perhaps later merge with the M31/Milky Way pair. There is a small chance that M33 will hit the Milky Way first.

The universe is expanding and accelerating, and collisions between galaxies in close proximity to each other still happen because they are bound by the gravity of the dark matter surrounding them. The Hubble Space Telescope's deep views of the universe show such encounters between galaxies were more common in the past when the universe was smaller.

A century ago astronomers did not realize that M31 was a separate galaxy far beyond the stars of the Milky Way. Edwin Hubble measured its vast distance by uncovering a variable star that served as a "milepost marker."

Edwin Hubble went on to discover the expanding universe where galaxies are rushing away from us, but it has long been known that M31 is moving toward the Milky Way at about 250,000 miles per hour. That is fast enough to travel from here to the Moon in one hour. The measurement was made using the Doppler Effect, which is a change in frequency and wavelength of waves produced by a moving source relative to an observer, to measure how starlight in the galaxy has been compressed by Andromeda's motion toward us.

Previously, it was unknown whether the far-future encounter will be a miss, glancing blow, or head-on smashup. This depends on M31's tangential motion. Until now, astronomers have not been able to measure M31's sideways motion in the sky, despite attempts dating back more than a century. The Hubble Space Telescope team, led by van der Marel, conducted extraordinarily precise observations of the sideways motion of M31 that remove any doubt that it is destined to collide and merge with the Milky Way.

"This was accomplished by repeatedly observing select regions of the galaxy over a five- to seven-year period," said Jay Anderson of STScI.

"In the 'worst-case-scenario' simulation, M31 slams into the Milky Way head-on and the stars are all scattered into different orbits," said team member Gurtina Besla of Columbia University in New York, N.Y. "The stellar populations of both galaxies are jostled, and the Milky Way loses its flattened pancake shape with most of the stars on nearly circular orbits. The galaxies' cores merge, and the stars settle into randomized orbits to create an elliptical-shaped galaxy."

The space shuttle servicing missions to Hubble upgraded it with ever more-powerful cameras, which have given astronomers a long-enough time baseline to make the critical measurements needed to nail down M31's motion. The Hubble observations and the consequences of the merger are reported in three papers that will appear in an upcoming issue of the Astrophysical Journal.

The science team that did the investigation is led by Principal Investigator R.P. van der Marel (Space Telescope Science Institute [sTScI], Baltimore, Md.), and further consists of S.T. Sohn and J. Anderson (STScI), G. Besla (Columbia University, New York, N.Y.), M. Fardal (University of Massachusetts, Amherst, Mass.), R.L. Beaton (University of Virginia, Charlottesville, Va.), Thomas M. Brown (STScI), P. Guhathakurta (UCO/Lick Observatory, University of California, Santa Cruz, Calif.), and T.J. Cox (Carnegie Observatories, Pasadena, Calif).

http://hubblesite.org/newscenter/archive/releases/2012/20/full/

It's a shame I'm not going to be alive to witness any of this because by all accounts it's going to be spectacular.

And really, some people seem to be under the impression that it's going to mean certain doom for organic life, which isn't necessarily true. Apart from the fact that the stars in galaxies are so widely spaced apart making a collision unlikely, the general consensus is that the position of the sun and solar system may shift compared to the rest of the galaxy the chances are the actual impact on the solar system won't be that big.

Estimates of the sun's remaining lifespan range from 5-7 billion years so it's still possible there may be some life left on earth when this event starts to occur but whether humans will still be here remains to be seen. Nonetheless still pretty cool and interesting

Doesn't matter, the Reapers will wipe us out before then.

:laugh:

^ Why are you not planning to be alive ? ;)

Unfortunately, death isn't something I can mitigate with planning. I could extend my life by eating healthy and exercising but I still think 4 billion years is a bit of a stretch :p

Doesn't matter, the Reapers will wipe us out before then.

We should immediately go back to caves, licking our own eyes (trying to, whatsoever) and eating flies, so perhaps the reaptards won't trouble us until we quit doing so.

Stupid telomeres, though... safeguard against cancer that leads to cell death, anyway. Dumbass circular logic! Living forever isn't quite what it used to be, but human lifetime indeed seems too short to me.

Well ... that or a Stargate ... quick, lets move to Egypt ... clearly if we get the pyramyids to work, we'll travel the stars in a Destiny like ship (hell the Enterprise will be build before that, so i think we'll be safe no matter what)

I'm not going to wait around for it to happen, I've got better things to do. Like install Windows 180,756,465,5764,465,576, service pack 75,648,493. Hey look, they finnaly brought Aero back!

  • Like 3

Damn it Apple! iCal won't let me make a new appointment for June 1, 4.000.002.012? :crazy:

Be wary, even if it one day lets you do so, you could just oversleep it :shiftyninja:

https://www.neowin.net/news/alarm-clock-bug-hits-iphones-ipads-and-ipods (etc.)

uh...didn't we already know this? I'm pretty sure I read a long, long time ago that scientists already extrapolated the two galaxy's trajectories and found out they will collide eventually. Did I miss something?

uh...didn't we already know this? I'm pretty sure I read a long, long time ago that scientists already extrapolated the two galaxy's trajectories and found out they will collide eventually. Did I miss something?

From what I'm gathering, whilst it's been suggested for a while that the 2 had a chance of colliding, I think this is the first time that scientists have managed to get a clearer extrapolation of the dynamics of what will happen when they do. I like Hubble simply because it takes some stunning pictures but things like this always hold an interest for me.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
  • Recent Achievements

    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      70
  • Tell a friend

    Love Neowin? Tell a friend!