Author Topic: SpaceX F9 : Starlink 6 (v1.0 L5) : Mar. 18, 2020 - Discussion  (Read 129281 times)

Online FutureSpaceTourist

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 50695
  • UK
    • Plan 28
  • Liked: 85214
  • Likes Given: 38173
https://twitter.com/abernnyc/status/1239349655613386753

Quote
Really dug this shot of @ChrisG_NSF and @julia_bergeron hard at work covering today's attempted @SpaceX launch

Offline marsbase

  • Full Member
  • ****
  • Posts: 443
  • North Carolina
  • Liked: 490
  • Likes Given: 101
Re: SpaceX F9 : Starlink 6 (v1.0 L5) : March 18, 2020 - Updates
« Reply #141 on: 03/17/2020 06:53 pm »
The updated press kit and new webcast.


Note that once again the time on the webcast "front page" in not correct.  Launch time is 08:16 EDT, 12:16 UTC.  It would also be 05:16 PDT. The time shown on the webcast page is 11:16 which makes no sense at all.

Offline drnscr

  • Full Member
  • *
  • Posts: 112
  • Liked: 128
  • Likes Given: 38
What, if anyone has heard, was the mitigation for the out of family reading?

Offline AndrewRG10

  • Full Member
  • **
  • Posts: 206
  • Brisbane, Australia
  • Liked: 364
  • Likes Given: 290
What, if anyone has heard, was the mitigation for the out of family reading?

I would say close to 80% of all aborts are due to sensor issues that need to be turned off and on. The remainder of the issues require a couple of weeks to replace faulty parts or it's a fuel problem where they just make sure fuel is cold enough.
We haven't heard official word but I think it's pretty likely the failure just needed a sensor turned off and on.

Offline ejb749

What, if anyone has heard, was the mitigation for the out of family reading?

I would say close to 80% of all aborts are due to sensor issues that need to be turned off and on. The remainder of the issues require a couple of weeks to replace faulty parts or it's a fuel problem where they just make sure fuel is cold enough.
We haven't heard official word but I think it's pretty likely the failure just needed a sensor turned off and on.

The fact that tomorrow is launch, and not a static fire seems to indicate it was a sensor problem, not an engine problem.

Offline mrhuggy

  • Full Member
  • ****
  • Posts: 667
  • East Yorkshire, UK
  • Liked: 441
  • Likes Given: 16
Just after the Entry Burn you could see the 1st stage oscillating back and forth and no word on landing.

Offline DavidH

  • Full Member
  • *
  • Posts: 144
  • Boulder, CO
  • Liked: 82
  • Likes Given: 145
At 6:40 in the launch sequence the first stage seemed to fly by a large object.

Sent from my Pixel using Tapatalk

TL;DR
Keep your posts short if you want them to be read.

Offline Kaputnik

  • Extreme Veteran
  • Senior Member
  • *****
  • Posts: 3091
  • Liked: 727
  • Likes Given: 840
So at this moment in time it looks like the booster might not have made it back to the drone ship.
The important thing, though, is that the 5th reflight did its job- as did the fairing reuse.
"I don't care what anything was DESIGNED to do, I care about what it CAN do"- Gene Kranz

Offline AndrewRG10

  • Full Member
  • **
  • Posts: 206
  • Brisbane, Australia
  • Liked: 364
  • Likes Given: 290
Recovery weather looks good. 1.5 metre waves and minimal winds and minimal gusts at altitudes below 20,000ft. Very good for the fairings. Looking like perfect launch, just got to hope it isn't jinxed and it fails on launch or landing or a parachute fails on the fairing.

Called it, you can never have a perfect launch (and landing) weather and conditions in spaceflight.

Let's hope it's a sensor issue and can recycle tomorrow.

Not to speculate but yep I was expecting that. I felt the last one would fail too

Offline ugordan

  • Senior Member
  • *****
  • Posts: 8560
    • My mainly Cassini image gallery
  • Liked: 3628
  • Likes Given: 775
Stage 1 looked wobbly after entry burn and no confirmation of landing burn.

