Connect with us
Boeing's Starliner and SpaceX's Crew Dragon spacecraft stand vertical at their respective launch pads in December 2019 and January 2020. Crew Dragon has now performed two successful full-up launches to Starliner's lone partial failure. (Richard Angle) Boeing's Starliner and SpaceX's Crew Dragon spacecraft stand vertical at their respective launch pads in December 2019 and January 2020. Crew Dragon has now performed two successful full-up launches to Starliner's lone partial failure. (Richard Angle)

News

SpaceX set to launch NASA astronauts first after Boeing narrowly avoids catastrophe in space

Boeing's Starliner and SpaceX's Crew Dragon spacecraft stand vertical at their respective launch pads roughly six weeks apart. (Richard Angle)

Published

on

SpaceX is set to become the first private company to launch NASA astronauts as few as three months from now, all but guaranteed after Boeing’s competing Starliner spacecraft narrowly avoided a catastrophe in space on its orbital launch debut.

The ultimate purpose of NASA’s Commercial Crew Program (CCP) is to ensure that the US is once again able to launch its own astronauts into orbit and to the International Space Station (ISS) – a capability the country has not possessed since it prematurely canceled the Space Shuttle in 2011. In a logical step, NASA decided to fund two independent companies to ensure that astronaut launch capabilities would be insulated against any single failure, ultimately awarding contracts to Boeing and SpaceX in 2014. Boeing did actually try to have Congress snub SpaceX back in 2014 and solely award the contract to Starliner, but the company thankfully failed.

As a result, SpaceX beating Boeing on the (not-a-) race to launch NASA astronauts to the International Space Station (ISS) would represent an immense and deeply embarrassing upset in the traditional aerospace industry – essentially a case of David and Goliath. For the better part of a decade, Congress, most industry officials, and Boeing itself have argued ad nauseum the Starliner spacecraft was clearly a far safer bet than anything built by SpaceX – Boeing, obviously, has far more experience (“heritage”) in the spaceflight industry. However, multiple “catastrophic” failures during Boeing’s recent Starliner ‘Orbital Flight Test’ (OFT) paint a far uglier picture.

The SpaceX Crew Dragon capsule and Boeing CTS-100 Starliner are pictured here during separate pad abort tests. (SpaceX/NASA)

As its PR team and executives will constantly remind anyone within earshot, Boeing helped build the first stage of the Saturn V rocket, while a company it bought years after the fact (Rockwell) did technically buy the company (North American) that built the spacecraft (Apollo CSM) that carried NASA astronauts from the Earth to the Moon (and back). Rockwell (acquired by Boeing) also built all five of NASA’s Space Shuttle orbiters.

In the 1990s, Boeing – set to lose a competition to build an expendable rocket for the US military – acquired McDonnell Douglas at the last second, slapping a Boeing sticker on the Delta IV rocket – designed and built by MD. Boeing then conspired to steal trade secrets from Lockheed Martin (bidding Atlas V) and used that stolen info to mislead the USAF about the real cost of Delta IV, thus securing the more lucrative of two possible contracts. This is all to point out the simple fact that Boeing has far less real experience designing spacecraft than it tends to act like it does.

Advertisement
Boeing’s Starliner spacecraft sits atop a ULA Atlas V rocket at the LC-41 launch pad ahead of its doomed orbital flight test (OFT). (Richard Angle)

As such, it’s substantially less surprising than it might otherwise be that Boeing’s Starliner spacecraft has had such a rocky orbital launch debut. Preceded just a matter of weeks by a quality assurance failure that prevented one of Starliner’s four parachutes from deploying after an otherwise-successful pad abort test, a second Starliner spacecraft launched atop an Atlas V rocket on its orbital launch debut (OFT) on December 20th, 2019. Atlas V performed flawlessly but immediately after Starliner separated from the rocket, things went very wrong.

Bad software ultimately caused the spacecraft to perform thousands of uncommanded maneuvering thruster burns, depleting a majority of its propellant before Boeing was able to intervene. Starliner managed to place itself in low Earth orbit (LEO), but by then it had nowhere near enough propellant left to rendezvous and dock with the ISS – one of the most crucial purposes of the uncrewed flight test. Unable to complete that part of the mission, Boeing instead did a few small tests over the course of 48 hours in orbit before commanding the spacecraft’s reentry and landing on December 22nd.

Starliner successfully landed on December 22nd after a partial failure in orbit. (NASA – Bill Ingalls)

But wait, there’s more!

As it turns out, although both NASA and Boeing inexplicably withheld the information from the public for more than two months, Boeing’s OFT Starliner spacecraft reportedly almost suffered a second major software failure just hours before reentry. According to NASA and Boeing comments in a press conference held only after news of that second failure broke after an advisory panel broached the issue in February 2020, a second Starliner software bug – caught only because the first failure forced Boeing to double-check its code – could have had far more catastrophic consequences.

