Spectacular deorbit burn / fuel dump from the Landsat 9 Centaur upper stage observed

click to enlarge

 

Yesterday 27 September 2021 at 18:12 UT, Landsat 9 was launched from Vandenberg with a ULA Atlas V rocket. 

2h 58m after the launch, after 1.5 revolutions and while over the east coast of the United Kingdom, the Centaur upper stage performed its deorbit burn, lowering perigee such that half an orbit later it would reenter over a designated area in the Pacific Ocean at the end of the second revolution. Following the deorbit burn, there was a fuel blow-out.

click map to enlarge

The deorbit burn and fuel blowout happened within minutes of shadow exit over NW Europe. When the resulting exhaust and fuel clouds came into sunlight, they caused a bright spectacle in the sky that was widely seen around 21:12 UT (23:12 CEST) from a.o. the Netherlands, the UK, Belgium, France and Scandinavia.

The event was anticipated: already before the launch, Cees Bassa had noted that the time of the burn coincided with a pass over NW Europe and alerted observers on the Satobs list. I then put out additional alerts on a.o. Twitter, and as a result, many people observed it. 

In addition, there were hundreds of unexpecting casual eyewitnesses, who often had no clue as to what they were seeing. One of the Dutch "UFO"-reporting sites got over 150 reports of a "UFO" in the northern sky as a result.

As seen from my hometown Leiden in the Netherlands, shadow exit would occur low in the northern sky, in Ursa Major. I had put up my camera opposite the historic Leiden Observatory in the center of Leiden, hoping to capture it over the telescope domes.

As it happened, the actual sky trajectory was slightly more eastwards in the sky than we had anticipated based on a pre-launch TLE estimate (my estimate placed in in the tail of the Big Dipper, while in reality it was in the bowl of the Big Dipper). Just enough to place it outside the FOV of my camera (and initially behind a tree). 

So when it became visible and I realized it was off the predictions, I quickly grabbed the tripod and repositioned it. This made me photographically miss the first 20 seconds or so of the event. Over slightly more than 1 minute, I managed to shoot 50 images of the exhaust and fuel clouds descending over the roof of one of the Observatory's auxilliary buildings.

I was lucky with the clouds too. Fields of cumulus were drifting across the sky, and the relevant part of the sky had been clouded out only minutes before the observation (the clouds leaving the scene are visible in the photographs and time-lapse below).

The event was downright spectacular: two v-shaped, comet-like clouds, one very bright and one fainter (see images) with the tips upward, moving down in the sky among the stars of Ursa Major. The brighter, trailing one of the two clouds was easily visible, and of negative magnitude (mag -4 perhaps, as a rough estimate). It's shape changed over time, with a shell-like structure moving away from the tip. Very spectacular!

The fainter cloud is probably rocket engine exhaust from the brief deorbit burn. The brighter cloud is a cloud of fuel particles, resulting from the blow-out (depressurization) of the Centaur's fuel tanks after the burn (this is a.o. done to avoid fuel remnants exploding). Both clouds are illuminated by the sun, which is why they are visible.

Here are some of the 50 images I shot

click images to enlarge

In two consecutive of the 50 images, an object briefly becomes visible between the fuel and exhaust clouds (arrow): it is not clear what this exactly is, as one would not expect the Centaur itself in this position (rather, at the tip of the bright cloud).

click to enlarge

Below is a time-lapse movie I constructed from the 50 images. It is at 13 times the real speed: the series of images from which the movie was made spans slightly over 1 minute in time:

The event happened somewhere between ~550 and 685 km altitude, over the United Kingdom and North Sea. An exact altitude cannot be given at the moment: landsat 9 was delivered to a ~685 km orbit, but the rocket made additional manoeuvres, while releasing cubesats.

I have always wanted to see an event like this, and now finally have (my 51 degree North NW European location does not see this kind of events often). Still on my list: a real reentry.

(all the images shown here were made with a Canon EOS 80D camera and EF 2.0/35 mm lens, at 1-second exposure at ISO 2500).

A weird Navigational Warning for a mass deorbit on August 9-10? [updated]

click map to enlarge

 

A weird Navigational Warning (NAVAREA XII 384/21) for "Space Debris" has appeared defining nine areas, some of them overlapping, in the Pacific for August 9, 16:27 to 17:29 UT and August 10, 17:16 to 18:17 UT.

I have mapped them in the map above. Below is the text of the Navigational Warning:

060929Z AUG 21
NAVAREA XII 384/21(GEN).
EASTERN NORTH PACIFIC.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
   091627Z TO 091729Z AUG, ALTERNATE
   101716Z TO 101817Z AUG
   IN AREAS BOUND BY:
   A. 22-52-40N 137-34-57W, 20-12-47N 134-02-08W,
      04-25-05N 146-28-48W, 06-54-48N 149-55-52W.
   B. 51-11-05N 141-36-54W, 49-40-18N 142-13-53W,
      50-44-15N 170-19-30W, 52-17-11N 170-39-50W.
   C. 12-58-15N 130-00-21W, 10-52-28N 127-06-04W,
      05-17-31S 138-47-34W, 03-13-54S 141-40-25W.
   D. 48-12-47N 135-38-42W, 46-20-17N 136-55-43W,
      50-55-14N 165-28-28W, 52-59-09N 165-19-24W.
   E. 13-53-47N 126-52-33W, 11-46-05N 123-56-09W,
      04-19-41S 135-37-56W, 02-14-45S 138-32-32W.
   F. 49-27-33N 135-51-45W, 47-43-47N 136-53-00W,
      50-56-51N 168-09-57W, 52-48-04N 168-20-28W.
   G. 14-27-06N 127-19-28W, 12-18-52N 124-23-30W,
      03-36-29S 136-03-34W, 01-31-24S 138-57-30W.
   H. 49-46-04N 136-40-41W, 48-05-08N 137-37-30W,
      50-55-01N 168-54-51W, 52-42-19N 169-08-13W.
   I. 31-49-12N 124-20-42W, 30-20-18N 122-34-43W,
      22-47-14N 130-25-52W, 24-10-15N 132-10-44W.
2. CANCEL THIS MSG 101917Z AUG 21.

The nine areas A to I cluster in basically three regions (which I have colour-coded in the map above).

The directions of the areas point to a series of deorbits from a 51-53 degree inclined Low Earth orbit. As I have indicated in the map in top of this post, two of the three defined regions with warning boxes line up with the ISS groundtrack during the two time windows given, but I think this is coincidence (and the series of boxes south of Alaska do definitely not line up with the ISS during these two time windows. In fact, this points to deorbits from at least two different orbital planes).

