Author Topic: SpaceX Falcon 9 : Telstar 18 Vantage/Apstar-5C : Sept 10, 2018 - DISCUSSION (Read 68351 times)

Nehkara · « **Reply #60 on:** 09/07/2018 09:47 pm »

Does anyone know the current location of OCISLY?

Is it anywhere near this brand new yellow X on the map?

Alexphysics · « **Reply #61 on:** 09/07/2018 10:01 pm »

Quote from: Nehkara on 09/07/2018 09:47 pm

Does anyone know the current location of OCISLY?

Is it anywhere near this brand new yellow X on the map?

I think not, it seems that mark is around 70ºW and the droneships are usually more like 74ºW, it seems that it is only 4º but that means at least 500km away in that direction, not to mention the droneship is a little bit more to the south so that adds distance, so probably that yellow X could be somewhere around 600-800km from the droneship. This is just by looking at it, nothing precise, I'm sure someone could do it much better

gongora · « **Reply #62 on:** 09/07/2018 10:12 pm »

Quote from: Nehkara on 09/07/2018 09:47 pm

Does anyone know the current location of OCISLY?

Is it anywhere near this brand new yellow X on the map?

Raul's SpaceX Map is usually a good place to check for that sort of information.

deruch · « **Reply #63 on:** 09/09/2018 03:05 am »

Quote from: Nehkara on 09/07/2018 09:47 pm

[Image]

Does anyone know the current location of OCISLY?

Is it anywhere near this brand new yellow X on the map?

We don't know where it is now, but the planned recovery location--based on the FCC filing for this mission--was approximately in the area I marked below (BTW, I borrowed the marker directly from the underlying image, so it's no longer indicating the post storm remnants). Whether that recovery zone is still the current one or if sea states or other long range storm effects have necessitated any changes we don't know.

Also, please note (Nehkara, Alexphysics, and all others): NSF site preference/guidelines is that all images be attached instead of directly linking to them. It requires an extra step of first saving/downloading a copy of the original image so that you can then attach it as a file when you comment, but it is easily accomplished by just right-clicking on the original image and choosing "save image" or similar option. Attaching, instead of linking, prevents the images from interfering with NSF's ability to have the site layout automatically adjust to fit variously sized screens. This policy should not only be adhered to by those posting but also by those quoting comments that include a unknowingly linked image. If you're unsure how to do this, you can look at how either @gongora or I have quoted Nehkara's comment and then edited the actual image link out of it (I just deleted the line of text which had the url/hyperlink and then included a placeholder marker). Thank you.

Alexphysics · « **Reply #64 on:** 09/09/2018 07:19 am »

Quote from: deruch on 09/09/2018 03:05 am

Quote from: Nehkara on 09/07/2018 09:47 pm
[Image]

Does anyone know the current location of OCISLY?

Is it anywhere near this brand new yellow X on the map?

We don't know where it is now, but the planned recovery location--based on the FCC filing for this mission--was approximately in the area I marked below (BTW, I borrowed the marker directly from the underlying image, so it's no longer indicating the post storm remnants). Whether that recovery zone is still the current one or if sea states or other long range storm effects have necessitated any changes we don't know.

Also, please note (Nehkara, Alexphysics, and all others): NSF site preference/guidelines is that all images be attached instead of directly linking to them. It requires an extra step of first saving/downloading a copy of the original image so that you can then attach it as a file when you comment, but it is easily accomplished by just right-clicking on the original image and choosing "save image" or similar option. Attaching, instead of linking, prevents the images from interfering with NSF's ability to have the site layout automatically adjust to fit variously sized screens. This policy should not only be adhered to by those posting but also by those quoting comments that include a unknowingly linked image. If you're unsure how to do this, you can look at how either @gongora or I have quoted Nehkara's comment and then edited the actual image link out of it (I just deleted the line of text which had the url/hyperlink and then included a placeholder marker). Thank you.

I quoted their comment but I don't know how to remove that thing, that's why it remained in my quote. Anyways, sorry for the inconvenience.

FutureSpaceTourist · « **Reply #65 on:** 09/09/2018 12:24 pm »

Look forward to seeing this:

Quote

For Sunday’s Falcon 9 launch, I’ll be accompanied by some folks from VICE! They’re making an HBO special about my coverage for this launch, looking at what goes into covering photographing rocket launches as a member of the media.

