Geoair2
Well-known member
I will attempt to make STS-98 first shuttle flight with the second generation cockpit
Project Space Shuttle Vessel
- Thread starter GLS
- Start date
That was actually STS-101 in May 2000.I will attempt to make STS-98 first shuttle flight with the second generation cockpit
Geoair2
Well-known member
Geoair2
Well-known member
Johan2011
Retired
TheShuttleExperience
Well-known member
Nice. Every mission is a good oneIn fact I didn't have the right information.
But next mission STS-98
You have 135 to chose from 
Geoair2
Well-known member
Unfortunately I don't see how unless we reduce the orbital altitude of the shuttle a little more after separation to go around the earth more quickly and have an earlier re-entry window.
How about performing the de-orbit burn on the historical date (July 21 2011)? Launching at the historical time and docking with ISS at the historical time and staying docked for the historical duration should lead to a de-orbit burn somewhere around 0800 UTC on July 21 2011 for a landing at KSC15.
Geoair2
Well-known member
STS-98 Assembly 4 stage
Stage 1 move the PMA-2 to Z1
Stage 2 capture Destiny in the cargo bay of Atlantis. Turn the module at 180 degrees and dock to Unity.
Stage 3 recover PMA-2 on Z1 and dock to Destiny
Stage 4 Deploy the Top Radiator on P6
Stage 1 move the PMA-2 to Z1
Stage 2 capture Destiny in the cargo bay of Atlantis. Turn the module at 180 degrees and dock to Unity.
Stage 3 recover PMA-2 on Z1 and dock to Destiny
Stage 4 Deploy the Top Radiator on P6
Geoair2
Well-known member
Last edited:
Johan2011
Retired
Johan2011
Retired
Geoair2
Well-known member
STS-101 is planned, for the moment I am focusing on the ISS missions I have nothing planned at the moment for STS-66
Little test STS-110
Last edited:
Geoair2
Well-known member
Could someone help me? I can't get the correct position data for the ISS at the time of the STS-111 launch. I find myself each time with too big a deviation in alignment with the ISS.
STS-110 Final test
STS-110 Final test
indy91
Addon Developer
- Joined
- Oct 26, 2011
- Messages
- 1,262
- Reaction score
- 727
- Points
- 128
I don't know how you have been doing it with the missions so far, but my system has been using Two-Line Elements and the Scenario Editor TLE tool. Likely this doesn't lead to a perfect alignment though unless you use nonspherical gravity.
GLS
Well-known member
Release Tuesday!!! 
SSV v1.9 is out! https://github.com/GLS-SSV/SSV/releases/tag/v1.9
Somewhat of a small release, it completes the runway database, now allowing the user to pick from over 180 runways to land the vehicle.
There are probably more runways that were considered for shuttle landings, but without "solid" information I left them out... anyway, I think there are more than enough runways now.
The mission landing site table configuration can now also be done by selecting one of the preset or default tables, provided in the Mission Editor (in addition to the existing "manual" option). These tables are not "official", and will rarely match exactly with what was used in actual missions, as available landing site changed often and earlier missions had smaller tables (the early flights had just 3 runway options).
And just to be clear, this release is (only) for Orbiter 2016.
Next I'll be finalizing the version for the new Orbiter, so that is ready for a release as soon as the new Orbiter comes out, and then I'll return to the mountain of work for the v2.0 release.
SSV v1.9 is out! https://github.com/GLS-SSV/SSV/releases/tag/v1.9
Somewhat of a small release, it completes the runway database, now allowing the user to pick from over 180 runways to land the vehicle.
There are probably more runways that were considered for shuttle landings, but without "solid" information I left them out... anyway, I think there are more than enough runways now.
The mission landing site table configuration can now also be done by selecting one of the preset or default tables, provided in the Mission Editor (in addition to the existing "manual" option). These tables are not "official", and will rarely match exactly with what was used in actual missions, as available landing site changed often and earlier missions had smaller tables (the early flights had just 3 runway options).
And just to be clear, this release is (only) for Orbiter 2016.
Next I'll be finalizing the version for the new Orbiter, so that is ready for a release as soon as the new Orbiter comes out, and then I'll return to the mountain of work for the v2.0 release.