Rather, my suspicion is a mass deorbit of Starlink satellites, who move in ~53 degree inclined orbits [but see update below].

UPDATE: 

After some discussion, Jan Hindrik Knot rightfully questioned whether Starlink satellites, with their ion thruster propulsion, are capable of a controlled deorbit in a designated area at all. That is a good point, which I overlooked initially.

So it appears we have no idea what will be deorbitted on August 9-10.

The combination of the areas in the mid-Pacific and those south or Alaska, to me point to deorbits from at least two different orbital planes (both inclined 51-53 degrees).

Note that, from the position of the areas, the fact that their shapes clearly point to deorbits from Low Earth Orbit, and that the NavWarning mentions time windows on two successive dates, it is clearly not related to this deorbit  (the Spectr-R rocket booster) from Deep Space either.

UPDATE 2:

The plot thickens: the on-line KML version of the Navigational Warning has appeared and mentions: 

"Authority: NASA 300917Z JUL 21"

(the versions sent to subscribers to the service doesn't mention the authorities issuing the warnings).

So it appears to be something NASA-related (HT to @john_moe on Twitter).

One possibility could be that these are emergency landing zones for Starliner (which was to be launched on July 30, the date mentioned in the "Authority:" line: but was scrubbed). Still open questions though: why August 9 and 10? Why where these same zones not published before the July 30 launch date? Questions, questions...

UPDATE 3:

I like the suggestion by Bob Christy that these are warnings for the reentry of the Starliner service module (that is jetissoned from the Starliner capsule before landing of the latter). That makes sense.

Proton-M rb (2021-066B) reentry forecast (updated)

 (this post is updated when I have run new predictions)

click diagram to enlarge

The Proton-M third stage from the July 21 Nauka launch (see previous post) is coming down fast. The current reentry forecast models place the reentry into the atmosphere in the early hours of August 6 UT.

The diagram above shows CSpOC TIP data in red, and my own GMAT model results in black. My GMAT predictions in tabular form:

DATE         UT    +-        LAT    LON    orbit epoch
6-8-2021     9:55  1.8  day                28-7-2021 12:12
6-8-2021    16:51  1.7  day                29-7-2021 06:01
6-8-2021     9:18  1.4  day                30-7-2021 04:16
6-8-2021     8:29  1.2  day                31-7-2021 05:28
6-8-2021     9:47  1.0  day                 1-8-2021 05:09
6-8-2021    18:23   23  hr                  1-8-2021 22:54
6-8-2021    21:00   23  hr                  2-8-2021 03:19
6-8-2021    13:52   17  hr                  3-8-2021 00:31
6-8-2021    11:44   14  hr                  3-8-2021 16:12
6-8-2021     9:29   11  hr    15 S  177 W   4-8-2021 00:05
6-8-2021     7:50    8  hr    19 N  180 W   4-8-2021 15:44
6-8-2021     6:40    6  hr    38 S  108 W   4-8-2021 23:04
6-8-2021     6:26    5  hr     4 N  146 W   5-8-2021 03:27
6-8-2021     2:56  2.9  hr    25 N  112 E   5-8-2021 12:14
6-8-2021     5:07  2.5  hr    22 S  104 W   5-8-2021 16:37
6-8-2021     5:34  1.7  hr    29 S   24 E   5-8-2021 21:00
6-8-2021     4:49  1.6  hr    32 N  148 W   5-8-2021 21:00*

The last orbit was re-issued with an epoch almost similar to the previous orbit. This orbit is indicated by an asterisk and my final forecast.

Within current uncertainty windows, no meaningful prediction can be given about the location of the reentry yet. The values nevertheless listed in the tabe for latitude and longitude are nominal values only for the middle of the quoted uncertainty interval (which spans multiple revolutions around the Earth). Given the current uncertainty intervals, they are basically meaningless. Only an hour or so before the actual reentry, the uncertainty interval becomes less than one revolution.

The map below shows the nominal GMAT and last pre-reentry CSpOC TIP positions, plus the trajectory over the uncertainty window [EDIT: see update with final TIP at end of post!!!!]:

 

click map to enlarge

The rocket stage has a dry mass of about 4 tons and is about 4 x 4 meter wide. The diagram below shows the evolution of the orbital altitude of the rocket stage so far, based on CSpOC tracking data. Perigee is the lowest point in it's elliptical orbit around earth, apogee the highest point. Altitudes refer to the equatorial radius of the earth.

 

The last few orbits shows signs of trouble in determining the (quickly evolving) orbit (look at the perigee values for the last four orbits issued). The last available orbit was issued in two versions

 

click diagram to enlarge

 

On July 21, a few hours after launch, I filmed the Proton rocket stage during a pass over Leiden, accompanied by three pieces of debris that were never catalogued by CSpOC:

 

(EDIT: see update below movie!)

UPDATE: 

The final CSpOC TIP is in: 4:46 +- 1m UT (August 6) near 37.8 N 155.7 W, north of Hawaii (this is probably based on a SBIRS detection of the reentry fireball, given the very accurate +- of 1 minute).

This is very close to my last nominal GMAT estimate (4:49 UT near 32 N 148 W)! 

In all honesty: given the uncertainty intervals, that very good match is down to pure luck....

click map to enlarge

From what altitude does space debris drop vertically?

While gearing up for the CZ-5B reentry in the first week of May, an interesting exchange developed on Twitter between @SpaceTrackOrg, @DutchSpace and me, regarding the way space debris falls down in the last few tens of kilometers before hitting ground surface. 

It was triggered by the comment by @SpaceTrackOrg that the coordinates in their TIP messages typically refer to the object at 10 km altitude, not ground level:

As I pointed out in the Twitter thread, increasing drag acting on the fragments during reentry will not only make them start to ablate (and fragment), but will also slow them down, to a point where they finally have lost all initial forward momentum. From that point onwards they drop straight down.

During that tweet exchange, I decided to prove my point to initial disbelievers with a General Missions Analysis Tool (GMAT) model. I constructed an orbit for a hypothetical satellite about to reenter. I next ran this object through a GMAT model, modelling descent through the MSISE90 model atmosphere: initially for a 10 kg mass and 1 m² drag surface, but later I ran the model for 5 kg and 50 kg masses too, capturing a range of area-to-mass ratio's. The initial speed was orbital (7.4 km/s) and the starting orbital altitude was 80 km, just below the tipping point between orbital and suborbital altitude (in this way, rapid reentry in the model was assured).

The movement in latitude and longitude from the model output was next converted to movement in meters at the earth surface (I did this in QGIS), i.e. horizontal displacement, yielding this diagram that maps the horizontal component of movement of each fragment against atmospheric altitude:

click diagram to enlarge

As can be seen, all three objects indeed reach a point where horizontal movement becomes essentially zero - they drop down vertically from a certain point. 

These points where the horizontal movement becomes zero are located at about 45 km altitude for a 5 kg object  (with a 1 m² drag surface), about 35 km for a 10 kg object (with 1 m² drag surface), and about 25 km for a 50 kg object  (with 1 m² drag surface).

So our GMAT model demonstrates what I argued: from a certain point, well above 10 km atmospheric altitude, fragments from a reentry loose their forward momentum and basically start to drop down vertically, essentially a free fall.

But the reality is, of course, a bit different and more complex than this model suggests. Apart from atmospheric drag and gravity, there is another force that starts to act on these fragments once in the (upper) atmosphere, one that GMAT does not account for. The force in question is high altitude winds, which above 50 km altitude can be very strong.

So the reality is, that these high altitude winds at a certain point start to become the main force of horizontal displacement - fragments are litterally being blown away by these winds. As a result, the actual fall from the mentioned altitudes is not straigth down: falling fragments can be blown away laterally from the initial trajectory, or foward along the trajectory, and even be blown backwards along the initial trajectory, depending on the direction of the high altitude winds! The displacement, especially for fragments that are relatively large for their mass (space debris fragments usually are, as they usually are not solid), can be many kilometers.

This effect is well known to meteor astronomers, as it is a complicating factor in calculating where any meteorite fragments from a fireball might have landed. Like space debris, meteorites likewise are slowed down once descending through the atmosphere, and from ~25 to ~15 km altitude (their initial speed is faster than that of space debris and they are more dense, hence they penetrate deeper before losing their cosmic speed) they start the same kind of free fall, moving primarily under the effects of high altitude winds.

As an aside: I would love to see someone add the capability to import and effect high altitude wind profiles into GMAT, so this kind of displacement could be modelled in GMAT!

Note that, in interpreting the diagram above, one should realise that it maps horizontal displacement relative to altitude in the atmosphere. The modelled fragments do not end up in the same geographic location. 

For a given drag surface, low mass objects will come down earlier along the trajectory than heavier objects. This can be seen in the diagram below, which also shows you that the debris footprint of a reentry can easily be hundreds of kilometers long, something to keep in mind when looking at reentry coordinates in TIP messages:

 

click diagram to enlarge

It takes quite a while for these objects to come down through the lower layers of the atmosphere too, especially if they are large but lightweight:

click diagram to enlarge

The actual fall durations are heavily influenced by the area-to-mass-ratio. Relatively solid fragments (low area-to-mass) will come down faster, sheet-like or hollow objects (high area-to-mass) will come down slower. Surviving fragments will trickle down over tens of minutes. This is one reason why the time windows given for hazard areas during a controlled rocket stage reentry are usually an hour or so in duration.

From meteoric fireball studies, we know that as a rule of thumb, ablation (mass loss, i.e. burning up) of fragments stops once their speed is below ~3 km/s. Note that for low melting point materials like aluminium, the speed might actually be somewhat lower (meteorites are rock or iron with melting points at ~1100-1500 C, while aluminium has a melting point at ~660 C).

For the three modelled fragments (all modelled for a drag surface of 1 m²), the 5 kg fragment reaches this point at 77 km altitude; the 10 kg fragment at 73 km altitude; the 50 kg fragment at 61 km altitude. Note that the results will be different when modelling with the same masses but a different drag surface (for a smaller drag surface, the altitudes for a given mass will get lower, as they don't slow down as rapidly). Also note my earlier remark about materials with low melting point temperatures. But in general: anything that survives to below ~50 km in the atmosphere, will probably reach ground surface.

Reentry predictions for the Chinese CZ-5B rocket stage 2021-035B [UPDATED]

UPDATE:

CSpOC/18th Space Control Squadron report that the CZ-5B rocket booster 2021-035B met a fiery end at 2:14 UT last night (May 9) over the Arabian peninsula and Indian Ocean. China reports reentry at 2:24 UT in the Indian Ocean near the Maldives

click map to enlarge

UPDATES 9 May 2021, 9:00 UT and 14:30 UT:

In the map above, I have plotted the approximate final trajectory (based on a SatEvo-evolved orbit propagated to reentry) and both the reentry locations reported by China (2:24 UT, 2.65 N, 72.64 E, in the Indian Ocean near the Maldives) and by CSpOC/18th Space Control Squadron (2:14 UT, 22.2 N 50 E, over the Arabian Peninsula).

Note how within minutes of the reentry, the rocket passed over the city of Riyahd in Saoudi-Arabia!

In looking at the plot, one should realize that a reentry is not an instantanious moment, but a process stretching over many minutes, where the object starts to break up and fragments burn up in the upper atmosphere. During this process, the object continues to move over a swat of trajectory that can be hundreds to a few thousands of kilometers long. It is very likely that this proces started over the Middle East or even over the Mediterranean already [edit: imagery from Jordan suggest that the object was still intact when passing over that location, but see a potential video from Oman below]. If fragments survived, they are scattered somewhere along the yellow line in the map, within the current uncertainties of the reentry location.

The video footage in the tweet below appears to show the (start of the) reentry, imaged from Oman, but is unverified for now:

وأخيرا سقط حطام #الصاروخ_الصيني

فيديو من سلطنة عمان يبين بداية دخوله للغلاف الجوي.

بحسب مصادر صينية، سقط الحطام في المحيط الهندي شمال المالديف.

بحسب مصادر أمريكية دخل الغلاف الجوي الساعة 02:14 أثناء مروره فوق سلطنة عمان وسقط الحطام أخيرا شمال المالديف. pic.twitter.com/aR6FEUHMd0

— مركز الفلك الدولي (@AstronomyCenter) May 9, 2021

I have tried, by fiddling with the area-to-mass ratio for the rocket in GMAT, to create a reentry trajectory that would match a splashdown in the Maldives around 2:24 UT, as reported by China. The closest I can get to the location reported by China is this result:

click map to enlarge

Of course, this is a simplified model (the proverbal "spherical cow in a vacuum") that does not take into account both mass loss from ablation and fragmentation over the reentry trajectory.

It however suggest that, if the time and location reported by China is right, the rocket stage would have been at an altitude of ~100 km around the position and time reported by CSpOC (the US military tracking network). It could be that the CSpOC position, with the quoted very small uncertainty in time of +- 1 minute, is based on a SBIRS satellite detection of the fireball (we have long suspected that TIP's with such 1-minute uncertainty quotes are based on satellite detections of the reentry fireball). 

About 100 km is a fair altitude for the ablative phase to start, similar to the altitude at which meteoric fireballs start. If the video from Oman above is the real deal, it is indeed suggested that ablation (and break-up) was starting over southern Arabia.

As a further update: interesting information about infrasound detections of the reentry from Djibouti, with source over the Arabian peninsula:

#CTBTO #IMS infrasound station IS19 #Djibouti🇩🇯 recorded an emergent, low-frequency signal of an object traveling at ~10000 km/h, compatible w/ re-entry of part of the #LongMarch5BRocket 🚀 over Arabian peninsula on 9 May @ 2:15 UTC & splash down in #IndianOcean near #Maldives pic.twitter.com/mlUlxtDI4b

— Lassina Zerbo (@SinaZerbo) May 9, 2021

[end of update]

(below is the  pre-reentry  version of this frequently updated post):

(this part below last updated 8 May 23:00 UT)

On 29 May  April, China used a CZ-5B rocket to launch the core module of it's new Space Station Tianhe-1 ("Harmony of Heavens-1"). The module was initially placed in a 41.5 degree inclined, 382 x 171 km orbit and subsequently raised to a 385 x 352 km orbit.

The massive CZ-5B core stage from the CZ-5B rocket used for this launch was left in a 375 x 170 km orbit. Like it's predecessor that flew in May 2020, it was not deorbited after payload release. This likely means that it will come down in an uncontrolled reentry somewhere on May 8 or 9.

Compared to 'normal' rocket upper stages (which are typically 3 to 10 meters long and say 1000-2500 kg in mass), the CZ-5B core stage is huge. It is 31 meters long, 5 meters in diameter, and very heavy: sources differ on the dry mass, but it is somewhere between 17 and 22 tons.

 

The informal Space industry standard for objects that are heavier than 10 tons, and launched into Low Earth Orbit, is to have a deliberate deorbit over an empty stretch of Ocean. This did not happen with the CZ-5B core stage from the 5 May 2020 launch a year ago, and does not seem to happen now following the Tianhe-1 launch either.

An uncontrolled reentry of an object this large and heavy means that sizable fragments can survive reentry and reach the surface of the earth, with the risk that this happens over inhabited parts of the world. This is not something that you want, from safety concerns. Several analysts have gone on the record calling the lack of a controlled reentry for the CZ-5B core stage 'irresponsible' for that reason.

I’ll just reiterate that uncontrolled re-entries of large rocket stages in 2021 is absolutely irresponsible behavior https://t.co/Q6RZAyFPpZ

— brianweeden (@brianweeden) April 30, 2021

Indeed, there are risks. For example, sizable fragments from the core stage of the previous CZ-5B launch, that also came down in an uncontrolled reentry, rained down on well populated parts of Ivory Coast in Africa in May 2020.

With the first lauch and uncontrolled reentry of a CZ-5B core stage a year ago, the question was whether a deliberate deorbit was planned but failed, or whether the CZ-5B core stage simply does not have a deorbit capability. As history now seems to repeat with this second CZ-5B launch, it starts to look like the CZ-5B indeed has no deorbit capability. This is highly surprising, and, indeed, irresponsible imho.

At the same time, while there is a risk (see what happened a year ago in Ivory Coast), the risk should not be overstressed. The risk that a random passenger aircraft ends up falling on your house is still orders of a magnitude larger, and we all have come to accept that risk.

We should also realize that much of the 17 to 22 tons mass of the stage will burn up before it reaches earth surface. Moreover, as a large part of the Earth consists of Ocean, it is likely that it will come down harmlessly over some Ocean.

Yet, it cannot be excluded that it will come down over a populated area, so some worry is justified. With an orbital inclination of 41.5 degrees, locations between 41.5 N and 41.5 S are in the danger zone for this reentry. The danger is slightly elevated at the extremes of this (41.5 N and 41.5 S). The latitude range where the CZ-5B booster can come down includes the whole of the United States, Australia, Africa, the southern parts of Asia and much of southern America. Europe is mostly safe, except for Spain, Italy and the Balkans:

 

When the reentry happens, the rocket stage will break up in the atmosphere and any surviving parts that have not burned up completely will rain down along the ground path along a very long stretch of earth: the area where fragments fall down can be hundreds of kilometers long.

 

PREDICTIONS

The diagram in the very top of this post gives reentry predictions. I will update it every time I run a new prediction. Below are the same predictions in table form. They are based on modelling of the orbital evolution in the General Mission Analysis Tool (GMAT).

Modelling is done for a mass of 17 tons (note that the true dry mass of the rocket stage is a bit uncertain: quoted values range between 17 and 22 tons, depending on the source) and with a drag surface at 60% of the maximum surface, as I have found that this generally fits well with tumbling rocket stages (which as a result of the tumbling have a variable drag surface). 

Each new prediction is based on a new orbital update from CSpOC. The MSISE90 model atmosphere is used, with past, current and estimated future Space Weather.

Note that these predicted reentry times are nominal values only. PLEASE NOTE THE VERY LARGE UNCERTAINTY IN THESE TIMES! 

The uncertainty margins shown are calculated as 20% of the time between the orbital epoch on which the prediction is based, and the predicted reentry time.

Note that the nominal position shown is only nominal: it is for the center of the uncertainty interval, but as long as the uncertainties in the reentry time measure in the hours, it is basically meaningless.

 

DATE      *NOMINAL* TIME        (issued)     (*nominal* position)

8 May     19:23 UT +- 22 hr     (May 4.22)

8 May     21:23 UT +- 21 hr     (May 4.46)

8 May     20:40 UT +- 21 hr     (May 4.53)

8 May     19:41 UT +- 20 hr     (May 4.59)

8 May     20:46 UT +- 18 hr     (May 5.08)

8 May     21:36 UT +- 18 hr     (May 5.20)

8 May     21:18 UT +- 16 hr     (May 5.51)

9 May     00:10 UT +- 16 hr     (May 5.58) 

9 May     04:40 UT +- 13 hr     (May 6.50)

9 May     03:52 UT +- 10 hr     (May 7.18)

9 May     04:01 UT +-  9 hr     (May 7.36)

9 May     03:36 UT +-  5 hr     (May 8.17)

9 May     03:10 UT +- 3.5 hr    (May 8.40)   (07 N 108 W)

9 May     03:11 UT +- 1.8 hr    (May 8.77)   (11 N 103 W)

9 May     02:54 UT +- 1.3 hr    (May 8.86)   (31 S 155 W) 
 

Uncertainties in the predicted reentry times will remain very large untill very shortly before the actual reentry.

click map to enlarge

Within the 2 hour wide uncertainty window of the current CSpOC TIP (9 May 2:04 UT +- 1 hr), which no doubt is more reliable than my amateurish efforts, the rocket stage can come down anywhere on the lines drawn in the map above (the lines show the rocket's trajectory over the uncertainty window). Within the risk window, the trajectory runs over central America, southern Europe, Arabia and the southern tips of Australia. China itself now appears to be out of the risk zone, ironically enough. The nominal point (but: with such a wide uncertainty that it is still basically meaningless!!!) is over Spain

The yellow dots in the map are those cities with populations of a million or more between 41.5 N and 41.5 S.

Other sources of predictions:

Most notably: Space-Track (the CSpOC portal: requires an account), which should be regarded as the most authoritive one.

Also: EU SST on Twitter

...and otherwise: Joseph Remis on Twitter, and Aerospace Corporation 

(note how all of these give somewhat differing forecasts: which shows you how difficult these reentry forecasts are!)

Several years ago I wrote a FAQ about reentries, and reentry predictions, that might answer any questions you have.

I will update this post with new data when I have the opportunity.

[UPDATED] Reentry predictions for the Falcon 9 RB 2021-017BN

click diagram to enlarge

In my previous post, I discussed 2021-017BN, the Falcon 9 upper stage from the March 4 Starlink launch that should have been deorbitted after 1.5 revolutions on March 4th, but didn't.

It is still on orbit. At the moment of writing, 23 March 2021 at 11:00 UT, it is in a 217 x 200 km orbit according to the latest available elements from CSpOC, and it will stay on orbit for a couple of days to come. But the end is near: the orbital altitude of the rocket stage is quickly decaying, as can be seen in the diagram below:

click diagram to enlarge

My current reentry prediction (see diagram in top of post and table below) is that it will come down in the early hours of March 26 (2021). My prediction, based on modelling in GMAT R2020a using the MSISE90 model atmosphere, appears to be well in line with the TIP from CSpOC so far.

[UPDATE: my final post-cast predicted reentry at 26 Mar 04:34 UT, which is some 35 minutes too late. It is based on a 2/3rd maximum drag surface value. Interstingly, using the maximum drag surface leads to a reenrty at 3:56 Ut, within minutes f the actual time]

Revisit this post for prediction updates in the coming days.

orbit epoch     pred. date     reentry time (UT)
21081.600725    26 Mar 2021    02:33 +- 16.8 hr
21081.922054    26 mar 2021    03:36 +- 15.5 hr
21082.113317    26 Mar 2021    03:59 +- 14.7 hr
21082.216601    26 Mar 2021    03:40 +- 14.1 hr
21082.278149    26 Mar 2021    03:43 +- 13.8 hr
21082.462749    26 Mar 2021    05:29 +- 13.3 hr
21082.585776    26 Mar 2021    05:29 +- 12.7 hr
21082.708770    26 Mar 2021    05:37 +- 12.1 hr
21082.954651    26 Mar 2021    06:13 +- 11.1 hr
21083.138960    26 Mar 2021    05:03 +-  9.9 hr
21083.261785    26 Mar 2021    05:15 +-  9.4 hr
21083.296296    26 Mar 2021    05:20 +-  9.2 hr
21083.507296    26 Mar 2021    05:28 +-  8.3 hr
21083.875164    26 Mar 2021    05:26 +-  6.5 hr
21084.120127    26 Mar 2021    05:59 +-  5.4 hr
21084.181325    26 Mar 2021    05:20 +-  5.0 hr
21084.486963    26 Mar 2021    05:00 +-  3.5 hr
21084.548018    26 Mar 2021    03:19 +-  2.8 hr
21084.974688    26 Mar 2021    04:46 +-  1.1 hr * post-cast
21085.095602    26 Mar 2021    04:34 +-  0.5 hr * final post-cast

UPDATE  26 March 2021  12:30 UT:

The reentry happened last night, over North America, and was widely seen from the US States Washington and Oregon, near 4:00 UT (March 26 UT: that is 9 pm on March 25 local time for that area).

CSpOC's final TIP places the reentry at 03:58 +- 1 min UT. This time matches the reports from Washington and Oregon well, and based on the last orbit it would indeed place the rocket stage near the NW United States coast.

The listed geographic position in the TIP, 24.5 N, 151 W, does however not match well (it is further down the track, near Hawaii, corresponding to the Falcon 9 position about 6 minutes prior to the observed reentry). We have  noted such discrepancies more often in recent TIP messages. In this case, I half suspect the position was that given by their reentry model, and they forgot to update it when the SBIRS detection of the actual reentry fireball came in.

click map to enlarge

My own final "post-cast" places reentry some 35 minutes after the actual reentry.

Here are some of the reentry sightings as reported on Twitter:

DID YOU SEE THIS? I have never in my life seen something so incredible. I am in awe. Just happened over Portland about 10 minutes ago. #LiveOnK2 pic.twitter.com/L9wLEXBrcW

— Genevieve Reaume (@GenevieveReaume) March 26, 2021

uuuuuhhhh holy shit we just saw this meteor shower across the sky?!?! #pdx pic.twitter.com/umaE0joW7J

— lynseylou (@lynseylou) March 26, 2021

 

UPDATE 2 April 2021 23:00 UT:

Debris has been recovered from this reentry. In Grant Country, Washington, a Composite Overwrapped Pressure Vessel (COPV) was found on farmland.

 

 

SpaceX recovered a Composite-Overwrapped Pressure Vessel from last week’s Falcon 9 re-entry. It was found on private property in southwest Grant County this week. Media and treasure hunters: we are not disclosing specifics. The property owner simply wants to be left alone. pic.twitter.com/dEIQAotItY

— Grant County Sheriff (@GrantCoSheriff) April 2, 2021

Apparent failed deorbit of the Starlink-18 Falcon 9 upper stage [UPDATED]

On 4 March 2021, after several delays, SpaceX launched the 18th Starlink batch (Starlink-18 or V1.0-17). While the launch and deployment profile appears to have been similar to other recent Starlink launches, it appears that something went wrong with the Falcon 9 upper stage near the end of its mission.

On March 8th, Polish observer Adam Hurcewicz reported a bright, fast object in the orbital plane of this launch, passing a few minutes before the main Starlink "train". It was seen on subsequent nights and by other observers as well: the video above is from the early morning of March 9. At it's brightest, this fast moving object reportedly reaches mag -3. It does not appear to match a known object from earlier launches. It also didn't match supplementary TLE's for the Starlink-18 payloads from Celestrak (which are based on State Vectors from SpaceX). The Polish observers therefore speculated it was the Falcon 9 upper stage from the launch. 

But that would be against expectations. The Falcon 9 upper stage normally does not stay in orbit: it is de-orbitted soon after payload release, usually about 1.5 revolutions (about 2.5 hours) after launch. So if this object is the Falcon 9 upper stage, this suggests  something went wrong and it failed to deorbit.

The speculation that this object is the Falcon 9 Upper Stage can now be bolstered by additional information. The first orbital element sets for this Starlink launch have appeared on the CSpOC portal  Space-Track late yesterday (11 March), with catalogue numbers ranging from 47722 to 47786. And they show an extra object!

With Starlink launches, 64 objects are usually catalogued: 60 payloads and four 'Falcon 9 debris' pieces. The latter 'debris' pieces are the payload stack retaining rods: four metal rods which keep the satellite stack together on top of the upper stage. They are jettisoned upon payload release.

An elset for the Falcon 9 upper stage is usually not released by CSpOC: as it normally stays on-orbit for barely more than 1 revolution, it is not catalogued.

But this time, not 64 but 65 objects have been catalogued. The extra 65th object must be the Falcon 9 upper stage, and it indicates it stayed on orbit for more than a few revolutions. Which lines up with the observations by the Polish (and later also other) observers.

Although the 65 objects, at the moment of writing, do not have been individually ID-ed by CSpOC yet (all have the temporary designation "TBA - TO BE ASSIGNED"), the 60 payloads, four retaining rods and the upper stage as such can be clearly identified among them. The objects separate in 3 groups in terms of orbital altitude. The 60 payloads all have (for orbits with epoch 12 March) a perigee above 280 km. The four retaining rods have clearly lower orbits: their perigee is near 243-246 km and apogee near 268-278 km.

The 65th object, which by inference must be the Falcon 9 upper stage, is in a still lower orbit . It has the smallest semi-major axis of all of them with perigee near 237 km and apogee near 270 km. The orbit for this object, catalogue nr 47782 (2021-071BN) also closely matches the observations by the Polish observers.

So why is the Falcon 9 upper stage still on-orbit? It suggests of course that the deorbit went not as planned, i.e. it failed for some reason (e.g. the rocket engine refusing to restart).

That the Falcon 9 upper stage should have deorbitted on March 4, after 1.5 revolutions, is clear from the Navigational Warnings that were issued in connection to this launch. Navigational Warning HYDROPAC 695/21 delineates the usual elongated deorbit zone in the Indian Ocean familiar from earlier Starlink launches:

 

021948Z MAR 21
HYDROPAC 695/21(GEN).
SOUTHERN INDIAN OCEAN.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
   041024Z TO 041326Z MAR,
   ALTERNATE 051004Z TO 051306Z MAR
   IN AREA BOUND BY
   29-43S 060-07E, 24-55S 064-27E,
   38-45S 084-30E, 45-12S 099-45E,
   49-46S 119-13E, 50-42S 138-19E,
   48-50S 156-44E, 51-46S 158-08E,
   54-42S 148-32E, 56-20S 131-03E,
   55-52S 107-50E, 49-11S 085-05E,
   34-32S 064-13E.
2. CANCEL HYDROPAC 685/21.
3. CANCEL THIS MSG 051406Z MAR 21.

I have plotted the zones from the Area Warnings connected to the launch in this map, along with the groundtrack for the first 1.5 orbital revolutions. The large elongated red zone in the southern Indian Ocean is the planned deorbit area from Navigational Warning HYDROPAC 695/21:

click map to enlarge

The position of the reentry hazard zone indicates a reentry was planned around 10:55 UT (March 4), 1.5 revolutions (2h 30m) after launch, following a deorbit burn some 30 minutes earlier.

But the deorbit evidently did not happen as it should have: the upper stage is still orbiting as we speak, a week after launch. The issued Navigational Warning for the deorbit hazard zone strongly suggests this is not intentional.

So how long will the upper stage stay in orbit? The current orbit is low (237 x 271 km), and the object is large (16 x 3.66 meter, with a mass of 4.5 tons) so eventually the rocket stage will have an uncontrolled reentry, somewhere between latitudes 53 deg N and 53 deg S. 

A first assessment using both SatEvo and a GMAT simulation suggests that the reentry will probably happen in the last few days of March or the first few days of April.

UPDATE 14 March 2021:
CSpOC has now added identifications to the objects, and indeed object 47782 is now listed as "Falcon 9 RB"

No, this reentry footage is not a fireball that appeared over Mexico on September 6/7

 

 

On 7 September 2020 near 2:14 UT (6 September 22:14 local time) a bright fireball appeared over Mexico, creating some media attention. As part of that attention, a video surfaced and was widely  retweeted, purporting to show this fireball. The image above is a screenshot of this video.

However: the object on this video is not the fireball from 7 September 2020. 

It is an 'old' recycled video from July 2020, showing a space debris reentry.

The video shows a very slow fragmenting object that is clearly reentering space debris. There was something familiar to it, which was one thing that raised my suspicion (I thought I had seen it before). The other thing that raised my suspicion was that this video clearly does not show the same object as other videos that showed up, which show the genuine September 7 fireball (like this one) .

Doing a Google Reverse Image Search quickly turned up Reddit posts from July 2020 (e.g. this one), featuring this same video, indicating that the footage was at least 2.5 months old (and hence definitely not the fireball of 7 September, confirming my suspicions).

The video does show a genuine reentry. The reentry in question happend on July 18th, 2020. The Reddit post linked above is from that date. Other video's of clearly the same reentry that was also seen from the USA posted on that date exist too.

And this is why the video looked so familiar to me: back in July I already identified footage of the same reentry as the reentry of a Russian Soyuz rocket stage (2019-079C), the second stage from the Soyuz rocket that launched the military Kosmos 2542 satellite on 25 November 2019. 

According to a CSpOC TIP message from July 18th 2020, this rocket stage reentered on 18 July 2020 07:02 UT (+/- 1 minute: this time accuracy indicates a SBIRS or DSP infra-red detection of the reentry) near 26.8 N, 101.2 W, over Northeast Mexico near the border with Texas. The map below depicts the final trajectory of the rocket stage and the CSpOC reentry position:

 

Click map to enlarge

This case highlights again that footage appearing on Twitter or other social media after an event  is not always what it purports to be, and one should always check whether it shows what it purports to show.

The Kosmos 482 Descent Craft: imaging an old Soviet Venera probe stuck in Earth orbit

click to enlarge

 

On May 7 I imaged a pass of the Kosmos 482 Descent Craft (1972-023E), using the WATEC 902H camera and a SamYang 1.4/85 mm lens. This is a very interesting object on which I have blogged earlier.

It is the ascend module of a 1972 failed Soviet Venera probe, meant to land on Venus but stuck in Earth orbit after its apogee kick engine failed to push it into Heliocentric orbit towards Venus in 1972. This is the video from (a part of) the May 7 pass of this object:




The object on the video, at that time at an altitude of about 1640 km and range of 1845 km, is about 1 meter large and weighs 495 kg. It should look like this:

photo: NASA. Click to enlarge

The photo above is not Kosmos 482 itself, but an exhibit replica of a sister ship, the Venera 8 landing module in its protective shell. Venera 8 was launched four days before Kosmos 482, and unlike the latter it was successful and did reach Venus.

The failed Kosmos 482 probe still in Earth orbit was launched from Baikonur on 31 March 1972, and put in a highly elliptical 220 x 9200 km parking orbit around Earth. It's apogee kick engine next failed to push it into a heliocentric orbit towards Venus, and the spacecraft then broke up into four pieces.

Three of these four pieces have already reentered, the fourth, that is believed to be the landing module in its protective shell, is still on-orbit and is the object I imaged. It's apogee altitude has been lowering significantly since 1972.  The object will probably reenter somewhere around late 2025 or early 2026: I wrote an extensive blog post about it including a lifetime simulation a year ago.

The diagram below is from that post and shows the observed orbital decay up to March 2019, and the future decay (light blue) that I modelled with GMAT:

click diagram to enlarge

The interesting thing is that the Kosmos 482 Descent Craft might survive reentry largely intact! It is, after all, a lander that was meant to survive ascend through the thick atmosphere of Venus. It's parachute system will probably no longer function (so it will impact rather than land), but we can expect the hardware to reach Earth surface largely intact.

From a Space Heritage point of view, both this and its history makes this 48-year-old piece of Soviet Space hardware a highly interesting object. This is material culture that represents humanities' babysteps in the exploration of other planets.

Which makes this an interesting object to image, from a "Space Archaeology" viewpoint, and an interesting object to keep an eye on the coming years, until it reenters about six years from now.



Added Note,  9 May 2020 13:30 UT:

In response to my statement that the object likely is the lander in its enclosing protective shell, several people have pointed me to telescopic imagery that purportedly would show that a part of the main bus is still attached.

I (and many others in the amateur satellite community - we had a heated discussion on it on the Satobs list a few years ago) distrust imagery of this kind. This is imaging at the edge of resolution, in this case also notably from a non-stable imaging platform (handtracking a moving object at the limit of resolution!). It unfortunately includes cherrypicking frames. It is very difficult to objectively determine what is real detail and what is artefact of the imaging procedure. It is easy to overinterpret.

I also want to note that taking the mass and dimension of the lander only, actually give a very good fit to the observed orbital decay.

The reentry of the Soyuz r/b 2020-026B over Spain and Portugal

This morning, Jon Mikkelson (@Itzalpean) drew my attention to this Twitter message:

Meteoro sobre A Coruña pic.twitter.com/OHa6dNfYmA

— Israel Borja Nuñel Timiraos (@Canaan_1983) April 28, 2020

The movie was shot from A Coruña in NW Spain this morning (28 April 2020) around 6:45 local time, which equates 4:45 UT. It clearly shows space debris reentering and breaking up.

Here are a few screenshots from the video:

A brief look in the CSpOC TIP messages showed a very clear candidate: 2020-026B, the upper stage from the Soyuz rocket that launched Progress MS-14 to the ISS on 25 April.

The CSpOC TIP lists the reentry for this object at 4:45 +- 1 minute UT for 28 April, near 38.4 N, 15.5 W, west of Portugal. This matches both time and location of the Spanish movie well.

Below is a map I created showing the final revolution of this rocket stage. The red circle is the nominal CSpOC position for the reentry (we suspect these "+-1 minute" positions are based on SBIRS detections). A Coruña where the video was shot is also indicated in the map.

Note that an observer in A Coruña looking towards the trajectory would see it move from right to left (towards the east), and this matches the video. Also note that while CSpOC gives an instantanious time in its TIP messages, reentries in reality take some time (several minutes). The object would pass A Coruña about 2 minutes after the nominal CSpOC time, which is well within a typical reentry duration.

click map to enlarge

Addition 17:15 UT (28 April):

For clarity: the trajectory above was created by taking the last available orbital elements for 2020-026B (elset 20119.06935500) and evolving these to a final decay orbit with SatEvo.


Here is a second video of the event:

California 30 January 12:30 UT: the "space debris" reentry that wasn't

On 30 January 2020 near 12:30 UT (10:30 pm PST), a bright, slow, spectacularly fragmenting fireball swooped over southern California. It was seen and reported by many in the San Diego-Los Angeles area. The video above was obtained by a dedicated fireball all-sky camera operated by Bob Lunsford. The fireball duration approached 20 seconds.

In the hours after the fireball, the American Meteor Society (AMS) initially suggested that this was a Space Debris reentry, i.e. the reentry of something artificial from earth orbit.

But it wasn't.

Immediately upon seeing the video, I had my doubts. Upon a further look at the video, those doubt grew. To me, the evidence pointed to a meteoritic fireball, a slow fragmenting fireball caused by a small chunk of asteroid entering our atmosphere.

A discussion ensued on Twitter, until NASA's Bill Cooke settled the issue with multistation camera triangulation data, which showed that this was an object from an Apollo/Jupiter Family comet type heliocentric orbit with a speed of 15.5 km/s. In other words: my doubts were legitimite. This was not a space debris reentry but indeed a chunk of asteroid or comet.

I've already set out my argumentation about my doubts on Twitter yesterday, but will reitterate them again below for the benefit of the readers of this blog.

My doubts started because while watching the video I felt that the fireball, while slow and of exceptionally long duration, was still a tad too fast in angular velocity in the sky, and too short in duration, for this to be space debris. In the video, it can be seen to move over a considerable part of the sky in just seconds time.

The image below shows two stills from the video 6 seconds apart in time. The fireball passes two stars, alpha Ceti and beta Orionis, that are 35 degrees apart in the sky, and it takes the fireball a time span of about 6 seconds to do this, yielding an apparent angular velocity in the sky of about 5-6 degrees per second. That is an angular velocity that is a factor two too fast for reentering space debris at this sky elevation, as I will show below.

stills from the fireball video, 6 seconds apart, with two stars indicated

Orbital speed of a satellite is determined by orbital altitude. Reentering space debris, at less than 100 km altitude, has a very well defined entry speed of 7.9 km/s. This gives a maximum angular speed in the sky of about 5 degrees/second would it pass right above you in the zenith (and only then): but gives a (much) slower speed (2-3 degrees/second) when the reentry is visible lower in the sky, such as in the fireball video.

To gain some insight in the angular velocity a reentering piece of space debris would have at the elevation of the California fireball, I created an artificial 70 x 110 km reentry orbit over southern California that would pass the same two stars as seen from San Diego.

The map below shows that simulated track, with the object (marked by the green rectangular box) at 70 km altitude and positioned 6 seconds after passing alpha Ceti (marked by the green circle):

Simulated reentry track. click to enlarge

The angular velocity in the sky for a reentering object at this sky elevation suggested by this simulation is barely half that of the fireball. During the 6 seconds it took the fireball to move over 35 degrees of sky passing alpha Ceti and beta Orionis, the simulated reentering object would have moved over only 15 degrees, i.e with an angular velocity of 2.5 degrees/second rather than the 5-6 degrees/second of the fireball.

So this suggested that the fireball was moving at a speed a factor two too high for space debris. This therefore pointed to a meteoritic fireball, not a space debris reentry.

There were other reasons to doubt a reentry too. There were no matching TIP messages on Space-Track, the web-portal of CSpOC, the US military satellite tracking network. A reentering object as bright as the fireball in the video would have to be a large piece of space debris: this bright is clearly not the "nuts and bolts" category but suggests a large object like a satellite or rocket stage. It is unlikely that CSpOC would have missed a reentry of this size.

To be certain I ran a decay prediction on the full CSpOC catalogue with SatEvo myself: no object popped up that was expected to reenter near this date either, based on fresh orbital elements.

The fragmentation in itself, one of the arguments in the AMS' initial but mistaken conclusion of a "space debris reentry", is not unique to space debris reentries. It is also a common occurence with slow, meteorite dropping asteroidal fireballs, especially when they enter on a grazing trajectory. Take the Peekskill meteorite fall from October 1992 for example:




Likewise, while a 20-second meteor is not everyday, it is not a duration that is impossible for a meteor. Such durations (and even longer ones) have been observed before. Such long durations are especially the case with meteors that enter in a grazing way, under a shallow angle.

At the same time, a 20 seconds duration would be unusually short for a satellite or rocket stage reentry. Such reentries are usually visible for minutes, not a few seconds or a few tens of seconds.

So, to summarize:

1) the angular velocity in the sky appeared to be too large for space debris;
2) the fireball duration would be unusually brief for space debris;
3) and there were no obvious reentry candidates.

On the other hand:

a) the angular velocity would match those of slow ~15 km/s meteors;
b) the 20 second duration, while long, is certainly not impossible for a meteor;
c) the fragmentation observed occurs with slow asteroidal origin meteors as well.

Combining all these arguments,  my conclusion was that this was not a space debris reentry, but an asteroidal origin, slow meteoritic fireball. This was vindicated shortly later by the multistation camera results of Bill Cooke and his group, which yielded an unambiguous speed of 15.5 km/s and as a result a heliocentric orbit, showing that this was not space debris but a slow chunk of asteroid or Jupiter Family comet.

In defense of the American Meteor Society (who do great work on fireballs): it is not easy to characterize objects this slow, certainly not from single camera images and visual eyewitness reports. Given the slow character and profuse fragmentation, it is not that strange that the AMS initially (but incorrectly) thought it concerned a space debris reentry. It does go to show that you have to be extremely careful in drawing conclusions about slow moving fireballs: not every very long duration fragmenting fireball is space debris.

An interesting CRS-19 Falcon upper stage deorbit area (UPDATED)

click map to enlarge

The Maritime Broadcast Warnings with the hazard areas for the upcoming December 4 SpaceX DRAGON CRS-19 supply mission to the ISS have appeared a few days ago.

These include a Broadcast Warning for the Falcon 9 upper stage deorbit area. And that deorbit area (depicted in red in the map above) has an odd position and timeframe:

HYDROPAC 3933/19

SOUTHERN INDIAN OCEAN.
DNC 02, DNC 03, DNC 04.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
042302Z TO 042344Z DEC, ALTERNATE
052240Z TO 052322Z DEC
IN AREA BOUND BY
58-52S 050-29E, 55-59S 052-23E,
55-26S 059-28E, 54-58S 065-18E,
54-08S 073-22E, 52-46S 083-57E,
51-25S 091-09E, 49-01S 100-13E,
46-34S 108-49E, 44-49S 113-54E,
46-47S 116-19E, 52-02S 109-55E,
52-57S 108-32E, 56-09S 102-10E,
59-05S 092-54E, 61-08S 081-09E,
61-48S 071-27E, 61-08S 060-26E.
2. CANCEL THIS MSG 060022Z DEC 19.//

