A Short Trip to Mars: Red Australia

By Aadg

The story a Short Trip to Mars is a fictional story, about the first exploratory mission to the Planets surface. The story is a fictional adventure of three convicts who were sent to Mars for six years. However, the story is based on the real concepts of the AADG 1147-01 Project. The story is a demonstration of how components of the project work and what their applications is. The facts and the components are completely real. There are no aliens or first contact situations in the story. However, the story is not dry. The main characters are a group of convicts who are selected for this mission because of the unusual orbit of Mars and safety issues. They are sent on this first mission, because as the unified International Space Administration states, there are to many unknown variables involved in sending a high quality crew. The crew makes some interesting discoveries as to the Martian surface and Martian history. They become a unified team when confronted with the conditions On Mars and build a highly involved relationship with each other The story is unique in circumstance, which give light to the way we look at space exploration and its future. If you dont know much about space travel or the angry Red Planet you will when you finish
this book.

• Language: English
• Publisher: Xlibris US
• Release date: Mar 9, 2012
• ISBN: 9781469150154

Book preview

Copyright © 2012 by AADG.

Library of Congress Control Number:         2012900419

ISBN:          Hardcover          978-1-4691-5014-7

                    Softcover           978-1-4691-5013-0

                    eBook               978-1-4691-5015-4

All rights reserved. No part of this book may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage and retrieval system, without permission in writing from the copyright owner.

This is a work of fiction. Names, characters, places and incidents either are the product of the author’s imagination or are used fictitiously, and any resemblance to any actual persons, living or dead, events, or locales is entirely coincidental.

Any people depicted in stock imagery provided by Thinkstock are models, and such images are being used for illustrative purposes only.

Certain stock imagery © Thinkstock.

Rev. date: 11/03/2014

Xlibris

1-888-795-4274

www.Xlibris.com

594440

Contents

Dedication

Introduction

The Navcomm System AADG

Chapter 1:   The Beginning

Chapter 2:   The Pick

Chapter 3:   The Prep

Chapter 4:   Back to School and the News

Chapter 5:   The Starr

Chapter 6:   Welcome Home

Chapter 7:   The Valles’ Marineris

Chapter 8:   Visitors

Chapter 9:   The Olympus Mons Expedition

Chapter 10: The Drop

Chapter 11: The Move

Chapter 12: Hellas Planitia

Chapter 13: The Capsule

Chapter 14: Going Up

Chapter 15: Homeward bound

Epilogue 1147-01/D (colonization)

Bio

Book Description

Dedication

This book is dedicated to the many people who worked on this project, Dr. Tyre Alexander Newton

Professor Emeritus of Mathematics at, Washington State University, Who died in 2009, and to all the people who think there must be a better way.

8.jpg

Dr. Tyre Alexander Newton

http://www.math.wsu.edu/Events/tnewton.php

Edited by: Norma Sheridan

Introduction

