Aircraft Maintenance Officer

You are the maintenance officer in training — the 2ndLt or 1stLt learning the flight line before the flight line trusts you with it. The Master Chief running your production control has forgotten more about the NAMP than you will know for three more years; your job is to learn fast, stay out of his way on the technical calls, and own the administrative and safety functions that are actually yours.

You arrive at your first fleet squadron — likely at MCAS Cherry Point, Beaufort, Miramar, Yuma, New River, or Iwakuni — with a fresh commission, The Basic School behind you, and a pipeline training course that gave you a conceptual framework for naval aviation maintenance. Your daily work is production control oversight, parts and man-hour tracking in NALCOMIS (Naval Aviation Logistics Command Management Information System), pre-flight and post-flight inspection coordination with the line division, and learning the specific aircraft systems (AV-8B, F/A-18, MV-22, CH-53, AH-1Z, UH-1Y) well enough to have a credible conversation with the mechanics doing the work. You own the aircraft discrepancy book (ADB) review process, you verify that maintenance documentation is completed correctly under COMNAVAIRFORINST 4790.2 (the NAMP), and you brief the squadron's maintenance officer on the daily readiness picture. The aircraft do not lie — if your documentation is wrong or your availability numbers are inflated, the CO finds out when the plane cannot fly.

• 01Navigate NALCOMIS OMA (Organizational Maintenance Activity) to track work orders, aircraft discrepancy book entries, and man-hour expenditure — the production control chief will not accept vague answers from the readiness brief.
• 02Read and correctly apply COMNAVAIRFORINST 4790.2 (NAMP) chapters governing maintenance documentation, deferred discrepancies, ground safety, and the CDI/QAR inspection authority chain.
• 03Brief the daily maintenance officer's call with accurate aircraft availability, up/down status, and projected recovery timelines — the operations officer makes the flight schedule from your numbers.
• 04Identify a critical TNMCS (Total Not Mission Capable due to Supply) vs. NMCM (Not Mission Capable due to Maintenance) distinction correctly in every ADB entry — getting it wrong distorts the readiness metric the wing commander sees.
• 05Conduct a maintenance foreign object damage (FOD) walk and flight-line safety check in accordance with OPNAVINST 3750.6 (Naval Aviation Safety Program) and the squadron SOP before every launch period.
• 06Write a factual, accurate ground mishap report or hazard report under the NAVAIR Safety Management System (SMS) when an incident occurs — the safety officer and the wing safety shop read these before anyone else.

• —COMNAVAIRFORINST 4790.2 — Naval Aviation Maintenance Program (NAMP): the governing document for every maintenance action, work order, discrepancy, CDI/QAR authority, and documentation requirement in a fleet squadron.
• —OPNAVINST 3750.6 — Naval Aviation Safety Program: mishap reporting, hazard reporting, and safety investigation procedures the maintenance officer is directly responsible for at the squadron level.
• —NAVAIRINST 13120.1 — NATOPS (Naval Air Training and Operating Procedures Standardization) Program: the NATOPS compliance framework the MOO is accountable for in the maintenance context.
• —MCO 3500.27 — Marine Aviation Training and Readiness (T&R) Program: the individual and collective training qualification framework the 6002 must track against for maintainers.
• —NAVMC 3500.15 — Aviation Ground Support T&R Manual: individual qualification standards for enlisted maintainers in your department.
• —NAVAIR 00-80T-114 — Aircraft Firefighting and Rescue: flight-line emergency procedures the maintenance officer must know before the first flight period.

• —Aviation Officer Indoctrination course and MOS-specific pipeline training complete — Naval Aviation Maintenance Officers School (Pensacola or follow-on pipeline) designates your 6002 MOS.
• —NATOPS Program Coordinator functions assigned and documented within the first 90 days of reporting — the wing NATOPS check is not optional.
• —PFT and CFT at 1st-Class per MCO 6100.13 — the flight-line is physical; your Marines watch whether the maintenance officer holds the same standard he briefs.
• —Aviation Safety Officer (ASO) collateral duty completion and Ground Safety certification within the first year — the NAMP places safety documentation responsibility directly on the maintenance officer.
• —NALCOMIS proficiency to production-control brief level within 60 days of reporting — if you cannot read the system, you cannot brief the commanding officer's readiness call accurately.

• —Signing off a deferred maintenance action that should have been non-deferred. Under the NAMP, the category of a deferral determines who is authorized to defer it — when a 2ndLt defers a grounding discrepancy without the maintenance officer's concurrence, the mishap investigation traces back to the signature.
• —Trusting a verbal readiness update over the NALCOMIS work order. Aircraft availability numbers that are verbally massaged before the brief are wrong numbers — and the CO flies the schedule based on your brief, not on what the mechanic thought he was going to fix.
• —Skipping the aircraft discrepancy book (ADB) review. Every entry in the ADB is a legal maintenance record and a safety document; a maintenance officer who does not review it daily does not know what his aircraft's actual status is.
• —Taking a TNMCS record and coding it NMCM to improve the readiness metric. Parts availability and maintenance man-hour coding directly affect the supply readiness indicators the Naval Aviation Enterprise tracks — and the QAR does not find the coding error; the wing maintenance officer does, during a formal inspection.
• —Treating the flight-line FOD walk as a ritual rather than a safety function. FOD ingestion into a turbine engine on your watch is a Class A mishap investigation with your name in the first paragraph.

The good 6002 lieutenant is the one the maintenance officer sends to brief the group maintenance officer without rewriting the brief first. His ADB is current, his NALCOMIS work orders close on time, and the CDI roster in his department has no expired authorizations. By month twelve the senior NCOs in production control are briefing him instead of around him — because he learned the system before he tried to correct it.

You are the Maintenance Officer (MOO) or the executive officer of a Marine aviation squadron's maintenance department — the billet the entire 6002 career is built around. Everything before was preparation; everything after is what the MOO tour makes possible or forecloses.

As the squadron Maintenance Officer (MOO) you are responsible for the maintenance, material condition, and airworthiness of the commanding officer's aircraft. You own the production control department, the quality assurance division, the supply interface, the NATOPS program, and the aviation safety management system (NASMS) at the squadron level. Your daily work is the morning maintenance officer's call — ADB review, aircraft availability brief, TNMCS and NMCM analysis, parts priorities — followed by the CO's readiness brief, supply coordination, CDI/QAR surveillance management, and every mishap or hazard report that lands in your in-box. You are the maintenance authority of record: every aircraft that launches does so because you certified its airworthiness and your signature or your designated CDI's signature is the paper trail. You write the FitReps on the maintenance chief, the QA officer, and the production control officer. The CO evaluates your tour by three metrics: aircraft availability rate, maintenance mishap rate, and the ability of the department to sustain tempo through the deployment cycle without breaking.

• 01Run the daily maintenance officer's call to a standard the CO and operations officer can brief the wing commander from — availability accurate, TNMCS/NMCM split correct, recovery timelines defensible, no surprises after the brief.
• 02Manage the CDI/QAR authorization roster under NAMP Chapter 10 — nominations current, letters of authorization signed, surveillance inspections documented, and authority suspended when the standard is not met.
• 03Brief the CO on the NATOPS compliance posture — currency of publications, checkflight status, NATOPS evaluator currency, deviations documented and dispositioned under the applicable NAVAIRINST.
• 04Coordinate with the supply officer and the AVDLR (Aviation Depot Level Repairable) system to reduce TNMCS aging — the wing maintenance officer tracks TNMCS days by tail number and by squadron.
• 05Manage the Naval Aviation Safety Management System (NASMS) at the squadron level — hazard reporting, mishap investigation support, safety culture metrics, and the monthly aviation safety action team (ASAT) brief to the CO.
• 06Write defensible FitReps on the maintenance chief, QA officer, production control officer, and senior NCOICs per MCO 1610.7 — the relative-value ranking you assign shapes the career trajectory of ten to fifteen people.

• —COMNAVAIRFORINST 4790.2 — NAMP: your operational bible from Chapter 1 through Chapter 10; as MOO you are accountable for every chapter, not just the ones that apply to the work centers.
• —OPNAVINST 3750.6 / MCO 3500.27 series — Naval Aviation Safety Program and Marine aviation T&R: the safety and training frameworks you own at the squadron level.
• —NAVAIRINST 13120.1 — NATOPS Program: as NATOPS Program Coordinator or MOO, you certify publication currency, checkflight compliance, and evaluator qualification for the entire squadron.
• —NAVSUP Publication P-485 — Naval Supply Procedures: the supply-side manual the 6002 MOO needs to read to fight effectively for parts through the naval aviation supply chain.
• —MCO 1610.7 — Performance Evaluation System: you write FitReps on multiple officers and senior SNCOs per cycle; the mechanics of relative-value ranking determine whose career advances.
• —OPNAVINST 4790.4 series — Aircraft Intermediate Maintenance Department (AIMD) instruction: the interface between your organizational-level maintenance and the IMA that supports you.

