From: Eugene Chang <eugene.chang@alum.mit.edu>
To: David Lang <david@lang.hm>, Dave Taht <dave.taht@gmail.com>
Cc: Eugene Chang <eugene.chang@alum.mit.edu>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] some post Starship launch thoughts
Date: Tue, 25 Apr 2023 00:46:57 +0000 [thread overview]
Message-ID: <74321D7F-D914-401B-8AE7-3185D9C2009C@alum.mit.edu> (raw)
In-Reply-To: <p6616q0q-o08q-ss2q-12s6-r87s403q7n26@ynat.uz>
[-- Attachment #1.1: Type: text/plain, Size: 3353 bytes --]
Anything (mass, object) in the path of the engine exhaust will experience thermo-shock and mechanical stress. Both will cause the exhaust diverter or exhaust defuser to have significant wear and short life.
A flame trench suggests a solution. Keep any mass farther away from the engine exhaust. The logical extension of this would be to put the rocket elevated (high) over the ground to have minimal force from the exhaust. I suspect this would be too much distance to be practical.
An alternative could be to launch the rocket over a big pool of water. Please, not over a natural body of water with any living organisms in it. The environmental impact of the thermo-shock would be substantial.
Gene
-----------------------------------
Eugene Chang
eugene.chang@alum.mit.edu
+1-781-799-0233 (in Honolulu)
> On Apr 24, 2023, at 9:16 AM, David Lang via Starlink <starlink@lists.bufferbloat.net> wrote:
>
> On Mon, 24 Apr 2023, Dave Taht via Starlink wrote:
>
>> Everyone wants a water deluge system and flame diverter
>
> and a flame trench...
>
> about 3 months ago they started building water-cooled steel plates to go under the launch pad, but it wasn't ready yet and the testing they didn (static fire at 50% thrust and firing raptors into blocks of concrete at McGregor) made them think that the concrete would be badly eroded by a full power launch, but did not predict nearly the level of damage they saw
>
> this is the probem you run into extrapolating from known data, you can't predict inflection points where the behavior changes significantly
>
> a common answer I've been giving re: flame trench
>
> Both Florida and Texas launch pads started with the ground just a few feet above sea level, so neither one can dig down (unless they want to create a permanent pool under the rocket, which would have all sorts of problems)
>
> In Florida, NASA trucked in a huge amount of dirt and built up a hill, leaving a flame trench that they then lined with concrete and bricks, later adding a ramp to divert the exhaust (and had a lot of problem finding a material that would not wear away too fast). They also had problems with some shuttle launches tearing up the walls of the flame trench.
>
> In Texas, SpaceX instead built stilts and put the rocket on top of that.
>
> As I understand it, the distance from the nozzles to the ground is higher in Texas than in Florida
>
> and the exhaust can get out in 6 direction, not just two.
>
> So if they had put the Starship stack on NASAs mobile launch platform and launched it in Florida, it would have done significantly more damage there, probagly tearing up large chunks of ground around the pad as well (imaging the ground where the crawler goes disappearing)
>
> The raptor engines have a significantly higher ISP than the F-1 that the Saturn 5 had, so it's exhaust is moving about 25% faster, and with double the thrust it's also moving about 60% more mass. These are conditions that have not existed anywhere on earth before this launch (I will note that the shuttle had even higher exhaust velocity from it's main engines, but less overall thrust)
>
> David Lang
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
[-- Attachment #1.2: Type: text/html, Size: 14820 bytes --]
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-04-25 0:47 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 [this message]
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
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=74321D7F-D914-401B-8AE7-3185D9C2009C@alum.mit.edu \
--to=eugene.chang@alum.mit.edu \
--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