Keep Factually independent

Whether you agree or disagree with our analysis, these conversations matter for democracy. We don't take money from political groups - even a $5 donation helps us keep it that way.

Loading...Time left: ...
Loading...Goal: $500

Fact check: Why did Hegseth ban the Navy from sharing weather data with NOAA?

Checked on July 7, 2025

1. Summary of the results

Based on the analyses provided, there is no evidence that Pete Hegseth was responsible for the Navy banning the sharing of weather data with NOAA. The sources reveal a completely different narrative about this weather data situation.

The actual reason for the Navy's decision to stop sharing satellite weather data with NOAA relates to technical and security considerations, not a policy directive from Hegseth. Specifically, the analyses indicate that the decision was driven by:

  • The transition to the Weather System Follow-on Microwave (WSF-M) system [1] [2]
  • The discontinuation of the Defense Meteorological Satellite Program (DMSP) due to its age and cybersecurity risks [1] [3]
  • Cybersecurity concerns with the aging DMSP system [1] [3]

Notably, the discontinuation was even delayed due to a request from NASA, suggesting this was a technical transition rather than a punitive policy decision [3].

2. Missing context/alternative viewpoints

The original question fundamentally mischaracterizes the situation by attributing the Navy's decision to Pete Hegseth when none of the analyzed sources mention Hegseth as being involved in this decision [1] [2] [3] [4].

The missing context includes:

  • This appears to be a routine technological transition from an aging satellite system to a newer one, rather than a politically motivated "ban"
  • The decision involved legitimate cybersecurity considerations regarding the aging DMSP system [1] [3]
  • NASA's involvement in requesting delays suggests this was a collaborative, technical decision rather than a unilateral policy directive [3]

While one source mentions Hegseth in relation to climate policy discussions, it does not connect him to the Navy's weather data sharing decision [5]. Another source discusses Project 2025's potential impact on NOAA and the National Weather Service, but again makes no connection to Hegseth or the Navy's specific decision [6].

3. Potential misinformation/bias in the original statement

The original question contains significant factual inaccuracies that could constitute misinformation:

  • False attribution: The question assumes Hegseth was responsible for the decision when no evidence supports this claim across any of the analyzed sources [1] [2] [3] [4]
  • Mischaracterization of the decision: Framing this as a "ban" implies a punitive or politically motivated action, when the evidence suggests it was a technical transition driven by cybersecurity and modernization concerns [1] [2] [3]
  • Loaded language: The use of "ban" creates a negative connotation that doesn't align with the technical nature of the actual decision

This type of misinformation could benefit those seeking to politicize routine military technological transitions or create controversy around defense officials without factual basis. The question appears to conflate separate issues - Hegseth's general climate policy positions with an unrelated Navy technical decision about satellite systems.

Want to dive deeper?
What is Pete Hegseth's stance on weather data sharing between the Navy and NOAA?
How does the ban on sharing weather data affect NOAA's forecasting capabilities?
What are the national security implications of restricting Navy weather data sharing with NOAA?
Did Pete Hegseth's decision to ban Navy weather data sharing with NOAA receive congressional approval?
How do other countries' militaries share weather data with their respective meteorological agencies?