Connect with us

News

SpaceX converts Falcon Heavy booster into Falcon 9

Published

on

More than two years after the rocket’s last launch, SpaceX appears to have finally decided to give at least one of two surviving Falcon Heavy Block 5 cores a new lease on life as a Falcon 9 booster.

Known as B1052, the Falcon Heavy side core or booster debuted in April 2019 as part of the first flight of the rocket’s Block 5 variant, successfully launching Saudi Arabia’s large Arabsat 6A communications satellite to an almost 90,000 km (56,000 mi) transfer orbit. Following in the footsteps of the first Falcon Heavy, the first Block 5 vehicle repeated its predecessor’s iconic double-landing back at Cape Canaveral. Just 74 days later, both Falcon Heavy Block 5 side boosters B1052 and B1053 launched again, this time supporting the US military’s long-delayed STP-2 rideshare and qualification mission.

From Falcon Heavy side booster to Falcon 9 booster in a handful of months. (Richard Angle)

Once again, B1052 and B1053 stuck near-simultaneous landings at SpaceX’s Landing Zones. Both missions’ center cores, however, weren’t so lucky. During Arabsat 6A, the first Falcon Heavy Block 5 center core did successfully land but high seas eventually toppled the booster, destroying it and leaving few intact remains. During STP-2, CEO Elon Musk revealed that SpaceX didn’t actually expect to recover the mission’s replacement center core due to the exceptionally hot reentry it would need to survive. As predicted, the center core did not survive, with Musk later reporting that the hot reentry damaged thrust vectoring hardware, causing the rocket to veer off course.

USAF photographer James Rainier's remote camera captured this spectacular view of Falcon Heavy Block 5 side boosters B1052 and B1053 returning to SpaceX Landing Zones 1 and 2. (USAF - James Rainier)
Mission complete! Taken by Airmen Alex Preisser, this photo shows B1052 and B1053 shortly after coming to a rest at SpaceX's Landing Zones.
Falcon Heavy Block 5 side boosters B1052 and B1053 rest at SpaceX’s Florida Landing Zones after a flawless launch debut. (USAF – Alex Preisser)
B1052 and B1053 nailed their landings once again – this time at night – after their second mission. (SpaceX)

Thankfully, both side boosters aced all four of their collective landings. However, despite previous statements from Musk indicating that Falcon’s new Block 5 design made it fairly easy to convert Falcon first stages between Falcon 9 and Falcon Heavy side booster configurations, both B1052 and B1053 dropped off the face of the Earth immediately after completing STP-2. Only in September 2021, 27 months later, did one of the two cores finally reappear in public – sans landing legs and grid fins but with a nosecone still installed.

As is now clear, that surprise appearance after years in storage was no coincidence. A bit less than three months later after the mystery Falcon Heavy side booster was spotted rolling down a Kennedy Space Center highway from a Cape Canaveral storage hangar to a new SpaceX facility, one of the two side boosters (B1052) was spotted once again – this time with landing legs and a Falcon 9 interstage installed where a nosecone once sat.

B1052 is reborn. (Richard Angle)

Aside from having clearly been converted into a Falcon 9 booster, former Falcon Heavy side booster B1052 was also mated to a new expendable upper stage – a strong indication of an imminent launch. Word on the ground is that the rocket and transporter were on their way to SpaceX’s Cape Canaveral Space Force Station (CCSFS) LC-40 pad for the company’s planned December 18th launch of Turkey’s Turksat 5B communications satellite.

Following SpaceX’s successful NASA IXPE launch on December 9th, the company has two more East Coast launches planned before the end of the year: Turksat 5B NET December 18th and CRS-24 NET December 21st. Several other Falcon 9 boosters (save for B1062, which is probably assigned to CRS-24) are likely available to launch Turksat 5B, so B1052’s assignment – while not implausible – isn’t guaranteed.

Advertisement

Above all else, B1052’s second life as a Falcon 9 is exciting because it means that B1053 probably isn’t far behind it, meaning that SpaceX’s fleet of operational Falcon boosters is about to grow significantly in a short period of time. As of now, that fleet contains eight Falcon 9 boosters that have each completed an average of more than six orbital-class launches. Half have flown nine times. Aside from expanding that fleet by 25%, the reintroduction of B1052 and B1053 will free up SpaceX to retire older boosters like B1049 and B1051, which CEO Elon Musk has said are slower and more expensive to reuse.

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 has to fix a big problem with its old headlights, NHTSA says

Published

on

tesla model 3 first generation headlight
Credit: Tesla Asia/Twitter

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.

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.

Continue Reading

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.

Published

on

By

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.

Continue Reading

Investor's Corner

Lucid CEO dispels any rumors of bankruptcy: ‘So far from the facts’

Published

on

Credit: Lucid

Lucid CEO Silvio Napoli responded to rumors of an imminent bankruptcy that was reportedly being mulled after a report stated the automaker was working with the firm AlixPartners to iron out its next steps.

The company felt a massive loss on Wall Street yesterday, as the report essentially pushed the stock down as much as 55 percent on Tuesday.

The report, published initially by Eletric-Vehicles.com, claimed Lucid was essentially in dire straits and was told by AlixPartners, a commonly used restructuring advisor, to either take shares private or file for Chapter 11 bankruptcy protection.

Lucid denies rumors of bankruptcy after over 40% stock drop

Lucid’s head of Communications, Nick Twork, immediately challenged the report and stated the company “has sufficient liquidity to carry its operations well into next year.”

Now, the company’s CEO is chiming in as well, stating that the report is “so far from the facts that they require a direct response.”

Napoli said:

“Lucid is not considering bankruptcy or a transaction to take the company private. Those reports are false. The Board did not explore either scenario. Period.

As disclosed in our most recent quarterly filing, Lucid has sufficient liquidity to fund its operations well into next year.

We work with outside advisors to improve operational performance and execution. They are not advising Lucid on a take-private transaction or bankruptcy, and any suggestion that they have recommended either course of action to management or the Board is false.

My priority is clear: turn this company around. That is where the leadership team and I are focused.

I look forward to providing a full update during our quarterly earnings call on August 4th.”

It seems pretty clear that Lucid is confident things will be okay, and, to be honest, they should not have much to worry about, especially considering the company has been backed by the Saudi Public Investment Fund (PIF) for years. It has solid financial backing, and its sales, while weak, are pretty much right on par with a company of this age.

Lucid also sent a Cease & Desist letter to the publication for their report.

Lucid shares have rebounded nicely and are up nearly 21 percent at the time of publication. As soon as the company dispelled the rumors of bankruptcy yesterday, the stock began to climb back toward more reasonable levels.

Continue Reading