NASA originally published this article on August 3, 2022. You can read the original here. Edits by EarthSky.
NASA troubleshoots Lucy after launch
Following the successful launch of NASA’s Lucy spacecraft on October 16, 2021, engineers huddled around a long conference table in Titusville, Florida. Lucy was only starting its 12-year flight, but an unexpected challenge surfaced for the first-ever Trojan asteroids mission.
Data indicated that one of Lucy’s solar arrays powering the spacecraft’s systems — designed to unfurl like a hand fan — hadn’t fully opened and latched. So the team had to figure out what to do next.
Teams from NASA and Lucy mission partners quickly came together to troubleshoot. On the phone were team members at Lockheed Martin’s Mission Support Area outside of Denver. They were in direct contact with the spacecraft.
The conversation was quiet, yet intense. At one end of the room, an engineer sat, folding and unfolding a paper plate in the same manner that Lucy’s huge circular solar arrays operate.
There were so many questions. What happened? Was the array open at all? Was there a way to fix it? Would Lucy be able to safely perform the maneuvers needed to accomplish its science mission without a fully array?
With Lucy already speeding on its way through space, the stakes were high.
NASA troubleshoots Lucy from the ground
Within hours, NASA pulled together Lucy’s anomaly response team, comprising members from science mission lead Southwest Research Institute (SwRI) in Austin, Texas; mission operations lead NASA’s Goddard Space Flight Center in Greenbelt, Maryland; spacecraft builder Lockheed Martin; and Northrop Grumman in San Diego, the solar array system designer and builder.
Donya Douglas-Bradshaw, former Lucy project manager from NASA Goddard, said:
This is a talented team, firmly committed to the success of Lucy. They have the same grit and dedication that got us to a successful launch during a once-in-a-lifetime pandemic.
United in their pursuit to ensure Lucy would reach its fullest potential, the team began an exhaustive deep dive to determine the cause of the issue and develop the best path forward. Given that the spacecraft was otherwise perfectly healthy, the team wasn’t rushing into anything.
Hal Levison, Lucy’s principal contempt from (SwRI) explained:
We have an incredibly talented team, but it was important to give them time to figure out what happened and how to move forward. Fortunately, the spacecraft was where it was supposed to be, functioning nominally, and – most importantly – safe. We had time.
A jammed lanyard
Staying focused during many long days and nights, the team worked through options. To evaluate Lucy’s solar array configuration in real time, the team fired thrusters on the spacecraft and gathered data on how those forces made the solar array vibrate. Next, they fed the data into a detailed model of the array’s motor assembly to infer how rigid Lucy’s array was. That helped uncover the source of the issue.
At last, they closed in on the root cause: a lanyard designed to pull Lucy’s massive solar array open was likely snarled on its bobbin-like spool.
After months of further brainstorming and testing, Lucy’s team settled on two potential paths forward.
In one, they would pull harder on the lanyard by running the array’s back-up deployment motor at the same time as its primary motor. The power from two motors should allow the jammed lanyard to wind in further and engage the array’s latching mechanism. While both motors were never originally intended to operate at the same time, the team used models to ensure the concept would work.
The second option: use the array as it was, nearly fully and generating more than 90% of its expected power.
Barry Noakes, Lockheed Martin’s deep space exploration chief engineer, stated:
Each path carried some element of risk to achieve the baseline science objectives. A big part of our effort was identifying proactive actions that mitigate risk in either scenario.
Testing the options
The team mapped out and tested possible outcomes for both options. They analyzed hours of the array’s test footage and constructed a ground-based replica of the array’s motor assembly. Then they tested the replica past its limits to better understand risks of further deployment attempts. They also developed special, high-fidelity software to simulate Lucy in space. Plus, it would gauge any potential ripple effects a redeployment attempt could have on the spacecraft.
Frank Bernas, vice president of space components and strategic businesses at Northrop Grumman, commented:
The cooperation and teamwork with the mission partners were phenomenal.
After months of simulations and testing, NASA decided to move forward with the first option, using a multi-step attempt to fully redeploy the solar array. On seven occasions in May and June, the team commanded the spacecraft to simultaneously run the primary and backup solar array deployment motors. The effort succeeded, pulling in the lanyard, and further opening and tensioning the array.
The mission continues as planned
The mission now estimates that Lucy’s solar array is between 353 degrees and 357 degrees open (out of 360 total degrees for a fully array). While the array is not fully latched, it is under substantially more tension, making it stable enough for the spacecraft to operate as needed for mission operations.
The spacecraft is now ready and able to complete the next big mission: an Earth-gravity assist in October 2022. Lucy should arrive at its first asteroid target in 2025. During its 12-year journey, the spacecraft will visit seven different asteroids – a main belt asteroid and six Trojans. Lucy will study the geology, surface composition and bulk physical properties of these bodies at close range.
Bottom line: Soon after launch, engineers discovered one of the solar arrays powering Lucy’s systems didn’t fully open and latch. The Lucy team was able to command the spacecraft to successfully redeploy the solar array.
Read more: Lucy mission to Jupiter’s Trojans gets the nod from NASA
Read more: Lucy spacecraft launched today to Jupiter’s Trojans