Sunday, 12 July 2020

OT: Comet C/2020 F3 NEOWISE

click to enlarge
The image above shows comet C/2020 F3 NEOWISE, which is currently visible low on the northern horizon after sunset and before sunrise. From my 51 degree latitude, it is circumpolar, so visible all night, although very low in the sky. For the Northern hemipshere, this is probably the best comet since Hale-Bopp in 1997.

I took the image (or rather: images, as it is an image stack) last night around 00:58 UT (2:58 CEST) from Polderpark Cronesteyn on the outskirts of Leiden. It is a stack of 45 images of 0.6s exposure eacht, at ISO's 1600 and 4000, taken with a Canon EOS 80D + Samyang 2.0/135 mm on a fixed tripod (i.e. no tracking). The comet was only 8 degrees above the N-NE horizon at that time.

Apart from the bright bent yellowish dust tail, a hint of the straight, faint blue ion (gas) tail can be seen.

It was a very nice night (with owls calling), but a bit moist, with a carpet of low fog over the meadows. I had an USB dew lint and USB battery with me, and was glad I did. My glasses fogged over at times.

The comet is visible with the naked eye (even from my urban environment) with a few degrees of tail. It is impressive in 10 x 50 binoculars. the brightness is somewhere around magnitude +2.

The 2.0/135 mm Samyang turned out to be a superb lens for this comet, by the way. I am surprised by what I can achieve with it on this comet without a tracking mount.

Saturday, 4 July 2020

ISS Debris Avoidance Manoeuvre of 3 July 2020

click to enlarge


ROSCOSMOS has announced that the International Space Station (ISS) had to make an unscheduled orbit adjustment (a debris avoidance manoeuvre)  at 18:53 Moscow Time (15:53 UT) on July 3, in order to dodge a piece of space debris. The rocket engine of the Progress MS-14 cargoship attached to the ISS were used for the manoeuvre, burning 100 seconds giving the ISS a delta V of 0.5 m/s. The ISS orbit was raised by about 900 meters as a result.

The brief bulletin did not identify which piece of space debris was dodged. Using COLA, I could however identify it as object 27923 (1987-079AG), a piece of debris from the Russian Proton rocket that launched the Kosmos 1883 GLONASS satellite on 16 September 1987.

