NOAA, NASA, and Space Force each operate satellites which contribute to our understanding of the weather but have different priorities, time scales, and acquisition approaches.
NOAAs mandate is protecting United States lives and property with operational (not research) satellites, with the planning occurring within the National Environmental Satellite Data and Information Service (NESD(S). NOAA collects satellite data for ingest into Numerical Weather Prediction models supporting short-term and medium-term forecasts, which broadcast meteorologists use for the local weather forecasts. Importantly, NOAA coordinates with international weather agencies, especially EUMETSAT, sharing data for global weather models. NOAA does not develop the technology or acquire weather satellites, rather they work through NASA for these traditionally expensive procurements. NOAA also directly procures commercial data through the Commercial Weather Data program, in which, rather than owning satellites they buy Radio Occultation and soon other data. NOAA is prohibited by the General Accounting Office from developing new satellite technology so they rely on other agencies for this purpose. Current operational satellites include GOES series and JPSS.
In contrast, NASA’s mission is primarily atmospheric and climate science research which improves our understanding of the Earth, along with supporting NOAA acquisitions. NASA satellites such as AIRS have contributed to weather data. NASA Earth Science Technology Office has developed new weather technologies such as TEMPEST-D which measures precipitation. Recently, NASA Earth Science Division developed the TEMPO satellite for aerosol and air quality measurements, and the CYGNSS satellite constellation for Radio Occultation measurements of upper atmospheric temperatures and other properties. The governing document for NASA Earth Science priorities is the ESAS Decadal Survey, of which priorities such as 3D Winds, Planetary Boundary Layer, and Air Quality are typical observation interests.
In comparison, the Department of Defense is mission-focused, at a global and hyper-local level with a wide variety of data products including some not a priority to NOAA. In terms of responsibilities, Space Force is the primary acquisition and operation office for weather satellites, while the Air Force Research Laboratory supports technology demonstrations and prototype development. Air Force Life Cycle Management Center supports new weather data processing technology development and is the acquisition office for the Commercial Weather Data Pilot. The Naval Research Laboratory (NRL) supports development of prototype remote sensing satellites specific to Navy METOC needs. Example satellites include the Defense Meteorological System Program polar satellite program and the NRL WindSat program. The governing document for DoD priorities is the 2014 Joint Requirements Observing Committee for Space Based Environmental Monitoring (SBEM). This document lists the 12-gaps in weather measurements, including Theater Weather Imaging and Cloud Characterization. Unfortunately, the document was outdated by the time it was released, as it did not include Microwave and Infrared Sounding.
Regarding applications, Air Force 557th Weather Wing provides the data processing and forecasts support for all the branches, except Navy. For the Navy, the Naval Meteorology and Oceanographic Command (METOC) provides the fleet with critical weather and oceanographic data. For the DoD, instead of a 5-day forecast, an example data request may be visibility in Kandahar, Afghanistan at 0500 hours from ground to 15000 ft. The increase in Uncrewed Autonomous Vehicle operations adds additional needs on DoD weather, as drones can be more susceptible to high winds, icing, and other unfavorable conditions.
These US government organizations work closely with each other to coordinate activities and leverage each other’s expertise. For example, Brandywine Photonics CHISI instrument started as a Phase II SBIR project and transitioned to a NOAA Phase III SBIR. Space 2.0 has changed the landscape of these collaborations, whereas formerly the organizations would team on one big satellite (failed NPOESS program), they can now each contribute one satellite to a hybrid space architecture.