• —MOO billet completed — 18-24 months as the signing maintenance authority for a Marine aviation squadron is the Key Developmental (KD) billet the 6002 career is evaluated against.
• —Squadron aircraft availability rate at or above the MAG/wing standard for the aircraft type — the wing maintenance officer publishes the rate comparison monthly and the CO knows where his squadron stands.
• —Zero Class A maintenance mishaps attributable to negligent maintenance documentation or supervision failures during the tour — one Class A generates a JAG Manual investigation the commanding officer has to explain to the wing commander.
• —NASMS fully operational per OPNAVINST 3750.6 — hazard reports submitted on time, ASAT meetings documented, safety culture surveyable at any Wing Safety inspection.
• —Expeditionary Warfare School (EWS) or command-equivalent PME complete — the LtCol board reads PME completion for the 6002 the same way it reads it for any Marine officer.

• —Allowing the CO to brief the wing commander on availability numbers that were not verified against the ADB and NALCOMIS that morning. Inaccurate readiness data travels up the chain quickly; when the wing maintenance officer queries the tail number and finds a different status than the CO briefed, the call goes to the MOO.
• —Signing a NATOPS flight authorization for an aircraft with an open checkflight discrepancy. The NATOPS evaluator's authority and the MOO's signature are separate lanes — when a checkflight is late or an aircraft is flying with an unresolved NATOPS discrepancy, the mishap investigation finds both names.
• —Letting the CDI roster age. An expired CDI authorization letter means every work order that mechanic signed is technically uninspected; the QAR audit identifies the date the authorization lapsed and traces every aircraft release since.
• —Failing to separate TNMCS coding from NMCM to improve availability statistics. The AVDLR metrics and the naval aviation enterprise readiness data both pull from your NALCOMIS coding — artificially improving availability by miscoding parts waits delays gets corrected at the wing maintenance inspection, not locally.
• —Under-supervising the quality assurance division. The QAR surveillance inspection rate, the hazard report submission rate, and the CDI oversight documentation are QA responsibilities the MOO owns in signature — when the wing QA staff audits and finds systematic gaps, the MOO's name is on the finding.

The good MOO captain is the one the wing maintenance officer calls when a MAG-wide parts shortage needs a squadron-level advocate who understands the AVDLR pipeline, the NALCOMIS work order queue, and the supply officer's COSAL limitations well enough to build the case for priority re-routing. His squadron availability rate is above the wing average, his CDI roster is current, and the CO briefs the readiness call from the MOO's numbers without editing them. The LtCol board FitRep from the CO reads "top block; ready for major maintenance command" — and the maintenance community is small enough that the next assignment monitor already heard the same thing from the wing maintenance officer.

You are the major in the maintenance chain — the group or wing-level maintenance officer, the inspector, or the type wing maintenance desk officer who audits the same MOO billets you held three years ago. The aircraft availability picture you managed at the squadron level is now a data point in your weekly group brief.

As a Marine aviation major in the 6002 community you are working at Marine Aircraft Group (MAG) or Marine Wing (MAW) level — Group Maintenance Officer (GMO), wing maintenance staff, type wing technical desk, Naval Aviation Depot (NADEP) liaison, or a joint maintenance staff billet. Your production control days are behind you; your work now is policy, inspection, cross-squadron coordination, and resource allocation across multiple squadrons and multiple aircraft types. The GMO role is the most direct extension of the MOO: you manage the availability reporting for the entire MAG, you coordinate TNMCS resolution across squadrons with the same AVDLR pipeline constraints, you conduct assistance visits to squadrons whose NAMP compliance is slipping, and you brief the MAG commander on maintenance readiness. You also write the maintenance portions of the MAG inspection schedule and coordinate with the Naval Aviation Maintenance Program-level (NAVAIR) representatives who visit the command. FitRep cycles at this rank are smaller and the relative-value competition is tighter — the LtCol board reads the GMO FitRep from the MAG commander, not from a squadron CO, and the profile is visible to a much smaller rater pool.