One of the rocket stages from this launch shed some 31 pieces of debris in 2003, most of which decayed rapidly. The object that necessitated the July 3 ISS manoeuvre is one of the larger, and one of the few remaining shed pieces on-orbit. It is is a very eccentric, 350 x 4454 km, 64.9 degree inclined orbit (it's apogee has come down considerably over the past 17 years, from almost 20 000 km in 2003). The CSpOC catalogue characterizes its size as 'medium' (i.e. an RCS of 0.1 - 1.0 m2).

Had the ISS not changed it's orbit, this piece of space debris would have made a pass to a nominal distance of ~0.5 km at 18:28:19.07 UT on July 3. Note that this is a nominal value based on two TLE's: so there is a possible error of 1-2 km. But it is clear that this larger piece of debris would have passed well within the 4 x 4 x 10 km safety box around the ISS, necessitating the debris avoidance manoeuvre.

COLA output:

DATE       UT            RANGE   dALT    ANGLE
3 Jul 2020 18:28:09.07   0.5     0.1     107.1

The encounter would have occurred at 436 km altitude over the south Atlantic some 600 km northeast of the Falklands, near 48.1 S,  51.7 W (see illustration above and movie below).

ISS debris avoidance manoeuvres like this are not very frequent: it happens maybe once per 1-2 years.

Saturday, 13 June 2020

A French M51 SLBM test with a 6000 km range on June 12

click image to enlarge

On the morning of June 12, 2020, the French Navy test launched an unarmed M51 SLBM from the Triomphant-class submarine Le Téméraire.

The launch was from a spot near the French coast just south of Audierne Bay in Bretagne, not far from the French Naval port of Brest, according to a French Government bulletin. Navigational Warnings place it around 47o.65 N, 4o.15 W. The launch direction was towards the Caribean, with impact in the Atlantic Ocean near 24o.4 N, 66o.1 W according to the same Navigational Warnings.

The locations of the hazard areas from these Navigational Warnings point to a 6000 km flight trajectory (see figures above and below):


HYDROLANT 1882/20

EASTERN NORTH ATLANTIC.
CELTIC SEA.
BAY OF BISCAY.
FRANCE.
DNC 08.
1. MISSILE OPERATIONS 0200Z TO 1100Z DAILY
11 JUN THRU 11 JUL IN AREAS BOUND BY:
A. 47-12N 010-25W, 47-49N 004-31W,
47-39N 004-01W, 47-24N 004-11W,
46-44N 010-17W.
B. 46-17N 019-54W, 46-50N 017-09W,
45-07N 016-29W, 44-35N 019-01W.
2. CANCEL THIS MSG 111200Z JUL 20.//

Authority: NAVAREA II 167/20 042002Z JUN 20.

Date: 060713Z JUN 20
Cancel: 11120000 Jul 20



 

NAVAREA IV 485/20

NORTH ATLANTIC.
1. MISSILE OPERATIONS 0200Z TO 1100Z DAILY
11 JUN THRU 11 JUL:
A. IN AREA BOUND BY
39-37N 040-14W, 40-40N 037-48W,
39-41N 037-07W, 38-39N 039-31W.
B. IN AREA WITHIN 92 MILES OF 24-24N 066-06W.
2. CANCEL THIS MSG 111200Z JUL 20.//

Authority: AVURNAV BREST 070808Z JUN 20.

Date: 070851Z JUN 20
Cancel: 11120000 Jul 20



I have plotted the Navigational Warnings on the map below. The line shown is a simple STK-modelled ballistic trajectory, which fits these area's well. Assuming a 1200 km apogee, the flight-time should have been around 23 minutes.

Click map to enlarge

The M51 is  the newest French SLBM. It is in service since mid-2010. It has three stages and can carry up to 10 RV's. It's maximum range is said to be near 11 000 km, i.e. comparable to the Trident-II SLBM of the US Navy and Royal British Navy. This is the 5th succesful test of an M51 SLBM (a 6th test attempt in May 2013 ended in failure).

A nice summary of what is known from public sources about this test is provided in this article by Tyler Rogoway on The Drive.


Note added
For those interested in these issues: last year, I did an in-depth analysis of several Trident-II SLBM test launches, including one that was serendipitously photographed by an astrophotographer from the Canary Island. The latter observation allowed to estimate the apogee altitude of that test.

Thursday, 11 June 2020

SkyTrack: a simple tool to calculate satellite positions and visuallize satellite trajectories in Google Earth



Over the past years I have written a number of simple software tools to ease some of my data analysis. Some of these I have released into the wild through my software webpage. Others, which are more experimental, I keep to myself for now.

This week I have released another tool into the wild: SkyTrack.

SkyTrack (now in version 2.5) was initially written by me to quickly create a datafile with geographic coordinates of the trajectory of a satellite, in a format that is easy to import in QGIS, the mapping application that I use to make the trajectory maps that you frequently see in my blog posts.

It has since evolved and is starting to get to a point where it might be useful to others, hence why I release it now.

The output of the program is numerical (a table with data), not graphical, which will limit the usefulness to many people. However, as of the latest version (2.5) the program has the option to generate a .kml file of the trajectory for import in Google Earth (if Google Earth is installed on your pc, it will actually auto-open it and load the .kml, after saving).

When the .kml is loaded into Google Earth, the resulting images look like this:







The program takes lines 1 and 2 of a TLE as input (you copy/paste them into the input textbox). You then provide it with a time window, a desired time step, and an observing site.

It will then calculate the ground-track (the subsatellite-point) over that time window, in the given time steps; it will also calculate the altitude above the Earth at each time instance; the range to the observing site and the satellite's position in both RA/DEC and azimuth/elevation as seen from the observing site. It will also provide an indication whether the satellite is sun-illuminated at each time instance

As optional output, the program can add EFG (ECEF) X, Y, Z coordinates, as well as the EFG velocity vector. It can also calculate the Doppler-shift corrected radio frequency for the satellite, if a center frequency is given.

There are also options to restrict the program to only provide output when the satellite is a specified distance in degrees above the horizon as seen from the observing site, and/or only provide output when the satellite is sun-illuminated.

There are a number of options as well regarding the output format. A pdf with the download provides instructions for use.

The program is currently only available for 64-bits Windows. It employs Microsoft's .NET framework, and SGP4 DLL's that are courtesy of the US AFSPC.

For the future, I want to add some direct graphical output options, but it might take a while before I get to that. So far, development of this tool was largely done when the need for a specific feature arose.

Wednesday, 3 June 2020

Introducing a new web resource: Launchtower

Before new launches, I frequently publish orbital element (TLE) estimates that can help satellite observers plan observations of the payload and/or associated rocket stage directly after launch.

Untill now, I published these pre-launch estimated TLE's on the SeeSat-L Mailing List and occasionally also on this blog. And I will keep doing that: but I realized that it would perhaps be good to have a central website for these pre-flight TLE's.

So I introduce to you: Launchtower (http://launchtower.langbroek.org).


The TLE estimates in question are based on public information about the launch site, launch date and launch time, and (if made public) the orbital altitude and orbital inclination aimed for.

For classified launches (where this information usually is not available), educated guesses are made based on amongst others information gleaned from NOTAM's and Navigational Warnings. These provide information on launch time windows, and the orbital inclination aimed for, which can often be deduced from the launch azimuth, which in turn can be deduced from the locations of the launch hazard areas and upper stage deorbit areas found in Navigational Warnings.

The website will provide TLE estimates for launches that are "of interest". The criteria for what comprises "of interest" are basically:  those launches that are of interest to me.

Generally speaking, these will be: classified launches; human spaceflight; and launches that overfly Europe on the initial revolution.

TLE's can be used to plot a sky track for your location, using predictive software like for example HeavenSat.

 
UPDATE:

On request, I have added a plain-text file URL as well, to which you can point software that can (stupidly) only load TLE's from plain text files on a web-adres. Link is on the main Launchtower page.

Sunday, 31 May 2020

Imaging a pass of the Crew Dragon Demo-2, and a close fly-by of the Crew Dragon by USA 245! [UPDATED]

click photograph to enlarge

Yesterday May 30 at 19:22 UT finally saw the launch of the SpaceX Crew Dragon Demo-2 with astronauts Hurley and Behnken on board, returning a human spaceflight capability to the USA after nine years of having to hitch rides on a Russian Soyuz.

When the Crew Dragon first passed over the Netherlands some 23 minutes after launch (see map with the launch trajectory in  a previous post), the sun was still just above the horizon for my Leiden location. I nevertheless tried with binoculars, using the moon as a guide, but saw nothing.

But two hours after launch on the second revolution, near 21:18 UT, we did have a visible pass, albeit in late twilight and very low above the horizon: at a maximum elevation of only 9 degrees over the horizon and a range of almost 1200 km!

To observe this pass I went by bicycle to Cronesteyn Polder at the edge of Leiden, where I have an uninterupted view to the horizon, and set up my photo camera. First, at 23:14 local time (21:14 UT), I saw the ISS pass with the naked eye low on the southwest horizon. I then took to binoculars and waited for the Crew Dragon, which should pass somewhat lower in the sky some 4 minutes after the ISS.

I picked the Crew Dragon up in my 10 x 50 binoculars starting around 21:17:30 UT, while it was passing through Crater and Corvus. I watched it untill it entered Earth shadow at about 21:19:00 UT. It was not particularly bright, due to the low elevation and still bright sky background. By comparison to stars in Corvus I estimate it to have been magnitude +3 to +3.5, too faint at this elevation and with this sky brightness to be seen naked eye. It was at a range of almost 1200 km at that time, over Northern Spain!

Click photograph to enlarge

The image above shows the Crew Dragon during this pass. It is a stack of 45 exposures of 0.5 seconds each, with a Canon EOS 80D and SamYang 1.4/85 mm lens at F2.0, 500 ISO, 21:17:40 - 21:18:09 UT (May 30). Stars in the image belong to the constellations Crater and Corvus. The small breaks in the trail are the brief moments between the successive photographs that make up the stack.

The image below is another stack, this time of 52 photographs with the same camera setup, made between 21:18:25 - 21:18:59 UT. You see the Crew Dragon disappear in Earth shadow at the left end of the image. The image is slightly wobbly - my tripod was on a soft grassy surface. I like this image best though:

Click photograph to enlarge

It was pretty cool seeing the Crew Dragon, while knowing it was carrying two astronauts!

But it becomes even more interesting: in two images around 21:18:19 UT, I have another brighter satellite moving under a slant upwards in the opposite direction. You can see it in the upper right corner of this image (several lay observers saw this brighter satellite too and mistook it for the Crew Dragon):


Click photograph to enlarge


This object is the classified US KH-11 spy satellite USA 245 (2013-043A).

And as it turns out, it was really close to the Crew Dragon, and my image truely captures, within a few seconds, the actual moment of closest approach! This was serendipity, as I had not planned this and the presence of USA 245 took me by surprise.




Nominally, the minimum distance between USA 245 and the Crew Dragon during this fly-by was only 125 km with closest approach happening at 21:18:17 UT. USA 245 was flying this distance 'above' the Crew Dragon. Both objects were over northern Spain around the time of the flyby, with the point of closest approach over 43.40 N, 2.50 W, on the Basque coast.

There is some uncertainty in the actual fly-by distance (see below), but not much.

This is the output from a COLA analysis for this fly-by:

DATE      UT          SSC   NAME    TARGET      KM  
5/30/2020 21:18:16.99 39232 USA 245 CREW DRAGON 125.3

My analysis is based on CSpOC elset epoch 20151.85044152 for the Crew Dragon, and amateur elset 20146.86101776 for USA 245. There is some leeway in the exact time and distance of the flyby, for two reasons:

1)  from my observations, the Crew Dragon was some 3 seconds late on the used elset;

2)  the USA 245 elset epoch, based on amateur observations that include my own, was 5 days old. However, the sky position of USA 245 in the image is very close to the ephemeris, so the 5-day-old orbit nevertheless seems a good fit to reality.

