From: David Lang <david@lang.hm>
To: Nathan Owens <nathan@nathan.io>
Cc: Dave Taht <dave.taht@gmail.com>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] 9 starlink flights planned for june
Date: Wed, 3 May 2023 17:33:13 -0700 (PDT) [thread overview]
Message-ID: <91393r13-o4r5-2n49-43q1-spr79r900q7q@ynat.uz> (raw)
In-Reply-To: <CALjsLJuOHzqTubNHR0k6uf2HCKh_L2Fob7ymbQiOnoKNKdx37Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2134 bytes --]
As of mid-march, there were 6 launches scheduled for 'march', 4 of them
starlink, at least 3 of them slipped.
When they list 'June 30 2023' this may have been from an actual scheduled launch
saying June 30, or it could be from a schedule entry of 'June' or one of 'Q2' or
even 'H1'
In March, some sites were listing SpaceX doing 3 launches from the same launch
pad the same day as a result of this.
But SpaceX has done 29 launches in the first 120 days, so they are a bit behind
schedule for their aim to do 100 launches this year.
rykllan (twitter and patreon) posts infographics showing the progress towards
this goal every few weeks. Last year (when the target was 60 launches) she did
it after every launch, but at the new pace, she's backed off a bit :-)
It's also almost time for the next Bryce Briefing reporting on the worldwide
launch stats for Q1 https://brycetech.com/briefing
David Lang
On Wed, 3 May 2023, Nathan Owens via Starlink wrote:
> FWIW, many of those are likely to slip, there are a number of commercial
> launches in June/July. Depends if they re-shuffle Group 6 ahead of other
> shells.
>
> Upcoming non-starlink launches from the cape:
>
> May:
> - Arabsat 7A (SLC-40)
>
> June:
> - CRS-28 (LC-39A)
> - WorldView Legion 1 & 2 (SLC-40)
> - Axiom 2 (LC-39A), TBD
> - Turksat 6A (39A or 40)
> - Astranis (39A or 40)
> - O3b MPower 5 & 6 (39A or 40)
>
> July:
> - Galaxy 37 (39A or 40)
> - USSF-52 (39A)
> - Euclid (39A or 40)
> - USSF-36 (39A or 40)
> - Thuraya 4-NGS (39A or 40)
>
> August:
> - Crew 7 (39A)
> - Echostar 24 (39A)
>
> Sept:
> - Axiom 3 (39A)
> - Polaris Dawn (39A)
> - Ovzon 3 (39A or 40)
>
> On Wed, May 3, 2023 at 2:19 PM Dave Taht via Starlink <
> starlink@lists.bufferbloat.net> wrote:
>
>> Ḿind boggling.
>>
>> https://twitter.com/VirtuallyNathan/status/1653867999919751169
>>
>>
>> --
>> Podcast:
>> https://www.linkedin.com/feed/update/urn:li:activity:7058793910227111937/
>> Dave Täht CSO, LibreQos
>> _______________________________________________
>> Starlink mailing list
>> Starlink@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/starlink
>>
>
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
Starlink mailing list
Starlink@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/starlink
next prev parent reply other threads:[~2023-05-04 0:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 21:18 Dave Taht
2023-05-03 21:30 ` Nathan Owens
2023-05-04 0:33 ` David Lang [this message]
2023-05-04 1:12 ` Dave Taht
2023-05-04 1:34 ` David Lang
2023-05-04 12:45 ` Dave Taht
2023-05-04 13:21 ` 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=91393r13-o4r5-2n49-43q1-spr79r900q7q@ynat.uz \
--to=david@lang.hm \
--cc=dave.taht@gmail.com \
--cc=nathan@nathan.io \
--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