From: "Rodney W. Grimes" <starlink@gndrsh.dnsmgr.net>
To: David Lang <david@lang.hm>
Cc: "Rodney W. Grimes" <starlink@gndrsh.dnsmgr.net>,
Dave Taht <dave.taht@gmail.com>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] some post Starship launch thoughts
Date: Thu, 27 Apr 2023 07:09:14 -0700 (PDT) [thread overview]
Message-ID: <202304271409.33RE9EUf099938@gndrsh.dnsmgr.net> (raw)
In-Reply-To: <2o06n7s5-9547-13pn-1659-s509p837o1on@ynat.uz>
> On Wed, 26 Apr 2023, Rodney W. Grimes via Starlink wrote:
>
> > Now that water cooled steel plate, if you treat it like a sacrificial
> > anode in a water heater, ie you expect it to be erroded over time it
> > could get interesting.
>
> They are designing towards hourly launches, so I don't expect it to be planned
> as a wear item. The way it was introduced (prior to the launch) was that even
> steel plate would wear if it wasn't water cooled.
They had best consider that as a wear item. Those steal plates are going
to rust, no mater what they do, and at those temperatures I expect the
surface rust rate to be rather high. Even if you water cool the back
side the exposed surface is going to get very hot, anyone have the
exhaust gas temperatures of starship?
While findin that temperature I found:
Kennedy 39A and 40 did have flame trenches lined with fire bricks, until successive
Shuttle launches blew them out and for some distance. Both flame trenches are now
lined with a thin layer of replaceable fireproof concrete.
So seems NASA has done this science.... I hope SpaceX is paying attention!
That temperature is suppose to be 2810C, steel melts at ~1500C, and
vaporizes at 2860C, I would say they better plan on regular replacement
of those plates, even water cooled.
Its probably time to let this thread die... and wait to see what they
come up with.
--
Rod Grimes rgrimes@freebsd.org
next prev parent reply other threads:[~2023-04-27 14:09 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 14:12 Dave Taht
2023-04-24 15:16 ` Michael Richardson
2023-04-24 15:27 ` Dave Taht
2023-04-24 15:37 ` Michael Richardson
2023-04-24 15:49 ` Nathan Owens
2023-04-24 19:03 ` David Lang
2023-04-24 19:16 ` David Lang
2023-04-25 0:46 ` Eugene Chang
2023-04-25 2:20 ` David Lang
2023-04-25 22:31 ` Bruce Perens
2023-04-25 23:04 ` Eugene Chang
2023-04-25 23:22 ` David Lang
2023-04-25 23:55 ` Eugene Y Chang
2023-04-26 19:14 ` Michael Richardson
2023-04-25 1:01 ` Bruce Perens
2023-04-26 19:29 ` Dave Taht
2023-04-26 20:05 ` Sebastian Moeller
2023-04-26 20:41 ` Rodney W. Grimes
2023-04-26 21:05 ` Eugene Y Chang
2023-04-26 22:15 ` Mark Handley
2023-04-26 22:29 ` [Starlink] Fondag Bruce Perens
2023-04-26 22:32 ` Rodney W. Grimes
2023-04-26 22:35 ` Nathan Owens
2023-04-26 23:09 ` Nathan Owens
2023-04-27 3:42 ` David Lang
2023-04-26 21:10 ` [Starlink] some post Starship launch thoughts Dave Taht
2023-04-26 21:26 ` Eugene Chang
2023-04-26 22:31 ` Rodney W. Grimes
2023-04-26 22:38 ` Bruce Perens
2023-04-26 23:25 ` Eugene Chang
2023-04-27 3:44 ` David Lang
2023-04-27 14:09 ` Rodney W. Grimes [this message]
2023-04-24 16:02 David Fernández
[not found] <mailman.798.1682383621.1222.starlink@lists.bufferbloat.net>
2023-04-25 20:40 ` David P. Reed
2023-04-25 21:31 ` Sauli Kiviranta
2023-04-25 22:37 ` David Lang
2023-05-11 16:24 ` Sauli Kiviranta
2023-04-25 22:33 ` David Lang
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=202304271409.33RE9EUf099938@gndrsh.dnsmgr.net \
--to=starlink@gndrsh.dnsmgr.net \
--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