Brief GOCE update, 7 November

This morning the average orbital altitude of GOCE had dropped to 181 km. The orbital droprate is now near 6 km per day. There is no sign yet that attitude control is failing.

The nominal re-entry forecast is slightly shifting backwards. My current forecast using Alan Pickup's SatAna and SatEvo software is re-entry in a 1.5 day uncertainty window centered on Nov 11.17 UT. This is assuming that the attitude control will hold until decay (see discussions in previous posts).

Brief (semi-) daily GOCE update, 6 November

GOCE's perigee is now below 183.5 km, the average orbit has dropped to 187 km (from 227.5 km originally). The orbital droprate is now close to 5 km/day.

The nominal forecast re-entry window is currently a two-day period centered on Nov 10.90 UT. However, see the caveat in my previous post. If GOCE loses its current drag-reducing attitude (flight orientation), the re-entry forecast above will turn completely obsolete.

A more elaborate explanation of factors involved can be found in my previous post, including an explanation on why re-entry forecasts for GOCE must be approached very cautiously.

Forecasts were made using Alan Pickup's SatAna and SatEvo software: for an explanation on the workings of this software and factors of influence, see an earlier post here.

GOCE update (5 Nov 2013)

GOCE, ESA's Gravity Field and Steady-State Ocean Circulation Explorer, is still steadily coming down (see previous posts). This morning, the average orbital altitude had dropped below 191.5 km (from originally 227.5 km before Oct 21) and perigee is already down to 188 km. The orbital altitude has dropped 36 km in 15 days and it is currently coming down at a rate of 4.5 - 5 km per day, and increasing.

The nominal center of the re-entry forecast window, a period of several days, is still hovering near November 10-11. My latest forecast (issue date Nov 5.22 UT) has it nominally at Nov 10.97, +/- 1.2 days. This is the approximate date the satellite would re-enter, if it remains in its current drag-reducing attitude (orientation).

The latter caveat is an important point to note in this case and its implication should not be ignored. The special aerodynamic design of GOCE means that (much more so than for other satellites) there is a large difference in the amount of drag it is experiencing in drag-reducing attitude compared to what it will experience when that attitude is lost. If the attitude control mechanism (magnetic torques) fails somewhere during the coming days and the drag reducing attitude is lost as a result, GOCE will come down much earlier than the current forecast suggests. That is one reason to be very cautious with GOCE re-entry predictions, certainly at this point in time.

It is currently impossible to say if, and if so when, such a loss of attitude will happen. But if it does, the current re-entry forecast will be turned completely obsolete.

Meanwhile, let us not forget that GOCE is still functioning! As it spirals down to its doom faster and faster, it continues to gather valuable data on the Earth's gravitational field.

GOCE below 200 km - now one week or less from reentry

Over the past 12 days I have been covering the demise of GOCE, ESA's Gravity Field and Steady-State Ocean Circulation Explorer. Following the cut-off of its ion engine on October 21st, it is coming down, at an increasing speed. It is heading towards an uncontrolled re-entry later this month, perhaps even within a week from now.
 

 

click diagram to enlarge

The diagram above shows the increasing rate at which the orbital altitude is dropping since October 21st. As I write this, the drop rate has increased to about 4 km/day (from initially about 1.5 km/day on October 21st) and that rate is increasing exponentially, as can be seen in the diagram.

The average orbit of GOCE, at 227.5 km altitude before the engine cut off, has now dropped to below 200 km altitude. Perigee is already below 195 km. The Mean Motion (the number of orbital revolutions per day) of the satellite is increasing fast.

While it is still too early to provide really meaningful predictions, I currently have a nominal re-entry prediction for a window of a few days centered on November 10.7. It hence now seems possible that GOCE is within a week of plunging into the atmosphere.

The diagram below shows how predictions of the re-entry window have been evolving the past days (the grey line is the nominal prediction value, i.e. the center of the uncertainty window, and the dashed lines show the window of uncertainty on the prediction. The top three panels give observed and predicted solar flux; drag terms; and the orbital drop rate trend).

These predictions were made using two satellite orbital decay programs written by Alan Pickup, called SatAna and SatEvo. The program called SatAna analyses the orbital evolution over a number of recent orbit determinations and (taking into account the average solar flux for that period) fits a decay term that should be a bit more realistic than the decay terms from one single orbit only (which vary widely, see the second subwindow with B* values in the diagram above). The SatAna result and the predicted average solar flux for the next few days is next fed into SatEvo, a program that evolves the orbit into the future, up to re-entry.

The calculated moment of re-entry becomes more accurate based on orbital elements closer to decay. Currently, some 7 days before the prognosed moment of re-entry, the uncertainty window is still very large (several days), so giving an exact time at this moment is still meaningless. It is also still completely impossible to say where it will come down.