• 01Build and brief the MAG-level maintenance readiness brief — multiple aircraft types, multiple TNMCS trends, AVDLR performance across squadrons, and a fleet-wide discrepancy trend analysis — to a standard the MAG commander can brief the wing commander from.
• 02Conduct a NAMP compliance assistance visit (CAV) to a squadron MOO — identify systemic documentation gaps, CDI roster issues, or quality assurance program deficiencies and write a findings report the squadron can act on without a formal inspection finding.
• 03Coordinate parts sharing and AVDLR cannibalization authorization across MAG squadrons to reduce TNMCS aging — the supply officer and the type wing desk both have equities and both need a maintenance officer who understands the technical and logistical constraints simultaneously.
• 04Interface with NAVAIR logistics representatives and the relevant Aircraft Controlling Custodian (ACC) to escalate TNMCS situations requiring depot-level intervention — the MAG maintenance officer is the bridge between the squadron and the industrial enterprise.
• 05Write field-grade FitReps on squadron-level 6002 officers per MCO 1610.7 — the GMO's relative-value ranking of the squadron MOOs shapes the LtCol selection picture for the entire community.
• 06Develop and execute a MAG-level maintenance training and inspection plan that integrates with the type wing T&R requirements and the wing's formal inspection cycle.

• —COMNAVAIRFORINST 4790.2 — NAMP: you are now the compliance inspector, not the compliance subject — know every chapter well enough to conduct a formal CAV or assist a squadron that is failing one.
• —NAVAIRINST 4790.14 series — Naval Aviation Logistics Information System (NALCOMIS) policy: the group-level maintenance officer reads the system output across multiple squadrons simultaneously.
• —OPNAVINST 3750.6 — Naval Aviation Safety Program: MAG-level safety data synthesis, mishap trend analysis, and the wing safety inputs you are now producing rather than receiving.
• —NAVSUP P-485 — Naval Supply Procedures: AVDLR management, COSAL adequacy, cannibalization authorization, and parts-sharing authorities at the MAG level.
• —MCWP 3-20 series — Marine Aviation: the operational doctrine context for why maintenance readiness translates directly to MAGTF aviation capability, which is the framing the wing commander uses at every readiness brief.
• —CJCSI 3401.01 series — Joint Reporting Requirements for Readiness: the joint readiness reporting framework that translates squadron and MAG NAMP metrics into the DRRS (Defense Readiness Reporting System) inputs the combatant command reads.

• —MAG Maintenance Officer or equivalent field-grade billet as primary assignment — the career-development assignment at O-4 that gates the LtCol community.
• —Command and Staff College (CSC) completion — resident or non-resident; the LtCol board reads PME at field grade as a basic expectation, not a differentiator.
• —MAG-level availability rate at or above the type wing baseline — the wing maintenance officer publishes a comparison report and the MAG commander's name is next to the number.
• —Zero formal inspection findings in the NAMP compliance domain attributable to systemic MAG-level policy failures during the tour — unit-level discrepancies are the squadron's; policy gaps are the GMO's.
• —Maj board cleared — the first genuinely competitive selection in the 6002 career; pull current MMPB promotion release for actual selection rates before drawing conclusions.

• —Running the MAG maintenance brief from squadron self-reported numbers without verifying the NALCOMIS data independently. Squadrons under pressure to show good availability numbers sometimes code TNMCS days differently from the policy standard; the GMO who catches the discrepancy in his own brief prevents the wing commander from receiving inaccurate readiness data.
• —Treating the NAMP compliance assistance visit as a box-check. A CAV that documents the finding and closes the report without a recovery plan is a record that the finding existed; a CAV that actually fixes the systemic issue is the one the wing commander remembers at FitRep time.
• —Failing to use cannibalization authority correctly. Unauthorized cannibalization — removing a serviceable component from one aircraft to fix another without proper documentation, authorization, and NALCOMIS work order — creates a maintenance liability that propagates through the type wing data and triggers an ACC-level audit.
• —Under-rating a squadron MOO on the FitRep relative-value stack because the personal relationship is comfortable. The 6002 community is small; the LtCol board reads the GMO's relative-value stack as the most honest signal available, and a compressed stack where everyone is tied for first communicates nothing.
• —Leaving the wing-level safety data brief to the wing safety officer without synthesizing it against the MAG's own mishap and hazard data. The MAG commander needs to understand whether his trends are an outlier or a reflection of a wing-wide pattern — that analysis lives with the GMO.

The good 6002 major is the GMO the wing maintenance officer calls when a squadron's NAMP compliance is slipping before it turns into a formal inspection finding — because his CAV methodology is known to be honest and his recovery plans are executable. His MAG availability rate is above the type wing baseline, his squadron MOO FitRep stack has something to say about differentiation, and the wing commander already knows his name from the right kind of readiness brief. The LtCol board reads his FitRep profile and sees a maintenance officer who ran the GMO billet like a command — not like a staff assignment.