Taking these points into account, I estimate that the uncertainty in the minimum distance between both objects is no more than 30 km, and only a few seconds in time.

In the map below, I have plotted the trajectories of both objects (I have accounted for the fact that the Crew Dragon was ~3 seconds behind on the elset in this map). USA 245 was moving nortwest-wards, the Crew Dragon southeast-wards.

Note that the USA 245 trajectory was situated some 125 km above that of the Crew Dragon. So to be clear, there was no danger of a collision. This is a safe distance.

click map to enlarge

 This is an animation of the close fly-by:




In fact, it could very well be that this close flyby was intentional, and that USA 245 was actually imaging the Crew Dragon at that moment.

USA 245 is a KH-11 electro-optical reconnaissance satellite: a satellite that resembles the Hubble Space Telescope and makes high resolution images of the earth surface (similar to this infamous one) with resolutions of 10 cm or better.

There have long been rumors, reported by amongst others NBC News, that KH-11 satellites were used to inspect the outside of Space Shuttles post-launch (e.g. that of the inaugural STS-1 flight) for tile damage. We also suspect that KH-11 satellites inspect X-37B's after launch, based on the odd jumps in launch times of the latter (see this analysis by Bob Christy).

So there is a real possibility that this close flyby of the Crew Dragon by USA 245 was intentional, and used to image the spacecraft to see if it was not damaged and everything deployed as it should.


