Connect with us

News

A SpaceX Starship rocket could take to the sky for the first time later this week

SpaceX has scrubbed a Starship static fire attempt for the third time as evidence grows that the ship's first flight could come as early as this week. (NASASpaceflight - bocachicagal)

Published

on

SpaceX has scrubbed its latest Starship static fire test for the third time since Friday but if another attempt succeeds within the next few days, a full-scale Starship prototype could lift off for the first time later this week.

SpaceX has attempted to perform a Starship static fire every day for the last three days without any luck, foiled by what must be mild technical issues and some extreme South Texas weather. That static fire – set to be Starship serial number 4’s (SN4) third – is required because SpaceX chose to replace the rocket’s installed Raptor engine (SN18) around 10 days ago after completing two successful tests on May 4th and 5th. Installed a few days after SN18 was removed, Starship and Raptor SN20 must now perform their own integrated static fire to ensure the complex systems are working properly.

Since SN4’s last test, SpaceX teams have been swarming the Starship prototype day and night, installing new COPVs (composite overwrapped pressure vessels; used to store high-pressure gas), new plumbing, and more. The specific purposes of all those in-situ changes can only be speculated at but what is clear is that SpaceX is preparing Starship SN4 for the first attempted flight test of a full-scale prototype, following in the footsteps of Starhopper’s bizarre but successful July and August 2019 hops. As SN4’s third Raptor static fire has slipped, though, so has that flight test. While the FAA has yet to officially publish a license for the 150m (~500 ft) Starship hop, NOTAMs (Notices to Airmen) filed recently suggest that that license and hop could come any day now.

Most recently, a NOTAM was filed on May 18th for what is likely Starship’s 150m hop test on Thursday, May 21st. Filed before SN4’s May 18th static fire test was aborted twice, that proposed May 21st hop test will almost certainly be delayed at least as long as the static fire that needs to precede it and is also dependent upon the FAA officially licensing the flight. The fact that NOTAMs are being filed for that flight strongly suggests that SpaceX and the FAA or in the late stages of hammering out a license, a process that can often involve a great deal of back-and-forth and compromise for experimental rocket launches.

Regardless, if or when Starship SN4 finally manages to fire up its new Raptor engine, it could be just a matter of days after that SpaceX attempts the first true Starship flight test. If everything goes according to plan, the ~30m (~100 ft) tall stainless steel rocket will lift off under the power of a single asymmetrically installed Raptor engine, capable of producing up to 200 metric tons (~450,000 lbf) of thrust with cryogenic liquid methane and oxygen propellant.

Starship SN4 is pictured beside the now-retired Starhopper test article on April 23rd. (NASASpaceflight – bocachicagal)

After lifting off from its ad-hoc South Texas launch mount, Starship SN4 will attempt to reach a peak altitude of 150m (~500 ft) and descend back down for a soft landing on an adjacent concrete pad, just like Starhopper did around nine months ago. A lot could go wrong: aside from using steel more than three times thinner than Starhopper’s, Starship SN4 will also be debuting an entirely new kind of landing leg, will be flying with asymmetric thrust, and will likely be using autogenous pressurization — all new challenges for SpaceX.

Nevertheless, there are also reasons for confidence. SpaceX has already successfully pressurized Starship SN4 all the way to 7.5 bar (~110 psi, sufficient for uncrewed orbital flight), performed multiple wet dress rehearsals and two Raptor static fire tests, and even tested what appears to be a new kind of cold gas thruster needed for roll control. Most importantly, even if Starship SN4 is destroyed during its next static fire or inaugural flight attempt, Starship SN5 is nearly at the same stage of completion and should be ready to take the reins almost immediately after the potential demise of its predecessor. With Crew Dragon’s inaugural NASA astronaut launch scheduled on May 27th, the rest of the month is set to be quite the event.

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

Tesla Robotaxi will be a 24/7 service: here’s when

Published

on

Credit: @AdanGuajardo/X

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.

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.

Continue Reading

News

Tesla Full Self-Driving will now overtake manual driving to avoid disaster

Published

on

Credit: Tesla

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.

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.

Continue Reading

News

Tesla Cybercab launch catches NHTSA’s attention who wants to know more

Published

on

(Credit: Teslarati)

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.

Continue Reading