Author Topic: FCC NGSO Constellation Processing Rounds (Nov 2016 and later)  (Read 33163 times)

Offline meberbs

  • Senior Member
  • *****
  • Posts: 3089
  • Liked: 3379
  • Likes Given: 778
Re: FCC NGSO Constellation filings (Nov 2016/Mar 2017)
« Reply #20 on: 10/09/2017 07:08 pm »
Public Notice from the FCC on the Ku/Ka band processing round.  It lists all of the constellation filings accepted so far with their number of satellites, orbits, frequencies, and where they will be licensed.  A round of public comments and replies starts on June 26.

They also established a cutoff for additional Ku/Ka band NGSO applications to be filed by July 26.

The V-band filings are being handled separately from the Ku/Ka band filings, so there should be another of these documents eventually for the rest of the constellation filings.
I just went back and looked through this in detail to get a better idea where everything stands.

I noted a few interesting things that I hadn't seen pointed out:
-Kepler is not mentioned in the document, and the link in the first post appears broken, I assume this means that application has been dropped.
-There was a deadline for additional applications for a variety of frequencies on July 26. These frequencies generally cover gaps in the One Web request: 12.75-13.25 GHz, 13.85-14.0 GHz, 18.6-18.8 GHz, 19.3-20.2 GHz and 29.1-29.5 GHz
-19.7 -20.2 GHz is particularly popular with everyone but SpaceX and One Web wanting to use it.
-Of the new frequency sets, Theia, SpaceX, and Boeing each requested some frequencies that have no competition in this grouping (unless there were more applications.)

I am not familiar with the best way to search FCC applications and notices.
Were there any relevant applications for the July 26 deadline?
Any chance someone has seen the comparable notice of acceptance for the V band applications? If the timing of about 6 months after the deadline holds, I would have expected it to appear in September.

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10772
  • US
  • Liked: 14953
  • Likes Given: 6553
Re: FCC NGSO Constellation filings (Nov 2016/Mar 2017)
« Reply #21 on: 10/09/2017 07:17 pm »
Here is a document accepting some of the V-Band applications on August 25.

Offline vaporcobra

Re: FCC NGSO Constellation filings (Nov 2016/Mar 2017)
« Reply #22 on: 10/09/2017 08:06 pm »
Nice find. Makes sense, both the Telesat and Space Norway constellations are minuscule relative to all other applicants.

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10772
  • US
  • Liked: 14953
  • Likes Given: 6553
Re: FCC NGSO Constellation filings (Nov 2016/Mar 2017)
« Reply #23 on: 10/10/2017 03:42 am »
Nice find. Makes sense, both the Telesat and Space Norway constellations are minuscule relative to all other applicants.

The only really big applications are SpaceX, Boeing, OneWeb.  Of the rest, isn't Telesat is the biggest? (roughly twice as big as Iridium)

Offline vaporcobra

Re: FCC NGSO Constellation filings (Nov 2016/Mar 2017)
« Reply #24 on: 10/10/2017 04:03 am »
Nice find. Makes sense, both the Telesat and Space Norway constellations are minuscule relative to all other applicants.

The only really big applications are SpaceX, Boeing, OneWeb.  Of the rest, isn't Telesat is the biggest? (roughly twice as big as Iridium)

I was too lazy to scour through filings, but I believe Telesat's constellation is 117 satellites. Roughly 2x Iridium NEXT, indeed :) Also roughly 6x smaller than the next smallest, OneWeb! Highly doubt those selections are a coincidence, given the FCC patently stating that they did not have the resources to evaluate the larger constellations and would simply pass the baton to the ITU.

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10772
  • US
  • Liked: 14953
  • Likes Given: 6553
Re: FCC NGSO Constellation filings (Nov 2016/Mar 2017)
« Reply #25 on: 11/07/2017 03:00 am »
Quote
[SpaceNews Nov. 6, 2017] FCC grants Telesat LEO market access despite ViaSat protests

Following market approval given to OneWeb in June, the U.S. Federal Communications Commission on Nov. 3 granted global fleet operator Telesat permission to reach the U.S. with a constellation of 117 low-Earth orbit satellites.

