News
SpaceX’s NASA astronaut launch debut jumps its place in line, now up next
According to NASASpaceflight.com reporter Michael Baylor, SpaceX’s Starlink-7 satellite launch has been indefinitely delayed due to drone ship constraints, meaning that the company’s Crew Dragon astronaut launch is now up next.
As a result, SpaceX’s next orbital launch has been delayed by at least eight days. In return, however, that launch will arguably be the most important in the company’s 18-year history, (hopefully) marking the biggest step by far SpaceX has taken towards its main goals of democratizing spaceflight and enabling the sustainable, permanent settlement of Mars. Known as Demonstration Mission 2 (Demo-2), it will simultaneously be the first crewed launch under NASA’s Commercial Crew Program (CCP) and SpaceX’s first astronaut launch ever and is scheduled to lift off no earlier than (NET) 4:33 pm EDT (20:33 UTC), May 27th.
Formerly scheduled to launch no earlier than (NET) May 7th, 17th, 18th, and 19th after a number of technical and weather-related delays, SpaceX’s 8th 60-satellite Starlink launch has now been delayed until sometime after Crew Dragon’s late-May inaugural astronaut launch. According to NASASpaceflight and speculated about in-depth on unofficial forums in the days prior, the schedule swap decision was made due to constraints in SpaceX’s drone ship. While simple on the face of things, the change does reveal a bit of the hidden strategy behind SpaceX’s management of both its rocket fleet and the ships that recover them.
Compounded by multiple largely unrelated delays, including weather in the planned booster and fairing landing zones, the Starlink-7/Demo-2 launch swap was caused by the simple fact that SpaceX only has one operational drone ship on the East Coast. The company coincidentally began sea trials with a second drone ship the very same day that Of Course I Still Love You (OCISLY) headed out to sea to catch Starlink-7’s Falcon 9 booster. However, that second ship has been extensively upgraded and will likely take several weeks of sea trials before it can be declared ready for its first East Coast rocket recovery attempt.
For each drone ship booster landing, it takes at least a week for the ship to be towed several hundred miles downrange to the recovery zone and at least as long to return to port. Add in the time required to safe and secure a landed Falcon 9 or Heavy booster, navigate sea states to prevent damage to – or the outright loss of – that booster, and the work needed to safely lift it off the drone ship’s deck onto dry land and it can easily be 9-10 days before a drone ship is ready for another landing.
At the same time, SpaceX’s turnaround record is about eight days between booster landings. Had SpaceX persevered and attempted to launch Starlink-7 on May 19th and Crew Dragon’s inaugural astronaut launch on May 27th, it’s possible that things would have worked out, with both booster landings occurring on schedule on the same drone ship. However, given just how much of a priority Crew Dragon Demo-2 is compared to an internal Starlink launch and a tropical storm threatening to delay Starlink-7’s launch and landing even further, SpaceX clearly decided that it just wasn’t worth the risk.
Given the extraordinary importance of Demo-2, set to be the first time the United States has launched its own astronauts into orbit in almost nine years, it’s not exactly surprising that SpaceX has chosen conservatism this time around and prioritized its inaugural NASA astronaut launch. According to Spaceflight Now, the Crew Dragon capsule assigned to SpaceX’s inaugural NASA astronaut launch – pictured above – actually joined the new Falcon 9 rocket that will launch it at Pad 39A on May 15th. Now fully fueled with liquid hydrazine and nitrogen tetroxide, the spacecraft could be mated with Falcon 9’s upper stage at any moment (if it hasn’t been already).
Once fully assembled, Falcon 9 booster B1058, a new Falcon 9 upper stage, Crew Dragon capsule C206, and an expendable trunk section will be rolled horizontally out to Kennedy Space Center (KSC) Pad 39A to perform a crucial pre-launch static fire test. Rollout and static fire operations could begin at any point within the next few days. It remains to be seen whether drone ship OCISLY will remain in the Atlantic Ocean or head back to Port Canaveral before departing again to catch booster B1058.
Elon Musk
Tesla Roadster is ‘sorcery and magic’ and might be worth the wait, Uber founder says
Perhaps the wait will be worth it, especially according to Uber founder Travis Kalanick, who recently teased the Roadster’s potential capabilities based on what he has heard from internal Tesla sources.
Tesla is planning to unveil the Roadster in late April after years of waiting. But the wait might be worth it, according to Travis Kalanick, the founder of Uber, who recently shed some light on his expectations for the all-electric supercar.
We all know the Roadster is supposed to have some serious capability. CEO Elon Musk has said on numerous occasions that the Roadster will be unlike anything else ever produced. It might go from 0-60 MPH in about a second, it might hover, it might have SpaceX cold gas thrusters.
However, the constant delays in the Roadster program and its unveiling event continue to send Tesla fans into confusion because they’re just not sure when, or if, they’ll ever see the finished product.
Perhaps the wait will be worth it, especially according to Uber founder Travis Kalanick, who recently teased the Roadster’s potential capabilities based on what he has heard from internal Tesla sources.
Kalanick said on X:
When I’ve run into people who are in the know, I inquire, they tell me nothing, but their eyebrows raise and their eyes widen in a way that can only mean something of sorcery and magic is coming…
— travis kalanick (@travisk) March 17, 2026
Musk has said this vehicle is not going to be geared for safety, and that, “If safety is your number one goal, do not buy the Roadster.”
There has been so much hype regarding the Roadster that it is hard to believe the company could not come through on some kind of crazy features for the vehicle.
However, the latest delay that Tesla put on the unveiling event is definitely eye-opening, especially considering it is the latest in a series of pushbacks the company has put on the vehicle for the past several years.
Tesla has made several jumps in the Roadster project over the past few months, as it has ramped up hiring for the vehicle and also applied for a patent for a new seat design.
The car has been a back-burner project for Tesla, as it has been focusing primarily on autonomy and the rollout of Robotaxi and Cybercab. Additionally, its other vehicle projects, like the Model 3 and Model Y refreshes, took precedence.
Tesla still plans to unveil the Roadster next month, so we can hope the company can stick to this timeframe.
Cybertruck
Elon Musk clarifies viral Tesla Cybertruck accident with driver logs
Musk has come out to say that the driver logs have already shown that the driver “disengaged Autopilot four seconds before crashing,” in a post on X.
Tesla CEO Elon Musk has clarified some details regarding the viral Tesla Cybertruck accident with company driver logs, which show various metrics at the time of an incident.
The logs have been used in the past to pull responsibility off of Tesla when the automaker’s Full Self-Driving (Supervised) or Autopilot platforms are blamed for a collision or accident. It appears this will be no different.
On Tuesday, a video of a Cybertruck crashing into an overpass barrier in August 2025 was shared by Fox Business in a story that reported a woman was suing the automaker for $1 million in a liability and negligence case.
In the suit, Justine Saint Amour said that, “Something terrifying happened, without warning, the vehicle attempted to drive straight off an overpass.” Her attorney, Bob Hilliard, said Amour “tried to take control, but crashed into the barrier and was seriously injured (mostly her shoulder, neck, and back).”
The Tesla Model Y is leading China’s electric SUV segment by a wide margin
Tesla vehicle crashes are widely popular to report by mainstream media outlets because of the sensationalism of the event. Oftentimes, these outlets will include Tesla in the headline, especially because it will pique the interest of the masses, as most who read the story are waiting to see the claim that Autopilot or Full Self-Driving was the culprit of the accident.
However, Tesla has access to the logs of every vehicle in its fleet, which will show the various metrics, like whether either FSD or Autopilot was active, if the accelerator was pressed, the speed, and other important factors.
Musk has come out to say that the driver logs have already shown that the driver “disengaged Autopilot four seconds before crashing,” in a post on X.
Logs show driver disengaged Autopilot four seconds before crashing
— Elon Musk (@elonmusk) March 18, 2026
If the logs do show this, which Tesla will likely have to prove in court, the real question would be why did the Amour disengage the suite?
Tesla’s Full Self-Driving suite is still not fully autonomous, meaning the driver cannot pull attention away from the road and must be ready to take over the vehicle at all times.
It will be interesting to see how this particular case pans out, especially considering the clip that was released by the law firm starts at about four seconds before the collision. Tesla logs have dispelled media reports in the past that have accused the company’s suite of being responsible for an accident, so there will be some major attention on what is proven in this particular case.
News
Tesla Robotaxi appears to be heading to a new U.S. city
Things are expanding for Robotaxi, but the big sign that it is really moving along greatly will be with the expansion to a new city. Tesla has not gone outside of Austin or the Bay Area as of yet, and launching in a new city will be a great indicator of progress.
Tesla Robotaxi appears to be heading to a new U.S. city, and although the company has revealed plans to launch in six new metros this year, it has yet to establish a new location outside of Austin and the Bay Area of California, where it has operated since last Summer.
A lot full of Model Y vehicles was spotted in Henderson, a town just north of Las Vegas, but there seems to be more than just this hint indicating that the Sin City will be the next location to offer potentially driverless rides in a Tesla using its Full Self-Driving suite.
These Model Ys are not your typical vehicles, as they are fitted with hardware that is only on Robotaxis: a rear camera washer is the dead giveaway:
🚨 These rear camera washers are only present on Robotaxi vehicles
Maybe Las Vegas is the next city to get the Robotaxi suite 😀 https://t.co/my3da5L4zc pic.twitter.com/jYFQuX1j2E
— TESLARATI (@Teslarati) March 17, 2026
The photos and video of the lot were taken by TheZacher on X, who spotted the Model Y fleet in the Henderson parking lot.
The rear camera washer is the main piece of evidence here that indicates Tesla could be looking to expand Robotaxi to Las Vegas, a major ride-hailing hot spot, as it is one of the biggest tourist attractions in the United States. Ride-sharing is a major industry in Vegas, especially for those who are staying off the Strip.
Tesla has also been extremely transparent that Vegas is on its radar for the Robotaxi fleet, as it revealed last year that it was one of five new U.S. cities that it planned to launch the ride-hailing service in this year.
Tesla confirms Robotaxi is heading to five new cities in the U.S.
The others were Phoenix, Dallas, Houston, and Miami.
Things are expanding for Robotaxi, but the big sign that it is really moving along greatly will be with the expansion to a new city. Tesla has not gone outside of Austin or the Bay Area as of yet, and launching in a new city will be a great indicator of progress.
It will also give Tesla a new benchmark against rival company Waymo, which has operated in Las Vegas for some time.
Tesla Roadster is ‘sorcery and magic’ and might be worth the wait, Uber founder says
Elon Musk clarifies viral Tesla Cybertruck accident with driver logs