This book is a tech book, on the AADG Space Exploration project, with a fictional story. However, the project and components that this story is based upon are not fictional. So, you may ask which part of this story is real and which part is fictional. The story is based on AADG’s 1147-01 Space Exploration Project and was produced to explain how components of the project work, and why it is to our advantage to consider their application. Full explanations of the components and fact sheets are not offered in the story, and not all components of the project are represented in the story. The project is a new way to look at our approach and development into Space Exploration. A perfect example of this is the Navcomm System, and other devices that we don’t have in application under our current plan. Other examples are the exterior hull repair device, a specialized component for long term missions, and the Emergency Operational System (EOS). There are over 120 components in the project that are designed to make space exploration a safer and more effective venture. The project is designed to save Money, Time, and Effort and present the possibility of a more correct way to the approach the concept of going into Space and the unknown. This project is presented in two books ‘A Short Trip to Mars’ and ‘Jovian Space: The Space Train’. It is staged over a seventy year period, chronicling the life of the main character, John Alexander. John is a man who just like now, exists in a technically active world, which is changing around him. John was born on January 1st 2001 at 1 am and lived for 70 years, until his death in 2070. The concept of an International Space Administration is of course a fictional concept, but might be a concept that may need to be considered. Space exploration is not cheap and this alliance may be the right way to approach the cost factor. The AADG 1147-01 project is divided into a five step program. The story of ‘A Short Trip to Mars’ is based on step ‘4’. Steps 1-3 are presented in this story in retrospect. Step ‘4’, is the first manned exploration of the Martian surface. The story presents a false image of the project with the presentation of mistakes that may become concerns in this development of Space Exploration, some of which can and should be avoided. The conclusion of facts presented by both books ‘A Short Trip to Mars’ (ASTTM) and ‘Jovian Space: the Space Train’ (JS: TST) demonstrate incites that we may wish to considered, and problems that we should have solutions for. It also shows a concept design for the mission, whereas the sponsors and designers plan ahead for problematic solutions to conquer the unknown. It’s doubtful that the first Mars surface exploratory mission to Mars will be more than two years. We estimate that the first mission of a manned landing on Martian surface and returning to Earth will most probably consist of a very short amount of actual time on the surface, less than 6 months and will probably not be accomplished by convicts. However, one of the AADG consultants that worked on the project made a significant point during its development. In exploring space, great time and distances need to be realized. If we are not prepared to go to distant Planets, then for safety reasons, we should not go. Hopefully this book will shed a light on a possible future of Space Exploration. This book reflex’s a series of possibilities that may eventually become a reality. This book also addresses a multitude of real facts about space exploration such as: signal lag time, food preparation in space, transportation, hydroponics and cryogenics. These concepts are facts that everyone who is interested in space exploration should be made aware of. For readers who don’t know much about the scientific concerns of space exploration, this book makes a rather complex understanding simpler. This book, is not an exact reference book however, the charts and values presented are fairly accurate.

The International Space Administration—fictional.

The concept of convicts being the first people on Mars—fictional.

The concept of the crew being international—possibly fictional.

The concept that the first mission’s duration is six years—fictional.

Real Components from the Beginning

The Earth lift vehicle—real.

The XPLM and CMP vehicles—real.

CTU-concept

Tri-Starr System—real

Navcomm System—real

Re-generative power supply technology—real.

Pods—real

Jumper—real

Rover—concept

Ariel—concept

Ariel float—concept

Space bathroom—real

Kitchen—real

Auto cooker—real

Module Interior Design—real

Electronic detective—real

EOS—real

Ion plasma propulsión engine—real.

Sensors application—real

Imagery and media—real

Lunar Starr concept—real

Orbital Platforms—real

Balloons—real

Lunar habitat development—concept

Facts on cryogenics—real

Hull repair—real

Expansion struts—real.

Panel construction—real

Glass panels—real.

Robots—real

Hydroponic systems introduced—real.

Air and system handlers—real

Theory of the Martian orbit and history—real

So, as you see, there are more real components in the book, than fiction. All the concepts innovations and inventions are considered intellectual property of the AADG 1147-01 project. So, intensive descriptions of how the components are built and work is limited. The principle story occurs on the equator of Mars in the region known as the Marineris Valles’, the Tharsis region, and surrounding areas. For further information on this project and its components please contact AADG at [e-mail]. So, enjoy the book.

fcreyer—Administrative Consultant, AADG

General Map

9.jpg10.jpg

The Navcomm System 11.jpg AADG

As it is explained in this book, the Navcomm Operational System plays a major role in the 1147-01 Project. This project, upon which the book A Short Trip to Mars is based, presents a five step program and an entirely new way to look at our approach into Space Exploration. As our role in space exploration grows, so does the navcomm application. The application of the Navcomm System in the project, is implemented in step one, which is the return to the Moon. It consists of the deployment of a series of mapping probes into an orbital format suspended in orbit around the Moon, and assists in the establishment of a permanent lunar base. The probes form a space information network, and a vector telemetry and detection web. The deployment of these Navcomm System probes assists in developing mapping and signal relay stations throughout the solar system. These units will complete a 3D navigational vector web map, which will assist exploratory vehicles in their journeys, and operations within the Solar System. The system also serves as a watchdog, and emergency assistance monitor. Currently, there are eight different types of Navcomm units containing different components. However, the main unit discussed in this book is the T-111 mapping probe, nicknamed the T-rex. This unit is, as are all navcomm units, a combination of many different sensor components. Its main function is to keep track on a section of space, and create time-scale maps of planetary motion, by monitoring the area and changes that occur within our Solar System. To do this, a series of T-111 units must be deployed in strategic locations throughout the Solar System. Once deployed, these navcomm units create the vector telemetry web, allowing communication and signal linking stations to solve monitoring and signal lag concerns. They can also work as a single unit structure to assist traveling exploratory vehicles and monitor conditions of changes within our local space. Every vehicle launched in the 1147-01 project contains a Navcomm System navigation unit onboard. The vector web supplies mapping of the planets and their moons, as well as large sectors of unoccupied space. Eliminating Mercury and Venus from an active interest, but including the Kuiper and Asteroid Belts, the probes form a sensor and signal booster web, establishing a solar orbital safety guide.

