Connect with us

News

SpaceX’s Starbase environmental review suffers third delay

Starbase's orbital launch site; March 2022. (SpaceX)

Published

on

The Federal Aviation Administration (FAA) has announced that the completion of a crucial ‘environmental assessment’ SpaceX needs to begin orbital-class Starship launch attempts out of South Texas has been delayed for the third time.

Official known as a programmatic environmental assessment or PEA, the FAA says it started the process in late June 2021 with the goal of verifying that SpaceX’s Starbase orbital launch site (OLS) was mostly benign before the end of 2021. Compared to a regular EA, the programmatic nature of SpaceX’s Starbase review would theoretically allow the company to start small and gradually expand and add new facilities and capabilities without having to restart the arduous review process for each change.

Along those lines, SpaceX’s first draft PEA requested permission for no more than five full-stack Starship launches per year compared to the maximum of 12 Falcon 9 launches or nine Falcon 9 and three Falcon Heavy launches out of Boca Chica that SpaceX had already received permission for from the FAA in 2014.

Unfortunately, even at the time that the start of the process was announced, completing a full PEA in half a year was already unbelievably optimistic. No comparable review, of which there are effectively none, has been completed anywhere close to that quickly. In the face of substantial local opposition, like in the case of Georgia’s Camden Spaceport, even an FAA environmental review for a relatively small rocket launch facility can make little progress after years of tooth-and-nail fighting.

However, the best possible comparison has always been SpaceX’s own environmental assessment for an almost identical orbital-class Starship launch site at Florida’s Kennedy Space Center. Despite the fact that no untouched ground would be broken and even with the apparent might of NASA behind it, it took the FAA and SpaceX about a full year to complete a Pad 39A EA for up to 24 Starship launches per year. As such, the idea that the FAA would be able to complete a PEA for Boca Chica Starship launches in six months was always almost unimaginable.

It should come as no surprise, then, that nine months after SpaceX and the FAA began their Starbase PEA, they appear to be only marginally closer to completing the review. Days before the original December 31st, 2021 deadline, the FAA announced a delay to February 28th, 2022. On February 14th, the FAA announced a second delay to March 28th. Most recently, on March 25th, the FAA announced a third delay to April 29th.

Advertisement
-

Put simply, the FAA is effectively saying that it is actually further away from completing SpaceX’s South Texas Starship PEA than it was in December 2021. The extraordinarily opaque nature of the process also means that anyone outside of the loop or without internal sources is left to simply guess what is causing those delays or why the FAA keeps pushing the goalposts back just one or two months at a time when it’s unclear that anyone can actually predict when the process will be completed.

Without journalists filing Freedom of Information Act (FOIA) requests, the full extent of public knowledge about what is causing those delays would be the FAA’s scant few statements on the process. The most valuable information provided thus far is that the FAA is “reviewing the Final PEA,” which does seem to imply some degree of progress. Nonetheless, the agency still included a boilerplate statement noting that it’s “completing consultation and coordination with agencies at the local, State, and Federal level,” making it hard to actually say if any progress has been made. In February 2022, the FAA said it was “continuing consultation and coordination with other agencies.”

In December 2021, the FAA stated that it was “continuing consultation and coordination with other agencies at the local, State, and Federal level” while “SpaceX continues to prepare the Final PEA for…FAA review and acceptance.” By using such vague and unspecific language, the FAA makes what little it does say virtually impossible to parse and barely better than nothing. Solely thanks to documents secured through FOIA, we know that the FAA itself may not actually be to blame for most or all of the PEA’s four months of delays.

Instead, the US Department of the Interior (DOI), Fish and Wildlife Services (FWS), and National Park Services (NPS) may be partially responsible through their required coordination with the FAA, which they appear to be taking full advantage of to exert some form of control over the outcome. Bureaucrats are being bureaucratic, in other words.

Outside of email chains and boardrooms, however, it’s no longer clear that completing the PEA and securing an FAA launch license are the limiting factor for the first orbital Starship test flights. SpaceX CEO Elon Musk recently announced that SpaceX is changing the prototypes assigned to the first full-stack launch – likely to Booster 7 and Ship 24. Super Heavy B7 has yet to begin any kind of testing and Starship S24 is still in several pieces, so it’s safe to say that SpaceX’s new pair are months of concerted testing away from launch readiness.

If anything goes wrong during those tests, any significant design issues are discovered, or any damage is caused, it’s entirely possible that what Elon Musk says could take as few as two months will actually take more like four to six. Only time will tell. For now, the FAA likely has a few months before Starship’s South Texas PEA and full-stack launch license truly become the limiting factor for the rocket’s first orbital launch attempt.

Advertisement
-

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

News

Verizon, AT&T and T-Mobile are trying to shut Starlink out before FCC vote

AT&T, Verizon and T-Mobile want 290 MHz cut from an FCC satellite plan before Thursday.

Published

on

By

Starlink D2D direct to device vs Verizon, AT&T (Concept render by Grok)

AT&T, Verizon and T-Mobile are asking the Federal Communications Commission to pull nearly 300 MHz of spectrum out of a proposal that would let satellite companies like SpaceX offer cell service directly to ordinary phones. The request lands one day before the agency votes on it.