NASA officials stated that had the second bug not been caught, some of Starliner’s thruster valves would have been frozen, either entirely preventing or severely hampering the spacecraft’s detached trunk from properly maneuvering in orbit. Apparently, that service module (carrying fuel, abort engines, a solar array, and more) could have crashed into the crew module shortly after detaching from it. Unsurprisingly, that ‘recontact’ could have severely damaged the Starliner crew capsule, potentially making reentry impossible (or even fatal) if its relatively fragile heat shield bore the brunt of that impact.

SpaceX has undeniably suffered its own significant failures, most notably when flight-proven Crew Dragon capsule C201 exploded moments before a static fire test, but the company has already proven that it fixed the source of the failure with the spacecraft’s second successful launch on a Falcon 9 rocket. Ultimately, it’s becoming nearly impossible to rationally argue that Boeing’s Starliner will be safer than SpaceX’s Crew Dragon – let alone worth the 40% premium Boeing is charging NASA and the US taxpayer.

As of February 2020, Crew Dragon has successfully docked with the ISS and completed two successful Falcon 9 launches in just nine months. (Richard Angle)

According to Ars Technica’s Eric Berger, Crew Dragon’s inaugural astronaut launch is now tentatively scheduled as early as late-April to late-May 2020. Paperwork – not technical hurdles – is currently the source of that uncertainty, and all Demo-2 mission hardware (Falcon 9 and Crew Dragon) is either already in Florida or days away from arriving.

Due to the combination of similar software failures Starliner suffered during its first and only launch, Boeing now has to review the entirety of the spacecraft’s software – more than a million lines of code – before NASA will allow the company to launch again. There’s also a very good chance that Boeing will now have to repeat the Orbital Flight Test, potentially incurring major delays. In short, it would take nothing less than a miracle – or NASA making a public mockery of itself for Boeing’s benefit – for Starliner to launch astronauts before SpaceX.

Advertisement

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

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

Elon Musk reveals date of Tesla Full Self-Driving’s next massive release

Initially planned for a January or February release, v14.3 aims to add some reasoning and logic to the decisions that Full Self-Driving makes, which could improve a lot of things, including Navigation, which is a major complaint of many owners currently.

Published

on

Tesla CEO Elon Musk revealed the date of Full Self-Driving’s next massive release: v14.3.

For months, Tesla owners with Hardware 4 have been utilizing Full Self-Driving v14.2 and subsequent releases. Currently, the most up-to-date FSD version is v14.2.2.5, which has definitely brought out mixed reviews. With releases, some things get better, and other things might regress slightly.

For the most part, things are better in terms of overall behavior.

However, many owners have been looking forward to the next release, which is v14.3, about which Musk has said many great things. Back in November, Musk said that v14.3 “is where the last big piece of the puzzle lands.”

He added:

“We’re gonna add a lot of reasoning and RL (reinforcement learning). To get to serious scale, Tesla will probably need to build a giant chip fab. To have a few hundred gigawatts of AI chips per year, I don’t see that capability coming online fast enough, so we will probably have to build a fab.”

Initially planned for a January or February release, v14.3 aims to add some reasoning and logic to the decisions that Full Self-Driving makes, which could improve a lot of things, including Navigation, which is a major complaint of many owners currently.

Tesla Full Self-Driving v14.2 is a considerable improvement from early versions of the suite, but we have written about the somewhat confusing updates that have come with recent versions.

Tesla Full Self-Driving v14.2.2.5 might be the most confusing release ever

They’ve been incredibly difficult to gauge in terms of progress because some things have gotten better, but there seems to be some real regression on a handful of things, especially with confidence and assertiveness.

Musk confirmed today on X that Tesla is already testing v14.3 internally right now. It will hit a wide release “in a few weeks,” so we should probably expect it by late April.

Overall, there are high hopes that v14.3 could be a true game changer for Tesla Full Self-Driving, as many believe it could be the version that Robotaxis in Austin, Texas, some of which are driverless and unsupervised, are running.

It could also include some major additions, including “Banish,” also referred to as “Reverse Summon,” which would go find a parking spot after dropping occupants off at their destination.

What Tesla will roll out, and when exactly it arrives, all remain to be seen, but fans have been ready for a new version as v14.2.2.5 has definitely run its course. We have had a lot of readers tell us their biggest request is to fix Navigation errors, which seem to be one of the most universal complaints among daily FSD users.

Continue Reading

Cybertruck

Chattanooga Charge: Tesla and EV fans ready for the Southeast’s wildest Tesla party

