News
SpaceX rocket ready for second reusability record, Starlink launch attempt
One of SpaceX’s first upgraded Falcon 9 Block 5 boosters is ready for its second attempt to set a reusability record after its March 15th Starlink launch attempt aborted at the very last second.
Now scheduled to send SpaceX’s sixth batch of 60 Starlink satellites into orbit no earlier than (NET) 8:16 am EDT (12:16 UTC), March 18th, the mission will be Falcon 9 booster B1048’s fifth. Just four months ago, the booster successfully launched the first 60 upgraded Starlink v1.0 satellites, also becoming the second SpaceX rocket to fly four times. While B1049 – B1048’s predecessor – was first to reach the four-flight milestone in May 2019, B1048 is now on track to take the next leap forward for Falcon 9 reusability.
First noted shortly after the abort on SpaceX’s March 15th launch webcast, the company later clarified that what could have been attributed to hardware failure was likely just an issue with software or sensors. Milliseconds before liftoff, Falcon 9’s autonomous flight computer seemingly didn’t like what it saw while interpreting the telemetry flowing in from the ignition of B1048’s nine Merlin 1D engines. Whatever the specific trouble, Falcon 9 believed that one or several of those Merlin 1D engines were producing more thrust than they should.
While likely oversimplifying what is a spectacularly complex logic system, the flight computers that control Falcon launch vehicles from T-1 minute to mission completion have to treat the messy uncertainty of reality through a black and white lens. Lacking the ability to heuristically interpret the data they process, the computers instead rely on algorithms that filter thousands of channels of telemetry into a handful of simple categories. If that data aligns with the computer’s expectations, things are okay. If the data doesn’t agree with the plan, things are not okay. There are, of course, many more levels of complexity, but the concept of operations remains mostly the same.
However, the telemetry itself is also a potential point of failure – bad data could lead the flight computer astray, concluding that things are okay when they aren’t or vice versa. To handle that potential failure mode, SpaceX relies on multiple strings of telemetry (and even multiple computers), all gathering and analyzing the same things simultaneously. If one of several redundant sensors starts to disagree with its brethren, reporting different data back to Falcon 9’s flight computers, it’s apparent that the sensor – not the thing it’s measuring – is likely at fault. Still, out of an abundance of caution, SpaceX avionics typically treat most “out-of-family” sensor readings as reason enough to delay or fully abort a launch. When a launch delay can be little more than an annoyance with a negligible cost, it’s almost universally better to be safe than sorry.
With Falcon 9 B1048’s March 15th false start, the rocket’s computer appears to have received conflicting readings from the same family (or families) of engine thrust sensors. While, as noted above, the fault almost certainly lay in an engine sensor or two and not in the engines themselves, the flight computer chose caution over expedience and halted the launch milliseconds before it would have otherwise commanded clamp release and lifted off.
Confirmed by SpaceX delaying the Starlink V1 L5 mission by just three days, the issue was almost certainly software or sensor-related. Given that SpaceX continues to push the envelope of launch vehicle reusability, it’s honestly more surprising that aborts like these aren’t more common. Instead, the reality is that Falcon 9 Block 5 – aside from delays from the occasional upper stage fault – almost never suffers hardware-related aborts when compared to the rocket’s prior iterations.
Featuring the second-ever flight-proven Falcon payload fairing, Falcon 9 B1048 will hopefully become the first SpaceX rocket to complete five orbital-class launches and landings. With more than a little luck, there’s also a smaller chance that the mission could mark the first time SpaceX successfully catches both fairing halves with twin ships Ms. Tree and Ms. Chief.
Tune in for SpaceX’s second Starlink V1 L5 launch attempt around 8am EDT (12:00 UTC) to catch the potentially record-breaking launch and landing live.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
Tesla AI lead Ashok Elluswamy said this week that 24-hour Robotaxi service is close. Replying on X to a rider who wanted Cybercab trips all night, he wrote that the capability would arrive “next month or so” once “the next tech to merge on the v15 plan” is ready.
The comment landed on September 4, one day after Tesla opened public Cybercab rides in Austin. It is the clearest near-term timeline yet for overnight unsupervised operation. Tesla’s paid Robotaxi network currently runs from 6 a.m. to 10 p.m. seven days a week across Austin, Dallas, Houston, Miami, Orlando, and Tampa.
next month or so. the next tech to merge on the v15 plan will enable it.
— Ashok Elluswamy (@aelluswamy) September 4, 2026
That 16-hour window is shorter than the 6 a.m. to 2 a.m. schedule the company used for much of the prior year.
Elluswamy did not name the specific feature or say whether the change would apply first to purpose-built Cybercabs, the existing Model Y fleet, or both. He also offered no city-by-city rollout list. The link to Full Self-Driving v15 is nevertheless significant.
Tesla has described v15 as a step-change architecture with seven parallel improvement tracks and roughly ten times more parameters than earlier builds. Early versions of that software already operate on the Robotaxi fleet and contain about 40 percent of the planned gains.
By July 2026, the unsupervised fleet had logged more than 380,000 miles across six cities in two states with what the company called an impeccable safety record and no notable incidents caused by the vehicles themselves. Tesla has repeatedly argued that camera-based end-to-end neural networks, rather than extra sensors, are the core of the solution.
Overnight service would test that claim in lower-light conditions and would also raise vehicle utilization, a key variable for Robotaxi unit economics. The company has already begun using public Superchargers at night and is building dedicated Robotaxi charging sites.
Riders have asked why software must change if the cars already drive in the dark. The practical answer appears to be reliability and scale: Tesla has held back mass expansion until more of the v15 stack is merged, citing the need for higher confidence before putting thousands of unoccupied vehicles on streets around the clock.
If the next module arrives on the timetable Elluswamy sketched, 24-hour service could begin in October 2026 in at least some markets.
That would mark a shift from a daytime-bounded pilot to a service that can run whenever demand exists, including the late-night hours that have so far remained out of reach.
Tesla is beginning to roll out Full Self-Driving Supervised v14.3.9 with a new active safety layer that can take control even when the driver is operating the car manually.
Tesla AI said the software can activate FSD on the driver’s behalf when an imminent collision is detected and Automatic Emergency Braking may not be enough. It may also engage if the system detects heavy distraction or an accidental FSD disengagement.
FSD Supervised v14.3.9 starting to roll out shortly
This release includes a new active safety feature set: FSD Supervised can now activate on your behalf when an imminent collision is detected and Automatic Emergency Braking (AEB) may not be enough.
It may also engage if we…
— Tesla AI (@Tesla_AI) September 4, 2026
The capability is essentially Automatic Collision Evasion. However, unlike conventional AEB, which mainly applies the brakes in a straight line, this feature can use steering, braking, and acceleration together if the car calculates that stopping alone will not prevent impact and a safer path exists. The system may change lanes or move toward a shoulder when conditions allow, then continue driving after the immediate threat is handled rather than simply coming to a stop.
The intervention is meant as a last-resort safety net, not a replacement for attentive driving.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
Tesla’s own description still frames FSD as supervised assistance. Secondary reports on internal release notes say the feature can fire while the car is being driven manually if cabin-camera monitoring suggests the driver is not sufficiently attentive, such as reaching toward the back seat, or if FSD appears to have been turned off unintentionally.
After the emergency maneuver, the car is expected to alert the driver and request a return to manual control.
The safety case is straightforward. Many collisions happen in the last second because a driver is looking away, fumbles a control, or faces an obstacle that braking cannot fully solve. A system that can both recognize that AEB is insufficient and execute a coordinated evasive path can reduce those remaining high-severity events.
Re-engaging after accidental disengagement also addresses a practical failure mode: a small steering nudge that drops FSD at the worst moment. The advantage is a background safety net that uses the same vision stack already running in v14, instead of leaving the car solely to emergency braking once the driver is no longer in command.
The feature still depends on FSD being enabled and, according to reports, an active FSD purchase or subscription. It does not make the vehicle unsupervised. Drivers remain responsible, and Tesla has not published how often the system is expected to intervene or how it will handle false positives.
If the rollout is conservative and the false-alarm rate stays low, the update is a meaningful step: FSD is no longer only a feature the driver turns on. In the rare moments when disaster is already forming, it can step in.
Tesla launched the all-electric, steering wheel-less, and pedal-less Cybercab last night at a quiet and small event in downtown Austin, Texas.
The launch, which marked the beginning of unsupervised ride-hailing for Tesla’s Robotaxi platform with Cybercab, has already caught the attention of the National Highway Traffic Safety Administration (NHTSA) who has more questions.
NHTSA opened an Audit Query (AQ) into the Cybercab’s Federal Motor Vehicle Safety Standards (FMVSS) certification that Tesla gave the vehicle. Manufacturers self-certify vehicles much of the time to avoid excessive regulatory delays.
Tesla Cybercab interior, note the lack of steering wheel and pedals. (Credit: @niccruzpatane/X< /a>)
However, the agency needs more information; it said in a summary:
“On September 3, 2026, Tesla began commercial deployment with a small number of its Cybercab vehicles in Austin, Texas. Tesla notified the Agency that it certified those Cybercab vehicles as compliant with all applicable Federal Motor Vehicle Safety Standards (FMVSS). Tesla also notified the Agency that it plans to gradually expand commercial deployment of the Cybercab to include additional vehicles and locations.”
It also went on to state that the Cybercab lacks traditional automotive controls, which is a groundbreaking move. The process is entirely new to the NHTSA, which gives the agency some leverage to put Tesla’s launch under a microscope:
“The vehicles lack permanently attached, conventional manual controls, such as a brake pedal, gas pedal, steering wheel, and mirrors. NHTSA is opening this AQ to examine the process and technical data on which Tesla relied when certifying the Cybercab and related issues. Among other things, NHTSA will consider the extent to which Tesla’s certification depended on determinations that certain FMVSS are inapplicable to the Cybercab.”
Tesla has added 45 Cybercab units to its fleet of Robotaxi-enabled cars in Austin, according to public documents the company submitted to the State of Texas over the past week. Enabling this level of self-driving is something Tesla has worked toward for many years, and now that it is finally here, it seems more than reasonable that regulatory agencies will have some questions.
Many outlets might try to frame this as a negative, but it is truly an agency looking to gain more information about groundbreaking tech that Tesla has been developing for years.
In an effort to keep riders, pedestrians, and property safe, any and all data accumulated from these first days, weeks, and months of rides will likely be shared with the NHTSA to enable broader rollout strategies across the United States and more in the future.
Tesla Robotaxi will be a 24/7 service: here’s when
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
