A fast-moving wildfire, one of many raging across Spain, bore down on the Madrid Deep Space Communications Complex on Friday, forcing an evacuation and temporarily suspending operations at one of NASA's most important tracking stations.
The tracking station is part of NASA's Deep Space Network, operating in concert with similar facilities in California and Australia to provide global coverage as Earth's rotation brings the planets, stars, and deep space probes in and out of view. The network supports more than 40 missions from the Moon to the edge of the Solar System, including Artemis, the James Webb Space Telescope, and NASA's twin Voyager spacecraft.
A NASA spokesperson confirmed the tracking station in Spain, located in the hills nearly 40 miles (65 kilometers) west of central Madrid, was evaluated Friday "due to ongoing wildfires in the region. Photos and video from the area showed flames and smoke plumes rising over the ground station's antenna array, anchored by a 230-foot-diameter (70-meter) radio dish and a collection of smaller 112-foot (34-meter) antennas.
A fast-moving wildfire, one of many raging across Spain, bore down on the Madrid Deep Space Communications Complex on Friday, forcing an evacuation and temporarily suspending operations at one of NASA's most important tracking stations.
The tracking station is part of NASA's Deep Space Network, operating in concert with similar facilities in California and Australia to provide global coverage as Earth's rotation brings the planets, stars, and deep space probes in and out of view. The network supports more than 40 missions from the Moon to the edge of the Solar System, including Artemis, the James Webb Space Telescope, and NASA's twin Voyager spacecraft.
A NASA spokesperson confirmed the tracking station in Spain, located in the hills nearly 40 miles (65 kilometers) west of central Madrid, was evaluated Friday "due to ongoing wildfires in the region. Photos and video from the area showed flames and smoke plumes rising over the ground station's antenna array, anchored by a 230-foot-diameter (70-meter) radio dish and a collection of smaller 112-foot (34-meter) antennas.
NASA’s New Horizons Spacecraft Wakes from Hibernation in Good Health
Following its longest hibernation period ever of nearly a year, NASA’s New Horizons spacecraft has emerged in good health and is ready to begin transmitting science data gathered in the distant Kuiper Belt far beyond Pluto.
From left, flight controllers Mark Lahr and Josh Albers, and Mission Operations Manager Alice Bowman, monitor telemetry streaming from NASA’s New Horizons spacecraft to the mission operations center at the Johns Hopkins Applied Physics Laboratory in Laurel, Maryland, on June 24, 2026. Now approximately 5.9 billion miles (9.5 billion kilometers) from Earth, New Horizons is ready to begin transmitting science data after being awakened from its longest ever, nearly yearlong hibernation period.
NASA/Johns Hopkins APL/SwRI/Justin Gladden
On June 23, flight controllers at the Johns Hopkins Applied Physics Laboratory (APL) in Laurel, Maryland, confirmed New Horizons, acting on stored commands uplinked to its main computer last July, had safely awakened from a 321‑day hibernation period that began Aug. 7. With the spacecraft now approximately 5.9 billion miles (9.5 billion kilometers) from Earth, the radio signals carrying that confirmation took about 8 hours and 52 minutes to reach the APL Mission Operations Center via NASA’s Deep Space Network station near Madrid, Spain.
The mission team typically places New Horizons in resource‑saving hibernation mode during long cruise periods. While the spacecraft is hibernating, operators do not send commands or retrieve data, but the spacecraft continues gathering and storing data around the clock from its heliospheric plasma sensors, Solar Wind at Pluto and the Pluto Energetic Particle Spectrometer Science Investigation, as well as its space dust detector, the Venetia Burney Student Dust Counter.
Alice Bowman, the New Horizons mission operations manager at APL, said the spacecraft reported back to Earth, via the Deep Space Network, with a weekly status beacon. “Every status report through this hibernation period was ‘green,’ meaning all was well aboard New Horizons each and every week,” she said.
As New Horizons resumes active operations, Bowman noted, the team will begin downlinking spacecraft health and safety data, followed by data from the three scientific instruments. In about three weeks, the spacecraft’s onboard Alice ultraviolet spectrograph will look at the hydrogen gas distribution in the outer heliosphere, while the Solar Wind at Pluto, the Pluto Energetic Particle Spectrometer Science Investigation, and the Venetia Burney Student Dust Counter instruments continue their measurements, and the ground team conducts a series of spacecraft and instrument checkouts.
The team also is completing upgrades to the ground‑system software that will make it easier to maintain operations of the spacecraft. Tests are already underway and are expected to continue through the year.
New Horizons is operating on updated autonomy logic designed for operations farther from the Sun and to accommodate the expected reduction in power and the naturally occurring increase in radio‑signal travel time.
The NASA spacecraft’s exploration of this distant region of the solar system marks the latest step in a journey that began in January 2006 with the fastest launch on record; a flyby of Jupiter in February 2007 that included stunning views of the gas giant and its moons; the first exploration through the Pluto system in July 2015; the first exploration of a Kuiper Belt object, Arrokoth, in January 2019, and unique studies of the Sun’s outer heliosphere and dozens of additional Kuiper Belt objects since then.
For more information on NASA’s New Horizons mission, visit:
NASA pushed its Deep Space Network beyond its limits during the Artemis I mission nearly four years ago. The global array of deep space communications antennas couldn't keep up with the routine demands of 40 robotic science missions and the extraordinary surge required by NASA's Orion space capsule as it flew around the Moon.
The experience in late 2022 reduced or delayed downlinks from several high-profile science missions, including the James Webb Space Telescope and Mars rovers, as the data-hungry Artemis I mission took priority on NASA's communications network. And that was before the first Artemis mission with astronauts onboard. When Artemis II launched April 1, NASA called upon the Deep Space Network (DSN) again to connect Mission Control to the Orion capsule as it soared more than a quarter of a million miles from Earth.
With a crew of four flying inside the spacecraft, the agency's appetite for data from Orion on Artemis II was even higher than it was on Artemis I. But at a little more than nine days, the Artemis II mission was shorter than the 25 days Artemis I spent in space, helping alleviate the communications overload. Artemis I also launched 10 small CubeSats into deep space, many of which required tracking and telecom services from the DSN. Artemis II carried fewer CubeSats.
NASA pushed its Deep Space Network beyond its limits during the Artemis I mission nearly four years ago. The global array of deep space communications antennas couldn't keep up with the routine demands of 40 robotic science missions and the extraordinary surge required by NASA's Orion space capsule as it flew around the Moon.
The experience in late 2022 reduced or delayed downlinks from several high-profile science missions, including the James Webb Space Telescope and Mars rovers, as the data-hungry Artemis I mission took priority on NASA's communications network. And that was before the first Artemis mission with astronauts onboard. When Artemis II launched April 1, NASA called upon the Deep Space Network (DSN) again to connect Mission Control to the Orion capsule as it soared more than a quarter of a million miles from Earth.
With a crew of four flying inside the spacecraft, the agency's appetite for data from Orion on Artemis II was even higher than it was on Artemis I. But at a little more than nine days, the Artemis II mission was shorter than the 25 days Artemis I spent in space, helping alleviate the communications overload. Artemis I also launched 10 small CubeSats into deep space, many of which required tracking and telecom services from the DSN. Artemis II carried fewer CubeSats.
Preparations for Next Moonwalk Simulations Underway (and Underwater)
This sunset photo shows Deep Space Station 14, the 230-foot-wide (70-meter) antenna at the Goldstone Deep Space Communications Complex near Barstow, California, part of NASA’s Deep Space Network.
NASA/JPL
NASA has completed the investigation into the damage sustained last year at its 70-meter radio-frequency antenna, known as the Deep Space Station 14 (DSS-14), at the Goldstone Deep Space Communications Complex near Barstow, California. The agency has classified the event as a Type A mishap based on the total cost of damages. The antenna will remain offline to complete repairs and previously scheduled upgrades.
“NASA takes safety and any departure from established procedures seriously, and the investigation at Goldstone made clear that we must strengthen our processes. We are acting on the investigation’s findings,” said Joel Montalbano, acting associate administrator for NASA’s Space Operations Mission Directorate at the agency’s headquarters in Washington. “We will update and improve procedures, rebuild core in-house capabilities, and reinforce operational discipline across the Deep Space Network. NASA remains focused on learning from this and modernizing systems, so DSS-14 and the broader network are ready to support our ambitious future missions.”
On Sept. 16, 2025, the DSS‑14 antenna over‑rotated while actively tracking the Juno mission, placing excessive stress on cabling and associated structural supports. Water lines tied to the antenna’s fire‑suppression system also were damaged, causing significant flooding in the facility. There were no injuries.
NASA convened a Mishap Investigation Board, bringing together experts from across the agency to examine the technical, organizational, and cultural factors behind the incident. The board conducted on‑site inspections, interviews, and detailed reviews of technical documentation and operational logs from all three Deep Space Network sites. The board completed its final report in April and submitted it for agency concurrence.
The investigation issued findings and recommendations that emphasize training, technical rigor, operational procedures, system design, clear roles and responsibilities, and safety assurance. At the same time, teams already are applying lessons learned across all network sites to improve operational consistency. These steps will help bolster the network and reduce the risk of future mishaps.
In its final report, the board found the mishap primarily stemmed from software weaknesses, human error, and an undetected failure in the antenna’s hydraulic limit system. Investigators determined an electrical issue at the antenna the previous day caused the control system to misreport the antenna’s rotation state, an issue that went unnoticed and triggered multiple limit-stops during the Juno track on Sept. 16. While working to identify the limit-stop problem, operators performed several troubleshooting steps that inadvertently bypassed software and hardware safeguards, which ultimately led to the over-rotation incident. After flooding in the antenna base was observed, operators attempted to stow the antenna as a safety precaution, however, because the system had already passed the rotation limits, this action drove the antenna further into over‑rotation, causing additional damage.
Additionally, the investigation found the antenna’s hydraulic limit system, its final mechanical safeguard, was inoperable on Sept. 16 after being damaged in an undocumented prior incident. The system also had not been adequately tested for an undetermined period of time.
Investigators also concluded workplace culture pressured operators to work as expeditiously as possible, often stretching beyond their usual roles, expertise, and training, to keep the antenna operating. The board states the cultural conditions observed at Goldstone were not present at the network’s other sites, where roles and responsibilities are followed more consistently. Other contributing factors outlined in the report include inadequate procedures, reliance on undocumented practices and tacit knowledge, and gaps in the antenna’s control logic. NASA will accept this as the final report.
The agency estimates repairs will cost between $4.1 and $4.6 million, with a final figure to be determined after the antenna’s systems are fully assessed. The antenna will remain offline as it enters its previously scheduled extended maintenance and upgrade period, originally set to begin in August and expected to be completed by October 2028. These upgrades are part of broader network improvements essential to supporting future exploration and science missions, as well as enhancing the nation’s planetary defense capabilities.
“We are committed to learning everything we can from this incident, and we’ve already begun putting those lessons into practice,” said Kevin Coggins, deputy associate administrator for NASA’s SCaN (Space Communications and Navigation) Program at the agency’s headquarters. “Our teams are working to strengthen and standardize processes and training across all three network sites to ensure it remains resilient, consistent, and ready to support the next generation of missions. Every challenge is an opportunity to improve, and this is no exception.”
The Deep Space Network continues to provide full coverage for more than 40 missions despite the DSS‑14 incident. The network’s 13 other antennas, located at complexes in California, Australia, and Spain, are supporting all tracking needs without interruption. A dedicated scheduling team allocates antenna time across the network to meet each mission’s science and data‑return objectives. The team also maintains continuous coverage when an antenna goes offline for maintenance or an unexpected outage.
To view the report, which includes redactions to protect proprietary and privacy-sensitive material, visit:
Login