...

Canada-based Telesat is the second LEO constellation after OneWeb to receive market access from the United States.

The FCC also granted Space Norway market access Nov. 3 to reach the U.S. with two satellites in non-geostationary elliptical orbits. Both Telesat and ViaSat sought to block Space Norway.

I don't see this on the FCC site yet.

Offline Mike Jones

  • Full Member
  • *
  • Posts: 101
  • Latvia
  • Liked: 34
  • Likes Given: 2
Re: FCC NGSO Constellation filings (Nov 2016/Mar 2017)
« Reply #26 on: 11/07/2017 06:48 pm »
Any news regarding FCC ruling for SpaceX constellation ?

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10772
  • US
  • Liked: 14953
  • Likes Given: 6553
Re: FCC NGSO Constellation filings (Nov 2016/Mar 2017)
« Reply #27 on: 11/07/2017 07:02 pm »
Any news regarding FCC ruling for SpaceX constellation ?

No

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10772
  • US
  • Liked: 14953
  • Likes Given: 6553
Re: FCC NGSO Constellation filings (Nov 2016/Mar 2017)
« Reply #28 on: 02/14/2018 04:46 pm »
Tweet from Ajit Pai:
Quote
If my proposal to grant @SpaceX's application is adopted, it would be the 1st approval given to an American-based company to provide broadband services using a new generation of low-Earth orbit satellites.

The SpaceX application is probably the only serious one for a high speed constellation from an American company (Boeing just wants to find someone else to pay them to build the satellites).
« Last Edit: 02/14/2018 04:47 pm by gongora »

Offline SWGlassPit

  • I break space hardware
  • Full Member
  • ****
  • Posts: 859
  • Liked: 918
  • Likes Given: 144
Re: FCC NGSO Constellation filings (Nov 2016/Mar 2017)
« Reply #29 on: 02/14/2018 06:22 pm »
Paper from AIAA Space 2017

Large Satellite Constellation Orbital Debris Impacts: Case Studies of OneWeb and SpaceX Proposals
https://arc.aiaa.org/doi/pdfplus/10.2514/6.2017-5200

Quote from: Abstract
Recent proposals for large constellations of communications satellites have added to the debate surrounding the long-term impact of large satellite constellations on spectrum regulation and orbital debris propagation.  The many spectrum license applications currently before the Federal Communications Commission for large, non-geostationary satellite constellation systems provide the satellite risk community with a unique opportunity to weigh the promise of these missions against their long-term impact on the orbital debris environment prior to their launch.  The last decade has seen approximately a 60% increase in the total orbital debris object count, and the additional impact of these pending proposals could significantly alter the LEO environment.  Furthermore, regulators should examine these proposals  within the existing space policy framework to identify potential regulatory inefficiencies.  Much of the existing literature focuses on the risk that the orbital environment poses to satellite constellations and distributed spacecraft missions, but the pending constellation requests can serve as case studies for examining the risk that large satellite constellations pose to the orbital environment.  Better understanding the proposed systems will offer insight into the risks that mission managers and regulators may be accepting now on behalf the future space community.  By examining the licensed OneWeb broadband services satellite constellation and the proposed initial deployment of a similar SpaceX system using the NASA Johnson Space Center Orbital Debris Engineering Model software (Version 3) and a small Monte Carlo analysis, we are able to examine potential implications of the proposed missions, as well as the policy decision space that may emerge as these proposals are reviewed over the coming months and years.

I only just now had a chance to look at this paper.  One fatal flaw:
Quote from:
we assume that each spacecraft is capable of withstanding an impact by any orbital debris less than 1 centimeter in diameter and that such a collision results in no change in performance of the spacecraft.

I know of exactly one vehicle -- or rather, one part of one vehicle, for which this statement is true.  A 1-centimeter piece of debris is enormous and would be catastrophic for all but very heavily-shielded vehicles.

Offline Robotbeat

  • Senior Member
  • *****
  • Posts: 39462
  • Minnesota
  • Liked: 25586
  • Likes Given: 12240