UPDATE 1 June 2020 13:50 UT:


I am retracting the notion of intentionality of this encounter. Both Michael Thompson and I have done an extended analysis of potential KH-11 encounters with the Crew Dragon, where we looked at potential encounters had the Crew Dragon launched on the original launch date of 27 May.

There appear to have been no particularly close encounters would the Crew Dragon have launched on May 27, which calls into question the intentionality of the encounter on May 30.

That said: it is still possible that imaging of the Crew Dragon took place, as of course this would have been a perfect opportunity. I guess we'll never know. Unless, as someone put it to me in private, tongue in cheeck: "if they put it in a briefing, maybe Trump will tweet about it!". 

The analysis also found a second close encounter for May 30, with the KH-11 satellite USA 224 (2011-002A), on 30 May 20:07:50 UT, some 45 minutes (half a revolution) after launch, with a nominal miss distance of 105 km. This however was a pass where the Crew Dragon was in Earth shadow, so not illuminated (which does not preclude infra-red imaging however). COLA output for this encounter:

DATE      UT          SSC   NAME    TARGET      KM 
5/30/2020 20:07:50.30 37348 USA 224 Crew Dragon 105.4


Saturday, 30 May 2020

New attempt to launch the Crew Dragon on May 30: trajectory

screenshot from the May 27 live webcast