A lot can still happen the coming few days, that can drastically alter the picture. I have written about this before: e.g., if GOCE for some reason loses its current drag-reducing attitude (flight orientation) or is starting to shed bits and pieces at some point, the drag it experiences will significantly change, and with that the re-entry predictions will significantly change. Differences between the predicted solar activity for the upcoming days and real solar activity values the coming days, likewise can change the re-entry time.

(note: I thank Alan Pickup for making available SatAna and SatEvo)

About half-way: another short update on GOCE, 10 days after its engine cut off

Ten days ago the ion engine of GOCE, the European Space Agency's 1-tonne Gravity field and steady-state Ocean Circulation Explorer scientific satellite (2009-013A), cut off after the satellite ran out of fuel.

Originally orbiting at an average orbital altitude of 227.5 km, it is since coming down (see earlier posts here and here and the first two diagrams below). Its perigee is now below 205 km and it is currently coming down at a rate of 2.7 km/day. That rate is increasing (see third diagram below): it is already a factor 3 larger than it was on October 21st just after the ion engine of GOCE cut off.

click diagrams to enlarge

As I wrote earlier, for various reasons it is still too early to provide reliable re-entry estimates. I nevertheless estimate that GOCE is now about half-way, in terms of days not altitude, from inception of its fall to re-entry.

After the latest orbital updates, the nominal re-entry date appears to slowly creep to an earlier date. Currently I have re-entry forecast for a several-day window around November 10.

That date can still (dramatically) shift if anything happens to GOCE, for example if it loses its current drag-reducing attitude (flight orientation - see also a previous post) or if we see a drastic change in solar activity.

The Sun has been very active the past few days, spewing several CME's. This solar activity has an influence on the density of the upper atmosphere, and this in turn has an influence on the magnitude of the atmospheric drag on GOCE, influencing how fast its orbit evolves.

I do expect the prognosed re-entry date to slowly creep to an earlier date over the coming few days. It therefore does seem that GOCE has less than two weeks, and possibly closer to a week, of lifetime left.

A short update on GOCE, five days after engine cut-off

It is now five days ago that the ion engine of GOCE, the European Space Agency's 1-tonne Gravity field and steady-state Ocean Circulation Explorer scientific satellite (2009-013A), cut off after the satellite ran out of fuel. Originally orbiting at an average orbital altitude of 227.5 km, it is since coming down (see earlier post here). The diagrams below provide an update on the evolution of the orbit's apogee, perigee and Mean Motion (see also earlier post here for explanations) .

 click diagrams to enlarge

As I write this, the average orbital altitude has dropped over 8 km already since the ion engine shut down on October 21st. Yesterday afternoon (25 October) the average orbital altitude had already dropped below 220 km altitude, with the perigee now below 217 km (see first diagram above).

GOCE is currently losing altitude at a rate near 2 km per day. That rate will notably increase over the coming days, as GOCE will drop faster and faster.

