Connect with us

News

Boeing Starliner spacecraft successfully returns to flight 29 months after ill-fated debut

Published

on

More than three years after SpaceX’s Crew Dragon spacecraft first safely reached orbit and almost three and a half years after Boeing’s Starliner crew capsule’s ill-fated launch debut, Boeing has finally returned to flight and made it farther than ever before towards a successful test flight.

Almost ten months after Boeing’s first attempt at Starliner’s second uncrewed Orbital Flight Test (OFT-2 #1), the stars aligned. As expected, the United Launch Alliance’s Atlas V rocket lifted off on time at 6:54 pm EDT (22:54 UTC) on Thursday, May 19th, ascending from Cape Canaveral Space Force Station (CCSFS) Launch Complex 41 (LC-41) without issue. After a four and a half minute burn, the Atlas V booster – powered by a Russian-built RD-180 engine – separated and the Centaur upper stage – powered by two Aerojet Rocketdyne RL-10 engines – took over.

Another six minutes later, Centaur shut down and Starliner ultimately separated from the rocket a bit less than 12 minutes after liftoff. Unlike SpaceX’s Crew Dragon, though, Starliner separated from its launch vehicle before reaching orbit – a task Boeing engineers chose to reserve for the spacecraft itself to limit stress on the spacecraft and crew in the event of a high-altitude abort. However, that design decision also adds significant risk in other ways and – after the spacecraft’s extremely poor performance during its first launch attempt – turns a Starliner launch into a sort of 30-minute cliffhanger.

While just a hair shy of true orbit, Starliner’s suborbital launch trajectory means that whether or not it wants to, the spacecraft will reenter Earth’s atmosphere about an hour after liftoff if it can’t complete a minute-long orbital insertion burn. In the case of OFT-2, that burn came about 31 minutes after liftoff and was thankfully successful, inserting Starliner into a stable, circular orbit and undoubtedly triggering a massive wave of relief for all employees involved. From that stable orbit, Starliner can finally begin to prepare to rendezvous with the International Space Station (ISS) for the first time ever.

The story of Starliner’s tortured orbital flight test (OFT) campaign began in earnest on December 20th, 2019, when an uncrewed prototype of the Boeing spacecraft first attempted to launch to the International Space Station (ISS) atop a United Launch Alliance (ULA) Atlas V rocket. Infamously, a major software bug that could have been easily detected with even the most basic integrated hardware-in-the-loop prelaunch testing caused Starliner to lose control the moment it separated from Atlas V. Only through a heroic last-second effort was Boeing able to insert Starliner into orbit and prevent the spacecraft from reentering prematurely, which would have likely destroyed it. After hundreds of seconds of unplanned burns of its many attitude control thrusters, Starliner no longer had enough propellant to safely reach the ISS.

Boeing would later correct another completely unrelated software bug mere hours before Starliner’s planned reentry and recovery. If undetected, it could have caused the spacecraft’s capsule and service sections to crash into each other shortly after separation, potentially damaging the capsule’s heat shield and dooming it to destruction during reentry. Had astronauts been aboard, either of the two software bugs could have potentially resulted in crew fatalities and total mission failure. Instead, through a combination of sheer luck and a quick emergency response from Boeing and NASA teams, the spacecraft was saved and recovered in New Mexico.

On a positive note, aside from raising deep and foreboding questions about Boeing’s software development and integrating testing capabilities and NASA’s inept and inconsistent oversight, OFT-1 did still demonstrate that Starliner was able to reach orbit, operate in space, deorbit, survive atmospheric reentry, and land softly under parachutes.

Advertisement
-

However, the problems were about to continue and spread beyond software. On July 30th, 2021, shortly before a different uncrewed Starliner was scheduled to reattempt the first Orbital Flight Test, the launch was aborted. Eventually, Boeing and NASA reported that 13 of Starliner’s 24 main oxidizer valves had failed to open during a prelaunch test just a few hours before liftoff. The resulting investigation ultimately concluded that the Aerojet Rocketdyne-supplied valves had a faulty design and that Boeing had failed to properly insulate those valves from humidity and water intrusion. It also delayed the next OFT-2 launch attempt by almost ten months.

But finally, after almost 30 months of work to rectify those software and hardware failures, Starliner has intentionally reached a stable orbit without running into a major problem – certainly cause for some amount of optimism. Still, safely rendezvousing and docking with the ISS may be the biggest and riskiest challenge Starliner has faced yet and Boeing will be attempting the feat for the first time in its modern history. Starliner is expected to begin proximity operations around 3 pm EDT on May 20th. If the first attempt is perfect, docking could occur as early as 7:10 pm EDT.

Ultimately, even if Boeing is now more than three years behind SpaceX, whose Crew Dragon spacecraft first reached orbit and the ISS in March 2019 and launched its first astronauts in May 2020, it’s essential that NASA has two redundant crew vehicles available to carry its astronauts to and from the station. SpaceX’s extraordinary success and heroic efforts have allowed the company to singlehandedly ensure NASA access to the ISS since November 2020, but no complex system is perfect and even a failure outside of SpaceX’s control could trigger a long delay that could threaten NASA’s uninterrupted presence on the International Space Station.

NASA has contracts with SpaceX to maintain that uninterrupted presence at the ISS through Crew Dragon’s Crew-7 mission, which could launch as early as September 2023 and would then return to Earth around March 2024. If OFT-2 is completed without significant issue, Boeing’s next priority is Starliner’s Crew Flight Test (CFT), a crewed launch debut that could happen before the end of 2022.

After that, Starliner’s first operational crew launch could potentially occur in Q1 2024, just before Crew Dragon’s Crew-7 recovery. Following Crew Dragon’s near-flawless uncrewed test flight, it took another 14 months for NASA and SpaceX to proceed to Demo-2, Dragon’s Crew Flight Test equivalent. Dragon’s first operational astronaut launch occurred in November 2020, 20 months after its uncrewed demo flight. If NASA follows a similar path for Starliner, that meshes well with an operational debut in early 2024.

Advertisement
-

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

News

Why SpaceX is finishing another space-internet system that isn’t Starlink

SpaceX launched three final O3b mPower satellites Sunday, finishing a lesser known SES satellite network.

Published

on

By

SpaceX had an 87 minute window opening at 2:49 p.m. Eastern on Sunday to fly a Falcon 9 out of Cape Canaveral carrying the final three satellites for SES’s O3b mPower constellation, a project that has taken more than a decade to finish since Boeing and SES first signed SpaceX on for the work.

Unlike the thousands of Starlink satellites SpaceX has stacked into orbit over the years, O3b mPower flies in a different neighborhood entirely. The three new satellites, tagged F11, F12 and F13, are headed for medium Earth orbit at roughly 5,000 miles up, more than ten times higher than Starlink’s shell around 340 miles but still a small fraction of the 22,000 miles where old school geostationary satellites sit. That middle position is the whole point, because a satellite that far out needs far fewer siblings to blanket the globe than a low orbit constellation does. Essentially, SES only needed 13 satellites total to build a network offering quick, steady service that used to require thousands of spacecraft.

With most people having heard plenty about Starlink and almost nothing about O3b mPower, SES and SpaceX already blend the two networks for some customers. Both SpaceX and SES sell satellite broadband, but they’re aimed at different buyers. Starlink is built for volume, direct to consumers, RVs, homes, small businesses, plus a growing aviation and maritime business. O3b mPower skips consumers entirely and sells enterprise grade connectivity to airlines, cruise lines, offshore energy operators, telecoms needing backhaul, and governments, priced and provisioned more like a dedicated circuit.

A 2023 partnership lets cruise ships combine Starlink’s speed with O3b mPower’s steady capacity depending on what a ship needs at a given moment. Sunday’s completed 13 satellite constellation effectively finishes the medium orbit half of that pairing, years after.

Sunday’s mission was already a something on SpaceX’s manifest well before O3b mPower entered the picture. This flight marked its 29th trip to orbit, a history that includes two crewed Axiom missions, the European Space Agency’s Euclid telescope and 22 separate Starlink batches. SpaceX has landed boosters on the droneship A Shortfall of Gravitas so often that Sunday’s touchdown attempt, if it went as planned, was set to be the 661st successful Falcon booster landing to date.

For a company that pushed the Starlink constellation past 11,000 satellites back in August, almost entirely through bulk launches from California, Sunday’s flight was a reminder that SpaceX’s schedule still has room for someone else’s satellites too. SES gets a finished network built for a narrower set of customers, and Falcon 9 gets one more line on an already long resume.

Continue Reading

Elon Musk

Tesla gives the Roadster an official “Go for launch” demonstration date

Tesla teased an October 1 Roadster reveal, reviving years of delayed SpaceX thruster hover promises.

Published

on

By

Concept rendering of a Tesla Roadster with SpaceX Package via Grok
Concept rendering of a Tesla Roadster with SpaceX Package via Grok

Tesla teased an October 1 event date for its next generation Roadster, posting an image on X Saturday that shows the car lit up like it is sitting on a launch pad, with the date “10.01” stamped across the bottom and the caption “Go for launch.” A countdown clock on Tesla’s Roadster order page now points to the same date, which falls on a Thursday. The company has not said where the event will happen or whether it will be streamed at the moment. Stay with us @Teslarati for live updates.


Tesla has since sent formal invitations to reservation holders confirming the event will take place in Waco, Texas, about 90 minutes north of its Austin headquarters, based on a digital ticket shared on X by Sawyer Merritt. Tesla did not name the exact venue, though Waco sits close to SpaceX’s McGregor, Texas, rocket test site, previously reported as the planned location for a Roadster thruster demonstration. The invite sets the reveal for 8:30 p.m. Eastern on October 1, requires RSVPs by midnight on September 16, and limits entry to guests 21 and older. Invitations are non-transferable.

The tease follows nine years of a project defined by unimaginable specs along with slipped dates. Musk first showed the second generation Roadster in November 2017 as a surprise reveal at the end of the Tesla Semi event, promising a 0 to 60 mph time under two seconds, a top speed above 250 mph, 620 miles of range from a 200 kWh battery, and production starting in 2020. At last November’s shareholder meeting, Musk set an April 1 demo date and joked the choice gave him “deniability” if it slipped again, which it did, moving first to late April, then to “a month or so,” then to August.

Tesla Roadster SpaceX Package’s 1.1-second 0-60 mph launch visualized in concept video

Whatever Tesla shows on October 1 is expected to center on the SpaceX developed thruster package Musk has described since 2018. Internally code named A71, a nod to the Lockheed SR-71 Blackbird, the system reportedly uses cold gas thrusters fed by a composite overwrapped pressure vessel, the same tank design SpaceX uses on Falcon 9. Musk has said a thruster equipped Roadster could hit 60 mph in about 1.1 seconds under roughly 2.75 g of launch force, well past the 1.9 second figure quoted for the standard car. That version reportedly will not be street legal and has reportedly been discussed as a limited run sold through a track only program.

The standard Roadster is still expected to carry the original $200,000 base price and $250,000 Founders Series tier, both set when Tesla opened $50,000 and $250,000 reservations in 2017. Tesla VP of Vehicle Engineering Lars Moravy has confirmed production will happen at Gigafactory Texas, with Musk targeting 2027 or 2028, 12 to 18 months after whatever the company demonstrates next month.

Continue Reading

News

Tesla plans big safety improvements for Full Self-Driving v15

Published

on

Credit: Tesla

Tesla is planning to roll out some pretty significant safety and accident avoidance features with Full Self-Driving version 15, which will be the next major FSD deployment from the company.

Tesla AI lead Ashok Elluswamy used a near-miss this week to preview what the company says is the next leap in Full Self-Driving.

In response to a driver whose car had swerved away from another vehicle pulling out of a parking lot, Elluswamy wrote that he was glad the owner was safe and that “even earlier prediction of hazards, even faster reaction time and overall significantly better safety and collision avoidance” would arrive with FSD v15.

The comment landed as Tesla continues to treat software as the primary safety upgrade path. v15 is described internally as a larger architectural step, with a much bigger neural network and tighter coupling between prediction and control.

The company has already begun using early v15 software in some robotaxi operations while rolling out safety features such as Automatic Collision Evasion into current customer cars, allowing the driving stack to intervene even when the driver is in manual control.

Tesla is rolling out a new FSD version with a massive safety addition

Tesla’s published telemetry is the backbone of its safety argument. In recent North American Vehicle Safety Report data, vehicles with FSD (Supervised) engaged traveled roughly 5.1 million to 5.7 million miles between major collisions, defined as airbag-deployment events.

Tesla’s estimate of the U.S. average over the same period is about 699,000 miles per comparable crash. That is the comparison Tesla often frames as roughly seven times fewer major collisions.

A tighter comparison uses the same Tesla fleet. Cars driven manually with active safety features such as automatic emergency braking still recorded a major collision about every 2.1 million miles. Against that baseline, FSD’s advantage shrinks to roughly 2.4 to 2.7 times fewer severe crashes, which independent researchers argue is the more apples-to-apples figure.

European data released in 2026 pointed in the same direction: Tesla reported FSD as 3.5 times safer than manual driving in the Netherlands and 4.1 times fewer collisions than manually driven Teslas with active safety across more than 100 million kilometers in five approved countries.

Those numbers do not settle every debate. NHTSA’s Standing General Order still shows Tesla accounting for the large majority of U.S. Level 2 driver-assist crash reports, in part because the fleet logs far more assisted miles than rivals. Critics also note that Tesla’s “U.S. average” mixes crash definitions and driving mix.

Even so, Tesla’s own same-car comparisons, plus lower rates of automatic emergency braking and harsh maneuvers when FSD is engaged, are the evidence Elluswamy is pointing to when he says v15 will push prediction and collision avoidance further. The claim is not that software already eliminates risk. It is that each major version is meant to widen the gap between the system and an unaided human driver.

Continue Reading