Possible navcomm locations:

As you can see, we have 32 primary locations selected as possible orbital anchors. They are the six major planets Earth, Mars, Jupiter, Saturn, Uranus, and Neptune and their Moons. However, we predict the deployment of the navcomm web to consist of over 60 navcomm units, with a minimum of 5 units apiece for the Asteroid Belt and the Kuiper Belt. One of the main concerns with this plan is the longevity of the navcomm probes. The Planet Neptune is approx. 4,553,946,490 Km away or 4.5 billion 3 million km or 2,829,691,159 miles. The Kuiper Belt extends another 2.5 billion miles past that point, which is a considerable distance estimated to be 5 to 5.5 billion miles from the surface of the Sun. To get to Neptune at the speed of 36,000 miles per hour, which is the current speed of our fastest satellite probes thus far, would take approximately 9 years. At current standard of our systems today is approx. 24,000 mph. It relates to an estimate of a trip to Neptune to take over 13 years. The longevity problem is the mapping probes need to be constructed to remain operational for a minimum of 20 years. Power supply and fuel usage top the list of concerns that were addressed in Navcomm’s development. It is speculation whether or not there will get to a time when we would have a manned mission as far out in space as the Kuiper Belt and the Oort cloud. However, we can see the eventual establishment of a Saturn Station for scientific investigation of Saturn’s ring structure. Mars, who is our closest neighbor, is 48,541,996 km (36 million miles during Perihelion—closest distance to Sun and Earth) away is estimated by scientists under current circumstances to be an 8 month, or a 250 day voyage. This would place Jupiter at 30 months away or 2.5 years, and Saturn at twice that, or 5 years out. If it is five years out, then it will take five years to return. A ten year round trip, would be a stretch under any circumstances. Health issues would be a primary concern, including radiation sickness, muscle control, mental fatigue and insanity (space happy). It would also require ten years of food, water, atmosphere and other utilities that would be needed to support such a mission. In the 1147-01 project, a working solution is addressed by sending the supplies ahead of the mission, before a manned mission is made. The Navcomm System acts as a guidance system with safeguards against collisions with rouge debris, and other unknown space hazards. Everything has to have a beginning, and the beginning for the 1147-01 Project is the establishment of a permanent lunar base on the Moon then Mars, and then to continue out into Jovian space. As the Navcomm units grow older, the older units will be easily refurbished and sent further out towards the Kuiper Belt. In the deployment of Navcomm in Jovian space, the units will be placed in orbit around planetary moons. However, in some applications the units can be anchored to the moon’s body, such as on the Martian moon Phobos and certain asteroids. Although as we have explained, navcomm units contain different components for different applications, some components are universal to all navcomm units: the transceiver, the Operating System, and the regenerating power supply.

