From: Michael Richardson <mcr@sandelman.ca>
To: Doc Searls <doc@searls.com>,
"starlink\@lists.bufferbloat.net"
<starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Sunburp kills 40 starlink satellites
Date: Wed, 09 Feb 2022 14:51:02 -0500 [thread overview]
Message-ID: <11609.1644436262@localhost> (raw)
In-Reply-To: <91731AE3-502A-4050-B91A-37B5446493C5@searls.com>
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
Doc Searls <doc@searls.com> wrote:
> Unfortunately, the satellites deployed on Thursday were significantly
> impacted by a geomagnetic storm on Friday. These storms cause the
> atmosphere to warm and atmospheric density at our low deployment
> altitudes to increase. In fact, onboard GPS suggests the escalation
> speed and severity of the storm caused atmospheric drag to increase up
> to 50 percent higher than during previous launches. The Starlink team
> commanded the satellites into a safe-mode where they would fly edge-on
> (like a sheet of paper) to minimize drag—to effectively “take cover
> from the storm”—and continued to work closely with the Space Force’s
> 18th Space Control Squadron and LeoLabs to provide updates on the
> satellites based on ground radars.
I wonder if the GPS data will be interesting/helpful to geomagnetic
scientists.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 398 bytes --]
next prev parent reply other threads:[~2022-02-09 19:51 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 18:50 [Starlink] Starlink for Tonga? Daniel AJ Sokolov
2022-02-07 18:51 ` Nathan Owens
2022-02-07 19:05 ` Christian von der Ropp
2022-02-07 19:06 ` Nathan Owens
2022-02-07 20:38 ` Ulrich Speidel
2022-02-07 20:44 ` Ulrich Speidel
2022-02-10 7:53 ` Ulrich Speidel
2022-02-07 21:18 ` Ben Greear
2022-02-07 21:24 ` David Lang
2022-02-07 21:36 ` Mike Puchol
2022-02-07 22:22 ` Ulrich Speidel
2022-02-07 22:29 ` Mike Puchol
2022-02-07 23:36 ` Ulrich Speidel
2022-02-07 23:47 ` David Lang
2022-02-08 0:20 ` Ulrich Speidel
2022-02-08 1:20 ` David Lang
2022-02-08 4:46 ` Inemesit Affia
2022-02-08 6:25 ` Daniel AJ Sokolov
2022-02-08 7:30 ` Ulrich Speidel
2022-02-08 7:49 ` Daniel AJ Sokolov
2022-02-08 8:22 ` Ulrich Speidel
2022-02-08 8:47 ` Mike Puchol
2022-02-08 8:49 ` Daniel AJ Sokolov
2022-02-08 8:58 ` Mike Puchol
2022-02-08 9:05 ` Daniel AJ Sokolov
2022-02-08 9:10 ` Mike Puchol
2022-02-08 15:22 ` Sebastian Moeller
2022-02-08 10:11 ` Ulrich Speidel
2022-02-08 13:50 ` Christian von der Ropp
2022-02-08 15:28 ` Mike Puchol
2022-02-08 16:25 ` Dave Taht
2022-02-08 18:20 ` Gary E. Miller
2022-02-08 19:12 ` David Lang
2022-02-09 12:09 ` Ulrich Speidel
2022-02-09 19:28 ` [Starlink] Sunburp kills 40 starlink satellites Doc Searls
2022-02-09 19:51 ` Michael Richardson [this message]
2022-02-09 12:58 ` [Starlink] Starlink for Tonga? Ulrich Speidel
2022-02-18 5:04 ` Daniel AJ Sokolov
2022-02-18 7:27 ` Mike Puchol
2022-02-18 9:01 ` Ulrich Speidel
2022-04-19 11:57 ` Mike Puchol
2022-04-19 12:06 ` Dave Taht
2022-04-19 12:43 ` Ulrich Speidel
2022-04-20 1:06 ` Ulrich Speidel
2022-04-20 1:14 ` Jeremy Austin
2022-02-18 10:27 ` Ulrich Speidel
2022-02-18 12:48 ` Rich Brown
2022-02-18 15:43 ` Nathan Owens
2022-02-18 10:29 ` Ulrich Speidel
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=11609.1644436262@localhost \
--to=mcr@sandelman.ca \
--cc=doc@searls.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