Stories
Slash Boxes
Comments

SoylentNews is people

posted by martyb on Friday August 02 2019, @10:02AM   Printer-friendly
from the better-not-blow-this-one dept.

[UPDATE (20190802_112243 UTC): SpaceX tweeted:

Team is setting up an additional static fire test of Falcon 9 after replacing a suspect valve. Will confirm updated target launch date for AMOS-17 once complete. (3:06 PM - 1 Aug 2019)

Here's hoping everything is nominal. --martyb]

Static fire test of Falcon 9 complete and team is assessing data—targeting August 3 for launch of AMOS-17 from Pad 40 in Florida

— SpaceX (@SpaceX)

While a successful static fire test isn't considered a huge milestone anymore, it's particularly important in this case because the customer, Spacecom, previously lost a satellite payload on a SpaceX flight in 2016. As a result, this launch will be provided to Spacecom free of charge, after that anomaly during the static fire testing resulted in an explosion of the launch vehicle and Spacecom's AMOS-6 satellite.

The new satellite, known as AMOS-17, will provide telecommunications access across the Middle East, Africa and Europe and will eventually finish up in a geostationary orbit around the Earth.

The launch schedule at Spaceflight Now has better data on the launch date and time:

Launch time: 2252-0020 GMT on 3rd/4th (6:52-8:20 p.m. EDT on 3rd)
Launch site: SLC-40, Cape Canaveral Air Force Station, Florida

A SpaceX Falcon 9 rocket will launch the Amos 17 communications satellite. Built by Boeing and owned by Spacecom Ltd. of Israel, Amos 17 will provide high-throughput broadband connectivity and other communications services over Africa, the Middle East and Europe. Delayed from May 27, June and July.

SpaceX regularly provides a live stream of its launches; this story will be updated when such a link becomes available to us.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.