Boeing’s new Starliner crew capsule has docked for the first time with the International Space Station, completing a major objective in a crucial test flight into orbit without astronauts aboard.
The rendezvous of the gumdrop-shaped CST-100 Starliner with the orbital research outpost, currently home to a seven-member crew, occurred on Friday nearly 26 hours after the capsule was launched from Cape Canaveral US Space Force Base in Florida.
Starliner lifted off on Thursday atop an Atlas V rocket furnished by the Boeing-Lockheed Martin joint venture United Launch Alliance (ULA) and reached its intended preliminary orbit 31 minutes later despite the failure of two onboard thrusters.
Boeing said the two defective thrusters posed no risk to the rest of the spaceflight, which comes after more than two years of delays and costly engineering setbacks in a program designed to give Nasa another vehicle for sending its astronauts to and from orbit.
Docking with ISS took place at 8.28pm EDT (00.28 GMT Saturday) as the two vehicles flew 271 miles (436km) over the south Indian Ocean off the coast of Australia, according to commentators on a live Nasa webcast of the linkup.
It marked the first time spacecraft from both of Nasa’s Commercial Crew Program partners were physically attached to the space station at the same time. A SpaceX Crew Dragon capsule has been docked to the space station since delivering four astronauts to ISS in late April.
Much was riding on the outcome, after an ill-fated first test flight in late 2019 nearly ended with the vehicle’s loss following a software glitch that effectively foiled the spacecraft’s ability to reach the space station.
Subsequent problems with Starliner’s propulsion system, supplied by Aerojet Rocketdyne, led Boeing to scrub a second attempt to launch the capsule last summer.
Starliner remained grounded for nine more months while the two companies sparred over what caused fuel valves to stick shut and which firm was responsible for fixing them, as Reuters reported last week.
Boeing said it ultimately resolved the issue with a tem