In an earlier post I discussed the SpaceX Crew Dragon Demo-2 launch. Originally slated for 27 May, it was postponed (with the astronauts already seated on board) because of bad weather: Tropical Storm Bertha more north on the US coast was the main culprit.

The new launch attempt will be on May 30 at about 19:22:45 UT (the subminute time comes from Spaceflight Now, not from an official SpaceX or NASA source, so is apocryphal). If that launch is scrapped to, the third backup date is May 31 near 18:59 UT.

As things currently (29 May 21:00 UT) stand, weather prospects are not that good for both these dates either, with currently a 50% chance of a weather violation on the 30th and 40% on the 31st: so perhaps we will see a scrub again.


Click map to enlarge

But in case the launch does happen on 30 May, the map above is the trajectory the Crew Dragon will fly on its first revolution (times on the map are in UT).

Some 23 minutes after launch, the Crew Dragon will pass over Europe, along this trajectory (times are inUT: add one hour to get BST and 2 hours to get CEST):

Click map to enlarge
Note the location of the day/night terminator...only eastern and southeastern Europe has sufficiently dark skies at that moment.

The launch time has shifted considerably forward compared to the May 27 original launch date, by about 1h 10m. As a result, the pass is no longer favourable for NW Europa, as the pass will be before sunset for the UK, and around sunset for coastal Europe.

Only longitudes east of say longitude 13 deg E will have a sufficiently dark sky to see it on the first revolution, so eastern and southeast Europe will have a prime seat this time.

Coastal western Europe and the UK might have, depending on your locality, a theoretical chance to see the second pass 1.5 hours later, near 21:18 UT. For most localities, that will however be a very low elevation pass though, often at a maximum elevation of les sthan 10 degrees.

At the end of this blogpost, I will provide some sky charts for several European localities for both those localities with a chance to see something of the first pass, and those who might theoretically catch the second pass.

The reason that the launch time is 1h 10m earlier on May 30 than on May 27, is that the launch time is instantanious as it is determined by the moment that the orbital plane of the ISS passes over the launch site. This time shifts back by 23m 22s each day, as is clear from this tabel in which I calculated orbital plane crossings over LC-39A (and is visualized in the illustrations below it):

ISS plane crossing over LC-39A:
-------------------------------
Date           UT   
27 May         20:36:52
28 May         20:13:30
29 May         19:50:09
30 May         19:26:47
31 May         19:03:26

-------------------------------



You can also see in the table that the actual launch time is a few minutes before the plane crossing. This has two main reasons.

One is that what is actually of relevance is the position of the orbital plane once the rocket reaches orbital height (a few minutes after launch).

The other is that the Crew Dragon initially is inserted into a ~200 km altitude orbit, which is only half the orbital altitude of the ISS. As a result, the Precession rate of the RAAN is faster than that of the ISS: so launch has to be somewhat earlier or otherwise, over the 19 hour flight, its RAAN would overshoot rather than match that of the ISS upon arrrival at the orbital altitude of the ISS.

