Connect with us

News

SpaceX Falcon 9 rocket rolls to launch pad earlier than usual for next Starlink mission

Pictured here in January 2020, Falcon 9 booster B1051 is scheduled to attempt its fourth launch no earlier than April 23rd. (Richard Angle)

Published

on

A SpaceX Falcon 9 rocket has rolled to the launch pad a full week before the company’s next 60-satellite Starlink launch is scheduled, much earlier than usual compared to all recent Starlink missions.

Thrice-flown Falcon 9 booster B1051 will be supporting the internal SpaceX launch, serving as a partial return-to-flight mission after a Falcon 9 rocket suffered its first in-flight engine failure since 2012 less than a month ago. Recently discussed on Teslarati, prime customer NASA – perhaps just a month away from its first astronaut launch on a SpaceX Crew Dragon and Falcon 9 – has to outwardly worry about the impact of Falcon 9’s March 18th engine failure. Most recently, administrator Jim Bridenstine signaled that SpaceX had already effectively determined the failure mode enough for him to state that it’s “not going to impact our commercial crew launch.”

Likely implying that the engine failure was closely related to the fact that Falcon 9 booster B1048 was on its fifth launch, a first for SpaceX, a successful Starlink launch next week would likely alleviate most remaining customer concerns. Delayed a week from April 16th to 23rd, the rocket’s move to the launch pad indicates that SpaceX may be exerting significantly more caution on this particular Starlink launch, a sign that the company is unsurprisingly prioritizing a fully-successful mission over speed.

Like the late Falcon 9 booster B1048, pictured here in March 2020, B1051 is scheduled to perform a static fire test at Pad 39A within the next few days. (Richard Angle)

Excluding delays, recent SpaceX Starlink launches have seen their Falcon 9 rockets roll out to the launch pad and perform their preflight static fire tests just a few days (or less) before liftoff. To achieve that, SpaceX – for the first time since September 2016 – has begun installing payloads (its own Starlink satellites) on top of Falcon 9 before their static fires. Known as Starlink V1 L6 or Starlink-6 for short, that also remains true for this particular mission – SpaceX’s 6th Starlink launch since November 2019 and 7th launch overall.

Easily visible in Spaceflight Now’s live views of Falcon 9’s roll to the launch pad, the rocket already has a payload fairing – presumably full of 60 Starlink satellites – installed atop its second stage. The fact that SpaceX has rolled the fully-integrated Starlink-6 rocket to the launch pad a full week before its planned liftoff is thus at least a little curious.

SpaceX has already launched four Starlink missions in 2020, averaging roughly one launch every three weeks if Starlink-6 is completed next week. (SpaceX)

The presence of a payload fairing effectively rules out an issue with Starlink satellites as the cause of the delay, while it also makes it much less likely – but not impossible – that any bugs were found in Falcon 9’s first or second stages. Were any such issues discovered, it’s hard to imagine that SpaceX would have chosen to roll the fully-integrated rocket to the launch pad, as any hardware issues would almost certainly require a return to the hangar and some level of disassembly.

As such, the reason for the rocket’s relatively early move to the launch pad is a bit of a mystery. Most likely, as briefly noted, SpaceX is simply taking a more cautious approach to this launch as a result of challenges faced in February and March. The use of Pad 39A – normally dedicated to Falcon Heavy and Crew Dragon launches – also raises the stakes a bit, as a vehicle failure on or around the launch pad would inherently result in major delays to NASA’s critical Commercial Crew Program astronaut launches.

Falcon 9 B1051’s fourth launch carries unique importance due to a recent in-flight engine failure. (SpaceX)

Either way, SpaceX’s Starlink-6 mission is set to be uniquely high-profile. According to launch photographer Ben Cooper, Falcon 9 is scheduled to launch no earlier than 3:16 pm EDT (19:16 UTC) on Thursday, April 23rd. Stay tuned for updates as the rocket approaches its static fire test.

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