From Cybertruck Convoys to Kid-Friendly Fun Zones: The Chattanooga Charge Has Something for Everyone

Published

on

By

Hundreds of like-minded Tesla and EV enthusiasts are descending on Chattanooga Charge this weekend for the largest Tesla meet in the Southeast. Taking place on March 20–22, 2026 at the stunning Tennessee Riverpark.

If you were there last year, you’ll know that it’s the ultimate experience to see the wildest Teslas in action, see the best in EV tech, and arguably the most fun – finally put a name to the face and connect with those social media buddies IRL! Oh, and that epic night time Tesla light show is a once-in-a-lifetime experience that will transform the Riverpark into something out of a sci-fi film that’s remarkably unforgettable and must be seen in person.

This year’s event takes everything up a notch, with over 100 Cybertrucks expected to be on display, many sporting jaw-dropping modifications and custom wraps that push the boundaries of what these stainless steel beasts can look like.

Whether you’re a diehard Tesla fan, EV supporter, or just EV-mod-curious, the sheer spectacle is worth the drive.

The Chattanooga Charge doesn’t wait until Saturday morning to get started. The weekend technically kicks off Friday, March 20th, and the venue sets the tone immediately. Come share roadtrip stories over drinks at the W-XYZ Rooftop Bar on the top floor of the Aloft Chattanooga Hamilton Place Hotel, with sunset views over the city.

Come morning, nurse your hangover with a some good coffee, and convoy with hundreds of other Tesla and EV drivers through Chattanooga to the event for some morning meet and greets before the speaker panel starts and the food trucks fire up.

Tesla owner clubs travel from across the country to be here, not just to show off their vehicles,, but to connect, share, and celebrate a shared passion for the future of driving.

Sounds like a plan to me. See you there, guys. Don’t miss it. Get your tickets at ChattanoogaCharge.com and join the charge. 🔋⚡

Chattanooga Charge is a premier Tesla and EV gathering inspired by the X Takeover, known as one of the largest Tesla event gatherings. What began as a bold idea from the team at DIY Wraps/TESBROS, hosted in their hometown of Chattanooga, Tennessee, the event quickly became a movement across social media. The first annual Chattanooga Charge united over 16 Tesla clubs from 16 states, proof that the EV community was hungry for something big in the South. Year after year, the event has grown in scale, ambition, and heart.

Continue Reading

News

Tesla Full Self-Driving gets latest bit of scrutiny from NHTSA

The analysis impacts roughly 3.2 million vehicles across the company’s entire lineup, and aims to identify how the suite’s degradation detection systems work and how effective they are when the cars encounter difficult visibility conditions.

Published

on

Credit: Tesla

The National Highway Traffic Safety Administration (NHTSA) has elevated its probe into Tesla’s Full Self-Driving (Supervised) suite to an Engineering Analysis.

The analysis impacts roughly 3.2 million vehicles across the company’s entire lineup, and aims to identify how the suite’s degradation detection systems work and how effective they are when the cars encounter difficult visibility conditions.

The step up into an Engineering Analysis is often required before the NHTSA will tell an automaker to issue a recall. However, this is not a guarantee that a recall will be issued.

The NTHSA wants to examine Tesla FSD’s ability to assess road conditions that have reduced visibility, as well as detect degradation to alert the driver with sufficient time to respond.

The Office of Defects Investigation (ODI) will evaluate the performance of FSD in degraded roadway conditions and the updates or modifications Tesla makes to the degradation detection system, including the timing, purpose, and capabilities of the updates.

Tesla routinely ships software updates to improve the capabilities of the FSD suite, so it will be interesting to see if various versions of FSD are tested. Interestingly, you can find many examples from real-world users of FSD handling snow-covered roads, heavy rain, and single-lane backroads.

However, there are incidents that the NHTSA has used to determine the need for this probe, at least for now. The agency said:

“Available incident data raise concerns that Tesla’s degradation detection system, both as originally deployed and later updated, fails to detect and/or warn the driver appropriately under degraded visibility conditions such as glare and airborne obscurants. In the crashes that ODI has reviewed, the system did not detect common roadway conditions that impaired camera visibility and/or provide alerts when camera performance had deteriorated until immediately before the crash occurred.”

It continues to say in its report that a review of Tesla’s responses revealed additional crashes that occurred in similar environments showed FSD “did not detect a degraded state, and/or it did not present the driver with an alert with adequate time for the driver to react. In each of these crashes, FSD also lost track of or never detected a lead vehicle in its path.”

The next steps of the NHTSA Engineering Analysis require the agency to gather further information on Tesla’s attempts to upgrade the degradation detection system. It will also analyze six recent potentially related incidents.

The investigation is listed as EA26002.

Continue Reading