Yeah, even the entry burn looked a bit sideways like the downrange or crossrange impact point distance was bigger than expected. Then the fairly aggressive grid fin steering.

My money's on downrange distance difference as that's going to be dependent actual vehicle ascent performance whereas it can keep inside the crossrange ascent corridor pretty well.
« Last Edit: 03/18/2020 11:33 am by ugordan »

Offline ZachF

  • Full Member
  • ****
  • Posts: 1648
  • Immensely complex & high risk
  • NH, USA, Earth
  • Liked: 2679
  • Likes Given: 537
We have two booster recover failures now (out of two) on the new Starlink delivery profile... perhaps it's time to ditch it?
artist, so take opinions expressed above with a well-rendered grain of salt...
https://www.instagram.com/artzf/

Offline toruonu

It may have been a blip, but just before MECO I thought I noticed a buff of vapor  from the engine region that seemed out of nominal, but the engines kept going so probably nothing.

Offline haywoodfloyd

  • Veteran
  • Full Member
  • ****
  • Posts: 664
  • Ottawa, Ontario CANADA
  • Liked: 199
  • Likes Given: 23
Might be a little early to make that call.
Last attempt failure was due to off-nominal or rather higher than expected winds.

Offline whitelancer64

We have two booster recover failures now (out of two) on the new Starlink delivery profile... perhaps it's time to ditch it?

We don't know the cause of this landing failure. Way too soon to say that.
"One bit of advice: it is important to view knowledge as sort of a semantic tree -- make sure you understand the fundamental principles, ie the trunk and big branches, before you get into the leaves/details or there is nothing for them to hang on to." - Elon Musk
"There are lies, damned lies, and launch schedules." - Larry J

Offline eeergo

Clearly something coming off the engine section. Maybe the liftoff abort was something to worry about.
« Last Edit: 03/18/2020 11:40 am by eeergo »
-DaviD-

Offline Glorin

  • Member
  • Posts: 32
  • Liked: 86
  • Likes Given: 376
It may have been a blip, but just before MECO I thought I noticed a buff of vapor  from the engine region that seemed out of nominal, but the engines kept going so probably nothing.

No, I saw that too and it didn’t look very normal. :)

Edit: T+2:21 to be exact-ish.
« Last Edit: 03/18/2020 11:39 am by Glorin »

Offline theonlyspace

  • Full Member
  • ****
  • Posts: 555
  • Rocketeer
  • AEAI Space Center, USA
  • Liked: 145
  • Likes Given: 844
Re: SpaceX F9 : Starlink 6 (v1.0 L5) : March 18, 2020 - Updates
« Reply #156 on: 03/18/2020 11:38 am »
To bad about the booster loss

Offline mdo

  • Full Member
  • *
  • Posts: 173
  • Liked: 6
  • Likes Given: 5
At T+6:37 an object seemed to separate from the first stage. Maybe just an ice particle?
« Last Edit: 03/18/2020 12:30 pm by mdo »

Offline ugordan

  • Senior Member
  • *****
  • Posts: 8560
    • My mainly Cassini image gallery
  • Liked: 3628
  • Likes Given: 775
Has there ever been such a big difference between S2 groundtrack and S1 groundtrack? S2 flew quite a bit north from ASDS, it's unclear if S1 was heading precisely toward it or slightly north as well?

Offline su27k

  • Senior Member
  • *****
  • Posts: 6414
  • Liked: 9104
  • Likes Given: 885
It may have been a blip, but just before MECO I thought I noticed a buff of vapor  from the engine region that seemed out of nominal, but the engines kept going so probably nothing.

No, I saw that too and it didn’t look very normal. :)

Edit: T+2:21 to be exact-ish.

Some kind of energetic event? An engine gave out?

Tags:
 

Advertisement NovaTech
Advertisement Northrop Grumman
Advertisement
Advertisement Margaritaville Beach Resort South Padre Island
Advertisement Brady Kenniston
Advertisement NextSpaceflight
Advertisement Nathan Barker Photography
0