NASA's Artemis II mission generated an unprecedented flood of imagery, video, and telemetry that strained the agency's decades-old space communications infrastructure, according to a recent episode of NASA's Houston We Have a Podcast. Greg Heckler, deputy program manager for capability development at NASA's Space Communications and Navigation (SCaN) program, told host Gary Jordan that the demand for data from the 10-day lunar flight—including live streams , still photos, and engineering telemetry—exceeded what the current Near Space Network and Deep Space Network were designed to handle. The episode underscores a critical bottleneck as NASA prepares for sustained lunar surface operations under Artemis.

The insatiable data hunger of Artemis II

During the Artemis II mission, which carried four astronauts around the Moon in a 330-cubic-foot Orion capsule, every discipline inside NASA wanted more data—and wanted it faster, Heckler explained on the podcast. Engineers needed telemetry to resolve technical issues, scientists craved observation context,and flight controllers required real-time operational data. The Public Affairs office alone was responsible for distributing live streams and still images to a global audience, competing with dozens of other data-hungry teams. "The demand for data delivered quickly is insatiable," Jordan noted, quoting the collective cry of "more, more, more" from across the agency. According to the podcast, the current communications networks—tried-and-true radio-frequency systems shared with many other missions—were built for an era when data volumes were far lower.

Why the 60-year-old Deep Space Network may not cut it

The Near Space Network and Deep Space Network that supported Artemis II, as reported in the podcast, have been in use for decdaes, supporting everything from low Earth orbit missions to the farthest reaches of the solar system. But the Artemis campaign demands a step change: sending data to the ground more quickly means less data has to be stored onboard, reducing risk and enabling richer science and operations. Heckler's SCaN capability development branch is focused on exactly that—figuring out what new infrastructure, from optical communications to more powerful antennas, will be needed to handle the torrent of information expected from lunar surface habitats, rovers, and eventually Mars missions.

Greg Heckler: from a magnet school in Indianapolis to NASA's comms lead

Heckler shared his personal journey on the podcast, describing how he grew up in Toledo, Ohio,and moved to Indianapolis at age 12, where he attended math and science magnet schools. He singled out a pivotal teacher, Dr. Blatchley, a PhD physicist who chose to teach at an inner-city school. "Not only me, but a lot of my friends I still have today—Dr. Blatchley kind of molded us into what we are," Heckler said. That cohort went on to become engineers, physicists, and mathematicians, many of them at Purdue University. Heckler himself chose aerospace engineering because it struck him as "the hardest and most interesting" field , eventually landing an internship at NASA Goddard after his sophomore year—a path that led to his current role shaping the future of deep-space communication.

The open question: which technologies will replace radio?

The podcast episode, while rich in vision, leaves several critical questions unanswered. Heckler did not specify which candidate technologies—optical laser links, new frequency bands, or software-defined radios—are likely to be deployed first for lunar missions. Nor did the episode mention a timeline or budget for the upgrades, which could cost hundreds of millions of dollars. Given that the Artemis II mission already stretched the current network, the gap between ambition and infrastructure is a clear risk. the source also does not address how the SCaN program plans to avoid traffic jams when multiple lunar assets—including the Gateway station—need simultaneous high-bandwidth links.