Saturday, 31 May 2014

[AGAIN UPDATED] USA 161 recovered (?) - and new ideas on changes in the KH system

CORRECTION 1 June 2014: The object I observed on May 31 turns out to be NOT the KH USA 161, but one of the IGS objects, IGS 8R (2013-002C) which we had 'lost' in the winter blackout, just like USA 161. Their orbital planes happen to be very close (with a few tenths of a degree in inclination and a few degrees in RAAN) at the moment.

This renders the whole story below incorrect and hence moot.

Luckily, Russell Eberst did observe the real USA 161 last night (June 1) and his observations fit with Leo's observations from May 23. More in a new post later. (this new post is up now here)

ML, 01/06/2014

- STOP PRESS - (31 May 2014, 19:00 UT). Okay. Cees Bassa thinks last night's object is not USA 161. See here. So read the story below with caution: the jury is still out on all this.

Although it all was/is a bit confusing, it appears USA 166 (2001-044A), the secondary East plane KH-11 Keyhole/CRYSTAL has finally been recovered. [UPDATE: OR PERHAPS NOT???]. It had not been positively observed since August 2013 and over the past half year had been hiding in the northern hemisphere winter blackout.

USA 161 ?. IGS 8R last night
(click image to enlarge)

Initially, Leo Barhorst in Almere (NL) appeared to have recovered it on May 23. However, his observed object now turns out to not have been USA 161 but an unidentified other object.

Last night it was clear, after a very rainy week. Suffering from a bout of insomnia, I took advantage of the clear skies by conducting a 30 minute plane search, from 01:00 UT to 01:31 UT (May 31), using the EF 2.0/35 mm wide angle lens.

Just as I was about to abandon the effort at 01:30 UT, a bright and fast satellite appeared with a direction that was correct for USA 161 in a generally correct area of the sky. I managed to capture it on two images, the second one of which is depicted above. The object was about mag +2 when I first visually picked it up, and then becoming brighter as it produced a slow flare to mag -2 near 01:30:27 UTC. The image above shows the slow flare moment. It moved fast, producing long trails on the 10 second images with the 35 mm wide angle, so it evidently was near perigee.

The object could not be matched to any known object, but did appear to move in the general secondary East orbital plane of the KH-11. Visually, the slow bright flare it showed was quite typical for the KH-11 too. So I was (and am) fairly certain it is USA 161. Or not? Problem was, my observation was difficult to match with Leo's observation a week earlier...

After I reported my observations, Ted Molczan next managed to positively match my object to a UNID observation by Björn Gimmle in Sweden on April 22 (so over a month earlier), proceeding to fit a very reasonable orbit. The suggestion of this all is, that Leo's object from May 23 was something else, as it does not fit well with the other observations.

The preliminary orbit calculated by Ted, which needs to be refined by further observations, suggests that USA 161 made a manoeuvre into a (compared to the orbit it was last seen in in 2013) slightly higher orbit of 411 x 425 km, with the orbital inclination changed by half a degree to 97.52 degrees. This is the same orbital inclination as USA 129 (1996-072A), the former secondary West plane KH which we have recently "lost" and which is suspected to have been de-orbitted, was orbiting in.

Like the drifting secondary West plane KH USA 186 (2005-042A, see several previous posts on this blog for a discussion), USA 161 is no longer sun-synchronous as a result of this manoeuvre, and hence in what appears to be a plane transfer orbit. Its distance in RAAN relative to the primary East plane KH-11, USA 224 (2011-002A), has increased and will keep increasing steadily until it makes a corrective manoeuvre (which I suspect will happen near June 12, see below).

The orbital constellation for May 31 looks like this:

(image removed)
click image to enlarge

The current situation is that the two new primary plane objects, USA 224 and USA 245, are keeping a more or less steady plane distance (in terms of RAAN) of 48.5 degrees. The two (older) secondary plane satellites, USA 186 and USA 161 however have now both lost sun-synchronicity, and are both drifting outwards with respect to the orbital planes of their corresponding primary plane satellite.

Frequent readers of this blog will remember that I initially expected USA 186 to manoeuvre back into a non-drifting sun-synchronous orbit when the RAAN difference with USA 245 was 10 degrees, early February. That didn't happen. As a secondary option, I then thought it would manoeuvre when the difference was 20 degrees, early May. That didn't happen either. I then was at a loss as to what "they" were planning to do with USA 186.

Now USA 161 has been recovered and turns out to have been manoeuvered into a drifting plane-changing orbit as well, just like USA 186, I am getting a possible idea again about what they might intend. Please note: I have been wrong twice before, so my track-record in these kind of predictions is not quite good :-p