The FCC will vote Thursday, October 29, on a notice of proposed rulemaking that would make an additional 482 MHz available for direct to device service, expanding the number of eligible bands from five to 13, according to the FCC fact sheet. It would also scrap the rule requiring a satellite operator to lease spectrum from carriers, replacing it with a certification that the operator has coexistence agreements in place or holds the terrestrial license itself.

That second path matters for SpaceX. As Teslarati reported earlier this month, SpaceX agreed to buy Grain Management’s nationwide 800 MHz portfolio to turn Starlink Mobile into a full US carrier, adding to the spectrum it already bought from EchoStar.

The carriers want two bands removed, 2.5 GHz and 3.45 GHz, which make up 290 MHz of the 482 MHz on the table. Through industry group CTIA, they argued that about 300 million users depend on those bands and that satellite operations in them are not technically feasible. T-Mobile, which calls 2.5 GHz the foundation of its Ultra Capacity 5G network, said in its own filing that satellite interference could wipe out up to 96% of a cell site’s uplink coverage area and cut uplink speeds by 88% to 99%.

Executives from all three carriers met with FCC staff on October 20, and T-Mobile CEO Srini Gopalan met separately with FCC Chairman Brendan Carr. T-Mobile’s role stands out because it is still SpaceX’s US launch partner for Starlink Mobile. The three carriers have also teamed up on their own satellite joint venture to pool spectrum, a move widely seen as a response to Starlink.

Advertisement
-

SpaceX is asking for the opposite. In an October 23 filing after meetings with FCC staff and commissioners’ offices, the company asked regulators to add the 902 to 928 MHz band to the proposal. “Doing so now saves time later,” SpaceX wrote. The company also asked the FCC to modernize interference rules and align satellite deployment requirements with those for terrestrial cell networks, saying the goal is to let satellite and ground networks work together so Americans stay connected wherever they are.

The carriers have not been shy about how they view SpaceX as a competitor. On Verizon’s third quarter earnings call Monday, its chief executive said Starlink Mobile “just can’t compete with a terrestrial network” and estimated SpaceX would need four to six years and $300 billion to $500 billion to build a full US carrier network.

Thursday’s vote will not settle which bands survive. Adopting the notice opens a public comment period, with final rules to come later in the proceeding. The FCC already considered and rejected 2.5 GHz for satellite coverage once, in 2024. SpaceX also is not the only satellite player watching: the FCC approved Amazon’s $11.6 billion acquisition of Globalstar on October 27, giving its planned direct to device fleet its own mobile satellite spectrum.

Continue Reading

News

Tesla Semi catches fire in California: what we know

Published

on

Credit: KTVU

A Tesla Semi caught fire in Hayward, California, which caused both directions of traffic to shut down for hours before being completely reopened early on Wednesday, the California Highway Patrol said.

The fire occurred just after 5:30 local time in Hayward on Tuesday, as the Semi caught fire in the southbound lanes of I-880 before CHP officials made the decision to shut down both lanes of traffic due to potential risks from hazardous chemical smoke.

There were no injuries reported.

The cause of the fire is currently unknown, as neither Tesla nor the CHP have not determined a cause.

However, some images taken before the Semi was completely destroyed by the fire seem to indicate this might have been an older unit, as it appears to be one of the designs that Tesla shipped as part of its pilot program, before revising it and starting mass production just a month ago.

At the time of publication, CHP had not returned our request for a comment for additional details, including the Semi involved and any potential collaboration on an investigation between the CHP and Tesla. We will update this story when we hear back from them.

The southbound lanes were reopened at 3:30 a.m. on Wednesday, with the northbound lanes opening last night a few hours after the fire began. The CHP did state that the lithium batteries were “incredibly difficult to extinguish,” according to NBC Bay Area.

The truck’s driver said that the Semi caught fire, but he did not have an explanation.

An estimated 5,000 to 7,000 semi-truck and large commercial vehicle fires occur on U.S. roadways every year.

Continue Reading

News

Tesla’s ‘Emergency Drive Away’ function gets its first use in the real world

Published

on

Credit: Tesla

Tesla’s launch of the “Emergency Drive Away” function a few months back offered owners a safe option to evacuate an area if they were in reasonable danger. The function finally got its first use in the real world, but it appears it was by mistake.

A video shared by u/Joshalander in the r/TeslaLounge subreddit recorded the instance from his vehicle and said the incident took place in Austin this past weekend during the city’s F1 Race.

“Was charging around 6 AM this past Sunday in Austin before heading to the F1 race and heard a pop. Looked over and saw the new emergency drive-away feature in action. Genuinely felt bad for the dude when he got out and realized what happened, since he looked exhausted and only seemed to half-read the prompts.”

Emergency Drive Away unlatches the Supercharger connector from the vehicle, but still causes damage to both the car and the Supercharger. Tesla has said that it will cost up to $25,000 in repairs to have everything fixed back to normal.

Additionally, the company said that if it were not used in an emergency situation, the driver of the vehicle who activated the Emergency Drive Away feature would be responsible for all repair costs.

Tesla constitutes the following situations as reasonable justifications for activating the feature:

  • You face an immediate threat to your life or personal safety.
  • You must leave the area immediately.
  • Exiting the vehicle is unsafe.
  • Unplugging the charge connector would unreasonably delay your departure or expose you to a risk to your personal safety.

After using the feature, Tesla requires the driver to schedule Service so the car can be inspected.

Continue Reading