https://twitter.com/johnkrausphotos/status/1038444217046118401

xm11 · « **Reply #66 on:** 09/09/2018 04:16 pm »

https://www.space.com/41762-spacex-telstar-18v-satellite-launch-webcast.html

the launch delay to 10 September

Comga · « **Reply #67 on:** 09/09/2018 04:21 pm »

Quote from: xm11 on 09/09/2018 04:16 pm

https://www.space.com/41762-spacex-telstar-18v-satellite-launch-webcast.html

the launch delay to 10 September

The article says launch is still tonight.
It is late enough that it’s Sept. 10 UTC.
So this is not announcing an additional slip.

JimO · « **Reply #68 on:** 09/10/2018 02:51 am »

Sunrise in SE Nigeria on Sep 10 is 05:24 UTC so a 04:00 liftoff would provide perfect observing conditions for the GTO burn plume [and dual-plume thermal conditioning dump], from the ground [and from ships and planes in the area]. It's probably too late to alert any known skywatchers in that region, they're all asleep?

xm11 · « **Reply #69 on:** 09/10/2018 03:33 am »

56 minute for launch

CJ · « **Reply #70 on:** 09/10/2018 04:40 am »

On case anyone is late to the party and scrambling around to find the webcast link (like I just did at T-6!) here it is.

T-5, hope the weather holds!

Chris_Pi · « **Reply #71 on:** 09/10/2018 04:40 am »

Per webcast, S2 oxygen's loaded already. How does this work out with the subcooling? Circulating new oxygen in to keep the stuff in the tank cold or something?

StephenB · « **Reply #72 on:** 09/10/2018 05:08 am »

Was it just me or did the rocket seem to have more acceleration, especially coming off of the pad?

Lar · « **Reply #73 on:** 09/10/2018 05:16 am »

Quote from: StephenB on 09/10/2018 05:08 am

Was it just me or did the rocket seem to have more acceleration, especially coming off of the pad?

Just you. It is common for people to post "it seemed faster"/"it seemed slower" after a launch. The mass is almost the same every time regardless of payload (which is a very small fraction of the GLOW) so the speed off the pad will be the same as well. To a very close approximation.

note: this is true for laucnhes using the same vehicle. There were changes as we progressed from 1.0 to FT to block 5...

JeanDV · « **Reply #74 on:** 09/10/2018 05:21 am »

It looks to me that S1 is leaning to the right.
Optical illusion or possible deformation of the legs?

Joffan · « **Reply #75 on:** 09/10/2018 05:22 am »

Great launch and deployment. Congrats to SpaceX once again and to Telesat for a successful evening's rocketry.

I noticed no invitation to look at the careers page at the end of the webcast there...

Steven Pietrobon · « **Reply #76 on:** 09/10/2018 05:29 am »

Quote from: JeanDV on 09/10/2018 05:21 am

It looks to me that S1 is leaning to the right.
Optical illusion or possible deformation of the legs?

Looks like a fish eye lens is bending the vehicle to the right.

Congratulations to SpaceX and Telesat for the successful launch!

HVM · « **Reply #77 on:** 09/10/2018 05:31 am »

MECO seems to happened lot sooner than timeline show, also meco to stage separation (mainly to the change view to inside of the intersatge) feels lot longer. Of course there can't be any actual problem coz S1 is on the droneship...

CorvusCorax · « **Reply #78 on:** 09/10/2018 05:41 am »

Quote from: HVM on 09/10/2018 05:31 am

MECO seems to happened lot sooner than timeline show, also meco to stage separation (mainly to the change view to inside of the intersatge) feels lot longer. Of course there can't be any actual problem coz S1 is on the droneship...

It was a bit confusing to me, too, but I think what happened was the screen switched to the internal camera view too soon. MECO hadn't yet happened, S1 engines were still running, yet all we saw was the S2 nozzle from both above and below. MECO was then announced by the commentator, and separation happened just the usual timespan after.

ZachS09 · « **Reply #79 on:** 09/10/2018 05:59 am »

First part of a series of photos taken from the Embry-Riddle Aeronautical University in Daytona Beach.

There was a barbed wire fence in front, but it's a good thing it did not block everything.