Nevertheless: assuming that symmetry is what is being aimed for, I think both objects (USA 186 and USA 161) will manoeuvre back into a non-drifting, sun-synchronous orbit on or near June 10 to June 12.

On May 31 the RAAN difference between USA 245 (primary West) and USA 186 (drifting secondary West) was 23.0 degrees. The RAAN difference between USA 224 (primary East) and USA 161 (drifting secondary East) was 23.7 degrees. Their rate of drift is different: it is -0.11 degrees/day for USA 186 and +0.056 degrees/day for USA 161 (i.e., USA 186 is drifting twice as fast as USA 161). These differential drift rates mean that at some point in time, both satellites will reach a matching value in RAAN difference with their primary partner, i.e.be at similar RAAN distances from their primary partner on the same day. This is depicted in the diagram below:

(image removed)
click diagram to enlarge

What can be seen from the diagram, is that this moment will occur in about 10-12 days from now, near June 10-12. On June 12, both satellites (USA 186 and USA 161) will reach a matching difference in RAAN of 23.3 degrees with their primary partners USA 245 and USA 224. Interestingly, this value is very close to 0.5 times the RAAN difference between the primary plane satellites, USA 224 and USA 245 which are 48.5 degrees apart in RAAN.

But please be advised: until now, I was wrong each time I thought I could make sense of it....

Wednesday, 21 May 2014

USA 224 recovered, USA 186 still drifting, and looking for GPS IIF-6 20 minutes after launch

For various reasons, I am a bit late in keeping the reader up to what is happening to the KH-11 Keyhole/CRYSTAL system of optical reconnaissance satellites.

USA 186 (2005-042A), the secondary West plane KH-11, is still in a non sun-synchronous orbit and hence still drifting westwards. It is drifting for over half a year now. The difference in RAAN with USA 245, the primary West plane KH-11, is now over 20 degrees (21.8 degrees on May 19th). I am very curious as to when the drifting will stop, if ever. If it continues to drift for many weeks to come, we should contemplate whether perhaps the satellite is "dead", i.e. has lost manoeuverability. Problem is that NW European observers temporarily have lost visibility of the satellite, due to the current short nights. Tracking all comes down now to observers in the US and southern Europe.

Meanwhile, Russell Eberst in Scotland recovered USA 224 (2011-002A), the primary East plane KH-11, on May 9th. It is in a 260 x 1006 km orbit, which means it has slightly lowered its apogee. Before the winter blackout it was in a 258 x 1023 km orbit. The difference in RAAN with USA 245, the primary West plane KH-11, is now 48.5 degrees.

My own first observation of USA 224 was in the night of May 16-17. The image below shows it crossing through Corona borealis:

click image to enlarge

USA 161 (2001-044A), the secondary East plane KH-11, has still not emerged out of the winter blackout. Meanwhile, USA 129 (1996-072A) has gone missing since April 24 (see a previous post). There is a good chance it has been de-orbitted.

The current KH-11 constellation now looks like this (where the current orbital configuration of USA 161, in red, is uncertain, and USA 129 left out as it is no longer in its old orbit, and presumed de-orbitted):




click images to enlarge

In the early morning of May 17 (evening of May 16 in the US) and after a one day delay due to bad weather, a new GPS satellite, GPS II-F6 was launched from Cape Canaveral on a Delta IV rocket. It would pass over the Netherlands some 20 minutes after launch, still ascending and still attached to the 2nd stage. A number of search orbit had been published, but it looks like none of these was very accurate. I visually observed a bright UNID near 00:24:00 UT (May 17) moving just a few degrees to the 'right' of Altair on a trajectory parallel to the predicted ones but some 20 degrees cross-track in a southern direction. It was already descending over the roof when I picked it up, so I had no time to snap a picture alas. It did not match any known object so I am quite confident it was GPS II F-6 on its way to orbit. It was bright, about mag +1 to 0.

Monday, 5 May 2014

KH-11 USA 129 is missing, USA 186 has still not manoeuvered

USA 129 (96-072A), the oldest of the KH-11 Keyhole/CRYSTAL/KENNAN optical reconnaisance satellites, has gone missing. The last observers to see it were me on April 22 and Russel Eberst on April 24. The photo below shows one of my images from April 22, with USA 129 passing near Castor and Pollux:


click image to enlarge

Somewhere between that date and May 1, when various observers noted it missing, it disappeared.

