Connect with us

News

SpaceX’s next Falcon Heavy launch may feature record-breaking center core landing

Falcon Heavy clears the top of the tower in a spectacular fashion during its debut launch. (Tom Cross/Pauline Acalin)

Published

on

Thanks to a temporary reopening of the US federal government, SpaceX was finally able to continue the process of filing FCC and FAA paperwork needed to acquire permits for upcoming launches, including Falcon Heavy.

One such filing related to the first operational Falcon Heavy launch has revealed a fairly impressive statistic: comprised of three first stage boosters, SpaceX indicated that Falcon Heavy’s center core will attempt to land on drone ship Of Course I Still Love You (OCISLY) nearly 1000 km (600 mi) away from its launch site, easily smashing the record for the greatest distance traveled by a Falcon booster in flight.

The same FCC filings also revealed a No Earlier Than (NET) launch date: March 7, 2019. Originally targeted for mid to late February, the complexity and logistical challenges of building, shipping, testing, and delivering two side boosters, a center core, one upper stage, and a payload fairing from SpaceX’s California factory to its Texas test facilities and Florida launch pad unsurprisingly took a small toll on the launch’s aspirational schedule. Nevertheless, if the launch data actually holds to March 7th, SpaceX will not have missed the mark by much considering that this Falcon Heavy – based on new and more powerful Block 5 boosters – is likely a significant departure from the Block 2/Block 3 hardware that has flight heritage from the triple-booster rocket’s Feb. 2018 launch debut.

Advertisement
The second (and third) flight of Falcon Heavy is even closer to reality as a new side booster heads to Florida after finishing static fire tests in Texas. (Reddit /u/e32revelry)

Just shy of a year after Falcon Heavy’s launch debut, it appears that the rocket’s second and third launches were pushed back by a fundamental lack of production capacity. In other words, SpaceX’s Hawthorne rocket factory simply had to focus on more critical priorities in the 6-9 months that followed the demo mission. At nearly the same time as Falcon Heavy was lifting off for the first time, SpaceX’s world-class production crew was in the midst of manufacturing the first upgraded Falcon 9 Block 5 booster (B1046) and wrapped up final checkouts just 10 days after Heavy’s Feb. 6 launch debut, sending the pathfinder rocket to McGregor, Texas for the first static fire of a Block 5 booster.

In the meantime, SpaceX’s decision to intentionally expend otherwise recoverable reused Falcon boosters after their second launches meant that the company’s fleet of flightworthy rockets was rapidly approaching zero, a move CEO Elon Musk specifically indicated was meant to make room for Block 5, the future (and final form) of the Falcon family. SpaceX’s busy 2018 launch manifest and multiple critical missions for the US government were thus balanced on the success, reliability, and rapid production of a serious number of Merlin engines, boosters, and upper stages. This included B1051 – the first explicitly crew-rated Falcon 9 – and B1054, the first SpaceX rocket rated to launch high-value US military (specifically Air Force) satellites. However, SpaceX also needed to produce a cadre of Falcon 9 boosters capable of easy reuse to support the dozen or so other commercial launches on the manifest.

 

That gamble ultimately paid off, with Block 5 performing admirably and supporting a reasonable – if not record-breaking – rate of reuse. SpaceX successfully launched B1054 for the USAF, completed B1051 (now at Pad 39A awaiting NASA’s go-ahead), and built enough reusable Block 5 boosters to support nine additional commercial missions in 2018. In hindsight, barring an assumption of a truly miraculous and unprecedented Falcon booster production rate, Falcon Heavy’s next launches were almost guaranteed to occur no fewer than 6-12 months after the rocket’s launch debut – SpaceX’s entire launch business depended on building 5+ unrelated Falcon 9 boosters, while Falcon Heavy customers Arabsat and the USAF were unlikely to be swayed to launch on flight-proven hardware so early into Block 5’s career.

https://twitter.com/_TomCross_/status/1048483536917823488

All cylinders firing

Once Falcon 9 B1054 departed SpaceX’s Hawthorne factory (see above) in early October, it appears that the company’s production team pivoted directly to integrating and shipping the next three (or more) Falcon Heavy boosters back to back for the rocket’s second and third launches. The first new side booster departed the factory in mid-November, followed by a second side booster in early December and a (presumed but highly likely) center core at the turn of 2019. Both side boosters have been static-fired in Texas and are now at SpaceX’s Florida facilities, while the center core either just completed its Texas static fire testing or is already on its way East.

