Quote from: DanClemmensen on 04/18/2024 09:27 pmThis is equivalent to saying that Kuiper will not make the July 2026 deadline to launch 1616 satellites. That in turn means they must plan to get a waiver from the FCC. But I suspect that just about everybody in the industry, not just SpaceX, will oppose that.I wouldn't be so sure that many others will oppose a short waiver. SpaceX probably will not, because its operations could be impacted the most in the future with any negative precedent.
This is equivalent to saying that Kuiper will not make the July 2026 deadline to launch 1616 satellites. That in turn means they must plan to get a waiver from the FCC. But I suspect that just about everybody in the industry, not just SpaceX, will oppose that.
An interesting scenario is if the threat of no waiver is real, how willing are both Amazon AND SpaceX to try to meet the deadline? Does SpaceX have enough breathing room to help Kuiper and meet their own Starlink deadlines (under the assumption Starship isn't ready in time to ease the load off Falcon 9)?There's a political calculus here, where if Kuiper was that desperate, SpaceX lends a hand, and privately when Starlink is facing their own deadline, they can turn around and say to the FCC we helped OneWeb and Kuiper which directly impacted Starlink's deadline achievement when we didn't have to, so give us a waiver...
Quote from: Asteroza on 04/19/2024 12:25 amAn interesting scenario is if the threat of no waiver is real, how willing are both Amazon AND SpaceX to try to meet the deadline? Does SpaceX have enough breathing room to help Kuiper and meet their own Starlink deadlines (under the assumption Starship isn't ready in time to ease the load off Falcon 9)?There's a political calculus here, where if Kuiper was that desperate, SpaceX lends a hand, and privately when Starlink is facing their own deadline, they can turn around and say to the FCC we helped OneWeb and Kuiper which directly impacted Starlink's deadline achievement when we didn't have to, so give us a waiver...AFAIK, Starlink FCC deadlines are comfortably distant and SpaceX should not have a problem hitting them even with launches just on the Falcon 9.
Quote from: Rebel44 on 04/19/2024 12:32 amQuote from: Asteroza on 04/19/2024 12:25 amAn interesting scenario is if the threat of no waiver is real, how willing are both Amazon AND SpaceX to try to meet the deadline? Does SpaceX have enough breathing room to help Kuiper and meet their own Starlink deadlines (under the assumption Starship isn't ready in time to ease the load off Falcon 9)?There's a political calculus here, where if Kuiper was that desperate, SpaceX lends a hand, and privately when Starlink is facing their own deadline, they can turn around and say to the FCC we helped OneWeb and Kuiper which directly impacted Starlink's deadline achievement when we didn't have to, so give us a waiver...AFAIK, Starlink FCC deadlines are comfortably distant and SpaceX should not have a problem hitting them even with launches just on the Falcon 9.SpaceX will need to get an extension on the V-band deadline. Also, it seems wise for the company not to set precedents that they eventually will come to regret.
Frank Calvelli is reported in the Wapo to be concerned that Vulcan cadence won’t ramp fast enough to meet NSSL requirements.https://www.msn.com/en-us/news/technology/pentagon-worried-its-primary-satellite-launcher-can-t-keep-pace/ar-BB1mjLY3I can’t say I’m surprised at this statement. I’d read this as a reminder that DoD is their primary customer and that they won’t be particularly happy if national security payloads are left waiting while ULA flys Kuiper. I’ll be amazed if Vulcan plays a significant role, if any, in launching Kuiper before 2026.
Quote from: ThatOldJanxSpirit on 05/13/2024 06:45 pmFrank Calvelli is reported in the Wapo to be concerned that Vulcan cadence won’t ramp fast enough to meet NSSL requirements.https://www.msn.com/en-us/news/technology/pentagon-worried-its-primary-satellite-launcher-can-t-keep-pace/ar-BB1mjLY3I can’t say I’m surprised at this statement. I’d read this as a reminder that DoD is their primary customer and that they won’t be particularly happy if national security payloads are left waiting while ULA flys Kuiper. I’ll be amazed if Vulcan plays a significant role, if any, in launching Kuiper before 2026.Vulcan is Kuiper's best bet to put up large numbers of satellites, other than the Atlas V launchers they purchased of course. They must really be betting the FCC and ITU will give them whatever extensions they need.
Quote from: RedLineTrain on 04/19/2024 10:02 pmQuote from: Rebel44 on 04/19/2024 12:32 amQuote from: Asteroza on 04/19/2024 12:25 amAn interesting scenario is if the threat of no waiver is real, how willing are both Amazon AND SpaceX to try to meet the deadline? Does SpaceX have enough breathing room to help Kuiper and meet their own Starlink deadlines (under the assumption Starship isn't ready in time to ease the load off Falcon 9)?There's a political calculus here, where if Kuiper was that desperate, SpaceX lends a hand, and privately when Starlink is facing their own deadline, they can turn around and say to the FCC we helped OneWeb and Kuiper which directly impacted Starlink's deadline achievement when we didn't have to, so give us a waiver...AFAIK, Starlink FCC deadlines are comfortably distant and SpaceX should not have a problem hitting them even with launches just on the Falcon 9.SpaceX will need to get an extension on the V-band deadline. Also, it seems wise for the company not to set precedents that they eventually will come to regret.In March 2023 SpaceX submitted an application to add V-band payload to the second-generation satellites rather than fly phase 2 V-band satellites as originally planned and authorized. And their 50% FCC deadline is in November 2024 with 0 satellites deployed.So, SpaceX is unlikely to need a deadline extension for Starlink. I expect that SpaceX won't oppose Kuiper getting a reasonable (max 2 years) deadline extension if Amazon buys a decent number of launches from SpaceX.
Quote from: Rebel44 on 04/19/2024 10:41 pmQuote from: RedLineTrain on 04/19/2024 10:02 pmQuote from: Rebel44 on 04/19/2024 12:32 amQuote from: Asteroza on 04/19/2024 12:25 amAn interesting scenario is if the threat of no waiver is real, how willing are both Amazon AND SpaceX to try to meet the deadline? Does SpaceX have enough breathing room to help Kuiper and meet their own Starlink deadlines (under the assumption Starship isn't ready in time to ease the load off Falcon 9)?There's a political calculus here, where if Kuiper was that desperate, SpaceX lends a hand, and privately when Starlink is facing their own deadline, they can turn around and say to the FCC we helped OneWeb and Kuiper which directly impacted Starlink's deadline achievement when we didn't have to, so give us a waiver...AFAIK, Starlink FCC deadlines are comfortably distant and SpaceX should not have a problem hitting them even with launches just on the Falcon 9.SpaceX will need to get an extension on the V-band deadline. Also, it seems wise for the company not to set precedents that they eventually will come to regret.In March 2023 SpaceX submitted an application to add V-band payload to the second-generation satellites rather than fly phase 2 V-band satellites as originally planned and authorized. And their 50% FCC deadline is in November 2024 with 0 satellites deployed.So, SpaceX is unlikely to need a deadline extension for Starlink. I expect that SpaceX won't oppose Kuiper getting a reasonable (max 2 years) deadline extension if Amazon buys a decent number of launches from SpaceX.To put a finer point on this, by November 2024, SpaceX must launch 3,750 satellites with V-band packages into its Gen2 constellation (50% of 7,500). We do not know how many V-band packages have been launched to date because it may be that the E-band packages that appear to have been launched on all v2-mini satellites can serve both bands to some extent.Assuming that SpaceX still wants the V-band frequencies on 7,500 satellites, they will need a short deadline extension. That needed extension can be as short as a few months and as long as a couple years, depending on the specs of the Gen2 satellites that it has launched.
Quote from: RedLineTrain on 05/13/2024 08:53 pmQuote from: Rebel44 on 04/19/2024 10:41 pmQuote from: RedLineTrain on 04/19/2024 10:02 pmQuote from: Rebel44 on 04/19/2024 12:32 amQuote from: Asteroza on 04/19/2024 12:25 amAn interesting scenario is if the threat of no waiver is real, how willing are both Amazon AND SpaceX to try to meet the deadline? Does SpaceX have enough breathing room to help Kuiper and meet their own Starlink deadlines (under the assumption Starship isn't ready in time to ease the load off Falcon 9)?There's a political calculus here, where if Kuiper was that desperate, SpaceX lends a hand, and privately when Starlink is facing their own deadline, they can turn around and say to the FCC we helped OneWeb and Kuiper which directly impacted Starlink's deadline achievement when we didn't have to, so give us a waiver...AFAIK, Starlink FCC deadlines are comfortably distant and SpaceX should not have a problem hitting them even with launches just on the Falcon 9.SpaceX will need to get an extension on the V-band deadline. Also, it seems wise for the company not to set precedents that they eventually will come to regret.In March 2023 SpaceX submitted an application to add V-band payload to the second-generation satellites rather than fly phase 2 V-band satellites as originally planned and authorized. And their 50% FCC deadline is in November 2024 with 0 satellites deployed.So, SpaceX is unlikely to need a deadline extension for Starlink. I expect that SpaceX won't oppose Kuiper getting a reasonable (max 2 years) deadline extension if Amazon buys a decent number of launches from SpaceX.To put a finer point on this, by November 2024, SpaceX must launch 3,750 satellites with V-band packages into its Gen2 constellation (50% of 7,500). We do not know how many V-band packages have been launched to date because it may be that the E-band packages that appear to have been launched on all v2-mini satellites can serve both bands to some extent.Assuming that SpaceX still wants the V-band frequencies on 7,500 satellites, they will need a short deadline extension. That needed extension can be as short as a few months and as long as a couple years, depending on the specs of the Gen2 satellites that it has launched.SpaceX has abandoned those V-band satellites and informed the FCC about it"However, the FCC noted that this is not a net increase in approved on-orbit satellites for SpaceX since SpaceX is no longer planning to deploy 7518 V-band satellites at 340 km (210 mi) altitude that had previously been authorized."https://spacenews.com/fcc-grants-partial-approval-for-starlink-second-generation-constellation/So, it is a non-factor regarding Starlink regulatory deadlines and the Gen2 constellation is ahead of time regarding regulatory deadlines.
Quote from: Rebel44 on 05/13/2024 09:03 pmQuote from: RedLineTrain on 05/13/2024 08:53 pmQuote from: Rebel44 on 04/19/2024 10:41 pmQuote from: RedLineTrain on 04/19/2024 10:02 pmQuote from: Rebel44 on 04/19/2024 12:32 amQuote from: Asteroza on 04/19/2024 12:25 amAn interesting scenario is if the threat of no waiver is real, how willing are both Amazon AND SpaceX to try to meet the deadline? Does SpaceX have enough breathing room to help Kuiper and meet their own Starlink deadlines (under the assumption Starship isn't ready in time to ease the load off Falcon 9)?There's a political calculus here, where if Kuiper was that desperate, SpaceX lends a hand, and privately when Starlink is facing their own deadline, they can turn around and say to the FCC we helped OneWeb and Kuiper which directly impacted Starlink's deadline achievement when we didn't have to, so give us a waiver...AFAIK, Starlink FCC deadlines are comfortably distant and SpaceX should not have a problem hitting them even with launches just on the Falcon 9.SpaceX will need to get an extension on the V-band deadline. Also, it seems wise for the company not to set precedents that they eventually will come to regret.In March 2023 SpaceX submitted an application to add V-band payload to the second-generation satellites rather than fly phase 2 V-band satellites as originally planned and authorized. And their 50% FCC deadline is in November 2024 with 0 satellites deployed.So, SpaceX is unlikely to need a deadline extension for Starlink. I expect that SpaceX won't oppose Kuiper getting a reasonable (max 2 years) deadline extension if Amazon buys a decent number of launches from SpaceX.To put a finer point on this, by November 2024, SpaceX must launch 3,750 satellites with V-band packages into its Gen2 constellation (50% of 7,500). We do not know how many V-band packages have been launched to date because it may be that the E-band packages that appear to have been launched on all v2-mini satellites can serve both bands to some extent.Assuming that SpaceX still wants the V-band frequencies on 7,500 satellites, they will need a short deadline extension. That needed extension can be as short as a few months and as long as a couple years, depending on the specs of the Gen2 satellites that it has launched.SpaceX has abandoned those V-band satellites and informed the FCC about it"However, the FCC noted that this is not a net increase in approved on-orbit satellites for SpaceX since SpaceX is no longer planning to deploy 7518 V-band satellites at 340 km (210 mi) altitude that had previously been authorized."https://spacenews.com/fcc-grants-partial-approval-for-starlink-second-generation-constellation/So, it is a non-factor regarding Starlink regulatory deadlines and the Gen2 constellation is ahead of time regarding regulatory deadlines.SpaceX has abandoned its V-band constellation with 7,518 satellites. In its place, the FCC has approved adding a V-band package to 7,500 satellites in SpaceX's Gen2 constellation. However, the original deadline of 50% by November 2024 still holds.
Am I in the wrong thread? There seems to be only SpaceX stuff here.Also as other people pointed out, launch doesn't seem to be the constraint. Even if Amazon had infinite launchers, it doesn't seem like they will be able to build enough satellites in time. Going from a couple satellites a year to ~500 a year seems to be a tall order.
Wrong, the Gen2 license comes with new regulatory deadlines (December 1 2028 for 50% and December 1 2031 for 100%) for completion here is the document: https://docs.fcc.gov/public/attachments/FCC-22-91A1.pdf
Now, the team is shifting focus to the first full-scale launch of Kuiper production satellites, kicking off a regular cadence of launches to deploy the entire 3,232-satellite constellation.
The dedicated, 172,000-square-foot facility will allow Project Kuiper to build up to five satellites per day at peak capacity.
“With our manufacturing facility in Kirkland coming online, we’re able to ramp satellite production ahead of our first launch and move faster in our mission to connect the world,” said Steve Metayer, Project Kuiper’s vice president of production operations.