Re: FCC NGSO Constellation filings (Nov 2016/Mar 2017)
« Reply #30 on: 04/13/2018 05:01 am »
Where does the 20Gbps bandwidth per Starlink satellite come from, exactly?
Chris  Whoever loves correction loves knowledge, but he who hates reproof is stupid.

To the maximum extent practicable, the Federal Government shall plan missions to accommodate the space transportation services capabilities of United States commercial providers. US law http://goo.gl/YZYNt0

Offline speedevil

  • Senior Member
  • *****
  • Posts: 4406
  • Fife
  • Liked: 2762
  • Likes Given: 3369
Re: FCC NGSO Constellation filings (Nov 2016/Mar 2017)
« Reply #31 on: 04/13/2018 07:41 am »
Quote from:
we assume that each spacecraft is capable of withstanding an impact by any orbital debris less than 1 centimeter in diameter and that such a collision results in no change in performance of the spacecraft.

I know of exactly one vehicle -- or rather, one part of one vehicle, for which this statement is true.  A 1-centimeter piece of debris is enormous and would be catastrophic for all but very heavily-shielded vehicles.
Yes, and no.

If you consider the whole cross-sectional area of the spacecraft, in most of that cross-sectional area, it's going to hit a solar panel and punch clean through.
If the solar panel is appropriately constructed with redundancy, his may cause no meaningful change in performance, most of the time.

Actually shielding from 1cm debris is going to involve extensive, heavy, ISS-like shielding - https://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/20120002584.pdf is 10cm thick, with a 2mm front Al piece, intermediate layers, and then 5mm on the backside.
The mass is less than 10mm thick aluminium, yet shields better than 50mm thick.

(30kg/m^2 for shielding)
« Last Edit: 04/13/2018 07:48 am by speedevil »

Offline jongoff

  • Recovering Rocket Plumber/Space Entrepreneur
  • Senior Member
  • *****
  • Posts: 6915
  • Erie, CO
  • Liked: 4196
  • Likes Given: 1922
Re: FCC NGSO Constellation filings (Nov 2016/Mar 2017)
« Reply #32 on: 04/13/2018 10:08 pm »
Quote from:
we assume that each spacecraft is capable of withstanding an impact by any orbital debris less than 1 centimeter in diameter and that such a collision results in no change in performance of the spacecraft.

I know of exactly one vehicle -- or rather, one part of one vehicle, for which this statement is true.  A 1-centimeter piece of debris is enormous and would be catastrophic for all but very heavily-shielded vehicles.
Yes, and no.

If you consider the whole cross-sectional area of the spacecraft, in most of that cross-sectional area, it's going to hit a solar panel and punch clean through.
If the solar panel is appropriately constructed with redundancy, his may cause no meaningful change in performance, most of the time.

Though a 1cm debris collision with a solar panel is pretty likely to generate additional debris (we are talking about kinetic energy levels comparable to the highest end sniper rifles if my math is right), with at least some of it big enough to be able to inflict significant damage to other satellites.

~Jon

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10772
  • US
  • Liked: 14953
  • Likes Given: 6553
Re: FCC NGSO Constellation filings (Nov 2016/Mar 2017)
« Reply #33 on: 07/25/2019 03:27 am »
ITU is going to discuss implementing deployment milestones for constellations, but the proposals look very lenient.  Right now it's just one satellite within 7 years.  Proposal would add further milestones after that.
https://spacenews.com/megaconstellation-ventures-cautious-about-deployment-milestones/

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10772
  • US
  • Liked: 14953
  • Likes Given: 6553
Re: FCC NGSO Constellation filings (Nov 2016/Mar 2017)
« Reply #34 on: 10/01/2019 06:50 pm »
I guess we never made a standalone thread for Leosat, so I'll put this here.

I mean this news may be interesting - 10 minutes ago I received mail:
//Dear valued LeoSat Partner,  We very much appreciate your interest and commitment to LeoSat and with this letter I would like to update you on the latest developments.
LeoSat as a NewSpace company is confronted with the same challenges of any start-up that is moving along the evolution from vision to reality. Whilst the company maintains its strong vision as a unique solution for B2B data connectivity in LEO, validated by the market and our early investors, we are now facing critical funding issues.  Late last week we had to make the very difficult decision to cancel our early obtained FCC license that required a long term financial commitment equal to that of multiple FTEs. As a startup we could no longer justify carrying the cost this early in the project and we will reapply for this license closer to launch, in parallel to obtaining our licenses in other countries.
//

