Showing posts with label SIGINT. Show all posts
Showing posts with label SIGINT. Show all posts

Friday, 14 March 2025

The Russian eavesdropping satellite LUCH (OLYMP-K) 2 has moved significantly

click diagram to enlarge

I have written before on this blog about the Russian military SIGINT satellite LUCH (OLYMP-K) 2 (2023-031A). It was launched  on 12 March 2023, and like its predecessor LUCH (OLYMP-K) 1, it has since moved about along the geostationary belt, doing proximity operations near western commercial geostationary satellites. 

Each two to four months, it is moved to a new target, where it stays in close proximity until moved to a new target again, behaviour in a similar fashion to the US satellite PAN/NEMESIS-1 in the past. It is probably clandestinely accessing and monitoring communication streams of the target satellites, and perhaps mapping contact networks. It can sometimes come very close to its target, to within a few to a few tens of kilometers (that is very close in space).

From September 2024 onwards it was positioned at 0.93 W close to Intelsat 1002, but on February 7, 2025, it started a drift eastwards. After a significant one-month drift over 62 degrees in longitude, it settled again on March 7 near 62 E, its new eavesdropping target being Intelsat 39 (2029-049B). This latest move is the largest since it was launched.

Due to a combination of flu, moonlight and the fact that the new position is barely above the eastern horizon for me, I have not been able to image it in its new position yet.

The diagram above shows the various repositionings of LUCH (OLYMP-K) 2 since it was launched. Since launch, it has taken up the following positions:

PERIOD                     LONG.      NEAR
21-03-2023  24-03-2023     78.00 E    (checkout) 
07-04-2023  02-05-2023     58.00 E    (checkout) 
22-05-2023  25-09-2023      9.00 E    EUTELSAT (KA SAT) 9A, EUTELSAT 9B
04-10-2023  04-12-2023      3.20 E    EUTELSATt 3B
05-12-2023  26-03-2024      2.60 E    EUTELSAT KONNECT VHTS
01-04-2024  22-06-2024      4.75 E    ASTRA 4A
01-07-2024  16-09-2024      0.54 W    THOR 7
18-09-2024  07-02-2025      0.92 W    INTELSAT 1002
07-03-2025                 62.02 E    INTELSAT 39

Saturday, 21 September 2024

The Russian SIGINT satellite LUCH (OLYMP-K) 2 has moved again

LUCH (OLYMP) 2 position change. Click image to enlarge

 

Luch (OLYMP) 2 (2023-031A), the second Russian OLYMP-K/LUCH 5X SIGINT satellite in geosynchronous orbit, has changed position several times since its launch in 2023. Each time, it was placed near a commercial communications satellite. I have written about it before on this blog (e.g. here), and two (here and here) 2023 Space Review article by Bart Hendrickx provides more background on the OLYMP-K program.

And now LUCH (OLYMP) 2 has moved again. From its previous position stalking THOR 7 (2015-022A) at longitude 0.54 W, where it arrived on July 1 2024, it has now made a small hop to the other side of the THOR + INTELSAT grouplet, to 0.92 W, taking a position inbetween THOR 6 (2009-058B) and INTELSAT 1002 (2004-022A).  

The move started on 16 September 2024 near 22 UTC and was completed on September 18.

LUCH 2 positions over time. Click diagram to enlarge

 
detail of the lastest move (top). Click diagram to enlarge

The photographs in top of this blogpost shows the change in position by LUCH (OLYMP) 2 over the past week: basically moving from one end of the grouplet to the other.

(as soon as the moon is less of a nuisance, I will attempt to get a better picture of LUCH (OLYMP) 2 at its new position, with a larger phase angle).

This is not the first "small hop" of LUCH (OLYMP) 2 to the other side of a visited satellite grouplet. In December 2023, it also made a small hop, from 3.2 E to 2.6 E, moving from EUTELSAT 3B to EUTELSAT KONNECT VHTS.

Meanwhile, it is not the first time either that a LUCH (OLYMP-K) satellite is checking out INTELSAT 1002. The latter has been visited by an earlier LUCH (OLYMP) satellite, LUCH (OLYMP) 1 (2014-058A) twice before.

The relocations of LUCH (OLYMP) 2 so far come at intervals of roughly 3 months.

It is still a bit mysterious why exactly these LUCH (OLYMP) satellites are stalking commercial satellites. The roles of their victims are somewhat diverse, although most of the stalking targets in one way or another have to do with data transmissions and TV broadcasts (but there appear to be no relations to recent Russian satellite TV hacks). They could perhaps be mapping contact networks, tapping data streams, analysing frequency hopping patterns, or even analyse weak energy field transmissions within their target satellites. Or they are just there to feed paranoia and provoke counterspace methods.

Sunday, 7 July 2024

The Russian SIGINT satellite LUCH (OLYMP) 2 has arrived at its new destination, next to THOR 7

LUCH (OLYMP) 2 imaged at its new location on July 6. Click image to enlarge

 

In a previous blogpost I signalled that the Russian military SIGINT satellite LUCH (OLYMP) 2 (2023-031A), also known as LUCH-5X, a satellite that stalks other satellites, started another relocation move on July 22, leaving its position near ASTRA 4A at longitude 4.8 E and drifting west at 0.9 degrees per day. 

On July 1, the drift stopped as it arrived at its new target destination at longitude 0.54 W. As expected, it has been placed close to yet another western commercial geosynchronous satellite: the Norwegian satellite THOR 7 (2015-022A).

The image above shows both satellites - plus a couple of other neighbouring ones - as imaged by me from Leiden in the night of July 6/7, when I finally had clear skies again, albeit briefly. The image is a 10-second exposure taken with a ZWO ASI 6200 MM PRO + 1.2/85 mm lens. 

At the moment the image was taken, LUCH (OLYMP) 2 and THOR 7 were some 84 km apart. That distance might diminish further: the Russian satellite is still slowly drifting closer to THOR 7.

This is the sixth relocation of LUCH (OLYMP) 2, and the fifth satellite it visits (see diagram above). I expect that it will stay close to THOR 7 for a few weeks and then move on again, possibly to one of the neighbouring satellites (THOR 5 or 6, or INTELSAT 1002), or to a new location altogether.

I also imaged LUCH (OLYMP) 1 (2014-058A), the predecessor of LUCH (OLYMP) 2 (see image below). It has been parked close to INTELSAT 37E (2017-059A) at longitude 18.1 W since September 2022, following an earlier life of frequent relocations (some 30 relocations between 2014 and 2022):

 

LUCH (OLYMP) 1 near INTELSAT 37E on July 6. Click image to enlarge

More on both LUCH (OLYMP) 1 and 2 and their program backgrounds can be found in this article from 2023 by Bart Hendrickx in The Space Review.

As I wrote in a previous blogpost, what LUCH (OLYMP) 2 and its predecesssor LUCH (OLYMP) 1 are doing so close to commercial satellites is an interesting issue. To name a few possibilities: they might be gathering information to map contact networks; geolocating targets that use the satellites; eavesdropping on data communications; prepare for or actually do jamming or spoofing activities; or checking these satellites for vulnerabilities that might provide a means to disable them, might need come.

Friday, 28 June 2024

LUCH (OLYMP) 2 is on the move again [UPDATED]

Image from June 27, 2024. Click to enlarge

 [ UPDATED on 5 July 2024 ]

The Russian military geosynchronous SIGINT satellite LUCH (OLYMP) 2 (2023-031A) is on the move again. It has left its position at longitude 4.7 E with a manoeuver initiated on 22 June 2024, likely around 11:40 UTC. It is now drifting westwards with a drift rate of approximately 0.9 degrees per day

The change in several orbital elements after mid June 22 is well visible in the TLE data:



It will be interesting to see what LUCH (OLYMP) 2's next stalking victim will be.

LUCH (OLYMP) 2, which was launched on 12 March 2023, is building a history of frequent relocations, like its predecessor LUCH (OLYMP) 1 (2014-048A) did. With each relocation, it is placed close to a commercial satellite. Below shows the position it had between April 1 and June 22 close (daily varying between 20-75 km) to ASTRA 4A at 4.7 E, where it arrived on April 2, 2024 (see this earlier blogpost) until it left there on June 22. 

 


 

So far LUCH (OLYMP) 2 has stalked at least four commercial satellites:

ARRIVED      LEFT         LON      NEXT TO
22-05-2023   25-09-2023   9.0 E    EUTELSAT (KA SAT) 9A/EUTELSAT 9B
04-10-2023   04-12-2023   3.2 E    EUTELSAT 3B
05-12-2023   26-03-2024   2.6 E    EUTELSAT KONNECT VHTS
01-04-2024   22-06-2024   4.7 E    ASTRA 4A

Below, the movements since launch in diagram form, showing the longitude of placement The first two placements at 78 E and 58 E were probably check-out placements.

click diagram to enlarge

What LUCH (OLYMP) 2 (and its predecesssor LUCH (OLYMP) 1) is doing so close to commercial satellites is an interesting issue. To name a few possibilities: it might be gathering information to map contact networks; geolocating targets that use the satellites; eavesdropping on data communications; prepare for or actually do jamming or spoofing activities; or checking these satellites for vulnerabilities that might provide a means to disable them, might need come.

 

UPDATES 5 and 7 July 2024

The westward drift of LUCH (OLYMP) 2 stopped on July 1, at longitude 0.54 W, where it has now stabilized its position. LUCH (OLYM) 2 is now close to the Norwegian commercial geosat THOR 7 (2015-022A). Due to bad weather, I have not been able to image it there yet. I imaged it at its new position on July 6/7, see this new blogpost.

Monday, 15 April 2024

Mentor 10 (USA 353), the NROL-70 payload, likely found near 98 E [UPDATED]

click image to enlarge. Image (c) by @mickeywzx, used with permission

It appears that Mentor 10 (USA 353), the payload of NROL-70, which launched on 9 April 2024 at 16:53 UTC, has been found on orbit by Twitter user @mickeyWZX (Zhuo-Xiao Wang) who is located at Baihuashan Observatory (MPC code P13) in the suburbs of Beijing. 

It is a bright object, reportedly about mag. +7.6, which conforms to the expectation of an ADVANCED ORION, a SIGINT satellite class known as 'Mentor' among independent trackers. These objects are the largest and brightest geosynchronous satellites in the sky with a typical observed brightness near mag +8 (see my 2016 article in The Space Review that discusses one of them as part of a larger story).

When found on April 11, two days after launch, it was located near longitude 97 E.

 A preliminary TLE which the observer posted on Twitter suggests it is drifting westwards in longitude at 0.6 deg/day, indicating it was originally inserted at 98.0 E

[update] a TLE over an arc of several days suggests it is drifting westwards in longitude at ~1.3 degrees/day, indicating it was originally inserted at 100.3 E. [/update]

That is basically in agreement with my pre-launch estimate (100 E), but the orbital inclination of 8 degrees is a bit higher than my estimated 5 degrees. Still, the resemblance to my pre-launch estimate is good.

 

click to enlarge

 

In the map below, my pre-launch estimated insertion orbit is depicted (blue) along with the orbital track of the payload after insertion (yellow), from April 9 22:45 UTC to April 19 12:00 UTC (note the daily analemma caused by the 8 degree orbital inclination). The yellow crosses give positions for various future dates if the current drift of 12.3 deg/day westwards continues:

Click map to enlarge


At this moment, the payload is probably controlled from Pine Gap Joint Defense Facility in Australia. If it continues to drift westwards, RAF Menwith Hill in the UK might at some point take over. 

At the current drift rate, if it continues this way, it should become visible at sufficient sky elevation from my location by late May 2024. 

It will be interesting to see where the drift stops. My guess, based on current hightened interest in what is going on in Ukraine, Gaza and the Red Sea area, is somewhere near 30 E. But who knows: it might go as far as 15 W, based on historic positions for this line of satellites.

A preliminary TLE based on observations by @mickeywzx [updated]:

Mentor 10
1 59453U 24067A   24109.01742676 0.00000000  00000-0  00000+0 0    06
2 59453   7.9821 302.0687 0008030 158.5115 201.5250  0.99896432    03

 

(I thank @mickeywzx for allowing the use of his photography in this post)

Wednesday, 27 March 2024

NROL-70, likely an ADVANCED ORION satellite

NROL-70 launch trajectory. Click map to enlarge

 

On 28 March 2024, if weather cooperates (see update at bottom of post), ULA will launch NROL-70 from SLC-37 at Cape Canaveral, carrying a classified payload for the National Reconnaissance Office (NRO). 

NROL-70 will be the last launch of ULA's iconic Delta IV Heavy rocket. Navigational Warnings for the launch (plotted on the map above) indicate a launch to Geosynchronous orbit. The launch window opens at 17:40 UTC and runs to 22:51 UTC. Back-up dates are March 29 to April 1. 

The classified payload is likely Mentor 10 (Orion 12), a Signals Intelligence (SIGINT) satellite in the ADVANCED ORION class.

The NRO launch patch for NROL-70 features a Snow Leopard:

 

NRO launch patch for NROL-70

 

ADVANCED ORION/MENTOR satellites are very large. At magnitude +8, they are the brightest geosynchronous satellites in the sky. In a 2010 speech a former Director of the NRO, Bruce Carlson, called one of these, the NROL-32 payload (Mentor 5), "the largest satellite in the world". 

The satellites feature a very large parabolic unfoldable mesh antenna, with estimates of the size of this antenna ranging from 20 to 100 (!) meter. An NSA internal newsletter from 2009 that was leaked as part of the Snowden files, contains an artist impression of the satellite which indeed features a large mesh dish antenna:


ADVANCED ORION artist impression from a 2009 leaked NSA newsletter

 

These ADVANCED ORION satellites (also known as 'Mission 7600') are huge listening 'ears' in the sky, monitoring large areas for radio emmissions, notably military COMINT (communications) and FISINT, as outlined in this leaked NSA document.

Here is an image of one of these ADVANCED ORION satellites, Mentor 4, imaged by me in January 2020. Note how much brighter it is, due to its size, than the nearby commercial geosynchronous satellite Thuraya 2 (that it is close to this commercial telecom satellite is no coincidence, see my 2016 article in The Space Review linked below):

 

click image to enlarge


From the Navigational Warnings for the launch and what we know of earlier ADVANCED ORION launches (see my 2016 Space Review paper), NROL-70 will first follow a low altitude (~200 km) coasting orbit. Near the descending node, some 25 minutes after launch, it will then boost into a Geosynchronous Transfer Orbit, which some 6 hours after launch will deliver the payload to a Geosynchronous orbit.

 

NROL-70 launch trajectory. Click map to enlarge

 

It initially will likely be placed near longitude 100 E, over Indonesia and within range of the Pine Gap facility in Australia, where it will undergo checkout. It will then be moved to its operational slot, which is unknown.

Initial control will be from the joint US/Australian Pine Gap facility in Australia. Depending on where its operational position will be, control at some point might be handed over to RAF Menwith Hill in the UK.

More backgrounds on the role of these kind of SIGINT satellites can be found in this 2016 article in The Intercept and in my 2016 article in The Space Review.

Here is the text of the relevant Navigational Warning (the three hazard areas A, B and C have been plotted by me as red boxes in the map above):

 

191855Z MAR 24
NAVAREA IV 333/24(GEN).
NORTH ATLANTIC.
FLORIDA.
1. HAZARDOUS OPERATIONS, ROCKET LAUNCHING
   281740Z TO 282251Z MAR, ALTERNATE
   291737Z TO 292251Z MAR AND 011725Z TO 012251Z
   APR IN AREAS BOUND BY:
   A. 28-34.73N 080-34.39W, 28-37.00N 080-20.00W,
      28-34.00N 079-44.00W, 28-30.00N 079-45.00W,
      28-28.00N 080-20.00W, 28-28.88N 080-32.26W,
      28-30.00N 080-32.80W, 28-33.65N 080-34.05W.
   B. 28-31.00N 073-23.00W, 28-22.00N 070-35.00W,
      27-51.00N 070-38.00W, 27-58.00N 073-22.00W.
   C. 22-05.00N 042-25.00W, 22-29.00N 042-17.00W,
      20-36.00N 036-57.00W, 20-22.00N 037-03.00W.
2. CANCEL THIS MSG 012351Z APR 24. 

 

Below are very approximate orbit estimates for the various phases of the launch. They are valid for launch on 28 March 2024, 17:40 UTC:


NROL-70 COASTING PHASE                        (valid 17:45-18:05 UTC)
1 70000U 24999A   24088.73611111  .00000000  00000-0  00000-0 0    06
2 70000 028.4000 281.1702 0007584 097.3393 339.7290 16.21678257    00

NROL-70 GTO PHASE                             (valid 18:05-23:30 UTC)
1 70001U 24999A   24088.75364583  .00000000  00000-0  00000-0 0    07
2 70001 028.4000 281.0464 7360043 179.7976 360.0000 02.21326367    09

MENTOR 10 initial placement guess              (valid from 23:30 UTC)
1 70002U 24999A   24088.98149645 0.00000000  00000-0  00000+0 0    02
2 70002   5.0000 278.2000 0001186 360.0000   2.0110  1.00277482    05

The last, Geosynchronous orbit assumes initial orbit placement at longitude 100 E at an initial orbital inclination of 5 degrees.

NRO Press kit for NROL-70
ULA Press kit for NROL-70

 

UPDATE 27 March 17:35 UTC:

Currently the weather forecast for 28 March does not look very positive, so launch might be postponed.

Friday, 13 October 2023

Did Russia position a geostationary satellite over Israel last month? No.

screenshot quote Budanov in interview with Ukranian Pravda
 

Based on this interview with Kyrylo Budanov, the Chief of the Intelligence Directorate of the Ukranian military, in the Ukranian Pravda newspaper, a story is going around claiming that Russia relocated a geostationary satellite over Israel in the last week of September, with the suggestion that this was part of an operation to help Iran and the terror organisation Hamas to commit the latter's atrocious assault on Israel.

I was asked by a journalist and a number of people on social media whether I had any evidence that could confirm Budanov's claim. 

In short: this claim cannot be substantiated and makes little sense.

The date mentioned (24 September) for the purported relocation implies that the satellite in question should be LUCH (OLYMP) 2 (2023-031A).  This is the second in the OLYMP-K series of SIGINT satellites operated by the Russian military, and was launched in March of this year.

Below is a plot of the longitudes of all operational Russian geostationary assets (civilian and military) in a wide swat of longitude spanning Africa to west Asia. Only LUCH (OLYMP) 2, indicated by the larger red dots, changes position starting near the mentioned date of September 25/26 (the relocation was completed by October 4), moving from 9.0 E to 3.2 E.

(the other satellite slowly drifting from 7 E to 15E, is the commercial satellite EXPRESS AM-33 which has been drifting for over a year, since august 2022).


click diagram to enlarge

 

Given the date quoted, Budanov's remarks clearly seem to indicate LUCH (OLYMP) 2 as the satellite in question. But it makes no sense, because:

(1) moving from longitude 9 E to 3.2 E, it is not located near Israel, the difference in longitude being almost 30 degrees;

(2) it is moving westwards, away rather than towards the longitude of Israel.

So Budanov's claim is quite a stretch (and I wonder if someone in his staff perhaps simply misinterpreted "3.2 E" as "32 E" and jumped the gun).

Moreover, the repositioning of the satellite has to be seen in the light that this is an OLYMP-K class satellite

These SIGINT satellites serve a similar role as the US satellite PAN (see my 2016 article in The Space Review for more on PAN): they rove from commercial telecom satellite to commercial telecom satellite, to eavesdrop on communications and map which sources are utilizing the satellite. Hence, their targets of interest are other satellites.

This behaviour can be well seen in this plot of longitude over time for LUCH (OLYMP) 2's predecessor, LUCH (OLYMP) 1  (2014-058A, aka 'OLYMP-K'). At least 24 relocations over the past 9 years can be seen (and each time, it was put next to another commercial telecom satellite:

LUCH (OLYMP) 1 behaviour. Click to enlarge

 

The newer sistership,  LUCH (OLYMP) 2 has only recently been launched, on 12 March 2023. In the 8 months since, it has been relocated 3 times (including the relocation now under discussion):

LUCH (OLYMP) 2 behaviour. Click image to enlarge


It is clearly following in the footsteps of its predecessor LUCH (OLYMP) 1, as it too is put close to commercial telecom satellites during these relocations

For example, here it is on September 20 (a few days before its last relocation) imaged by me from Leiden in the Netherlands. At that time the satellite was positioned very close to Eutelsat (KA Sat) 9A - the true distance between the two satellites was about 22 km at the moment of imaging:

 

click to enlarge


 And here it is on October 14, after relocation to 3.2 E, close to Eutelsat 3B:

 

click to enlarge

The targets of  LUCH/OLYMP satellites are other geostationary satellites, on which they eavesdrop. That they frequently relocate, is a normal, well-established pattern.

Combined with the fact that LUCH (OLYMP) 2 is actually not located over Israel at all but almost 30 degrees more West in longitude, there is no credible evidence that the late September relocation had anything to do with the events in Israel on October 7.

Tuesday, 4 October 2022

PAN is moving back westwards again

 

click diagram to enlarge

In September 2021 I wrote a blogpost noting that the enigmatic geosynchronous SIGINT satellite PAN/NEMESIS I (2009-047A) had left 47.7 E and was drifting eastwards. By 30 August 2022 it had drifted as far as 63.1 E.

But somewhere in September 2022, it reversed its drift and started to move Westwards again. Greg Roberts in South Africa recovered it on 30 September 2022 at 55.7 E after he looked for it in vain at more eastward positions.

From tracking data over the period May 2021 - August 2022, PAN was drifting eastwards at a rate of about 0.27 degrees/day. The drift started late February 2021.

It subsequently must have rapidly moved West again, by at least 0.23 degrees/day. It is not clear yet whether the drift continues, or if it is now stable at 55.7 E. Future observations will tell.

At the time of the eastward drift, I was not sure whether the drift was deliberate or the result of an operational "end-of-life". With the halt of the drift and subsequent rapid move westwards this month, it seems to me that the drift was deliberate and the satellite is still operational.

PAN/NEMESIS I was launched in 2009 and is a SIGINT satellite with a very unusual role. As the diagram in top of this post shows, it frequently relocated between late 2009 and late 2013 (which was very unusual), stalking a number of commercial communications satellites and eavesdropping on them. By 2014, this behaviour suddenly stopped, and for a long time it was kept at a stable position near 47.7 E, untill it started to drift in February 2021.

Six years ago I wrote an in-depth article on this enigmatic satellite for The Space Review that you can read here.

Wednesday, 20 April 2022

USA 327 / NROL-85


The video above which I shot yesterday evening (19 April 2022) shows USA 327, the NROL-85 payload, passing over my home in Leiden, slightly over two days after it was launched. The footage was shot with a WATEC 902H2 Supreme Low Light Level CCTV camera with a Canon FD 1.8/50 mm lens fitted.

NROL-85 (see two previous posts about this very recent classified launch here and here) has now been catalogued (with orbital elements witheld) by CSpOC as USA 327, catalogue nr 52259, COSPAR ID 2022-040A. Only one object was catalogued, there was no spoof second 'debris' object entered.

As already mentioned in a recent post, the fact that there is no second object is a big surprise. We expected NROL-85 to deliver two payloads, a pair of INTRUDER (also known as NOSS, which stands for Naval Ocean Surveillance System), SIGINT satellites used for geolocating shipping on the High Seas by means of time difference of arrival of their radar/radio emmisions.

Before 2001, NOSS systems existed of three co-orbiting satellites forming a thight triangular formation. From 2001 onwards (with the launch of NOSS 3-1, the first of the Block 3 NOSS-es) , this changed into two co-orbitting satellites.

(the video below, from 30 August 2018, shows a typical NOSS pair, in this case both briefly flaring due to a favourable sun-satellite-observer angle on some reflecting part of the satellites. While operational, NOSS pairs always move this close together. The NOSS pair in question is  NOSS 3-6, the same NOSS pair into which orbital plane the new USA 327 satellite was launched).


And now, we have only one, not two, satellite launched in a NOSS-like orbit. Analysts are scratching their heads over this.

Given the strong similarity in orbit, and the fact that it was launched into the orbital plane of an existing 10-year-old NOSS pair (see previous post), NOSS 3-6 (2012-048A & P), there is clearly some conceptual link of the new satellite to the NOSS program

But in what way exactly? There are a couple of options:

(1) This is a new generation of NOSS/INTRUDER, (i.e. NOSS block 4-1), that needs only one satellite;

(2) This is something else, something new, but related to NOSS/INTRUDER;

(3) This was meant to be NOSS 3-9, a regular NOSS pair, but something went wrong and the second satellite was not deployed;

(4) There is a second satellite but it is small (cubesat) and not yet detected;

(5) The second satellite still has to detach from the first

 

So let us briefly comment on these various options:

Option (1) apparently, is feasible, according to some. Apparently it is possible to do TDA using just one satellite

With regard to option (2), the most interesting one, one could think of for example an optical or radar counterpart to the existing NOSS 3-6 SIGINT pair: one that images the ships geolocated by NOSS 3-6. This makes sense (and it also makes sense that the new satellite orbits half an orbit apart from the NOSS pair).

While we cannot exclude option (3), I think it is not the most likely option. The same goes for option (5): with previous NOSS launches, two objects were detected right after launch. I have no opinion on option (4).

If we look at the current orbit of USA 327 and the orbit of the NOSS 3-6 pair, we note that: 

(a) they move in almost the same orbital plane; 

(b) they currently are almost exactly half an orbital revolution apart (see illustration below); 

(c) because of the latter difference in Mean Anomaly, their ground tracks are not the same but have some distance between them.

 

click map to enlarge

Observation (c) does not entirely make sense to me. Wouldn't you want your imaging satellite to follow the same ground track as the geolocating SIGINT satellites? On the other hand: true: the footprints are large enough to cover a large overlap in ocean space from both groundtracks. But still....

Another aspect of this that does not completely make sense to me is that, if USA 327 is a technology demonstrator for a new complementary IMINT mode to the NOSS SIGINT system, then why pick a 10-year-old, nearly retired pair of NOSS satellites to test it with? Why not pick a fresher pair, so you can happily experiment away for the time to come?

But maybe, those fresher pairs of NOSS satellites are deemed more suited for when, after this technology demonstration, the truely operational system is deployed. But then again, why bother with that, just replace the technology demonstrator with the operational version and deorbit the technology demonstrator.

Questions, so many questions, and my still post-COVID impaired brain cannot make much sense of it yet...

It will be interesting to see what USA 327 does (in terms of orbital manoeuvres etcetera) the coming months.

Meanwhile, Radio observer Scott Tilley in Canada has detected the first S-band radio signals from USA 327. He reports "huge fades in signal", which is odd. From Cees Bassa I understand that the frequency in question, 2277.5 MHz, is a know frequency used during the checkout-phase of NOSS 3-x pairs.

Tuesday, 12 April 2022

NROL-85: probably NOSS 3-9, a new pair of INTRUDER Naval SIGINT satellites

 

image: Wikipedia

 EDIT (15 & 16 Apr):  the launch of NROL-85 has been postponed by at least two days, 'due to technical difficulties'

EDIT (17 Apr): new launch date is 17 April 2022 13:13 UT

On 15 April 2022, at 13:41 UT (or later) according to a tweet by the NRO, SpaceX will launch NROL-85 for the National Reconnaissance Office (NRO). The launch will be from SLC-4E at Vandenberg SFB. [edit 16 Apr: launch was postponed to 17 April 13:13 UT]

NROL-85 is almost certainly a pair of NOSS satellites. NOSS stands for Naval Ocean Surveillance System; they are also known under the code name INTRUDER. If correct, the duo would become NOSS 3-9 (the 9th mission of block III). It will probably enter with the designation USA 327 in the CSpOC catalogue (with orbital elements witheld).

NOSS satellites are SIGINT satellites operated by the US Navy. They geolocate shipping on the high seas, by detecting their radio/radar emissions. They always operate in close pairs. The secondary object is usually listed (with orbital elements witheld) as "debris" in the CSpOC catalogue, but this is a ruse that fools nobody: it is a payload too that manoeuvres and keeps a careful constant close distance to the primary satellite.

Information from the launch contract tender for this launch reveals that the mission aims for a semi-major axis of  7500.5 km, an orbital eccentricity of 0.0131, an orbital inclination of 63.535 degrees and an argument of perigee of 190 degrees (i.e. perigee almost on the equator). The listed semi-major axis and eccentricity translate to a 1024 x 1221 km orbit

The combination of the 63.5 degree orbital inclination and 1024 x 1221 km orbit strongly points to a NOSS/INTRUDER mission. These typically have an orbital inclination of 63.4 degrees and a semi-major axis of 7485 km, values close to those quoted for NROL-85. If launch is indeed at 13:13 UT on April 17, the resulting orbital plane will be very similar to that of the existing NOSS 3-6 duo (2012-048A and 2012-048P) which was launched in 2012, as can be seen in the figure below. That also lines up with a new NOSS-launch: NOSS-pairs are typically replaced after 10 years on-orbit.

The shift in launch time with date due to the two launch postponements agree with the estimated orbital altitude and orbital plane and matches the nodal precession of a typical NOSS orbital plane.


click image to enlarge

 

The Navigational Warnings for this launch (NAVAREA IV 336/22 NAVAREA XII 228/22 and HYDROPAC 987/22) define a launch direction towards the south-southeast, and agree with the 63.5 degree orbital inclination of the launch contract tender. 


[EDIT: The first NavWarning has been corrected: I initially copied the wrong NavWarning for this post.....]

100706Z APR 22
NAVAREA XII 228/22(18,21).
EASTERN NORTH PACIFIC.
CALIFORNIA.
1. HAZARDOUS OPERATIONS 1150Z TO 1514Z DAILY
   15 AND 16 APR IN AREAS BOUND BY:
   A. 34-41N 120-38W, 34-39N 120-40W,
      34-28N 120-38W, 34-04N 120-17W,
      34-04N 120-05W, 34-19N 120-14W,
      34-39N 120-19W.
   B. 32-03N 118-53W, 32-01N 118-49W,
      30-51N 117-56W, 30-21N 117-39W,
      30-08N 117-47W, 30-11N 118-01W,
      30-32N 118-18W, 31-54N 118-53W.
2. CANCEL THIS MSG 161614Z APR 22.


100644Z APR 22
HYDROPAC 987/22(22,83).
EASTERN SOUTH PACIFIC.
DNC 06.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
   1425Z TO 1649Z DAILY 15 AND 16 APR
   IN AREA BOUND BY
   20-12S 123-30W, 19-00S 119-00W,
   33-48S 109-30W, 36-00S 114-12W.
2. CANCEL THIS MSG 161749Z APR 22.

 

I have mapped the hazard areas from the Navigational Warnings and the resulting launch trajectory in the map below (the times listed along the trajectory are in UT and for the updated launch date with launch at 13:13 UT (17 April):
 

click map to enlarge


Based on the parameters from the launch contract tender, this is my orbital estimate, valid for launch at 13:41 UT on April 15 updated for launch at 17 April 13:13 UT:


NROL-85                         for launch on 17 Apr 2022 13:13:00 UT
1 70002U 22999A   22107.55069445 0.00000000  00000-0  00000+0 0    02
2 70002  63.5350 124.8521 0131000 190.0000 291.3542 13.36458926    04

 

There is an uncertainty of several minutes in pass time in this elset, progressively so after more than one revolution, and some cross-track error is possible. But the elset should be good enough for a plane scan, taking a wide time window around a predicted pass. Be carefull not to misidentify the NOSS 3-6 duo as NROL-85. An elset for NOSS 3-6 can be found here.

If the eventual launch time turns out to be later than 13:13 UT, the elset above can easily be adjusted to match the new launch time using my "TLE from Proxy" software downloadable here.

The Northern hemisphere will see good, fully illuminated evening passes on the day of launch and the days after it, so prospects are good for a quick on-orbit detection after launch.

The Falcon 9 upper stage deorbit is over the southern Pacific, just after the end of the first revolution. The deorbit-burn might be visible from south and/or central Asia.

The launch patch (see top of this post) features a cat, with a tiger as its reflection. The NRO itself explains some of the symbolism in the patch in this way:

"In the NROL-85 patch, the 3 stars represent guidance, protection, and allegiance. The cat represents loyalty and devotion shared among our nation and partners. The tiger in the cat’s reflection demonstrates that while space can be challenging, a determined attitude helps NRO succeed in going"


Given that this is going to be NOSS 3-9, the 9th instance of the Block III NOSS generation, I wonder if the cat was inspired by the proverbial 'nine lives' of cats.

It is possible that a number of other small satellites will be included in this launch as a rideshare.

The NRO press kit for NROL-85 is downloadable here.

FOLLOW-UP POST HERE reporting the first observations of NROL-85 from the evening of April 17. NROL-85 might not be an INTRUDER/NOSS after all!

A SECOND FOLLOW-UP POST HERE, going a bit deeper into various speculations about what the NROL-85 payload might be.


[a small update to this post was made 13 April 2022 09:00 UT, adding a bit more background information]

[an error where I had initially copied the wrong text of a NavWarning into this post was corrected at 13 Apr 20:30 UT - many thanks to the anonymous sharp-eyed reader who noted it!] 

[updated April 15 & 16 to reflect launch postponements] 

[updated 17 Apr 8:45 UT with updated launch trajectory map and orbital plane diagram]

Thursday, 11 November 2021

PAN/NEMESIS 1 is still drifting

 

click image to enlarge

In a blog post in September, I wrote that after almost eight years of being steady at longitude 47.7 E, the classified  SIGINT satellite PAN/NEMESIS 1 (2009-047A) had started to slowly drift eastwards, with the drift starting in February 2021.

Observations on the evening of November 8 show that it is still drifting. Currently it is near longitude 54.8 E, close to Yamal 402 and the grouplet GSAT 8, GSAT16 and GSAT 29, as is visible in the image above.

As it is drifting eastwards, it is getting lower in my sky: currently it is at 14.7 degrees elevation above my northeastern horizon.

The history of PAN's relocations so far (for backgrouds on PAN, its probable role and its frequent relocations during the first five years of its life, see my 2016 article in The Space Review):

click diagram to enlarge

Tuesday, 14 September 2021

PAN (NEMESIS 1) is on the move again

Pan on August 8/9, 2021, imaged from Leiden. Click image to enlarge

Five years ago, in 2016, I wrote a long article in The Space Review titled "A NEMESIS in the sky: PAN, Mentor 4 and close encounters of the SIGINT kind". The primary subjects of that article were two SIGINT satellites: PAN (Nemesis 1) and Mentor 4.

In the article, I discussed what we had observed and deduced about PAN as amateur trackers, to what had been recently revealed about PAN by leaked documents from the Snowden files.

In the article I documented the frequent movements of PAN (2009-047A): for four years between its launch in September 2009 and mid 2013, PAN, very unusual for a geosynchronous satellite, was roving from location to location, each time being put close to a satellite for commercial satellite telephony.
For information on the "why" of that, and the larger context of it (a new kind of SIGINT information gathering), I refer to the earlier mentioned Space Review paper which goes into details.

Mid-2013, four years after launch, the frequent relocations stopped. For 8 years, the position of PAN remained stable in longitude near 47o.7 E. It's roving days, snooping around and sniffing other satellites, were over. Until this year.  

Somewhere between 6 February and 7 May 2021, PAN started to move again, eastwards in longitude. Observed longitudes over the period May-August 2021 suggest a drift eastwards at about 0.025 deg/day

Assuming a stable drift, the move appears to have been initiated within a few days of 11 February, 2021.The last observation still showing PAN at 47.7 E was on 6 February 2021 (as it happens, our network did not observe it again untill early May 2021 when it had already moved eastwards by two degrees).

The diagram below (an updated version of one that appeared in my 2016 Space Review article) shows the positions in longitude that PAN has been taking up since its launch in 2006. Note the frequent relocations over the period 2009-2013, then the long stabilization at 47.7E, and the start of a new drift episode in 2021:

click diagram to enlarge


The question now is, what this drift since February means:

(1) Has it deliberately been brought into a drift state to move it to an eventual new position? 

(2) Has it reached end-of-life and been manoeuvered into a graveyard orbit?

A 'graveyard orbit' is usually an orbit that is located at least 235 km higher than a geosynchronous orbit. That does not appear to be the case here: if anything, the orbit seems to be a few km lower than it previously was. So it appears to be option (1).

It will be interesting to see whether PAN will stabilize its longitude at some point or not, and where that will be. Unfortunately, as it is drifting eastwards it is getting lower in my sky (currently, it is some 16 degrees above my local horizon), and there do not appear to be many other amateurs covering it currently.

It would be interesting to see whether radio observers can detect radio signals from PAN, which shortly after launch was emitting at frequencies similar to that of the "UFO" (UHF Follow On) constellation.


PAN on 2/3 June, 2021, imaged from Schiermonnikoog Island. Click to enlarge

Tuesday, 6 April 2021

LUCH (Olymp-K), an eavesdropping SIGINT snooping around commercial comsats

 

click image to enlarge

Back in 2016, I published an article in The Space Review (A NEMESIS in the sky: PAN, Mentor 4 and Close Encounters of the SIGINT kind) about the mysterious US classified satellite PAN, and Mentor 4, another classified US satellite.

Both are SIGINT satellites launched in 2009, that are positioned close to commercial telephony communications satellites in GEO in order to eavesdrop on their communications. While Mentor 4 (an ADVANCED ORION) dedicatedly covers Thuraya 2, PAN (NEMESIS 1) moved from satellite to satellite in a 'roving' role every few months during the first 5 years of its operational existence. Its sister ship CLIO (NEMESIS 2) launched in 2014 has done pretty much the same.

But (of course) the USA is not the only country playing this game. In the same year that CLIO (NEMESIS 2) was launched, the Russian Federation launched LUCH (2014-048A), aka OLYMP-K or OLIMP-K. In 2015, in an essay in The Space Review, Brian Weeden pointed out that LUCH was roving from satellite to satellite too, possibly eavesdropping on their communications. This created headlines at the time. By all means, LUCH/OLYMP-K is the Russian equivalent of PAN and CLIO.

The diagram below shows the frequent repositionings of LUCH/OLYMP-K over the years ( a table with major repositionings is at the end of this post):


click diagram to enlarge

LUCH has recently (in the second week of February, 2021) been relocating from longitude 3 W to 8 W and is now positioned near EUTELSAT 8 WEST B (2015-039B). Before the relocation, it had been close to ABS-3A (2015-010A) for several weeks. 

I shot this image below on March 29th, when LUCH and EUTELSAT 8 WEST B were about 90 km apart:

 

click image to enlarge


The image was made with a CANON EOS 80D and Samyang 2.0/135 mm lens (10 seconds at 1000 ISO) and was a by-product of targetting MEV-2 and several classified objects in this stretch of sky.

The table below gives longitudinal positions for LUCH/OLYMP-K. The table focusses on major relocations.

Dates refer to he moments the longitude appears to get stabilized, and have generally been preceeded by a period of drift. Also indicated is what satellite was closest to LUCH/OLYMP-K at the start of each stable period. Note that in several cases, multiple satellites were close by and possibly targetted as well.


TABLE: positions of LUCH/OLYMP-K since late 2014 

DATE          LON      NEAR

17-02-2021    08.1 W   EUTELSAT 8 West B       2015-039B
06-11-2020    03.1 W   ABS-3A                  2015-010A
28-09-2020    04.9 W   Eutelsat 5W B           2019-067A
11-05-2020    01.1 W   Intelsat 10-02          2014-058A
28-03-2020    21.5 E   EUTELSAT 21B            2012-062B
28-11-2019    70.6 E   EUTELSAT 70B            2012-069A
22-10-2019    68.4 E   Intelsat 20             2012-043A
25-08-2019    65.9 E   Intelsat 17             2010-065B
01-07-2019    64.0 E   Intelsat 906            2002-041A
21-02-2019    60.0 E   Intelsat 33E            2016-053B
28-10-2018    57.0 E   NSS 12                  2009-058A
03-07-2018    49.9 E   Turksat 4B              2015-060A
07-06-2018    48.0 E   Eutelsat 28B            2008-065B
27-04-2018    47.5 E   Yahsat 1B               2012-016A
17-01-2018    41.9 E   Turksat 4A              2014-007A
25-10-2017    38.1 E   Paksat 1R               2011-042A
18-08-2017    32.7 E   Intelsat New Dawn       2011-016A
14-09-2016    09.9 E   Eutelsat 10A            2009-016A
11-01-2016    01.1 W   Intelsat 10-02          2004-022A
05-10-2015    24.3 W   Intelsat 905            2002-027A
26-06-2015    18.1 W   Intelsat 901            2001-024A
22-02-2015    96.4 E   Express AM-33           2008-003A


Thursday, 23 March 2017

NOSS 3-8 (NROL-79) components now close to operational separation

In a recent blog post I documented the intricate manoeuvering of the two NROL-79 payloads (NOSS 3-8) over the past three weeks. They were manoeuvering to circularize and synchronize their orbits and manoeuvre to a desired mutual distance.

click image to enlarge


Much of this manoeuvering is now done, and the two spacecraft are now flying in formation at a mutual distance of ~50.5 km. They now look like a typical NOSS pair, as can be seen in the image above shot in the evening of March 21 (the bright star is Procyon).

Below is an updated diagram, showing the evolution of the separation between the two spacraft over time:

click diagram to enlarge

After an initial rapid post-launch separation with a drift of ~31-32 km/day, reaching a maximum separation of ~202 km on day 6 after launch, the separation distance started to decrease post day 6, and is now, by day 20-21 after launch, clearly flattening out to a stable separation distance of about 50 km.

The Mean Motion/orbital period of the two spacecraft are now very similar too, as is their orbital inclination: all signs that they are now close to the desired configuration. The two orbital planes are currently about 0.2 degree separated in RAAN.

click diagram to enlarge
click diagram to enlarge
click diagram to enlarge

While they are now at their operational distance (which looks to be ~50 km in this case) and close to operational configuration, this does not mean that NOSS 3-8 is now fully operational. Over the coming weeks, they will probably undergo extensive check-out tests. I also expect them to continue to make small manoeuvres for a while (but while maintaining a more or less stable mutual distance at ~50 km).

Several amateur satellite trackers contributed data to this analysis, including Leo Barhorst, Cees Bassa, Russell Eberst, Alain Figer, Paul Camilleri, Dave Waterman, Alberto Rango, Brad Young and me.