Journal article
AGN as potential factories for eccentric black hole mergers
- Abstract:
-
There is some weak evidence that the black hole merger named GW190521 had a non-zero eccentricity1,2. In addition, the masses of the component black holes exceeded the limit predicted by stellar evolution3. The large masses can be explained by successive mergers4,5, which may be efficient in gas disks surrounding active galactic nuclei, but it is difficult to maintain an eccentric orbit all the way to the merger, as basic physics would argue for circularization6. Here we show that active galactic nuclei disk environments can lead to an excess of eccentric mergers, if the interactions between single and binary black holes are frequent5 and occur with mutual inclinations of less than a few degrees. We further illustrate that this eccentric population has a different distribution of the inclination between the spin vectors of the black holes and their orbital angular momentum at merger7, referred to as the spin–orbit tilt, compared with the remaining circular mergers.
- Publication status:
- Published
- Peer review status:
- Peer reviewed
Actions
Access Document
- Files:
-
-
(Preview, Accepted manuscript, pdf, 544.6KB, Terms of use)
-
- Publisher copy:
- 10.1038/s41586-021-04333-1
Authors
- Publisher:
- Springer Nature
- Journal:
- Nature More from this journal
- Volume:
- 603
- Issue:
- 7900
- Pages:
- 237-240
- Publication date:
- 2022-03-09
- Acceptance date:
- 2021-12-10
- DOI:
- EISSN:
-
1476-4687
- ISSN:
-
0028-0836
- Pmid:
-
35264755
- Language:
-
English
- Keywords:
- Pubs id:
-
1243593
- Local pid:
-
pubs:1243593
- Deposit date:
-
2023-05-01
Terms of use
- Copyright holder:
- Samsing et al.
- Copyright date:
- 2022
- Rights statement:
- Copyright © 2022, The Author(s), under exclusive licence to Springer Nature Limited
- Notes:
-
This is the accepted manuscript version of the article. The final version is available from Springer Nature at https://doi.org/10.1038/s41586-021-04333-1
If you are the owner of this record, you can report an update to it here: Report update to this record