# 2nd stage speed - with respect to what? (SpaceX webcast of Orbcomm OG2 deployment)

As a follow-up question to this answer by @TildalWave, exactly what frame is used to calculate the "speed" in the inset display of speed and altitude in the SpaceX broadcast of the Falcon 9 launch and Orbcomm-2 deployment. Since it starts at zero before launch, is it the ground speed of the orbit projected on the Earth's surface, or something else?

I'm trying a simple physics exercise to convert speed to velocity under some assumptions (fixed inclination, radial velocity from $\Delta altitude/\Delta t$) and then integrate it to try to reconstruct the orbit for fun. I know there are other ways, but this is what I want to try.

For example, as a rough test of the numbers (in Python):

import math

pi     = math.pi
two_pi = 2. * pi

r_earth  = 6371. # km from google
altitude = 629.  # km from screen shot
r_orbit  = r_earth + altitude

speed_screen = 25947.  # km/hr from screen shot

print 60. * two_pi * r_orbit / speed_screen, "minutes"

r_florida = r_earth * math.cos((pi/180.)*23.4)
speed_florida = two_pi * r_florida / 24.

print speed_florida, "kph"

print 60. * two_pi * r_orbit / (speed_screen + speed_florida), "minutes"


gives:

101.704930397 minutes
1530.74487421 kph
96.0390978625 minutes


Adding the "speed" from the screen shot to the "speed" of Florida (to get a speed closer to something in an inertial frame) gives 96 minutes - close to the 97.4 minute period of the Orbcomm-2 satellites currently. You can use this link and click on any of the Norad IDs between 41179U through 41189U.

This is just very rough back of the envelope (for example, inclination is 47 degrees), but it suggests that the speed is in the rotating frame of the Earth. Imagine a giant x, y, z axes draw from the Earth and rotating with it.

Is this actually what it means?

• It seems Earth surface is the frame of reference, but it's not just projected as vertical speed is definitely a factor, the display speed growing rapidly at launch. – SF. Dec 27 '15 at 2:30
• Maybe speed from the launch point? – PearsonArtPhoto Dec 27 '15 at 5:24
• I think that's the right idea @SF. I added an ugly little calculation to the question along that line of thought. – uhoh Dec 27 '15 at 8:31
• I adjusted the title again - conciseness over grammar here. – uhoh Dec 27 '15 at 14:10

On-screen telemetry readings caused a bit of confusion in our chat as we were observing the launch, too:

PearsonArtPhoto: Stage 2 seems low...

So we started calculating what the speeds for target semi-major axis of 625 km (639 x 611 km / 2) and then current altitude of 622 km for circular orbits should be. Using $v_o \approx \sqrt{\mu/a}$, that came out at 27,157 and 27,163 km/h, respectively. And for the 629 km altitude that your screen is showing, that comes out at 27,149.35 km/h, but telemetry shows 25,947 km/h and slowly dropping, while the altitude was slowly climbing. Something isn't quite right, and this can't have been readings for inertial frame of reference. If the upper stage was 1,202.35 km/h or 4.4% short of its orbital speed, it would start reducing its altitude and increasing speed as it falls in a wide arc towards the Earth. Yet we saw the opposite;

So I started plugging some more values into the formula, suspecting the values given were for rotating frame of reference (i.e. downrange speed), which would make sense since the launch vehicle started at 0 speed and not the Earth's eastward rotation at 28.562106° N for SLC-40 latitude and accounting for Earth's flattening:

$$v_\text{LS} = 2 \cdot \pi \cdot 6378.14 \text{ km } \cdot cos(28.562106°) \cdot (1 - 0.0033528)\ /\ 0.99726968 \text{ day}$$

Which comes out at 1,465.65 km/h. Subtracting this value from previous results, as the launch site is rotating towards the upper stage, I get 25,683 km/h for a circular orbit at 629 km altitude. That's better! Now my calculations are off only by 264 km/h, which can be attributed to small difference in stage's azimuth with respect to the launch site during deployment, and explains why the upper stage is still slowly climbing without propulsion while telemetry readings show its speed to be slowly dropping. I.e. that is still has some excess orbital energy from the impulse burns and it will take a bit of time for it to climb the orbit, while the Orbcomm OG-2 satellites will have to remove that much speed to later circularize their final orbit.

So, while I don't have any official sources for this, it does appear that the telemetry readings were downrange speed, given in a rotating frame of reference. And the next best thing to official sources of information, here's the simulated upper stage graphs of the SpaceX Orbcomm OG-2 launch profile, made by FlightClub.io:

Target orbit there is described as:

apoapsis: 639 km
periapsis: 611 km
inclination: 47.6°
eccentricity: 0.0020

with upper stage engine cut-off at T+2004 seconds.

• OK this is getting quite interesting! Thanks! So I think this is the "rightests" answer I can expect, I'll hold off a little longer before accepting. The flightclub link is fascinating - gotta figure out what that's all about next. – uhoh Dec 27 '15 at 11:41
• Those numbers look great! The eleven Orbcomm-2 satellites can be viewed on this page of satview.org under the Norad names 41179U through 41189U. They're playing follow-the-leader, possibly centered on the Falcon 9 Stage 2 oribit at the time of deployment. They have been at peri / apo of about 614 / 656 km for a while now, inclination ~47 degrees. – uhoh Dec 27 '15 at 14:13