The reason May 28 and May 29 were not chosen as backup dates, is because of a second consideration: the ISS has to be within a certain distance window to the launch site in order for the two (Crew Dragon and ISS) to meet up after 19 hours of flight. As it happens, and I am not sure that is deliberate or just a happy coincidence, this also means that on the chosen dates, docking will happen on the night-time side of the Earth (with launch on May 28 or 29 it would have happened on the daytime-side).

Below are a number of sky maps for localities that have a dark enough sky (generally: sun no less than 5 degrees below the horizon) to see the first pass, some 25 minutes (for eastern Europe) after launch near 21:46 CEST. Note that there is a time uncertainty of about 1 minute or so.

TLE's are provided below the maps.

NOTE: if you are not near one of these localities, then Heavens-Above provides you with predictions for your custom location. Please note however that Heavens-Above predictions for the second revolution (the 23:19 CEST pass over Europe) seem to be based on the TLE for the first revolution, resulting in a time difference of about 1 minute with my predictions below.(but also realise there is an uncertainty of 1-2 minutes in the estuimated orbit anyway).










Maps for locations in NW Europe might theoretically be able to see the Crew Dragon on its second revolution, near 23:18 CEST (22:18 BST), some 2 hours after launch. But in most cases this will be very low above the horizon. Please note that the time uncertainty is 1-2 minutes at least!







Here is an estimated TLE for the first revolution:

CREW DRAGON                                      initial orbit
1 70000U 20999A   20151.80474535 -.00003603  11390-4  00000+0 0    04
2 70000  51.6423 075.0039 0122953  45.6251 315.4951 15.99554646    01



And here is an estimated TLE for the second revolution:

CREW DRAGON                                      second revolution
1 70001U 20999A   20151.93029831 -.18507952  12289+0 -23808-1 0    05
2 70001  51.6233 074.5097 0096856  46.3995 314.2887 15.95177824    03


Tuesday, 26 May 2020

Imaging some splendid passes of HTV-9 (Kounotori-9) and Cygnus NG-13



It are very busy times at the International Space Station. Spaceships come and go.

First, on May 11, the US cargoship Cygnus NG-13 was released from the ISS, three months after berthing to it. This cargoship had been launched on 15 February 2020 and berthed on 18 February. After its release from the ISS two weeks ago, it is currently free-flying to do experiments. It will perform a controlled reentry over the southern Pacific on 29 May.

On 20 May at 17:31 UT, the Japanese cargoship HTV-9 (Kounotori-9) was launched. It berthed to the ISS on 25 May. This provided the opportunity to see two ISS cargoships, one departing and one arriving, in the sky last week.

And it continues: we are in anticipation of the Crew Dragon Demo-2 launch, on May 27 if weather cooperates (see my previous blogpost), bringing to astronauts to the ISS.

Both Cygnus NG-13 and HTV-9 made some splendid evening passes last week. Weather was clear on most days, allowing me to observe and photograph several passes, often two on one evening. Through Twitter, I managed to get a lot of people to go out and watch the passes. HTV's are very bright and distinctly orange objects, easily visible with the naked eye even in deep twilight and from an urban environment. So they are ideal objects to get people out and watch.

HTV-9 was a spectacular sight on every pass. It reached magnitude 0 to -1, with a very distinct orange colour that is due to the orange thermal foil it is wrapped in. It was also prone to producing brief bright flares to magnitude -2 to -3. It did this on almost every pass, sometimes multiple times. here is an example, from May 21:


Click to enlarge

click to enlarge

Below are a number of photographic stacks I made during these HTV-9 passes (gaps in the trails are the brief periods between successive photographs in the stack). The first image showing another flare: the second bright satellite crossing the path of HTV-9 in the third image is Resurs P1. Note the orange colour, especially apparent in the second image. Visually, the orange colour was even more profound than in these images (where they have washed out a bit due to the brightness of the trail).


Click to enlarge
Click to enlarge
Click to enlarge


Cygnus NG-13 was much fainter than HTV-9. During a  good pass it would reach magntude +3, but often was below naked eye visibility. Here is imagery from one of the brighter passes, on May 19 when it reached magnitude +3:


