News
SpaceX tracks towards first launch of 2019 with flight-proven Falcon 9 static fire
SpaceX has completed a Falcon 9 static fire test ahead of the company’s first launch of 2019, kicking off what is looking to be a truly jam-packed year for Falcon 9 and BFR. Most important, of course, is SpaceX’s primary business and main sources of revenue – safely and reliably launching customer satellites, payloads, and – soon – astronauts into orbit.
Previously tasked with launching heavy communications satellite Telstar 18V in September 2018, Falcon 9 B1049 is now set to launch an arguably historic mission for both SpaceX and customer Iridium, the eighth and final contracted launch of the upgraded Iridium NEXT satellite communications constellation.
Static fire test of Falcon 9 complete. Working with customer to determine best launch opportunity to complete the Iridium NEXT constellation; will announce targeted launch date once confirmed.
— SpaceX (@SpaceX) January 6, 2019
Struck all the way back in June 2010, Iridium’s decision to award the full NEXT constellation launch contract to SpaceX less than two weeks after Falcon 9’s first and only launch may well be the greatest calculated leap of faith in the history of commercial spaceflight. SpaceX did admittedly offer an unbeatable price ($492M for eight launches, $61.5M per launch) that may have allowed Iridium to afford a new constellation in the first place, but the risk Iridium took was truly immense at the time.
Originally launched between 1997 and 1998, the first Iridium constellation became and still remains the only satellite communications constellation in history to offer global and persistent coverage anywhere on Earth, allowing those with Iridium devices to guarantee connectivity no matter where they are. To some extent, the original constellation has become a subtle but omnipresent backbone of a huge variety of ventures, companies, and services, ranging from marine vessel tracking and emergency response to the go-to solution for those heading far off the beaten path. As just one small example, SpaceX’s large fleet of sea-going vessels and its cross-country transport infrastructure both rely on Iridium for streamlined company-wide movement tracking, making life considerably easier for logistics and planning teams.
@SpaceX #falcon9 vertical at SLC-4. Iridium NEXT-8 slated for 01/08 from #VandenbergAFB. #spacex #iridium pic.twitter.com/uJBIgG5Lrp
— Brian Sandoval (@sandovalphotos) January 6, 2019
Iridium’s decision to use SpaceX for its NEXT constellation likely also gave SpaceX a massive stature boost, taking it from the company with just a handful of commercial contracts that had failed three of its last five launches to the company that secured what was at the time the largest single commercial launch contract in history. Alongside NASA’s Commercial Orbital Transport Services (COTS) and Resupply Services (CRS) commitments (~14 launches as of 2010), Iridium NEXT raised SpaceX’s commercial manifest from perhaps 2 missions to ~10 while also taking the value of those contracts from an almost negligible sum to well over half a billion dollars.
Although SpaceX and Iridium originally planned for launches to take place over a roughly 24-month period stretch from 2015 to 2017, unplanned technical delays and a duo of catastrophic Falcon 9 failures (CRS-7 and Amos-6) in 2015 and 2016 ultimately pushed Iridium NEXT’s launch debut back several years. Despite those immense hurdles and a range of smaller issues, SpaceX and Iridium were finally able to begin launching satellites in January 2017 and have continued to consistently do so every 3-4 months since then. Aside from one partial NASA rideshare mission that featured five NEXT satellites in May 2018, all seven launches have placed ten NEXT satellites (weighing approx. 10,000 kg or 22,000 lb total) in a variety of low polar orbits without a single known hitch.
- A rare glimpse inside SpaceX’s SLC-4 rocket integration hangar, January 2017. (SpaceX)
- Iridium-7’s Falcon 9 payload fairing, July 2018. (Pauline Acalin)
- LEO communications satellites like Iridium’s NEXT constellation feature totally flat panels of phased array antennas, capable of forming beams digitally. (Harris)
Falcon 9 enters the era of reusability
Closely following SES, NASA, and SSL (BulgariaSat), Iridium also became the fourth commercial entity to launch on a flight-proven Falcon 9 rocket for the launch vehicle’s fourth flight-proven mission ever. Iridium-8 will become the fourth constellation launch to fly aboard a sooty Falcon 9 rocket, meaning that a full 50% of the next-gen satellites will have launched on reused rockets, easily one of the coolest bragging rights ever. Currently standing at 65 NEXT satellites in orbit and rapidly nearing operational status, Falcon 9 B1049 and a fresh upper stage will (fingers crossed) place the last ten satellites in orbit to complete the constellation’s last plane and seal the last gap in its perfect global coverage.
Although NEXT would have been valuable for the sole reason that its predecessor satellites are now 5-10 years past their designed lifespans, NEXT will also serve to dramatically increase Iridium’s overall bandwidth, slash concurrent user bottlenecks, and provide a platform for new services like Aireon, which hopes to become the first operator of a truly commercial aircraft tracking service with global satellite-based coverage.
- Falcon 9 B1041.2 seen before launching Iridium-5. (Pauline Acalin)
- Iridium-1’s successful and scenic landing on Pacific drone ship JRTI, January 2017. This could be an increasingly rare occurrence in the Pacific, thanks to SpaceX’s new land-based landing zone. (SpaceX)
- 2017 saw SpaceX recovery 10 Falcon 9 first stages, 5 by sea. (SpaceX)
All things considered, it will be hugely bittersweet to watch Iridium and SpaceX’s direct relationship come to a close with the launch of Iridium-8. Aside from nine additional on-orbit spares once all 75 are launched, Iridium will also have a complement of six more spares that will be kept in storage on the ground until they are required in orbit. If or when those times come, SpaceX will be able to compete with other launch providers for the opportunity to carry maybe one or two Iridium satellites – likely as rideshare payloads – into orbit sometime in the future.
Iridium open to rideshares for spare satellite launches https://t.co/ino39oWCHw pic.twitter.com/56PTcaEMW3
— SpaceNews (@SpaceNews_Inc) January 4, 2019
In the meantime, stay tuned for Iridium-8’s official launch time and date, likely to be announced by SpaceX sometime within the next 24-48 hours.
For prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket recovery fleet check out our brand new LaunchPad and LandingZone newsletters!
News
Tesla briefly offered this Robotaxi part for your personal car
Tesla briefly offered one Robotaxi part in its Parts Catalog for your personal car, only to remove it just a short time after it was first noticed.
Tesla’s Robotaxi camera washer apparatus was briefly available for purchase on the company’s Online Parts Catalog. The camera washer was first noticed on Model Y Robotaxi vehicles about six months ago in Austin.
🚨 Tesla looks to have installed Camera Washers on the side repeater cameras on Robotaxis in Austin
pic.twitter.com/xemRtDtlRR— TESLARATI (@Teslarati) January 23, 2026
First noticed by Not a Tesla App, the Camera Washer entries appeared for the new “Juniper” Model Y under a category called “Halo,” which has also now disappeared. Interestingly, Halo probably is related to Tesla’s internal “Project Halo,” which was a project that aimed to retrofit customer-owned Model Ys into functional Robotaxis.
This hardware addition would likely be required for the vehicle to operate as a Robotaxi, as the Camera Washer seems to be a non-negotiable part of the vision-based system Tesla utilizes for self-driving efforts.
However, this part has since been removed and is no longer visible on the EPC.
Now the true question lingers: Why would Tesla add this Camera Washer to the Model Y parts catalog? Is it planning to make it available for owners to utilize on their own cars for personal use, or will it become a prerequisite for Robotaxi operation in customer-owned cars?
While discussing the upgrade options for Hardware 3 vehicles during the Q1 Earnings Call, Tesla CEO Elon Musk had said that the company could establish small, satellite shops that would upgrade cameras and self-driving computers. Perhaps this same strategy could be utilized for vehicles that want to be included in Robotaxi but do not have the correct hardware.
AI4 is currently represented as capable of unsupervised self-driving, and the same was said about HW3 at one point, only for Tesla to admit last quarter that it would, unfortunately, not be possible. Perhaps AI4 vehicles might need this camera washer as a prerequisite, just as HW3 cars will need that camera and computer upgrade.
This could be the first hint of that’s where we are headed.
News
Tesla Robotaxi gets sweeping but polarizing change
Tesla has started rolling out a broader change to the ride experience for its Robotaxi fleet by silencing turn signals, but the change is certainly polarizing.
Tesla has generally made it clear that its purpose-built ride-hailing platform, Robotaxi, will cater to the rider in nearly every way possible. This includes having climate preferences, music, and other personal settings loaded up in the car as the rider enters.
But Tesla is taking it a step further by muting turn signal chimes altogether, a change that appears to be a way to make the ride more peaceful:
Tesla has finally turned off the blinker/turn signal noises in their Model Y Robotaxis.
This is a small update, but will definitely be noticeable for riders. It didn’t really make much sense to leave the turn signal sound on when it’s Unsupervised. pic.twitter.com/ITwx60PAMO
— Sawyer Merritt (@SawyerMerritt) July 27, 2026
However, there are a handful of people who are not thrilled about this change. Turn signals are a conditioned part of the human mind for those who ride in a car regularly.
Taking a turn without one feels strange and odd, and not hearing it click while activated could set off some alarms for riders, who might use the noise as confirmation that other drivers know of their intention to turn.
I kind of like it being on, threw me off when riding with Zoox who has had it disabled
— Dan Burkland (@DBurkland) July 27, 2026
Turn signal noises are still audible in customer cars, so if you use FSD in your personal vehicle, you will still hear the turn signal.
The move is certainly one that is unique, but not one that separates it from other ride-sharing services. In a normal car, the clicking sound confirms to the driver that the blinker is active. In a fully driverless Robotaxi, that feedback serves no purpose for passengers, other than peace of mind.
News
Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
Tesla released Full Self-Driving version 14.3.6 last week, and after what was potentially one of the best FSD releases in v14.3.5, there has been a bit of a regression. While there are some bright spots, the changes made to v14.3.6 seem to have backtracked some behaviors.
Overall, it is hard to really complain about FSD in any sense; it has revolutionized how I travel literally anywhere. According to my self-driving app, the last time I went a day without using it was 59 days ago.
However, I think it’s also important to recognize when things are just plain bad with FSD. There are times it does truly mind-boggling things, and I’ll dive into those here. Additionally, I only had these issues on local roads, not on highways. Highway operation, generally, is always incredible other than the occasional complaint about speed or left lane camping.
With those things being said, my personal experience may not represent others’ experiences. A handful of people have said they have had a similar experience on v14.3.6, while others have said it is more than normal.
Turning Hesitancy, Inaccuracy
I’ve noticed more inaccuracy turning into multi-lane stretches of road than in any version I can remember. I’ve had at least three instances of FSD turning into a stretch of roadway that has two or more lanes, and not selecting a lane confidently as it has in past versions.
I think Tesla FSD v14.3.6 is a regression from previous .3 branches
This version in particular has been incredibly hesitant, jerky, and indecisive at times. There’s actually been two drives that I have decided to not used FSD for the remainder of the trip. These were local trips… pic.twitter.com/YobHDOKRS6
— TESLARATI (@Teslarati) July 26, 2026
Instead, the car will drive over one of the dashed road lines, and the steering wheel will jerk back and forth before picking the lane. It should be said that it has always picked the correct lane when choosing based on the navigation, but it is still very indecisive. The steering wheel jerking is reminiscent of some of the later versions of v13.
I admit I really hate to see the steering wheel jerking come back. However, I think when Tesla releases v14.3.7, it won’t be present. When there are occurrences of it in FSD versions, it is usually resolved by the following release.
FSD Disregards Manual Turn Signals
This is my biggest bone to pick with FSD other than Navigation issues, but this one seems like it would be such an easy fix.
If Tesla is going to put the word “Supervised” on the end of “Full Self-Driving,” then when I tell the car to do something, it should do it. If I input an increase in speed by pressing the accelerator, the car will immediately respond. It does not disregard my input because it feels it is traveling at the right speed.
FSD should never disobey and turn off turn signals that the driver inputs. Trying to direct the car into the correct lane, I had initiated the left turn signal not once, not twice, but three times, with the car turning it off all three times and continuing in a lane that would end in just one block. The only solution at this point would be to zipper merge.
This goes back to the fact that self-driving’s biggest bottleneck might be rider preference. A zipper merge might have been more than reasonable, might have saved me time that I spent sitting through an additional light cycle, and might be something many drivers would do. I was in no hurry, I traditionally do not try to zipper merge because it feels inconsiderate, and lastly, the car should have just followed my input.
This caused me to disengage and drive manually the rest of the way home. Sometimes I just do not need FSD to try to pass every car it can at intersections.
Bird Braking is a Thing of the Past
The big complaint with recent versions of Full Self-Driving has been what we’ve coined as “bird braking,” which is when the car will brake suddenly as a bird flies past.
There have been zero issues with this so far in v14.3.6, which is an excellent improvement.
FSD Might Already Be Taking Note of Driver Preferences
Another thing I have noticed over the past few days is that v14.3.6 seems to already be taking my preferences with navigation into account.
This is something that is supposed to be rolling out with the Summer Update, but I have a hunch it’s already present and might have been included in this v14.3.6 build. On Friday, FSD pulled into an entrance to a local convenience store that it had never attempted to go into before.
Typically, I manually pull into this entrance because it avoids heavy cross traffic at the main entrance. FSD has always chosen that congested main entrance.
I don’t want to get anyone excited but my Tesla running FSD v14.3.6 just:
✅ Pulled into an entrance at my local Sheetz that I routinely pull into manually but FSD never has entered
✅ Pulled into my assigned parking space at home despite many other spots being vacant https://t.co/ZUShvknTWO pic.twitter.com/83O5a2S0eh
— TESLARATI (@Teslarati) July 24, 2026
Additionally, FSD has pulled into my assigned parking spot at my townhouse community on multiple occasions with this release. This is something that used to happen ocassionally, but not consistently.
It also navigated back to the same convenience store last night, drove through crazy cars scrambling to gas pumps, navigated out of the parking lot correctly, drove me home, and, once again, parked in my assigned spot.
As previously stated, this release just seems to have a few things that need to be brought to Tesla’s attention, and also to make others who use FSD aware of some things that I’ve experienced. I look forward to the next release that will remedy these issues, just as Tesla has always done in the past.







