UNITED STATES MARINE CORPS AVIATION SAFETY AWARENESS PROGRAM
Date Signed: 3/29/2019 | MARADMINS Number: 202/19
MARADMINS : 202/19

R 281900Z MAR 19
MARADMIN 202/19
MSGID/GENADMIN/CMC WASHINGTON DC AVN APP//
SUBJ/UNITED STATES MARINE CORPS AVIATION SAFETY AWARENESS PROGRAM//
REF/A/MSGID: DOC/MCO 3710.8/YMD: 20110930//
REF/B/MSGID: DOC/OPNAVINST 3710.7V/YMD: 20161122//
REF/C/MSGID: DOC/CNAF M-3710.7/YMD: 20160505//
REF/D/MSGID: DOC/OPNAVINST 3750.6S/YMD: 20140513//
AMPN/REF A IS UNITED STATES MARINE CORPS NAVAL AIR TRAINING AND OPERATING PROCEDURES STANDARDIZATION (NATOPS) PROGRAM.  REF B IS NAVAL AIR TRAINING AND OPERATING PROCEDURES STANDARDIZATION PROGRAM.  REF C IS NATOPS GENERAL FLIGHT AND OPERATING INSTRUCTIONS MANUAL.  REF D IS NAVAL AVIATION SAFETY MANAGEMENT SYSTEM ORDER.//
POCs/C. WALKER/LTCOL/ CURTIS.L.WALKER1@USMC.MIL AND T.MURPHY/CDR/THOMAS.P.MURPHY@USMC.MIL UNIT: COMMANDANT OF THE MARINE CORPS (SAFETY DIVISION)/-/TEL: DSN 664-4384 /TEL: COMM(703)604-4384//
GENTEXT/REMARKS/1. The purpose of this MARADMIN is to provide direction for the implementation of the United States Marine Corps Aviation Safety Awareness Program (ASAP).  ASAP is a self-evaluation and improvement program used to prevent aviation mishaps and improve agency safety processes and procedures to maintain and/or increase readiness.  The goal of ASAP is to provide squadron commanders direct insight into possible safety issues within their unit so that these issues can be addressed at the lowest level.  Participation in ASAP is required by reference (c), NATOPS General Flight and Operating Instructions Manual, paragraph 3.15.
1.a. Procedures will ensure proper control and use of the de-identified operational and human performance data entered by Marine Corps personnel and contractors into ASAP.
1.b. ASAP data shall not be used as evidence to support punitive or administrative action.  All documents and electronic files generated under ASAP must be labeled, “For Official Use Only, Freedom of Information Act Exempt.”
2. This MARADMIN provides direction for conducting administrative and operational functions necessary to sustain ASAP.
3. Background.  In 2003, the Secretary of Defense directed the Department of Defense to reduce the number of mishaps and accident rates by at least 50% in order to produce an increase in operational readiness and decrease the costs associated with the loss of life and equipment.  The Secretary of Defense established the Defense Safety Oversight Council and directed a review of accident and incident trends, ongoing safety initiatives, and private sector and other governmental agency best practices in order to make recommendations to the Secretary of Defense for safety improvement policies, programs, and investments.  As a result of the Secretary of Defense’s guidance, the U.S. Navy used the Federal Aviation Administration’s Aviation Safety Action Program as a model to develop its own ASAP in 2006.  Most recently on 5 May 2016 in CNAF M-3710.7 “NATOPS General Flight and Operating Instructions Manual,” the Commander Naval Air Forces directed that an aviation safety awareness program be employed to accomplish the following tasks:
3.a. Identify errors, potential precursors to mishaps, and improve operational efficiency.
3.b. Identify and proactively address unfavorable trends pertinent to aircrew training, aircraft maintenance, and flight and ground operations using human factors data and error reporting.
3.c. Validate existing operating and maintenance procedures.
3.d. Identify required changes to procedures based on metrics using aggregate data.
3.e. Establish leading indicators of human factors that may lead to mishaps and/or diminish readiness.
4. As a result of a successful beta test across 2d Marine Aircraft Wing (MAW) from October 2018 to February 2019, Commandant of the Marine Corps (Safety Division) is introducing ASAP throughout all Marine Aviation to initiate alignment with reference (d), Naval Aviation Safety Management System.  The technical capabilities of ASAP software facilitates reporting and analyzing hazards as directed by reference (d), paragraphs 110b and 111.  ASAP should be used as a tool to effectively execute the goals of the Naval Aviation Safety Management System and should not be viewed as a separate program.  Use of ASAP for punitive measures is prohibited – Fostering and maintaining a non-retributive environment that focuses on eliminating hazards via a just culture is essential to a successful ASAP program. 
5. ASAP Program Implementation.  ASAP Officer roles will be established at the squadron level, and ASAP Reviewer roles will be established at the Marine Aircraft Group (MAG), MAW, MARFOR, and HQMC levels.  The ASAP User Manual can be found under “User Manual” at the following website:  https:(slash)(slash)asap-usmc.com.
6. Program Controls.  By design, the ASAP process contains specific controls to ensure that critical, time-sensitive, and systemic issues do not escape detection.
6.a. The squadron is the primary focus for ASAP data collection and initial review; however, all personnel who operate on and around airfields are strongly encouraged to participate.  The squadron Aviation Safety Officer (ASO) (or designated unit ASAP Officer) should be the first ASAP administrator to detect critical and time-sensitive issues; the MAG ASO (or designated MAG ASAP reviewer) provides redundancy for detection of MAG-wide trends.
6.b. Trending is generally associated with, but not limited to, the viewing of larger volumes of aggregated data and is primarily accomplished at the MAW and MARFOR levels.
7. Program Process Measurement and Controls.  Process measurements are defined metrics to ensure task accomplishment by assigned personnel.  Controls ensure continuity of ASAP execution.
7.a. One member of each flight event shall submit an ASAP report; the Division Lead, Section Lead, Pilot in Command, or Mission Commander is responsible for meeting this requirement.  For cross country or multiple leg flights, one report per day is the minimum requirement.  Additionally, one maintenance member from each maintenance shift shall submit an ASAP report; the senior member of Maintenance Control is responsible for meeting this requirement.
7.b. An ASAP report can be designated as either an “Event” report or a “No Event” report.
7.b.1. “Event” reports provide details regarding a specific hazard to operations that was observed before, during, or after the flight event.  “Event” reports also collect data related to command climate and other specific questions as directed by squadron CO, MAG, MAW, MARFOR, or HQMC.
7.b.2 “No Event” reports are submitted when no significant hazards were observed before, during, or after the flight event.  “No Event” reports collect data related to command climate and other specific questions as directed by squadron CO, MAG, MAW, MARFOR, or HQMC.
7.c. Other flight event and maintenance members are encouraged to submit an ASAP report if they observe additional hazards to operations; there is no limit on how many reports an individual, flight event, or maintenance shift may submit.
7.d. ASAP Officers are required to review their unit’s “Event” reports weekly.  Once the report has been reviewed, other ASAP Reviewers external to the unit may then see the event details within the report.  However, command climate data will not be visible outside the reporting squadron.
8. Definitions
8.a. ASAP Data:  Any data, regardless of format or form, collected for the specific purpose of supporting ASAP.
8.b. Privileged Material:  Information that is restricted to safety use only and is access restricted as defined in reference (d).
8.c. ASAP Reviewers:  Reviewers shall be Naval Aviators, Naval Flight Officers, senior Naval Aircrewman, senior Maintenance Personnel, or Government employees/contractors designated by CMC SD, respective MARFOR/MAW Commanding Generals, MAG Commanding Officers, or squadron Commanding Officers.  The intent is to select experienced aviation participants capable of administering ASAP in a continuous manner.
8.d. ASAP Tool:  The primary ASAP internet-based data collection and reporting system for identifying crew reported errors and analyzing hazards.
9. Release authorized by LtGen S. R. Rudder, Deputy Commandant for Aviation.//