Advertisement

 

Once the center core and upper stage make their way to SpaceX’s Kennedy Space Center Pad 39A, the company’s technicians and engineers will be able to integrate the second Falcon Heavy to have ever existed in preparation for a critical static fire test. That could occur as early as February, although the launch debut of Crew Dragon (DM-1) – now NET March from Pad 39A after a relentless string of slips – will likely take precedence over Falcon Heavy and could thus directly interfere with its launch, as the launch pad and transporter/erector (T/E) has to undergo at least a few days of modifications to switch between Falcon 9 and Heavy.

Regardless, the next two Falcon Heavy launches will be well worth the wait. SpaceX’s FCC filings indicate that the center core may travel nearly 1000 km (600 mi) East of Pad 39A to land on drone ship OCISLY after launch, smashing the previous record attempt – during the June 2016 launch of Eutelsat 117WB – of ~700 km (430 mi). That Falcon 9 booster – albeit a less-powerful Block 2 variant – was unsuccessful in its landing attempt, running out of oxidizer seconds before landing. Falcon Heavy’s debut center core also happened to suffer a wholly different but no less fatal anomaly during landing, causing it to miss the drone ship and slam into the Atlantic Ocean at almost half the speed of sound (300 mph/480 km/h).

Advertisement

Known for their rocket performance estimates, NASASpaceflight forum user “Orbiter” first pointed out the impressive distance – gathered by mapping coordinates included in SpaceX’s Jan. 28th FCC filing – and estimated that the Falcon Heavy center booster flying a trajectory as implied could be traveling as fast as ~3.5 km/s (2.2 mi/s) at main engine cut-off (MECO), the point at which the booster separates from the upper stage and fairing. This would be a nearly unprecedented velocity for any Falcon booster, let alone a booster with plans to land after launch. Falcon 9 MECO typically occurs at velocities between 1.5 and 2.5 km/s for recoverable missions, while even the recent expendable GPS III launch saw F9 S1’s engines cut off around 2.7 km/s.

Whether that MECO velocity estimate is correct, Falcon Heavy’s NET March launch of the ~6000 kg (13,300 lb) Arabsat 6A satellite is likely to be an exceptionally hot reentry and recovery for the center core, while the rocket’s duo of side boosters will attempt a repeat of the debut mission’s spectacular double-landing at LZ-1.


Check out Teslarati’s newsletters for prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket launch and recovery processes!

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

Elon Musk

‘I don’t understand TSLAQ:’ notable investor backs Tesla, Elon Musk

Published

on

tesla showroom
(Credit: Tesla)

One notable investor that many people will recognize said today on X that he does not understand Tesla shorts, otherwise known as $TSLAQ, and he’s giving some interesting reasons.

Martin Shkreli was long known as “Pharmabro.” For years, he was known as the guy who bought the rights to a drug called Daraprim, hiked the prices, and spent a few years in Federal prison for securities fraud and conspiracy.

Shkreli is now an investor who co-founded several hedge funds, including Elea Capital, MSMB Capital Management, and MSMB Healthcare. He is also known for his frank, blunt, and straightforward responses on X.

His LinkedIn currently shows he is the Co-Founder of DL Software Inc.

One of his most recent posts on X criticized those who choose to short Tesla stock, stating he does not understand their perspective. He gave a list of reasons, which I’ll link here, as they’re not necessarily PG. I’ll list a few:

Advertisement
  • Fundamentals always have and will always matter
  • TSLAQ was beaten by Tesla because it’s “a great company with great management,” and they made a mistake “by betting against Elon.”
  • When Shkreli shorts stocks, he is “shorting FRAUDS and pipe dreams”

After Shkreli continued to question the idea behind shorting Tesla, he continued as he pondered the mentality behind those who choose to bet against the stock:

“I don’t understand ‘TSLAQ.’ Guy is the richest man in the world. He won. It’s over. He’s more successful with his 2nd, 3rd, and 4th largest companies than you will ever be, x100.

You can admit you are wrong, it’s just a feeling which will dissipate with time, trust me.”

Advertisement

According to reports from both Fortune and Business Insider, Tesla short sellers have lost a cumulative $64.5 billion since Tesla’s IPO in 2010.

Elon Musk issues dire warning to Tesla (TSLA) shorts

