If Elsbeth III's AIS is still turned off Friday morning, can someone try to get a visual? Because if she's still in port by mid-morning, something is wrong. Should have left ~12 hours ago.Hoping they haven't been shut down by this Coast Guard drydock inspection thing.
Quote from: Kabloona on 06/10/2016 02:38 amIf Elsbeth III's AIS is still turned off Friday morning, can someone try to get a visual? Because if she's still in port by mid-morning, something is wrong. Should have left ~12 hours ago.Hoping they haven't been shut down by this Coast Guard drydock inspection thing.If I remember correctly (a very big if) we've always seen some activity with the support ships a few hours or more before a sortie. I've checked on two sites, and both Elsbeth III and Go Quest haven't sent an AIS signal since the 7th. My guess; either there's a launch delay they haven't announced yet, or OCISLY is mired in paperwork and won't be going out this time. If the latter, and the ABS inspection due dates I posted earlier are accurate, then it's not a scheduled inspection that's the problem, and an inspection has been required for some other reason. Edit to add; I get a distance of 370 nautical miles to the recovery location from Port Canaveral. At a speed of advance of 5 knots, that's 74 hours. Call it 75 due to having to exit the port, and maybe add 5 for setting up and getting OCISLY in position? That's 80 hours. The launch is scheduled (so far as we know) for 10:32 AM EDT, Tuesday, June 14th. It is currently 1:05 AM, June 10th, there right now. I make that as as 105 1/2 hours from now. So, I'll start getting worried if they're still in port this time tomorrow. (or, I messed up the math).
Quote from: CJ on 06/10/2016 03:58 amQuote from: Kabloona on 06/10/2016 02:38 amIf Elsbeth III's AIS is still turned off Friday morning, can someone try to get a visual? Because if she's still in port by mid-morning, something is wrong. Should have left ~12 hours ago.Hoping they haven't been shut down by this Coast Guard drydock inspection thing.If I remember correctly (a very big if) we've always seen some activity with the support ships a few hours or more before a sortie. I've checked on two sites, and both Elsbeth III and Go Quest haven't sent an AIS signal since the 7th. My guess; either there's a launch delay they haven't announced yet, or OCISLY is mired in paperwork and won't be going out this time. If the latter, and the ABS inspection due dates I posted earlier are accurate, then it's not a scheduled inspection that's the problem, and an inspection has been required for some other reason. Edit to add; I get a distance of 370 nautical miles to the recovery location from Port Canaveral. At a speed of advance of 5 knots, that's 74 hours. Call it 75 due to having to exit the port, and maybe add 5 for setting up and getting OCISLY in position? That's 80 hours. The launch is scheduled (so far as we know) for 10:32 AM EDT, Tuesday, June 14th. It is currently 1:05 AM, June 10th, there right now. I make that as as 105 1/2 hours from now. So, I'll start getting worried if they're still in port this time tomorrow. (or, I messed up the math).For SES-9, someone on Reddit had satellite AIS and tracked them the whole way out. It took them almost exactly 4 days, close to 100 hours to reach the LZ. They had left port around 120 hours in advance, so they had almost a full day at the LZ to set up.Maybe they are planning go go faster this time; we'll see.
I'm told by a reliable source that USCG is requesting *drydock* inspections of both barges for permitting.
IMHO, it'd make sense to not cut it too close, just in case they have problems when setting up at the LZ. If they have the time, why not use it for a safety margin? That makes the current lack of motion even more ominous.
I just noticed something on vesslefinder; Go Quest and Go Searcher haven't moved, but their AIS, which had been silent since the 7th, went active - both at the same time, about 15 minutes ago. Still nothing from EIII.
Can I safely assume that in this context the word "requesting" has very much the same meaning as "demanding"?
For SES-9, someone on Reddit had satellite AIS and tracked them the whole way out. It took them almost exactly 4 days, close to 100 hours to reach the LZ. They had left port around 120 hours in advance, so they had almost a full day at the LZ to set up.Maybe they are planning go go faster this time; we'll see.
Quote from: Kabloona on 06/10/2016 09:21 amFor SES-9, someone on Reddit had satellite AIS and tracked them the whole way out. It took them almost exactly 4 days, close to 100 hours to reach the LZ. They had left port around 120 hours in advance, so they had almost a full day at the LZ to set up.Maybe they are planning go go faster this time; we'll see.Hey, maybe we missheard the "Gas&Go" objective and it was in fact "Catch&Go" ! Imagine the sight of the ASDS coming full speed ahead to catch the stage right on the spot ! This would make for some pretty awesome videos.
we don't have as many on the ground resources as in some past times...
Elsbeth III back on AIS, now showing up at OCISLY berth. Game on!Don't know why they're leaving a day later this time. Maybe they've gotten enough experience to know they can tow a little faster. Or the captain had a schedule conflict.
wonder if in the future they could create a loop hole by making the thrustmasters detachable lego elements that get installed at the landing site and removed before they tow back in.
According to ABS records, JRTI (Marmac 303) has a drydock survey due date of June 10th, 2016https://www.eagle.org/safenet/record/record_vesselclassurveystatus?ReferrerApplication=PUBLIC&Service=1For OCISLY (Marmac 304) the due date for the drydock survey is September 15th, 2016https://www.eagle.org/safenet/record/record_vesselclassurveystatus?ReferrerApplication=PUBLIC&Service=1IMHO, both of those dates are uncomfortably close, but worse for JRTI (tomorrow!).
Quote from: Lar on 06/10/2016 01:06 amwe don't have as many on the ground resources as in some past times...I am out of state