There is a possibility that it has been de-orbitted, as it is over 17.5 years old now and appears to be 'redundant' after the launch of USA 245 and plane move of USA 186 (see various earlier posts on this blog). On the other hand, we should be cautious and not too hasty: in the recent past (Feb 2014) we erroneously wrote USA 129's eulogy before, and it turned out it had just manoeuvered. Maybe it did this time as well. A dedicated plane watch I did in the evening of 3 May between 20:41 -21:05 UT yielded nothing.

Meanwhile, we had expected USA 186 (2005-042A) to manoeuvre early May. But up to yesterday May 4th it hasn't. Maybe it will do in the coming days. On May 1st the difference in RAAN with the main West plane KH, USA 245, was 19.8 degrees. At a drift rate of 0.11 degrees/day, it reached 20 degrees the past weekend. If it hasn't manoeuvered by the end of the coming week, it will become interesting. Unfortunately, it is disappearing in evening twilight for my location these days.

The image below shows USA 186 crossing Canis minor in deep evening twilight of May 2nd:

click image to enlarge

I imaged USA 245 (2013-043A), the current main West plane KH-11, last Saturday evening. In evening twilight, it was visible in the same camera field with FIA Radar 1 (2010-046A):


click image to enlarge

Sunday, 4 May 2014

Imaging SWARM A and C

On 22 November 2013, ESA launched SWARM, a group of three futuristically looking scientific satellites (2013-007A, B and C) whose purpose is to map the strength, variation and structure of the Earth's magnetic field. Two of the three operate as a close pair in a similar orbital plane at 460 km altitude, the third at 530 km altitude will eventually orbit at an angle to the orbit of the other two (the orbital plane is currently still quite similar, but that will change over the coming years).

The satellites look like a cross between a techno aardvark and a vacuum cleaner:

image credit: ESA

On the night of May 3-4 I was taking images with the EF 2.0/35mm wide field  in an attempt to recover KH-11 USA 224. I did not recover USA 224 but my images showed a number of objects. Including a serendipitous catch of the SWARM A & C duo (2013-007B & C) crossing through Cygnus near 23:32:02 UTC.

click image to enlarge


The yellowish whisps in the image are clouds. SWARM C shows a bright flare near the start of its trail, then the brightness suddenly drops. SWARM A is faint.

Sunday, 20 April 2014

[UPDATED & CORRECTED] Observing the SpaceX Dragon CRS-3, the ISS and two pieces of Dragon launch debris

CORRECTION (21/04/2014 12:55 UT): in the initial post, the two debris pieces were misidentified. "2014-022C" turned out to be 2014-022H, and "2014-022H" turned out to be 2014-022G.

click image to enlarge

Last Friday at 19:25 UT, SpaceX launched the Dragon CRS-3 commercial supply ship to the International Space Station ISS. It passed over Europe 20 minutes later but unfortunately I was clouded out in Leiden. In the middle and eastern parts of the Netherlands as well as elsewhere in Europe, observers were treated to a spectacular view of the Dragon, the Falcon upper stage, and two faint pieces of debris passing by as a thight group of objects.

SpaceX Dragon CRS-3
click image to enlarge

I was more lucky yesterday when the sky was clear and the Dragon and ISS made a late twilight pass culminating at approximately 26 degrees altitude in the SW near 20:06 UT (22:06 local time, sun at -12 deg.). The image above shows the Dragon CRS-3 due south already somewhat past culmination. It was easy to see with the naked eye, attaining magn. +1.5. Its brightness is more similar to a Progress or ATV then to the much fainter commercial Orbital Sciences Cygnus.

The Dragon was about 1m 12s behind the ISS, a visual distance of somewhat over 40 degrees. Pre-observation predictions based on elements a few hours old had put it in front of the ISS, so at first I was wondering whether I missed it. Then, as the ISS was descending towards the SE, I saw it approaching in the SW, chasing the ISS. A very fine sight!

The ISS passing the same sky area as the
earlier image, 1 min earlier
(click image to enlarge)

While I was photographing at the nearby city moat, I had also set up the video in my girlfriend's appartment, and this capture both objects as well: first the ISS, then a minute later the Dragon:




(the display says "GPS BAD" because my GPS time inserter failed to lock on a GPS satellite. I hope it is not broken...)

Apart from the Dragon and the ISS, I observed and photographically imaged a third debris object related to the launch. It is the object catalogued by JSpOC as 2014-022C/#39682. 2014-022H, #39687. It is either the jettisoned Dragon nose cone cover, or one of the solar panel covers   or possibly one of the Nanosat dispensers: I think it is too bright to be one of the several released nanosats itself. It was faint and slowly tumbling, alternating between invisibility and a max magnitude of about +3.5:

tumbling Dragon debris 2014-022H
(click image to enlarge)


[UPDATE:] Later I discovered a second piece of Dragon CRS-3 launch debris on my imagery. It is faint, irregular in brightness and present on two images, the best of which is this one from 20:04:07 UTC:

tumbling Dragon debris 2014-022G
(click image to enlarge)


This turns out to be the object designated 2014-022H, #39687  2014-022G, #39686. This is the other solar panel cover.

Saturday, 12 April 2014

Progress M-22M in twilight

Yesterday evening in late twilight (sun 11 degrees under the horizon, waxing gibbous moon low in the sky) I observed Progress M-22M (2014-005A), the Russian cargoship that undocked from the ISS on April 7.

 click image to enlarge

The undocked Progress will be flying solo for several days, during which ionospheric tests are conducted. It will be de-orbitted on April 18 near 15:43 UT.

As usual, the Progress spacecraft was easily visible to the naked eye, reaching about mag. +2. It passed between Gemini and Canis minor (and roughly halway between Procyon and Jupiter, see image above), then over the head and body of Leo and through the Coma Berenices cluster (see imagebelow) before disappearing behind the roof. It was about 25 minutes ahead of the ISS.

click image to enlarge

25 minutes later I did a first attempt to image the ISS in high resolution through my C6. I managed to get two images of it, but they are not of good quality. I guess I have to practise a bit more :-)

Thursday, 10 April 2014

Eagle Eyes

Recently I posted a topic on USA 184, one of the SBIRS-HEO satellites. That post was illustrated with amongst others this patch:

click image to enlarge

A sharp eyed reader, graphic designer and illustrator Olivier Rossel (PXP), noted something odd in the patch. More exactly, in the bothom "beard" of feathers of the Eagle's head.

I had not noted it until Olivier pointed it out (and it is so obvious now!), but letters are spelled out there:

(image courtesy of Olivier Rossel)

You can read the words "GEO", "DSP" and "HEO". These are all relevant to the US Infrared Early Warning system. SBIRS has satellites in two kind of orbits: GEO (geosynchronous) and HEO (Highly Elliptical Orbit - see my earlier post). DSP is the Defense Support Program, the predecessor of the newer SBIRS, consisting of a number of satellites in GEO.

Some Russian guy, Ivan Karavay, identified the words earlier in a post in this forum (in Russian) but I had never seen it until Olivier pointed it out to me.This while I knew words are sometimes hidden in NRO-related patches. Take these patches for example, from the NRO launches NROL-25, NROL-34, NROL-41 and NROL-49:





click images to enlarge

In the "vermicelli" that fills in the Earth in these patches, letters can be discerned that sometimes solve into acronyms: "4 SLS" (4th Space Launch Squadron),  NRO or NROL, and other letter combinations that are less easy to interpret.

Speaking of logo's and patches: I recently re-designed the logo of SatTrackCam. The new design is based on the older design but less cluttered:

click image to enlarge



Like in NRO patches, there is some coded information in this design: the Coat of Arms for example has a double meaning. The (pig-) Latin actually refers to a notorious NRO patch, as well as a famous internet meme.

Tuesday, 1 April 2014

[updated] The bright fireball over Germany of 31 March 2014, 22:34 CEST: an earthgrazing meteor, not a satellite re-entry

[updated 20:55 UT (1/4/2014) to reflect revised fireball duration]

Yesterday evening German astronomical internet fora and my Twitter timeline erupted in a frenzy about a very bright, magnitude -10, west to east moving, very long duration fireball seen over southern Germany near 20:34 UT (22:34 CEST, March 31).

The fireball was widely seen by eye witnesses and captured by a video all-sky station near Ulm. The very spectacular image, by Thomas Tuchan, can be seen here (scroll down in the message list) on the AKM message forum.

As usual, it was science writer Daniel Fischer who was the first to knock on my digital door for an opinion. The question that had popped up, as it does with every long duration slow fireball, was whether this was a meteoric fireball or perhaps a satellite re-entry? In most cases, it is not, although there are exceptions.

My first check in such cases always is with JSpOC to see whether there was a suitable re-entry candidate in the TIP-messages. There was not. This while a re-entering artificial object of this brightness must be a very big object, for which you expect a TIP message.

Next more information came available on the fireball length and duration, notably through Thomas Tuchan's all-sky video image. It shows an almost horizon to horizon event, with a duration of 16 33 seconds. It starts at approximately 15 degrees elevation in Perseus, culminates at 60 degrees North, and ends low on the opposite horizon, at an elevation of about 12 degrees. A span of some 150 degrees!

[Update 20:55 UT: the duration was later revised to 33 seconds]

The very long 150 degree trajectory with a duration of 16 seconds rules out the re-entry of an artificial object. It shows that this was a meteoric fireball, and one that entered the atmosphere at a very shallow angle: a so called Earthgrazing meteor. There are even some examples (most famous one the Grand Tetons fireball of 1972) where such Earthgrazing fireballs left the Earth's atmosphere again!

Satellite re-entries take place between 150 and 50 km altitude. At such altitudes, an earth-orbiting object has a speed of 7.5-7.8 km/s and the resulting apparent angular velocity is about 3 degrees/second for 100 km, and about 5 degrees/seconds for 50 km altitude: but only in the zenith. Lower above the horizon, the angular speed is much less.

I constructed an artificial set of orbital elements for an orbital altitude of 90 km (re-entry in progress) as a test: it takes such an object 1 minute 15 seconds to move from 15 degrees elevation above the western horizon to 15 degrees elevation on the opposite horizon. By contrast, it took the German fireball only 16 33 seconds: i.e. almost a factor two-and-a-half faster.

[Update: the duration was first reported as 16 seconds, later revised to 33 seconds]

All this makes very clear that the German fireball of March 31 was not the re-entry of an artificial object, but a meteoric fireball, most likely an Earth-grazing object of asteroidal origin..

Monday, 31 March 2014

Observing USA 184 (TRUMPET-FO/SBIRS-HEO)

It had been a while since I last observed objects in HEO (Highly Elliptical Orbit). Most of my recent focus has been on the KH-11 in Low Earth Orbit and on geosynchronous objects.

USA 184, 29 March 2014, 21:34 UTC
click image to enlarge

Last Saturday evening I however targetted USA 184 (2006-027A), a classified US military satellite in HEO which hovered almost in the zenith for my locality during the observation. It is the tiny trail indicated by the arrow in the image above, taken with my Canon EOS 60D and a 2.8/180mm Zeiss Sonnar MC. Stars in the image belong to Ursa maior.

A Highly Elliptical Orbit (HEO) is an orbit which is highly eccentric ("elliptical") with a low perigee at only a few hundred kilometers altitude (usually in the southern hemisphere) and a high apogee, often in the 20 000 to 39 000 km altitude range. The orbit is typically inclined by about 63 degrees.  USA 184 is in a 63.58 degrees inclined, 1590 x 38 760 km orbit.


USA 184, orbital position 29 March 2014 21:34 UTC
click image to enlarge

Satellites in such an orbit spend a long time near the apogee of the orbit. As a result, they hover high above the northern hemisphere for many hours a day. Just like a geosynchronous orbit, this allows long duration coverage of a (large) area. The difference with a geosynchronous orbit is that a HEO orbit is well suited to cover high polar latitudes, while a geosynchronous orbit has a poor coverage of such high latitudes. HEO orbits are therefore typically used for applications that demand long-duration coverage of high Northern latitudes. It concerns communications satellites (notably by the Russians), SIGINT satellites and Infrared Early Warning satellites.

USA 184 falls in the latter two categories. It is a TRUMPET-FO (the FO stands for "follow-on", i.e. it is an improved version of the older TRUMPET) SIGINT satellite. In addition, it has a piggyback SBIRS (Space Based Infrared System) package, which is dedicated to the detection of ICBM launches by their Infrared signatures. It is one of two HEO sensors in the SBIRS system (the other one is on USA 200, 2008-010A), in addition to the two dedicated SBIRS satellites in geostationary orbit (SBIRS-GEO 1 and SBIRS-GEO 2, 2011-019A and 2013-011A).

At the time of the observation, USA 184 was at an altitude of  38 355 km over the Northern Atlantic at 62.74 N, 4.84 W. It was almost in its apogee, and hovered at 76 degrees elevation in the sky. This is the approximate view from the satellite at that time:


view from USA 184, 29 March 21:34 UTC
click image to enlarge 

The images below are uniform patches related to the launch of USA 184 (as NROL-22 on 27 June 2006), and the SBIRS program:







note: the orbital diagrams were made with JSatTrak software and amateur orbital elements calculated by Mike McCants.

Saturday, 29 March 2014

An update on the evolving KH-11 Keyhole/KENNAN/CRYSTAL system

In several previous posts from September 2013 onwards, I analysed and prognosed changes to the KH-11 Keyhole/KENNAN/CRYSTAL optical reconnaissance satellite system. Main focus was on the changes, notably in the orbit of USA 186 (2005-042A), following the addition of USA 245 (2013-043A) as a replacement for USA 186 in the Keyhole primary West plane.

Indeed, as predicted, USA 186 was moved out of the primary West plane, and started to drift towards the secondary West plane in mid-November 2013 following a manoeuvre that changed its inclination and made it loose sun-synchronisity.

USA 186 is still drifting westwards. It currently is moving westward at a rate of 0.11 degree/day relative to USA 245 (2013-043A), the primary satellite in the West plane since the autumn of 2013. The difference in RAAN between the two satellites currently is slightly over 16 degrees:


 click images to enlarge

Late 2013 and early 2014, I expected that the drift would end early February 2014, when the RAAN difference between USA 245 and USA 186 reached 10 degrees, the old separation between USA 186 and USA 129, the former primary and secondary West plane satellites. I was proven wrong with my prediction, when USA 186 continued to drift past that date.

I then turned to a second scenario: that the intended RAAN difference between USA 245 and USA 186 will be 20 degrees, similar to the difference between USA 224 and USA 161 in the East plane.

With the current rate of precession of 0.1111 degrees/day relative to USA 245, the RAAN difference between USA 186 and USA 245 will reach 20 degrees near May 1. So I expect USA 186 to manoeuvre into a lower, sun-synchronous orbit on or near that date. The KH-11 constellation will then look like this:



click images to enlarge

An open question is what will happen to USA 129 (1996-072A), the over 17 year old former secondary West plane satellite. I still think it will be de-orbited somewhere this year. But I have been wrong before.

Note: the orbits for USA 129, USA 186 and USA 245 in the West plane in the images above are based on recent observations. The East plane satellites USA 161 and USA 224 have not been observed since autumn 2013, and will not be visible from the Northern hemisphere before mid-April. There is therefore a possibility that one or both have moved, but since we have no information on their current whereabouts, I have depicted them in their 'old' orbital planes of the autumn of 2013 relative to the West plane.

Friday, 28 March 2014

A flare show by USA 245

Wednesday evening saw a dynamic atmosphere, where clear skies intermittently were broken by fields of fast moving scattered clouds.

I targeted all three West plane KH-11 Keyhole/CRYSTAL satellites that evening: USA 129 (1996-072A), USA 186 (2005-042A) and USA 245 (2013-043A).

USA 245 had a pass during a period where patches of clouds occupied the southern sky up to the zenith. The image below shows it rising through Leo, over the roof of my house, amidst scattered clouds:

click image to enlarge

USA 245 twice flared brightly during this pass. Such flares are caused when a reflective surface on the satellite (solar panels, an antenna panel, a dish or some other part of the structure) acting like a mirror reflects sunlight directly towards the observer. I love it when they do that, it is always spectacular.

The first flare was a slow bright one up to magnitude -2 peaking near 20:27:28 UTC (26 March) just above the back of Leo:

click image to enlarge

One-and-a-half minutes later at 20:29:03.64 UTC, while passing through Uma, it flared again, a more brief glint/flare to magnitude -1:

 click images to enlarge

USA 129 was also observed, low in the west while emerging from earth shadow. It only faintly registered on one image, allowing one position determination. USA 186 was not seen, but this was likely due to unfavourable circumstances (it was too faint for the lens used) as Cees Bassa did observe it, on-time, the next day.

Sunday, 23 March 2014

First post winter-blackout observations of KH-11 Keyhole/CRYSTAL USA 129

One by one the KH-11 Keyhole/CRYSTAL optical reconnaissance satellites are emerging from the Northern hemisphere winter black-out. Following USA 186 (2005-042A) on Feb 21, and USA 245 (2013-043A) on March 3, USA 129 (1996-072A) has now been recovered as well on March 21.

USA 129 was last seen by Greg Roberts in South Africa on Feb 12.  It had hence not been seen for over a month until it was recovered by me and Leo Barhorst last Friday evening. Below is my recovery image:

recovery image of USA 129, 21 March 2014
click image to enlarge

This means all three objects in the West (evening) plane have now been recovered. Recovery of the two East (midnight) plane objects (USA 161 and USA 224) will have to wait until mid-April.

I went to my secondary site in the Cronesteyn polder in the evening of March 21, with the explicit aim of recovering USA 129. I had aimed the camera, with the 1.4/85mm lens, at 33 degrees elevation, at a point covering the orbital plane of the satellite where it should just have emerged out of earth shadow.

And it did, 104 seconds late and 0.8 degree off-track from the orbital elements based on Greg's last observation of Feb 12. Running a series of images for several minutes, I snapped it on two images.

In Almere (also in the Netherlands), some 55 km Northeast of me, Leo Barhorst also captured it using his WATEC camera, and reported it as an "unknown".

Over the coming days, we hope to capture more positions as the satellite gradually becomes more visible.

click image to enlarge

That same evening, I photographed two other classified objects: USA 186 (2005-042A, above, with two strays Russian rocket boosters in the image as well) and SAR-Lupe 5 (2008-036A), a German military Synthetic Aperture Radar satellite.

click image to enlarge

SAR-Lupe 5 was captured by accident, when I was making a test image to check lens focus. Two satellites showed up in the test image: the very old Russian weather satellite Meteor 1-5 (1970-047A) and SAR-Lupe 5. As I had not carefully timed this image (I did not expect a classified object to be in it), Meteor 1-5 provided a welcome time calibration for the image. SAR-Lupe 5 was 57 seconds early and 1 degree off-track relative to 10-day old orbital elements.

Monday, 17 March 2014

Open Question: Could US Military SIGINT satellites help to narrow down flight MH370's last location?

Please note: this post contains discussions of a highly speculative nature

Over the past days, it has become clear that the lost Malaysian Airlines flight MH370 has flown on for some 7 hours after contact was lost at 17:20 UT (March 7 UT, local March 8). This information comes from radio "ping-backs" of the aircraft's ACARS system received by the Inmarsat 3-F1 satellite, a geostationary communications satellite that is located at longitude 64 E over the Indian Ocean. These ping-backs were received hours after the last radio contact with the pilots and hours after the transponder was shut off, and indicate that the aircraft was still powered and 'alive' hours after it disappeared. A well written story at the CNN website gives backgrounds on the receptions and the system.

Position and footprint of Inmarsat 3-F1
click image to enlarge

In this post, I will briefly summarize how Inmarsat 3-F1 detected the aircraft and determined a wide arc where the aircraft could have been at that time. I will then explore whether additional signal receipts by classified US Military Signals Intelligence (SIGINT) satellites might perhaps have been possible. If such additional receptions exist (an open question!) they would enable to further narrow down the location of the last ping-back.

That will largely be a theoretical exercise, as so far there has been no word that the US SIGINT satellite constellation did detect these ping-backs. This post therefore entails a clear element of speculation, and the central question remains an explicit open question.


Backgrounds: 'Marco Polo' between an aircraft and a satellite

Someone in the aircraft shut off the radar transponder beacon and the active ACARS messaging system near 17:20 UT. Yet this did not fully disable the ACARS system. The system kept answering periodic "pings" by the Inmarsat 3-F1 (1996-020A) satellite. These "pings", basically a kind of "Marco?" message,  are periodically sent out by the satellite and when received by the aircraft ACARS antenna, the aircraft pings back a brief "handshake" basically saying "Polo!". While such a handshake does not contain clear information about where the aircraft is when the active ACARS is disabled, it does contain the aircraft ID.

According to press reports, the last ping-back from flight MH370 was received 7 hours after the flight disappeared, near 00:11 UT on March 8. Apparently, only Inmarsat 3-F1 received these ping-backs.

From the time it took the radio-ping to travel from Inmarsat 3-F1 to the aircraft and then back again, the distance (but not direction) of the aircraft to the satellite can be determined. For example, at a radiowave speed of 300 000 km/s, a time difference of say 0.2 seconds between Inmarsat sending the ping and receiving the answer back, indicates the aircraft is at a distance of 30 000 km from the satellite.

Once you know the distance, you can draw a globe with that radius around the location of the Inmarsat satellite. Where that globe cuts the earth surface, it creates a circle, centred on the sub-satellite point. The aircraft must have been somewhere on that circle. This is basically how the wide arc that has been published was constructed, an arc which runs from Thailand to Kazakhstan in the north, and Indonesia to Australia and the Indian Ocean in the south. The aircraft could have been anywhere on that big arc, an area stretching thousands of kilometers.


To pinpoint the aircraft more accurately to a particular spot in the arc, one needs a detection by a second and preferably a third satellite.


Could US SIGINT satellites provide additional receptions for these pings?

One source of such additional ping-back signal receptions, in theory could be one of several Signals Intelligence (SIGINT) satellites employed by the US military. Please note that I say IN THEORY as the US government hasn't provided any statements that they did (which might indicate that they didn't). In other words: I am speculating on an open question here.

It depends on a lot of factors, not the least of which are questions whether these satellites were listening at the time, and whether they were monitoring the particular VHF/UHF radiofrequencies in question. Those are questions I do not have the answers to. What I will do, is discuss which US military satellites could potentially have received these ping-backs because they had coverage of the area.

