News
SpaceX’s next Falcon Heavy launch may feature record-breaking center core landing
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.
Of Course I Still Love You will be positioned a record ~965km downrange. That's nearly 300km further that the previous greatest distance of 681km, set during the Eutelsat-117WB mission in June 2016. (The landing was a failure, with the booster running out of LOX!) https://t.co/RECKjMtd37
— Gav Cornwell (@SpaceOffshore) January 28, 2019
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.

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.
- Falcon 9 B1046 is processed in Port of LA shortly after its third successful launch and landing, December 2018. (Pauline Acalin)
- Falcon 9 B1047 is pictured here beneath an upper stage and satellite Es’hail-2 prior to its second launch. (Tom Cross)
- Falcon 9 B1048 returned to Port of Los Angeles aboard drone ship Just Read The Instructions after its first launch. July 27. (Pauline Acalin)
- Falcon 9 B1049 returned to Port of Los Angeles after its second successful launch and landing in four months. (Pauline Acalin)
- Falcon 9 B1050 is seen here just after liftoff. GPS III SV01’s Falcon 9 will feature no grid fins or landing legs. ☹ (Tom Cross)
- Falcon 9 B1051 and Crew Dragon vertical at Pad 39A. (SpaceX)
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.
- SpaceX’s Falcon Heavy Block 5 side booster is pictured here in Texas in November 2018. (Teslarati/Aero Photo)
- 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)
- SpaceX Facebook group member Joshua Murrah captured the second Falcon Heavy side booster to arrive in Florida in the last month. (Joshua Murrah, 01/17/19)
- The next Falcon Heavy’s first side booster delivery was caught by several onlookers around December 21. (Instagram)
- A booster – likely the next Falcon Heavy center core – was vertical at McGregor’s S1 static fire stand. (Instagram /u/tcryguy)
- A booster – either Falcon Heavy’s next center core or a new Falcon 9 – was vertical at SpaceX’s McGregor, TX test facilities on Jan 28. (Instagram /u/n75sd)
- A diagram from a recent SpaceX document offers an idea of what Falcon Heavy Block 5 will look like. (SpaceX)
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).
Looks like early liquid oxygen depletion caused engine shutdown just above the deck pic.twitter.com/Sa6uCkpknY
— Elon Musk (@elonmusk) June 17, 2016
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.
Elon Musk
Elon Musk reveals unfortunate truth of Tesla Full Self-Driving development
In a candid reply to a dramatic video of Tesla’s Full Self-Driving (FSD) system averting disaster, Elon Musk laid bare a harsh reality facing autonomous vehicle technology.
Tesla’s Full Self-Driving suite is one of the most significant technological developments in terms of passenger travel in decades, but it is not all sunshine and rainbows, even with major strides in safety, CEO Elon Musk revealed.
In a candid reply to a dramatic video of Tesla’s Full Self-Driving (FSD) system averting disaster, Elon Musk laid bare a harsh reality facing autonomous vehicle technology.
The clip shows a Model 3 traveling at over 65 mph on a foggy, rain-soaked highway when a pedestrian suddenly steps into traffic.
Full Self-Driving instantly detects the threat and swerves safely, preventing what could have been a fatal collision for both the pedestrian and the driver’s cousin.
Musk’s response was unequivocal:
“Tesla self-driving saves a lot of lives – the statistics are unequivocal. That doesn’t mean it’s perfect, of course.” Even with a projected 10x safety improvement over human drivers, FSD would still prevent roughly 90% of the world’s approximately one million annual auto fatalities. The remaining 10%—roughly 100,000 deaths—would expose Tesla to relentless lawsuits. Meanwhile, the vast majority of lives saved would go unnoticed. “The 90% who are still alive mostly won’t even know that Tesla saved them. Nonetheless, it is the right thing to do.”
This “unfortunate truth,” as Musk implicitly framed it, highlights a fundamental asymmetry in how society perceives safety technology. Human drivers cause the overwhelming majority of crashes through distraction, fatigue, or error.
Tesla self-driving saves a lot of lives – the statistics are unequivocal.
That doesn’t mean it’s perfect, of course.
Even when we improve safety 10X, saving 90% of the million lives lost in auto accidents every year, Tesla will still get sued for the 10% who did die. The 90%… https://t.co/OrNB1mO5eF
— Elon Musk (@elonmusk) April 6, 2026
Yet when FSD errs, the incident becomes headline news and a courtroom target. Prevented tragedies, by contrast, leave no trace.
Survivors simply continue their journeys, unaware of the split-second intervention that kept them alive. The result is a distorted public narrative that amplifies failures while rendering successes invisible.
We have seen this through various headlines throughout the years, including the mainstream media’s obsession with only mentioning the manufacturer’s name in the instance of an accident when it is “Tesla.”
Opinion: Tesla Autopilot NHTSA investigation headlines are out of control
The video’s real-world example underscores FSD’s current capabilities. In near-zero visibility, the system’s cameras and neural network reacted faster than any human could, demonstrating the life-saving potential Musk cites.
Tesla’s latest safety data already shows FSD (Supervised) performing significantly better than the U.S. average, with crashes occurring far less frequently per mile driven.
Still, regulatory scrutiny, liability concerns, and media focus on edge-case failures continue to slow widespread adoption. Musk’s frank admission suggests Tesla is prepared to push forward despite the legal and perceptual headwinds.
As FSD edges closer to unsupervised autonomy, Musk’s post serves as both a progress report and a reality check. The technology is already saving lives today.
The unfortunate truth is that proving it and scaling it responsibly will require society to value statistical lives saved as much as dramatic stories of those lost. In the race toward safer roads, perception may prove as formidable an obstacle as the fog and rain in that viral video.
News
Tesla Full Self-Driving v14.3: First Impressions
Tesla started rolling out Full Self-Driving v14.3 to Early Access Program (EAP) members earlier today, and I had the opportunity to see some of the improvements that were made from v14.2.2.5.
While a lot of things got better, and I truly enjoyed using Full Self-Driving again after being stuck with the widely confusing and frustrating v14.2.2.5, Tesla still has one major problem on its hands, and it has to do with Navigation and Routing. I truly believe those issues will be the biggest challenges Tesla will face with autonomy: the car simply going the correct way, not conflicting with what the navigation says, and taking the simplest and most ideal route to a destination.
Here’s what I noticed as an improvement with my first hour with v14.3. This is not a full review, nor is it reflective of everything I will likely experience with this new version. This is simply what I saw as a noticeable improvement from the past version, v14.2.2.5.
There is also a more streamlined version on X, available at the thread below:
Tesla Full Self-Driving v14.3 testing now: pic.twitter.com/9UuP11Fv9f
— TESLARATI (@Teslarati) April 7, 2026
Yellow Light Behavior is Significantly Better
On v14.2.2.5, I had so many instances of the car slamming the brakes on to stop at a yellow light when it was clearly the safer option to proceed through. There were several times when the car would be about 20 feet from the line, traveling at 15-20 MPH, the light would turn yellow, and it would slam the brakes to stop. I would nudge it through yellow lights constantly because of this by putting my foot on the accelerator.
The instances I’m talking about here would not have been close calls — the car would have likely moved through the intersection completely before the light would turn red.
On multiple occasions this evening, FSD proceeded through yellow lights safely, without hesitation or any brake stabbing. It was refreshing:
🚨 Here’s an EXCELLENT example:
v14.2.2.5 would have slammed the brakes and stopped at this stop sign. I would have tapped the accelerator to proceed.
You can see the light turns yellow and the car makes — in my opinion — the correct decision to proceed. https://t.co/hHMikimkbp pic.twitter.com/Iesta1OYoV
— TESLARATI (@Teslarati) April 7, 2026
This was a huge complaint with v14.2.2.5. Sometimes, it’s a safer option to go through a yellow light, especially when you have traffic behind you. It’s a great way to get rear-ended.
Parking Performance
I had four instances of parking, and FSD v14.3 really did a flawless job. I was very impressed with how solid it was, but also with how efficiently it moved into the spot. When there was traffic around with past versions, I usually chose to park manually just because FSD took its time getting into a spot. I don’t see that being an issue anymore.
I complained about parking a lot and shared several images on X and Facebook of those examples:
Still a few issues with parking on FSD v14.2.2.4 pic.twitter.com/BphvVWDPqe
— TESLARATI (@Teslarati) February 5, 2026
No issues with it this evening. 4/4. Here are two looks:
Highway Performance
FSD v14.3 passed the five cars shown in this image:
The sixth was 200-300 yards ahead of the fifth. In v14.2.2.5, FSD would usually stay in the left lane, especially on Hurry and Mad Max. It did not do that, as it instead chose to get back over in the right lane after passing the final car.
Speed was not much of a concern here, even though it was going 21 MPH over. Although it was fast, I did have a line of cars behind me traveling at the same speed, and FSD had just merged about a half mile prior, so I chose to let it continue.
There were no instances of camping in the left lane for extended periods of time. I do want to do more testing with the Speed Profiles because they were in need of some work with the previous version. I am starting to side with those who want a Max Speed setting, which was removed last year.
Navigation and Routing Still Need Work
I was heading back toward where I came from, so I turned “Avoid Highways” on to take a different way. This confused the Routing system, and instead of turning left, then right, as the Routing said, the car turned right, then indicated for another right, basically going in a big rectangle. The car ignored the second right-hand turn and continued straight. I ended up turning “Avoid Highways” off and letting the car pick the same routing option as what took me here.
I have truly complained so much about Navigation and Routing that I’m starting to feel sort of bad. It is obviously such a massive challenge for some reason, but I am confident it will improve. I recall seeing Tesla hiring someone for this role a few months back, so perhaps there is hope for it to get better.
Smarter Behavior When Approaching Exits/Routing
This probably should be grouped in with Highway Behavior, but I wanted to highlight it on its own.
The highway exit pictured was always frustrating for v14.2.2.5. In the Hurry speed profile, I have seen it try to execute passes on multiple cars with as little as 0.6 miles to spare before taking the exit.
With three cars ahead of it, it chose to reduce speed and just wait until the exit. It was refreshing to see an improvement here, so I hope this behavior persists. Sometimes there’s just no reason to pass when you’re less than a mile from getting off the highway anyway.
Larger Visibility Warnings
Tesla seems to have increased the size of these “Camera Visibility Limited” warnings. Previously, they were just small thumbnails:
🚨 The warnings of “Camera Visibility Limited” appear to be larger with v14.3
Previously, it was a small thumbnail. Haven’t seen it this magnified before. https://t.co/iKJLsZ8P4Q pic.twitter.com/qRWwFyIZNd
— TESLARATI (@Teslarati) April 7, 2026
Stop Sign Behavior
This is probably the biggest improvement of all, because how it behaved at Stop Signs in v14.2.2.5 was so incredibly terrible and disruptive to the flow of a busy intersection.
There are several four-way, all-stop intersections near me. In the past, FSD would stop well behind the Stop Sign or the white-painted line on the road. It would then inch forward, stopping again at this line, essentially making two stops at a single intersection.
If there is visibility, I don’t truly care where FSD stops, as long as it stops once. Stopping twice just isn’t ideal or logical. I can’t imagine many humans would do it, I know I wouldn’t.
I didn’t have that issue this evening:
🚨 Here’s a look with some commentary – Previously, FSD would stop where it did in this video, then again at the white line, before proceeding. https://t.co/xwyVGMy28y pic.twitter.com/MObgUa7DoA
— TESLARATI (@Teslarati) April 7, 2026
This was pretty tight, too, in the sense that both my car and the other one got to the intersection at the same time. FSD may have stopped first, but the other vehicle was probably around the same point that I was when FSD decided to stop. I was happy to see the assertiveness to proceed; it felt like it was ideal to just go through. I was happy it didn’t stop a second time up at the line. I’d be fine if it stopped at the line, as long as that was the only stop it made.
News
Tesla Full Self-Driving v14.3 rolls out: here’s what’s new
We are in EAP and will be on the road with v14.3 in the coming hours, so we’ll have a lot of things to discuss over the next few days, especially coming from v14.2.2.5, which I called the most “confusing” FSD release of all time.
Tesla has officially started rolling out Full Self-Driving v14.3 to Early Access Program (EAP) members, and there are a lot of new improvements.
We are in EAP and will be on the road with v14.3 in the coming hours, so we’ll have a lot of things to discuss over the next few days, especially coming from v14.2.2.5, which I called the most “confusing” FSD release of all time.
🚨 Tesla Full Self-Driving v14.3 is here and it is coming with so many new features
Looks like there will be some MAJOR improvements to the general performance.
Truly seems like it will be significantly different than v14.2 pic.twitter.com/mhdfBLuDup
— TESLARATI (@Teslarati) April 7, 2026
Tesla brought out a lot of improvements, according to the v14.3 release notes, which list a vast number of fixes, new features, and new capabilities.
Here’s what Tesla’s release notes for the v14.3 release state:
- Improved parking location pin prediction, now shown on a map with a P icon.
- Increased decisiveness of parking spot selection and maneuvering.
- Rewrote the Al compiler and runtime from the ground up with MLIR, resulting in 20% faster reaction time and improving model iteration speed.
- Enhanced response to emergency vehicles, school buses, right-of-way violators, and other rare vehicles.
- Mitigated unnecessary lane biasing and minor tailgating behaviors.
- Improved handling of small animals by focusing RL training on harder examples and adding rewards for better proactive safety.
- Improved traffic light handling at complex intersections with compound lights, curved roads, and yellow light stopping – driven by training on hard RL examples sourced from the Tesla fleet.
- Upgraded the Reinforcement Learning (RL) stage of training the FSD neural network, resulting in improvements in a wide variety of driving scenarios.
- Upgraded the neural network vision encoder, improving understanding in rare and low-visibility scenarios, strengthening 3D geometry understanding, and expanding traffic sign understanding.
- Improved handling for rare and unusual objects extending, hanging, or leaning into the vehicle path by sourcing infrequent events from the fleet.
- Improved handling of temporary system degradations by maintaining control and automatically recovering without driver intervention, reducing unnecessary disengagements.
Tesla also listed a handful of future improvements as well:
- Expand reasoning to all behaviors beyond destination handling
- Add pothole avoidance
- Improve driver monitoring system sensitivity with better eye gaze tracking, eye wear handling, and higher accuracy in variable lighting situations
CEO Elon Musk has said that v14.3 could be “where the last big piece of the puzzle finally lands.” We have high expectations for this release because, in a lot of ways, v14.2’s final version was extremely disappointing and seemed to be a regression more than anything.
Nevertheless, Full Self-Driving v14.3 is going to be quite an interesting test, considering this is also the first time Musk has stated it will feel like the car will be “sentient.”
Reasoning will be a bigger piece of the puzzle with this release, although there were some elements of it in v14.2.
Tesla AI Head says future FSD feature has already partially shipped
We plan to travel plenty of miles with it over the next few days, so we’ll keep you posted on what our thoughts are.