You are the lieutenant colonel who either commands a Marine Aviation Logistics Squadron (MALS) or sits on the wing or TECOM staff as the maintenance policy authority. The MALS command tour is the 6002 career equivalent of commanding a rifle battalion — the billet that defines the rest.

Marine Aviation Logistics Squadrons (MALS) are the intermediate maintenance activity (IMA) and aviation supply organization that supports all squadrons within a Marine Aircraft Group. The MALS commanding officer is accountable for intermediate-level maintenance (IMA), ground support equipment (GSE), aviation supply chain management, AVDLR item repair and return, and the calibration and metrology support for the entire MAG. Your command encompasses several hundred Marines across multiple functions, multiple aircraft types, and a supply chain that runs through the naval aviation enterprise. You write the FitRep stack for twelve to twenty officers and senior SNCOs, you interface with NAVAIR logistics representatives and NAVSUP on AVDLR performance, you lead the MALS through the formal Wing Maintenance Inspection (WMI), and you brief the MAG commander and the wing commander on MALS readiness. Simultaneously, you may be serving on the wing staff as the wing maintenance officer or the wing aviation safety officer, managing the same aggregate-level brief at wing scope. The MALS command FitRep from the wing commander is the document the colonel board reads — and the colonel community is small enough that every wing commander in the MAW has an opinion about the MALS CO before he arrives at the command.

• 01Manage a Marine Aviation Logistics Squadron as commanding officer — production control at IMA level, AVDLR repair and return performance, aviation supply effectiveness, GSE readiness — to the Wing Maintenance Inspection standard.
• 02Build the MALS readiness brief that the wing commander can brief the MARFORPAC/MARFORCOM maintenance staff from — IMA production rates, AVDLR turn-around times, supply effectiveness percentage, and TNMCS aging trends across the MAG.
• 03Coordinate the MALS formal inspection cycle with the Wing Maintenance Inspection (WMI) schedule — pre-inspection NAMP compliance audit, corrective action tracking, and post-inspection recovery plan execution.
• 04Manage the MALS AVDLR program — items inducted, items turned around within standard, items awaiting parts, items condemned — and interface with NAVSUP and the ACC to improve turn-around time on aging inductions.
• 05Write command-level FitReps on a mixed officer and SNCO population across multiple functional areas — the relative-value ranking under MCO 1610.7 at MALS command scope shapes the 6002 community pipeline for a full promotion cycle.
• 06Develop and brief the MAG's ground safety and aviation safety trend analysis to the wing safety board — MALS's data combines IMA, supply, and GSE mishap and hazard data that no squadron-level safety officer sees in aggregate.

• —COMNAVAIRFORINST 4790.2 — NAMP at IMA level: Chapter 8 (AIMD/MALS organizational structure and responsibilities) is the foundational document for every process the MALS runs.
• —NAVSUP P-485 — Naval Supply Procedures: AVDLR management, requisitioning, supply effectiveness metrics, and COSAL management at the MALS level.
• —NAVAIRINST 4790.14 series — NALCOMIS: the MALS CO reads the IMA production module and the supply module simultaneously; NALCOMIS is the source of truth for every brief to the MAG and wing commander.
• —OPNAVINST 3750.6 / MCWP 3-20 series — Naval Aviation Safety and Marine Aviation doctrine: the framing context for translating MALS maintenance and supply readiness into MAGTF aviation capability.
• —CJCSI 3401.01 / DRRS-N — Defense Readiness Reporting System (Naval): MALS readiness data rolls into the DRRS readiness report the combatant command reads; know the coding requirements before the first quarter close.
• —MCO 1610.7 — Performance Evaluation System: command-level FitRep mechanics, PRO/CON recommendation authority, and relative-value stack management across a large and functionally diverse population.

• —MALS commanding officer tour completed — 18-24 months as the commanding officer of the MAG's intermediate maintenance and aviation supply organization; the colonel board's primary data point for the 6002 community.
• —Wing Maintenance Inspection (WMI) with no major findings attributable to systemic command-level failures in NAMP policy compliance or supply management during the tour.
• —AVDLR turn-around time at or above the type wing baseline — the wing maintenance officer and the ACC both publish metrics; the MALS CO's name is next to the number.
• —Colonel board cleared — the most competitive selection event in the 6002 career outside of general officer screening; pull current MMPB release for actual selection rates before drawing conclusions.
• —Senior School (National War College, Marine Corps War College, or equivalent) completion — the colonel board reads senior school the same way the LtCol board reads Command and Staff College.

