Connect with us

News

NASA head calls out SpaceX CEO Elon Musk over Starship event in bizarre statement

SpaceX CEO Elon Musk presented an update on Starship on September 28th. NASA's administrator did not approve. (Teslarati - Eric Ralph)

Published

6 years ago

on

Roughly 24 hours before SpaceX CEO Elon Musk was scheduled to present an update on the company’s Starship launch vehicle development, NASA administrator Jim Bridenstine tweeted a bizarre and wholly unprovoked statement on the subject.

Seemingly equating SpaceX’s recent Crew Dragon delays with the distribution of Elon Musk’s public attention, the NASA administrator’s comment was almost universally criticized by the spaceflight community at large – and rightfully so.

https://twitter.com/JimBridenstine/status/1177711106300747777

First, some context. Created in 2010 and first supported with serious funding some 12-24 months later, NASA’s Commercial Crew Program (CCP) exists to replace the astronaut transport capabilities once offered by Space Shuttle and now achieved with contracts for seats on Russian Soyuz launches. Primarily the result of inept bureaucracy in NASA and Congress, the Space Shuttle was “retired” in 2011 in full knowledge that the US would have to rely on Russia to get NASA astronauts to the ISS until 2015 (at the absolute earliest).

Congress shut down multiple 2010 proposals to continue Shuttle flights until the late 2010s, choosing instead to kill the Shuttle and divert its associated funding to the expendable Ares V rocket (now the Space Launch System, SLS) and Orion crew capsule. More on that later...

Retweeted by Bridenstine’s official Twitter account, above is the absolute best-case interpretation of the NASA administrator’s comment. Although Eric Berger means well, the interpretation gives NASA far too much credit. Specifically, Bridenstine (or whoever fed him the statement) went out of his way to make it entirely one-sided in its focus on SpaceX. By all appearances, it would have never been posted if not for Elon Musk’s plans to present on Starship. Bridenstine additionally notes that “Commercial Crew is years behind schedule” and indicates that “NASA expects to see the same level of enthusiasm focused on [its] investments”.

Altogether, it’s simply impossible to interpret it as anything less than Bridenstine scolding SpaceX – and SpaceX alone – for not falling to the floor, kissing NASA’s feet, and pretending that Crew Dragon and Falcon 9 are the only things in existence. Absent from Bridenstine’s criticism was NASA’s other (and even more delay-complicit) Commercial Crew Partner, Boeing, who has yet to complete a pad abort or orbital flight test of its Starliner spacecraft. SpaceX completed Crew Dragon’s pad abort in 2015 and completed a flawless orbital flight test in March 2019.

A render of Boeing’s Starliner spacecraft. (Boeing)
An actual photo of Crew Dragon in orbit. (NASA)

In essence, Bridenstine is publicly implying that SpaceX needs to stop being (or appearing to be) distracted by Starship and focus 100% on Crew Dragon. Boeing was not mentioned, despite being a minimum of six months behind SpaceX and dramatically more ‘distracted’ in the Bridenstine-style interpretation of the word. For reference, Boeing is a publicly-traded company with 150,000 employees, annual revenue of more than $100B, and a market cap of $206B. Boeing has 14 subsidiaries, a handful of which are involved in spaceflight, and has no less than one or two dozen products that are each more fiscally important to shareholders and board members than Starliner.

Compared to Boeing’s annual ~$100B revenue, the entirety of the Starliner development program – from the drawing board in 2010 to crewed, orbital spaceflight sometime in 2020 – is ~$4.8B. On the scale of corporate focus, Starliner has likely been a blip at most in 2019, with the company probably far more focused on the systematic organizational failures that lead to the deaths of hundreds of people in two near-identical 737 MAX crashes. Alas, NASA administrator Jim Bridenstine did not release a statement publicly implying that Boeing needs to devote the “same level of enthusiasm” to Starliner after the second fatal 737 MAX crash in March 2019. Nor did Bridenstine release a statement charging Boeing with a lack of focus after continuous reports of issues with the company’s KC-46 Pegasus tanker program, nor Boeing’s recent $9.2B US Air Force trainer jet contract, or myriad other corporate focuses.

A Boeing Starliner test article prepares for thermal vacuum (TVac) testing in January 2019. Starliner’s uncrewed orbital flight test (OFT) – comparable to Crew Dragon’s March 2019 DM-1 launch – is unlikely to occur until November or December 2019. (NASA)

On the other hand, as Musk noted in his relatively subtle September 28th responses to Bridenstine’s implicitly derisive comment, something like 50-80% of the entirety of SpaceX’s workforce and resources are focused on Crew Dragon, the Falcon 9 rockets that will launch it, or a combination of both. At present, Starship is – at most – a side project, even if its strategic importance to SpaceX is hard to exaggerate. The same is largely true for Starlink, SpaceX’s ambitious internet satellite constellation program. It may be true that Starship will eventually make Crew and Cargo Dragon (as well as Falcon 9 and Falcon Heavy) wholly redundant, but that is likely years away and SpaceX will support NASA – as it is contractually required to – for as long as the space agency has vested interest in using Crew Dragon.

