Showing posts with label Iran. Show all posts
Showing posts with label Iran. Show all posts

Saturday, 13 April 2024

Russian ICBM test launch (Topol?) from Kapustin Yar seen from the Middle East

click to enlarge

On 12 April 2024 near 16:00 UTC, the Russian Armed Forces test-fired an unarmed ICBM from Kapustin Yar, targetting the test range at Sary Shagan at a distance of some 2000 km. The missile was likely a TOPOL-M.

In the image above, I have modelled the likely trajectory, assuming apogee at 1000 km altitude as in previous tests. Below is Russian MoD footage of the launch:

 


The missile launch was widely seen as a bright comet-like object in the sky, in Russia as well as in the Middle East, with reports from as far south as a.o. Iran and Iraq. As many there where in anxiety about an expected Iranian retaliation attack on Israel, it created  a bit of a stir.



 

In the aftermath, there were some people that expressed doubt whether a Russian ICBM test would be visible from the Middle East. So I reconstructed the area of visibility to show that it is in fact visible. 

In the map below, I have drawn isocircles around the estimated point of cut-off of the missile's third stage. That stage cut-off happened after 3 minutes of flight at an altitude of about 570 km (there is some leeway in both figures possible, but in general the figure below will give you a good indication of the area of visibility).

click map to enlarge

 

The isocircles give you the altitude in the local sky as seen from a region encompassing southern Russia and the Middle East. 

As can be seen, the area of visibility is large, and horizontally extends about 2600 km from the geographic location of stage engine cut-off, to as far as southern Iran. 

Bar the first few tens of kilometers, the trajectory was fully sun-illuminated, and as a result the exhaust clouds of the missile were also sun-illuminated, making them  shine brightly in the sky.

That exhaust clouds from the upper stages of missile launches can be seen over a avery large area isn't something new. Russian ICBM tests from Plesetsk have multiple times resulted in sightings of bright "spirals" in the Arctic sky (e.g. here). Chinese tests have also been observed, e.g. this example that was observed from South Korea in 2019, which I further analysed here. Meanwhile, the post-boost vehicles of ICBM's/SLBM's sometimes also cause visible phenomena in the sky: see my analysis of one such sighting from La Palma in 2013 related to a US Trident SLBM test for example.

Wednesday, 6 May 2020

Imaging the new Iranian satellite NOUR 1 (2020-024A) [UPDATED triple]

click to enlarge

On 22 April 2020 around 4:00 UT, Iran's Islamic Revolutionary Guard surprised the world by launching a military satellite. The satellite is named NOOR 1. The name 'NOOR' means 'Light' in Pharsi.

The object is designated NOUR 01 by CSpOC, with catalogue number 45529  and Cospar designation 2020-024A.

NOUR 1 was launched using a new 3-stage Qased rocket from Shahroud (36.200 N, 55.334 E), the first Space Launch from this facility.

Little is known about NOUR 1, but the fairing of the Qased rocket depicted what looks like a 6U cubesat, i.e. a small satellite with a bus of roughly 10 x 20 x 30 cm in dimension (not counting any deployed solar panels):




The satellite deployed in a 427 x 435 km, 59.8 degree inclined orbit. The orbit is not sun-synchronous, but does have a repeating ground-track about every 4 days.

Three days after the launch, on 25 April, I managed to image the Upper Stage of the Qased rocket that launched the satellite, with a WATEC 902H camera and Samyang 1.4/85 mm lens:





Attempts to image the payload itself (NOOR 1) initially failed, because the late April/early May passes for my location were not the most favourable concerning illumination angles and sky elevation (these passes were low north for me).

But last night, May 6 around 1:52:11 UT, I had a more favourable pass and clear skies, and successfully managed to image the payload NOOR 1 with the WATEC 902H camera and a SamYang 2.0/135 mm lens. As this camera/lens combo has a small field of view (FOV), the observed arc is short: about 4 seconds. Here is the video:





The satellite was at a range of 595 km and a sky elevation of 46 degrees in the south-southwest at the time of the observation. I estimate it to be around magnitude +7.5 in the imagery.

The satellite shows no clear brightness variation during the captured 4 seconds, as is also visible from this 100-frame stack of the video frames:


click to enlarge