Shorts did accumulate a temporary profit of $16.2 billion earlier this year.

Continue Reading

News

Tesla will let you bring back this removed Model 3 part for a price

It will cost $595 and is available on Tesla’s website. You will have to have a Model 3 on your Tesla account to purchase the stalk retrofit kit.

Published

on

Credit: Tesla Asia/X

Tesla is now letting Model 3 owners in the United States bring back one part that the company decided to remove after it refreshed the all-electric sedan last year. Of course, you can do it for a price.

With the Model 3 “Highland” refresh that Tesla launched last year, one of the most monumental changes the company made was to ditch the turn signal stalk altogether. Instead, Tesla opted for turn signal buttons, which have been met with mixed reviews.

I drove the new Tesla Model 3, here’s what got better

The change was widely regarded as Tesla preparing for more autonomous driving in its vehicles, especially as its interiors have gotten even more minimalistic.

The lack of a stalk in the new Model 3 was just another move the company made to adjust drivers and passengers to seeing less at the steering wheel column.

Advertisement

However, many drivers did not prefer the use of buttons and wanted the stalk reinstalled. Tesla allowed it in several regions, launching a retrofit kit. It has now made its way to the United States:

It will cost $595 and is available on Tesla’s website. You will have to have a Model 3 on your Tesla account to purchase the stalk retrofit kit.

It is interesting to note that despite Tesla’s strategy to remove the stalk with the new Model 3, which was released in early 2024, the company did not choose to make the same move with the new Model Y.

Advertisement

The new Model Y launched in the United States in early 2025, and Tesla chose to install a stalk in this vehicle.

It seemed as if the turn signal buttons were too much of a polarizing feature, and although the company technically could have given orderers an option, it would not have been the most efficient thing for manufacturing.

Continue Reading

News

Tesla Full Self-Driving v14.1 first impressions: Robotaxi-like features arrive

Tesla Full Self-Driving v14.1 is here, and we got to experience it for ourselves.

Published

on

Tesla rolled out its Full Self-Driving v14.1 yesterday, its first public launch of its most robust and accurate FSD iteration yet. Luckily, I was able to get my hands on it through the Early Access Program.

The major changes in FSD v14.1 were revealed in the release notes, which outline several notable improvements in areas such as driving styles, parking, and overall navigation. Here’s what Tesla outlined fully in its release notes:

  • Added Arrival Options for you to select where FSD should park: in a Parking Lot, on the Street, in a Driveway, in a Parking Garage, or at the Curbside.
  • Added handling to pull over or yield for emergency vehicles (e.g. police cars, fire trucks, ambulances).
  • Added navigation and routing into the vision-based neural network for real-time handling of blocked roads and detours.
  • Added additional Speed Profile to further customize driving style preference.
  • Improved handling for static and dynamic gates.
  • Improved offsetting for road debris (e.g. tires, tree branches, boxes).
  • Improve handling of several scenarios including: unprotected turns, lane changes, vehicle cut-ins, and school busses.
  • Improved FSD’s ability to manage system faults and recover smoothly from degraded operation for enhanced reliability.
  • Added alerting for residue build-up on interior windshield that may impact front camera visibility. If affected, visit Service for cleaning!

I wanted to try it for myself. My big must-dos were my complaints with v13.2.9, which included parking when arriving at a destination, Navigation when leaving a destination, and definitely a general improvement in the car traveling at an acceptable rate of speed, even when using the “Hurry” driving style.

Here’s what I noticed with the new Full Self-Driving v14.1:

Speed Profiles are More Realistic

I am driving on “Hurry” about 95% of the time when utilizing Full Self-Driving. In past versions, most notably v13.2.9, my Tesla would slowly reach the speed limit, and it would tend to hang out at about 1-2 MPH either above or below it.

My first observation with v14.1 was the vehicle’s tendency to get right up to speed and, since I was still on Hurry, drive slightly above the speed limit. It never got out of line; it traveled at speeds I would typically drive at manually.

Advertisement

I think this is a big improvement on its own, because I felt that I was pressing the accelerator too frequently in past FSD versions. Oftentimes, it just wasn’t going fast enough to justify the “Hurry” label; it felt more conservative and more like a student driver than anything.

Check it out:

This was among my favorite improvements, and it was the first thing I noticed as the car navigated me to the Supercharger, where my next positive is.

Navigating into parking lots, self-parking at Supercharger