At the same time, NASA has explicitly and publicly chosen to prioritize safety over schedule with the Commercial Crew Program, accepting the possibility of delays and cost overruns to ensure that SpaceX and Boeing can build the safest spacecraft possible.

In a September 28th interview with CNN, Musk bluntly noted that the hardware was – at this point in time – more or less ready for flight and will be on-site at SpaceX’s Pad 39A Florida launch site within the next two months. According to Musk, from then on, any additional launch delays can almost entirely be attributed to the paperwork and reviews NASA must complete before giving SpaceX the go-ahead. If Bridenstine wants SpaceX to launch astronauts sooner, one – and possibly the only – solution is to tackle the roadblocks created by NASA’s own self-enforced red tape. The question, then, is whether Bridenstine wants to cut away red tape that may (or may not) be there for good reason.

When the pot calls the kettle black

Detached from whining about a contractor’s CEO presenting about a non-NASA program, complaining about Commercial Crew delays is at least slightly more reasonable. Originally intended to launch as early as 2015, Congress systematically underfunded the Commercial Crew Program by more than 50% for over half a decade, dispersing $2.4B of the $5.8B NASA requested from 2011 to 2016. Unsurprisingly, this completely upended Boeing and SpaceX development schedules. By September 2014, SpaceX aimed to have Crew Dragon certified by NASA for astronaut transport before the end of 2017, but even then, NASA already saw that schedule as overly optimistic.

Advertisement

It would be another two years before Congress began to seriously fund Commercial Crew at its requested levels, beginning in FY2016. In response to Bridenstine, former NASA deputy administrator Lori Garver noted that over the ~5 years Congress consistently withheld hundreds of millions of dollars of critical funds from Commercial Crew, NASA’s SLS rocket and Orion spacecraft were just as consistently overfunded above and beyond their budget requests. From 2011 to 2016 alone, SLS and Orion programs requested $11B and received an incredible $16.3B (148%) from Congress, while Commercial Crew requested $5.8B and received $2.4B (41%).

NASA’s SLS rocket seen in its Block 1 configuration with on Orion capsule on top. (NASA)

Ironically, despite literally receiving almost seven times as much funding as Crew Dragon and Starliner, SLS and Orion are arguably just as – if not more – delayed than their commercial brethren. Originally intended to launch an uncrewed test flight in 2017, there is now little to no chance that that mission (known then as EM-1 and now as Artemis-1) will launch before 2022, a delay of roughly half a decade. The cost of the SLS/Orion program recently crested $30B, a figure likely to grow to ~$40B before it has conducted a single launch. Of that funding, approximately a third has gone to Boeing, the primary contractor responsible for NASA’s comically-delayed SLS Core Stage – the orange booster pictured above.

The Commercial Crew development program will likely cost NASA $8B total over 9-10 years and produce two clean-sheet, high-performance, (relatively) low-cost crewed spacecraft. After their demonstration launches are completed, NASA will transition to fixed-price service contracts with SpaceX and Boeing to routinely send astronauts to the ISS several times per year.

Put simply, if Bridenstine actually cared about defending “the investments of the American taxpayer” more than wielding their sanctity as a political weapon, he wouldn’t have folded like a house of cards at the slightest resistance to his attempts to cull SLS/Orion delays and cost overruns, and he certainly wouldn’t be wasting breath complaining about what SpaceX’s CEO is or isn’t talking about.

Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.

Related Topics:

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

Elon Musk

‘I don’t understand TSLAQ:’ notable investor backs Tesla, Elon Musk

Published

3 hours ago

on

October 8, 2025

By

tesla showroom
(Credit: Tesla)

One notable investor that many people will recognize said today on X that he does not understand Tesla shorts, otherwise known as $TSLAQ, and he’s giving some interesting reasons.

Martin Shkreli was long known as “Pharmabro.” For years, he was known as the guy who bought the rights to a drug called Daraprim, hiked the prices, and spent a few years in Federal prison for securities fraud and conspiracy.

Shkreli is now an investor who co-founded several hedge funds, including Elea Capital, MSMB Capital Management, and MSMB Healthcare. He is also known for his frank, blunt, and straightforward responses on X.

His LinkedIn currently shows he is the Co-Founder of DL Software Inc.