It should be noted that there is footage from May 3rd obtained by Paul Maley in the US which does seem to show some variability. But Paul's footage is very noisy, making interpretation difficult [edit: but see below!]:



(footage by Paul Maley)


At any rate, my own observation from last night does not show clear signs of tumbling, but I'll be monitioring the payload further the coming nights to look for any variability.

-----
UPDATE 7 May 2020

New observations from the night of 6 on 7 May do show brightness variation. The satellite was filmed during a near-zenith pass with the WATEC 902H and a Samyang 1.4/85 mm lens.

Below image is a stack of 126 video frames (representing 5 seconds of footage) shwoing a brightness variability with a peak-to-peak period of about 3.2 seconds:

click to enlarge

Here is video footage from alst night: the framestack above is from the first of the 3 shown sequences:



So the satellite is rotating, at the least (note that rotation can be intentional, e.g. spin stabilisation). So far it does not seem to be wildly tumbling, but I will continue monitoring and adding more data.

[end of update: continuation of original post below]
-----

Why this interest in potential tumbling behaviour? There has been speculation about the state of the satellite, following derogatory remarks shortly after the launch by the US Chief of Space Operations, General Jay Raymond, who called it "a tumbling webcam in space" (and says its a 3U cubesat):



US military sources are clearly trying to imply that the satellite is a failure, but that seems a politically inspired stance. My own optical imagery from last night, as presented here, has no indication for tumbling: if it tumbles at all, then it is at a very slow rate. neverthless, the new data from May 7 do show that the satellite is at least rotating.

Moreover, during the three weeks after the launch, several amateurs including myself have received strong telemetry signals from the satellite at 401.5 MHz, consisting of regularly spaced data packets with one data packet sent each 10 seconds.

The signals were first detected and identified as coming from NOUR 1 by Scott Chapman, and the story of this identification can be read in this highly informative blogpost by Scott Tilley which also points to some interesting aspects of the signal, which can be partly decoded (!).

Below is a spectrogram of the telemetry signals as received by me from Leiden, the Netherlands, during a pass in the evening of  30 April 2020: note how strong and regular the signal is:

click to enlarge

The Doppler curve of the signal matches that for NOUR 1 well, so there is little doubt this signal comes from the Iranian satellite.

(note: the spectrogram also shows the signal of a second satellite at 401.5475 MHz, 'Object F', which is an unidentified cubesat from a Chinese launch in December 2019)

Radio amateurs closer to Iran have reported data dumps when the satellite is in reach of Iranian ground stations. So clearly, the satellite is alive and relaying data of an unspecified nature.

At the end of the first week of May, reports have been coming in that detected signals were weakening or absent. This could indicate that after 3 weeks of functioning, the satellite has developed battery problems. On the other hand it could also mean that after a check-out phase the satellite has been shifted to operational mode, and might only be sending while over Iranian groundstations. Further monitoring should shed light on this.


UPDATE  6 May 2020, 18:50 UT:

 I monitored the NOUR 1 pass of 18:42 UT (May 6) and can confirm that the telemetry signal at 401.5 MHz is no longer present.

Perhaps the satellite has completed checkout and is now in operational phase, which could mean it only sends when in range of Iranian groundstations.


UPDATE 9 May 2020, 20:55 UT:

After Iranian sources indicated the 401.5 MHz frequency would be used again for a few hours on the night of May 9/10, I indeed had positive observations of the telemetry signal again on 9 May during the 18:09 and 19:45 UT passes. Here are a screenshot, full spectrogram, and Doppler-curve fit (blue line: theoretical Doppler curve for NOUR 1. Black dots: observations).

This means the satellite is still alive and the absence of the 401.5 MHz signal for a week was because it was in another operational mode, switching to another frequency.


click to enlarge
click to enlarge
click to enlarge



Tuesday, 11 February 2020

Iran's failed Zafar launch: where did it go?

Zafar-1 launch on 9 Feb 2020. image: IRNA

On 9 February 2020 at 15:48:15 UT, Iran tried to launch a new satellite, Zafar-1, on a  Simorgh (Safir-2) rocket. Video released by the Iranian government shows that lift-off was succesful, and so was first stage separation and second stage ignition around 15:50:00 UT, and fairing separation around 15:50:18 UT. The upper stage next however failed to reach the necessary speed to put the satellite into earth orbit.

