Roles and Responsibilities - DAFMAN15-129 PDF

DAFMAN15-129 7 SEPTEMBER 2023 7 Chapter 2 ROLES AND RESPONSIBILITIES 2.1. Air Force Director of Weather. The Director of Weather will: 2.1.1. Manage weather...

DAFMAN15-129 7 SEPTEMBER 2023 7 Chapter 2 ROLES AND RESPONSIBILITIES 2.1. Air Force Director of Weather. The Director of Weather will: 2.1.1. Manage weather services for the DAF and Army. 2.1.2. Provide Air Force Weather (AFW) functional expertise to coordinate and advocate for applicable Intelligence Community (IC) weather priorities and requirements. 2.1.3. Provide guidance and develop doctrine, policy, and standards for U.S. weather support to the DAF, Army, unified commands, North Atlantic Treaty Organization (NATO), other allies, coalition partners, national programs, and emergency response operations. 2.1.4. Serve as the Functional Area Manager (FAM) for the AFW enterprise IAW DAFI 10- 401, Operations Planning and Execution. 2.1.5. Evaluate the effectiveness and readiness of weather forces by maintaining oversight of Weather Technical Readiness program’s most critical processes through analysis of readiness reporting data. 2.1.6. Develop, coordinate, and approve interservice, intra-service, interagency, and international support agreements. 2.1.7. Provide policies and procedures and tools to measure and evaluate the operational effectiveness and technical performance of selected atmospheric and space environmental weather products (WPs). 2.1.8. Develop and implement mid- and long-range strategy and vision for the organization, equipment, manpower, and technology necessary to meet future DAF and Army weather requirements. Act as advocate for all weather requirements. 2.1.9. Engage with service, interagency, international, industry, and academic partners to advance programs and initiatives including numerical weather modeling, climate monitoring, arctic forecasting, hydrology, artificial intelligence, information warfare, electromagnetic spectrum and space weather, environmental sensing, and space-based environmental monitoring (SBEM). 2.1.10. Serve as Functional Manager for officer, enlisted and civilian career fields delegated by the Functional Authority, the HQ AF Deputy Chief of Staff, Operations. 2.1.11. Provide training products and technical services to the field. 2.1.12. Oversee Training Requester Quota Identifier management responsibilities for the Army Weather Support Course allocating seats to Major Commands (MAJCOMs). 2.1.13. Oversee and advocate for the Air Force Weather Weapons System (AFWWS) financial portfolio. 2.1.14. Lead Strategy, Design, Planning, Programming and Budget (SDPPBE) processes and advocate to the Air Force Corporate Structure for AFWWS development, fielding, and sustainment. 8 DAFMAN15-129 7 SEPTEMBER 2023 2.1.15. Liaise with Department of Army HQ, Training and Doctrine Command, Army Futures Command and Army Materiel Command (AMC), and Army Installation Management Command (IMCOM) for weather support to U.S. Army operations. 2.1.16. Liaise with USSF HQ, Space Operations Command (SpOC), Space and Systems Command (SSC) and Space Training and Readiness Command, for weather support to USSF operations. 2.1.17. Serve as a member of the Global Integrated Intelligence and Reconnaissance Council of Colonels, Enterprise Information Technology (IT) Advisory Council and Centralized Asset Management Advisory Council 2.1.18. Advise the Department of Defense (DoD) lead agent for the Next Generation Weather Radar (NEXRAD) program, pursuant to tri-agency Memorandum of Agreement with DoD, Department of Commerce and Department of Transportation, Interagency Operation of the Weather Surveillance Radar-1988, Doppler (WSR-88D). 2.1.19. Serve as the Security Controls Assessor Representative for AFWWS National Security System to work with the Program Manager, Information System Security Manager, Information System Security Officer, and Risk Management Framework (RMF) team to assess security controls for the Security Control Assessor per AFI 17-101, Risk Management Framework (RMF) for Air Force Information Technology (IT). 2.1.20. Serve as the AFWWS Lead in the implementation of DoD/DAF cyber policy and USCYBERCOM/AFCYBER order compliance oversight. 2.1.21. Serve as the Functional Data Officer to develop data policies, guidance, procedures, and standards related to AFW and establish related training. Manage and oversee compliance to these data policies to protect and manage data as a strategic asset. Serves as senior advisor to the AF Chief Data and Artificial Intelligence Office for all data matters within the weather enterprise, per DoD Data Stewardship Guidebook Section 2.2, AFI 17-140, Cybersecurity Architecting, section 2.5, and DAFI 90-7001, Enterprise Data Sharing and Data Stewardship. 2.2. Major Command (MAJCOM), Component MAJCOM (C-MAJCOM), Component Numbered Air Force (C-NAF), and Army Service Component Command (ASCC) weather staffs. 2.2.1. MAJCOM Weather Staffs. In addition to the requirements in AFPD 15-1, Weather Operations, MAJCOM weather staffs: 2.2.1.1. Manage deployment taskings for weather resources within its MAJCOM IAW DAFI 10-401 and AFI 10-403, Deployment Planning and Execution. 2.2.1.2. Provide weather inputs applicable to the development/revision of weather support plans and other documents for their command. 2.2.1.3. Engage in planning, programming, and budgeting for MAJCOM weather resources IAW AFI 65-601, Volume 1, Budget Guidance and Procedures. 2.2.1.4. Coordinate with applicable contract offices to ensure contracted weather support is appropriately defined IAW AFI 64-102, Installation Contracting. 2.2.1.5. Manage execution of MAJCOM weather programs. DAFMAN15-129 7 SEPTEMBER 2023 9 2.2.1.6. Provide staff assistance, technical training assistance, and technical consultant assistance to assigned weather organizations upon request. 2.2.1.7. Provide weather subject matter expertise to the MAJCOM Inspector General, serve as pertinent oversight authority for inspection deficiencies against aligned weather organizations, and assist with evaluations of aligned weather organizations upon request IAW DAFI 90-302, The Inspection System of the Department of the Air Force. 2.2.1.8. Develop and cross feed technical training materials throughout their command. 2.2.1.9. Oversee the accuracy and currency of equipment accountability and readiness reporting in authoritative databases. 2.2.1.10. Coordinate with and/or serve as Weather Data Steward(s) to establish weather data protection, sharing, and governance guidelines; maintain data names, definitions, data integrity rules, and domain values within the command; ensure compliance with legal and policy requirements, and conformance to data policies and standards; ensure application of appropriate security controls; and analyze and improve data quality. Appoint Data Managers and Data Custodians as required. Provide guidance to AFW Data Manager(s) per the per DoD Data Stewardship Guidebook Section 2.3 and DAFI 90-7001. 2.2.2. C-MAJCOM, C-NAF, and ASCC weather staffs will: 2.2.2.1. Coordinate with the Combatant Command (CCMD)/Joint Force Commander staff, Senior Meteorological and Oceanographic (METOC) Officer (SMO), Joint METOC Officer (JMO), and service component staffs as necessary to provide weather inputs applicable to the development/revision of war, exercise, and contingency plans. 2.2.2.2. Coordinate with applicable contract offices to ensure contracted weather support is appropriately defined IAW AFI 64-105, Contingency Contracting Support, and that contracted weather capabilities are consistent with the theater weather Concept of Operations (CONOPS). 2.3. 557th Weather Wing (557 WW). The 557 WW is the DAF’s only special mission weather wing composed of two operational groups that deliver information on the past, current, and predicted state of the natural environment across all warfighting domains, to include the electromagnetic operational environment. The 557 WW enables multi-domain decision advantage for weather and non-weather warfighters and decision makers throughout the United States Government, allied, and partner nations at all levels of warfare. The 557 WW will: 2.3.1. Generate and provide environmental products (terrestrial, space, information warfare, climate) to the DoD, military Services, all unified commands, the IC, interagency, and Allied and coalition partners across multiple security domains as directed or as requested IAW Chapter 10. 2.3.2. Operate applications and conduct Forecaster-in-the-loop (FITL) processes to generate operational data and information IAW Chapter 7. Operate applications to generate numerical weather prediction (NWP) output as first look for airfield weather services, mission forecasts, specialized modeling, and automated weather products. Note: 557 WW data provides forecasters with an initial first look to assist in developing mission weather products (MWP). 557 WW data and information may be designated as controlling weather products (CWP) by a lead weather unit (LWU). 10 DAFMAN15-129 7 SEPTEMBER 2023 2.3.2.1. Operate enterprise services to disseminate products and data via DoD Information Network core services, as well as leverage alternate operational data transmission options to mitigate communication outages, as coordinated for supported operations. 2.3.2.2. Operate enterprise applications to conduct data operations to provide trusted data and products collected from other sources (e.g., space products, coalition/allied products, etc.) at security domains to meet end user requirements. 2.3.3. Conduct documentation functions IAW Chapter 3. 2.3.4. Conduct Weather Integration and Mission Execution Forecast Process (MEFP) IAW Chapter 4. 2.3.5. Provide Installation and Airfield Weather services IAW Chapter 5. 2.3.6. Provide Aviation Weather Forecasting services IAW Chapter 6. 2.3.7. Conduct Forecast and Analysis Production functions as described in Chapter 7. 2.3.8. Provide weather data to agencies processing DoD-approved Chemical, Biological, Radiological, and Nuclear (CBRN) dispersion models for CBRN consequence assessment, consequence management, and contamination avoidance IAW AFI 10-2501, Emergency Management Program and AFMAN 10-2503, Operations in a Chemical, Biological, Radiological, and Nuclear (CBRN) Environment. Maintain the capability to provide chemical downwind messages (CDM)/effective downwind messages (EDM) upon request from installation emergency management (EM), the installation emergency operations center or other disaster response/management personnel. 2.3.9. Provide backup capability for the National Weather Service's (NWS) Storm Prediction Center and Aviation Weather Center IAW established support agreements. 2.3.10. Plan, coordinate and accomplish operational test and evaluation as the AFWWS Principle Operational Test Organization IAW DODI 5000.89_DAFI 99-103, Capabilities- based Test and Evaluation. 2.3.11. Operate and maintain the Solar Electro-Optical Network (SEON). Note: SSC is the Sponsored Projects Officer (SPO) for SEON, providing sustainment and maintenance of the program. 2.3.12. Provide global merged cloud, snow, and ice analysis and forecasts for the IC. 2.3.13. Provide mission-tailored terrestrial, Electro-magnetic spectrum (EMS), space weather analyses and forecasts, indications, and warnings at appropriate security domain to meet documented requirements of commanders, planners, or operators and the IC. 2.3.14. Provide unclassified worldwide public weather planning forecasts to the Defense Media Agency per current support agreement. 2.3.15. Develop, secure, and operate applications to collect, quality control, and archive terrestrial weather and climate data to assess the state of the climate and characterize current conditions within historical context to power the unit's applied climatology mission spanning the past, present, and future climate system. 2.3.16. Develop and provide risk assessments, forensic meteorological analyses, and climate services. DAFMAN15-129 7 SEPTEMBER 2023 11 2.3.17. Provide climate and hydro-climatology (including historical data, climate predictions, and climate projections), analysis, and analyst-in-the-loop services, and subject matter expertise. 2.3.18. Develop, secure, operate, and exploit high-resolution NWP capabilities, specialized modeling applications, tailored applications, and automated graphical depictions of environmental conditions to support DAF, DoD, Inter-agency, and international partners. Act as an NWP subject matter expert. 2.3.19. Monitor analyses, forecasts, and tailored warfighter effects for quality, ensuring modeling and to ensure software applications and environmental products meet warfighter and IC requirements. 2.3.20. Provide operational modeling and simulation (M&S) support for training, acquisition and testing as required by DoD and act as the subject matter expert for operational M&S support. 2.3.21. Collect, authenticate, validate, and secure METOC data and information published to trusted DAF data layers and archives in all security domains. 2.3.22. Make available observations and forecasts of volcanic ash for DoD and intelligence community operations at multiple classification levels. 2.4. Weather Organizations supporting Space Launch, Missile, and Test Operations. Weather organizations supporting Space Launch, Missile, and Test Operations provide weather observations, forecasts, watches, observed weather warnings/advisories, specialized weather information for launch sites, specified ranges, and abort landing sites. These units will: 2.4.1. Conduct Documentation functions IAW Chapter 3. 2.4.2. Conduct Weather Integration and MEFP IAW Chapter 4. 2.4.3. Provide Installation and Airfield Weather services IAW Chapter 5. 2.4.4. Provide Aviation Weather Forecasting services IAW Chapter 6. 2.4.5. Provide operational, mission specific, and Launch Weather Officer support to DoD, National Aeronautics and Space Administration (NASA), other US government and commercial customers performing space launch, landing, recovery, or ballistic missile test operations at the Eastern or Western Range, to include generating and disseminating customer- specific WPs as organizational resources permit. 2.4.6. Coordinate with program support managers, range safety, and range coordinators, at a minimum, for determination of weather requirements for all phases of launch. 2.4.7. Provide weather “GO/NO GO” determinations for Launch Agency constraints and Lightning Launch Commit Criteria per Space Systems Command Manual (SSCMAN) 91- 710V6, Range Safety User Requirements Manual-Ground and Launch Personnel Equipment, Systems and Material Operations Safety Requirements and NASA-STD- 4010, NASA Standard for Lightning Launch Commit Criteria for Space Flight, for each launch/test mission. 12 DAFMAN15-129 7 SEPTEMBER 2023 2.4.8. Provide METOC support to Human Space Flight (HSF) operations per applicable Operation Orders (OPORDs) and in coordination with the HSF JMO and United States Space Force Command (USSPACECOM) SMO as required. 2.5. Combat Weather Units Supporting Army Operations. See AR 115-10/AFI 15-157, Weather Support and Services for the US Army, for further information. In addition to roles and responsibilities outlined in paragraph 2.14, these units, (to include Expeditionary Combat Weather Squadrons (ECWS) and ANG Combat Weather Flights (CWFs), where applicable) will: 2.5.1. Train and posture forces and equipment to provide Staff Weather Officer (SWO) support to aligned ASCC, supported land force commander(s), and aligned units, both in garrison and in tactical environments. 2.5.2. As applicable, perform Personnel Parachute Program Management duties for completion and documentation of personnel parachute/airborne training as defined in AFI 10- 3503, Personnel Parachute Operations. 2.5.3. Manage unit supply accounts and Army Modification Table of Organizational Equipment (MTOE) equipment, wherever possible, as defined in DoDI 5000.64_DAFI 23- 111, Accountability and Management of DoD Equipment and other Accountable Property and to ensure required UTC and Army-provided support equipment is on-hand and deployable. 2.5.4. As applicable, coordinate with local Central Issue Facility (CIF) and Rapid Fielding Initiative (RFI) provider to equip unit personnel with personal tactical/deployment equipment. 2.5.5. Coordinate deployment posturing, logistic requirements, and readiness exercise support through appropriate channels (e.g., Weather FAM, Unit Deployment Manager, Logistics Squadron, Army G-4/S-4, or G-2/S-2) and IAW the Weather Functional Area Prioritization and Sequencing Guide. 2.6. 23d Special Operations Weather Squadron (23 SOWS). The 23 SOWS provides Geographic Combatant Commands (GCC) with weather support tailored to meet deployed Air Force and Army Special Operations Force (AFSOF/ARSOF) mission requirements and ensure horizontal consistency with other weather units within the GCC Area of Operations. The 23 SOWS will: 2.6.1. Provide centralized weather analysis and forecasting products, and data in support of the 160th Special Operations Aviation Regiment, AFSOC Special Operations Task Groups, and deployed AFSOF/ARSOF without organic support. 2.6.2. Conduct Documentation functions IAW Chapter 3. 2.6.3. Conduct Weather Integration and MEFP IAW Chapter 4. 2.6.4. Provide Installation and Airfield Weather services IAW Chapter 5. 2.6.5. Provide Aviation Weather Forecasting services IAW Chapter 6. DAFMAN15-129 7 SEPTEMBER 2023 13 2.7. 53d Weather Reconnaissance Squadron (WRS). The 53 WRS (Air Force Reserve Command (AFRC)) provides weather reconnaissance (WR) aircraft and crews, command, and control (C2), support equipment and personnel capabilities in support of CCMD requirements. IAW AFMAN 11-202V3, Flight Operations, and AFMAN 11-2WC-130JV3, WC-130J Operations Procedures, FCM Publication 12, National Hurricane Operations Plan, and FCM Publication 13, National Winter Season Operations Plan. These operations are managed as three different types of missions: Defense Support to Civil Authorities (DSCA), DoD support, and other outside agency support. The 53d WRS will: 2.7.1. Support missions for the Department of Commerce are considered DSCA missions with the National Oceanic and Atmospheric Administration (NOAA) identified as the lead federal agency. These operations are conducted under Chairman of the Joint Chiefs of Staff DSCA Execution Order authority and are conducted under the tactical control of either USNORTHCOM or USINDOPACOM. AFI 10-801, Defense Support to Civil Authorities, identifies the AFRC Commander as the force provider of WR forces. 2.7.2. Support DoD missions include environmental information collection requiring either airborne collection or deployment of collection sensors to support DoD research or operations. 2.7.3. Support other outside agency missions to include any agencies outside of the DoD requesting WR capabilities primarily for research purposes. These operations must be funded by the requesting organization and should provide a benefit to the DoD. Requests for support should be submitted for vetting to AFRC weather branch via email at [email protected]. 2.7.4. As Chief, Aerial Reconnaissance Coordination, All Hurricanes (CARCAH), 53 WRS OL-A, Miami, FL provide command and control and liaison support for WR DSCA operations. In this role, the CARCAH will: 2.7.4.1. Plan, organize, and coordinate all WR DSCA activities to meet interagency strategic and operational objectives to include the coordination of any WR requests for assistance (RFA) for publishing in a WR Plan of the Day (POD). The POD is considered the validated and approved RFA. 2.7.4.2. Provide oversight of WR DSCA operations to include mission planning and execution, to include real-time adjustment of reconnaissance patterns based on the dynamic meteorological scenario, coordinating foreign overflight clearance, and a metrics program to measure operational demand and effectiveness. 2.7.4.3. Support data collection and dissemination operations through ensuring aircraft have threat situational awareness, data quality assurance, and act as the focal point for interagency data sharing. 2.7.4.4. Represent the WR functional capability on interagency working groups to align research and sensor integration programs as well as lead federal agency requirements with operational needs. 2.8. Air Operations Center (AOC) Weather Specialty Teams (WST). AOC WSTs integrate weather information into the full spectrum of operations and intelligence, providing environmental situational awareness and enabling decision advantage for commanders IAW DAFMAN13- 1AOCV3. WSTs will: 14 DAFMAN15-129 7 SEPTEMBER 2023 2.8.1. Use analyzed weather information and data provided by other weather organizations to build a 4-D picture of the battlespace and the environmental threats affecting it, in addition to 2.8.2. Provide Weather Operations C2 for Air Component supporting units within the theater of operations and coordinate with MAJCOM Staff and SMO for multi-unit operations and exercises. 2.9. Air Combat Command Air Operations Squadron Weather Flight (ACC AOS/WX). The ACC AOS/WX provides tailored weather support to AOS-controlled missions and may also be called upon to support other non-AOS controlled missions as required (e.g., ACC GLOBAL POWER, E-3 AWACS/E-8 JSTARS). ACC AOS/WX will: 2.9.1. Determine and document weather support requirements for all aircraft movements under control of the ACC AOS. 2.9.2. Assume LWU role and inherent responsibilities for all AOS-controlled missions, including all CORONET movements. 2.10. Air Force Operations Group (AFOG) Weather Branch. IAW Air Force Mission Directive 23 (AFMD 23), Air Force Operations Group, the AFOG Weather Branch provides and/or arranges for global weather support to Headquarters Department of the Air Force (HQ DAF), Headquarters Department of the Army (HQDA), National Joint Operations Intelligence Center (NJOIC), U.S. Air Force and U.S. Army Crisis Action Teams, and Headquarters U.S. Army Corps of Engineers (HQ USACE) supporting HQ AFW policy, and other supporting agreements. The AFOG Weather Branch is also responsible for providing and/or arranging situational awareness weather products and briefings to senior DoD and U.S. government leaders as well as arranging for dissemination of local weather alerts for the Pentagon Reservation. The AFOG Weather Branch will: 2.10.1. Tailor and integrate air, space, land, and oceanographic environmental information into situational awareness products in support of HQ DAF, HQDA, DoD Joint Staff, HQ USACE and other senior Pentagon staff organizations as required. 2.10.2. Provide staff weather support to the Air Force Crisis Action Team and Army Crisis Action Team during contingencies, emergencies, and exercises. 2.10.3. Provide climatology data/products, planning weather and other staff weather support as required. 2.10.4. Coordinate with and assist 557 WW with weather watch, warning, and advisory support as required for the Pentagon. 2.10.5. Arrange for dissemination of local weather watches, warning and advisories for the Pentagon Reservation and the National Capital Region in support of HQ DAF, HQDA, and Pentagon Building Management Office. 2.11. Contingency Response Force (CRF). CRF weather personnel perform functions and responsibilities consistent with AFI 10-202, Contingency Response Forces. DAFMAN15-129 7 SEPTEMBER 2023 15 2.12. Remotely Piloted Aircraft (RPA) support. For the purposes of this publication, the terms RPA, and Unmanned Aircraft System (UAS) are synonymous. When applicable, units will provide direct (tailored) weather support to Group 3-5 RPA and general weather support (regional forecast) to Group 1-2 RPA (direct support may be provided, resources permitting) IAW Chapter 6. NOTE: Refer to JP 3-30, Command and Control of Joint Air Operations, for definitions of unmanned aircraft groups. 2.13. Joint Typhoon Warning Center. The Joint Typhoon Warning Center (JTWC) is a joint United States Navy (USN) – Air Force weather forecast organization located in Joint Base Pearl Harbor-Hickam Hawaii and reports to USN’s Fleet Weather Center in San Diego. The JTWC issues and disseminates tropical cyclone advisories and warnings in the North-West Pacific Ocean, South Pacific Ocean, and Indian Ocean for the DoD and other U.S. government agencies. Specific forecaster responsibilities regarding JTWC tropical cyclone warnings and forecasts are described in Chapter 5. 2.14. WFs/Detachments (Dets). WF/Dets primary purpose is to integrate environmental impacts into every phase of end-user operations, from planning to execution. WFs/Dets assess the mission environment to determine environmental threats and opportunities, and where possible, identify alternatives to enable mission execution. Though each unit has unique characteristics and functions based on its parent/host unit’s mission, geographic location and level of command, core roles, responsibilities, processes, and procedures are largely the same. As required, WFs/Dets will: 2.14.1. Conduct Documentation functions IAW Chapter 3. 2.14.2. Conduct Weather Integration and MEFP IAW Chapter 4. 2.14.3. Provide Installation and Airfield Weather Services IAW Chapter 5. 2.14.4. Provide Aviation Weather Forecasting services IAW Chapter 6. 2.14.5. Provide space weather impacts to supported agencies utilizing products and services outlined in Chapter 8. 2.14.6. Develop and implement severe weather action plan (SWAP) operations to ensure sufficient personnel are available during potential/actual severe weather events or during meteorological/operational events critical to mission success (does not apply to all ANG managed U.S.C. Title 5 and contract weather sites which perform limited weather services (observing, eyes-forward, observed Watch, Warning and Advisory (WWA) support). Conduct and document annual SWAP exercises and ensure validity of plans to respond to severe weather. Real world events meet this requirement if properly evaluated and documented, to include lessons learned. 2.14.7. If equipped with upper air observing equipment, provide upper air observations as defined in Federal Meteorological Handbook No. 3 (FMH-3), Rawinsonde and Pilot Balloon (Pibal) Observations to support garrison/deployed operations. 2.14.8. Meet the operational requirements of the installation supervisor of flying program or Army equivalent. 16 DAFMAN15-129 7 SEPTEMBER 2023 2.14.9. Assist installation/garrison commanders in assessing the effects of severe weather and a changing climate on existing and planned infrastructure and facilities, and natural infrastructure using provided DOD products, services, and assessments (e.g., Air Force Severe Weather/Climate Hazard Screening and Risk Assessment Playbook, Army Climate Resilience Handbook, DOD Climate Assessment Tool (DCAT), 14WS Installation Threat Assessments, etc.). 2.15. ANG WFs. As applicable, ANG WFs are assigned roles and responsibilities outlined in paragraph 2.5 (ANG CWFs), paragraph 2.12 (ANG RPA WFs) and paragraph 2.14 (ANG WFs). The primary mission of ANG WFs while in IDT (Inactive-Duty Training) or Title-32 (Active-Duty Training) status is to train all assigned weather personnel to support aligned ANG and/or Army National Guard (ARNG) customers upon their federal mobilization. ANG personnel may support rotational taskings on a volunteer basis. Deployable ANG personnel must be trained and equipped to the same level as their RegAF counterparts. ANG personnel must train and keep current with readiness requirements to support steady state, backfill or sustainment and mobilization requirements as formally tasked by the RegAF component. 2.16. White House Military Office (WHMO) Operations. The WHMO weather unit provides essential service to the President and helps maintain the continuity of the Presidency. They provide weather observations, mission specific forecasts, watches, observed weather warnings/advisories, specialized weather information for White House functions and WHMO operational units to include the White House Communications Agency, Presidential Airlift Group, White House Medical Unit, Camp David, Marine Helicopter Squadron One, Presidential Food Service, and the White House Transportation Agency. 2.17. Research, Development, Test, and Evaluation Meteorologists (RDT&E Mets). Personnel serving as RDT&E Mets provide specialized air and space weather/environmental science support focused on DAF research, technology development, acquisition, and sustainment activities. RDT&E Mets integrate with requirements managers, program managers, and other system experts to ensure successful identification and mitigation of weather and environmental threats during the acquisition lifecycle of DAF and Joint/Allied/Coalition systems, subsystems, or end items. Support is provided during all phases of a system's lifecycle to ensure effective acquisition and sustainment of systems to satisfy valid warfighter capability needs. Weather organizations supporting DAF acquisition activities will conduct the following tasks, IAW their assigned unit's mission and available resources: 2.17.1. Identify and document, in coordination with program/project/work unit offices, environmental thresholds of systems and programs undergoing RDT&E and procurement. 2.17.2. Assist AF RDT&E projects/programs with identification and mitigation of any effects the atmospheric and space environments may have on systems, subsystems, or components. 2.17.3. Support AF development planning, capability development, and acquisition projects/programs through the identification and mitigation of any effects the atmospheric and space environments may have on the performance and/or employment of systems, subsystems, or components. 2.17.4. Provide consultation services to program managers, engineers, and MAJCOM requirements managers for inclusion of weather support and environmental threat mitigation requirements in program/system requirements documents as needed/requested. DAFMAN15-129 7 SEPTEMBER 2023 17 2.17.5. Provide meteorological analysis on system performance and employment for the life cycle of any weather-sensitive programs or basing activities. 2.17.6. Provide weather support for RDT&E activities occurring at test sites and specified ranges. 2.17.7. Coordinate test criteria and environmental support for systems undergoing testing with RDT&E projects/programs; provide or arrange for support (unique or tailored weather services/products) to those projects/programs; and monitor progress of those projects/programs for changes affecting that support. 2.17.8. Provide on-site support for test operations when required and within available resources and capabilities. 2.17.9. Assist AFW and environmental science community in identifying and developing weather support requirements for emerging technologies and weapon systems, to include modeling and simulation requirements. 2.17.10. Provide input to development of support concepts, CONOPS, and weather tactics, techniques, and procedures to inform weather support and integration for new and emerging technology. 2.17.11. When tasked, serve as SME to Sponsor Point of Contact and Technical Point of Contact (TPOC), develop or assist TPOC in authoring Small Business Innovation Research (SBIR) and/or Small Business Technology Transfer (STTR) topic solicitations, and assist TPOC in evaluating proposals. 2.17.12. Provide documentation of current/future environmental support to RDT&E efforts to AFMC weather branch, annually. 2.17.13. When required, complete initial and continuation training to include completing ACQ 101 Fundamentals of Systems Acquisition Management course and/or earning certifications in Program Management, Test and Evaluation, and/or Science and Technology Manager level 1 through Defense Acquisition University (www.dau.mil). 2.17.14. Operate specialized or nonstandard weather systems (e.g., surface and upper-air data collection sensors/systems, models, data acquisition and processing tools, etc.) required to support RDT&E projects/programs. 2.18. Units assigned weather equipment (Fixed-base and tactical). Weather units will: 2.18.1. Coordinate and establish outage reporting procedures for equipment with their aligned garrison/deployed maintenance unit. Radar, Airfield, and Weather Systems (RAWS) work centers have maintenance responsibility of weather sensing equipment (garrison or deployed) as defined in AFMAN 13-204v4, Radar, Airfield, and Weather Systems and applicable RAWS career field guidance memorandum. 2.18.2. Report outages and maintenance actions on equipment not maintained by RAWS work centers. Guidance is provided in DAFI 21-103, Equipment Inventory, Status and Utilization Reporting, DAFMAN 17-1203, Information Technology (IT) Asset Management (ITAM). 2.18.3. Maintain accountability of equipment as Defense Property Accountability System (DPAS) Property Custodian as defined in DAFMAN 17-1203 and DoDI 5000.64_DAFI 23- 111. DAFMAN15-129 7 SEPTEMBER 2023 23 Chapter 4 WEATHER INTEGRATION, PLANNING AND THE MISSION EXECUTION FORECAST PROCESS 4.1. General. Weather personnel should understand all aspects of weather’s effect on operations and relay these effects to commanders at all echelons. Commanders leverage and integrate accurate, consistent, timely, and relevant weather information to anticipate, exploit, and mitigate weather effects and enable their situational understanding of the operational environment, decision-making, and risk management. Weather personnel must understand their supported commander’s requirements and integrate weather capabilities to achieve mission success. This chapter identifies multiple concepts that need to be executed to ensure proper integration of weather personnel and information into the planning, execution, and assessment phases of operations. Weather leadership will: 4.1.1. Organize personnel to support operations that maximize the unit’s ability to reliably inject the right information at the right time every time into their supported organizations’ decision-making process. (T-3) 4.1.2. If possible, pattern duties at home station to mirror those described in Mission Capability Statements for UTCs postured at that unit. (T-2) 4.1.3. As applicable, familiarize themselves with the weather functional community Prioritization and Sequencing Guidance and the weather supplement to the War Mobilization Plan (Volume 1). 4.1.4. Establish and actively maintain working relationships with supported organizations’ key operational decision makers, operators, information specialists, tactical-level mission planners, schedulers, and weapons and tactics experts. (T-3) 4.1.5. Maintain operational situational awareness through active participation in operational end-users’ battle rhythms which include, but are not limited to, planning group(s); threat working group(s); mission planning; rehearsals; mission execution; battle update briefs; commanders update briefs; and operations updates. (T-3) 4.1.6. Understand weather and supported unit(s) TTPs, mission essential tasks (MET), and environmental sensitivities/limitations of weapon systems and their associated missions. (T-1) Use information obtained from supported units or derived from authoritative sources, such as technical orders and AFMAN 11-202v3, on the mission design series (MDS) specific aircraft operations procedures, MDS AFTTP (NIPR: https://intelshare.intelink.gov/sites/561jts/SitePages/Home.aspx or SIPR: https://intelshare.intelink.sgov.gov/sites/561jts), and AR 95-1, Aviation Flight Regulations. (T-1) 4.1.7. Leverage knowledge of historical, current, and forecast state of the environment to provide operators with the opportunity to exploit favorable environmental conditions for mission execution. (T-3) Inject environmental subject matter expertise, as appropriate, throughout the planning, execution, and assessment phases of the continuous operations cycle. (T-3) This is the opportunity for weather Airmen to offer value-added options to commanders during mission planning and execution. 24 DAFMAN15-129 7 SEPTEMBER 2023 4.1.8. Coordinate with supported units, including tenant organizations, to provide or arrange for WPs. (T-3) These include, but are not limited to, mission execution forecasts (MEFs), intelligence preparation of the battlefield (IPB), environmental inputs to mission planning/analysis, environmental staff estimates, and any other WPs to meet supported unit needs or information to attain domain awareness and meet supported unit needs. 4.1.9. Coordinate with host/parent and supporting units on required environmental inputs to tactical decision aids (TDAs). (T-3) This includes, but is not limited to, working proactively with the installation Civil Engineering, Intelligence units or IMCOM / Directorate of Public Works to ensure that the most accurate meteorological data is input into program of record TDAs. (T-3) 4.1.10. Use locally available C2 / mission planning systems / advanced battle management systems to integrate decision-grade weather information into supported unit(s) decision- making processes to the maximum extent possible (personnel tempo and operational tempo permitting). (T-3) 4.2. Coordinated Weather Operations. Coordinated weather operations ensure planners and decision-makers at every level receive consistent, comprehensive, standardized, and relevant weather information. Weather organizations will coordinate weather information with all supporting weather units for missions involving more than one unit or service. (T-1) Coordinated weather operations encompass LWU, CWP, METOC Production Center (MPC), METWATCH, MISSIONWATCH, and the MEFP. 4.3. MEFP. The MEFP is an organized and systematic process to provide decision-quality environmental information to mitigate risks and exploit asymmetric capabilities in the Military Decision-Making Process (MDMP). The MEFP specifies how to apply environmental information to mitigate mission limitations and meet operational requirements. Weather units develop processes and procedures to establish meteorological situational awareness and apply environmental weather for the parent/host unit’s decision cycle. Weather units will: 4.3.1. Utilize the MEFP to provide environmental information to mitigate risks and exploit asymmetric capabilities throughout the MDMP. (T-2) 4.3.2. Develop internal processes to continuously adapt and improve the MEFP based on coordination/feedback from supported unit(s). (T-1) Formally review and document these processes annually. (T-1) 4.3.3. The MEFP consists of two primary components, Administrative and Operational. 4.3.3.1. Administrative Process. These are steps within the MEFP which are accomplished by weather unit leadership to maximize the effectiveness of military operations. Table 4.1 details administrative processes. DAFMAN15-129 7 SEPTEMBER 2023 25 Table 4.1. Example MEFP Administrative Process. 1. Define/document Weather Thresholds a. Identify critical terrestrial and space weather thresholdvalues (e.g., airframe, mission types, weapon systems, decision timelines). b. Identify critical resource protection thresholds (e.g., maintenance, security forces,logistics, emergency response, etc.). c. Know where these parameters are applied (e.g., airfields, ranges, DZs, ARs, low-flyroutes, etc.). d. Identify training requirements to ensure all assigned weather Airmen qualified to mitigate mission-impacting environmental hazards. 2. Attain and Maintain Situational Awareness a. Identify logical process for obtaining situational awareness to identify trends and state of the atmosphere to others (e.g., shift change, shift duty checklist). b. Leverage analysis products from DoD, and U.S. Government (USG) sources. Use of non- DoD or USG products should be done only as a matter of necessity, not convenience. Whenever possible, utilize only those products that will be available during contingency or conflict situations. c. Determine best products to use (primary and back-up) for each step including purpose of the product utilized and value to the MEFP. d. Collaborate with other METOC organizations as appropriate. e. Include review of centrally or locally established C2 systems (e.g., Global DecisionSupport System (GDSS), unit flying schedules). 3. Coordinate Operations a. Identify times, criteria, and delivery format of environmental information for established supported units (e.g., LAN/webpage, mass briefing, flight weather briefing, crisis action briefing, etc.). b. Provide or arrange for support for units when away from home station. c. Request special terrestrial, climatic, and space WPs IAW Chapter 10 of this publication, if required. 4. Mission Verification/MISSIONWATCH a. Determine parameters, timelines, and critical thresholds for MISSIONWATCH. b. Standardize mission/products utilized to report WP MEF Verification (MEFVER)IAW 26 DAFMAN15-129 7 SEPTEMBER 2023 MAJCOM guidance. c. Identify products, frequency, and communication in the MISSIONWATCH process. d. Establish parameters for forecast reviews. e. Develop feedback performance mechanisms to incorporate seasonal training or specific forecast parameter improvement DAFMAN15-129 7 SEPTEMBER 2023 27 4.3.3.2. Operational process. This is the executable phase of the MEFP. Table 4.2 details the operational processes. 4.3.3.2.1. Define a methodology to incorporate analysis products, forecast techniques, and a logical, verifiable process to conduct weather operations. The process identifies data sources, documents forecast methods, and describes methods of obtaining environmental situational awareness. (T-1) 4.3.3.2.2. Ensure all sources, processes, and procedures for refining environmental information and WPs are derived from trusted DoD, U.S. government, coalition/allied military/government, or academic sources, then non-government civilian sources, in that order. (T-1) Incorporate AFH 15-101 and validated local area rules of thumb into the MEFP. (T-3) 4.3.3.2.3. Weather units will alert supporting weather organizations (e.g., LWU) to locally developing situations not encoded in meteorological reports that potentially drive amendments to forecast products or pose a risk to flight safety. (T-1) 4.3.3.2.4. Maintain consistency with LWU guidance during execution. (T-1) 28 DAFMAN15-129 7 SEPTEMBER 2023 Table 4.2. MEFP Operational Process. 1. Obtain Situational Awareness a. Identify mission types (e.g., air, ground, change of command, maintenance). b. Utilize pre-established procedures (e.g., shift change, shift duty checklist, open/close procedures). c. Review relevant operational weather products. 2. Determine Environmental Threat(s) and Opportunities of the Day a. Identify potential threats to or opportunities for alternate/modified mission execution. b. Prioritize support based on mission priority and threat to mission execution. c. Identify WPs best utilized to mitigate weather impacts. 3. WP Generation/Dissemination a. Conduct appropriate-scale review of global and theater-level products to identify state of the atmosphere affecting a particular mission. b. Analyze real-time data (e.g., PIREPs, AIREPs, radar, satellite imagery, surface observations). c. Apply specific forecast techniques (e.g., icing, turbulence, contrails, ROT). d. Integrate geographic, terrain, urbanization, and vegetation influences on the environment and the mission. e. Include EM/space weather conditions and effects on the mission. f. Generate forecast in proper format employing critical (or Go/No- Go) thresholds. Generate TDA output, as required. g. Evaluate product for accuracy and disseminate IAW established guidelines (e.g., C2 system, LAN/webpage) to appropriate customers, decision-makers, and other weather units. h. Retain WPs IAW the records disposition schedule, which is located in Air Force Records Information Management System. 4. MISSIONWATCH/Mission Verification a. Conduct MISSIONWATCH utilizing real-time WPs. b. If capability exists, notify mission C2 element if thresholds cross-critical event parameters. c. Gather feedback from supported units and review weather products, as necessary, to verify WP MEF. d. Develop weather product review based on established guidelines if necessary. DAFMAN15-129 7 SEPTEMBER 2023 29 4.4. LWU. When two or more military units operate together and share the same air/battlespace (e.g., air refueling routes, military operating areas, drop zones), the LWU, identified using the rules in Table 4.3, coordinates overall weather services for the supported mission(s) and is the liaison between supporting weather units. (T-2) When possible, the LWU for a given supported mission should be identified in an applicable OPLAN, fragmentary order (FRAGO), or TASKORD. LWU responsibilities lie with the weather unit providing weather support to the overall mission C2 element. The LWU will: 4.4.1. Coordinate with all units involved in the supported mission(s) to identify and obtain point of contact (POC) information (e.g., secure/non-secure telephone numbers, fax numbers, email addresses) for each organization. (T-2) 4.4.2. Collect information to define supported mission schedule(s), types (e.g., aerial refueling, airdrops, combat sorties and ground tactics), weapon systems and critical weather thresholds from the supported C2 element and supporting unit POCs. (T-2) 4.4.3. Determine WPs, data, and service requirements for the supported mission(s). (T-2) 4.4.4. Determine the CWP format (e.g., text, graphics), content, delivery method/times and amendment criteria. (T-2) 4.4.5. Coordinate CWP issue times and delivery methods with the supported C2 element and supporting weather organizations involved in the mission(s). (T-2) 4.4.6. Coordinate with supporting weather organizations to METWATCH the CWP and amend it as required based on mission critical weather thresholds. (T-2) 30 DAFMAN15-129 7 SEPTEMBER 2023 Table 4.3. Prioritized Rules for Determining the LWU. Rule Type of Mission Designated LWU 1. Joint Missions JMO-designated LWU for a Joint Operation in an OPORD / Exercise Directive, or FRAGO. 2. Global Power – ability to Weather unit providing the overall mission C2 hold at risk or strike any element with weather information. target anywhere, assert Note: The C2 element for GLOBAL POWER missionis national sovereignty, typically delegated to the wing-level. safeguard joint freedom of action, and create swift, decisive, precise effects (i.e., fighters, bombers) CORONET - group of Weather unit providing the ACC C2 element with 3. fighters assigned one or weather information. multiple tankers Note: Normally the ACC AOS/WX 4. Global Reach - ability to Weather unit integrated with the AMC C2 Element project military capability Note: Normally the 618 AOC (TACC)/WXD responsively–with unsurpassed velocity and precision–anywhere, and provide mobility to rapidly supply, position, or reposition joint forces. 5. Air Refueling (Training) Weather unit servicing the lead receiving aircraftunit. 6. Unmanned Aircraft Weather unit assigned to the Unmanned Aircraft Operational-Level C2 element (e.g., 432d Wing Operations Center, Global Hawk Operations Center). See Chapter 6 for more details. 7. Joint Airborne/Air Weather unit servicing the lead airlift aircraft unit. Transportability Training(JA/ATTs) & Drop Zone(DZ) 8. Landing Zones (LZ) & Weather unit attached to the lead Army unit. Land Maneuver 9. Special Operations LWU depends on nature of the operation as directed by the appointed JMO. DAFMAN15-129 7 SEPTEMBER 2023 31 10. Multinational Missions with multiple alliance/coalition METOC units should follow multinational doctrine and procedures ratified by the U.S. 11. Other For missions not defined above, units will coordinate between each other to determine the LWU. If units are unable to come to a consensus, elevate to the MAJCOM or component staff, as appropriate, to resolve. 4.5. Control Weather Products (CWPs). CWPs represent the official mission forecast and are defined by the LWU. All weather units supporting a mission as defined in Table 4.3 will utilize CWPs to ensure mission forecast consistency. (T-1) Supporting units will not deviate from the mission-specific, critical weather thresholds specified in CWPs without prior coordination with the LWU. (T-1) 4.6. METOC Production Centers (MPC). MPCs (Table 4.4) are service-retained, reach-back organizations that provide trusted METOC data and information to fulfill CCMD and component requirements. Weather personnel will coordinate MPC support IAW Chapter 10. (T-1) Table 4.4. MPCs. Force MPC METOC Capabilities and Support Provider Global and regional graphical weather forecast, 557 WW (Operational airfield, and installation (TAF and RP), aviation Weather Squadron forecasts, specialized environmental (OWS), 2d Weather information, space weather and EMS products USAF Squadron (WS), 16 WS, and services, climatology products and services, and 14 WS) numerical weather modeling and visualization products and services, data collection and dissemination services. Global and regional weather forecasts, airfield, and installation support (TAF and RP), aviation 23 SOWS USAF forecast products and services for deployed USAF/Army/USSOCOM SOF support Fleet Numerical Global and regional METOC, ensemble model, Meteorology and wave, sea surface temperature, sea anomaly USN Oceanography Center forecast products Tropical cyclone forecast products for JTWC USN INDOPACOM Naval Oceanographic USN Global Tailored global oceanographic, 32 DAFMAN15-129 7 SEPTEMBER 2023 Office hydrographic, bathymetric, geophysical, and acoustic products and services DAFMAN15-129 7 SEPTEMBER 2023 33 4.7. METWATCH. This is a deliberate process for monitoring environmental conditions in the land, air, and space domains. METWATCH identifies when and where sensed conditions significantly diverge from forecast conditions which may drive the need to update or amend forecasts and notify end users (as necessary). Units will: 4.7.1. Establish and maintain a prioritized threat-based METWATCH process for all locations for which it is responsible for characterizing environmental conditions or issuing products (e.g., WWAs), and employ RM steps to identify weather threats impacting operations and maximize effectiveness of resources. (T-1) 4.7.2. Monitor and identify changes in weather conditions that cross critical weather thresholds and evaluate forecast products/reasoning when conditions are not occurring as forecast. (T-1) 4.7.3. Amend forecasts based on specification and amendment criteria IAW established procedures. (T-1) 4.7.4. Develop METWATCH procedures to include the following: 4.7.4.1. Identify primary METWATCH data sources, document forecast methods, and standardize methods of obtaining weather situational awareness. (T-1) 4.7.4.2. Identify WPs and services affected by unexpected changes to forecast conditions at points, areas, and routes where the unit is directed or tasked as issuance authority. At a minimum, units that have METWATCH responsibilities prioritize procedures for WWAs, TAFs, Joint Operational Area Forecast (JOAFs), and flight hazards. (T-1) 4.7.4.3. Outline the actions to take when forecast conditions change during the METWATCH. (T-1) Specify the units to contact using primary and backup contact methods (e.g., telephone, e-mail, phone patch). (T-1) 4.8. MISSIONWATCH. MISSIONWATCH is the deliberate process for monitoring terrestrial weather or the space environment for specific mission-limiting environmental factors or exploitable opportunities. Weather units integrated with supported end-users should have a keen understanding of mission-critical thresholds and mission profiles. This understanding allows forecasters to continuously monitor ongoing missions for any potential threshold-crossing weather parameters and allow forecasters to quickly notify C2 elements of these changes. The MISSIONWATCH process identifies and alerts decision makers to changes that will enable mission success. Weather units will: 4.8.1. Develop procedures to determine critical thresholds requiring intensified MISSIONWATCH and update supported unit(s) on changes to environmental conditions critical to the mission. (T-1) 4.8.2. Maintain a MISSIONWATCH tailored to the mission(s) of the day. (T-1) 4.8.3. Employ sound RM techniques to assign risk, allocate resources, and direct activities to conduct MISSIONWATCH for supported unit(s) missions. (T-1) 4.8.4. Inform the issuing weather unit when WPs do not accurately reflect observed conditions and may impact mission execution. (T-1) 34 DAFMAN15-129 7 SEPTEMBER 2023 Chapter 5 INSTALLATION AND AIRFIELD WEATHER SERVICES 5.1. General. Installation and airfield weather services consists of weather observing, TAF generation, METWATCH, and RP. For Collocated Weather Organizations, the Senior Airfield Authority (SAA) coordinates airfield weather services support responsibilities when weather organizations supporting flying organizations from multiple Services (e.g., Navy and Air Force) are located at a base. 5.2. Weather Observing. Units responsible for the airfield observation evaluate conditions, prepare, and disseminate routine, local, and special weather observations. Guidance on recording and disseminating observations can be found in AFMAN 15-111, and MAJCOM supplements, as applicable. 5.3. TAFs. A TAF provides official meteorological information for flight planning and C2 activities for a specific aerodrome. These processes focus on uniformity, production, and quality assurance of final products according to locally developed guidance. AFMAN 15-124, Meteorological Codes, defines compliance and dissemination guidance. 5.3.1. TAF Roles and Responsibilities. 5.3.1.1. Weather units at assigned DAF and Army airfields responsible for airfield weather services will produce, disseminate, amend, and verify TAFs during published air-traffic controlled (ATC) hours of operation. (T-1) 5.3.1.2. The 557 WW will: 5.3.1.2.1. Produce, disseminate, amend, and verify TAFs during published ATC hours of operation or as required for airfields where the DAF or Army is assigned airfield weather services responsibilities and there are no weather personnel assigned. (T-1) 5.3.1.2.2. Produce, disseminate, amend, and verify TAFs during published ATC hours of operation or as required for airfields where ANG managed U.S.C. Title 5 and/or contract weather sites performing limited weather services. (T-1) 5.3.1.2.3. Produce, disseminate, amend, and verify TAF products for exercises, contingencies, or defense support to civil authority as tasked to fulfill CCMD requirements IAW Chapter 10. (T-1) 5.3.2. TAF Processes and Procedures. Units producing a TAF will: 5.3.2.1. Employ risk management practices when using a model (e.g., Global Air-Land Weather Exploitation Model (GALWEM)) based automated aerodrome forecasts as a tool to create first-look TAF products. (T-1) First-look TAFs issued without forecaster adjustments are required to meet specification criteria requirements and be amended IAW Table 5.1. (T-1) 5.3.2.2. Develop a TAF production cycle for locations and coordinate TAF issue times with supported units. (T-1) 5.3.2.3. Issue forecasts valid for a 30-hour period. (T-1) DAFMAN15-129 7 SEPTEMBER 2023 35 5.3.2.4. Issue TAFs during controlled airfield hours, at a minimum of every 8 hours and within 15 minutes of the issue times that were previously coordinated with supported units. (T-1) 5.3.2.5. Disseminate all TAF-coded forecast products (including amendments) via weather enterprise operational production applications. (T-1) 5.3.2.6. Disseminate TAF-coded forecasts for limited operation airfields IAW local unit requirements. (T-3) 5.3.2.7. Coordinate with base operations leaders to issue NOTAMs for temporary changes to TAF services at an airfield (e.g., switching to limited duty TAF due to personnel shortages). (T-1) 5.3.2.8. Specify the onset, duration, and intensity for the standard criteria in Table 5.1 throughout the valid period of the forecast. During airfield-controlled hours, amend TAFs when conditions do not match specified conditions within Table 5.1. (T-1) 5.3.2.9. Specify and amend ceiling and visibility categories for Army or Air Force flight planning criteria throughout the valid period of the forecast. (T-2) Use the lower of the two conditions to determine the ceiling and visibility amendment category. (T-2) 5.3.2.9.1. Use ceiling and visibility specification criteria in Table 5.2 for TAF-coded forecasts issued for Army airfields. (T-2) 5.3.2.9.2. Use ceiling and visibility specification criteria in Table 5.3 for TAF-coded forecasts issued for Air Force operating locations. (T-2) 5.3.2.10. Establish TAF trend data from standard display systems (e.g., Airfield Sensor Displays) to determine prevailing conditions. (T-1) Prevailing conditions are those that persist for at least 30 consecutive minutes. Conditions occurring once during a specified time-period for less than 30 consecutive minutes or occurring for an aggregate total of less than 30 minutes of every hour are temporary. During periods of rapidly changing ceilings or visibilities crossing multiple categories, consider conditions occurring for the greatest aggregate total during the full hour the predominant condition for that hour. 5.3.2.11. Coordinate and document unit back up TAF production and dissemination procedures in the Continuity of Operations (COOP)/ Primary, Alternate, Contingency, and Emergency (PACE) plans. (T-2) Establish plans to provide temporary assumption of METWATCH, to include TAF issue/amend authorities in the enterprise production applications during transition to or from an Alternate Operating Location (AOL) or for other unforeseen/emergency circumstance that precludes the local weather unit from performing their assigned duties. (T-2) Non-COOP transfers of TAF responsibilities will require coordination through MAJCOMs and/or component functionals, as appropriate. (T-2) 36 DAFMAN15-129 7 SEPTEMBER 2023 Table 5.1. Standard Specification and Amendment Criteria. Rule Phenomena Criteria Source Notes, Examples or Applications IF: Forecast winds 23018G25KT THEN: Amend if predominant Wind Speed: The difference winds equal or between the predominant wind exceed 28 knots, speed and the forecast wind or if observed speed is > 10 knots gusts equal or Wind Gusts: The difference exceed 35 knots between observed gusts and 1 Surface Winds Amend if the forecast is > 10 knots predominant winds Wind Direction: A change > are 8 knots or less 30 degrees when the or gusts do not predominant wind speed or meet 15 knots gusts are expected to be 15 Amend for knots or greater prevailing wind directions outside of the arc extending from 200 through 260 degrees Icing, not associated with thunderstor The beginning or ending of AFMAN 11- ms, from icing first meets, exceeds, or 202 Vol. 3, 2 the surface decreases to less than moderate AR 95-1, and to 10,000ft (or greater) thresholds and was AFH11-203v 1 Above not specified in the forecast Ground Level (AGL) DAFMAN15-129 7 SEPTEMBER 2023 37 The beginning or ending of Turbulence AFMAN 11- turbulence first meets, exceeds, (for 202 Vol. 3, or decreases below moderate weather AR 95-1, and or greater thresholds and was category II AFH11-203v 1 not specified in the forecast aircraft), not 3 associated with thunderstor ms from the surface to 10,000 ft AGL Occur, or are expected to occur Note: Watches are during the forecast period, but exempt from this were not specified in the requirement. forecast Forecasters may specify watch Specified in the forecast but are 4 criteria in the TAF Weather no longer expected to occur Warning when, in their during the forecast period Criteria judgment, the specific nature of the threat dictates Altimeter setting meets or AFMAN 11- exceeds 31.00 INS and was not 202 Vol. 3 specified in the forecast Altimeter setting, if above, drops below 31.00 INS and was not specified during the forecast period 5 Altimeter setting drops below 28.00 INS and was not specified in the forecast Altimeter Setting Altimeter setting, if below 28.00 INS, increases above 28.00 INS and was not specified in the forecast 38 DAFMAN15-129 7 SEPTEMBER 2023 Occur, or are expected to occur Note: Advisories during the forecast period, but issued for an area Forecast were not specified in the not including the Weather forecast terminal 6 aerodrome forecast Advisory Specified in the forecast but are Criteria area are exempt no longer expected to occur from this policy during the forecast period Incorrect forecast start or end AFMAN 11- 7 Thunderstorms time 202 Vol. 3 and AR95-1 Forecast conditions specified AFMAN 11- as temporary become 202 Vol. 3 and predominant conditions AR95-1 Specification of Forecast conditions specified 8 Temporary as temporary do not occur Conditions during the hour as forecast Forecast conditions specified as temporary are no longer expected to occur Forecast change conditions occur before the beginning of the specified period of change Changes to and are expected to persist Predominant Forecast change conditions 9 Conditions do not occur within 30 (BECMG or minutes after the specified FM group) time Forecast change conditions are no longer expected to occur Forecast conditions are not considered representative of existing or forecast conditions Representative and amending the forecast 10 improves safety, flight Conditions planning, operations efficiency, or assistance to in-flight aircraft DAFMAN15-129 7 SEPTEMBER 2023 39 Table 5.2. Army Airfield Ceiling and Visibility Specification and Amendment Criteria. Rule Category Ceiling Visibility Source Visibility GTE Aircrew must file for an alternate if Greater Than or Equal to 4800 meters (M) 1 D conditions are less (GTE) 1500ft (3 statute miles than 1500M/3SM [SM]) IAW AR 95-1 Airfield weather Visibility LT 4800M conditions must Less Than (LT) 1500ft (3SM) but equal or exceed but GTE lowest GTE lowest these criteria to 2 C published landing published landing qualify as an minimum plus 400ft minimum plus alternate when 1600M/1SM flight filing IAW AR 95-1 Airfield does not LT lowest published qualify as an LT lowest published landing minimum alternate for flight landing minimum plus 1SM (1600M) planning but is 3 B plus 400ft but GTE but still suitable for lowest published GTE lowest arrival providing a landing minimum published airfield suitable alternate landing minimum is available IAW AR 95-1 Airfield is not a LT lowest published LT lowest published suitable 4 A airfield landing airfield landing destination IAW minimum minimum AR 95-1 40 DAFMAN15-129 7 SEPTEMBER 2023 Note 1. Forecasts specify when conditions decrease to less than, or if below, increase to equal or exceed the categories in the table. Note 2. Forecast category is determined by the lower of the ceiling or visibility value. Note 3. Use predominant conditions to determine forecast category (i.e., not tempo or varying). Note 4. For locations Outside the Continental United States (OCONUS), 5000M and 1500M may be substituted for 4800M and 1600M respectively, based on the host-nation practice. Substitutions should be documented in local support plans and operating procedures. DAFMAN15-129 7 SEPTEMBER 2023 41 Table 5.3. DAF Airfield Ceiling and Visibility Specification and Amendment Criteria. Rule Category Ceiling Visibility Source: Aircrew must file for an alternate if forecast conditions are less 1 E GTE 2000ft GTE 4800M (3SM) than 2000/3 IAW AFMAN 11-202 Vol 3 LT 4800M (3SM) but Airfield qualifies as LT 2000ft but GTE GTE 3200M an alternate IAW 2 D 1000ft AFMAN 11-202 Vol (2SM) or lowest published 3 visibility minima, whichever is greater LT 4800M (3SM) LT 1000ft and GTE but Airfield qualifies as lowest published GTE 3200M an alternate IAW 3 C landing minimum AFMAN 11-202 Vol plus 500ft (2SM) or lowest published 3 visibility minima, whichever is greater Airfield does not qualify as an LT the lowest LT 3200M (2SM) alternate for flight published landing planning but is still minimum plus 500 but GTE the lowest 4 B suitable for arrival ft and GTE the published airfield landing provided a suitable lowest published minimum alternate is available landing minimum IAW AFMAN 11- 202 Vol 3 Airfield is not a LT the lowest LT the lowest published suitable destination 5 A published airfield airfield landing minimum IAW AFMAN 11- landing minimum 202 Vol 3 42 DAFMAN15-129 7 SEPTEMBER 2023 Note 1. Forecasts specify when conditions decrease to less than, or if below, increase to equal or exceed the categories in the table. Note 2. Forecast category is determined by the lower ceiling or visibility value. Note 3. Use prevailing surface visibility to determine forecast category. Note 4. For OCONUS locations, 5000M and 3000M may be substituted for 4800M and 3200M respectively, based on the host-nation practice. Note 5. For DAF operations, Category A minima may be replaced with pilot weather categories in MAJCOM supplements to AFMAN 11-202v3. Note 6. Air Force rotary wing criteria may be substituted when rotary wing aircraft are the primary aircraft assigned at the TAF location as stated in AFMAN 11-202v3. 5.4. RP/WWAs. The weather organizations listed below perform local area METWATCH and produce, disseminate, amend, and verify WWAs to inform key decision makers and personnel of potential and observed weather conditions that require protective actions. 5.4.1. WF/Dets will: 5.4.1.1. Issue all required WWAs for their host installation/aerodrome complex and supported parent/tenant unit missions and resources (See Table 5.4 for exceptions). (T-2) WWA support for ANG/ARNG dual-use military/civilian airfields will be documented IAW Chapter 3. (T-2) 5.4.1.1.1. For limited-duty locations, WF/Dets will attempt to develop or arrange alternative solutions (e.g., Cooperative Weather Watch, Commercial or Government Off-the Shelf solutions) to perform local area METWATCH and issue host installation/aerodrome WWAs outside of regular duty hours. (T-2) 5.4.1.1.1.1. WF/Dets will coordinate with their applicable component SWO or MAJCOM functional to attempt to resolve the shortfall if no practical alternative local solution(s) exist. (T-2) 5.4.1.1.1.2. If component SWO or MAJCOM functional cannot provide a solution, WF/Det leadership should submit a support request IAW Chapter 10 to establish RP recall/backup procedures. WF/Dets will document their recall procedures in their WSD and/or IDP. (T-2) 5.4.1.1.2. Determine and document host/parent unit requirements for NOAA flash flood, river/coastal flood, and fire warnings IAW paragraph 5.6.2. Coordinate and document requirements and dissemination processes with the 557 WW in local support agreements and the IDP. (T-1) 5.4.1.2. 557 WW will: 5.4.1.2.1. Produce, issue, amend and verify WWAs for DAF or Army locations (e.g., airfields, high use ranges, drop zones, missile fields) where there are no weather personnel are assigned to provide RP/WWA services. (T-2) DAFMAN15-129 7 SEPTEMBER 2023 43 5.4.1.2.2. Produce, issue, amend and verify forecast WWAs for ANG-managed locations staffed by U.S.C. Title 5 and contracted personnel that only perform “eyes forward” and observed WWA functions. (T-2) 5.4.1.2.3. Produce, disseminate, and amend WWAs for adversary point, aerodrome complexes and military operating areas using latitude/longitude, International Civil Aviation Organization (ICAO), or basic encyclopedia (BE) designations as requested. (T-2) 5.4.1.2.4. Produce, issue, amend and verify WWAs for emergency, contingency, or forward deployed operating locations as coordinated and validated in OPLANs, EXPLANs, and Defense Security Cooperation Agency Plans as requested IAW Chapter 10. (T-2) 5.4.1.2.5. Produce, issue, amend and verify WWAs outside of established hours of operations for installations manned exclusively by DAF and Army civilian or contract weather support and for foreign bases where neither the DAF or Army are designated as the SAA, but DAF or Army assets are operating or located. (T-1) 5.4.1.2.6. Establish and employ procedures to recall standby WF/Det forecaster(s), upon request, to provide operational or RP weather support at limited-duty locations. (T-2) 5.4.1.2.7. Collect and display NOAA issued fire and flood WWA products for U.S. locations and territories using enterprise program of record capabilities. (T-1) 5.4.1.2.8. Coordinate with installation/garrison emergency management centers to relay available and trusted flood, fire, and tsunami warnings using enterprise data services for locations requiring RP without weather personnel assigned to perform RP support. (T-1) Note: For joint installations where the DAF has the lead for WWAs, emergency management personnel may be from another service. 5.4.1.3. 23 SOWS will produce, disseminate, amend, and verify WWAs for deployed AFSOF/ARSOF operations without organic weather personnel. (T-1) 5.4.1.4. When sufficient time does not exist to communicate a change in weather, weather units not responsible for WWAs may, under PACE (primary, alternate, contingency, and emergency) conditions, without prior coordination, facilitate RP actions. When time permits, weather units will forward pertinent information to the responsible unit and transfer responsibility for the WWA. (T-1) 44 DAFMAN15-129 7 SEPTEMBER 2023 Table 5.4. Dual-use Civilian/Military Airfield, Observation, and WWA Responsibilities. Airfield Airfield Observed Forecast Location Observation Forecast WWA WWA Albuquerque International Sunport FAA NWS OWS OWS Airport/Kirtland AFB WF/Det Charleston IAP/JB (during duty FAA NWS OWS Charleston AFB hours; OWS when closed) Colorado Springs Municipal FAA NWS WF/Det WF/Det Airport/Peterson AFB Eglin AFB/Destin-Ft Walton General WF/Det WF/Det WF/Det WF/Det Airport Killeen-Ft Hood WF/Det WF/Det WF/Det WF/Det Regional Airport Joint Base Pearl Harbor- NWS NWS WF/Det WF/Det Hickam/Honolulu IAP Rickenbacker IAP/Rickenbacker FAA NWS OWS OWS JRB Scott AFB – Mid America Regional WF/Det WF/Det WF/Det WF/Det Airport Wichita Falls Regional WF/Det WF/Det WF/Det WF/Det Airport/Sheppard AFB 5.4.2. RP/WWA Processes and Procedures. Units providing RP will: 5.4.2.1. Coordinate annually with each supported unit and maintain documented WWA thresholds, desired lead time (DLT), and mission impacts (this may be accomplished in concert with review of WSD, or equivalent). (T-3) Units will use the default minimum DAFMAN15-129 7 SEPTEMBER 2023 45 desired lead-times in Table 5.5 if the supported organization does not specify a minimum DLT. (T-1) 5.4.2.2. Ensure WWAs maintain horizontal consistency with TAF, and other forecast products. (T-1) Watches are not required to be horizontally consistent with the TAF, except for lightning watches. (T-1) 5.4.2.3. Notify the 557 WW and/or LWU if their products are inconsistent with locally issued WWAs to maintain horizontal consistency throughout all WPs. (T-1) 5.4.2.4. Maximize the use of watches within their affected area of operations until conditions warrant issuing a warning to meet desired lead-time requirements for supported organizations. (T-1) 5.4.2.5. Issue WWAs in a standard format and numbering scheme through the AFWWS enterprise application (primary) or local dissemination systems. (T-1) Note: Units may enable automated functions to issue observed advisories if fixed base weather observation systems are fully functional. 5.4.2.6. Issue WWAs in Coordinated Universal Time (UTC) and/or Local Time. (T-3) Note: Local time is changed for Daylight Saving and does not always correspond to Local Standard Time. 5.4.2.7. Issue WWAs with a separate valid time for each criterion when warranted. (T-1) The beginning valid time for observed WWAs is when the criteria are first observed. An ending valid time is not used for observed WWAs. In place of and ending valid time, the following statement is used: "Valid until further notice." (T-1) 5.4.2.8. Specifically state the area affected when issuing WWAs. (T-1) Watches may be issued for an area larger than the corresponding warning (e.g., Watch for high winds for Random AFB and surrounding local flying area. Warning for high winds for Random AFB [applicable to the aerodrome]). Note: Warnings normally affect an area no larger than a 5NM radius of the airfield. WWAs for Military Operating Areas (e.g., training areas, ranges, and missile complexes) may cover larger areas. Document deviations in supported agency data pages or applicable plans or instructions. (T-2) 5.4.2.9. Include the maximum expected hail size, rain/snow accumulation, or wind speed as applicable in warnings and advisories. (T-1) Include additional criteria IAW local support agreements (IDP, WSD, etc.). (T-1) 5.4.2.10. Issue watches for phenomena other than lightning a minimum of one hour prior to issuing a warning for the same phenomena. Issue lightning watches at least 30 minutes prior to issuing a lightning warning or IAW the desired lead time of the supported unit/installation, whichever is longer. 5.4.2.11. Issue lightning watch and the observed lightning warning as stand-alone criteria as they do not supersede WWAs previously issued for other criteria. 5.4.2.12. Issue warnings, as required, regardless of whether a watch had previously been issued. Note: A watch is not a substitute for a warning. Do not issue a forecast WWA for a single, un-forecast event that is not expected to persist or reoccur. 46 DAFMAN15-129 7 SEPTEMBER 2023 5.4.2.13. Issue a completely new warning or advisory with a new number when a WWA no longer adequately describes the phenomenon's occurrence. WWAs may be extended provided the extension is issued prior to the expiration of the original notice. 5.4.2.14. Issue only one weather forecast warning or advisory for the same criteria when in effect at any given time. (T-1) This does not prohibit the use of a watch, a forecast warning, and an observed advisory being valid at the same time for different thresholds of the same criteria (e.g., A watch for GTE 50kts, a warning for 35-49kts, and an observed advisory for GTE 25kts all valid at the same time). 5.4.2.15. Clearly state how amended, extended, or cancelled WWAs affects any other issued notices for the same criteria (e.g., “This upgrades warning XX-XXX” or “This extends advisory XX- XXX” or when canceling “Watch XX-XXX for lightning within 5NM remains in effect” etc.). 5.4.2.16. Cancel WWAs when conditions are no longer occurring and are not expected to reoccur within the DLT of the WWA. (T-1) Note: Cancel observed WWAs at the discretion of the responsible agency. This is typically 15 minutes after the last occurrence of the criteria is no longer forecast to take place. 5.4.2.17. Cancel lightning watches only when the potential for lightning within the next 30 minutes is no longer forecast. Do not cancel if there is potential for another thunderstorm withing 30 minutes. (T-1) 5.4.2.18. Upgrade WWAs when adding phenomena or crossing to a higher threshold. Downgrade WWAs when removing a phenomenon or crossing to a lower threshold. Use the default wording for upgrading/downgrading in the AFWWS enterprise application. (T-1) 5.4.2.19. Notify ATC and the C2 authority responsible for the Installation Notification and Warning System (per AFI 10-2501 or AR 525-27) along with other supported units when the WWA notification system is inoperable. (T-1) Utilize an DAF Form 3807, Watch/Warning Notification and Verification, or on an DAF Form 3806, Weather Watch Advisory Log, as applicable, until the WWA notification capability is restored. (T-2). Instructions for completing the DAF Form 3807 and 3806 are found in Attachment 4 and Attachment 5 respectively. 5.4.2.20. If responsibility for WWAs is transferred to another unit, that unit is responsible for conducting verification and entering data into the AFW enterprise dissemination system until the service disruption is over and WWA responsibility is transferred back to the original unit. (T-1) 5.4.2.21. Document sound meteorological reasoning used in determining the need for all forecast WWAs in the appropriate spaces provided in AFW enterprise dissemination system. (T-1) 5.4.3. WWA Verification. WWAs fall into one of five verification categories (see Figure 5.1.). DAFMAN15-129 7 SEPTEMBER 2023 47 Figure 5.1. Weather Warning and Advisory Verification Process. 5.4.3.1. Verify all issued WWAs based on the desired lead-time (DLT) and area specified in the criteria. For example, issue and verify a warning for lightning within 5NM of an airfield based on lightning strikes or radar returns within the verification area, or when reported as occurring on station in a surface observation. Verify a forecast advisory for lightning within 25NM based on lightning strikes or radar returns within the verification area, or when reported as occurring (within 25NM) in a surface observation. When performing WWA verification, units will: 5.4.3.1.1. Omit reporting locations within the verification radius that are not representative of the location receiving WWA products and document these sites in forecast reference material or SOPs. (T-2) 48 DAFMAN15-129 7 SEPTEMBER 2023 5.4.3.1.2. Employ all data available from representative sources of sensed or observed data within the verification area to objectively verify warnings and advisories. (T-2) Consider data sensed from radars, mesonets, environmental monitoring systems, tactical ATC systems, forward armament and refueling points, or other sensing systems objective data for evaluating and verifying WWA products. Use unofficial reports from credible sources (e.g., Storm Prediction Center Storm Reports, NWS Citizen Weather Observation Program (CWOP) and Community Collaborative Rain, Hail and Snow Network (CoCoRaHS), off-duty AFW personnel, storm spotter reports, etc.) within the verification area of the warned location to verify warnings and advisories when unit leadership determines the reports are credible based on corroborating objective weather data or subjective analysis of relevant weather data (e.g., a weather Airman lives within a verification area and notifies the unit performing verification that they observed 3/4” hail; unit leadership determines whether this report is credible and can be used for verification). 5.4.3.1.3. When objective verification is not possible, inadequate, or misrepresentative, use subjective analysis of available data to determine if an event occurred. (T-2) In situations where units use subjective verification, unit leadership will take responsibility for a missed occurrence of the weather threat if these phenomena are reported with no WWAs in effect at that time. MAJCOM or component weather staffs serve as approval authority for subjective verification. (T-2) 5.4.3.1.4. Verify each phenomenon separately. (T-2) 5.4.3.1.5. Verify severe thunderstorm and moderate thunderstorm warnings upon first occurrence of either wind or hail threshold at the warned location. Occurrence of either of the specified criteria in severe thunderstorm and moderate thunderstorm warnings verifies these warnings; “bundle” the criteria for verification purposes. 5.4.3.1.6. Verify a lightning watch as if it were a forecast WWA product with a 30- minute desired lead-time. Base the lead-time on the issued time of the watch subtracted from the time of first occurrence of the lightning within specification distance of the warned location. 5.4.3.1.7. Verify heavy precipitation warnings using measurements from the airfield observing system, radar precipitation measurements, other rain gauges, or storm reports in the verification radius for the warned location. (T-2) 5.4.3.1.8. Verify heavy rain warnings specifying an accumulation in a specified time period by using a summation of the one-hour precipitation measurements from the airfield observing system. (T-2) Collect the one-hour amounts reported by the airfield observing system commencing with the hour that the warning was issued and indicate on a weather warning verification tracker when the specified precipitation total was reached. (T-2) Continue to collect the one-hourly accumulations during the valid period of the warning and enter the total liquid precipitation received during the valid period of the warning into the verification database in the AFW enterprise dissemination system. (T-2) DAFMAN15-129 7 SEPTEMBER 2023 49 5.4.3.1.9. Use accumulated reports of 6-hourly, 12-hourly, or summary of the day during the valid period of the warning for verifying heavy rain warnings at locations where the unit does not have access to the hourly rain gauge data from an airfield observing system. (T-2) If necessary, estimate actual time of occurrence based on interpolations from the rate of accumulation in METAR or Synoptic reports. 5.4.3.1.10. May use radar generated precipitation total products to supplement direct measurements from a rain gauge and verify precipitation accumulation warnings. Evaluate radar-generated precipitation products for accuracy against reliable rain gauges (military or NWS sites) for at least one season to account and correct for high reflectivity phenomena such as hail or bright band contamination of the data. (T-2) 5.4.3.1.11. Verify heavy snow warnings using manually observed snowfall totals from Air Force, sister service, coalition partners, or host nation sources where the capability exists. (T-2) 5.4.3.1.12. In the absence of manual snowfall totals, the unit conducting verification of a heavy snow warning converts one-hour liquid precipitation measurements into hourly snow equivalent according to procedures in AFMAN 15-111. (T-2) Collect the one-hour amounts reported by the airfield observing system commencing with the hour that the warning was issued and indicate on a weather warning verification tracker when the specified snowfall total was reached. (T-2) Continue to collect the one-hourly accumulations during the valid period of the warning and enter the total snowfall and liquid precipitation received during the valid period of the warning into the verification database. (T-2) 5.4.3.1.12.1. Weather radar data is unreliable for determining snowfall and cannot be used to objectively verify heavy snow warnings. (T-2) Units may use radar reflectivity returns or NWS CWOP to subjectively evaluate heavy snowfall warnings to justify warnings that do not verify by other means. 5.4.3.1.12.2. Use accumulated reports of 6-hourly, 12-hourly, or summary of the day during the valid period of a heavy snow warning at locations where the unit does not have access to hourly data from an airfield observing system. (T-2) If necessary, estimate actual time of occurrence based on interpolations from the rate of accumulation in METAR or synoptic reports. Use the observation date/time group on METAR reports with snow increasing rapidly remarks (SNINCR s/tt) to verify heavy snow warnings when either value in the remark meets or exceeds the warning threshold. (T-2) 5.4.3.2. WWA Lead-time Com