spinner
x
This website is using cookies, in order to track this cookie warning and other popups, for managing login sessions, and for website analytics. We do not collect or store personally identifiable information, nor track or display advertising related information. That's Fine
 - Galactic Exploration Catalog - 
Revision for Palatine-Franconian Lighthouse

Previous Revision, by CMDR Marx [2022-09-17 15:42:33]→Selected revision, by CMDR Marx [2022-09-17 15:46:09]
DISCOVERER
CMDRs Kolumbus and Michael0903→CMDRs Kolumbus and Michael0903
NAME
The Palatine-Franconian Lighthouse→Palatine-Franconian Lighthouse
SYSTEMNAME
Kasu AA-A h0→Kasu AA-A h0
CATEGORY
Sights and Scenery→Sights and Scenery
CATEGORY 2
→
REGION
Outer Arm→Outer Arm
LATITUDE
→
LONGITUDE
→
CALLSIGN
→
SUMMARY
Located in the Outer Arm region, this system is only accessible with a fleet carrier, and houses a single landable but scorching hot HMC planet.→Located in the Outer Arm region, this blue-white super giant star is only accessible with a fleet carrier, and houses a single landable but scorching hot HMC planet.
DESCRIPTION
→

On 3308/09/13, the two explorers risked everything to explore the Kasu AA-A h0 system.

Located in the Outer Arm region, this system is only accessible with a fleet carrier.
The nearest known systems are Gyrafaae DC-B d14-0, at a distance of 398.84 ly:

and Kasu WN-B d0, 454.03 ly away:

These could not be reached even with an Anaconda that had a jump range of about 80 ly.

So, the two explorers used Kolumbus' fleet carrier named "Betty Boop", disregarding its already low tritium reserves, to reach the system.

There is a blue-white supergiant of spectral class B with 69.6953 solar masses and 385.1161 solar radii.
A lonely High Metal Content planet orbits it with an orbital period of 3,304.6 days, and has surface temperatures between 2,776 and 5,424 Kelvin. There are no bodies in the system other than this one.

At great risk to life and limb, the two explorers set out to explore the planet not only by ship and SRV, but also on foot:

One last look before departure.

And the journey continues.

→

On 3308/09/13, the two explorers risked everything to explore the Kasu AA-A h0 system.

Located in the Outer Arm region, this system is only accessible with a fleet carrier.
The nearest known systems are Gyrafaae DC-B d14-0, at a distance of 398.84 ly:

and Kasu WN-B d0, 454.03 ly away:

These could not be reached even with an Anaconda that had a jump range of about 80 ly.

So, the two explorers used Kolumbus' fleet carrier named "Betty Boop", disregarding its already low tritium reserves, to reach the system.

There is a blue-white supergiant star of spectral class B with 69.6953 solar masses and 385.1161 solar radii.
A lonely High Metal Content planet orbits it with an orbital period of 3,304.6 days, and has surface temperatures between 2,776 and 5,424 Kelvin. There are no bodies in the system other than this one.

At great risk to life and limb, the two explorers set out to explore the planet not only by ship and SRV, but also on foot:

One last look before departure.

And the journey continues.

JOURNAL
→
OBSERVATORY
→
All content is licensed under Creative Commons (CC BY‑NC‑SA 3.0)
Copyright © CMDR Orvidius, All Rights Reserved.  --- Forum Thread (exploration) | Forum Thread (player tools) | About | Data Sources | API Details | Patreon / Contribute

This website is not an official tool for the game Elite: Dangerous and is not affiliated with Frontier Developments. All information provided is based on publicly available information and data supplied by players, and may not be entirely accurate. 'Elite', the Elite logo, the Elite: Dangerous logo, 'Frontier' and the Frontier logo are registered trademarks of Frontier Developments plc. All rights reserved. All other trademarks and copyrights are acknowledged as the property of their respective owners.

Special thanks go to all commanders and explorers who graciously upload their data to EDDN, EDSM, and EDAstro to make all of this possible. We wouldn't exist without your data contributions. For any bug reports or feature suggestions, please visit our forum thread.