From: Dave Taht <dave.taht@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] saving ship 20
Date: Sat, 12 Feb 2022 09:01:50 -0800 [thread overview]
Message-ID: <CAA93jw6n4oFfujVN6_O7VB-680TbnSi5k+2xP3jzU=R-_p5EFg@mail.gmail.com> (raw)
(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.
https://starshipcampaign.com/starship/ship-20/
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...
Do they not have enough thrust, even with an empty payload bay, to
stay up there?
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...
Not even sure if there is a working door...
--
I tried to build a better future, a few times:
https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
Dave Täht CEO, TekLibre, LLC
next reply other threads:[~2022-02-12 17:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 17:01 Dave Taht [this message]
2022-02-12 18:36 ` Gary E. Miller
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='CAA93jw6n4oFfujVN6_O7VB-680TbnSi5k+2xP3jzU=R-_p5EFg@mail.gmail.com' \
--to=dave.taht@gmail.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