News
SpaceX scrubs Starhopper’s final Raptor-powered flight as Elon Musk talks “finicky” igniters
For unknown reasons, SpaceX’s Starhopper prototype suffered a hold just 0.8 seconds prior to its second planned flight test, a hold that was eventually followed by a decision to scrub the August 26th attempt and try again tomorrow, August 27th.
Starhopper is a full-scale, partial-height testbed for SpaceX’s next-generation Starship launch vehicle, serving more as a semi-mobile test stand for steel rockets and Raptor engines than an actual Starship prototype. The unusual vehicle took flight for the first time ever on July 25th, reaching an altitude of roughly 20m (65 ft) under the power of a single Raptor engine, capable of producing up to 200 tons (450,000 lbf) of thrust. That test also suffered a minor scrub on the 24th, followed by a successful flight one day later, a chapter that Starhopper may now mirror on its second attempted flight, a 150m (500 ft) hop.
Notably, SpaceX CEO Elon Musk took to Twitter just seconds after the rocket’s scheduled liftoff suffered a last-second hold to indicate that Raptor’s torch igniters were proving somewhat finicky relative to the chemical alternative used by SpaceX’s proven Merlin engines.
The CEO later confirmed that that comment was directly related to the 26th’s scrub, indicating that Raptor serial number 06 (SN06) needed to have its igniters inspected prior to a second hop test attempt, now scheduled to occur no earlier than 6pm EDT (22:00 UTC) on August 27th. The gist of the difficulties with Raptor’s igniter starts with the reason that SpaceX is attempting to integrate an entirely new form of ignition into the engine, replacing the methods successfully used over tens or even hundreds of thousands of seconds of firing with the company’s Merlin 1 and Merlin Vacuum engines.
Merlin 1D and MVacD both rely on a relatively simple, reliable, cheap, and easy method of chemical ignition, using a duo of pyrophoric materials known as triethylaluminum-triethylborane (TEA-TEB). When mixed, these materials immediately combust, generating an iconic green flash visible during Falcon 9 and Heavy launches, and thus producing the ‘spark’ needed to start Merlin engines.
Generally speaking, TEA-TEB is an excellent method of igniting rockets, even if it is more of a brute-force, inelegant solution than alternatives. It does, however, bring limitations: every single ignition requires a new ‘cartridge’ be expended, fundamentally limiting the number of times Merlin 1D (and Merlin Vacuum) engines can be ignited before and after liftoff.
This doesn’t even consider the fact that TEA-TEB are extremely complex chemical products that would be next to impossible to produce off of Earth, at least for the indefinite future.
To combat these downsides, SpaceX has designed Raptor with an entirely different method of ignition, known as torch ignition. Technically speaking, Raptor’s power, design, and methalox propellant combine to demand more than a relatively common solution, in which spark plugs are used to ignite an engine. Instead, Raptor uses those spark plugs to ignite its ignition sources, what CEO Elon Musk has described as full-up blow torches. Once ignited, those blow torches – likely miniature rocket engines using the same methane and oxygen fuel as Raptor – then ignite the engine’s methane and oxygen preburners before finally igniting those mixed, high-pressure gases in the combustion chamber.
In simple terms, the fact that Raptor is a full-flow staged-combustion (FFSC) engine means that the pressures it must operate under are extreme, verging on unprecedented in large-scale rocketry. Extremely high-pressure gases (on the order of 3,000-10,000+ psi or 200-700+ bar) are just as difficult to reliably ignite, especially if hypergolic solutions (i.e. TEA-TEB) are off the table.
To get an even ignition – critical to avoid burn-through, minor explosions, and even catastrophic engine failures – Raptor’s torch ignition may actually involve a 360-degree ring of spark plug-lit torches around the point of ignition, an undeniably complex solution.
However, as Musk notes, these significant, “finicky” challenges brought on by Raptor’s exotic ignition method are motivated by the potential benefits such a solution might bring. Relative to Merlin 1D’s TEA-TEB ignition, torch ignition – once optimized and matured into a reliable solution – will permit an almost unlimited number of Raptor ignitions before, during, and after flight.
Avoiding TEA-TEB and other complex chemical igniters also means that Starship will technically be able to launch to Mars or the Moon, perform injection and landing burns, maybe even hop around the surface, and still be able to return to Earth – all without resupply. Such a return voyage would still be predicated on the ability to generate the methane and oxygen propellant needed to fuel Starships, but – assuming that challenge can be solved – torch-lit Raptors would be ready for such a mission. In the event that, say, something like August 26th’s scrub happens to a Starship on Mars, the crew would also be able to get out, inspect Starship’s Raptors, and even replace faulty spark plugs if necessary.
Technically, one could bring lots of spare TEA-TEB cartridges and install those in space or after landing, but those cartridges are quite literally firebombs waiting to ignite, whereas spare spark plugs are entirely inert.
For now, we’ll have to wait for SpaceX technicians to get their eyes and hands-on Starhopper’s lone Raptor engine to verify that its ignition hardware is in good health. If all goes well, Starhopper will attempt its final flight test as early as August 27th.
Update (August 27th): Starhopper is reportedly set for a second attempted 150m (500 ft) flight test today, scheduled to occur no earlier than 5pm EDT (21:00 UTC) on August 27th. Stay tuned for SpaceX’s official Livestream!
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
News
Waymo sues Santa Monica over order to halt overnight charging sessions
In its complaint, Waymo argued that its self-driving cars’ operations do not constitute a public nuisance, and compliance with the city’s order would cause the company irreparable harm.
Waymo has filed a lawsuit against the City of Santa Monica in Los Angeles County Superior Court, seeking to block an order that requires the company to cease overnight charging at two facilities.
In its complaint, Waymo argued that its self-driving cars’ operations do not constitute a public nuisance, and compliance with the city’s order would cause the company irreparable harm.
Nuisance claims
As noted in a report from the Los Angeles Times, Waymo’s two charging sites at Euclid Street and Broadway have operated for about a year, supporting the company’s growing fleet with round-the-clock activity. Unfortunately, this has also resulted in residents in the area reportedly being unable to sleep due to incessant beeping from self-driving taxis that are moving in and out of the charging stations around the clock.
Frustrated residents have protested against the Waymos by blocking the vehicles’ paths, placing cones, and “stacking” cars to create backups. This has also resulted in multiple calls to the police.
Last month, the city issued an order to Waymo and its charging partner, Voltera, to cease overnight operations at the charging locations, stating that the self-driving vehicles’ activities at night were a public nuisance. A December 15 meeting yielded no agreement on mitigations like software rerouting. Waymo proposed changes, but the city reportedly insisted that nothing would satisfy the irate residents.
“We are disappointed that the City has chosen an adversarial path over a collaborative one. The City’s position has been to insist that no actions taken or proposed by Waymo would satisfy the complaining neighbors and therefore must be deemed insufficient,” a Waymo spokesperson stated.
Waymo pushes back
In its legal complaint, Waymo stated that its “activities at the Broadway Facilities do not constitute a public nuisance.” The company also noted that it “faces imminent and irreparable harm to its operations, employees, and customers” from the city’s order. The suit also stated that the city was fully aware that the Voltera charging sites would be operating around the clock to support Waymo’s self-driving taxis.
The company highlighted over one million trips in Santa Monica since launch, with more than 50,000 rides starting or ending there in November alone. Waymo also criticized the city for adopting a contentious strategy against businesses.
“The City of Santa Monica’s recent actions are inconsistent with its stated goal of attracting investment. At a time when the City faces a serious fiscal crisis, officials are choosing to obstruct properly permitted investment rather than fostering a ‘ready for business’ environment,” Waymo stated.
News
Tesla FSD v14.2.2 is getting rave reviews from drivers
So far, early testers have reported buttery-smooth drives with confident performance, even at night or on twisty roads.
Tesla Full Self-Driving (Supervised) v14.2.2 is receiving positive reviews from owners, with several drivers praising the build’s lack of hesitation during lane changes and its smoother decision-making, among others.
The update, which started rolling out on Monday, also adds features like dynamic arrival pin adjustment. So far, early testers have reported buttery-smooth drives with confident performance, even at night or on twisty roads.
Owners highlight major improvements
Longtime Tesla owner and FSD user @BLKMDL3 shared a detailed 10-hour impression of FSD v14.2.2, noting that the system exhibited “zero lane change hesitation” and “extremely refined” lane choices. He praised Mad Max mode’s performance, stellar parking in locations including ticket dispensers, and impressive canyon runs even in dark conditions.
Fellow FSD user Dan Burkland reported an hour of FSD v14.2.2’s nighttime driving with “zero hesitations” and “buttery smooth” confidence reminiscent of Robotaxi rides in areas such as Austin, Texas. Veteran FSD user Whole Mars Catalog also demonstrated voice navigation via Grok, while Tesla owner Devin Olsen completed a nearly two-hour drive with FSD v14.2.2 in heavy traffic and rain with strong performance.
Closer to unsupervised
FSD has been receiving rave reviews, even from Tesla’s competitors. Xpeng CEO He Xiaopeng, for one, offered fresh praise for FSD v14.2 after visiting Silicon Valley. Following extended test drives of Tesla vehicles running the latest FSD software, He stated that the system has made major strides, reinforcing his view that Tesla’s approach to autonomy is indeed the proper path towards autonomy.
According to He, Tesla’s FSD has evolved from a smooth Level 2 advanced driver assistance system into what he described as a “near-Level 4” experience in terms of capabilities. While acknowledging that areas of improvement are still present, the Xpeng CEO stated that FSD’s current iteration significantly surpasses last year’s capabilities. He also reiterated his belief that Tesla’s strategy of using the same autonomous software and hardware architecture across private vehicles and robotaxis is the right long-term approach, as it would allow users to bypass intermediate autonomy stages and move closer to Level 4 functionality.
News
Elon Musk’s Grok AI to be used in U.S. War Department’s bespoke AI platform
The partnership aims to provide advanced capabilities to 3 million military and civilian personnel.
The U.S. Department of War announced Monday an agreement with Elon Musk’s xAI to embed the company’s frontier artificial intelligence systems, powered by the Grok family of models, into the department’s bespoke AI platform GenAI.mil.
The partnership aims to provide advanced capabilities to 3 million military and civilian personnel, with initial deployment targeted for early 2026 at Impact Level 5 (IL5) for secure handling of Controlled Unclassified Information.
xAI Integration
As noted by the War Department’s press release, GenAI.mil, its bespoke AI platform, will gain xAI for the Government’s suite of tools, which enable real-time global insights from the X platform for “decisive information advantage.” The rollout builds on xAI’s July launch of products for U.S. government customers, including federal, state, local, and national security use cases.
“Targeted for initial deployment in early 2026, this integration will allow all military and civilian personnel to use xAI’s capabilities at Impact Level 5 (IL5), enabling the secure handling of Controlled Unclassified Information (CUI) in daily workflows. Users will also gain access to real‑time global insights from the X platform, providing War Department personnel with a decisive information advantage,” the Department of War wrote in a press release.
Strategic advantages
The deal marks another step in the Department of War’s efforts to use cutting-edge AI in its operations. xAI, for its part, highlighted that its tools can support administrative tasks at the federal, state and local levels, as well as “critical mission use cases” at the front line of military operations.
“The War Department will continue scaling an AI ecosystem built for speed, security, and decision superiority. Newly IL5-certified capabilities will empower every aspect of the Department’s workforce, turning AI into a daily operational asset. This announcement marks another milestone in America’s AI revolution, and the War Department is driving that momentum forward,” the War Department noted.
Waymo sues Santa Monica over order to halt overnight charging sessions
Tesla FSD v14.2.2 is getting rave reviews from drivers
