News
SpaceX fairing recovery vessel Mr. Steven’s owner abruptly files for bankruptcy
The legal owners of SpaceX’s sole fairing recovery vessel are in dire financial straits, signaled by business owner Steven Miguez’s decision to file for bankruptcy as a last chance of protecting Seatran Marine, a company which owns and leases eight utility vessels known as crew boats.
Mr. Steven, leased by SpaceX in late 2017, is one of those crew boats, although he has since been dramatically modified to support a series of consecutively larger arms, nets, and other various components in hopes of eventually catching Falcon 9 payload fairings out of the air. While there is most likely no serious risk of SpaceX actually losing access to Mr. Steven, this development still raises the question of what will happen to the ship in the near and more distant future.
The bankruptcy paperwork filed is chapter 11 – "proposing a plan of reorganisation to keep a business alive." The paperwork protects Mr Steven from foreclosure for now so there is no immediate change to anything.
— Gav Cornwell (@SpaceOffshore) November 21, 2018
As indicated in the tweet above, the ultimate outcome – at least for the time being – is simple uncertainty, as Chapter 11 bankruptcy filings will prevent Miguez from having to foreclose on Mr. Steven in the short term. If the Miguez family can rapidly find a solution for its money troubles, all could proceed unchanged. However, with all due respect to the owners and to Seatran Marine’s employees, Chapter 11 bankruptcy simply is not easily undone and is generally a last resort to be used only after all alternative solutions have been exhausted. Chapter 11 bankruptcy proceedings can take anywhere from a few months to several years to complete, tending to take longer as the scale and complexity of the filing party grows.
Making the best of a bad situation
Leased by Seatran to operator Guice Offshore (GO), SpaceX’s primary fleet manager on both coasts, GO (and thus SpaceX) had contracted to pay at least $3300 a day to use Mr. Steven, although that contract expired in October 2018. The new terms are unclear and it’s unknown if a replacement contract has yet to be signed.
Given the situation at hand and despite the sad financial circumstances facing the vessel’s owners, SpaceX may be in the best position yet to purchase Mr. Steven outright, assuming the company expects to continue attempting Falcon fairing recoveries for the indefinite future. In 2015, namesake Steven Miguez took out a $22.5M loan to cover Mr. Steven’s construction costs, offering a rough price ceiling for the modern, high-performance Fast Supply Vessel (FSV). While the most obvious interested buyer would be GO itself, it’s unlikely that the company has a sum of that size to offer, meaning that GO would need to take out its own loan to acquire the ship.
-
- Mr. Steven took to sea to test out a new recovery-related appendage – purpose unknown – on November 12. (Pauline Acalin)
-
- After an afternoon attempting to catch Falcon fairings dropped by a helicopter, Mr. Steven returned to port on Nov. 14. (Pauline Acalin)
-
- (Pauline Acalin)
-
- One half of SpaceX’s Iridium-6/GRACE-FO just moments before touchdown on the Pacific Ocean. (SpaceX)
-
SpaceX, on the other hand, quite literally just closed a debt funding round of $250M, terms unknown, leaving the company more than enough liquid capital to enable a cash transaction assuming there is some interest in becoming Mr. Steven’s legal owner. SpaceX already owns its two operational autonomous spaceport drone ships (ASDS) outright and has extensively modified Mr. Steven to support fairing recovery, quite literally building its prototype recovery apparatus around the rented vessel. As the vessel’s new owner, SpaceX could likely keep contracting to GO for general operations and support, perhaps even continuing to lease Mr. Steven to GO to create as few waves as possible.
By selling Mr. Steven outright, Miguez could likely acquire more than enough funds to preserve Seatran Marine and its subsidiaries long enough to recover his financial footing and return his companies to a stable state.
Business as usual?
In the meantime, it does not appear that these unfortunate legal issues have had a tangible impact on GO and SpaceX’s near-term ability to operate Mr. Steven. Around November 20th, SpaceX and GO crew performed the most recent of a series of Falcon fairing recovery tests, dropping a half from a helicopter to provide Mr. Steven a comparatively controlled environment to practice catches. Earlier this month, CEO Elon Musk appeared to imply that Mr. Steven would not attempt to catch Falcon 9’s fairing halves following the West Coast launch of SSO-A, at the time scheduled for November 19th.
Since then, SSO-A’s flight-proven Falcon 9 launch has slipped a full two weeks thanks to a combination of additional inspections and bad weather, now targeting launch NET December 2. It’s a stretch, but there is at least a slight chance that SSO-A’s excessive launch slips could mean that Mr. Steven will be able to attempt fairing recovery after all, at least per Musk’s suggestion that SpaceX would “try again next month”.
https://www.instagram.com/p/BqtGWFxADOk/
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.
-
Elon Musk’s massive Terafab project, which will be the first true conglomeration between each of his major entities, is set to get its final location soon, the CEO said on Tesla’s recent earnings call.
“The Terafab, we expect to announce a location soon, and provide more details about our plans in that regard. We’ll leave that to the product, the launch announcement rather than try to squeeze it into an earnings call,” Musk said last Wednesday.
Tesla Terafab set for launch: Inside the $20B AI chip factory that will reshape the auto industry
Terafab was announced by Musk back in March and was essentially a massive, vertically integrated semiconductor manufacturing project that would provide all the chips the three companies needed for their AI initiatives without needing third-party companies.
The plant will produce over 1 terawatt of AI compute each year, and will help back up projects like Optimus, Full Self-Driving, and other AI-based projects that Musk’s companies are working on.
In April, less than a month after the project was launched, Intel announced it would join the project, contributing manufacturing expertise and consulting to Terafab as a whole. Intel is one of three chip manufacturers that produce sub-5 nanometer chips at scale. TSMC and Samsung are the other two.
However, there was no true indication of where Terafab would end up, but most believe it will likely be somewhere in Texas. Business Insider has reported that SpaceX plans to build out Terafab in Grimes County, Texas, but this is unconfirmed.
-
Musk confirmed recently that it would not be on Giga Texas property, as it is simply too large.
The sheer scale of TERAFAB is going to be insane.
Elon said it wouldn’t be suitable for anywhere on Giga Texas property because it’s too big:
“We couldn’t possibly fit the Terafab on the GigaTexas campus. It will be far bigger than everything else combined there.
Several… pic.twitter.com/79GbhNNuf4
— TESLARATI (@Teslarati) March 23, 2026
Terafab holds much of Musk’s grand ambitions for the future within its construct. It holds so much responsibility for the future and the biggest projects that Musk’s companies can imagine.
-
“I think this is a very big announcement and it deserves to have its own day in the spotlight and not be squeezed into an earnings call,” he said. “I do think Terafab is going to be an amazing initiative and a necessary one, and one without which we will be constrained in our ability to scale Optimus production, because we simply won’t have enough AI chips.”
He continued by stating that Terafab is necessary for scaling Optimus, which Musk said could be the biggest product of any kind of all time. “It’s crucial to solve that, and we’ll have to solve memory, logic, and packaging in order to scale Optimus.”
SpaceX performed a secret test on a specific portion of Starship with its recent 13th test flight last week, CEO Elon Musk revealed.
Starship’s 13th test flight took place last Friday, and in many aspects, it was one of the most overwhelmingly successful launches in the project’s history.
All of the mission objectives were met without incident, both the Super Heavy Booster and Ship managed to perform safe splashdowns in the Gulf of America and the Indian Ocean, respectively, and the deployment of Starlink satellites came and went without any complications.
— Elon Musk (@elonmusk) July 25, 2026
However, there was more on the agenda for SpaceX with Flight 13. Musk revealed an internal test of the ship’s heat shield tiles, as the space exploration company wanted to push them to the limits after previous issues.
Many noticed that Starship’s initial launch seemed to be more accelerated than normal, and that was not a mistake. Musk revealed that SpaceX decided to give Flight 13 an intentionally aggressive acceleration rate in an effort to test how well the tiles would remain attached to the ship:
-
This flight intentionally had much higher acceleration to test how well the heat shield tiles would remain attached at high dynamic pressure.
Test was successful.
— Elon Musk (@elonmusk) July 25, 2026
SpaceX had issues with some of the heat shield tiles remaining attached early on in the Starship program. The first six test flights presented some kind of anomaly with them, so the company’s big focus with them was to figure out a way to keep them intact through the duration of the flight.
Things truly improved as Flight 10 showed that ceramic tiles generally stayed attached to the ship far better due to refined attachment, as SpaceX utilized pins instead of adhesives. Flights 10 through 13 truly showed some clear progress with the heat shield tiles, and this latest test seems to be where some real progress was noticed, especially by Musk.
The 13th Starship launch last Friday was the second with Starship V3, SpaceX’s latest and greatest iteration of the spacecraft. Goals and ambitions are getting even grander as the project continues to progress. Musk has already hinted that SpaceX will likely try to catch Starship with Flight 14.
-
Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
Musk’s massive Terafab project will get final location soon
