News
SpaceX Cargo Dragon spacecraft arrives at space station on second to last mission
SpaceX’s Cargo Dragon has successfully rendezvoused with the International Space Station (ISS) as part of NASA’s CRS-19 resupply mission, marking what is almost certainly the spacecraft’s second to last orbital launch.
On December 5th, new Falcon 9 booster B1059 lifted off from SpaceX’s LC-40 Cape Canaveral Air Force Station (CCAFS) launch pad with a fresh upper stage and twice flown Cargo Dragon capsule C106 atop it. A little over nine minutes after launch, B1059 prepared to be robotically secured on drone ship Of Course I Still Love You (OCISLY) while Cargo Dragon – now in orbit – separated from Falcon 9’s upper stage and headed on its merry way.
Cargo Dragon’s 20th orbital mission and 19th trip to the ISS, CRS-19’s twice-flown spacecraft commanded the deployment of its two solar arrays, primed its Draco maneuvering thrusters, and opened up its Guidance, Navigation, and Control (GNC) bay. Using star trackers, inertial measurement devices, and lasers, Dragon then proceeded to precisely deliver itself to the ‘door’ of the space station before gradually approaching.
Astronauts aboard the ISS then manually guided Canadarm2 – a massive robotic arm externally attached to the space station – towards Cargo Dragon as it used its thrusters to essentially hover in place, ultimately grabbing the spacecraft with a sort of mechanical hand. At that point, Dragon effectively became a part of the ISS and astronauts monitored the subsequent (and mostly automated) process of using Canadarm2 to fully berth spacecraft with the station.
After berthing, astronauts are able to equalize the pressure between the ISS and visiting spacecraft and open the hatch, gaining access to whatever cargo it was loaded with prior to launch. Alternatively, visiting vehicles can also dock with the International Space Station, a process controlled entirely by the arriving spacecraft, a bit like berthing but with almost all of the risk on its shoulders. All Russian spacecraft currently use this method, as do Boeing’s Starliner and SpaceX’s Crew Dragon.
As it turns out, CRS-19 – partially hinted at in the name – is the second to last launch of SpaceX’s Dragon 1 (Cargo Dragon), which become the first commercial spacecraft capable of reentering Earth’s atmosphere in 2010 and rendezvousing with a space station in 2012. Five months later, SpaceX launched CRS-1 – its first operational resupply mission – and the rest is (more or less) history.
In the seven years since CRS-1, Cargo Dragon – including CRS-19 – has now flown 18 successful space station resupply missions and delivered more than 90,000 lb (50,000 kg) to its ever-changing crew of astronauts. Cargo Dragon has undergone at least two significant upgrades and suffered its fair share of mishaps, but has still successfully completed its mission every time it reached orbit.
NASA’s CRS1 SpaceX contract ultimately called for a total of 20 Cargo Dragon missions to the ISS, although more could technically be added retroactively if both entities were to decide they were needed. Currently, the plan is for CRS-20 – Cargo Dragon’s next launch – to be the spacecraft’s last orbital mission and is scheduled no earlier than March 2020.
After CRS-20, SpaceX – via its subsequent CRS2 NASA contract – means to introduce a version of Crew Dragon (Dragon 2) modified for cargo-only missions, optimally taking flight-proven Crew capsules and reusing them as Cargo Dragon 2s.
SpaceX recently revealed that the first Cargo Dragon 2 spacecraft will unexpectedly not feature Crew Dragon’s complex SuperDraco abort system, a feature that has recently created several roadblocks. However, this dramatically simplifies Dragon 2 and means that SpaceX is still quite confident that the upgraded cargo spacecraft will be ready for its launch debut next year.
Known as CRS-21, that mission will see SpaceX’s CRS launches move from LC-40 to Kennedy Space Center’s LC-39A pad in order to enable extremely late and convenient cargo-loading via Pad 39A’s Crew Access Arm (CAA), to be primarily used by astronauts boarding Crew Dragon. Similarly, Cargo Dragon 2 will dock with the ISS instead of using Dragon’s current berthing route, nominally requiring less hands-on astronaut time for each resupply mission.
Cargo Dragon will be missed but will forever remain a major piece of commercial spaceflight history. Dragon 2 will likely toe the line for the first half of the next decade, but SpaceX ultimately wants to get its generation Starship launch vehicle online as soon as possible – a feat that will make all Falcon and Dragon vehicles redundant if things go as planned.
Check out Teslarati’s newsletters for prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket launch and recovery processes.
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