• —Allowing AVDLR inductions to age without escalating to NAVSUP and the ACC. Aging AVDLR items reduce the supply effectiveness metric the wing commander briefs to MARFORPAC; when the metric degrades and the recovery plan is not already in motion, the first question is how long the MALS CO knew.
• —Treating the Wing Maintenance Inspection as a standalone event rather than a sustained compliance posture. Inspection preparation that spikes three months before the WMI and collapses immediately after creates a documentation pattern the wing maintenance staff recognizes across cycles.
• —Miscoding IMA production data to improve turn-around metrics. NALCOMIS IMA production records are auditable at every echelon from MALS to NAVAIR; metric manipulation traced back to a command is the kind of finding that travels to the wing commander's FitRep comment.
• —Running a command-level FitRep cycle with a compressed relative-value stack to avoid difficult ranking conversations. At MALS CO scope the colonel board expects to see differentiation; a stack where twelve of fourteen officers are ranked identically tells the board only that the CO avoided the hard call.
• —Under-investing in the MALS ground safety program because the aviation safety program gets more attention. MALS ground operations — IMA production deck, GSE maintenance, fuel handling, ordnance support — have a higher routine mishap exposure than flight operations; the ground safety record is part of the WMI and part of the wing safety brief.

The good 6002 lieutenant colonel commanding a MALS is the one the wing maintenance officer calls when the MAG's TNMCS aging trend breaks in the wrong direction — because he understands the AVDLR pipeline from the induction dock to the NAVSUP requisitioning system and he already has the escalation package drafted before the call ends. His WMI was a confirmation of a sustained posture, not a sprint from a baseline. The colonel board reads the wing commander's FitRep and sees a maintenance CO who ran a complex multi-function command without a major finding — and the MALS's AVDLR metrics are above the type wing baseline for the second year running.

You are the colonel running the wing maintenance function or the type wing maintenance desk — the senior maintenance authority for an entire Marine Aircraft Wing or a major weapons system class. The decisions you make about NAMP policy, inspection standards, and resource prioritization reach every squadron and every MALS in the MAW.

At colonel grade a 6002 officer is serving as the Wing Maintenance Officer, the type wing maintenance desk officer at MARFORPAC or MARFORCOM, a senior NAVAIR technical representative, or as the commanding officer of a large maintenance activity. The wing maintenance officer position is the most prominent: you manage the maintenance readiness picture for all squadrons and MALS units within the Marine Aircraft Wing, you brief the wing commander on aviation readiness for every aircraft type in the MAW's inventory, and you manage the formal inspection cycle (Wing Maintenance Inspections, QAR audits, naval aviation safety surveys) across the entire command. Your work is briefing, policy, inspection oversight, and resource advocacy — not production control. You interface directly with NAVAIR program offices, with type wing desks at MARFORPAC and MARFORCOM, and with NAVSUP's aviation supply chain managers. The colonel board has already cleared your name; now the only remaining competitive event is the brigadier general screening, and the wing commander's FitRep from this billet is the document that gets read.

• 01Build and deliver the wing-level maintenance readiness brief to the wing commander — aggregate availability rates across all aircraft types, TNMCS trend analysis, safety trend data, and a resource prioritization recommendation — accurate enough for the wing commander to brief MARFORPAC.
• 02Manage the formal Wing Maintenance Inspection cycle for all subordinate units — inspection scheduling, pre-inspection compliance reviews, findings management, and post-inspection recovery plan tracking across multiple squadrons and MALS.
• 03Interface with NAVAIR program office representatives and type wing desks on systemic airworthiness issues, technical directive compliance, and aircraft modification program timelines that affect MAW readiness.
• 04Advocate for wing-level maintenance resource requirements in the PPBE process — man-hours, parts funding, GSE modernization, NALCOMIS infrastructure — and translate technical requirements into the programmatic language the wing commander and the MARFOR staff need for budget submissions.
• 05Manage the wing aviation safety program in concert with the wing safety officer — mishap trend analysis, hazard reporting culture, safety climate surveys, and the wing commander's monthly aviation safety action team (ASAT) brief.
• 06Mentor the MAG GMOs and MALS commanding officers in the wing — the wing maintenance officer's FitRep authority over the O-5 population shapes the 6002 community pipeline through a full LtCol and colonel selection cycle.

• —COMNAVAIRFORINST 4790.2 — NAMP: at wing level you are the policy authority, the senior inspector, and the escalation point for every systemic NAMP compliance problem in the MAW.
• —OPNAVINST 3750.6 — Naval Aviation Safety Program: wing-level safety program management, mishap investigation oversight, and safety survey requirements that the wing commander delegates to the wing safety staff you supervise.
• —MCWP 3-20 — Marine Aviation: the operational doctrine framing that connects NAMP compliance and MALS logistics performance to MAGTF aviation capability at the theater level.
• —CJCSI 3401.01 / DRRS-N — Defense Readiness Reporting: wing-level readiness data feeds the combatant command's operational planning; the wing maintenance officer is the source of the maintenance component.
• —NAVAIR technical directives and program office correspondence for all aircraft types in the MAW inventory — at colonel grade you are reading the airworthiness authority documents, not just implementing them.
• —MCO 1400.32 — Marine Corps Promotion Manual: BGen screening mechanics, FitRep profile requirements, and the select-and-command pipeline for the 6002 community beyond colonel.

• —Wing Maintenance Officer or equivalent senior-colonel billet as primary assignment — the billet that defines the 6002 community contribution at O-6 grade.
• —MAW-level maintenance readiness at or above the MARFOR baseline — the type wing desk publishes comparative readiness data across all MAWs; the wing commander's name is next to the wing number.
• —Zero Class A maintenance mishaps attributable to systemic wing-level policy failures during the tour — wing-level policy failures at O-6 are career-defining events in a small community.
• —War College or equivalent senior PME complete — Senior Service School is the non-negotiable PME requirement for the BGen screening board.
• —BGen screening board eligible — O-6 is the final milestone before the most competitive selection event in the entire 6002 career; pull current MMPB and HQMC screening release data.

• —Allowing the wing maintenance inspection schedule to slip because the squadrons and MALS are under operational pressure. The WMI cycle exists precisely because operational pressure creates the conditions for NAMP compliance degradation — the wing maintenance officer who defers inspections during the high-tempo period is deferring the audit of the period most likely to produce findings.
• —Briefing MARFORPAC readiness numbers from self-reported MAG data without independent NALCOMIS validation. The type wing desk pulls NALCOMIS data independently; when the wing's brief and the type wing's data diverge, the first call goes to the wing maintenance officer.
• —Treating the aviation safety program as the wing safety officer's problem. The wing maintenance officer is the senior maintenance authority; when a maintenance-related Class A mishap occurs in the MAW, the investigation reads the wing maintenance officer's safety program documentation alongside the wing safety officer's.
• —Running a compressed FitRep stack on the O-5 population because the GMOs and MALS COs are all performing above standard. At colonel grade the FitRep relative-value ranking shapes the colonel board read for the entire community — an undifferentiated stack from a wing maintenance officer communicates that he avoided a management responsibility.
• —Ignoring NAVAIR technical directive compliance timing across the MAW. Technical directives (TDs) have compliance deadlines that affect airworthiness authority; aircraft flying with overdue TDs are flying with compromised NATOPS certification, and the wing maintenance officer's name is on the airworthiness status.

The good 6002 colonel is the wing maintenance officer whose MAW arrives at a major exercise with the highest aggregate availability rate in the type wing comparison — and whose WMI findings from the prior cycle were corrected before the next WMI was even scheduled. His NAVAIR counterparts call him before the formal technical directive package arrives because they have learned that his compliance plan is already drafted. The BGen screening board reads his wing commander's FitRep and sees a maintenance authority who ran the wing maintenance function as a command discipline, not a staff function — and the community knows it without being told.

You are the general officer whose aviation maintenance background informs decisions about Marine aviation force structure, readiness resourcing, and the long-term viability of the naval aviation enterprise that the 6002 community exists inside. At this level the technical is indistinguishable from the strategic.

General officers with a 6002 background serve in MAW command, MARFOR aviation staff positions, HQMC aviation branch leadership (Deputy Commandant for Aviation and subordinate), NAVAIR senior acquisition and logistics roles, and joint aviation readiness positions at the combatant command and OSD level. The aircraft availability rates you managed at squadron, MAG, and wing level are now data points in the aviation readiness briefings you give to the Commandant, to SECNAV, and to the House and Senate Armed Services Committees during budget defense cycles. PPBE advocacy for aviation maintenance funding, force structure decisions about MALS organization, the NAVAIR program office relationships you built as a colonel — all of these reach their policy-level expression at general officer grade. You are also the most senior voice in the 6002 community's talent management pipeline: the BGen screening board reads your endorsements, the Marine Corps Recruiting Command, HQMC Manpower, and the MARFOR commanders all call for your read on the officers behind you. The technical career you built from the first NALCOMIS brief in a fleet squadron ends here — as the institutional memory and the strategic advocate for a maintenance community most of Washington encounters only as a line item in the aviation readiness report.

