From: David Lang <david@lang.hm>
To: Dave Taht <dave.taht@gmail.com>
Cc: David Lang <david@lang.hm>, Nathan Owens <nathan@nathan.io>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] 9 starlink flights planned for june
Date: Thu, 4 May 2023 06:21:03 -0700 (PDT) [thread overview]
Message-ID: <9s8p4214-637n-o30s-722n-839s88650p18@ynat.uz> (raw)
In-Reply-To: <CAA93jw5EPYnZSn8z6m2T0bR5FHA0je-nyXWGHQ4-9Y6SH_uKxg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4433 bytes --]
Adding SLC-6 will help the pad congestion, we haven't heard of them contracting
for a 4th landing barge yet.
David Lang
On Thu, 4 May 2023, Dave Taht wrote:
> To break the bottlenecks you describe below, it seems like either
> export to countries otherwise attempting their own massive launch
> programs, or leverage of bases the USA has around the world, would be
> needed.
>
> On Wed, May 3, 2023 at 6:34 PM David Lang <david@lang.hm> wrote:
>>
>> On Wed, 3 May 2023, Dave Taht wrote:
>>
>>> Thx as always for ever more links to information. They recently
>>> attempted launch from two pads on nearly the same day, I am wondering
>>> what the turnaround time is for boosters these days, and how much
>>> inventory they have. If they can improve their cycle time, 9/month
>>> seems achievable on the 3 pads they have, aside from conflicts with
>>> other launches.
>>
>> rykllan posts infographics for most launches (not just SpaceX) but for SpaceX
>> launches she shows the history of the booster used, including the turnaround
>> time for each launch
>>
>> https://twitter.com/_rykllan
>>
>> for tonight's launch, the refurb times have been 47, 44, 55, 55 48, 250 days
>> (going back in time)
>>
>> SpaceX just leased SLC-6 at Vandenberg (Shuttle, Delta pad) and has stated that
>> their plan is to set it up to be able to launch the Falcon Heavy and Falcon 9
>>
>> I think their biggest limiting factors are pad availability and landing barge
>> availability.
>>
>>> Random thought - other launch sites long term? This was built to great
>>> fanfare a while back
>>>
>>> https://www.spaceportamerica.com/business/lease-build/
>>
>> Virgin Galactic has had a pause on their flights for a while. I understand that
>> they are soon going to do another employee only flight, but then expect to be
>> able to start carrying paying customers
>>
>>> Also: https://en.wikipedia.org/wiki/Guiana_Space_Centre
>>
>> It's heavily used by the ESA, but with the fallout from the Ukraine war, ESA
>> lost access to Russian rockets that were launched out of there. They are almost
>> out of Ariane 5 rockets to launch from there. Ariane 6 was supposed to fly in
>> 2020, but they are now hoping to launch the first one late this year (or next
>> year)
>>
>>> And: https://en.wikipedia.org/wiki/Kwajalein_Atoll
>>
>> Pegasus is pretty much dead, there was a mission a couple years ago that was
>> carefully tailored to be a match for the Pegasus @$25m launch cost, but SpaceX
>> won the bid and used a dedicated Falcon 9 (it's not public what the winning bid
>> cost, but we can infer from the Pegasus marketing material and their failure to
>> win the bid)
>>
>> I think that's just too far from the ability to generate fuel for any serious
>> launch capacity.
>>
>> David Lang
>>
>>>
>>>
>>>>
>>>> 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
>>>>>>
>>>>> _______________________________________________
>>>> Starlink mailing list
>>>> Starlink@lists.bufferbloat.net
>>>> https://lists.bufferbloat.net/listinfo/starlink
>>>
>>>
>>>
>>>
>
>
>
>
prev parent reply other threads:[~2023-05-04 13:21 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
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 [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=9s8p4214-637n-o30s-722n-839s88650p18@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