Authority: PACMISRANFAC 250217Z NOV 19.

Date: 290929Z NOV 19
Cancel: 06002200 Dec 19


With DRAGON CRS launches, the Falcon 9 upper stage deorbit usually happens in the second part of the first revolution, south of Australia or in the southern Pacific. See e.g. the deorbit area for the Falcon 9 upper stage of CRS-17 from May this year, depicted in blue in the map above.

But not this time. The Maritime Broadcast Warning above suggests that the CRS-19 upper stage deorbit happens much later, about 5.5 hours or 3.5 revolutions after launch. In addition, the area is shifted southwards compared to the CRS-19 ground track, indicating a deorbit from an orbital inclination clearly higher than the 51.6 degrees orbital inclination of the DRAGON. In fact, it fits an orbital inclination in the order of of 57-58 degrees, i.e. some 5 degrees higher in inclination.

So that is odd.

The prolonged on-orbit time might be a coasting test with an eye on future missions that require coasting over several revolutions. The indicated inclination change might likewise be a test for a future mission requirement.

I have been entertaining the possibility of an undisclosed cubesat rideshare, to a ~58 degree inclination orbit. But that remains pure speculation and is perhaps not very likely.

Note: in the map in top of this post, the dashed white line is the DRAGON CRS-19 trajectory up to 23:45 UT (Dec 4), the end of the timewindow given by the Maritime Broadcast Warning for the Falcon upper stage deorbit.


UPDATE 4 Dec 2019 10:15 UT:

During the CRS-19 pre-launch press conference yesterday, the SpaceX Director of Dragon Mission Management, Jessica Jensen, said the Falcon 9 upper stage is doing a "thermal demonstration" after the CRS-19 orbit insertion, that amounts to a six-hour coasting phase:




In reply to reporter questions she provided slightly more details somewhat later in the press conference, adding that the test is done at the request of a customer for future missions that require a long coast. During the long coast phase, they will a.o. measure the thermal environment in the fuel tanks. The apparent ~5 degree orbital inclination change was not mentioned: