Showing posts with label DSP. Show all posts
Showing posts with label DSP. Show all posts

Tuesday, 19 December 2017

[UPDATED] Where to hide your nuclear missile submarine? (but be quick)

(Updated 20 Dec 2017 23:25 UT with a new plot that includes DSP)

Say, you are the leader of a nefarious country that is in posession of submarines equiped with long range nuclear missiles. You want to launch a stealth missile attack codenamed "Operation Orange Squeeze" on a northern hemisphere Super Power.

Where would you direct your submarine, and where would you best fire you missiles, from the perspective of an as-late-as-possible space-based detection of your missile launches?

The answer came to me today when, after a question by someone (in the context of a war crime investigation), I looked into the current global coverage of the Space Based Infra Red System (SBIRS), the US system of Early Warning satellites that looks for missile launches:

click map to enlarge

The red areas in the map above have an almost continuous coverage by SBIRS satellites (and often by multiple SBIRS satellites at the same time). The dark blue and black areas in the map by contrast have only a few minutes of SBIRS coverage each day, or even none at all.

As you can see, there is a clear gap in coverage in the southeastern Pacific, with lowest coverage in the area near the Galapagos islands. That is where I would park my nuclear missile submarine.

You might have to be quick to pull off your nefarious plan though. A new SBIRS satellite, the fourth satellite in the geostationary component, will launch in January. It wouldn't surprise me if it stops the gap, once operational.

Of course, this map is in fact somewhat deceptive anyway. It only shows the coverage by SBIRS. But there is also the legacy early warning satellite system called DSP (Defense Support System), which still has active satellites, and which is not taken into account here [UPDATE: but see the plot at the end of this post!]. It is less sensitive than SBIRS, but likely will detect your ICBM SLBM launch.

Back to SBIRS. SBIRS is made up of two components, each currently consisting of three satellites (so six in total): three geosynchronous SBIRS-GEO satellites at geostationary altitude, and three SBIRS-HEO satellites (TRUMPET-FO SIGINT satellites with a piggy-back SBIRS package) in 64-degree inclined Highly Elliptical Orbits with two revolutions a day.

click map to enlarge

The map above shows the coverage of the three geosynchronous SBIRS satellites (a fourth will be launched in January). Eurasia, Africa and the western Pacific Ocean has a continuous coverage by these satellites, with central Asia, Pakistan and India (the latter two known nuclear powers) particularly well covered.

The SBIRS-HEO coverage is more variable and depends on the date and time of day, but the system is designed such that at least one of the HEO satellites will have much of the Northern hemisphere in view at any time. Here are a few examples, for various times of the day: note how coverage of the Northern hemisphere is near-continuous (the HEO component also particularly covers the Arctic region well, which is at the edge of the GEO component's coverage).




click maps to enlarge
A SBIRS satellite typically has two modes: there is the scanning mode, which scans the whole visible hemisphere of the earth (as seen from the satellite) for infra-red heat signatures in less than 10 seconds. And there is the staring mode, a more sensitive sensor which can be used to observe a specific region or just detected infra-red event.

In the case of a missile launch, the sensors pick up the heat signal of the missile engine. Because of the large degree of worldwide coverage which the system now provides, an undetected stealth launch of a nuclear missile has become almost impossible.

SBIRS is probably an important source of  Early Warning capacity and information on the recent North Korean missile tests.


UPDATE 20 Dec 2017  23:25 UT:

I now also included the four DSP satellites that are still operational according to the database of the Union of Concerned Scientists. That leads to the following map:

click map to enlarge
As you can see, the gap has become smaller, but a gap is still there. Red October might be lurking in front of the South American west coast.

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.

Thursday, 13 March 2014

Satellites and Malaysian Airlines flight MH370

Reconnaissance satellites - Chinese and US - are suddenly all over the news, in connection to the mysterious disappearance of Malaysian Airlines flight MH370 on 2014 March 7 (UT: local March 8th).

There is a crowd-sourcing initiative to look for aircraft debris in commercial satellite imagery; the Chinese thought one of their reconnaissance satellites had photographed such debris on March 9 (but it turned out to be unrelated); and US authorities said there were no signs of an explosion in data from US infrared Early Warning satellites.

Let us look at the latter two cases. What satellites were used to look for an explosion and for debris?

SBIRS: looking for a mid-air explosion

First, the reported non-observation of a mid-air explosion by US military infra-red Early Warning satellites. Two such systems exist: the older DSP (Defense Support Program) and the newer SBIRS (Space-Based Infrared System).

Both US systems are dedicated to detect ICBM launches and have a semi-global coverage. They use infrared telescope equiped satellites to look for the infrared signatures of rocket launches. They also detect other transient infrared events such as meteoric fireballs, re-entering spacecraft, surface detonations and, it is claimed, exploding aircraft.

According to the news reports, the SBIRS network was used to look for any traces of a mid-air explosion of flight MH370. Defense specialists quoted in the news article claim that the SBIRS system is capable to detect such mid-air aircraft explosions.

click image to enlarge

SBIRS currently consists of four satellites (see image above): two satellites in Geostationary orbit (SBIRS Geo 1 and SBIRS Geo 2, 2011-019A and 2013-011A), and two satellites in a Highly Elliptical Orbit (USA 184 and USA 200, 2006-027A and 2008-010A) with a SBIRS package piggybacked on to them.

Of these, two satellites had a view of the area where flight MH370 disappeared at that moment it disappeared: the geostationary SBIRS Geo 1 and the SBIRS HEO USA 200:


click images to enlarge

It is less likely that the older DSP system was used. It probably does not have enough sensitivity, and the spokespersons in the news articles explicitly talk about the newer SBIRS. Two DSP satellites, DSP F21 and DSP F22 (both in a geostationary orbit) would have had a view of the relevant area:


click image to enlarge


Gaofen 1: Chinese satellites looking for debris

On March 12 a Chinese government website released military reconnaissance satellite images of possible aircraft debris floating near 105.63 E, 6.7 N. The images were reportedly taken on March 9 near 11 am (presumably Beijing time). They later turned out to be unrelated to the missing aircraft (or rather: they have not been found by searching ships).

image: China Resources Satellite Application Center

China orbits several optical reconnaissance satellites, in the Yaogan and Gaofen series. According to analyst Brian Weeden, the images were likely taken by Gaofen 1 (2013-018A), as this satellite reportedly has enough resolution.

The listed time of "March 9, 11 am" corresponds to 9 March 3 UT. Gaofen 1 made a pass over the area at 3:40 UT, almost right overhead.


click images to enlarge


The only other two Chinese imaging satellites passing near the area around that time are Yaogan 12 (2011-066B) and Yaogan 19 (2013-065A) who passed near 2:45 and 2:50 UT, but more to the East (but with the target area nevertheless in their visibility footprint):

click image to enlarge


Note added 18/03/2014: there is a follow-up post here about the Inmarsat 3-F1 detection of ACARS ping-backs from the aircraft, and the potential use of SIGINT satellites.

Sunday, 24 June 2012

30 (mostly) geostationary objects in one image


Click image to enlarge

The image above was made by me just after midnight of June 18-19, 2012. It is a single image taken with my new Canon EOS 60D and a SamYang 1.4/85mm lens (800 ISO, 10s exposure). It was shot from the center of Leiden town.

The image shows a 11 x 14 degrees wide field low in the south-southeastern sky, between 20 and 30 degrees elevation above the horizon. Diagonally over the image runs a part of the geostationary belt, at declination -7.4 deg for my location.

In this single image, as much as 30 mostly geostationary satellites are visible: 23 commercial geostationary satellites, 1 classified military geostationary satellite (Milstar 5, 2002-001A), and 6 rocket boosters.

I did a poor job with the focus of this image, resulting in a slight unsharpness (especially near the edges of the image). Yet, the number of  objects nevertheless visible in this small piece of low southern sky is amazing!

This is just one of several images I took that night. Apart from Milstar 5, a number of other classified (military) geostationary satellites were imaged and astrometry on them obtained.



PAN in it's new position at 37.9 E

One of these objects is PAN (2009-047A), an enigmatic satellite I have written about before. Here is an image from June 18-19:


click image to enlarge

One of the curious aspects of this strange classified geostationary satellite operated by an undisclosed agency (see Dwayne Day's article in The Space Review), is that it is very frequently repositioned. It recently did so again (see my imagery of May 16, when it was still on the move). It has now stopped drifting and taken up position at 37.9 deg E (a position it has occupied before) not far from Paksat 1R, as can be seen in the image above. A stray Atlas Centaur rocket booster passed the area as well when the image was taken.


Vortex 4 and Mercury 2

Other classified objects imaged include  the older geostationary satellites Vortex 4 (1984-009A) and Mercury 2 (96-026A), the latter of which currently also is on the move (it is probably being sent to a disposal orbit after reaching the end of its operational mission):


click image to enlarge

Vortex 4  (launched on 31 January 1984) and Mercury 2 (USA 118, launched on 24 April 1996) both are SIGINT (eaves-dropping) satellites, with the Mercury being a further advanced version of the Vortex.

In addition, a newer SIGINT satellite was imaged as well,  Mentor 4 (2009-001A, one that frequently features in this observational blog, as it is bright and easy to observe), and the object designated by our amateur network as  UNK 060616 (probably an old r/b).


Prowler, AEHF 1 and DSP F15 imaged from Winer observatory, USA

While the above imaging was all done from my home in the Netherlands, I also imaged a few objects 'remotely' using the UoI Rigel (MPC 857) 37-cm Cassegrain telescope at Winer Observatory, Sonoita, Arizona, USA.

The enigmatic Prowler (1990-097E), a clandestine launch from Space Shuttle mission STS-38 which has featured on this blog more often (read the intriguing story of Prowler here; plenty of suspense!) was imaged on June 19 and 22. On June 19 I also imaged the military communications satellite AEHF 1 (2010-039A), and on June 22 the old DSP Infra-red early-warning satellite DSP F15 (1990-095A). Images of these objects below:

click images to enlarge




Comet 185P/Petriew

In addition to all these satellites, two  Solar System Minor Bodies were imaged: 2012 LZ1 and 185P/Petriew.

I posted imagery of the June 15 fly-by of Near Earth Asteroid (NEA) 2012 LZ1 here before in my previous post, and obtained more astrometry on this object on subsequent nights. In addition, I obtained some imagery on the faint periodic comet 185P/ Petriew on June 22. Below is a stack of 5 images of 45s exposure each:

click image to enlarge



Not a pretty picture, but the comet was near magnitude +17 to +18! My astrometry has been included in MPEC 2012-M33 (22 June).


New camera: a Canon EOS 60D

I had completely forgotten to mention this: during the second half of May, my EOS 450D camera broke down. During a macro-session on Dragonflies, the shutter broke. Much to my regret.

I had the choice between having the shutter repaired (expensive), or buying a new camera. I choose the latter option, as the new generation of EOS cameras performs notably better than the 450D, especially in performance at high ISO (less noise). So I decided to upgrade.

The choice I made was for the Canon EOS 60D, an 18 MP DSLR with Digic IV processor. So far (and having mostly used it for "normal" photography for now) I very much like it!

Before I can use it on satellites in Low Earth Orbit, I'll first have to complete a calibration program with the camera. This calibration entails the delay between the moment you press the shutter button and the exposure is actually taken; and the real duration of exposures (a "10 second" exposure is not exactly 10.00 seconds). I have some preliminary calibration results by now, but it will take some time before I have final results and can start to use the camera regularly on satellites. For geostationary satellites (where the timing accuracy isn't that much of a factor; rather the astrometry is) the preliminary results I have mean I can already use it (as has been done, see this post).

Monday, 26 September 2011

Could the reentry of UARS have been monitored from Space?

One of the open questions regarding the inability to pinpoint the exact location and time of the UARS reentry, is whether the US military might have space-based detections from their infra-red early warning satellites.

The US military operates two constellations of such satellites, whose purpose is to detect and provide early warning for enemy ICBM launches using infra-red detection sensors. The older constellation is the DSP (Defense Support Program) series of satellites in geostationary orbit. There is also the newer SBIRS (Space-Based Infrared System) constellation, consisting of one geostationary satellite (SBIRS Geo-1) and two SBIRS sensors piggybacked on HEO satellites (USA 184 and USA 200).

We know that the DSP satellites have, in the past, frequently observed meteoric fireballs. It is therefore widely believed (and indeed likely) that the system should have been able to detect the UARS reentry fireballs as well. The problem is that post-9/11 the DoD has stopped declassifying meteor detections (which were previously shared with meteor scientists). Which makes you wonder whether, if they did detect the UARS reentry fireball, they would be forthcoming with that information. Probably not.

Would the UARS reentry have been visible from one of the DSP or SBIRS satellites? Would they cover the relevant areas? Yes they would.

Below map shows the location (for 4:16 UTC [edit 28 Sep: this was written before the reentry time was revised to 4:00 UTC, see here]) of UARS plus it's track, and the locations of the relevant satellites.

click map to enlarge

Yellow dots are the block 5 DSP satellites, white dots the SBIRS satellites. The green circle outlines show the coverage area of DSP F16, DSP F20, and SBIRS Geo-1.

The DSP's and SBIRS GEO-1 are geostationary and hence always above the geographic spot depicted in the map (with some minor latitudinal variation): for the HEO SBIRS platforms USA 184 and USA 200 the position plotted is for 4:16 UTC.At that time USA 184 was near apogee and basically almost in the same position (in geographic subsatellite point terms) for an hour on each side of 4:16 UTC. USA 200 was moving towards perigee, but would have UARS in view during the whole Africa pass of the latter.

DSP F16, DSP F20, SBIRS GEO-1 over the eastern Pacific as well as the SBIRS platform USA 184 over Siberia would cover the approach track over the Pacific and nominal center of the reentry window of UARS. Basically, they cover UARS on it's final track from New Zealand to over Canada.

Beyond Canada (would UARS have survived well beyond 4:16 UTC), DSP F17 over Brasil and the SBIRS platform USA 200 moving over Africa would have taken over, joined by DSP F18 plus DSP F21 and DSP F22 (all over Africa or the  Indian Ocean) once over Africa.

I also checked whether the experimental satellites in the STSS (Space Tracking and Surveillance System) series would have been able to capture it: turns out they would not have, as these satellites (in low earth orbits) were not near the relevant part of the UARS track at that time.

In conclusion: there is plenty of possibilities for the US military to have detected the UARS reentry from space, using their space-based assets (DSP and SBIRS) in GEO and HEO. Even if groundbased tracking facilities were sparse over UARS' final track, the space-based sensors should have been able to observe and pinpoint the reentry.

Yet, I suspect that if these observations exist (allowing the DoD a clear indication as to where UARS debris might have showered down), this information will not be released to the public.

(text slightly editted 27 Sep to clarify USA 200 movement)