Starlink will have minus one competitor  and more interest from investors

Space News had an article last week updating their situation, which basically boils down to they haven't been able to raise enough money yet.  Much like a lot of Oneweb's early investors, the big name partners that Leosat found haven't actually been willing to put in much money yet.
[Space News] LeoSat, facing ITU deadline, restarts manufacturing competition, changes funding strategy

I don't see anything in their FCC application yet about the cancellation.  It sounds like they decided to stop maintaining this required surety bond:
Quote
25. IT IS FURTHER ORDERED that this authorization is also subject to the following
requirements:

a. LeoSat must post a surety bond in satisfaction of 47 CFR §§ 25.165(a)(1) & (b) no later
than December 19, 2018 and thereafter maintain on file a surety bond requiring payment in the event of a
default in an amount, at minimum, determined according to the formula set forth in 47 CFR §
25.165(a)(1); and


b. LeoSat must launch 50 percent of the maximum number of proposed space stations, place
them in the assigned orbits, and operate them in accordance with the station authorization no later than
November 19, 2024 and LeoSat must launch the remaining space stations necessary to complete its
authorized service constellation, place them in their assigned orbits, and operate each of them in
accordance with the authorization no later than November 19, 2027. 47 CFR § 25.164(b).

Failure to post and maintain a surety bond will render this grant null and void automatically,
without further Commission action.
Failure to meet the milestone requirements of 47 CFR § 25.164(b)
may result in LeoSat’s authorization being reduced to the number of satellites in use on the milestone
date. Failure to comply with the milestone requirement of 47 CFR § 25.164(b) will also result in
forfeiture of LeoSat’s surety bond. By December 4, 2024, LeoSat must either demonstrate compliance
with its milestone requirement or notify the Commission in writing that the requirement was not met. 47
CFR § 25.164(f).

Attached is their last filing on record (September 16) for the surety bond, which they've been steadily incrementing as little as possible.
Quote
In accordance with Section 25.165 of the Commission’s rules, 47 C.F.R. § 25.165, and paragraph
25.a of the Order and Declaratory Ruling1 granting access to the U.S. market to LeoSat MA, Inc.
(“LeoSat”) for the operation of a non-geostationary satellite system operating in Ka-band
spectrum, LeoSat hereby submits the attached surety bond rider.
The surety bond rider increases the overall bond amount by $20,000 to $1,570,000 which is the
amount required to cover the period through and including September 27, 2019 pursuant to the
formula set forth in Section 25.165(a)(1) of the Commission’s rules.

LeoSat and the surety will execute a further rider to the bond on or before September 27, 2019 to increase the amount of the
bond in accordance with the Commission’s requirements.
« Last Edit: 10/01/2019 06:51 pm by gongora »

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10772
  • US
  • Liked: 14953
  • Likes Given: 6553
Re: FCC NGSO Constellation filings (Nov 2016/Mar 2017)
« Reply #35 on: 11/13/2019 03:25 am »
Peter B. de Selding is reporting the LeoSat is shutting down.

Satellite broadband constellation startup LeoSat ends hunt for investors, shuts down; Thales Ka-band ITU filing at risk
Quote
PARIS — Startup satellite broadband B2B provider LeoSat has suspended operations — which in recent months has mainly consisted of looking for investors — and laid off all its staff in the wake of...

Offline gongora

  • Global Moderator
  • Senior Member
  • *****
  • Posts: 10772
  • US
  • Liked: 14953
  • Likes Given: 6553
Re: FCC NGSO Constellation filings (Nov 2016/Mar 2017/May 2020)
« Reply #36 on: 05/27/2020 01:00 pm »
In 2016, there was a rush of filings for new satellite networks with the FCC after OneWeb’s application triggered a processing round in which all of the non-geostationary (NGSO) satellite communication networks filed in a given time frame would be treated as equals for sharing access to Ku- and Ka-band communications in the US market.

