Showing posts with label Mentor 6. Show all posts
Showing posts with label Mentor 6. Show all posts

Monday, 14 December 2015

Imaging Geostationary satellites, and PAN's past relocations

Last week saw some clear evenings, and I used one of them to image some geostationary satellites. It concerned "the usual suspects": MENTOR's, MERCURY's and the enigmatic, probably SIGINT satellite PAN (2009-047A). The latter satellite has not been moved for quite a while now: since the end of 2013 it is at longitude 47.7 E, parked close to a number of commercial comsats. In the past it was frequently relocated, taking positions next to various commercial COMSATS. In four years time between 2009-2013, it moved at least 9 times (which is a lot) to various longitudes between 33 E and 52.5 E.

PAN amidst several commercial COMSATS on 9 December 2015 (click to enlarge)

The diagram below charts these frequent movements of PAN. Relocations typically took place about once every 6 months. Late 2013, they stopped. PAN however must still be operational, as active station-keeping is necessary for it to stay at 47.7 E.

relocations of PAN over time, 2009-2015 (click to enlarge)

Four other SIGINT satellites and a military comsat were imaged as well: Mentor 4 (2009-001A) and Mentor 6 (2012-034A), Mercury 1 (1994-054A) and Mercury 2 (1996-026A), and the military comsat Milstar 5 (2002-001A).


Mentor 4, next to commercial comsat Thuraya 2 on 9 Dec 2015 (click to enlarge)

Mentor 6 and a number of commercial satellites, close to the Orion nebula, on 9 Dec 2015

Using the remote telescope at Warrumbungle (MPC Q65) in Australia, I recently (4 December 2015) also checked-up on the recently launched US Navy COMSAT MUOS 4 (2015-044A). It is still at its check-out location over the Pacific at longitude 172 W, but some recent press statements suggest check-out has been successfully completed, and it will be moved to its operational position at longitude 75 E near India in the spring of 2016.

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

Thursday, 2 January 2014

An unknown object in (near) Geostationary orbit: Express AM-5?

The evening of December 29 2013 started clear, so I did a small survey of a part of the geostationary belt. Main focus of the session was PAN, as well as Mentor 4 and 6.

Inspecting the images I found an unidentified object in near-Geostationary orbit some 4 degrees east of PAN, between Mentor 6 and NSS 5, on several images (positions here). The image below shows it near M42, the Orion nebula, near 19:17 UT:

click image to enlarge

In addition to the UNID you can also see a classified satellite at left, Mentor 6 (2012-034A), a SIGINT satellite also known under the code name Advanced Orion. At right are two commercial geostationary satellites, NSS 5 (1997-053A) and Galaxy 26 (1999-005A).

Cees Bassa in the Netherlands and Greg Roberts in South Africa also observed what is likely the same UNID object later that night. While it is not easy to fit a reliable orbit to such a relatively short span of observations, the suggestion is an object with an inclination near 0 and a Mean Motion of about 0.92 revolutions per day, i.e. an object near Geostationary altitudes.

The Mean Motion could suggest an old object being moved to a Graveyard Orbit. If this is the case, we haven't been able to identify which 'old' object it is yet.

Another option is that this is a new object. The only likely candidate in that case is the Russian satellite Express AM-5 which was launched on December 26th. This object seems to have been temporarily "lost" by JSpOC: as I write this (Jan 2),  Space-Track does not list orbital elements later than December 26th (when it was still in  a temporary transfer orbit).

For the moment, Mike McCants has given it the name UNK 131229 (with the acronym UNK meaning "Unknown").

This observing session also served to check on PAN (2009-047A). PAN is a highly mobile satellite and often moves position in May and December (I have written on the mystery of this satellite before). Not this time, it seems: it is still at the position it has been in for several months, forming a trio with the commercial satellites Yahsat 1B and Intelsat 10:


click image to enlarge

Other classified objects imaged this night were the old SIGINT Mercury 1 (USA 105, "Advanced Vortex", 1994-054A), and the SIGINT Mentor 4 (USA 202, 2009-001A). Mercury 1 was placed at 48 E and recovered by me about a year ago.


click images to enlarge

During this observing session, I captured a bright irregular orange light moving across the sky: a 'Thai Lantern' ( a miniature hot-air balloon). They are the cause of many false fireball and re-entry reports. Here it is, moving through Orion while carried by the wind:



Two days earlier, on December 27, I also did my periodic check on Prowler (90-097E), using the 61-cm Cassegrain of Sierra Stars Observatory in Markleeville, California (MPC G68).

I concluded the evening of the 29th by making some shots of M31, the Andromeda Galaxy. Unfortunately, some thin haze came in after a while. The image below is a stack of 16 haze-free images of 30 seconds exposure each, with a CLS filter (against light pollution - the images were taken from Leiden town center)) and Zeiss 2.8/180mm lens piggyback on the mount of my C6:

click image to enlarge

Monday, 17 September 2012

Tracking the new NOSS 3-6 (NROL-36) launched September 13th, and imaging USA 237 (NROL-15) and SDS 2-2

NROL-36 (NOSS 3-6)

At 21:39 UTC on September 13th, 2012, the NRO launched NROL-36 from Vandenberg AFB. The launch vehicle was an Atlas V containing a classified NRO payload in addition to a number of cubesats. Several analysts already suspected the classified payload of this launch to concern a new duo of US Navy NOSS satellites.

That suspicion appears to be born out by the first observations of the launched objects, which show two satellites in close formation, typical of a NOSS formation.

The Centaur last stage was the first object from this launch to be observed, by Björn Gimle in Sweden, who observed it 5 hours after launch, and then by BWGS chair Bram Dorreman in Belgium 1.5 hours later, who remarked it was variable in brightness. Alas I was clouded out in Leiden at that moment. Eleven hours after launch, Kevin Fetter in Canada observed it next. Over the following day Russell Eberst in Scotland and Scott Tilley in Canada added more observations.

The payloads were first observed by Kevin Fetter in Canada near 9:43 UTC (Sep 14), 12 hours after launch. Scott Tilley, also in Canada, next observed them on the 15th near 12:34 UT.

On the morning of the 16th, 2 days and 5 hours after the launch, it was clear in Leiden allowing me to join the chase. I (photographically) observed the Centaur r/b pass at 2:49 UTC (see image below) and then the payloads at 2:55 UTC (Sep 16).

The NROL-36 Centaur booster
(click image to enlarge)

The observations were done under difficult conditions: it was somewhat hazy, the passes were at very low altitude due east (only 14 degrees elevation for the Centaur and 21 degrees elevation for the payloads), and the phase angles for the objects were unfavourable, resulting in dim magnitudes (around +7 for the payloads). The resulting images (one of them below) are therefore not quite pretty: even with use of the 1.4/85mm SamYang lens the trails were so faint that they were marginally visible at best. As reported earlier by Scott Tilley, the leading object indeed seemed to be somewhat variable (on some images it wasn't visible at all).

The NROL-36 payloads (NOSS 3-6)
(click image to enlarge)

Over the next days, I'll hopefully be able to obtain much better imagery during more favourable passes (this morning I was alas clouded out again, however....)


USA 237 (Mentor 6?)

That same morning, following the NROL-36 related observations, I took a few images of the area near the bright geostationary Mentor 4 (USA 202, 2009-001A). These images not only recorded this 3-year-old Mentor, but also the geostationary satellite USA 237 (2012-034A), a classified NRO payload launched from Cape Canaveral as NROL-15 on 29 June 2012, employing an Atlas IV-Heavy as launch vehicle.

These were my first observations of this object: tracking of this object over the summer was done mostly by Greg Roberts in South Africa (who was the first to discover the object) and Peter Wakelin in Britain. Over the summer it had slowly been drifting westwards: as of mid-September 2012 it appears to have stabilized at 47.8 E. For me in Leiden it is currently located at 20 degrees elevation in azimuth 129 degrees (low SE), about 6 degrees separated from Mentor 4 in the sky.

USA 237 (NROL-15)
(click image to enlarge

The identity of this object is still provisional. There have been some thoughts that NROL-15 launched a stealth Misty satellite in LEO/MEO and then progressed to put a decoy (the object designated as USA 237) in geostationary orbit. USA 237 is very bright however (about mag. +8), ranking it among the brightest geostationary objects in the sky, the Mentor SIGINTs. As Ted Molczan showed, they seem very similar in terms of absolute brightness. The likeliness can be well seen in the photographic comparison below, which shows Mentor 4 and USA 237 (the crops come from one and the same image):

(click image to enlarge)

This gives reason to think that NROL-15/USA 237 is perhaps a sixth Mentor SIGINT (i.e., it is Mentor 6).


SDS 2-2

As by-catch of the NROL-36 payload and Centaur observations, I also obtained my first observations of the geostationary SDS satellite SDS 2-2 (USA 67, 1990-097B). It is located at an elevation of only 16.5 degrees, very low in the east for me. To my surprise, it was rather bright and easily visible in the 5-second exposures, of which the one below is one:

 (click image to enlarge)