Quote from: scr00chy on 07/19/2020 12:04 pmQuote from: gongora on 07/19/2020 03:38 am I followed the story on the web: https://bit.ly/EquiposSAOCOMThe article has some good infoQuoteFive days before launch, the Argentine and SpaceX engineers will conduct a second procedural test, which this time will include the launcher and the satellite.Are they saying they're going to do the static fire with payload attached?As far as I know, yes, this is the case. We'll use this test as the last rehearsal before the launch.PS: I was surprised, too. I thought they stopped doing static fires with the payload attached after AMOS-6.
Quote from: gongora on 07/19/2020 03:38 am I followed the story on the web: https://bit.ly/EquiposSAOCOMThe article has some good infoQuoteFive days before launch, the Argentine and SpaceX engineers will conduct a second procedural test, which this time will include the launcher and the satellite.Are they saying they're going to do the static fire with payload attached?
I followed the story on the web: https://bit.ly/EquiposSAOCOMThe article has some good info
Five days before launch, the Argentine and SpaceX engineers will conduct a second procedural test, which this time will include the launcher and the satellite.
Quote from: KTigress on 07/20/2020 02:20 amQuote from: scr00chy on 07/19/2020 12:04 pmQuote from: gongora on 07/19/2020 03:38 am I followed the story on the web: https://bit.ly/EquiposSAOCOMThe article has some good infoQuoteFive days before launch, the Argentine and SpaceX engineers will conduct a second procedural test, which this time will include the launcher and the satellite.Are they saying they're going to do the static fire with payload attached?As far as I know, yes, this is the case. We'll use this test as the last rehearsal before the launch.PS: I was surprised, too. I thought they stopped doing static fires with the payload attached after AMOS-6.They did, but it has technically always been up to the customer to have the payload on or not. NASA allowed the DM-1 Dragon to be on the booster for the static fire. Several (all? I haven't been keeping track) of the Starlink static fires have had the Starlinks on top.
What was the reason for changing launch locations from VAFB to KSC?
Quote from: TJL on 07/21/2020 12:34 amWhat was the reason for changing launch locations from VAFB to KSC?1st off prove they can do it, since the Range approved Launching certain SSO & polar trajectories with a Dogleg again from the Eastern Range. 2nd keep the launch team & personal at same location because it's pretty much 1 team now. 3rd it's a little easier for foreign nationals to travel KSC VS VAFB & CCAFS/CCSFS
SAOCOM 1B is pushed to late August * the launch of the SAOCOM 1B had to be rescheduled towards the end of August , due to the additional time that the company SpaceX required for the launch vehicle's set-up .* ...
Quote from: Aphelios on 07/25/2020 03:59 pmSAOCOM 1B is pushed to late August * the launch of the SAOCOM 1B had to be rescheduled towards the end of August , due to the additional time that the company SpaceX required for the launch vehicle's set-up .* ...Is the Spanish "puesta a punto" (fine tuning?) consistent with saying they need more time to finish refurbishing B1059, which made its third flight back on 13 June (Starlink v1.0 L8)?
I could imagine this flying on B1060.2 and B1059.4 being used for Starlink v1-11 instead.
Finally, [Gabriel Absi ,Manager of INVAP's Space Projects Area] explained the reason why they had to postpone the [SAOCOM 1B launch] date from the end of July to the end of August: "There is a North American [USA] satellite [NROL-44] that has priority over the rest because it is used for the security of the United States and that is why they postponed us a month, We don't have a specific date yet but we have a launch scheduled for the end of August."
https://spaceflightnow.com/launch-schedule/ (August 17 update)QuoteAug. 27 • Falcon 9 • SAOCOM 1BLaunch time: 2319 GMT (7:19 p.m. EDT)Launch site: SLC-40, Cape Canaveral Air Force Station, Florida
Aug. 27 • Falcon 9 • SAOCOM 1BLaunch time: 2319 GMT (7:19 p.m. EDT)Launch site: SLC-40, Cape Canaveral Air Force Station, Florida
Scheduled:Date - Satellite(s) - Rocket - Launch Site - Time (UTC)2020August 26 - NROL-44: Orion 10 (Mentor 8 ) (TBD) - Delta IV-H [D-385] - Canaveral SLC-37B - 06:16-10:25 Late August 27 - SAOCOM-1B, Capella 2 (Sequoia), GNOMES-1 - Falcon 9-092 (B1059.4 L) - Canaveral SLC-40 - 23:19Changes on August 8thChanges on August 17th
Quote from: whitelancer64 on 07/20/2020 11:13 pmQuote from: KTigress on 07/20/2020 02:20 amQuote from: scr00chy on 07/19/2020 12:04 pmQuote from: gongora on 07/19/2020 03:38 am I followed the story on the web: https://bit.ly/EquiposSAOCOMThe article has some good infoQuoteFive days before launch, the Argentine and SpaceX engineers will conduct a second procedural test, which this time will include the launcher and the satellite.Are they saying they're going to do the static fire with payload attached?As far as I know, yes, this is the case. We'll use this test as the last rehearsal before the launch.PS: I was surprised, too. I thought they stopped doing static fires with the payload attached after AMOS-6.They did, but it has technically always been up to the customer to have the payload on or not. NASA allowed the DM-1 Dragon to be on the booster for the static fire. Several (all? I haven't been keeping track) of the Starlink static fires have had the Starlinks on top. DM 1 and 2 were left on the vehicle because it contained an escape system. Starlink is SpaceX owned...it was their choice to leave it intact for the static firing.