Issue |
A&A
Volume 638, June 2020
|
|
---|---|---|
Article Number | A10 | |
Number of page(s) | 14 | |
Section | Planets and planetary systems | |
DOI | https://doi.org/10.1051/0004-6361/201936929 | |
Published online | 04 June 2020 |
Transit least-squares survey
III. A 1.9 R⊕ transit candidate in the habitable zone of Kepler-160 and a nontransiting planet characterized by transit-timing variations
1
Max Planck Institute for Solar System Research,
Justus-von-Liebig-Weg 3,
37077
Göttingen,
Germany
e-mail: heller@mps.mpg.de
2
Sonneberg Observatory,
Sternwartestraße 32,
96515
Sonneberg,
Germany
e-mail: michael@hippke.org
3
Visiting Scholar, Breakthrough Listen Group, Berkeley SETI Research Center, Astronomy Department,
UC Berkeley,
Berkeley,
USA
4
Institut für Astrophysik, Georg-August-Universität Göttingen,
Friedrich-Hund-Platz 1,
37077
Göttingen,
Germany
e-mail: jfreude@astro.physik.uni-goettingen.de
5
Department of Astronomy & Astrophysics, University of California,
Santa Cruz, 1156 High St.,
Santa Cruz,
CA
95064,
USA
6
NASA Ames Research Center,
Moffett Field,
CA
94901,
USA
Received:
16
October
2019
Accepted:
3
May
2020
The Sun-like star Kepler-160 (KOI-456) has been known to host two transiting planets, Kepler-160 b and c, of which planet c shows substantial transit-timing variations (TTVs). We studied the transit photometry and the TTVs of this system in our search for a suspected third planet. We used the archival Kepler photometry of Kepler-160 to search for additional transiting planets using a combination of our Wōtan detrending algorithm and our transit least-squares detection algorithm. We also used the Mercury N-body gravity code to study the orbital dynamics of the system in trying to explain the observed TTVs of planet c. First, we recovered the known transit series of planets Kepler-160 b and c. Then we found a new transiting candidate with a radius of 1.91−0.14+0.17 Earth radii (R⊕), an orbital period of 378.417−0.025+0.028 d, and Earth-like insolation. The vespa software predicts that this signal has an astrophysical false-positive probability of FPP3 = 1.8 × 10−3 when the multiplicity of the system is taken into account. Kepler vetting diagnostics yield a multiple event statistic of MES = 10.7, which corresponds to an ~85% reliability against false alarms due to instrumental artifacts such as rolling bands. We are also able to explain the observed TTVs of planet c with the presence of a previously unknown planet. The period and mass of this new planet, however, do not match the period and mass of the new transit candidate. Our Markov chain Monte Carlo simulations of the TTVs of Kepler-160 c can be conclusively explained by a new nontransiting planet with a mass between about 1 and 100 Earth masses and an orbital period between about 7 and 50 d. We conclude that Kepler-160 has at least three planets, one of which is the nontransiting planet Kepler-160 d. The expected stellar radial velocity amplitude caused by this new planet ranges between about 1 and 20 m s−1. We also find the super-Earth-sized transiting planet candidate KOI-456.04 in the habitable zone of this system, which could be the fourth planet.
Key words: eclipses / methods: data analysis / planets and satellites: detection / planetary systems / techniques: photometric / planets and satellites: individual: Kepler-160
© R. Heller et al. 2020
Open Access article, published by EDP Sciences, under the terms of the Creative Commons Attribution License (http://creativecommons.org/licenses/by/4.0), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.
Open Access funding provided by Max Planck Society.
Current usage metrics show cumulative count of Article Views (full-text article views including HTML views, PDF and ePub downloads, according to the available data) and Abstracts Views on Vision4Press platform.
Data correspond to usage on the plateform after 2015. The current usage metrics is available 48-96 hours after online publication and is updated daily on week days.
Initial download of the metrics may take a while.