1. The Mentor and Trumpet SIGINT satellites

Two US SIGINT systems in high orbits cover(ed) the relevant area: (1) several of the very large Mentor/Advanced Orion SIGINT satellites in geostationary orbit: and (2) one of the SBIRS/TRUMPET combined SIGINT and SBIRS satellites which moves in a Highly Elliptical Orbit and hovered high above the northern hemisphere at the time.

These SIGINT satellites serve to eavesdrop on radio communications including satellite- and mobile telephony, missile telemetry and signals from groundbased and airborne radar systems.

USA 184 TRUMPET imaged on 25 Aug 2009 by the author

 Mentor 4 imaged on 18 Nov 2012 by the author


The TRUMPET satellite in HEO which had coverage of (a part of) the area at that time is  USA 184 (2006-027A). The geostationary Mentor satellites covering the area are Mentor 1, 3, 4, 5 and 6 (1995-022A, 2003-041A, 2009-001A, 2010-063A and 2012-034A).

Position of various Mentor satellites and TRUMPET USA 184
Mentor satellite footprints


USA 184 area coverage and footprint detail
click image to enlarge

2. NOSS (Naval Ocean Surveillance System) SIGINT satellites

Apart from the Mentor and Trumpet SIGINT satellites in high orbits, the US also operates a series of SIGINT satellites with accurate geolocalization capabilities in a Low Earth Orbit. It concerns the US Navy Naval Ocean Surveillance System (NOSS) satellites, of which there are several. They operate in close pairs, orbiting at an altitude of about 1000 x 1200 km in 63 degree inclined orbits. Their main purpose is to locate and track shipping through the radio communications of the latter.

A NOSS duo (NOSS 3-4) imaged by the author on 29 Jan 2011


Two duo's of NOSS satellites were covering the northern half of the area at the time of the last ping-back received by Inmarsat 3-F1: the NOSS 3-5 and NOSS 3-6 duo's (2011-014A and B and 2012-048A and P).

The NOSS 3-6 duo had the best coverage, which includes the full northern arc from Thailand to Kazakhstan determined by the Inmarsat reception:

click images to enlarge
position of the NOSS 3-5 and NOSS 3-6 duo at the time of the last pingback

in 3D: yellow arc is where the aircraft could be according to the Inmarsat 3-F1 reception

Chinese SIGINT

China operates a satellite system similar to the US NOSS, consisting of three satellite trio's in the Yaogan series (Yaogan 9A, B, C; 16A, B, C; 17A, B, C). None of these however had coverage of the relevant areas in the Indian Ocean, central Asia or southern Eurasia at that time.

Coverage summary

From the brief satellite coverage analysis summed up above, it seems that the northern overland arc from Thailand to Kazakhstan was potentially well covered by various US military SIGINT satellites: five Mentor satellites, a TRUMPET and a NOSS duo. The southern Indian Ocean arc is slightly less well covered (no TRUMPET or NOSS coverage) but was nevertheless in view of several geostationary Mentor SIGINT satellites.

The question now is: could one or more of these SIGINT satellites have captured the same ACARS ping-backs received by Inmarsat 3-F1? If so, the combination of their data with the Inmarsat data could potentially narrow down the last known position of the aircraft considerably.

It all depends on whether the satellites in question were actively listening at that time, and moreover, whether their monitoring includes the radio frequencies in which the ACARS ping-backs of flight MH370 operated. It perhaps also includes questions like whether any signals received are all kept on file, or if some selection is made and much deemed of no interest is directly discarded.

Those are some big serious "ifs", that I simply do not know the answers to: this stuff is, after all, classified. So far, the US government has not indicated that one of their SIGINT systems did capture the ping-backs. Which might mean that they didn't, as I can't imagine that they did not check for it.

Classified SIGINT satellite positions in this post (and previous posts) are based on orbits calculated by Mike McCants, based on amateur observations communicated on the SeeSat-L mailing list.


Addendum 18 March 2014:
In my initial analysis posted 17/03/2014, I forgot to include two other and older geostationary US SIGINT satellites: the two Mercury/ADVANCED VORTEX satellites that are located over East Africa.


 click images to enlarge

It concerns Mercury 1  (1994-054A) and Mercury 2 (1996-026A). Both satellites were recently moved to a new orbital position over East Africa and are station-keeping there, indicating they are operational. Their footprint includes the area of interest, although the southern Indian Ocean arc is close to the edge of their coverage.

Mercury 1 imaged by the author on 29 Dec 2013