That was quite a long trail of green as S2 lit up. I guess I hadn't noticed that before. I didn't see a jellyfish plume on S2 this time, perhaps it needs light reflecting off it from the sun or moon.
Great launch.
You'll only see a jellyfish if the launch is just before dawn or after sunset. The 2nd stage plume needs to be illuminated by the sun to create that effect, and in this case the 2nd stage did not get into sunlight until a couple of minutes after engine cutoff.
Yea, too far away by then for me to see it with my binoculars.
Binoculars would have made no difference :-), the stage was way over the horizon and practically over Africa before it hit sunlight.
Looked very sub-synchronous. Telemetry froze for a while, but when it resumed (at 30:43) it showed 32835 km/hr = 9120 m/s. Add in the 402 m/s from Earth's rotation, to get 9522 m/s. That's about a 14000 km apogee (assuming no inclination reduction), and another 600 m/s to go to get to a nominal GTO. So GEO - 2400 m/s.The variable we won't know until we get TLE's is the inclination. There could be a bunch of inclination reduction in that burn as well that won't show up in the final velocity.
Spaceflight Now is reporting this sat's mass is 7075kg, the heaviest GTO sat ever. Link to article: https://spaceflightnow.com/2018/07/21/record-setting-commercial-satellite-awaits-blastoff-from-cape-canaveral/
At last the mythical 7-ton sat Gwynne mentioned shows up
Looked very sub-synchronous. Telemetry froze for a while, but when it resumed (at 30:43) it showed 32835 km/hr = 9120 m/s. Add in the 402 m/s from Earth's rotation, to get 9522 m/s. That's about a 14000 km apogee (assuming no inclination reduction), and another 600 m/s to go to get to a nominal GTO. So GEO - 2400 m/s.The variable we won't know until we get TLE's is the inclination. There could be a bunch of inclination reduction in that burn as well that won't show up in the final velocity.
Unless you have another look at worldmap with the trajectory on the livestream. You'll see it shifting north from crossing Lake Bangweulu to crossing above Lake Mweru - or roughly half the north-south extend of Lake Malawi. Which is a difference of about 300km at a distance of about 3000km from the equator. So it lost on the order of 6 degrees of inclination.
So ths reduces the delta-v required for plane change to 245 m/s, saves 75m/s and makes it approximately a GEO -2325m/s trajectory. [Goof corrected.]
Were the fairings halves recovered?
Looked very sub-synchronous. Telemetry froze for a while, but when it resumed (at 30:43) it showed 32835 km/hr = 9120 m/s. Add in the 402 m/s from Earth's rotation, to get 9522 m/s. That's about a 14000 km apogee (assuming no inclination reduction), and another 600 m/s to go to get to a nominal GTO. So GEO - 2400 m/s.That's what I'm getting too, something like a 250 x 14,000 km (or less) orbit. I think we expected subsynchronous, but I wonder about the "very" part.
- Ed Kyle
HISPASAT 30W-6 (with its smaller mass of 6,092 kg) was launched by Falcon 9 Block 4 to 184 x 22,261 km, 26.97°
Looked very sub-synchronous. Telemetry froze for a while, but when it resumed (at 30:43) it showed 32835 km/hr = 9120 m/s. Add in the 402 m/s from Earth's rotation, to get 9522 m/s. That's about a 14000 km apogee (assuming no inclination reduction), and another 600 m/s to go to get to a nominal GTO. So GEO - 2400 m/s.That's what I'm getting too, something like a 250 x 14,000 km (or less) orbit. I think we expected subsynchronous, but I wonder about the "very" part.
- Ed Kyle
HISPASAT 30W-6 (with its smaller mass of 6,092 kg) was launched by Falcon 9 Block 4 to 184 x 22,261 km, 26.97°And now we see TLEs showing 243 x 17,863 km x 27 deg for 7,075 kg Telestar 19V. We missed the maximum velocity at engine cutoff due to the data dropout (screen freeze), which led us to our lower initial apogee estimate.
They had planned to attempt OSCILY landing for the Hispasat booster, but sea states prevented an attempt.
As I see it, VA-189/TerraStar 1 still holds the record for GTO mass (6,910 kg to 250 x 35,786 km x 6 deg), since Telestar 19V went subsynchronous.
- Ed Kyle
2018-059A/43562 (243 km x 17863 km x 27.00°) has a delta v to GTO of 2064.5751 m/s or it is in GTO-2065
2018-059B/43563 (242 km x 17860 km x 27.00°) has a delta v to GTO of 2064.7341 m/s or it is in GTO-2065
according to my C/C++ program based on this.
2018-059A/43562 (243 km x 17863 km x 27.00°) has a delta v to GTO of 2064.5751 m/s or it is in GTO-2065
2018-059B/43563 (242 km x 17860 km x 27.00°) has a delta v to GTO of 2064.7341 m/s or it is in GTO-2065
according to my C/C++ program based on this.What parameters did you use? I get 2277 m/s using that approach (which seems to agree with this online implementation)...? BTW, doing a third of a degree of the inclination change in the first apogee raising burn saves ~4 m/s.
| #include <iostream> #include <iomanip> #include <cmath> using namespace std; int main() { int stay; do { stay=0; double perigee, apogee, inclination; cout << "Enter perigee in km, apogee in km, inclination in degrees." << endl; cin >> perigee >> apogee >> inclination; cout << setprecision(4) << fixed << "Perigee: " << perigee << " km" << endl << "Apogee: " << apogee << " km" << endl; double sma; sma = ((perigee + apogee) / 2) + 6371; //semi-minor axis, 6371 is Earth radius in km cout << setprecision(4) << fixed << "Semi-major axis: " << sma << " km" << endl; double const MU = 3.986005e14; double vp, va; vp = sqrt((MU * (apogee + 6371) * 1000) / ((perigee + 6371) * sma * 1e6)); va = sqrt((MU * (perigee + 6371) * 1000) / ((apogee + 6371) * sma * 1e6)); cout << setprecision(4) << fixed << "Speed at perigee: " << vp << " m/s" << endl << "Speed at apogee: " << va << " m/s" << endl; double rpd = 8681663.653 / pow(sma, 3 / 2); //revolutions per day cout << setprecision(4) << fixed << "Revolutions per day: " << rpd << endl << "Days per revolution: " << 1 / rpd << endl; double sync = 35786; sma = (sync + apogee) / 2 + 6371; perigee = sync; double nvp, nva; nvp = sqrt((MU * (apogee + 6371) * 1000) / ((perigee + 6371) * sma * 1e6)); nva = sqrt((MU * (perigee + 6371) * 1000) / ((apogee + 6371) * sma * 1e6)); cout << setprecision(4) << fixed << "Speed at perigee: " << nvp << " m/s" << endl << "Speed at apogee: " << nva << " m/s" << endl; double cross, along, need_along, dv_top, dv_bot, total; double const GEO_V = 3075; cross = va * sin((inclination / 180) * M_PI); along = va * cos((inclination / 180) * M_PI); cout << setprecision(4) << fixed << "Cross v at apogee: " << cross << " m/s" << endl << "Along track: " << along << " m/s" << endl; need_along = nva - along; dv_top = sqrt(pow(cross, 2) + pow(need_along, 2)); cout << setprecision(4) << fixed << "Delta-v at top: " << dv_top << endl; dv_bot = nvp - GEO_V; cout << setprecision(4) << fixed << "Delta-v at bot: " << dv_bot << endl; total = dv_top + dv_bot; cout << setprecision(4) << fixed << "Delta-v (total): " << total << endl; cout << "Enter 1 to restart or any key to close." << endl; cin >> stay; }while(stay==1); return 0; } |
2018-059A/43562 (243 km x 17863 km x 27.00°) has a delta v to GTO of 2064.5751 m/s or it is in GTO-2065
2018-059B/43563 (242 km x 17860 km x 27.00°) has a delta v to GTO of 2064.7341 m/s or it is in GTO-2065
according to my C/C++ program based on this.What parameters did you use? I get 2277 m/s using that approach (which seems to agree with this online implementation)...? BTW, doing a third of a degree of the inclination change in the first apogee raising burn saves ~4 m/s.
I used the TLE data along with the program written by LouScheffer. I literally "translated" that program.
This is the program, it should compile with GCC using C++11:
...