On March 24, 2020 the FCC opened another processing round for Ku- and Ka-band NGSO communication satellites that would be open through May 26.  This round was led by several filings:  OneWeb’s request to expand the size of their constellation from 720 to 1980 satellites (which was withdrawn this week); Amazon’s application for their 3,236 satellite Project Kuiper Ka-band constellation; and New Spectrum Satellite’s application for an initial 15 satellite constellation using elliptical orbits to construct a Content Delivery Network using C-, Ku-, and Ka-bands.  As expected there were multiple new filings on May 26, the last day of the processing round.

SpaceX: FCC / fcc.report
SpaceX, which already has about 12,000 Starlink satellites approved in two LEO constellations, filed for another constellation.  This one is up to 30,000 satellites in a mix of polar and lower inclination orbits ranging from 328 to 614km in altitude.  These satellites will use Ku-, Ka- and E-band.  SpaceX is currently deploying their initial constellation of about 1500 Ku- and Ka-band version 1 satellites, with six launches of 60 satellites completed and another due in early June. 

OneWeb: FCC / fcc.report
OneWeb is a British satellite operator that ran out of money after launching about 70 satellites and is currently in bankruptcy proceedings.  News reports have suggested that the company is unlikely to continue in its current form and the pieces would likely be auctioned off.  They submitted a filing to restructure their first generation constellation and redefine their second generation constellation.  The initial constellation, which is part of the first processing round, would be reduced from 720 satellites to 716, with 588 of those staying in the existing 87.9 degree inclination, and 128 of them changing to a 55 degree inclination.  The second phase, as part of this second processing round, would increase the constellation to 47.844 satellites with a combination of 87.9, 55, and 40 degree inclinations at 1200km.

O3b: FCC / fcc.report
O3b filed for an expansion of their Ka-band network.  O3b currently has twenty satellites in an equatorial MEO (medium earth orbit) at around 8000km altitude, and plans to expand the system with the launch of seven new mPOWER satellites on two SpaceX launches in 2021.  The new filings would add 10 satellites in equatorial MEO, 24 satellites in polar MEO and 36 satellites in a lower SSO (sun-synchronous orbit) at 507 kilometers.  The new satellites would have inter-satellite links to communicate both within their own constellation and with other satellites in GEO.  The lower altitude of the LEO satellites would allow better support of IoT uses.

Telesat: FCC / fcc.report
Canadian operator Telesat, who currently has about a dozen GEO satellites in service, made a filing for two increases in the size of their already approved constellation of 117 LEO satellites.  The first phase, which Telesat would like to be processed as a modification within the first processing round, would add 181 satellites.  The second phase, which is intended to be part of the second processing round, would add another 1373 satellites.  This would bring the total constellation to as many as 1671 satellites in a mix of polar and mid-inclination orbits between 1000 and 1325km in altitude.  Telesat launched a test satellite in January 2018 and lost another in a launch failure.  Since then they have been working through a procurement process for contracts to build the constellation and have said they intend to award those contracts in the second half of 2020.  It will be interesting to see if they actually execute on that plan in the coming months.

Kepler: FCC / fcc.report
Another Canadian operator, Kepler Communications, is building a constellation of cubesats to support IoT and bulk data transmission.  They currently have two prototype cubesats on orbit and are preparing to launch their third prototype.  They have begun building their first generation constellation of 140 nanosats, which will use 575km polar orbits, in-house with launches beginning later this year on SpaceX rideshares.  Kepler filed for an additional constellation of 360 Ku- and Ka-band satellites in 600km altitude polar orbits to serve customers above 55 degrees latitude.

Viasat: FCC / fcc.report
Viasat, who currently operates several GEO satellites and are preparing to start launching their new generation ViaSat-3 GEO satellites in 2021, already has an approved filing for a system of 20 Ka- and V-band satellites in polar MEO orbits at 8700km altitude.  Their new filing proposes changing their system to 288 high-throughput satellites inclined at 45 degrees to the equator at an altitude of 1300km.  This new configuration would allow them to offer service with sub-100ms latency to regions between 60 degrees north and 60 degrees south latitude.  Like Telesat, Viasat has not yet committed to building out their NGSO network but are still in the study phase.

