> On March 3, the team noticed that activity from one part of the flight data system stood out from the rest of the garbled data. While the signal wasn’t in the

> On March 3, the team noticed that activity from one part of the flight data system stood out from the rest of the garbled data. While the signal wasn’t in the format the Voyager team is used to when the flight data system is functioning as expected, an engineer with NASA’s Deep Space Network was able to decode it. Such cool work. Imagine issuing debug commands into your Prod system, waiting 40 hours for an unintelligible reply, then one keen engineer notices a pattern and is able to extract something meaningful from it. It's amazing the expertise on these systems continues to develop and thrive.