Connect with us

News

Boeing's astronaut capsule flies off course, fate uncertain after launch debut

Boeing's Starliner spacecraft lifts off atop ULA's Atlas V rocket on its orbital launch debut. (Richard Angle)

Published

on

Roughly 30 minutes after lifting off for the first time on a United Launch Alliance (ULA) Atlas V rocket, Boeing’s Starliner crew capsule suffered a major failure when it attempted to raise its orbit with onboard engines.

A few hours after the failure came to light, NASA and Boeing held a press conference to update members of the media on the situation, with the space agency offering some candid – if a bit odd – insight into Starliner’s anomalous launch debut. Before the spacecraft’s software threw a wrench into the gears, the plan was for Starliner to separate from ULA’s Atlas V Centaur upper stage and use its own thrusters to reach orbit and begin the trek up Earth’s gravity well to the International Space Station (ISS).

While it will likely take weeks or even months for Boeing and NASA to determine exactly what went wrong during the mission, preliminary information has already begun to paint a fairly detailed picture.

Around 15 minutes after liftoff, Starliner separated from the rocket as intended but it appears that things began to go awry almost immediately afterward. Most notably, according to NASA administrator Jim Bridenstine’s tweets and later comments, a very early look at the telemetry suggests that Starliner’s internal clock was somehow tricked into believing that the time was either earlier or later than it actually was.

Thinking that it was in the midst of a lengthy thruster firing meant to raise its orbit and send the spacecraft on its way to the space station, Starliner was thus focused on ensuring that it was pointed as accurately as possible. Although the space station is the size of a football field, in the vastness of space, rendezvousing with it is a bit like threading a needle. While firing thrusters to do so, spacecraft thus need to point themselves as accurately as possible.

While coasting before or after one of those orbit-boosting thruster firings, Starliner thought it was actually burning towards the space station and was thus very carefully controlling its orientation with a dozen or so smaller thrusters. In short, those unintentional thruster firings burned through a ton of Starliner’s limited propellant supply – enough to make it impossible (or nearly so) for the spacecraft to rendezvous and dock the ISS, a central purpose of this particular launch.

Advertisement
-
A long-exposure of Starliner’s Atlas V launch debut. (Richard Angle)

This ultimately means that Starliner is leaning heavily on the “test” aspect of this Orbital Flight Test (OFT), uncovering failure modes and bugs that Boeing was clearly unable to tease out with ground testing and simulation. While in a totally different ballpark, SpaceX similar Crew Dragon spacecraft suffered its own major failure earlier this year, although that capsule explosion occurred during intentional ground testing, whereas Starliner’s software failed during its high-profile launch debut and has severely curtailed the scope of the spacecraft’s first orbital flight test.

In fact, Bridenstine was unable to rule out the possibility that Boeing will have to attempt a second uncrewed orbital flight test (OFT) before Starliner will be qualified to launch the space agency’s astronauts. Although early signs suggest that Boeing will still be able to attempt to deorbit and recover the spacecraft a day or two from now, the fact that Starliner will not be able to perform critical demonstrations of its ISS rendezvous and docking capabilities will make it far harder for NASA to rationally certify the spacecraft for astronaut launches.

Crew Dragon approaches the ISS during its March 2019 Demo-1 launch debut. (NASA)

SpaceX’s Crew Dragon, for reference, completed a more or less flawless launch, orbit raise, and rendezvous before docking with the ISS. It’s almost impossible to imagine NASA giving SpaceX permission to proceed immediately into its first astronaut launch if Crew Dragon had failed to reach the proper orbit or dock with the space station.

Regardless, it’s far too early to tell whether Boeing will have to repeat Starliner’s OFT. If Starliner performs absolutely perfectly between now and its planned soft-landing in New Mexico, there might be a chance that NASA will still allow Boeing to effectively cut corners to its astronaut launch debut, but only time will tell.

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

Lifestyle

Watch Tesla’s “guardian angel” FSD feature take over for collision evasion

Published

on

By

Tesla’s Automatic Collision Evasion feature can be seen in one of the first owner videos of it in action.

Tesla owner Spencer (@scotsrule08) posted on Monday that the feature “worked flawlessly,” saying FSD reengaged itself just as he was about to hit a curb. Ashok Elluswamy, who leads Tesla’s AI team, shared the clip and wrote, “A guardian angel always looking out for you.”

The video arrives in the middle of a staged rollout. Tesla first shipped Automatic Collision Evasion with FSD (Supervised) v14.3.9 in software update 2026.27.6 earlier this month, which Teslarati covered as it reached cars. Update 2026.27.10, which began going out on September 19, carried the feature improvements with FSD v14.3.10, according to release notes tracked by Not a Tesla App. The newer 2026.27.11 build is now reaching another wave of vehicles.


The feature only runs on HW4 vehicles, and it requires an active FSD purchase or subscription with both FSD (Supervised) and Automatic Emergency Braking enabled. HW3 owners receive FSD v14.2 Lite in the same updates, but that build does not include collision evasion.