click to enlarge
Click to enlarge
Click to enlarge

Click to enlarge


Sunday, 24 May 2020

The trajectory of the upcoming Crew Dragon Demo-2 launch, returning the US to crewed spaceflight

Photo: SpaceX

UPDATE: the Crew Dragon launch has been postponed to NET 30 May, 19:22 UT
Below is the original text and maps, which are however no longer valid!
New maps in a new, separate post.

If everything goes well, SpaceX and NASA will launch the Crew Dragon Demo-2 flight with astronauts Bob Behnken and Doug Hurley to the International Space Station on 27 May 2020. The launch is slated for 20:33:33 UT (note: some sources now say 20:33:31 UT), from LC-39A.

This is a historic flight, because after a 9-year hiatus it will return NASA to a crewed flight capacity. It is the first crewed flight launching from US soil on a US rocket since the Space Shuttle program ended in 2011. Over the past 9 years, US astronauts had to hitch a ride on Russian Soyuz spacecraft in order to get to space.

The Crew Dragon Demo-2 will fly this approximate flight trajectory, bringing it over Europe some 23 minutes after launch:

click map to enlarge
click map to enlarge

The times in the map above are in UT (GMT): for CEST add +2 hours; for BST add +1 hour. I created the maps using the (uncrewed) Crew Dragon Demo-1 test flight from March 2019 as a proxy.

Based on that same Crew Dragon Demo-1 flight, I estimate these orbital elements for the first orbit:


CREW DRAGON DEMO-2   
1 70000U 20999A   20148.85443285 -.00003603  11390-4  00000+0 0    03
2 70000  51.6423 089.9835 0122953  45.6251 315.4951 15.99554646    09
 

estimated initial orbit for launch at 27 May 2020, 20:33:33 UT


You can use this so called TLE (for an explanation of these numeric lines click here) to make pass predictions and maps of the trajectory in your local sky for your own location, using prediction software like HeavenSat.

Be aware that it is approximate: so allow for a possible error of 1-2 minutes in the time it will pass in your sky, and a small cross-track error (I expect this latter to be less than 1 degree, i.e. less than two moon diameters).

Weather willing,  the Crew Dragon containing the astronauts and the Falcon 9 upper stage will be visible from much of Europe some 23 minutes after launch.

Northwest Europe has it pass in twilight, but Dragon's tend to be bright, so twilight should be no problem and the Dragon and Falcon 9 should be easily visible by the naked eye, except perhaps from the British Isles where it is still quite light.

I do advise using binoculars once you have located the spacecraft, as the Crew Dragon and the Falcon 9 upper stage will be close together, and with binoculars you will see them separately (you can see some photographs of a pass of a just launched Cargo-Dragon and its Falcon 9 upper stage from March this year in an earlier post here).

If you are lucky, you might even catch some small corrective thruster firings as small "puffs", like in this movie which I shot of a pass of the Dragon CRS-20 in March this year (look for the "puff" going upwards around 05:13:00 UT in the video):




(the two slowly varying objects astride the Dragon and Falcon 9 stage in the video above are the two ejected solar panel covers. The Crew Dragon does not have these, as far as I know).

The Falcon 9 upper stage will be deorbitted some 55 minutes after launch, over the southern Indian Ocean west of Australia.


photo: SpaceX

Below are my predicted sky tracks for a number of places in West and Central Europe, valid for launch on 27 May at 20:33:33 UT .

Times listed in the plots below are in local time (generally CEST, except for London which is BST). Please be aware that there is an uncertainty of about 1 to 2 minutes in the actual pass time!!! The track placement in the sky should generally be correct though. Bottom of the plots is either South or North, depending on the location (see the annotations on the plots).


Note added 25 May: the Heavens-Above webservice now provides you with custom predictions for the Crew Dragon for your observing site.



Amsterdam

Berlin

Brussels

London

Paris

Prague

Vienna
Hamburg

Lyon

Marseille

Munich

Reims

Strassbourg