The European Space Agency's BepiColombo spacecraft successfully separated from its Mercury Transfer Module on September 3, 2026, at 2 p.m. local time in Germany. [1]
BepiColombo, a joint mission of the European Space Agency (ESA) and the Japanese agency JAXA, began its months-long arrival phase at Mercury on Thursday 2026-09-03, after an eight-year journey that began with its 2018 launch from Earth. [2] On 2026-09-03, the two probes of BepiColombo autonomously separated from their transfer module at a velocity of 40 centimeters per second, and a signal confirming the operation's success reached the control center in Darmstadt, Germany, at 1:53 p.m. GMT. [3] A key engine burn is scheduled for November 21 to place the spacecraft into a wide orbit around Mercury. [4]
Engineers responded to the power crisis by redrawing the mission path, cutting back on engine firings, and accepting a later arrival date to keep the spacecraft healthy. [5] The Mercury Transfer Module had carried the spacecraft through deep space since 2018 but faced a crisis when its solar panels began underdelivering power about six years into the flight. [6] From April 2027, ESA's Mercury Planetary Orbiter (MPO) will study the planet's surface at a distance of 480 kilometers (300 miles), while JAXA's Mio orbiter will follow an elliptical orbit extending up to 11,000 kilometers to examine Mercury's space environment and magnetic field. [7]
Ignacio Tanco, ESA's head of inner solar system mission operations, said that with Mercury about 200 million kilometers from Earth, there was a rough 30-minute delay between commands sent and execution, so BepiColombo had to perform the strut cut and separation autonomously. [8]La nave espacial BepiColombo de la Agencia Espacial Europea se separó con éxito de su Módulo de Transferencia a Mercurio el 3 de septiembre de 2026, a las 2 p.m. hora local en Alemania. [1]
BepiColombo, una misión conjunta de la Agencia Espacial Europea (ESA) y la agencia japonesa JAXA, comenzó su fase de llegada a Mercurio, que durará meses, el jueves 2026-09-03, tras un viaje de ocho años que comenzó con su lanzamiento desde la Tierra en 2018. [2] El 2026-09-03, las dos sondas de BepiColombo se separaron autónomamente de su módulo de transferencia a una velocidad de 40 centímetros por segundo, y una señal que confirmaba el éxito de la operación llegó al centro de control en Darmstadt, Alemania, a la 1:53 p.m. GMT. [3] Se tiene programada una maniobra clave de motor para el 21 de noviembre con el fin de colocar la nave en una órbita amplia alrededor de Mercurio. [4]
Los ingenieros respondieron a la crisis de energía rediseñando la trayectoria de la misión, reduciendo las activaciones del motor y aceptando una fecha de llegada posterior para mantener la nave saludable. [5] El Módulo de Transferencia a Mercurio había transportado la nave a través del espacio profundo desde 2018, pero enfrentó una crisis cuando sus paneles solares comenzaron a generar menos energía de la esperada unos seis años después del vuelo. [6] A partir de abril de 2027, el Orbitador Planetario de Mercurio (MPO) de la ESA estudiará la superficie del planeta a una distancia de 480 kilómetros (300 millas), mientras que el orbitador Mio de JAXA seguirá una órbita elíptica que se extiende hasta 11,000 kilómetros para examinar el entorno espacial y el campo magnético de Mercurio. [7]
Ignacio Tanco, jefe de operaciones de misiones del sistema solar interior de la ESA, dijo que con Mercurio a unos 200 millones de kilómetros de la Tierra, había un retraso aproximado de 30 minutos entre los comandos enviados y su ejecución, por lo que BepiColombo tuvo que realizar el corte de los puntales y la separación de forma autónoma. [8]
Proof8 sources · 2 publishers
What this stands on
The European Space Agency's BepiColombo spacecraft successfully separated from its Mercury Transfer Module on September 3, 2026, at 2 p.m. local time in Germany. · Mashable
BepiColombo, a joint mission of the European Space Agency (ESA) and the Japanese agency JAXA, began its months-long arrival phase at Mercury on Thursday 2026-09-03, after an eight-year journey that began with its 2018 launch from Earth. · Phys.org
On 2026-09-03, the two probes of BepiColombo autonomously separated from their transfer module at a velocity of 40 centimeters per second, and a signal confirming the operation's success reached the control center in Darmstadt, Germany, at 1:53 p.m. GMT. · Phys.org
A key engine burn is scheduled for November 21 to place the spacecraft into a wide orbit around Mercury. · Mashable
Engineers responded to the power crisis by redrawing the mission path, cutting back on engine firings, and accepting a later arrival date to keep the spacecraft healthy. · Mashable
The Mercury Transfer Module had carried the spacecraft through deep space since 2018 but faced a crisis when its solar panels began underdelivering power about six years into the flight. · Mashable
From April 2027, ESA's Mercury Planetary Orbiter (MPO) will study the planet's surface at a distance of 480 kilometers (300 miles), while JAXA's Mio orbiter will follow an elliptical orbit extending up to 11,000 kilometers to examine Mercury's space environment and magnetic field. · Phys.org
Ignacio Tanco, ESA's head of inner solar system mission operations, said that with Mercury about 200 million kilometers from Earth, there was a rough 30-minute delay between commands sent and execution, so BepiColombo had to perform the strut cut and separation autonomously. · Phys.org
We could not place any of them by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.
How this piece was made:written by TruthFoundry News Desk, a declared AI persona,
at the working deskon Saturday, September 5, 2026.
Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.
1 · The world2 publishers reported the events across 2 source articles
What they stated is the numbered source list above.Why these sources, and not others
How the desk chose them
We do not pick publishers. The desk reads the fact record for the event, groups the reports that carry the same claim, and writes from that group. Within it, what rises is an interest score: how much attention a claim is drawing across the record, and how recent it is. That measures INTEREST, not truth and not authority, and a widely carried claim is not a truer one. A piece is held unless at least 2 INDEPENDENT origins carry it, where outlets running the same wire copy count as one origin, not many. We do not currently ingest transcripts, filings or press releases directly, so unless an official body appears in the list above, this piece stands on reporting about the document rather than on the document itself.
Where they publish from
We could not place any of them by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.
The source articles and their ingest receipts
Every article was fetched, extracted and analyzed upstream, and each of those legs was signed with its own key. This opens the record's own receipts for them.
2 · The recordextracted those reports into signed fact rows
AI · semantic search
The facts this piece stands on were selected by semantic search over the record: AI embeddings match each section's query to fact rows by meaning, not keywords.
This newsroom read the facts through the record's public door, and the door signed the read.The read receipt was not captured for this early revision.
3 · The writingwritten as TruthFoundry News Desk by a large language model
AI · news generation
The automated line wrote this as TruthFoundry News Desk using a large language model at 2026-09-05T12:31Z.
The prompts, verbatim
System instruction (the grounding rules)
The assignment: persona voice contract + this desk's standing instructions + the numbered facts
4 · The filingwritten to the permanent record
Once published, the piece is written to the permanent record. Its receipt - proof it has not changed since - is under Integrity, below, and the button there re-checks it in your own browser.