The intended orbit according to Iranian sources was a 530 km altitude, 56-degree inclination orbit. Orbit insertion however failed because the Simorgh upper stage burnt out at a speed of 6.533 km/s, almost 1 km/s short of the necessary 7.4 km/s,  according to the Iranian minister of Communications and Information Technology, Mohammad Javad Azari Jahromi. The upper stage and satellite reached an apogee at 541 km altitude before making a long ballistic flight back to earth surface.

Zafar 1 on top of the Simorgh rocket at Semnan. Photo: IRNA

In order to get some idea where it's flight ended, I have modelled the failed launch in STK and GMAT.

The ascend to 541 km altitude was modelled in STK, with launch into the azimuth needed to reach a 56.0-degree orbital inclination (launch azimuth about 134.7 degrees - this was calculated with software I have written myself). I positioned apogee such as to correspond with an attempted orbit insertion about 10 minutes after launch (a typical value for launch into lower LEO). Burnout speed was put at 6.533 km/s, per Iranian sources.

The resulting State Vector was then used as input in GMAT to model the ballistic descend. I did this for two cases: for a 90 kg mass, ~0.25 m2 cross-section object corresponding to the Zafar satellite; and for a 1000 kg mass, 4.5 m2 cross-section object corresponding to the spent Simorgh upper stage. As I had no values for mass and size of the latter, I used values similar to a North Korean UNHA-3 upper stage. The MSISE90 atmosphere with current Space Weather was used in GMAT.


click map to enlarge

The result of this modelling is impact in the Indian Ocean some 25 minutes after launch and some 6400 km downrange from Semnan, at about 12 S, 88 E, for both the satellite and the Simorgh upper stage (see map above). These values should not be taken too strictly, given several uncertainties in the model input: they are ballpark figures.

As it turns out in this case, varying the mass and size have mostly minor effects on the impact position only (note: in an earlier modelling attempt posted on Twitter, the impact point came out closer to Iran, because in that initial model run I had been using a lower burnout speed).

Sunday, 1 September 2019

Image from Trump tweet identified as imagery by USA 224, a classified KH-11 ENHANCED CRYSTAL satellite

click to enlarge. image: US Government

The incredibly detailed image above was leaked declassified and revealed to the world by US President Donald Trump, very characteristically in a tweet, on 30 August 2019.



It shows the aftermath of the failed Iranian Safir launch of August 28/29, with considerable damage to the platform and vehicles. Obviously, there was an explosion or crash of some sort, likely an explosion of an engine or rocket stage or failed lift-off.

The image is a photograph of a printed photograph: you can see the reflection of the camera flash on the photographic print near the center of the image and the silhouet of the person photographing it. There is also some image distortion, likely because the print was curling somewhat at the edges. But the level of detail is amazing (and the original might have been even more detailed).

That level of detail quickly led to speculation: what platform took this image? A drone? A high altitude reconnaissance aircraft? A satellite?

Some initially argued that the level of detail was too high for a satellite. But as we will see in this post, it was made by a satellite, and we can even say which satellite.

The level of detail in the image is incredible and points to one of the NRO's classified KH-11 EVOLVED ENHANCED CRYSTAL electro-optical reconnaissance satellites (they are also known as ADVANCED CRYSTAL, KENNEN, and colloquially as 'KeyHole').

These are high resolution optical satellites that resemble the Hubble Space Telescope, but look down to Earth instead of to the heavens. It is known that the optics of these satellites are 2.4-meter diameter mirrors. Theoretically, from the perigee of their orbits this would yield a resolution of just under 10 cm.

Christiaan Triebert analysed the shadow directions on the image and placed the time of the image between 9 and 10 UT (August 29), or 13:30-14:30 local Iranian time. Michael Thompson pointed out on Twitter that one of the KH-11 satellites, USA 224 (2011-002A), made a pass over the launch site in that time window.

This satellite is a classified satellite, but we do know its orbit because amateur trackers track this object regularly. This is USA 224 passing over my hometown Leiden in June 2014 for example:


USA 224 passing over Leiden, 21 June 2014


This blogpost consolidates two analysis which I initially published through Twitter. I will show in this analysis that there is very little doubt that USA 224 took this image.


Matching view angles 


The map below shows how USA 224 passed almost right over the launch site at 9:43:47 UT on August 29, with a maximum elevation of 87.7 degrees. The photograph tweeted by President Trump was taken post culmination, from the location indicated by the white cross in the map above. That position is based on the analysis that now follows.

click map to enlarge


The depicted trajectory for USA 224 is based on amateur tracking data. I used elset 19239.00965638 which was ~2.5 days old at the time of the overflight. In the absence of a manoeuvre, it should be accurate to a few seconds in time along-track and very little error cross-track.

USA 224
1 37348U 11002A   19239.00965638 0.00010600  00000-0  95384-4 0    03
2 37348  97.9000 349.1166 0536016 134.6567 225.3431 14.78336728    04


The imaged launch site itself is located at 35.2346 N, 53.9210 E, altitude 936 m, and indicated by the blue dot in the map. The launch platform is part of Iran's Imam Khomeini Space Port, near Semnan.

click to enlarge. Image: US Government

Trump's image shows the platform viewed under an oblique angle, looking in a northern direction (i.e. with the satellite to the south of the site). As the launch platform is circular, we can use the ellipticity of the platform on the image to estimate the angle under which the platform was imaged. For this, we have to measure the semi-minor and semi-major axis of the ellipse (denoted Y and R in the diagram below): their ratio corresponds to the sinus of the viewing angle.




The result of this measurement is a nominal view angle of 46.03 degrees. For USA 224, this elevation with respect to the imaged site was reached at 09:44:20.7 UT (nominally), post-culmination when the satellite was to the south of the site. From the satellite ephemeris, the satellite was at an azimuth of 194.85 degrees as seen from the imaged site at that moment. The satellite's geographical position was near 33.005 N,  53.220 E at an altitude of  283 km. The range to the imaged site was 385 km.

I used these values as input in STK and simulated the view of the damaged launch platform as seen from USA 224 for 29 August 09:44:20.7 UT. The images below compare the original image from President Trump's tweet (top) and the simulated view from USA 224 (bottom):


click to enlarge

Ignoring the shadow directions, the simulated view is very similar to the actual image, pointing out that indeed the image very likely was taken by the USA 224 satellite.

(the simulated view uses an overhead commercial satellite image taken at another time, rendered to mimic an oblique view, hence the different shadow directions).

Cees Bassa, in an independent analysis, has calculated very similar figures for the viewing angle and from that azimuth and elevation.


Matching times


In a second analysis, I tried to improve on the time of the image derived from the shadow directions.

When projecting a line through the shadow of one of the masts at the edge of the platform, this line passes almost through the middle of the access road at top right in the image:

click to enlarge

I used this observation to measure the direction of the shadow in Google Earth. It corresponds to an approximate azimuth of 40.45 degrees, which would place the sun at an azimuth of about 220.45 degrees (+- 1 degree error or so):

click to enlarge

Looking this direction up in the solar ephemerids for the imaged site (calculated with MICA), this solar azimuth corresponds to 09:46:25 UT (Aug 29). This is only 2 minutes later than the time for which the image best matches the USA 224 view of the site, as reconstructed earlier in this post.

This again confirms that this image could very well have been taken by USA 224. Both the time matches, and the view matches.

With the uncertainties in the shadow direction measurement taken into account (including uncertainties introduced by possible image deformations), within error margins the two times match. The difference between the measured (~220.45) solar azimuth and the solar azimuth calculated for 09:44:21 UT is 0.85 degrees, i.e. under a degree and hence small.

The 09:44:21 UT  derived from matching the satellite view to the image, probably is more accurate than the time derived from the shadow analysis. This time is probably accurate to a few seconds, given that the satellite TLE used was 2.5 days old.


Why?!


And then the baffling question: why did President Trump tweet an image that otherwise would be considered highly classified?

The KH-11 satellites are classified, and so is imagery from these satellites. If an adversary gets her hands on KH-11 imagery, it reveals information about the optical capacities of these space assets.

In 1984, a Navy intelligence analyst was sent to prison for leaking three KH-11 images to the press.