Other components that may be similar are the sensor array, the maneuvering thruster array, internal system integration, antenna, and data storage. When the units are fully deployed and operational, the vector web that they produce will form a security web inside our Solar System. Nothing inside this web that moves or changes will be undetected. Wherever the units signals link, it will form a communication data conduit. This telemetry web will exist on both sides of the Sun with a range of 12 billion cubic miles. The Operating System used by the Navcomm System is the most important component in complexity and importance. Since a journey to Neptune, under current technology is estimated to be 13 years, most of that time you would spend in Jovian Space, going between the planets of Saturn and Neptune. This represents a distance of two billion miles, well over 60% of your travel time from Earth. After you reach Neptune, you’re still looking at two and a half billion miles to navigate the Kuiper Belt, and arrive into deep space past the Oort cloud. For the navcomm application we needed to change the value of the International Astronomical Unit (or IAU). An IAU is commonly noted as a unit of measurement of distance, equal to 149,597,870 kilometers or 92,955,807.3 miles, which is supposed to represent the approximate distance from the Sun to Earth. However, this value does not represent a relative value for us. We substituted the value to 161,000,000 kilometers or 100,000,000 miles, and gave it a designation of that value to be one Navcomm Astronomical Unit or a NAU. This changed the value of the Solar System measurement to be 28 NAU instead of 29 (IAU standard), but the conversion value made it easier to calculate, and makes more sense for our purpose. If I would say one half an NAU, that would be easier for you to understand that value as 50 million miles or 80.5 million Km. Than it would be using the IAU values of 46,477,903.65 miles or 74,798,930 Km. By changing this value it allowed us to use multiple scaling, and linear tracking on a multi-faceted dimensional sliding scale. If you could travel 100,000,000 an hour (1 NAU/h) it would only take you approx. 3.19 years to reach Neptune, but you would be traveling at a velocity of 27,777 miles per second or 99,997,200 mph, a little under 1/6th the speed of light. One sixth the speed of light is equal to 31,033.33 miles per second or 111,720,000 mph times six gives us the speed of light at 670,320,000 mph or 6.7032 NAUs per hour approx. Light from the Sun takes 8.3 minutes to reach Earth. However, it takes 8.96 minutes for light to cross the distance of one NAU. Thus 6.7032 NAUs per hour yields: 160.8768 NAUs per day (or 16.8 billion miles), 58,720.032 NAUs per light year, and 191,427.3043 NAUs per parsec. Proxima Centauri our nearest star is 1.3009 parsecs away or 249,027.7802 NAUs in distance.

1.jpg

Tycho Brahe, Johannes Kepler—The Navigators

Tycho Brahe was a Danish astronomer who is credited for one of the first known studies of planetary motion and navigation, which later generated Interplanetary Geo Vector Mathematics. His assistant, Johannes Kepler later developed the Three Primary Laws of Planetary Motion. The Operational System that the Navcomm System utilizes is a default program known as the Solar Orbital Clock (SOC), which by definition is a timescale calculator based on a multitude of mathematical structures, including linear algebra, vector relations, differential equations, and planetary motion mapping. Here is a brief explanation of how it works. However, I must state that in designing this program, we used an application called Mtronics, an AADG product, which is under constant development. Mtronics is used to produce an inter-solar scalable matrix index of the orbital structure and motion of our Solar System. The SOC is a primary product that appears in the programming as a set of indexed timescale map establishing a default map of the Solar System. Because we used Mtronics, the program has a variable (a sliding linear algebraic timescale). Meaning it can be set into scale creating a rotational map of the planetary motion based on Kepler’s 2nd & 3rd Law of planetary motion, velocity and planetary incline with relation to the elliptical curvature of the major and minor elliptical axis. Given a speed, Navcomm can tell you how long it will take you to go from point A to point B and the position the planets and moons will be in when you arrive at that destination. It can plot the course and fuel usage requirements, as well as polar inclination and rotation, orbital velocities, satellite rotation, and rouge objects suspension in space, such as the ring structures and the Kuiper and Asteroid belt suspension structure. The grid maps are based on basic default unit information given and retained by the SOC and is updated by the navcomm sensors arrays of the probes.

Solar Distance Conversion Meridian Orbital Distance to NAU (100,000,000 miles/ 161,000,000 Km); Earth to Neptune X (minor axis):

Orbital circumference in Degrees: Each degree represents the following distance in miles from Solar center.

Timescale-relative to one degree. The planets complete one degree in:

Distance of Orbit Solar point (A To Image54696.PNG B)

