Aviation Safety Program

Why the Safety Program Stands Apart

Naval aviation is high-consequence, high-velocity, high-cost work. The Naval Aviation Safety Management System exists because aviation mishaps kill aircrew, destroy aircraft, and end careers. The system is built on documented appointment, school-trained personnel, recurring climate assessment, and disciplined reporting.

The Aviation Commander's Mentorship Handbook captures the posture:

"I have never lost any sleep over grounding someone or removing an individual's wings. I have lost sleep for not doing it."

The safety program is the commander's tool for executing the posture before it costs aircrew or aircraft.

The Aviation Safety Officer (ASO)

OPNAVINST 3750.1B requires every Marine aviation squadron to appoint an Aviation Safety Officer in writing. The ASO is school-trained at the Naval Postgraduate School Aviation Safety Officer Course.

ASO appointment requirements

The ASO is not the SACO. The ASO is not the Marine Corps Safety Officer (under MCO 5100.29C) at the squadron level. The ASO is the aviation-specific safety lead with direct reporting to the CO.

Where the ASO appointment goes wrong

• ASO appointed without NPS course completion. Procedural defect.
• ASO appointed at too junior a level to influence aircrew or maintenance practices. Program degrades.
• ASO without direct CO access. Filters the safety information stream.
• ASO collaterally assigned a flight schedule equivalent to line aircrew. Loses time for safety program execution.
• ASO succession not planned. Course attendance for replacement not scheduled before departure of incumbent.

CO-level discipline on the ASO

The CO meets with the ASO weekly at minimum. The ASO has unfiltered access to brief safety concerns. The ASO presents at every Aviation Safety Awareness Council. The ASO's read on aircrew and maintenance culture is one of the highest-signal inputs the CO receives.

Aviation Safety Awareness Council (ASAC)

The ASAC is the recurring forum for safety program oversight at the squadron level. OPNAVINST 3750.1B requires it.

Standard composition

• CO (chair)
• XO
• ASO
• Operations Officer
• Maintenance Officer
• NATOPS Officer
• Quality Assurance Officer (QAO)
• Flight Surgeon if assigned
• Senior Maintenance Marines
• Aircrew representation by mission/platform

Standard agenda

1. Prior ASAC action items
2. Recent HAZREPs and trend review
3. Mishap investigation status
4. ORM updates on current operations
5. NATOPS evaluation status across aircrew
6. Maintenance trend review
7. Aircrew currency picture
8. Safety stand-down recommendations
9. MAWTS-1 inputs if applicable
10. Action items

Cadence

Monthly minimum per OPNAVINST 3750.1B. Higher cadence during sustained tempo or after a mishap.

MCAS Climate Survey

The Maintenance Climate Assessment Survey (MCAS) is the aviation-specific annual climate instrument. Per MCO 5100.29C Para 060402, the CO at O-5/O-6 level completes the survey annually.

What MCAS measures

• Squadron maintenance culture
• Maintenance Marine perception of safety reporting climate
• Communication between aircrew and maintenance
• Workload sustainability
• Tool and equipment readiness
• Supervisory culture

How it differs from Ground CAS

Ground CAS is generic to non-aviation Marine commands. MCAS is aviation-specific and probes maintenance-aircrew dynamics. The Ground CAS does not substitute. Aviation commands run MCAS.

What the CO does with the results

• Review with ASO and Maintenance Officer
• Identify the top 3 trends
• Build a POA&M for response
• Annotate in FITREP per MARADMIN 468/23 pattern
• Coordinate with Wing Safety for cross-squadron context

Mishap Reporting

OPNAVINST 3750.1B defines the classes of mishap (Class A through Class E based on injury and aircraft damage). The CO's role is to ensure timely reporting and supportive investigation.

Class structure (summary, verify against OPNAVINST 3750.1B current text)

• Class A: fatality, permanent total disability, or aircraft destroyed
• Class B: permanent partial disability or significant aircraft damage
• Class C: lost workday case or moderate aircraft damage
• Class D: minor injury or damage requiring report
• Class E: events not meeting above thresholds but requiring reporting

The threshold dollar figures and disability classifications change. Verify against the current OPNAVINST 3750.1B before any mishap response.

Initial response by the CO

When a mishap occurs:

1. Ensure aircrew and personnel safety. Medical response is first.
2. Notify Wing Safety and next higher commander immediately.
3. Secure the mishap site and aircraft.
4. Coordinate with Aircraft Mishap Board (AMB) on convening.
5. Notify family members appropriately if Class A.
6. Pause flight operations as ASO recommends.

Investigation process

• AMB convenes per OPNAVINST 3750.1B.
• Mishap report submitted within required timeline.
• Privileged safety information stays within the safety chain.
• Adverse personnel actions, if appropriate, proceed through a separate non-safety chain.

The "privileged" status of safety information is critical. Information gathered for safety investigation cannot be used in punitive proceedings. Comingling the two chains taints both.

HAZREP (Hazard Report)

HAZREPs are the bottom-up safety signal. Any Marine is authorized to submit. The CO ensures the system encourages submission and tracks corrective action.

What goes in a HAZREP

• The hazard observed
• The contributing factors
• The recommended corrective action
• The submitter's contact (or anonymous if local procedure allows)

CO's discipline on HAZREPs

• Establish low-friction submission process
• Direct ASO to track every HAZREP to closure
• Review HAZREP trends at ASAC
• Publish closed HAZREP outcomes (without punishing submitters)
• Train aircrew and maintainers on the rule: HAZREP submission is rewarded, not punished

A squadron where HAZREP submissions decline over time often signals climate concern, not absence of hazards. MCAS climate survey results sometimes correlate.

Operational Risk Management (ORM)

MCO 3500.27C governs ORM at the operational level. Aviation commanders integrate ORM into:

• Flight scheduling
• Mission planning
• Maintenance task assignment
• Training event execution
• Operational deployment cycles

The CO does not write each ORM analysis. The CO sets the standard: ORM is conducted, documented, and reviewed for every mission and training event.

ORM at the squadron level

Common Failures in the Aviation Safety Program

1. ASO appointed before NPS course completion. Procedural defect.
2. MCAS not run annually. Direct violation of MCO 5100.29C.
3. HAZREP submissions punished informally. System degrades. Aircrew and maintainers stop reporting.
4. Safety chain and disciplinary chain commingled. Tainted both proceedings.
5. ASO without direct access to CO. Filtered safety signal.
6. ASAC running monthly but with no documented action items. Compliance theater.
7. Mishap response without immediate next-higher and Wing Safety notification. Procedural cascade fails.
8. ORM as paper exercise. Not integrated into actual planning.
9. Use of safety stand-down as punishment. Damages the program's purpose.
10. Failure to track HAZREP corrective actions to closure. Same hazard repeats.

How This Interacts With the Force Preservation Council

The aviation safety program and the Force Preservation Council are separate but related.

A Marine flagged in CIRRAS for personal stressors might also appear on the ASO's watch list for aircrew currency or attitude. The two forums share leadership but not membership composition. Cross-coordination is the CO's job.

Related Pages

• Aviation Commander Overlay (this topic, order 1) - the topic index
• Aviation Pre-CoC Requirements (this topic, order 2) - including ASO succession planning at turnover
• Aviation Readiness and Training (this topic, order 4) - T&R, NATOPS, FRS interaction with safety program
• FPC Overview (Force Preservation topic) - the parallel forum
• Suicide Attempt and Mental Health Crisis Response (Incident Playbooks) - response when an aircrew is affected