EOS Defense Systems USA: FCC / fcc.report
EOS Defense Systems USA bought the remains of Audacy after that company failed in 2019.  Audacy had planned to use a constellation of 3 Ka- and V-band satellites in MEO to act as a relay between other satellites and ground stations.  The new filing from EOS DS seeks to add additional frequencies to Audacy's previously approved network, as well as adding the ability for user terminals on the ground to communicate over the network, which appears to be targeted mainly at military applications.

Mangata: FCC / fcc.report
Mangata Networks, a newly formed company led by Brian Holz, who has previously held senior positions at O3b and OneWeb, filed for a constellation of 791 Ku-, Ka- and V-band satellites distributed in 27 medium earth orbit (“MEO”) planes with inclinations between 45-52.5 degrees and 32 highly elliptical orbit(“HEO”) planes with inclinations of 63.4 degrees.  Mangata’s satellites are being registered through the U.K.

New Spectrum Satellite: FCC / fcc.report
New Spectrum Satellite amended their application for a 15 satellite constellation using an interesting setup where the satellite planes rotate in such a way as to give a semi-geosynchronous effect to the constellation.  These orbits are at 1,125 x 26,679km altitude and 63.4 degrees inclination.  They also dropped the C-band frequencies from their application.

Of the companies in the earlier processing round, there have been several failures but many of the companies are still in various stages of planning or deploying their networks.  In addition to those already mentioned above, here are some other status updates from the previous processing round:  Space Norway's two satellites in highly elliptical orbits for polar coverage are under construction and due to be launched in late 2022; LeoSat shut down after they were unable to raise funding for their constellation based on an ITU filing from Thales Alenia; Boeing withdrew most of their filings, which were likely a fishing expedition to try and find a customer to pay Boeing to build the constellation, much like Thales did with LeoSat;  Theia seems to still be quietly working on their constellation; there has been little news of Karousel.

Constructing and running these satellite networks is an expensive and time-consuming process that few companies manage to successfully complete.  Also, while government and business users may be able to afford expensive phased-array terminals or ground stations with multiple parabolic antennas tracking the satellites, there are still challenges to overcome with the production of low-cost and easy-to-use terminals for consumer applications to communicate with these LEO networks.  We will watch in the coming years to see which, if any, of these newly proposed constellations come to fruition.

Amazon Kuiper (filed previously): FCC / fcc.report
« Last Edit: 05/30/2021 04:15 pm by gongora »

Offline Rondaz

  • Senior Member
  • *****
  • Posts: 27056
  • Liked: 5301
  • Likes Given: 169
Re: Starlink : General Discussion - Thread 2
« Reply #37 on: 05/27/2020 01:13 pm »
.@OneWeb, @KeplerComms, @SpaceX & @Telesat modify filings in 2nd @FCC NGSO processing round. SES_Satellites adds 36 LEOs @ 507km + 34 MEOs to O3b mPower. @ViasatInc replaces 20 filed MEOs by 288 LEOs. Mangata Networks led by OneWeb's ex-CEO files for MEO constellation of 791 sats


https://twitter.com/Megaconstellati/status/1265610801718722561

Offline Rondaz

  • Senior Member
  • *****
  • Posts: 27056
  • Liked: 5301
  • Likes Given: 169
Re: Re: Starlink : General Discussion - Thread 2
« Reply #38 on: 05/27/2020 01:14 pm »

Offline RedLineTrain

  • Senior Member
  • *****
  • Posts: 2844
  • Liked: 2718
  • Likes Given: 11183
Re: FCC NGSO Constellation filings (Nov 2016/Mar 2017/May 2020)
« Reply #39 on: 05/27/2020 01:16 pm »
Was this round only for constellations that already had some form of approval?  If not, I'm surprised that Kuiper didn't put in for a constellation to supplement their earlier request (in case the FCC doesn't add it to the earlier round).

Tags:
 

Advertisement NovaTech
Advertisement
Advertisement Margaritaville Beach Resort South Padre Island
Advertisement Brady Kenniston
Advertisement NextSpaceflight
Advertisement Nathan Barker Photography
0