News
SpaceX Starship engine completes orbital-duration static fire test in Texas
A local resident and unofficial SpaceX observer has reported hearing a test of one of Starship’s Raptor engines that lasted more than five minutes at the company’s McGregor, Texas development facilities.
If accurate, it could be the longest static fire of a Starship engine that SpaceX has ever completed in the two years since full-scale Raptor testing first began. Whether it was successful or not, a five or six-minute static fire would also confirm that SpaceX is well into the process of qualifying Raptor for Starship’s first orbital launch attempts.
An FCC “Special Temporary Authority” (STA) request filed by SpaceX itself for Starship’s inaugural “Orbital Test Flight” earlier this month provided several significant details about that milestone mission. Aside from revealing that Starship will ultimately attempt a soft ocean landing – splashdown – off the coast of a Hawaiian island after traveling ~75% of the way around Earth, it also included a precise timeline of launch events.
According to that timeline, ten seconds shy of three minutes after liftoff, Starship’s Super Heavy booster will shut down and separate from the spacecraft. Starship will then ignite either three or six Raptor engines for a bit less than six minutes to boost itself within the vicinity of orbital velocity. Curiously, the same timeline makes no mention of a deorbit burn, without which the first “orbital” test flight will technically be suborbital even if Starship is traveling very close to orbital velocity.
Regardless, the document confirms that Starship’s orbital insertion burns will be approximately 5.5-6.5 minutes long – the maximum stamina required from its Raptor engines, in other words. Rephrased, in its current design, Starship will never be able to reach orbit without Raptor engines capable of continuously operating for around six minutes. Up until high-altitude Starship test flights began in December 2020, the extent of Raptor’s long-duration capabilities and thus the state of SpaceX testing was effectively a mystery.
When Starship SN8 debuted, however, it quickly became clear that SpaceX had made significant progress after one of its three Raptor engines burned without apparent issue for 280 seconds (4:40). If SN3x and SN4x Raptors could handle almost five minutes of continuous operation, the engine was just ~20% improvement away from being able to complete a plausible orbital insertion burn.
Now, six months later, Raptor appears to have completed at least one truly orbital-class burn at SpaceX’s Central Texas development campus. McGregor typically completes multiple static fires every day and already performs similar-duration testing of Merlin Vacuum engines and upper stages, so it’s possible – if not probable – that one or several other five or six-minute-long tests have simply been missed over the last few months.
Beginning just a handful of months ago, SpaceX has been rapidly building a new Raptor test stand with two vertical engine bays and new liquid oxygen and methane propellant storage to go with it. Given that a six-minute Raptor engine static fire at or close to full thrust would consume around 220 metric tons of propellant, it’s possible that SpaceX’s ground test facilities simply didn’t have the storage capacity to support such long tests prior to those recent upgrades.
Regardless, the first unofficially confirmed orbital-duration test is an exciting and important milestone with or without SpaceX confirmation and continues to make it abundantly clear that the company is now almost entirely focused on reaching orbit (or getting close).
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.
Featured
Tesla Cybercab is coming to Asia this month as US service officially begins
Tesla Asia says Cybercab will be on display in Hong Kong, Tokyo, Beijing and Shanghai this month.
Tesla’s Cybercab is heading to Asia. The official Tesla Asia account posted on X Thursday, inviting Cybercab fans to “Come experience the future of autonomy in Hong Kong, Tokyo, Beijing & Shanghai.” The post went up within hours of Tesla’s own Cybercab milestone in Texas, where the company said Thursday it had begun offering rides in across Austin.
Exact dates and venues for the Asia tour haven’t been released yet, though Tesla Hong Kong replied to the announcement with “Cybercab will be on display in Hong Kong soon,” while Tesla Japan’s response pointed fans to a sign up page for updates. Neither post mentions test rides or a service area, and nothing so far suggests Tesla is launching Robotaxi operations in any of the four cities. Based on how Tesla has run past Cybercab tours, in Europe in late 2024 and at US shopping centers that same December, the Asia stops are almost certainly static displays at Tesla stores or public venues as a means to stimulate buzz for its future driverless ride-hailing service in the big cities.
Cybercab will be on display in Asia this month!
Come experience the future of autonomy in Hong Kong, Tokyo, Beijing & Shanghai. pic.twitter.com/wGmmEastfX— Tesla Asia (@Tesla_Asia) September 4, 2026
The timing lines up with Tesla’s only prior Cybercab appearance in the region, a booth at the China International Import Expo in Shanghai last November, which Teslarati covered at the time. At that event, Tesla’s regional general manager for Shanghai framed the car as evidence of the company’s broader mission, a message Tesla has since formalized in its Master Plan Part IV, which states that “autonomous vehicles have the capacity to dramatically improve the affordability, availability and safety of transportation while reducing pollution, particularly in our increasingly dense global cities.” The same document is where Tesla lays out its “sustainable abundance” framing for Cybercab and Optimus alike, describing the two as the hardware behind an AI driven push to cut the cost of transportation and labor at scale.
Whether Cybercab actually operates as a robotaxi anywhere in Asia remains an open question, considering China has already pushed an autonomous ride-hailing market that’s run on homegrown players like Baidu’s Apollo Go and Pony AI. For now, the four city tour reads as a marketing push timed to Austin’s momentum.
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
Tesla Cybercab launch catches NHTSA’s attention who wants to know more
