News
SpaceX Falcon 9 launch up next after ULA spy satellite mission hits snag
On Wednesday, November 3, a United Launch Alliance (ULA) Atlas V 531 rocket was set to launch the NROL-101 mission – a classified payload for the National Reconnaissance Office (NRO) of the United States government – from Space Launch Complex 41 (SLC-41) at Cape Canaveral Air Force Station. At neighboring Space Launch Complex 40 (SLC-40) a SpaceX Falcon 9 stood ready and waiting to launch a US military GPS satellite just a day later.
Ultimately, due to an anomaly with launchpad ground support equipment, the ULA launch attempt of the Atlas V NROL-101 mission was scrubbed Wednesday evening. Admittedly, the weather did not look promising either with ground winds remaining a concern throughout the countdown window.
With an hour and forty-seven minutes to go – just five seconds after a planned fifteen-minute hold was released – the launch teams announced that an anomaly had been discovered with “a ground valve issue with the liquid oxygen system for the Atlas V first stage.” The discovery initiated an immediate stop to the countdown and launch teams entered into an unplanned hold that would delay the targeted launch time.
At first, ULA conducted remote troubleshooting, but the anomaly was not remedied and a return-to-pad team would be required to enter the secured launchpad to physically investigate.
An anomaly team was deployed to investigate the valve that was restricting the flow of liquid oxygen (LOx) to the first stage of the Atlas V rocket. The hold remained for over an hour allowing the propellant lines to warm to a temperature that would be needed to be re-cooled prior to resuming the countdown.
Eventually, the return-to-pad team was able to evacuate the pad securing it for launch once again. Chill-down procedures to return the propellant lines back to an operational temperature began but were halted almost immediately. The anomaly had not been completely rectified and not enough time remained in the launch window to re-address it and re-chill the propellant lines. This led to the scrubbed launch attempt.
Typically, a scrubbed ULA mission for the NRO means that a neighboring SpaceX mission has to wait until the problem is fixed and ULA gets its rocket off of the nearby launchpad. However, that was not the case with Wednesday’s scrub. ULA stood down for a 48 hour recycle – rather than a typical 24 hour recycle – to attempt to launch the Atlas V 531 again on Friday, November 6.
This cleared the way for SpaceX to keep its targeted launch date of Thursday, November 5 during a launch window that extends approximately fifteen minutes from 6:24 – 6:39 p.m. EST (2324-2339 UTC) from SLC-40.
Following a successful static fire test of all nine Merlin 1D engines, SpaceX will attempt to launch the GPSIII-SV04 satellite for the United States military for a second time on Thursday, November 5.
The previous launch attempt on Friday, October 2 was thwarted at T-2 seconds due to anomalous engine start-up behavior. The unexplained early start-up of two Merlin 1D engines was eventually determined to be caused by “unexpected pressure rise in the turbomachinery gas generator” as explained by SpaceX CEO Elon Musk.
The engine anomaly prompted a thorough investigation of all Merlin 1D engines on the launch vehicle, as well as, a thorough investigation of the engines on two Falcon 9 launch vehicles designated for future NASA missions – the first operational rotation mission of the Commercial Crew Program, Crew-1, and the launch of the NASA and European Space Agency Earth-observation satellite, the Micheal Freilich Sentinel-6. Engines were eventually replaced on all three Falcon 9 launch vehicles.
A live hosted webcast of Thursday’s launch attempt will be provided on the company website and is expected to be available for viewing approximately fifteen minuted before liftoff.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
Elon Musk flew under the radar with his recent purchase of a $1 billion energy company, according to Federal Trade Commission (FTC) documents.
Transaction number 202612350 listed Tesla and SpaceX frontman Elon Musk as the acquiring party and CF APR Super Holdings LLC as the seller, with New APR Energy, LLC as the acquired entity. The deal, which closed without public announcement, came to light on May 14.
BREAKING: Elon Musk acquires Jacksonville power company APR Energy in a deal valued at more than $1,000,000,000.00.
— Polymarket Money (@PolymarketMoney) July 15, 2026
Analysts inferred the deal’s scale from minority stakeholder disclosures, including one report of a 5 percent interest sold for approximately $50.4 million. Fortress Investment Group had purchased APR’s assets in late 2024, rebranded the operation as New APR Energy, and subsequently transferred ownership to Musk.
APR Energy specializes in rapidly deployable power infrastructure. The company maintains one of the world’s largest fleets of mobile gas and diesel turbines, with more than 1.1 gigawatts of generation capacity. Its modular units, which are often trailer-mounted, enable turnkey installations ranging from 20 MW to over 500 MW.
APR provides full engineering, procurement, construction, operation, and maintenance services for behind-the-meter power plants, serving everything from data centers, utilities, and industrial clients.
The firm has expanded aggressively to meet surging demand, recently adding turbines and deploying over 100 MW for a major AI hyperscaler. Its solutions bridge critical gaps where grid interconnections face delays of two to five years, according to Yahoo.
The acquisition means something more for Musk. As he continues to expand projects in artificial intelligence, especially xAI, his AI venture, there is a greater need to supply energy-intensive supercomputing clusters, including the Colossus project, with what they need: reliable and high-capacity power.
Ownership of APR provides immediate access to flexible generation assets that can be deployed adjacent to data centers, reducing dependence on a strained infrastructure. It also complements Tesla’s energy storage business, so Musk will be able to pull from his own entities to address the rapid scaling demands of AI training and compute.
Tesla had a petition protesting a recall to fix a potential issue with 2017-2023 Model Y and Model 3 vehicles’ headlights was denied, as the National Highway Traffic Safety Administration (NHTSA) disagreed with the company’s opinion of things.
The recall covers approximately 19,917 Model Y and Model 3 vehicles built from 2017 to 2023. Tesla initially submitted a noncompliance report for the headlights on these vehicles on March 15, 2024. Tesla then petitioned for an exemption from the fix, which violated FMVSS No. 108 (40 CFR 571.108), arguing that the “noncompliance is inconsequential as it relates to motor vehicle safety.
🚨 Tesla was denied a petition by the NHTSA to avoid a recall of 19,900 2017-2023 Model 3 and Model Y vehicles.
The NHTSA found that the vehicles’ headlights may exceed maximum lighting levels. Tesla argued it was inconsequential and did not require a recall. pic.twitter.com/m8Jmm1teLL
— TESLARATI (@Teslarati) July 16, 2026
The NHTSA disagreed, stating that Tesla’s conclusion that the headlights do not increase any risk was not an opinion it shared. The agency said it disagreed with Tesla’s assumption that glare is not increased to surrounding traffic. This issue could be highlighted even more in certain weather conditions.
Tesla will be required to remedy the issue, the NHTSA ruled:
“In consideration of the foregoing, NHTSA has decided that Tesla has not met its burden of persuasion that the subject FMVSS No. 108 noncompliance is inconsequential to motor vehicle safety. Accordingly, Tesla’s petition is hereby denied, and Tesla is consequently obligated to provide notification of and free remedy for that noncompliance under 49 U.S.C. 30118 and 30120.”
The issue here appears to be the angle of the headlights and the brightness they emit during operation. The NHTSA report states that:
“Tesla’s headlamp supplier, Marelli Automotive Lighting, tested 25 right-hand and 25 left-hand lamps, and for this sample, found the maximum photometric intensity measured in the 10°U to 90°U and 90°L to 90°R zone was between 136.2 cd and 230.1 cd for the right-hand lamps and between 117.5 cd and 160.3 cd for the left-hand lamps. According to Tesla, these tests revealed that the photometric intensity of the right-hand and left-hand headlamp lower beam on the subject vehicles may measure as much as 230.1 cd in the 10°U to 90°U and 90°L to 90°R zone, exceeding the maximum photometric intensity by 105.1 cd. Additionally, Tesla states that a left-hand lamp tested by a Transport Canada recognized laboratory measured a maximum of 171.27 cd in the 10°U to 90°U and 90°L to 90°R zone. Despite these measurements exceeding the allowed photometric maximum of 125 cd, Tesla believes that the subject noncompliance is inconsequential to motor vehicle safety.”
Tesla also argued at some points that the headlights had not been deemed responsible for any complaints, accidents, or injuries related to the noncompliance.
Lifestyle
NTSB findings on fatal Tesla crash tell a very different story
The NTSB confirmed the driver, not Tesla’s FSD, caused the fatal Texas house crash.
The National Transportation Safety Board released preliminary findings Wednesday confirming that a Tesla driver, not the vehicle’s software, caused a fatal crash in Katy, Texas in June. The driver, 44-year-old Michael Butler, had engaged Full Self-Driving Supervised mode on Rose Hollow Lane, a residential street with a 30 mph speed limit, before manually overriding the system by pressing the accelerator pedal all the way to 100%. Data recovered from the 2025 Tesla Model 3 showed the vehicle was traveling over 70 miles per hour when it struck a home and killed 76-year-old Martha Avila, who was inside. Weather was clear, the road was dry, and it was daylight.
Texas man charged in fatal Tesla crash where he blamed Autopilot
Butler told authorities he had passed out at the wheel. But security camera footage obtained by the NTSB told a different story, and showed the car accelerating through an intersection before leaving the road entirely. Police also found that Butler’s phone had Google searches including the terms “Tesla FSD not aggressive enough 2026” and “Tesla FSD too timid,” raising serious questions about how he was using the system before the crash. Butler has since been charged with manslaughter. The victim’s family has filed a lawsuit against both Butler and Tesla, alleging negligence.
The NTSB findings aligned directly with what Tesla VP of AI Software Ashok Elluswamy had already stated publicly on X in the weeks after the crash, writing that “the driver manually overrode self-driving by pressing the accelerator all the way to 100%.” The data confirmed his account.
Yup. In this case, the driver manually overrode self-driving by pressing the accelerator all the way to 100% of the accel pedal in this residential area. They reached a speed of 73 mph during the crash, and had the accelerator pressed even after the crash.
— Ashok Elluswamy (@aelluswamy) June 22, 2026
Elon Musk secretly acquires $1B energy company to power the AI future
Tesla has to fix a big problem with its old headlights, NHTSA says
