Connect with us

News

SpaceX Starship rocket gets new Raptor engine for Starhopper-style hop test debut

SpaceX has delivered a Raptor to Starship SN4 for installation for the second time in two weeks. (SPadre)

Published

on

SpaceX has decided to install a different Raptor engine on its fourth full-scale Starship prototype in the buildup to the next-generation rocket’s inaugural flight test.

Starship SN4 recently became the first prototype to pass a cryogenic proof test, followed by two successful Raptor engine static fire tests and an even more successful pressure test on May 9th. Set to occur as early as later this month, that string of successes means that Starship SN4 is now all but guaranteed to become the first prototype to take flight. According to photos and information from CEO Elon Musk and FCC filings, that first hop – regardless of the ship – will be powered by a single off-center Raptor engine and likely follow in the footsteps of Starhopper, targeting a max hop height of 150m (~500 ft).

This time around, though, Starship SN4 will be around twice as tall as Starhopper, making for quite a spectacle regardless of the outcome. Currently, SpaceX has already received FCC authorization for Starship communications and is mainly just waiting on FAA approval for the short hop test – a license to launch that Musk suggested could arrive more than a “few weeks” after April 26th. Before Starship is technically ready for that milestone, however, one more test must be completed.

Raptor SN20 arrived at the launch pad on May 10th. (SPadre)

SpaceX has already successfully performed two static fire tests with a Raptor engine (likely SN18) installed on Starship SN4 on May 5th and 7th but the company has decided to replace that particular engine for unknown reasons. Raptor SN18 was removed from SN4 the morning after its (presumably) successful second static fire test, a move that is believed to have been made to avoid losing an engine in the event that a more ambitious cryogenic pressure test destroyed Starship.

As it turned out, that caution was unnecessary and Starship SN4 passed said pressure test with flying colors, reaching a planned maximum pressure of 7.5 bar (110 psi) – technically enough to qualify the rocket’s structure for (uncrewed) orbital launches.

For whatever reason, though, SpaceX has decided to replace Raptor SN18 with Raptor SN20, another of three engines currently on site at SpaceX’s South Texas rocket build and test facilities. That engine swap means that another Starship/Raptor static fire test is now needed to ensure that the new engine has been installed correctly and that both it and Starship are functioning as intended. As of now, SpaceX has scheduled that third static fire as early as Monday, May 11th, with a test window open from 9am to 9pm CDT (UTC-5).

SpaceX successfully fired up a Raptor engine on a full-scale Starship rocket for the first time ever on May 5th. (NASASpaceflight – bocachicagal)

If that static fire and include wet dress rehearsal (WDR) is successful, Starship will technically be cleared for flight. The only obvious missing piece is an attitude control system (ACS). Starhopper, for example, used cold nitrogen gas thrusters quite literally taken off of flight-proven Falcon boosters. It remains to be seen if SpaceX will take the same approach with Starship SN4 or if a different kind of ACS thruster is already installed on the rocket and hidden in plain sight. For now, it looks like we won’t have to wait long at all to find out.

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