Tesla’s release notes describe two triggers. The first is an imminent frontal collision that braking alone may not prevent, in which case the car can activate FSD to steer, brake or accelerate around the hazard. That scenario is limited to highways below 85 mph, with no pedestrians or cyclists detected and no slippery road surface. The second covers a driver who appears inattentive, such as reaching into the back seat, or who seems to have switched off FSD by accident. Spencer’s curb clip appears to fall into that second category.

Tesla plans big safety improvements for Full Self-Driving v15

Once the system takes over, the accelerator is muted and light brake input will not cancel the maneuver. Drivers need to apply firm, deliberate steering force to take back control, and the car chimes to hand control back once the danger has passed.

Elluswamy recently noted that earlier hazard prediction, faster reaction time and better collision avoidance would arrive with FSD v15, the next major version.

Continue Reading

News

Tesla Roadster event gets delayed due to unfavorable weather

Published

on

Credit: Tesla

Tesla is delaying its event for the Roadster, moving it from this Thursday, October 1, to Thursday, October 15, due to unfavorable weather.

The company has said it has been tracking the weather for this Thursday closely with local meteorologists, and because the event can only be held outside, Tesla is making the call to delay it:

“We’ve been tracking the weather closely with local meteorologists, but given the severe conditions predicted & because this event can only be held outdoors, we’ve made the difficult decision to reschedule. New date is October 15. Additional details to follow.”

We are sure that this is bringing back PTSD for some Tesla fans, and we know it is not ideal, but this also reveals some things about the event. Tesla said that this can only be held outdoors, meaning it bodes well for the rumors that the vehicle could potentially hover.

Some believe that this was essentially confirmed by the FAA airspace restriction they were granted, but this could have been for a drone show or to keep drones from spying on the event.

Tesla Roadster is available for order once again following brief hold

The Roadster event has been long-awaited, and it is unfortunate that the weather is going to keep us all waiting a little bit longer.

The Tesla Roadster will be unveiled in Waco, Texas.

Continue Reading

Elon Musk

SpaceX turned a heralding moment for Starship into its greatest

Starship reached orbit despite losing an engine, deployed 26 Starlink V3 satellites on Flight 14.

Published

on

By

SpaceX’s Starship reached orbit for the first time on Monday, and for a few nail-biting minutes it looked like it wouldn’t. During ascent on Flight 14, one of Ship 41’s six Raptor engines shut down early, and SpaceX’s livestream host Dan Huot told viewers the team had decided not to commit to orbit. Minutes later, after what Huot described as a lot of conversation in the control room, the final poll came back in favor, and a roughly 19 second burn of a single Raptor pushed the ship into orbit about 170 miles up.

The reversal matters because SpaceX had written the exit ramp into the mission plan. The company said it would only fire the orbital insertion burn if flight controllers confirmed enough backup hardware remained for the deorbit burn, a condition Teslarati laid out ahead of the flight. Losing an engine was exactly the scenario that rule was built for.

Pressing forward fits Elon Musk’s history. Falcon 1 failed three straight times before its fourth launch reached orbit in 2008, with SpaceX nearly out of money, and Starship was developed by flying prototypes until they broke. What changed this year SpaceX going public, and with $SPCX sliding below its IPO price in July when Flight 13 slipped, the short interest climbed significantly, as Teslarati reported at the time. A Starship potentially lost today with revenue generating next-gen Starlink satellites aboard would have landed directly on shareholders.

That pressure showed up after orbit. SpaceX cut a flight planned to last nearly 10 hours to about three, moving splashdown from west of Chile to the North Pacific near Hawaii. SpaceX gave no reason, though Musk said this month the company was being extremely cautious about debris risk. The single Raptor for deorbit worked, and Ship 41 completed its flip and landing burn before breaking apart in the water, an outcome SpaceX expected. Musk has structured SpaceX’s governance to shield long term bets from market pressure.

The payload is the bigger business story. Musk posted that all 26 Starlink V3 satellites deployed and are “operating nominally.” Each V3 is rated for about 1 Tbps of downlink and 160 Gbps of uplink, so this single launch adds roughly 26 Tbps, about 10 times what a Falcon 9 load of V2 Mini satellites adds. The V3 is too large for Falcon 9, making Starship the only vehicle that can build out the planned 100,000 satellite constellation, at up to 60 per flight once it reaches routine service. Unlike the 20 V3 units on Flight 13, which reentered on a suborbital path, these will raise their orbits and could begin serving customers within weeks and bring in hundreds of millions of additional dollars in projected Starlink revenue.

SpaceX has already begun winding down Falcon 9 Starlink launches from Florida in favor of Starship. Reported targets put Flight 15 as early as October 19, leaving about three weeks to diagnose Monday’s engine shutdown before the next orbital attempt.

Continue Reading