One of his most recent posts on X criticized those who choose to short Tesla stock, stating he does not understand their perspective. He gave a list of reasons, which I’ll link here, as they’re not necessarily PG. I’ll list a few:

  • Fundamentals always have and will always matter
  • TSLAQ was beaten by Tesla because it’s “a great company with great management,” and they made a mistake “by betting against Elon.”
  • When Shkreli shorts stocks, he is “shorting FRAUDS and pipe dreams”

After Shkreli continued to question the idea behind shorting Tesla, he continued as he pondered the mentality behind those who choose to bet against the stock:

“I don’t understand ‘TSLAQ.’ Guy is the richest man in the world. He won. It’s over. He’s more successful with his 2nd, 3rd, and 4th largest companies than you will ever be, x100.

You can admit you are wrong, it’s just a feeling which will dissipate with time, trust me.”

According to reports from both Fortune and Business Insider, Tesla short sellers have lost a cumulative $64.5 billion since Tesla’s IPO in 2010.

Elon Musk issues dire warning to Tesla (TSLA) shorts

Shorts did accumulate a temporary profit of $16.2 billion earlier this year.

Continue Reading

News

Tesla will let you bring back this removed Model 3 part for a price

It will cost $595 and is available on Tesla’s website. You will have to have a Model 3 on your Tesla account to purchase the stalk retrofit kit.

Published

6 hours ago

on

October 8, 2025

By

Credit: Tesla Asia/X

Tesla is now letting Model 3 owners in the United States bring back one part that the company decided to remove after it refreshed the all-electric sedan last year. Of course, you can do it for a price.

With the Model 3 “Highland” refresh that Tesla launched last year, one of the most monumental changes the company made was to ditch the turn signal stalk altogether. Instead, Tesla opted for turn signal buttons, which have been met with mixed reviews.

I drove the new Tesla Model 3, here’s what got better

The change was widely regarded as Tesla preparing for more autonomous driving in its vehicles, especially as its interiors have gotten even more minimalistic.

The lack of a stalk in the new Model 3 was just another move the company made to adjust drivers and passengers to seeing less at the steering wheel column.

However, many drivers did not prefer the use of buttons and wanted the stalk reinstalled. Tesla allowed it in several regions, launching a retrofit kit. It has now made its way to the United States:

It will cost $595 and is available on Tesla’s website. You will have to have a Model 3 on your Tesla account to purchase the stalk retrofit kit.

It is interesting to note that despite Tesla’s strategy to remove the stalk with the new Model 3, which was released in early 2024, the company did not choose to make the same move with the new Model Y.

The new Model Y launched in the United States in early 2025, and Tesla chose to install a stalk in this vehicle.

It seemed as if the turn signal buttons were too much of a polarizing feature, and although the company technically could have given orderers an option, it would not have been the most efficient thing for manufacturing.

Continue Reading

News

Tesla Full Self-Driving v14.1 first impressions: Robotaxi-like features arrive

Tesla Full Self-Driving v14.1 is here, and we got to experience it for ourselves.

Published

7 hours ago

on

October 8, 2025

By

Tesla rolled out its Full Self-Driving v14.1 yesterday, its first public launch of its most robust and accurate FSD iteration yet. Luckily, I was able to get my hands on it through the Early Access Program.

The major changes in FSD v14.1 were revealed in the release notes, which outline several notable improvements in areas such as driving styles, parking, and overall navigation. Here’s what Tesla outlined fully in its release notes:

  • Added Arrival Options for you to select where FSD should park: in a Parking Lot, on the Street, in a Driveway, in a Parking Garage, or at the Curbside.
  • Added handling to pull over or yield for emergency vehicles (e.g. police cars, fire trucks, ambulances).
  • Added navigation and routing into the vision-based neural network for real-time handling of blocked roads and detours.
  • Added additional Speed Profile to further customize driving style preference.
  • Improved handling for static and dynamic gates.
  • Improved offsetting for road debris (e.g. tires, tree branches, boxes).
  • Improve handling of several scenarios including: unprotected turns, lane changes, vehicle cut-ins, and school busses.
  • Improved FSD’s ability to manage system faults and recover smoothly from degraded operation for enhanced reliability.
  • Added alerting for residue build-up on interior windshield that may impact front camera visibility. If affected, visit Service for cleaning!

I wanted to try it for myself. My big must-dos were my complaints with v13.2.9, which included parking when arriving at a destination, Navigation when leaving a destination, and definitely a general improvement in the car traveling at an acceptable rate of speed, even when using the “Hurry” driving style.

Here’s what I noticed with the new Full Self-Driving v14.1:

Speed Profiles are More Realistic

I am driving on “Hurry” about 95% of the time when utilizing Full Self-Driving. In past versions, most notably v13.2.9, my Tesla would slowly reach the speed limit, and it would tend to hang out at about 1-2 MPH either above or below it.

My first observation with v14.1 was the vehicle’s tendency to get right up to speed and, since I was still on Hurry, drive slightly above the speed limit. It never got out of line; it traveled at speeds I would typically drive at manually.

I think this is a big improvement on its own, because I felt that I was pressing the accelerator too frequently in past FSD versions. Oftentimes, it just wasn’t going fast enough to justify the “Hurry” label; it felt more conservative and more like a student driver than anything.

Check it out:

This was among my favorite improvements, and it was the first thing I noticed as the car navigated me to the Supercharger, where my next positive is.

Navigating into parking lots, self-parking at Supercharger

One of the changes noted in the Release Notes was the addition of Arrival Options, which allows the car to select the appropriate parking situation. Since I was going to charge, the car had already chosen “Charger” as the parking option.

Pulling into a gas station or convenience store, especially during work days, can be stressful, as they are usually congested and full of foot and vehicle traffic. In past FSD versions, I have noticed the car being slightly “jumpy” and even hesitant to proceed through the lot.

Driving through parking lots was a noticeable improvement. It seems as if the car is much more confident in making its way through, while still being aware and cautious enough to safely navigate to the Supercharger.

It then backed straight into a Supercharger stall, which was recently repaired and is once again active. I was actually upset it chose this specific stall because it had been inactive for a while. However, Tesla got this stall back up and running, the car chose it, and backed into the spot flawlessly:

This was super cool to experience, and I think it is a testament to how hard the Tesla AI team has worked. CEO Elon Musk recently stated that FSD would enable automatic parking at Superchargers, which was really awesome to experience firsthand.

I decided to leave the Supercharger and go to an auto parts store to pick up some interior cleaner and some microfiber towels. I love keeping my Tesla clean!

I also thought it would be a great opportunity to see how it would react to another parking lot, how it would navigate it, and let it choose a parking spot. It did it all flawlessly:

I had zero complaints about everything here. All of it was done really well.

Making a choice after being caught in the middle of an intersection

I arrived at a tight intersection in Dallastown, PA, and what my car did next has catalyzed quite a conversation on X.

It proceeded out into the middle of the intersection as the light was green. It had to yield to oncoming traffic, and while waiting, the light turned yellow, then red.

Most people, including myself, would have turned right and proceeded through the intersection since the car was already past the line. However, FSD chose to back up and wait for the next light cycle, which I felt was also a more than acceptable option:

There are some conflicting perspectives on what it chose to do here. Some said they would have proceeded and would want FSD to also proceed. I can agree with that perspective, but I also think it is not the worst thing in the world to back up. In Pennsylvania, I couldn’t find the exact law that says what is right or wrong. Instead, I did see that a left turn on red is only feasible when you’re going from a One-Way street to another One-Way.

I’m not totally sure what is “correct” here, but I think either option is fine. I have personally done both, and I’ve seen other drivers do both. I was more than fine with the car doing this, and I was honestly impressed that it did.

Navigated a busy grocery store lot, found suitable parking

This is not the busiest my local grocery store gets, but it was still congested enough for me to be impressed.

FSD decided to do one loop in the parking lot before it found a spot that it felt was good enough for me. I was perfectly fine with where it chose to park, and I thought it did a really great job. I was impressed with how stress-free I felt, as I have noted in the past that parking lots are definitely an area where Tesla needs to improve.

I was happy with its performance:

Strange right turn signal as if it saw an emergency vehicle

This was the first bug I noticed with FSD v14.1. While traveling on a local road, it put the right turn signal on and approached the curb as if it was pulling over for an emergency vehicle or as if it was going to park on the street.

It then realized its mistake and proceeded:

I’m not super sure what caused this, but I was a tad bit confused. There were no police cars, ambulances, or anyone with flashing lights to my rear. There was a dump truck on the other side of the road, and I almost felt like the way it navigated “around” that was probably what triggered it.

Navigation is still making strange decisions

I’ve written about navigation and my discontent with some of its decisions. It seems v14.1 didn’t resolve much of anything with navigation, and it did a couple of things wrong.

The first was that it tried to take the illogical and pointless path out of the Supercharger. I wrote about this a few days ago, as FSD tried to take my car the wrong way.

It did it again, but I overrode the decision, and it was all okay:

This is a minor issue, but it is still pretty frustrating. Hopefully, the navigation will learn after performing this adjustment after enough times.

The next navigation issue was more frustrating than the Supercharger one, especially considering it completely ignored the route. The navigation had the vehicle very clearly heading straight, but out of nowhere, the right turn signal went on. I overrode it, but the car still turned right, ignoring the navigation completely:

I ended up taking over here and driving until I could get to a stop sign.

Final Thoughts

I am really impressed with all of the changes Tesla made with FSD v14.1, and while there were a handful of bugs, things were tremendously better than v13.2.9.

Continue Reading

Trending