Soyuz 7k-t-af 1

Vaeter program of G2Vbeta f is a space program to explore G2Vbeta c.

Kap Spieneun

This mission was to flyby G2Vbeta c. Sadly, a rocket mechanism failure stuck it in a low orbit. It crash-landed back on G2Vbeta f a year later.


This mission was to flyby G2Vbeta c. Sadly, radio communication failed and is now classified as space junk.

Spieneun 19

This mission was intended to land on G2Vbeta c. Sadly, it met a fate like Kap Spieneun due to the same problem.

Spieneun 20

This mission was intended to do the same as S19, but the same happened.

Spieneun 21

This mission was intended to flyby G2Vbeta c, but a Challenger-like incident happened.

Vaeter 40.7A

This mission also attempted to do the same as S21, but the same as S19-20 happened.

Spatium 27

It attempted to do the same as V40.7A, but the same happened.

Vaeter 2

It attempted to do something like V40.7A, but radio communication failed. Additionally, the probe is lost.

Vaeter 3

It attempted to land the planet. Unfortunately, communication failed just before touchdown and crash-landed in the Bheleikuo Valley.

Spatium 96

It attempted to land on the planet, but it did not leave their planet's gravity. It crashed on the other side of its planet, causing a huge racket.

Vaeter 41.3A

It attempted a flyby, but the launcher failed and it blew up on the surface of the launch pad. 3 bystanders were killed.

Vaeter 4

It explored and transmitted atmospheric data about G2Vbeta c. Unfortunately, the probe had a parachuting problem and ended up as a fireball, landing in Bheleikuo Valley.

Spatium 167

It attempted to land on G2Vbeta c, but due to mechanism error, it reentered its planet a month later.

Vaeter 5

It did the same as Vaeter 4, and the fate was the same.

Vaeter 6

It did the same thing as V4,5, and what happened was the same too.

Vaeter 7

It did the same thing, transmitted photos on the surface, such as a city. Unfortunately, it landed upside down, which got the right way up a year later when the wind blew it.


The city it landed nearby.

Spatium 359

When it was in the midst of escaping the planet's gravity, the engines failed. It now orbits its planet in a highly eccentric orbit, instead of landing on the intended planet.

Vaeter 8

It did the same thing as V7. It landed finally on the right side, and on Mt.Eallmaest.


Even Mt. Eallmaest's summit is of high altitude life thrives due to the thick atmosphere and the higher temperatur.

Spatium 482

This lander blew up when the probe started its engines in orbit around its planet.


The big boom.

Vaeter 9

It did the same as V8.

Vaeter 10

It also did the same thing.

Vaeter 11

It did the same, but sadly the imaging systems were impaired.

The only picture taken from the planet. Exposure was pathetic and it was black and white. This only shows the outline of Mt. Eallmaest.

Vaeter 12

It probed the lands for a day until lightning struck.


The lightning. This was photographed a millisecond before breakdown.

Vaeter 13

Landed at the same place. It detected a rare mineral.


Leucite, a very rare mineral.

Vaeter 14

It landed and detected a kind of rock found in mid-ocean ridges.

The mid-ocean-ridge rock. The place might have once been sea.

Vaeter 15-16

It orbited the planet, trying to map it.

Vaeter Delta

It landed in Lakeurma Plateu, taking pictures of snowy lands, However, photos did not reveal any large ice cap.


The icy lands it landed at.



G2Vbeta c 10000km away from Vaeter 1. This was photographed 1 hour before breakdown.


The atmosphere of G2Vbeta c, taken 2 mins before breakdown.


The sun from G2Vbeta c, taken by Vaeter 5.


G2Vbeta c from Vaeter 11. This was a warning sign of the imaging systems due to exposure problems but no people at the space agency really cared.


It was a cloudy day when Vaeter 12 landed. Taken 1 day before storm.

Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.