U.S. Representative Kevin Kiley (R-CA) has sent a letter to FAA Administrator Michael Whitaker over his recent claims about SpaceX. During Tuesday’s Transportation Committee hearing, Whitaker advanced several alleged safety concerns about SpaceX’s operations, all of which were strongly denied by the private space company.
During his testimony, the FAA Administrator alleged that SpaceX must operate at the highest level of safety, which includes having a safety management system program and a whistleblower program. He also alleged that SpaceX had launched without a permit last year in Cape Canaveral, FL and that the delay in Starship’s Flight 5 launch was due to SpaceX failing to provide an updated sonic boom analysis, among other safety concerns.
FAA Administrator Whitaker made several incorrect statements today regarding SpaceX. In fact, every statement he made was incorrect.
It is deeply concerning that the Administrator does not appear to have accurate information immediately available to him with respect to SpaceX… pic.twitter.com/OrtMUvnCNI— SpaceX (@SpaceX) September 24, 2024
SpaceX strongly denied each of Whitaker’s claims. In a letter, Mat Dunn, senior director of global government affairs at SpaceX, stated that “every statement (the FAA Administrator) made was incorrect.” Dunn also argued that SpaceX is currently the “safest, most reliable launch provider in the world, and is absolutely committed to safety in all operations.”
Kiley’s recent letter to Whitaker carried some of the points from SpaceX’s rebuttal of the FAA Administrator’s claims. As per the Representative, Whitaker must provide answers to a number of questions surrounding his claims during the Transportation Committee hearing.
FAA Administrator Whitaker made a number of false statements in his testimony about @SpaceX. Either he doesn’t know what’s going on at his agency or he deliberately deceived Congress.
I’ve asked him which it is. Either possibility calls into doubt his fitness to lead the FAA. pic.twitter.com/lW2KcOnItT— Rep. Kevin Kiley (@RepKiley) September 25, 2024
Following is U.S. Representative Kevin Kiley’s letter to FAA Administrator Michael Whitaker.
September 25, 2024
Michael Whitaker
-
800 Independence Avenue, SW
Administrator
Federal Aviation Administration
Washington, DC 20591
Dear Administrator Whitaker,
On September 24, 2024, you testified at a hearing of the Aviation Subcommittee of the House Transportation and Infrastructure Committee. I asked you several questions during that hearing regarding the FAA’s decisions with respect to SpaceX launches. Your answers appear to be filled with inaccurate statements. Such falsehoods raise serious concerns about your fitness to lead the FAA. Please provide my office with responses in writing to the following questions –
- You claimed that SpaceX launched recent Falcon missions without a permit. SpaceX has said these claims are completely false, and that the FAA has not alleged previously that the company was not permitted or licensed to launch these missions. Can you share the evidence for your claim that SpaceX launched these missions without a permit?
- You claimed that SpaceX moved a fuel farm closer to the population without completing a risk analysis statement. SpaceX says that the new location was twice the distance from the nearest publicly accessible area, that the company provided the FAA with all the required analysis, and that the FAA ultimately approved the revised location. Please supply all correspondence between the FAA and SpaceX relative to the fuel farm.
- You claimed that SpaceX failed to provide an updated sonic boom analysis. SpaceX refutes this and says that the Fish and Wildlife Service had already reviewed Starship’s sonic booms and determined they had no environmental impact. While SpaceX has acknowledged it recently provided the FAA data showing a slightly larger sonic boom area than originally anticipated, the company maintains this results in no new environmental impact.
- What evidence does the FAA have of a new environmental impact?
- How long will it take the FAA to make this minor paperwork update?
- What evidence does the FAA have for your assertion that this is a safety related incident”?
- You claimed that SpaceX was in violation of Texas state law. What Texas laws did SpaceX violate?
- Does the FAA need to be reformed to keep up with innovation in the commercial space industry?
From the dawn of the space age, America has set the standard in exploration. Our nation’s spirit of innovation has propelled us to the moon and pushed the boundaries of what’s possible. If we want to keep that legacy alive, we must work with innovators, rather than slow them down. We cannot hinder private industry that is pushing the limits, with regulatory red tape and constant delays. The longer we stall, the more ground we lose. We must continue to empower our private space companies to innovate, build, and lead. This is the only way that we can ensure our national security, while also guaranteeing that America defines the next generation of space exploration. I look forward to your response.
Sincerely,
-
Kevin Kiley
Member of Congress
Don’t hesitate to contact us with news tips. Just send a message to simon@teslarati.com to give us a heads up.
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