These are important charts, as they tell you the mean distance from point (A), to point (B). They also set up the orbital rotation for the clock, in a time sequence. Included would be a map of navcomm stations and their orbital velocities on a Timescale of Meridian Orbital Distances (Navcomm meridian default values). Meridian values of the SOC are default values and are used as a default base represented as a center point structure. In other words a circular orbit aligned to the center of the Sun. Using the center of the Sun as our major focal axis and extending the X axis of our foci upper limit to 12 billion miles in length and using our z axis as 360 degrees gives us a three dimensional scale large enough to encompass the entire Solar System, plus the Asteroid and the Kuiper Belt. As a Planet orbits the Sun, it has three variances that must be taken into consideration. One is the differential ratio between the aphelion and the perihelion. The second is the ratio between the Sun’s axis and the inclined elliptical orbital plane of the planets orbit. The third is the differential of the planet’s velocity, which increases during the perihelion and decreases during the aphelion. A perfect circle contains 360 degrees. These variances are added to the clock in plus or minus values and then time scaled to produce a vector track of the planetary orbits. In our Solar System the planets orbit the Sun not in a circle, but in a counter-clockwise ellipse, which also contains 360 degrees (Kepler’s 1st). However, we are not dealing with a two dimensional space, but a three dimensional space containing 360 degrees squared or 129,600 degrees. In order to integrate the Navcomm linear maps into a timescale clock format, we need to realize what the NAU value of one degree is, as to the planets orbital circumference. So, we use the major axis to divide space into degree squares. However, the farther we extend our distance on the X axis the greater volume of a degree becomes. The values of a degree in space would be a square the same length on all four sides and exist in the orbital curve of the planets track line.

Example: value of one degree on-

One reason for creating this clock in a 3D format is the planetary inclinations. As the planets orbit the Sun these variances form a 3D conduit or a tunnel pathway of the planets solar orbital rotation. We can use the default SOC meridian and tracking values to complete this functional map with the planetary curve. However, we also need the value table of orbital inclinations.

12.jpg

Time in a bottle:

To correctly implement navcomm into our Solar System, we need to establish the focal point of our major axis. For this purpose, we use the center of the Sun (not the surface of the Sun). We create an ‘X’ and a ‘Y’ line segment to identify our focal center and 360 degrees as the value of ‘Z’. Next we need to set our upper and lower limits. The Oort cloud, at the end of the Kuiper Belt, is currently estimated as the end of our Solar System at a distance of 5.5 billion miles. We can use this distance to set our upper limit. However, since this is an orbital clock we also need to add the radius of the Sun (696,342km. or 432,686.5 miles). Let’s set our upper limit of XZ axis to 6 billion miles times 2, so that we can cover both sides of the Sun, so 12 billion miles times 360 degrees. Our Solar System is designed like a rotating plate, in which there are a lot of objects on the plate rotating around the center axis. However, there are no known permanent objects above or below the plate in orbit over 45 degrees in inclination. Our navcomm vector web must be able to operate on both sides of the Sun and since our inclination doesn’t exceed 45 degrees we can set our y axis to 6 billion miles (+3 billion and – 3 billion at axis) and our x, z axis to twelve billion miles times Pi. This structure creates a conic section of a cylinder. Imagine a Plexiglas cylinder section where 1 inch equals 1 billion miles. Our cylinder would be 12 inches in diameter by 6 inches in height with our solar system imbedded in the center inside. Using the formula for the volume of a cylinder V = π × r² × h, we now know that the navcomm vector web will have a value of 678.456 billion cubic miles. We now have a telemetry web of 678 billion cubic miles, or 678 billion boxes, cubes, or dice units. This can serve as the distance values of our solar system. Using Mtronics (an AADG application) allows us to form a linear algebraic floating scale, which develops orbital tracking tunnels of planetary motion. These tunnels or conduits contain the planet, plus all properties of the planets including moons and suspended particles such as their rings. This motion index is also applied to all parts of the Asteroid and Kuiper belt including the gaseous movement of the Oort cloud. Our demonstration above is how to put our solar system in a time box, or time in a bottle. In space: time, velocity, and distance are our operating values. We now wish to divide this space for accuracy in measurement. Our default division is to segment this structure by 10. This will give us 6784.56 billion cubic navcomm units each containing 100 million cubic miles (NAU (100 million miles, by 100 million by, 100 million miles)). We continue to segment our blocks by ten from 100, 10, 1 million to 100, 10, 1 thousand to 100, 10 and 1. We have segmented our structure nine times, at the end we have a designation of 1 cubic mile or 1 cubic kilometer, which results in an index of 678,456,000,000 units. Every section of space in our box now has a navcomm timescale (SOC) location identity. Using the center of the Sun as our foci point or major axis origin (000) allows us to design the structure of the Y extension to 6 billion miles and the encryption of the Z extension to be 360 degrees this has validity, because the elliptical inclined plane of planetary orbits are positive values in relation to Y above the center of the Sun. The value in degrees of the Z axis (360/ 00) would be a tracking variance of Z using the apogee point of Neptune as magnetic north. The XY distance values will give your location from the center of the Sun and your degrees will give your orbital location. If you would like to go to a free space position between Jupiter and Saturn, we simply need to set the controls to the destination coordinates from the Sun to (x = 7 NAU, Y = + 5.75 degrees in inclination from the Solar axis and Z to be equal to 360/00, +/—(Distance) times (Velocity) = travel time +/—track position. This will get you to a position almost exactly half—way between Jupiter and Saturn at the apogee point, in a direct line to Earth’s apogee point. With Saturn below you and Jupiter above you at approx. ½ degree or a variance of 177,430 miles in inclination and a distance of 230,359,056.5 miles (2.3 NAU) from either planet. This should give us a quick understanding of planetary orbital mapping.

Using the Earth as minor axis as 2nd focal point, and giving the value of the Earth’s Meridian Orbit as 1, we get the x axis values of the distance to the other planets:

Orbital Circumference conversion into NAU/miles—100 million miles to equal to 1 NAU/or 161 million Kilometers

Meridian Orbit, Navcomm equivalent NAU: Upper grid (International Mechanical Engineering Standard Metric (IMESM) in Kilometers – distance between planets Km top, miles bottom

Lower grid—American Standard of Mechanical Engineering (ASME) in miles

Planetary Velocity—velocity in miles

You are launching a robotic vehicle from the Earth’s Lunar Platform to Saturn and then to Neptune. You wish to intercept Saturn at its Apogee point and then proceed to Neptune. To do so, you will need to convert the formula into the Solar Orbital Clock to develop a timescale navigation map. In the SOC we use both the center of the Sun as the primary focal point (which would be the center of the Sun (minus its mass)) and the origin point, the position of Earth and the Lunar Platform. Let us assume that the Earth and the Platform are at their Apogee as well (Earth’s Apogee is 152,098,232 Km + distance to Moon= 384,400 Km: Total = 152,482,632 Km/or 94,748,334,1 miles/or.947 NAU). Your journey to Saturn, will depend on your velocity and the position of Saturn at the intercept or destination point. Saturn’s aphelion distance is 1,513,325,783 Km/ or 940,337,042 miles (9.4 NAU). Therefore, the trip to Saturn’s apogee, minus the aphelion distance of the origin point (Earth’s lunar platform) equals 1,360,843,151 Km/or 845,588,728 miles/or 8.455 NAU. From our chart we gauge the elliptical incline from the Sun’s solar equator at apogee to be 7.155 for Earth and 5.51 for Saturn or a negative differential of—1.645 degrees. Since Saturn’s orbitial degree is 7,769,352.9 miles the value of 1.645 will be equal to—12,780,585.5 miles. At this point the Sun’s x axis extension is 42,809,134.48 miles/26600,311.89 Km below Saturn’s orbit. The velocity of your vehicle will be the deciding factor. We will set or lower limit bar of our calculation to the escape velocity of Earth (11.2 Km/s or 22,932 mph). We will of course set our upper limit at N, but for this example will substitute a velocity value of 100,000 mph ( which is a ficticious number, and a rediculously fast speed, by our current standards). At our lower limit your vehicle will be traveling approx. 1,360,843,151 Km/or 845,588,728 miles at 11.2 meters per second or 22,932 mph. This will take you 36,873.7 hours, or 1536 days, or 4.2 years to reach your destination. However, if you where able to achieve and hold a average velocity of 100,000 mph or 27,777 miles per secod. You would arrive at your intercept location with Saturn in approx. 352 days, or just less than one year. This is important because, as your vehicle is approaching the intercept point with Saturn at apogee. Saturn is continuing its rotational solar orbit at the rate of 3 miles per second or 259,960 miles per day (minus its transverse velocity of the aphelion – (Kepler’s 2nd ). If your vehicle arrives at the intercept point as much as 12 hours late, Saturn will have passed the intercept point by over 129,980 miles and may be out of reach, and your vehicle may not be able to intercept. In space navigation applications, it is better to arrive at your intercept destination position early, rather than to arrive late. In order to do this you must launch your 100,000 mph vehicle 12 degrees before Saturn is at its apogee point. For your 22,932 vehicle that would be 51.15 degrees. You will then arrive at the intercept point ahead of Saturn and be able to enter into the orbital pathway around the planet when it arrives. So, if your math is right Saturn should be rapidly approaching your vehicles position. For the second part of your mission you will need to have navcomm calculate your pathway to Neptune. In this case the best path would be when Saturn passes Neptune on its way back to the Sun. The Meridian distance to Neptune is 1,907,841,663, almost 2 billion miles. The solar orbital incline is 6.43, which is +0.92 degrees higher than Saturn’s inclination. You still have your 100,000 mph vehicle. However, you’ve spent a significant amount of fuel getting to Saturn. Navcomm calculates that you can only achieve a average propulsion velocity of 50,000 mph. That gives a travel time of 38,156.8 hours, or 1589.8 days, or 4.35 years. However, the orbital curvature and the eccentricity must also be calculated.

\frac{1}{a^{2}b^{2}}\left(\frac{x^{2}}{a^{4}}+\frac{y^{2}}{b^{4}}\right)^{-\frac{3}{2}} excentifity varience, a—is primary focal b-is minor facal

C = 4 a E(e) Circumference, a-major axis, E is eccentricity, (e) is minor axis eccentricity

P=2\pi\sqrt{a^3\over{\mu}} P is body traveling trough eplliptical period, u is standard gravitational parameter

This may lower your distance from poit A to point B using the destinations orbital curvature depending upon your origin position. For our example, a launch window of 1586 days or 4.35 years after as Saturn’s orbit passes Neptune. In order to achieve this intercept you must launch when Saturn is 9.49 degress ahead of Neptunes orbit. However, as explained there is such a thing known as cutting the orbital loop, which is accomplished by using the curvature of the orbit to get the shortest distance.

You’ll notice in this book, as well as in the sequel Jovian Space, that the onboard crew doesn’t spend a lot of time figuring out equastions for navigation, and that there is little to no actual piloting involved. Using vector math, linear algebra and matrix indexing allows us to scale space into navigational degrees, and motion into orbital conduits and thus create a timescaled orbital conduit monitoring system for our Solar System. However, this system is only relevent within our solar system, which stops at the end of the Oort Cloud. After that point, you need to change to your Galactic clock for navigation. To do this, we need to build a Galactic orbital clock. We should use the center of the galaxy as magnetic north, and our Sun’s extension as polar south, by drawing a line from the center of the galaxy through our solar axis we will have a Galactic clock. Dimensions of the galaxy are estimated to be 100-120 Kly (thousand light years) in distance, and 1000 ly in thickness. Our solar system is located approximately 27,000 light years from the galactic center, which is suggested to contain a massively dense black hole. However, the center of the galaxy is 60 degrees out of phase with our Solar rotation, so a direct line with our planetary rotation is not a option. The line would enter our Sun axis and exit on a diagonial, representing an offset of 60 degrees in respect to the galaxtic center. The estimation of the location of the galactic center is 8.3 +/—0.34k parsec’s. To run this application in our Solar System is not a problem for the navcomm mapping program, which may use the developed a dual index and a cross reference ordinates to the galactic center including the Sun’s orbital galactic velocity currently. Our Suns orbital velocity with regard to the galactic center is currently estimated at 220 km or 136.45 miles per second thus 491,220 per hour, 11,789,280 miles per day. If there every comes a time that we should attempt a exhibition to Proxima Centarui having a galactic clock already set up and operational may be to our advantage. These charts are a demonstration of two of the variable charts used in the SOC application. There are over 40 charts or maps per planet including moons or satellites, velocities, rotation, inclination, orbits, gravitational field strength, and radiation emission. The primary calculation which is point A to point B navigation is: Location (A)—Direction (X)—Velocity and Time (T) TIME it will take to get to location (B) and where location (B) will be when you arrive at that point, and how much fuel you will need to get there. The T-111s’ contain dual projection sensors, which allow the creation of a 3 dimensional image maps for a section of space. Another important fact about space travel, which is avoided by Sci-Fi books, is signal lag time. It takes 8.329 minutes for light to reach Earth from the Sun (one IAU). The navcomm value is 8.96. However, when the sending station is located on the opposite side of the Sun you can double this time, in other words to communicate with Mars when Mars is on the other side of the Sun. The signal would have a lag time of 20 plus minutes. Our NAU value makes the point of a lag time of over 4 hours one way when sending a signal to Neptune, so transmitting operational corrections is not practical application, thus making navcomm a must have application. Fortunately, navcomm is a system that can be implemented on every vehicle. As the Navcomm system progresses into space, certain areas where two units can be linked together can create virtual maps, which will allow for the creation of a virtual tour of the Solar System and its planets. This is most common when the vehicle modules, which all contain Navcomm units, link together to form an orbital platform. To get the location value of current planets look here: (http://www.fourmilab.ch/cgi-bin/Solar.) For an illustration of SOC design look here: (http://lab.aadg.info) (in the AADG Pages). The Navcomm System allows operators on Earth, and other Navcomm stations to view images in virtual 3d from anywhere on the web, at any time, minus the signal lag. We intend to construct a working navcomm interface on the AADG website located at (http://1147-01.aadg.info). Imagine this: You and your crew of eight are on your way in the first exploratory vehicle to the planet of Jupiter. You’re going to need food, water and air for 2.5 years and reserves for the 2.5 year return. After you pass Mars, and are approaching the asteroid belt. A large stone impacts your vehicle putting a hole in your hull and your exterior fuel tanks, venting your internal atmosphere and disabling your craft. You’re a year and a half from Earth and you don’t have enough fuel to return. And even if you did, you don’t have enough oxygen to last, but a few months. There is not an emergency station where you can pull in and fix the problem. It is solutions to problems like this that hinders our exploration into space. Before we can start thinking of interplanetary space travel, we need to find solutions to potential problems, which may occur. Navcomm and the 1147-01 project offer possible solutions. Suppose, you are seven months out on your way to Mars, and one of the crew spills coffee in the main control panel shorting it out and making it unusable. Now what do you do? Well, the solution might be as simple as, don’t allow coffee in the control room or make sure you have good cup holders, but the AADG EOS system offers a better solution. Then there are always first contact complications such as, what to do if we encounter an alien race, what is the procedure?? You and your crew are two billion miles out in Jovian Space and encounter an alien space vehicle. They attempt communications and docking. What do you do? Anyhow the 1147-01 project solves a lot of these problems. So, we are hoping you enjoy the book. If you like to know more about the project and the Story feel free to visit the website (http://1147-01.aadg.info).

"On the subject of explorations into Jovian Space, great distances and time are primary concerns, accurate navigation and detection will need to be developed and employed.—AADG

3d maps and structure are important, because there is no 2d space, only 2d applications

Dr. Tyre Alexander Newton—AADG Consultant

Chapter 1

The Beginning

The alarm clock went off as usual, meaning it was 7:00 am, but it had to be put on hold. Twenty minutes later, it went off again. Reality stirred Jason Greene to consciousness. He knew he had to get up, but lately energy had been evasive, and getting out of bed had become a major chore. He had no idea why his energy was so low, but whatever was causing it wasn’t a concern right now. He had a meeting with the United States director to the International Space Administration at nine this morning. He had gotten the call yesterday around 3 pm. As a deputy assistant to the United States director, these meetings were not uncommon for him. However, most of his work came over the wallboards, via the ‘Link’. Communications had come a long way since he was in high school in 2010. Sure, there were wallboards then (they called them TVs), but they weren’t as affordable or sophisticated as they were now. Around 2018 ‘3D’ screens had come of age, in the last ten years over three-quarters of the world now had ‘3D’ virtual boards that operated on the World Global Network (WGN), also called the Link. Most general meetings were held via the WGN link. However, anything that required security had to be done in person. This evidently, was one of those things. Jason shoved some food down his throat and gulped down a cup of coffee, and was out the door and down to the street.

Montreal was well into its morning stir. It was a brisk September day with a slight wind. The leaves had just started to change into their autumn colors, and Jason’s energy picked up instantly. He caught the tram downtown, as it was cheaper and faster to take the tram than personal transportation inside the city. Ever since the International Space Administration had located their headquarters here in 2022, Montreal had grown by leaps and bounds. The Administration Committee was composed of six independent groups or consortiums: the Europeans, the Asians, the Russians, the Chinese, the United States, and the English concerns, which included Australia and Canada and their lobbies. The lobbies were made up of business factions and conglomerates, pushing to get their initiatives in order to make a profit off of space exploration. The Committee was originally designed to coordinate the ventures and the regulations of the exploration of space, but in the last few years it had become more like