• 01Brief aviation maintenance readiness to HQMC, SECNAV, and Congressional staffs in terms that connect NAMP compliance and AVDLR performance to operational availability and MAGTF capability — the technical detail must survive translation to the policy level without losing accuracy.
• 02Advocate in the PPBE process for aviation maintenance funding — sustainment accounts, AVDLR repair funding, MALS modernization, NALCOMIS infrastructure — against competing priorities inside a constrained TOPLINE.
• 03Shape MALS force structure decisions that balance IMA capability, supply effectiveness, and forward deployment requirements against the personnel and infrastructure costs the Marine Corps is willing to sustain.
• 04Manage the 6002 talent pipeline at the senior leadership level — endorse promotion and selection board recommendations, shape BGen screening inputs, and ensure the community's best officers are positioned for the billets the aviation enterprise needs filled.
• 05Interface with NAVAIR program executive offices and the ACC structure on systemic airworthiness issues, major modification programs, and naval aviation enterprise policy that affect Marine aviation readiness at the force level.
• 06Represent Marine aviation maintenance interests in joint and allied aviation forums — interoperability requirements, shared maintenance infrastructure agreements, and coalition readiness standards.

• —MCWP 3-20 series — Marine Aviation: the doctrinal foundation for translating maintenance readiness into operational capability at the MAGTF level.
• —NAVAIR acquisition and technical authority publications — the program office relationship that connects general officer advocacy to the airworthiness authority structure.
• —DoD Financial Management Regulation (FMR) and PPBE process documentation — the budget process the general officer uses to defend aviation maintenance funding.
• —Congressional Budget Justification (CBJ) documents for the Marine Corps aviation account — the document the 6002 general officer contributes to and defends on the Hill.
• —CJCSI 3401.01 — Joint Readiness Reporting: the joint framework through which Marine aviation maintenance readiness feeds the National Military Strategy readiness assessment.
• —MCO 1400.32 — Marine Corps Promotion Manual at the general officer tier: BGen and MajGen screening mechanics, the Commandant's advisory role, and the SecNav confirmation process.

• —General officer selection — the most competitive selection event in the entire 6002 career and the Marine Corps officer corps; a small fraction of colonels with distinguished records across MOO, MALS command, and wing-level assignments are screened.
• —Senior Service School and strategic-level PME complete as prerequisite for BGen billet assignment.
• —Senate confirmation for BGen and above — the constitutional requirement that transforms a promotion to a commission.
• —Sustained aviation readiness metrics across the career portfolio — the BGen and MajGen communities are small enough that every general officer knows the readiness record of every peer by name.
• —No Class A mishaps attributable to systemic policy failures within the officer's span of command across the career — the general officer's maintenance legacy is visible in the mishap record of the units they commanded.

• —Losing the technical grounding that makes the 6002 general officer's advocacy credible. A general officer who can no longer explain AVDLR turn-around time mechanics or NALCOMIS coding requirements to a Congressional staffer loses the credibility differential that justifies having a maintenance-background officer in the advocacy seat.
• —Allowing PPBE advocacy to compress into a single annual cycle without maintaining continuous engagement with the program offices and the NAVSUP aviation supply chain staff. Aviation maintenance funding fights are won across the year, not in the November budget submission.
• —Under-endorsing 6002 colonels for BGen screening because the relationships are professionally comfortable and the differentiation is difficult. The community is small; an undifferentiated general officer endorsement package communicates that the senior officer avoided the management responsibility that his rank requires.
• —Treating joint aviation readiness forums as attendance obligations rather than influence opportunities. Marine aviation maintenance standards and interoperability requirements are shaped in joint forums by the officers who show up with prepared positions — absence cedes the argument to whichever service sent a prepared advocate.
• —Failing to translate the NAMP framework into policy language the SECNAV staff and the Congressional staffs can use. Aviation maintenance readiness that cannot be explained in terms of operational impact and strategic risk does not survive the budget process — and the 6002 general officer's job is to ensure it does.

The good 6002 general officer is the one the Commandant calls when the SECNAV needs someone who can explain why the AVDLR repair funding line is the most operationally consequential line in the aviation sustainment account — and who can do it in three minutes without losing the technical accuracy that makes the argument defensible. His career maintenance record is legible in the mishap data and the readiness reports from every command he touched. The BGen behind him inherited a community with a clear talent pipeline, a PPBE position that reflects the real cost of sustained aviation readiness, and a NAVAIR relationship that converts program office technical authority into squadron-level aircraft availability.