From: David Lang <david@lang.hm>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: David Lang <david@lang.hm>, starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starship's 4th flight test was magnificent
Date: Mon, 10 Jun 2024 06:37:32 -0700 (PDT) [thread overview]
Message-ID: <o47ro3p5-sor4-o2so-57n5-0o70p297pr7r@ynat.uz> (raw)
In-Reply-To: <41a94256-6aeb-4efa-845f-764dfe83b9b0@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1366 bytes --]
Alexandre Petrescu wrote:
>> Also, during reentry, the plasma tha builds up blocks any radio down to the
>> ground, and with anything other than a starlink, it even blocks radios up
>> to satellites.
>
> I did not know they use plasma to propel that rocket. Actually I dont know
> much about how these things can be propelled, but I know that with these high
> speed objects photos one can see many things like 'aura' or 'glow' or even
> 'glory' in the certain light conditions. If that is 'plasma' then that could
> be it.
it's not propelled by plasma, but as it's reentering, the air can't get out of
the way and gets compressed into plasma. Watch the flight test 3 and 4 videos,
at about the 45 min mark as it gets down below ~120Km you start to see a glow
build up. That is the air being compressed into plasma around the ship.
with the typical small capsules, it wraps around the capsule to completely
encose the capsule and results in zero (or close to it) communications during
the most dangerous part of the reentry.
The combination of the Starship size and the Starlink capability means that
these two flights are the only ones in history where we have a real-time feed
through the hottest parts of the flight. We have recordings from other flights,
but until they slow down, no way to get the data out of the spacecraft.
David Lang
prev parent reply other threads:[~2024-06-10 13:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-09 23:50 Dave Taht
2024-06-10 0:15 ` Ulrich Speidel
2024-06-10 2:22 ` Michael Richardson
2024-06-10 10:51 ` Ulrich Speidel
2024-06-10 12:04 ` David Lang
2024-06-10 12:15 ` Ulrich Speidel
2024-06-10 2:38 ` David Lang
2024-06-10 11:04 ` Ulrich Speidel
2024-06-10 12:06 ` David Lang
2024-06-10 12:21 ` Ulrich Speidel
2024-06-10 8:57 ` Alexandre Petrescu
2024-06-10 9:49 ` David Lang
2024-06-10 13:22 ` Alexandre Petrescu
2024-06-10 13:37 ` David Lang [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=o47ro3p5-sor4-o2so-57n5-0o70p297pr7r@ynat.uz \
--to=david@lang.hm \
--cc=alexandre.petrescu@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