One of the changes noted in the Release Notes was the addition of Arrival Options, which allows the car to select the appropriate parking situation. Since I was going to charge, the car had already chosen “Charger” as the parking option.

Pulling into a gas station or convenience store, especially during work days, can be stressful, as they are usually congested and full of foot and vehicle traffic. In past FSD versions, I have noticed the car being slightly “jumpy” and even hesitant to proceed through the lot.

Driving through parking lots was a noticeable improvement. It seems as if the car is much more confident in making its way through, while still being aware and cautious enough to safely navigate to the Supercharger.

Advertisement

It then backed straight into a Supercharger stall, which was recently repaired and is once again active. I was actually upset it chose this specific stall because it had been inactive for a while. However, Tesla got this stall back up and running, the car chose it, and backed into the spot flawlessly:

This was super cool to experience, and I think it is a testament to how hard the Tesla AI team has worked. CEO Elon Musk recently stated that FSD would enable automatic parking at Superchargers, which was really awesome to experience firsthand.

Advertisement

I decided to leave the Supercharger and go to an auto parts store to pick up some interior cleaner and some microfiber towels. I love keeping my Tesla clean!

I also thought it would be a great opportunity to see how it would react to another parking lot, how it would navigate it, and let it choose a parking spot. It did it all flawlessly:

Advertisement

I had zero complaints about everything here. All of it was done really well.

Making a choice after being caught in the middle of an intersection

I arrived at a tight intersection in Dallastown, PA, and what my car did next has catalyzed quite a conversation on X.

It proceeded out into the middle of the intersection as the light was green. It had to yield to oncoming traffic, and while waiting, the light turned yellow, then red.

Most people, including myself, would have turned right and proceeded through the intersection since the car was already past the line. However, FSD chose to back up and wait for the next light cycle, which I felt was also a more than acceptable option:

There are some conflicting perspectives on what it chose to do here. Some said they would have proceeded and would want FSD to also proceed. I can agree with that perspective, but I also think it is not the worst thing in the world to back up. In Pennsylvania, I couldn’t find the exact law that says what is right or wrong. Instead, I did see that a left turn on red is only feasible when you’re going from a One-Way street to another One-Way.

I’m not totally sure what is “correct” here, but I think either option is fine. I have personally done both, and I’ve seen other drivers do both. I was more than fine with the car doing this, and I was honestly impressed that it did.

Navigated a busy grocery store lot, found suitable parking

This is not the busiest my local grocery store gets, but it was still congested enough for me to be impressed.

Advertisement

FSD decided to do one loop in the parking lot before it found a spot that it felt was good enough for me. I was perfectly fine with where it chose to park, and I thought it did a really great job. I was impressed with how stress-free I felt, as I have noted in the past that parking lots are definitely an area where Tesla needs to improve.

I was happy with its performance:

Strange right turn signal as if it saw an emergency vehicle

This was the first bug I noticed with FSD v14.1. While traveling on a local road, it put the right turn signal on and approached the curb as if it was pulling over for an emergency vehicle or as if it was going to park on the street.

It then realized its mistake and proceeded:

I’m not super sure what caused this, but I was a tad bit confused. There were no police cars, ambulances, or anyone with flashing lights to my rear. There was a dump truck on the other side of the road, and I almost felt like the way it navigated “around” that was probably what triggered it.

Navigation is still making strange decisions

I’ve written about navigation and my discontent with some of its decisions. It seems v14.1 didn’t resolve much of anything with navigation, and it did a couple of things wrong.

The first was that it tried to take the illogical and pointless path out of the Supercharger. I wrote about this a few days ago, as FSD tried to take my car the wrong way.

Advertisement

It did it again, but I overrode the decision, and it was all okay:

This is a minor issue, but it is still pretty frustrating. Hopefully, the navigation will learn after performing this adjustment after enough times.

Advertisement

The next navigation issue was more frustrating than the Supercharger one, especially considering it completely ignored the route. The navigation had the vehicle very clearly heading straight, but out of nowhere, the right turn signal went on. I overrode it, but the car still turned right, ignoring the navigation completely:

I ended up taking over here and driving until I could get to a stop sign.

Advertisement

Final Thoughts

I am really impressed with all of the changes Tesla made with FSD v14.1, and while there were a handful of bugs, things were tremendously better than v13.2.9.

Continue Reading

Trending