It is too early yet to provide meaningful estimates of the re-entry date. My current prognosis (for which I used Alan Pickup's SatAna and SatEvo software) suggests a re-entry in the second week of November, but note that this date will probably shift to an earlier date over the coming week.

Currently, the satellite is still maintaining an attitude (orientation) that is optimizing for low drag. It does so using magnetic torques. At some point close to re-entry, that system will probably fail and GOCE will then lose attitude control. As it does so, drag will increase, which will seriously influence the re-entry date, shifting it to an earlier time. Meanwhile, the sun has been quite active the last few days, which speeds up the decay as well as the density of the Earth's outer atmosphere changes under the influence of solar activity. My very preliminary prognosis was made with an average forecast F10.7 cm solar flux of Fx=135 for the coming 20 days, but unexpected solar outbursts might alter the true picture.

I expect that several sources will start to provide re-entry estimates in the days before re-entry. The chief authoritive sources will be ESA itself, and the TIP-messages by USSTRATCOM on their  Space-Track portal (needs an account to access).  I expect that several independent analysts will provide re-entry estimates as well. The Aerospace Corporation provides re-entry estimates based on their own re-entry models, but is usually lagging behind. Their predictions sometimes strongly differ (up to several hours) from the final re-entry times and locations determined by USSTRATCOM (which I consider to be a more reliable and authoritive source).


(note: in the first diagram above, the values for perigee and apogee show some short-term fluctuation during the first 2-3 days after engine cut-off. These fluctuations are the result of errors in the orbit determinations, which easily occur (and are inevitable) when the data-arc used is still short and fitting error margins are hence wide. As the observational arc grows, the orbital determinations become more stable, which is indeed what we see over the last two days.
The apogee and perigee altitudes in the first diagram have been calculated from the values for Mean Motion and eccentricity using a fixed Earth radius of 6378 km, ignoring Earth's oblateness. Orbital elements are from USSTRATCOM (needs an account to access) with a secondary source (open access) here).

Note 31 Oct 2013: a new update here.

A farewell to GOCE

In the past, I have observed ESA's gravity probe GOCE (2009-013A), the Gravity field and steady state Ocean Circulation Explorer, a number of times (e.g. here, here, here, here and here), usually as a rather faint object producing brighter specular flares near culmination.

 click image to enlarge

This weekend I tried again, spurred to do so by some people at ESA's ESOC in Darmstadt. The reason was that GOCE does not have much lifetime left. It's ion engine will run out of Xenon and cut-off somewhere mid- to end October, and the expectation is that the spacecraft will then re-enter and disintegrate in the atmosphere within 2 to 3 weeks. Some 250 kilo of the one-ton spacecraft might survive re-entry, divided over 50+ fragments.

The Goce orbit already had been brought down in November 2012: its orbital altitude currently is no  more than 225 km. As a result, it currently zips across the sky at high speed. Because of the low altitude, it is visible in twilight or very shortly after twilight only.

The image above shows GOCE over the roof of my home in Leiden center in deep evening twilight of  Sunday 29 September. It was visible with the naked eye, but only barely.

The image was shot with an EF 2.0/35mm lens and because of the bright twilight sky I used a short exposure of 2.5 seconds. The elevation of the spacecraft was around 40 degrees, passing east of me. The sky background shows stars in Andromeda: about halfway of the chimney and the GOCE trail you can see the fuzzy glow of M31, the Andromeda nebula.

I had also tried to image the spacecraft the evening before (Saturday the 28th), but Murphy struck. I was a bit late in checking for passes that day (in twilight already) and discovered that the only visible pass would happen within minutes of me checking for passes! So I ran outside, grabbed the camera, slammed it on the tripod, aimed it...and forgot to take off the lens-cap....

That particular pass, in a somewhat darker late-twilight sky and at a higher elevation through Cygnus, was a nice one, where GOCE was clearly visible to the naked eye. GOCE was racing through the sky, about the fastest you will ever see a satellite move in the sky. Quite apt for "the Ferrari among the satellites"!

This might have been my last view of GOCE ever: over the coming days the passes will become increasingly more unfavourable for my location.

It will be interesting to follow the satellite to decay once its engine has cut off. The ESOC people told me they will try to put it in a fine-pointing mode just before it does so, but there is a possibility that at one point it will lose attitude and will start tumbling.

Fireball over NW Europe of the evening of 13 February 2013: Re-entry of a Soyuz r/b

Reports are pouring in of a very long duration, bright fireball near 22:15 CET (21:15 GMT) seen from Belgium, the Netherlands and Germany. Reports indicate 30-40 seconds visibility, and an "explosion" halfway, and some reports indicate sonic booms.

This fireball was with a high degree of certainty the re-entry of a Russian Soyuz 3rd stage, #39083 (2013-007B), the 3rd stage from the Soyuz that launched the Progress cargoship Progress-M 18M towards the ISS on February 11th.

USSTRATCOM issued a TIP message indicating decay at 21:15 +/- 1 m UTC near 49N, 13 E.

Below is a quick map (made using Orbitron) of the trajectory and approximate position of the re-entry.

click map to enlarge

Time, general description and reentry data all fit quite well.

Mapping a year of space debris re-entries

The year 2012 saw as many as 72 uncontrolled re-entries of larger pieces of space debris.

Just for fun, I mapped the data for those 52 re-entries where the time of the re-entry is known to 15 minutes or better. The latter means that the general area over which the re-entry occurred can be established with some confidence.

click maps to enlarge

As can be seen from the kernel density map, Africa got the brunt of the re-entries last year. Common wisdom has it that most re-entries occur over the Pacific. That is true for controlled re-entries, but for uncontrolled re-entries that is not born out by the map above. There is a "but" in this all however: the aparent emptiness of the Pacific is, likely, an artifact of a lack of tracking sensors there. Re-entries over this part of the world will have larger uncertainties in their time of decay estimates, and hence they do not show up on this map.

[UPDATED] The 21 September fireball: a small Aten asteroid?

-- edited/corrected 25/9 15:25 UT. I initially made a small error in the used trajectory azimuth (not properly taking into account effects of a spherical earth). That is corrected, but the conclusions do not alter. --

In my previous post I presented clear evidence that the splendid fireball seen over NW Europe on September 21st, 2012, was a meteoric fireball. I also presented a first, very preliminary idea of its trajectory.

Based on that trajectory, I can now present some very first, very cautious conclusions about the heliocentric orbit of this meteoroid.The solutions strongly favour an identification as an Aten asteroid.

The entry azimuth of the fireball from the reconstructed preliminary trajectory is around 80 95 degrees. Based on observations by Ramon van der Hilst who observed the fireball from Bussloo, the estimated entry angle for the fireball is about 5 degrees only: a very shallow, earthgrazing angle which explains the long trajectory. (I asked Ramon to estimate the angle of the fireball with respect to the horizontal at the moment Ramon was looking roughly perpendicular to the preliminary trajectory. That angle, about 5 degrees as Ramon reports, should be close to the entry angle)

I used these values and an 18-20 km speed estimate to compute a nominal heliocentric orbit: and then played around by widely varying the values for speed, entry angle, entry azimuth around these nominal values.

The interesting point is, that for all of these, I get an Aten orbit as a result. Aten asteroids are asteroids whose perihelion lies within the orbit of the earth and who's aphelion lies only just outside the orbit of the earth. They have a semi-major axis < 1.0 AU and aphelion (just) over 1 AU.

The aphelion values I get for the approximate fireball orbit, are in the range 1.0 - 1.15 1.05 AU, the semi-major axis values are in the range 0.9 to 0.6 AU. Solutions based on higher speeds (I varied between 12 km/s and 30 km/s in my calculations) favour the slightly larger aphelion values and shorter semi-major axis.

A wide variation in entry azimuth (I tried between 60 and 110 120 degrees) and entry angle (I tried for values between 5 and 45 degrees, the latter clearly a too large value by the way) does not alter this picture much: they all result in Aten orbits.

I need to alter the trajectory direction to values significantly larger than entry from a direction of  120 degrees (well past due east) to get aphelion values that start to get well beyond 1.15 AU and semi-major axis values > 1.0 AU.

For the current very preliminary nominal trajectory solution (entry azimuth ~82 ~95 degrees, entry angle ~5 degrees) I get these values when varying the assumed entry speed of the fireball:

[editted table 15:25 UT to reflect new calculations/correction of error]

Vini    q    Q     a     e     i

12.0   0.82  1.00  0.91  0.10  6.5
15.0   0.46  1.02  0.74  0.39  15.0
18.0   0.31  1.04  0.67  0.55  20.7
20.0   0.24  1.05  0.65  0.62  24.8
25.0   0.16  1.09  0.62  0.76  37.4
27.0   0.13  1.11  0.62  0.79  43.7
30.0   0.11  1.14  0.62  0.83  54.5

Vini is the initial speed (in km/s), q the perihelion distance (in AU), Q the aphelion distance (in AU), a the semi-major axis (in AU), e the eccentricity, i the inclination.

These values should be taken with caution and only as rough indications. There are (still) large uncertainties in the trajectory and entry angle, as well as the speed of the fireball. They do show however (as well as variations on the trajectory not listed here) that an Aten-orbit is the implied solution.

The Earth encountered the meteoroid close to the meteoroid's aphelion, when it was moving almost in parallel with the Earth.

-------------------------------
NOTE / UPDATE 26/09/2012, 19:25 UT: There is some confusion on the web regarding my analysis and the "retrograde"/ "prograde" character of this object.
The "retrograde"character is only true for an earth-centered orbit (i.e., an object orbiting the earth, such as an artificial satellite). An east-west movement in that case means it is "retrograde" (against the motion of the earth's rotation).
This is not necessarily the case for a sun-centered orbit however. An east-west moving object then can be (and is, in this case!) in a normal, "prograde" orbit (=moving in the same direction around the sun as the planets). The difference is the frame of reference: earth-centric versus sun-centric.
So beware: the "retrograde" orbit refers to what the orbit would be for an earth-orbiting satellite (which this object was not). The Aten heliocentric orbit presented here, is however prograde.

More on the 21 September 2012 fireball: why it definitely was a meteor

I should have done this analysis earlier but did not have the time available until now. What follows now is a quick and back-of-the-envelope kind of calculation, but in my (not so) humble opinion it is adequate to the question at hand.

It concerns, of course, the splendid slow fireball seen widely over NW Europe near 21:55 UT on 21 September 2012. I posted on it before, focussing on saying "no" to the suggestion that this could have concerned a satellite reentry. In the post that now follows, I further strengthen the conclusion that it was not a satellite reentry, but a genuine meteoric fireball.

The map above gives a quick (and not particularly accurate) back-of-the-envelope reconstruction of the fireball trajectory. It is based on trajectory descriptions from Bussloo in the Netherlands and Dublin in Ireland: by taking reported altitudes (with respect to stars) and general directions of reported start and endpoints, and an assumed altitude of 50 km, the trajectory above is what approximately results. (update 19:10 UT, 24 Sep: an updated version of the map is at the bottom of this post).

The resulting trajectory is some 1000-1200 km long. In what now follows, I have taken 1100 km as the distance travelled by this fireball.

Observers near the western and eastern ends of the trajectory would probably not see the complete trajectory. Observers approximately mid-way, in mid-Britain, would potentially see most if not all of the trajectory (from experience I know you can see bright fireballs from distances of 500 km).

Observers report durations between 20-60 seconds: most video's on the web suggest a 40+ seconds duration.

It would take a reentering satellite travelling at 8 km/s (the orbital speed at decay altitudes) about 138 seconds or roughly 2.25 minutes to travel this distance. While the reported fireball durations are long, none of the reports nor videos comes even remotely close to that value.

A meteoric fireball travelling at the lowest speed possible for such an object, 11.8 km/s, would take 93 seconds to travel that distance. This is still longer than almost all of the reports suggest, but clearly getting closer.

If we take an estimated duration of 60 seconds, the 1100 km trajectory length results in a speed of  approximately 18 km/s.

18 km/s is a very reasonable speed for a slow, asteroidal origin fireball.

(it is, let me repeat, also way too fast for a satellite reentry).

Meteorite dropping fireballs typically have speeds between 11.8 and 27 km/s. A speed near 18 km/s sits squarely in the middle of that speed interval.

(update: diagram added 14:45 UT, 24 Sep)

(click diagram to enlarge)

The 60 seconds probably represents the upper boundary value for the duration of the fireball. If we take a shorter duration of 40 seconds, the speed already increases to 27.5 km/s.

This quick back-of-the-envelope reconstruction therefore shows that this must have been a meteoric fireball, quite likely of asteroidal origin, and we definitely can exclude a satellite reentry.

The fragmentation described and filmed is not unusual for meteorite dropping fireballs (see the video's of the Peekskill meteorite fall in my previous post). The object probably entered the atmosphere under a very shallow angle, which together with the slow speed explains the unusually long duration of the event.

Meteors of this kind are rare, but they have been seen before. Think of the Peekskill meteorite fall, but also the famous 1972 daylight fireball over the Grand Tetons (that had a duration of over 100 seconds) and the Cyrilid Meteor Procession from 1913 (that lasted minutes).

Note: a previous post gives a number of other lines of evidence which likewise suggest this fireball was not man-made space debris.

UPDATE: a further update is given in a new post: a very cautious orbital solution suggests an Aten orbit.

Note 2: on how I made this quick and (emphasis) rough trajectory reconstruction. I took observations that contain clear sky locations: e.g. a sighting from Dublin stating it went "through the pan of the Big Dipper"; the description from Bussloo observatory in the Netherlands; and later adding a.o. a photo from Halifax, UK, showing it just above the tail of Ursa Major. These descriptions can be turned into directions and elevations. Next, I drew lines from these sighting points towards the indicated directions, marking distances roughly corresponding to 30, 50 and 80 km altitude as indicated by the observed elevation [ distance = altitude / tan(elevation) ]. Near the start of the trajectory I marked 50 and 80 km, for Britain and Ireland I marked 30 and 50 km. These points then provide you with a rough trajectory.
From Dublin the object passed through North towards west. From Bussloo the object started NE (azimuth 60 degrees): these are important points of information too as it shows that the object started at least as far east as the Dutch-German border (and more likely over Sleswig-Holstein in N-Germany) and had its endpoint at least as far west as the northern part of Ireland.

Above: Updated map version, 24 Sep 19:10 GMT , also showing the principle of how it was reconstructed for three sighting locations. With thanks to Ramon van der Hilst for providing more detailed information on sky trajectory as seen from Bussloo (NL) on request.

Fireball over N-Europe on 21 September 2012, 21:45 GMT was likely NOT a reentry

UPDATE (24/9/2012): more and definite arguments that this was not a reentering satellite, can be read here in my follow-up post from Sep 24th. This includes a first rough trajectory reconstruction for this fireball.

Reports are pouring in from The Netherlands, Britain, Ireland and other N-European countries about a very bright, extremely slow fragmenting fireball appearing around 21:45 - 21:55 GMT (23:45 -23:55 CEST) on the evening of 21 September 2012.

Various video's have been posted on Youtube, notably by observers from Britain (large parts of the Netherlands were clouded out, including the all-sky stations):





Because of the unusually long duration and slow movement, some people have suggested the possibility of a satellite reentry. For various reasons, this is however very unlikely.

Multiple reports make clear the object was moving from east to west. A report of observers from Bussloo Observatory, the Netherlands, for examples states that the fireball appeared in the north, moving from Perseus  to Bootes, almost horizontally from east to west. Similar reports (e.g. here and here) come from Ireland.

Almost all non-polar satellites move prograde,  from west to east (or north-south and v.v. for a polar orbit). An east to west movement would necessitate the object to have a retrograde orbit (meaning that it moves counter to the earth's direction of rotation). Such objects are extremely rare: they literally amount to only a handful of objects (including the US FIA Radar satellites, and the Israeli Ofeq/Shavit satellites/rb). For this reason, it is extremely unlikely that this fireball was a reentering satellite.

Update 24 Sep: in the comments to this blog post, the issue was raised of the potential reentry of a classified object. However, the larger classified pieces are tracked by us amateurs. We have no likely decay candidates among the retrograde objects that we track. We can account for and hence exclude the FIA's for example (the rocket bodies of that launch were deliberately de-orbitted right after launch so are no candidates either). The Israeli Ofeq/Shavit are no candidates as their orbital inclinations never take them over the Netherlands and the British Isles. And there are simply no other suitable retrograde objects -- end of update.

There are moreover no unclassified reentry candidates for this date listed by USSTRATCOM on their space-track portal. Given the brightness of the fireball, this should have been a seizable chunk of space debris, that really would have been tracked (and predicted). Again, this makes it very unlikely that this fireball was a satellite reentry.

While the duration of the fireball is unusual, it is not unprecedented. In many ways, the descriptions and video are reminiscent of the Peekskill fireball that dropped meteorites near Peekskill in 1992:

(below: two video's of Peekskill fireball, 1992)

It is therefore my opinion that the 21 September fireball was most likely of meteoric origin: a chunk of asteroid. Alas, any surviving remains appear to have splashed down in sea (update: or possibly Scotland - N. Ireland).

The duration of the event, though not unprecedented, is certainly unusual and for this reason, I am saying "most likely not" rather than "certainly not".

UPDATE (12:45 GMT, 22 Sep):  another bright fireball was widely seen from the US and Canada that same night near 20:30 GMT. There was at least one hour inbetween the two events, so they do not appear to be related (i.e. they do not concern the same fireball).

UPDATE 2 (13:30 GMT, 22 Sep): Suggestions that the fireball might be related to Chinese CZ-4 space debris, catalogue #26213, are plainly incorrect. That object (and any fragments of it) are in a 98 degree polar orbit. This is completely incompatible with the reported movement of the fireball. As seen from Bussloo in the Netherlands and Dublin in Ireland, the fireball moved perpendicular, not parallel, to the orbital plane of this Chinese space debris (and that of any related fragments).

 IMPORTANT UPDATE 3 (24/9/2012): more and definite arguments that this was not a reentering satellite, can be read here.

The re-entry of IGS 1B on 26 July 2012

While I was away on holidays, the Japanese spy satellite IGS 1B (03-009B) that malfunctioned in March 2007, re-entered on 26 July 2012, over Polynesia.

The demise of this satellite was covered for over a year on this blog: as the satellite was weighing 1.2 tons and as it had an unknown amount of remnant fuel onboard, the uncontrolled reentry raised some questions and initial concerns (see coverage here).

The last amateur observations of the object were done by Mike Waterman (USA) on July 24th and Alain Figer (France) in evening twilight of July 25th. The last amateur orbital update by Ted Molczan based on a.o. Mike Waterman's observations, showed it to have descended to a 211 x 213 km orbit on July 24th and analysis of this dataset by this author using Alan Pickup's SatEvo suggests reentry on July 26, somewhere between approximately 9:50 and 10:50 UTC.

USSTRATCOM published a final TIP for IGS 1B on July 26th (that they did so for a classified object is unusual), placing re-entry at 26 July 2012, 09:52 +/- 2 min UTC, near 25 S, 186 E, which is near New Zealand. This is at the start of the reentry window given above and hence seems very reasonable even though the reentry coordinates are a verbatim copy (down to one decimal) of a pre-decay prediction issued at 7:34 UTC (only the uncertainty value has changed, from 2 hours to 2 minutes). No details on the orbital development in the final few revolutions were given.

The map below shows the USSTRATCOM determined reentry location and final trajectory. In principle, the re-entry could have been observed from the northern islands of New Zealand and potentially the Fiji-Tonga area. Note that only half a revolution later (about 30 minutes later) it would have passed over NW Europe and next west Africa.

click map to enlarge

The diagram below shows the orbital evolution in terms of apogee and perigee altitudes, from malfunction early 2007 to decay on 26 July 2012. It is based on orbital element sets calculated by Mike McCants and Ted Molczan from amateur observations, including mine:

click diagram to enlarge

2

IGS 1B was a nice object to observe over the past years: it was bright, and it was interesting to follow its orbital evolution towards decay. The observation that remains the most vivid imprint in my memory is the one that resulted in the picture below: on 2 September 2011, while I was watching and photographing a pass in a slightly hazy sky, the satellite brightly flared to at least magnitude -8 if not more: the brightest satellite flare I have ever seen. I was jumping up and down and yelling "WOOOOOWWWW!!!!" when this happened. It resulted in this wonderful, eerie picture:

click image to enlarge

Update on IGS 1B (10 June 2012)

We are slowly getting closer to the uncontrolled re-entry of the 1.2 tons malfunctioned Japanese spy satellite IGS 1B (2003-009B). The satellite's orbit has by now dropped below 340 km altitude (see second diagram below, perigee/apogee values from orbits calculated by Mike McCants based on amateur observations including mine). That is well below the ISS orbital altitude (ISS is currently in a 392 x 406 km altitude orbit). A mere month ago it was still considerably higher, in a 366 x 368 km orbit: it lost over 25 km or orbital altitude since. It is dropping fast, and the rate increases (see diagram below).

Using the latest amateur orbital elements for the object and Alan Pickup's SatEvo software with the current 10.7 cm solar flux, re-entry is currently estimated to occur between mid-July and early August 2012.

Space debris lands in Brazil village

Through Carlos Bella on the satobs mailing list, news broke today that an object which almost certainly is space-debris crashed in the Brazilian village of Anapurus on February 22, 2012, near 6 am local time (9 UTC). It landed about 6 yards from a house and damaged trees upon impact.

Photo's of the object can be see here.They show a spherical object that strongly resembles a spherical rocket fuel cell (tank) or a Helium pressurization tank. These are the most resistent objects among space debris and often involved in reported cases of space-debris reaching earth surface.

Ted Molczan quickly noted that date, time and location correspond well to the re-entry of 1997-016C, an Ariane 44L rocket stage from the launch of two geostationary satellites, Thaicom 3 and Bsat-1A, on 17 April 1997.

The Ariane 44L r/b in question re-entered at 9:09 UTC +/- 1 min on 22 February 2012, near 4 S, 312 E. This corresponds well with the time and location of the Anapurus event (3.7 S, 317 E). Anapurus is located right on the re-entry track and was passed within a minute of the estimated re-entry time (movement of the r/b was from West to East, i.e. to the right in the map):

click map to enlarge

Phobos-Grunt: a final TIP on where it came down

USSTRATCOM today (Jan 23rd) has finally released a traditional format final TIP for Phobos-Grunt. It yields similar values to the ones initially circulating through Russian press releases (see earlier post here): 17:46 GMT (+/- 1 m) and a location in the southern Pacific, near 46 S, 87 W.

click map to enlarge

More thoughts on the Phobos-Grunt reentry

It appears that the Russian news bulletins claiming that Phobos-Grunt reentered over the southern Pacific at 17:45 UT yesterday (see my previous post) rather were model predictions than reentry times based on actual final track detections. The Russians (nor the US, for that matter) actually do not have much in terms of tracking facilities in the indicated area (S-Pacific, S-America and S-Atlantic).

The southern Oceans: a blind spot

This highlights the problem, and the similarity between the UARS case last September and the current Phobos-Grunt case. In both cases, determining where it came down was likely hampered by the final revolution and final half hour or more of its trajectory being largely over remote and empty territory. Specifically, in both cases: the southern Oceans.

A lack of tracking facilities (and humans in general) in these areas, mean that they represent a large blind spot for those who's profession it is to track these objects. Once a satellite near decay starts to make its final passes and significant parts of that happen to be over these remote locations, it basically disappears into a black hole. That's what happened with UARS in September, and what now happened with Phobos-Grunt.

Not as in the movies

While some in the media and public have expressed frustration about the lack of published information (and the contradictory information) right after Phobos-Grunt presumably came down, I feel those people lack a realistic outlook on these matters. These people apparently expect that the military is able to determine a clearcut point of reentry within minutes after the satellite has reentered.

In reality, this is not how it works. The military has intermittent detections when the object moves over tracking facilities, spread wide and far over a number of places around the globe. They do not have continuous coverage. They cannot track where they have no tracking facilities. And the big and empty southern oceans represent a large swath of Earth where that is the case.

In Hollywood movies and TV-series, the military (or "NASA", even though in reality it is not NASA doing the tracking) are portrayed as having a second-to-second real-time tracking opportunity of objects, with a moving dot on the screen that disappears in real-time as soon as the satellite reenters. That however, as most things in movies, is a highly unrealistic view which has little resemblance to reality.

It will take the professional analysts at USSTRATCOM and elsewhere some time to ponder the last tracking data, detections and non-detections, and maybe even then there will remain uncertainty about where Phobos-Grunt came down. Such is life, and reality.

Space-Based detections?

In the case of UARS last September, some of us have had some suspicion that Space-Based observations (Infra-Red detections by the early warning satellites of Missile Defense) were perhaps involved in the final determination of the point of reentry. These resort under another part of the military, and comments by those "in the loop" have indicated that normally there is little data exchange between these guys and the groundbased tracking guys. There is also the open question whether reentry fireballs are bright enough for these space-based systems (the DSP and SBIRS satellites) to detect them. As the specifications of these systems are of course classified, little is known about this.

[Updated] Phobos-Grunt down over the southeast Pacific?

click map to enlarge

Early reports in the Russian media report that Phobos-Grunt has come down over the southern Pacific Ocean at 17:45 UT (15 Jan).

These same Russian media have misinterpreted decay bulletins in the (recent) past however, so this is all under some caveat until clear data from non-media sources (e.g.a USSTRATCOM TIP message) appears.

The map above is a preliminary map based on orbital elements from 16:35 UT, an hour before the reentry, and shows the approximate position for Phobos-Grunt for 17:45 UT. There  might be some small discrepancy between the pictured position and real position as it is based on orbital elements from one hour before the reentry.

Note added 20:30 GMT:  Confusingly, Ria-Novosti in a new press release mentions another time and position: 17:59 UT and the Atlantic, 18S and 311 E (49 W). This exemplifies what I mean above with the caveats....

Update 20:40 GMT: USSTRATCOM released a TIP message at 20:34 UT simply saying: "Object Decayed Inside Predicted Window".
That probably means: within the window of their earlier TIP message: 16:59-17:47 UT. This could be taken to support the 17:45 UT value of the Russians and reentry over the S-Pacific.

Summary of current Phobos-Grunt reentry predictions (15 jan 11:00 UT)

Summary of current Fobos-Grunt reentry predictions, round-up of predictions compiled at 15 Jan 11:00 UTC:

USSTRATCOM (14 Jan 20:30): interval 14:52 - 19:40 UTC
Harro Zimmer (15 Jan 07:10): 17:49 +/- 45 m UTC
Ted Molczan (15 Jan 04:59): 20:39 +/- 3 hrs UTC
Aerospace Corp. (15 Jan 06:25): 19:21 +/- 3 hrs UTC 
Roscosmos (14 Jan):  18:36 UTC (uncertainty window not stated)

Listed are: source; time prediction was issued (UTC); predicted time and uncertainty interval, or predicted interval.

My own current prediction, using Alan Pickup's SatEvo, current F10.7cm flux and 09:21 UT epoch orbital elements:  20:07 +/- 2 hrs.

PLEASE take note of the still large uncertainty intervals. As yet, it is still impossible to realistically say where it will come down.

[Updated] Summary of Phobos-Grunt reentry predictions as off 14 Jan, 13:00 UTC

Current predictions by various sources for the reentry of the failed Russian Mars probe Fobos-Grunt all still have a very large uncertainty window. Therefore, it is still impossible to provide any realistic statements about the when and especially where the reentry will happen. Suggestions in the press such as these only demonstrate a continuing and thorough misunderstanding of the whole issue among some journalists.

Perhaps as a result of this, USSTRATCOM has changed the way it presents it's Fobos-Grunt reentry predictions. While for other objects they still use the classical TIP format (time with uncertainty interval, and position at the nominal time), they altered the presentation for F-G: they only list the uncertainty interval, without positions or nominal time. Given the way that TIP messages were taken completely out of context and misinterpreted in the press recently (e.g. the notorious and utterly misinformed Novosti-RIA publication here), this is all a very understandable precaution.

A summary of the current predictions (round-up of predictions at 14 Jan, 13:45 UTC. Listed are: source; time/date prediction was issued; predicted time plus uncertainty interval, or uncertainty interval only):

USSTRATCOM (13  Jan 15:30 UTC): 15 Jan 08:25 - 16 Jan 03:37 UTC
Harro Zimmer (13 Jan 11:51 UTC): 15 Jan 17:05 +/- 3 hrs UTC
Ted Molczan (14 Jan 08:35 UTC): 15 Jan 22:31 +/- 8 hrs UTC
Celestrak (T.S. Kelso, 14 Jan 11:00 UTC): 17 Jan 10:04 +/- 1 day UTC
AeroSpace Corp. (13 Jan 10:40 UTC): 15 jan 17:52 +/- 14 hrs UTC
Roscosmos (14 Jan UTC):  15 Jan  21:51 17:51 UTC (no uncertainty window listed)

[added 15:45 UT, 14 Jan] My own estimate, using Alan Pickup's SatEvo and the current space weather (F10.7 cm flux) and the Jan 14.54 orbit, is for 15 Jan, 21:50 +/- 7 hrs UTC.

PLEASE take note of the large uncertainty windows on all these predictions! The uncertainty amounts to many revolutions of F-G around the Earth, so it is impossible to even indicate a Continent or Ocean (as some media sources do) where F-G will end up, at this moment.

Most of the predictions favour the 2nd part of Sunday Jan 15th.