From: Nathan Owens <nathan@nathan.io>
To: David Lang <david@lang.hm>
Cc: Dave Taht <dave.taht@gmail.com>, starlink@lists.bufferbloat.net
Subject: Re: [Starlink] saving ship 20
Date: Sat, 12 Feb 2022 13:53:00 -0800 [thread overview]
Message-ID: <CALjsLJvYixxES34pz9cV=sOJMp5D=_=sivpptGrB9y03k+r45g@mail.gmail.com> (raw)
In-Reply-To: <p6roq2qs-7opr-66p8-5s90-6ossn416r6q5@ynat.uz>
[-- Attachment #1: Type: text/plain, Size: 1960 bytes --]
The top spot to chat about space stuff is Reddit, probably followed by the
NASASpaceFlight Forums, fwiw.
On Sat, Feb 12, 2022 at 1:49 PM David Lang <david@lang.hm> wrote:
> On Sat, 12 Feb 2022, Dave Taht 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.
>
> they need to test reentry and the heat shield.
>
> > 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?
>
> 'space junk', the powers that be frown on putting stuff in orbit. many
> shuttle
> flights had the delta-v to take the external tanks to orbit, but they
> deliberatly had them burn up instead.
>
> hopefully, once commercial stations become a thing, they will be
> interested in
> accumulating 2nd stages and other things that we currently are deliberatly
> deorbiting.
>
> > 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...
>
> No door at all on ship 20-24. there is a barrel section that has a door
> cut in
> it, but that's it so far.
>
> David Lang
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
[-- Attachment #2: Type: text/html, Size: 2774 bytes --]
prev parent reply other threads:[~2022-02-12 21:53 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
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 [this message]
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='CALjsLJvYixxES34pz9cV=sOJMp5D=_=sivpptGrB9y03k+r45g@mail.gmail.com' \
--to=nathan@nathan.io \
--cc=dave.taht@gmail.com \
--cc=david@lang.hm \
--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