News
Firefly nears second orbital launch attempt as US forces Ukrainian founder to divest
While the rocket startup he is responsible for resurrecting is preparing for a second orbital launch attempt, a Ukrainian multimillionaire – an entrepreneur, businessman, and the founder of Firefly Aerospace – has once again been forced to take extreme actions by the US government.
Resurrected in 2017 after going bankrupt and ceasing operations the year prior, Firefly is a private launch provider based out of Austin, Texas and founded by Maxim Polyakov and former CEO Tom Markusic. Polyakov has supported the company since its second inception, privately funding the startup with over $200 million earned through success in Ukrainian tech industries. With those contributions, Polyakov was able to singlehandedly resurrect the startup from bankruptcy and continue the development of an even more ambitious Alpha launch vehicle.
For the last two years, though, Polyakov has been under scrutiny from US government officials, who’ve objected to Polyakov – a Ukrainian and UK citizen – having control over the company, with fears that the launch technology developed by the company could make its way back to Ukraine and poses a national security threat.
The update that's rolling out to the fleet makes full use of the front and rear steering travel to minimize turning circle. In this case a reduction of 1.6 feet just over the air— Wes (@wmorrill3) April 16, 2024
In late 2020, Polyakov quietly stepped down as chairman and withdrew from Firefly’s day-to-day operations in the hopes of killing the controversy and giving the startup a better chance at being awarded government contracts. Firefly’s board of directors includes many former U.S government officials, including Deborah Lee James, former secretary of the Air Force, and Robert Cardillo, former director of the National Geospatial Intelligence Agency.
However, officials were not satisfied with Polyakov simply stepping down from operations, indicating they want him to have less ownership in the company as well. In November 2021, just two months after Firefly’s inaugural flight test, Polyakov received a letter from the Committee on Foreign Investment in the U.S (CFIUS). This letter expressed these ongoing concerns and asked that he, along with his investment company, Noosphere Venture Partners, sell their stock in Firefly; which amounted to over 50% stake in the company. Because of this request, Firefly halted their operations at Vandenberg Air-force Base.
Before halting launch operations, Firefly claimed to be on track for another Alpha launch as early as January 2022. Firefly’s first launch on September 2nd, 2021 ended in failure around two minutes after liftoff due to a premature engine shutdown. Jason Mello, president of Firefly Space Transportation Services, stated in an interview that fixing the problem responsible for the failure was “fairly easy and straightforward.”
On February 16th, 2022 Polyakov revealed that the United States government had once again gone on the offensive, this time forcing him to fully and permanently cede any involvement in his company. He posted the following statement on Facebook:
-
Polyakov revealed that he chose to sell his 58% stake in the company to co-founder and CEO Tom Markusic for $1 USD – a selfless act given that selling his stake for nothing all but guarantees he will never recoup a cent of the several hundred million dollars he invested in Firefly.
Previously, Polyakov expressed how excited he was to turn Firefly into a massive aerospace company that both the United States and Ukraine could be proud of and benefit from. “During the Soviet era, Ukraine produced some of the world’s best rocket and engine technology, but much of those inventions have languished in recent years due to lack of investment. The hope was that Firefly could pair its best engineers from the U.S. and Ukraine together to make a fleet of large rockets capable of taking many satellites into orbit and, later on, missions to the moon. Polyakov wanted the U.S. to gain access to Ukrainian expertise, while also finding a way to boost the prospects of Ukrainian aerospace engineers, he has said.” (Bloomberg)
It is speculated that the US government’s sudden and extreme requests came because of concerns over the rising tensions caused by Russia’s increasingly unstable posturing and recurring threats of invasion. Even though Ukraine is friendly with the United States, concerns of conflict with Russia may have increased worries about what might happen to technology developed inside of the country. Ukraine, a sovereign nation, has been forced to increase security along its borders as fear of a Russian invasion grows.
Despite the recent legal and organizational setbacks and drama caused by the US government, Firefly has been doing extremely well from a technical standpoint. The company recently shared a video of the successful static fire testing of both stages of the second Alpha rocket, indicating that it could be ready for flight in the very near future. Even though Polyakov was forced to abandon his aerospace startup, it’s never been more clear that his investment not only saved Firefly but raised the company closer to success than it’s ever been before.
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.
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.
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.
Tesla briefly offered this Robotaxi part for your personal car
Tesla Robotaxi gets sweeping but polarizing change