Reconnaissance satellite imagery made public by the US Government itself over the past decades were either from commercial DigitalGlobe satellites, or purposely degraded in quality such as not to reveal the optical capacities of the KH-11. But now we see a US President tweet, on what appears to be a whim for the purpose of gloating, a very detailed image that as was shown in this post definitely was taken by a KH-11 satellite.

The occassion at which this happened, is eyebrow raising. A failed space launch hardly is a matter of great geopolitical concern. It is something trivial compared to e.g. imagery showing preparations for an invasion, the production of WMD, or atrocities against humanity. The latter could perhaps be argued to be a valid reason to publish imagery that also divulges the capacities of your best space-based imaging platforms: this occasion was not.

Which makes this a rather momentous occasion.

(note: there is a black block in the upper left of the image that seems to be placed there to redact some information that might have been printed there. I think it is likely this information was the time of image, space platform ID and the location of the latter. It points out that some deliberate thought was given to the release of this image, before it was tweeted).


USA 224 passing through Corona Borealis, 17 June 2014



Edit (2 Sep 2019):

In the comments, Russ Calvert makes a very valid point: the phone camera used to photograph the photographic print might also introduce some slant. But I suspect the error introduced this way is small as normally you would try as best as you can to hold the camera perpendicular to the paper you are photographing. A clear slant angle of the camera also would introduce a sharpness gradient that does not seem to be there. The good match between the image and the simulated view from the satellite also bears out that error introduced in this way is likely small.

Edit II (2 Sep 2019): 

Added two archive images of USA 224 passing through the night sky over my hometown Leiden.

Edit III (24 Sep 2019)

Between the infamous 1984 leak by Samuel Moring Lorrison and Trumps 2019 tweet, there was one other occasion that (parts of a) full resolution KH-11 imagery became public. That was an image from the Snowden files published in September 2016 as part of an article in The Intercept,
which according to the annotations on it was taken on 28 January 2009 at 5:16 UT,

I had forgotten about it untill this article by Dwayne Day brought it to my attention again, and then I remembered that I had already identified this image as being taken by USA 129 (1996-072A), a now deorbitted KH-11 reconnaissance satellite.

image source: The Intercept 6 Sept 2016

In 2018 Bill Robinson geolocated the image as showing a part of Zaranj, a southern Afghanistan village on the border with Iran. I in turn was able to show that USA 129 was near this location (see Bill's blog post), in an appropriate position to make the image. As een from the position of USA 129 at 5:16 UT, Zaranj was located at a range of 368 km. Seen from Zaranj, the satellite was in azimuth 216 degrees, elevation 66 degrees at that time.
click map to enlarge

Friday, 10 February 2012

The Iranian satellite Navid photographed

On February 3, 2012, Iran succesfully launched its third satellite into orbit, Navid (2012-005A), using a Safir rocket.

This evening was clear and I had a 86 degree pass of this new Iranian satellite. It is very small (a 50 kg semi-kube, only 50 x 60 cm large!) and hence faint. Using the 1.4/85mm SamYang lens, I nevertheless managed to photograph it, catching it as a faint trail just south of the alpha Persei star group on a 5 second exposure:

click image to enlarge



This is probably the smallest object in orbit I have ever photographed.

Navid is reportedly an imaging satellite, taking photographs from a 250 x 375 km orbit. At the time the photograph above was taken, it was at 316 km altitude.

Saturday, 7 March 2009

An Iranian rocket (Safir 2 r/b)

Weather finally allowed me to observe one of the new Iranian objects from the February 2nd launch. It concerned the rocket booster from the launch, the Safir 2 r/b (09-004B).

Conditions were not perfect (somewhat hazy), but the rocket booster was well visible and I captured it on two images (see below). It showed a clear very slow amplitude brightness variation (amplitude >20 seconds), going between mag. +3 and near-invisibility for the naked eye (> +4). Around the brightness peak it gives a short bright glint. Both my photographs captured such a glint.

(update) Based on the two pictures, and assuming I didn't miss a glint in between them, the glint period is 33.25 seconds, with glints at:

7 Mar 2009 04:26:12.60 UTC
7 Mar 2009 04:26:45.85 UTC


Below the two pictures (as usual, Canon EOS 450D @ 800 ISO + EF 50/2.5 Macro @ F2.8), and the brightness profiles for these trails.

(click images to enlarge)