News
Watch SpaceX’s last launch and landing of 2020 live [webcast]
Update: Despite no plans for a preflight static fire, SpaceX remains on track to attempt its last launch and landing of 2020 as early as 9 am EST (14:00 UTC), Thursday, December 17th.
After performing a routine preflight wet dress rehearsal (WDR) and booster static fire prior to every launch since September 2016, SpaceX has gradually begun to loosen the requirement for flight-proven rockets in 2020. Instead, if a prior flight or post-flight inspection reveal issues, static fires will serve more as a data-driven diagnostic tool. For flight-proven boosters with a clean bill of health, so to speak, SpaceX appears to be confident enough to skip the procedure on a few internal Starlink launches and the odd customer mission.
Now, despite NROL-108 begin the NRO’s first direct launch contract with SpaceX and first flight on a flight-proven Falcon 9 rocket of any kind, let alone the four-flight booster assigned to support it, the espionage agency apparently has equal faith in SpaceX. Falcon 9 B1059, a new upper stage and payload fairing, and the unspecified NROL-108 payload(s) went vertical at Kennedy Space Center (KSC) Launch Complex 39A on December 16th – far too late for any WDR or static fire testing prior to an early December 17th launch attempt.
The mission will be SpaceX’s 26th and final launch of 2020 and – barring a major surprise – the last orbital US launch of the year. As usual, SpaceX will broadcast the launch live, with coverage beginning around 15 minutes prior to liftoff (8:45 am EST/UTC-5).
The National Reconnaissance Office (NRO) says that SpaceX remains on track to attempt its last Falcon 9 launch and landing of the year after an almost two-month delay.
Originally scheduled to launch as early as October, the secretive orbital espionage agency’s NROL-108 launch plans were quietly revealed in routine communication permission requests filed by SpaceX with the FCC. Unfortunately, those plans came around the same time as a Falcon 9 booster engine issue aborted a SpaceX launch at the last second and forced the company to undergo a quick but extensive anomaly investigation. As it turns out, the Falcon 9 booster assigned to support NROL-108 (B1059) was practically siblings with the three new boosters affected by the investigation.
SpaceX may have had to swap some of the nine Merlin 1D engines on B1059, although a far less likely outcome given that B1059 had successfully completed four launches and landings at that point. Ultimately, while nothing is known for sure, payload-side issues with the NROL-108 satellite(s) are the most likely cause of most of the eight-week delay that followed. Now, confirmed by the NRO on December 14th, SpaceX is scheduled to launch its second mission for the spy agency no earlier than (NET) 9 am to 12 pm EST (14:00-17:00 UTC) on Thursday, December 17th.
For SpaceX, this will be the third time in a single month that a customer has effectively leapfrogged several Falcon 9 booster reuse milestones, once again exhibiting an extreme amount of confidence in the company’s expertise with flight-proven rockets. On December 6th, Falcon 9 booster B1058 lifted off for the fourth time in support of SpaceX’s CRS-21 space station resupply mission for NASA, marking the space agency’s first launch on a twice- or thrice-flown booster.
On December 13th, carrying a large communications satellite for Sirius XM, another Falcon 9 booster lifted off for the seventh time, becoming the first private customer to launch on a five-flight or six-flight SpaceX rocket.
As few as four days after SXM-7, SpaceX is now scheduled to launch the mysterious NROL-108 mission. It will be the first time the NRO has launched a payload on a flight-proven commercial rocket of any kind, as well as its first launch on a two-flight, three-flight, or four-flight booster – by far the biggest numerical leap a SpaceX customer has ever taken. NRO’s first and only SpaceX launch – technically contracted by spacecraft provider Bell Aerospace, not NRO itself – was completed in May 2017.
While less significant, NROL-108 will also be SpaceX’s first US government launch on a four-flight Falcon 9 booster, yet another indication that even its most conservative customers have fully bought into the value and technical viability of reusable rockets.
After launch, Falcon 9 B1059 will flip around and head back towards the Florida coast for a landing at one of SpaceX’s two East Coast Landing Zones. Deploying a minute or so after booster separation, Falcon 9’s two payload fairing halves are expected to splash down some 330 km (~205 mi) downrange, where SpaceX recovery ships GO Search and GO Ms Tree will attempt recovery.
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.
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.
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.
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.
🚨 A Tesla Semi reportedly caught fire, with California Highway Patrol confirming. The Semi was on I-880 SB
An estimated 5,000 to 7,000 semi-truck and large commercial vehicle fires occur on U.S. roadways every year
— TESLARATI (@Teslarati) October 28, 2026
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.
@Tslachan From on of the videos looks like it’s an old Semi (not the refresh version that recently started production) https://t.co/KzwmR2kXow
— Area Under The Curve 🎗️ (@AreaUnderCurve) October 28, 2026
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.
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.”
🚨 Here’s the first look at Tesla’s Emergency Drive Away function in action:
Apparently this driver accidentally enabled it and drove forward; you can see the Supercharger pull with the car.
Tesla said previously this would cost up to $25k if not used properly. https://t.co/B4qQRrsO6B
— TESLARATI (@Teslarati) October 28, 2026
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.
Verizon, AT&T and T-Mobile are trying to shut Starlink out before FCC vote
Tesla Semi catches fire in California: what we know
