News
US Air Force issues RFP for massive rockets, SpaceX’s BFR could be one of them
The US Air Force has released a Request For Proposal (RFP) that hopes to fund the development of multiple heavy-lift rocket prototypes to launch no later than 2021. The USAF specified on October 5 that it wants to partially fund prototype development for at least three promising US-sourced launch vehicles, while maintaining the options to select none of the proposals or even more than three. The purpose of these broad strokes is to provide the Air Force and US military in general redundant access to space by way of “at least two domestic…launch service providers” capable of meeting National Security Space (NSS) requirements.
However unlikely it may seem, NASA experienced this firsthand when two of the vehicles it funded, SpaceX’s Falcon 9 and Orbital-ATK’s Antares, experienced complete failures within less than a year of each other. Both vehicle failures destroyed supplies intended for the International Space Station and forced NASA to rely on Soyuz missions to fill the gaps created while producing considerable uncertainty for the agency. By funding two or more independent launch vehicles, the Air Force would lessen the impact of such failures, and this assured access is rightly perceived as an invaluable commodity in the military.
-
- .While SpaceX’s own visualizations are gorgeous and thrilling in their own rights, Romax’s interpretation adds an unparalleled level of shock and awe. (SpaceX)
-
- A render of Blue Origin’s larger New Glenn vehicle. (Blue Origin)
-
- The only current render of OATK’s Next Generation Launcher. (OATK)
Several details in the latest proposal make it relatively easy to name the obvious prospective applicants. The payload requirements necessitate heavy lift or even super-heavy lift launch vehicles capable of placing anywhere from 5,000 to 37,500 pounds into a variety of Earth orbits, ranging from low Earth orbit (~500 mi) to direct transfer geostationary orbits (~19,200 mi). This narrows the field considerably, pushing out all smaller-scale vehicles. Also telling is a requirement that proposed launch vehicles make use of rocket propulsion systems (RPS) already funded for development by the USAF if at all possible.
Considering the inherently complex and difficult process of developing massive rockets, initial launch dates no later than 2021 (or 2024) likely mean that the vehicles being considered must already be under some level of serious development. This leaves us with four possible options in the US, undoubtedly not a coincidence given the RFP’s explicit goal of facilitating the creation of “at least three…prototypes as early as possible” and “at least two domestic…launch service providers”. These four vehicles are SpaceX’s BFR, Blue Origin’s New Glenn, ULA’s Vulcan, and Orbital-ATK’s NGL, all of which already have tentative inaugural launch dates clustered from 2019 to 2022. Perhaps even more revealing, all four vehicles can be expected to utilize several rocket propulsion systems (rocket engines) already funded by the Air Force, namely SpaceX’s Raptor, Blue Origin’s BE-4 and BE-3U, and Aerojet-Rocketdyne’s AR-1.
While the development of BE-4 and AR-1 have been somewhat veiled, SpaceX’s Raptor engine has publicly made a great deal of progress. As discussed during Elon Musk’s IAC 2017 presentation, the company has conducted an array of successful tests with its subscale Raptor program, to the tune of 42 individual hot-fire tests totaling more than 1,200 seconds. Musk also reported that the only thing preventing tests longer than 100 seconds was the size of the propellant tanks at the test stand, a genuinely impressive accomplishment if true. The sticking point, however, is how much difficulty SpaceX will have as they transfer to full-scale Raptor testing. The subscale Raptors being tested have a reported thrust of 1,000 kN, whereas the new full-scale thrust targets for BFR have settled on 1,700-1,900 kN, considerably smaller than the 3,000 kN figure from 2016 but still nearly a factor of two larger than the test articles SpaceX has had success with. In fact, educated speculation from SpaceX fans suggest that the operational Raptor as shown in 2017 may only need to be about 15% larger than the current test article(s). The pressure the full-size engine operates at will be considerably higher, so SpaceX’s work is not done by any means, but the company’s next-gen rocket propulsion system is arguably far closer to completion than any of its competitors’ offerings.
-
- SpaceX’s subscale Raptor engine has completed more than 1200 seconds of testing in less than two years. (SpaceX)
-
- A subscale version of BE-4 testing staged combustion and nozzle technology. (Blue Origin)
-
- Aerojet-Rocketdyne’s AR-1 preburner conducted its first successful test earlier this year. (AR)
As far as we are publicly aware, SpaceX’s subscale Raptor testing has yet to result in a major failure and has largely been a great success. Blue Origin’s BE-4 is known to have experienced at least one critical failure during hot-fire testing, while AR-1 has not yet begun full engine tests but is well into concrete hardware testing. Blue Origin’ s BE-4 engine and its New Glenn rocket are currently expected to fly for the first time before 2020, with AR’s NGL tentatively planning for a 2021 inaugural flight, assuming the company chooses to continue pursuing its development.
-
SpaceX has not yet specified when BFR or BFS will first take flight. Raptor is likely to begin full-scale testing relatively soon, and Musk revealed that SpaceX was aiming to begin construction of the first BFR as early as Q2 of 2018. It’s quickly starting to look like the U.S. is about to enter a sort of modern commercial space race and regardless of the outcome, the next several months and years are bound to be tense and exciting for SpaceX, Blue Origin, and the established incumbents as they battle for both public and private contracts.
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
