From: "Gary E. Miller" <gem@rellim.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] saving ship 20
Date: Sat, 12 Feb 2022 10:36:10 -0800 [thread overview]
Message-ID: <20220212103610.576e44b1@spidey.rellim.com> (raw)
In-Reply-To: <CAA93jw6n4oFfujVN6_O7VB-680TbnSi5k+2xP3jzU=R-_p5EFg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1813 bytes --]
Yo Dave!
On Sat, 12 Feb 2022 09:01:50 -0800
Dave Taht <dave.taht@gmail.com> wrote:
> (is there a good email list for spacex, rather than starlink stuff?
> I'm really not into twitter, reddit, etc)
>
> After watching elon musk's presentation thursday night I was struck by
> the symbolism of ship 20 behind him and wondering why the planned
> flight was to attempt a splashdown at the end.
I agree this is not the place, but if not, where?
> I could think of a more leapfrog-like approach where they left it in
> orbit, to analyze the effects of a longer term stay there, testing
> restarts, or vacuum welding problems on the engines, using as a
> agena-like target for rendezvous maneuvers, trying out repairing or
> replacing various parts...
It is very hard to inspecct a booster in space. One of the big wins for
the returnable rocket has been the after action failure analysis. You
can see all the things the almost screwed the mission, Then improve them
for the next one.
And, as we have seen many times, getting back in one piece is the hardest
part to get right.
> Do they not have enough thrust, even with an empty payload bay, to
> stay up there?
I'm sure they do, but to stay up they would need a course corrction
or two.
> Is there a dummy payload planned? I was thinking of one of bigalow's
> demo inflatable habs, and along that rathole was, why not just cut a
> hole in the side and spray in insulation...
Maybe another Tesla?
RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
gem@rellim.com Tel:+1 541 382 8588
Veritas liberabit vos. -- Quid est veritas?
"If you can't measure it, you can't improve it." - Lord Kelvin
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 851 bytes --]
next prev parent reply other threads:[~2022-02-12 18:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 17:01 Dave Taht
2022-02-12 18:36 ` Gary E. Miller [this message]
2022-02-12 19:42 ` Dave Taht
2022-02-12 22:04 ` David Lang
2022-02-12 23:08 ` Dave Taht
2022-02-12 21:49 ` David Lang
2022-02-12 21:53 ` Nathan Owens
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220212103610.576e44b1@spidey.rellim.com \
--to=gem@rellim.com \
--cc=starlink@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox