Fire Controlman

You are the newest set of hands on the most lethal surface combatant in the world. The SPY radar is running overhead and you have not touched it yet — your job is to earn the right to stand in Combat Information Center and be trusted with what it sees.

Fresh out of FC A-school at NTTC Dam Neck or Great Lakes, you check aboard a DDG-51 Arleigh Burke destroyer or CG-47 Ticonderoga cruiser and the ship's combat systems division hands you a PQS binder and a mop. Your first months are cleaning consoles in CIC, standing watch messenger, logging maintenance discrepancies in 3-M, and watching the FC2s and FC1s run Built-In Tests on the Mk 99 Fire Control System or cycle the AN/SPY-1D radar through its startup checklist. You will learn the AEGIS combat system from the bottom up — which takes longer than you think. The PQS does not sign itself. Every watch section you stand, every maintenance evolution you log, and every evolution brief you sit through is building toward the moment the LPO trusts you to put hands on the SPY or the Mk 41 VLS with a senior FC watching. On a deploying ship, "watching" becomes "doing" faster than you expected — come ready.

• 01Complete FC-rate PQS and your ship's 3-M System watch qualification on the LCPO's timeline — every line item signed, not blank-checked.
• 02Log a Planned Maintenance System (PMS) maintenance action correctly in the ship's 3-M system: job sequence number, MRC reference, work performed, signature chain — clean enough that the division officer does not send it back.
• 03Identify the major AEGIS combat system components by designation and location aboard ship: AN/SPY-1D/SPY-6 radar, Mk 99 Fire Control System, AN/UYK-43/44 or AEGIS computing hardware, Mk 41 VLS, CIWS Mk 15 — by compartment, not just by name.
• 04Stand a CIC watch at the assigned console without drawing a correction from the watchsupervisor; report contacts and track data by the ship's procedures, not improvised.
• 05Handle all electronic warfare-sensitive maintenance documentation and weapon-system access logs according to the ship's security classification requirements — one mishandled document goes to the XO.
• 06Meet the Navy Physical Readiness Program standard under OPNAVINST 6110.1 every cycle — the combat systems division chief watches who falls out during PT formation on the flight deck.

• —OPNAVINST 4790.4 series — Ships' 3-M Systems Procedures Manual; every maintenance action you log runs inside this program from day one.
• —OPNAVINST 6110.1 — Navy Physical Readiness Program; your PRT and BCA standard from check-in.
• —NAVPERS 18068 Vol II — Manual of Navy Enlisted Manpower and Personnel Classifications; read the FC-rate NEC entries so the C-school conversation is not a surprise.
• —AEGIS Weapon System training documentation and your ship's Combat Systems Readiness Manual (CSRM) — your LPO will tell you which volumes govern your division's work centers.
• —NWAE Bibliography for Advancement (BIB) for FC3 cycle — pull the current BIB from MyNavyHR/NETC and build a study plan before the advancement window closes on you.
• —OPNAVINST 1306.2 series — Enlisted Distribution and Assignment; understand how the detailing system works before the first sea tour ends.

• —FC-rate PQS complete and signed on the LCPO's timeline — every section, not the ones you found convenient.
• —Ship's 3-M watch qualification earned within the command's expected window; the FCSN who is still unqualified at the six-month mark is visible to the department head.
• —PRT Good Low or higher; BCA in standard — aviation squadrons and surface combatants both notice who falls out during physical training.
• —NWAE study habit established early — FC3 eligibility arrives faster than new FCSNs expect; pull the current BIB from MyNavyHR/NETC and start.
• —Zero security violations tied to classified combat system documentation, weapon system access logs, or CIC entry controls — one goes to the CO and your command will remember it.

• —Logging a maintenance action from memory instead of the MRC. An incorrect job sequence number or a missing corrective-action step is a 3-M audit finding and the division officer's headache at the next Type Commander assessment.
• —Treating CIC access controls and classified systems documentation as bureaucratic overhead. Combat systems spaces have real security controls for real reasons — one unescorted entry log error becomes a security incident report with your name on it.
• —Going around the FC2 or FC1 on a technical question about the combat system. The watch-section chain exists because the AEGIS system is complex, layered, and unforgiving of well-intentioned improvisation; going around it marks you as a sailor who cannot be trusted with the console.
• —Letting your PQS slip because the ship is underway and the schedule is busy. The busy ship is exactly where the LCPO identifies who is self-directed and who needs to be managed — the eEVAL reflects that difference.
• —Posting photos from CIC or the missile deck on social media. The SPY radar, VLS cells, weapon system configurations, and ship-movement patterns are adversary collection targets. The S6 and PAO both sweep social media; the CO is not sympathetic.

The good FCSN is the apprentice the FC1 sends into CIC to clean consoles and pull readings while the senior FCs are running a maintenance evolution, because the FCSN's 3-M documentation comes back accurate and the security log is signed correctly. By month nine the PQS is signed, the ship's 3-M watch is qualified, and the LCPO is asking whether the sailor is leaning toward the fire control track, the SPY radar track, or the VLS/missile side — because the C-school conversation starts before you think it does on a deploying DDG.

You are a petty officer inside the most sophisticated air-defense and strike system the surface Navy operates. The crow means the FC1 trusts you at a console in CIC during an actual evolution, and the ship's combat systems are only as reliable as the maintenance you log.

You own a section of the combat systems maintenance bill — the SPY radar work center, the Mk 99 fire control work center, the Mk 41 VLS, the CIWS, the SSDS suite, or the computing environment depending on your ship and your NEC track — and you execute scheduled maintenance under the FC2 or FC1's supervision. On a DDG-51 with the AN/SPY-1D, that means running MRC-driven PMS on radar transmitter groups, receiver/processor assemblies, and the command and decision computers while the ship is in port, then standing your combat systems watch in CIC during underway operations — calling tracks, managing the tactical picture on the AEGIS display, and reporting system-status changes to the ATAWC or TAO. On a DDG-51 Flight III with the AN/SPY-6 Air and Missile Defense Radar (AMDR), the systems are newer but the maintenance discipline is the same: if it is not in the 3-M system, it did not happen. The C-school and NEC track conversation is now serious — pull the current NEC source-rating NAVADMIN and the OPNAVINST 1306.2 detailing guidance before you fall in love with a pipeline a shipmate told you about two years ago.

• 01Execute a Planned Maintenance System (PMS) MRC on an AEGIS combat system component — SPY radar, Mk 99 FCS, AEGIS computing hardware, or VLS — and document the action in the ship's 3-M system without a return-for-rework from QA.
• 02Stand a CIC watch qualification at the Anti-Air Warfare Coordinator (ATAWC) or Tactical Action Officer (TAO) console as required by the ship's watch bill — report contacts, track status changes, and system alerts by procedure, not instinct.
• 03Identify and report a combat system fault at the component level — radar transmitter fault, fire control loop failure, VLS cell inhibit — with the correct technical language and the correct maintenance reporting chain before the watch supervisor asks.
• 04Operate the ship's combat system in degraded-mode configuration during a training evolution and know which backup modes exist for the SPY, Mk 99, and CIWS when the primary chain faults.
• 05Maintain sub-account tool control and classified system documentation for your assigned work center — every calibrated test tool accountable, every access log signed, nothing left open at watch relief.
• 06Run a safety-of-flight-equivalent safety-of-ship write-up through the combat systems QA chain: correct MRC reference, system impact statement, applicable tech-manual reference, signed by the work center supervisor.

• —OPNAVINST 4790.4 series — Ships' 3-M Systems Procedures Manual; the maintenance program you run every evolution inside.
• —NAVSEA technical manuals for your ship's installed AEGIS combat system components (SPY-1D or SPY-6 series, Mk 99 FCS, Mk 41 VLS, CIWS Mk 15) — your LPO will assign the volumes governing your work center.
• —Combat Systems Readiness Manual (CSRM) for your hull — the command-level governance document that ties together your PMS, watchstanding, and casualty response procedures.
• —NAVPERS 18068 Vol II + the current NEC source-rating NAVADMIN — read the FC-series NEC entries and pull the current cycle before you quote any specific NEC code.
• —NWAE Bibliography for Advancement (BIB) for FC2 cycle — pull from MyNavyHR/NETC; the BIB is the test and the test is the BIB.
• —OPNAVINST 6110.1 — Navy PRT/BCA standard; surface warfare ships pull from the same physical readiness pool as the rest of the sea-duty rotation.

• —NWAE for FC2 prep on the LCPO's timeline — the FC3 who walks into the exam cold is the FC3 who watches the advancement slate from the maintenance bench.
• —QA-clean 3-M documentation: zero return-for-rework on your closed maintenance actions over a deployment cycle is the bar — one return patterns.
• —Ship's combat systems watch qualification earned and current; the Surface Warfare device (SW) in progress before the first deployment ends.
• —PRT Good Medium or better; BCA in standard.
• —At least one NEC pipeline packet in conversation with your LCPO — the FC3 without a documented direction is the one the detailer fills a billet with, not the sailor who asked.

• —Closing a combat system MRC without performing every step. An incomplete maintenance action on the SPY radar transmitter or Mk 41 VLS is not a paperwork problem — it is a casualty waiting to announce itself during an actual engagement evolution, and the 3-M system traces the last signature.
• —Signing off a corrective action you observed but did not personally perform. Co-signing a job you witnessed is one thing; signing for a job you only heard about from the passageway is a fraudulent maintenance entry and a JAGMAN waiting to happen.
• —Improvising a combat system fault response outside your maintenance authorization. The AEGIS system has a defined casualty response and escalation chain; going outside it because you think you found the root cause gets the ship written up for an unauthorized modification and your name on the preliminary inquiry.
• —Letting test equipment calibration slip because the ship is underway and the parts cycle is long. Out-of-cal test equipment contaminates every measurement you made since the last valid calibration date — the Type Commander assessment finds it under your work center.
• —Posting OPSEC-relevant content from the ship's weapons systems: VLS cell configurations, SPY radar alignment photos, CIC console displays, weapon system readiness states, ship departure dates. Adversary intelligence services follow surface combatant social media. One photo ends careers — not just yours.

The good FC3 is the technician the FC1 sends to troubleshoot the maintenance discrepancy that came back twice, because his fault analysis is procedural — he reads the tech manual, follows the MRC, and does not call it until the evidence supports the call. His 3-M documentation closes clean at QA, his CIC watch station requires no supervision, and the LCPO is already mentioning his name for the next FC2 advancement slate and the NEC pipeline the ship needs filled before the next deployment workup.

You are the working senior FC on the maintenance bench and in CIC. The FC3s call you LPO whether the watchbill says so or not, the combat systems chief is mentoring you toward anchors, and the ship's operational readiness is directly dependent on whether your maintenance section runs clean.

You run a section of the ship's combat systems maintenance — the SPY radar work center, the Mk 99 Fire Control System cell, the Mk 41 VLS and weapon systems support, the CIWS and SSDS work center, or the AEGIS computing environment — and you are the senior technician who either owns the fault diagnosis or reviews the FC3's work before it goes to QA. On a DDG in the middle of a deployment workup, that means fault-isolating an AN/SPY-1D transmitter discrepancy with a flight in four hours, checking the Mk 41 VLS cell inhibit log before a live-fire exercise, or troubleshooting a Mk 99 FCS tracking loop fault the ship's tactical team has been working around all watch. You train and qual-sign two to four FC3s and FCSNs, build the section's training plan, manage your sub-account of calibrated test equipment and sensitive work center documentation, write the section's input to the weekly combat systems readiness report, and own the technical authority the LCPO does not have time to be for every job. The NWAE for FC1 is no longer abstract; the eEVAL ranking against your peer FC2s starts to matter for the next advancement slate. NEC-coded billets define the seat — pull the current NEC source-rating NAVADMIN before quoting any specific code to your FC3s.

• 01Own a complex combat system fault from the write-up through fault isolation through corrective action on the AN/SPY-1D or AN/SPY-6 radar, Mk 99 FCS, or Mk 41 VLS — with the system back in readiness status and the 3-M documentation closing clean before the next evolution.
• 02Run a section training plan that keeps FC3s progressing on PQS, NWAE study, and practical proficiency without requiring the LCPO to supervise every milestone.
• 03Review FC3 maintenance documentation before QA sees it — catch the incorrect MRC step, the missing corrective-action reference, the vague discrepancy description — so the section's rework rate stays below the command average.
• 04Stand a qualified Anti-Air Warfare Coordinator (ATAWC) or equivalent senior CIC watch and operate the AEGIS combat system tactical picture at the speed the Tactical Action Officer expects — not learning under fire.
• 05Brief a combat system discrepancy to the Combat Systems Officer (CSO), Weapons Officer, or the Combat Systems Maintenance Manager in terms the watch-section officer understands: what the system was doing, what the fault indicates, what the fix timeline is, and what the backup mode is in the interim.
• 06Mentor an FC3's NEC and C-school packet from idea to selection — and be honest about which NECs actually open billets versus the ones that sound good on the mess deck.

• —OPNAVINST 4790.4 series — Ships' 3-M Systems Procedures Manual; the program your section runs maintenance inside, including the QA provisions you enforce.
• —NAVSEA technical manuals for your ship's AEGIS combat system components — at FC2 you own the technical content, not just the procedure steps your FC3 follows.
• —Combat Systems Readiness Manual (CSRM) for your hull — the command-level governance document that the CSO holds you to at weekly readiness briefs.
• —NAVPERS 18068 Vol II + the current NEC source-rating NAVADMIN — you mentor packets off the current cycle, not the version on the shared drive from two years ago.
• —NWAE Bibliography for Advancement (BIB) for FC1 cycle — current; build a study plan with milestones, not a stack of PDFs nobody opens underway.
• —NAVEDTRA series and Navy COOL program — civilian credentials (CompTIA, FCC General Radiotelephone Operator License, radar/electronics certifications) that the command can fund and the LCPO will note on the EVAL.

• —NWAE for FC1 prep on the LCPO's timeline; BIB study log the chief can defend at the advancement worksheet review.
• —Section QA rework rate at or below command average — your name is on the documentation your FC3s produce after you review it.
• —NEC awarded or in-pipeline — the FC2 without a clear NEC track is visible at the next ranking board in a way that does not help.
• —PRT Good High or better; BCA in standard; Surface Warfare device pinned.
• —eEVAL trait average and ranking that supports an EP or MP recommendation; your LCPO knows your number before the EVAL board reads it.

• —Rubber-stamping FC3 maintenance documentation without actually reading it. Your initials are the standard; if QA finds the error on a closed MRC, the FC2 who signed it owns the finding at the next Type Commander assessment.
• —Chasing an AEGIS combat system fault with parts replacement instead of procedure. An intermittent radar or fire control fault that keeps coming back because the fault isolation was abbreviated costs the supply system, generates a negative trend in the combat systems readiness brief, and lands the section in a QA review.
• —Letting calibration slip on test equipment because the ship is deployed and the depot turnaround is slow. Out-of-cal test sets corrupt every measurement the section produced since the last valid calibration date — the ISIC maintenance assessment finds it under your work center's name.
• —Working outside your maintenance authorization level on an AEGIS subsystem because you are confident in the diagnosis. The authorization chain exists because the combat system has cascading dependencies — the Type Commander and NAVSEA both ask who authorized the work when the casualty board convenes.
• —Going around the LCPO to the CSO. The combat systems chain runs through the chief; the command master chief hears about it the same day and your Chief packet feels it at the next ranking.

The good FC2 is the technician the Combat Systems Officer calls when the SPY radar writes up a fault on deck before an AEGIS readiness event and the clock is running, because the FC2's fault diagnosis is methodical, his 3-M documentation closes clean, and the system is either back in full readiness with a real fix or correctly reported down for a real reason. His FC3s are advancing on schedule, his section's rework rate is in the bottom tier of the department, and the LCPO is already mentioning his name for the next FC1 slate and the advanced NEC pipeline the ship needs filled before the next deployment.

You are the LPO. The chief is editing your Chief packet; the Combat Systems Officer calls you by name before calling the chief; the FC2s and FC3s read the ship's combat systems climate off how you carry the work center at quarters.

You are LPO of a combat systems work center — the SPY radar division, the Mk 41 VLS and weapons systems section, the CIWS/SSDS work center, the fire control track, or the AEGIS computing environment division — running 8-20 FCs and a piece of the ship's overall combat systems readiness. You write four to six eEVALs per cycle for FC2s and FC3s that pick the next NWAE advancement slate. You build the division's training plan, defend the combat systems readiness metrics at the weekly Combat Systems Maintenance Management Board (CSMMB) brief (system availability percentages, deferred maintenance status, PMS completion rates, NEC billet fill), manage calibrated test equipment and classified system documentation accountability at the LPO level, and mentor at least one FC a year into an advanced NEC pipeline, FCC General Radiotelephone Operator License, a commissioning program (LDO/CWO surface warfare, STA-21), or the civilian defense contractor and federal civilian market. The Chief board packet conversation is no longer future-tense — your LCPO is editing your record, your eEVAL profile is being built across the year, and the Surface Warfare device on your blouse is a floor, not a ceiling. Pull the current NEC source-rating NAVADMIN before you advise a junior on any specific NEC code.

• 01Run a work-center combat systems training plan that produces qualified, NEC-progressing, NWAE-advancing FCs without the LCPO having to track every milestone.
• 02Defend the division's combat systems readiness metrics — PMS completion rate, deferred maintenance count, system availability, NEC billet fill status — at CSMMB level without the Combat Systems Officer rewriting your numbers.
• 03Manage calibrated test equipment accountability and classified system documentation at the LPO level — chain-of-custody, calibration due-dates, access-log reconciliation — clean at every no-notice inspection.
• 04Operate as the senior FC technical voice during a combat system casualty, a live-fire exercise, or a Type Commander or INSURV inspection, including the call to brief the department head when the ship's combat readiness posture has actually shifted.
• 05Translate a complex multi-system AEGIS fault — SPY radar chain, Mk 99 fire control loop, Mk 41 VLS cell inhibit, CIWS self-test failure — into weapon system availability language the Combat Systems Officer and the TAO both understand: not jargon, not hedging, a clean assessment with a timeline and a backup mode.
• 06Mentor an FC2's NWAE cycle, NEC pipeline packet, FCC license or commissioning packet from idea to selection — and counsel honestly when the path is wrong for the sailor.

• —OPNAVINST 4790.4 series — Ships' 3-M Systems Procedures Manual; fluent across the QA, tool control, and maintenance documentation provisions you enforce.
• —NAVSEA technical manuals for your ship's AEGIS combat system components — you are the technical authority the CSO signs behind on work center discrepancies.
• —Combat Systems Readiness Manual (CSRM) for your hull — the governance document you defend at CSMMB every week.
• —NAVPERS 18068 Vol II + current NEC source-rating NAVADMIN — build the pipeline off the current cycle.
• —FCC General Radiotelephone Operator License and NAVEDTRA series — you are mentoring your FCs through these credentials, not just pointing at Navy COOL.
• —MILPERSMAN articles governing enlisted promotions, retention, separation, and NJP — you are in the room for the conversations that happen at FC1 visibility level.

• —Chief board packet under construction with the LCPO's eye on every line; eEVAL profile defensible at department head and CO level; Surface Warfare device pinned and current.
• —Work center QA rework rate, calibration compliance, and classified documentation audit posture defensible at CSO and CO level — every cycle, no caveats.
• —Advanced NEC maintained and current; verify currency requirements against the current source-rating NAVADMIN, not from memory.
• —Pipeline output — advanced NEC, FCC license, commissioning, federal civilian or defense contractor credential path — producing at least one selectee or completion per year from your work center.
• —Chief Petty Officer selection board preparation built across the year: the eEVAL profile, the FITREP profile, the awards package, and the warfare qualifications are year-round work, not a week-before submission.

• —Briefing combat systems readiness numbers you have not personally validated against the 3-M system and the PMS schedule. The CSO catches the discrepancy once and your Chief packet feels it permanently.
• —Letting a senior FC2 carry calibrated test equipment or classified documentation accountability because "he is your guy." When he transfers mid-deployment, the gap surfaces under the LPO's name at the next ISIC assessment.
• —Confusing seniority with current technical depth on a new AEGIS baseline — SPY-6 hardware, new AEGIS Baseline software drop, or updated Mk 41 VLS configuration. The FC2 who just came off C-school may know the new baseline better than you do. Let him brief it and stand behind him; the LCPO sees who is honest about the gap.
• —Going around the LCPO to the CSO or the XO. The combat systems leadership chain runs through the chief; the command master chief hears about it the same watch rotation, and the next Chief board reads the pattern.
• —Treating the FCC license, commissioning program, or civilian credential mentoring conversations as transactional checkboxes. The FCs you help credential and commission at this rank shape the surface warfare workforce for the next decade — counsel honestly about every path.

The good FC1 is the LPO the LCPO trusts to run the combat systems work center through a deployment without daily check-ins. His readiness metrics brief without caveats at CSMMB, his eEVALs pick FCs above expectation, and his work center pipeline produces advanced NEC holders, FCC license credentials, and commissioning packets the CSO can brief the CO without rewriting. He sits the Chief selection board with a record that reads itself.

You are a Chief. The gold-fouled anchors mean the goat locker is yours, the Weapons Officer asks you by name before asking the division officer, and the entire combat systems department reads the ship's readiness climate off how you stand at morning quarters on the mess deck.

The job changes more between FC1 and FCC than at any other promotion in the rate. As LCPO of a combat systems department division — the AEGIS systems division on a Arleigh Burke running the SPY radar, the weapons systems division running the Mk 41 VLS and SM-2/SM-3/SM-6 maintenance, the CIWS and SSDS division, or the fire control systems section — you run 10-30 FCs and you own enlisted combat systems execution from the deckplate up. You write Chief-quality eEVALs that pick the next FC1 and FCC slate; you sit at the Combat Systems Maintenance Management Board and Quality Assurance sync as the senior enlisted combat systems voice; you walk the work centers and CIC during a surge, a deployment, or a INSURV or Type Commander weapons systems inspection and identify the broken procedure before the inspector does. You build the next LPO. You mentor the next NEC pipeline, FCC license, LDO/CWO or STA-21 commissioning packet, or defense contractor path. You enforce the 3-M documentation, calibration, classified system security, and QA standards in uniform every day while the deckplate watches whether your technical rigor matches your leadership.

• 01Run an LCPO's shop of FCs — accountability, training, readiness, discipline, family, finance — with weekly cadence the Combat Systems Officer and the department head can predict and trust.
• 02Defend the division's combat systems readiness metrics, QA rework posture, calibration compliance, classified documentation audit status, and deferred maintenance trend at command-level CSMMB without your numbers being rewritten by the CSO.
• 03Walk a real-world surge, INSURV preparation, or Type Commander weapons inspection as the senior enlisted combat systems voice — your AAR is what the Weapons Officer briefs up the chain to the commodore.
• 04Mentor four to six FC1s into Chief-board-competitive candidates; mentor at least one FCC license, LDO/CWO packet, STA-21 application, or defense contractor credential path to completion per year.
• 05Operate as the senior enlisted combat systems voice during a deployment or contingency — including the call to brief the commanding officer when the ship's AEGIS readiness posture has shifted and the tacticians need to know.
• 06Translate NAVSEA, Type Commander, and CSMMB-level combat systems maintenance strategy into deckplate decisions the FCs rehearse without rewording the message.

• —OPNAVINST 4790.4 series — Ships' 3-M Systems Procedures Manual; QA provisions, tool control, and documentation standards you enforce across every work center under your LCPO signature.
• —NAVSEA technical manual library for your ship's AEGIS combat system baseline — you are the LCPO the FC2s and FC1s bring the policy question to.
• —Combat Systems Readiness Manual (CSRM) for your hull — the governance document you defend and execute at command level.
• —COMNAVSURFLANT / COMNAVSURFPAC Type Commander maintenance instructions and NAVADMINs — pull each one as it drops; the ones from two years ago may be superseded.
• —MILPERSMAN — fluent in the articles that govern enlisted personnel actions (advancement, retention, separation, NJP) at FCC-level visibility.
• —CPO 365 / Chief's Mess transition guidance, Senior Enlisted Academy reading list — the goat locker and the wardroom both hold you to this standard every watch rotation.

• —CPO Academy / Chief's Mess transition complete; standing as a Chief in the mess at the deckplate level — not a Chief in title alone.
• —Division QA rework rate, calibration compliance, classified documentation audit posture, and INSURV / Type Commander weapons inspection posture defensible at CSO and CO level every cycle.
• —Advanced NEC maintained and current; verify currency requirements against the current source-rating NAVADMIN.
• —Pipeline producing 1+ FCC license, LDO/CWO packet, STA-21, or defense contractor credential completion per year — and the Weapons Officer can name them.
• —Zero Chief-level integrity incidents — fraternization, financial mismanagement, OPSEC breach, tool accountability fraud, falsified 3-M records. One ends the career permanently.

• —Mistaking the goat locker for a private club. The mess is a working leadership platform; the FCs who watch you enter it every morning are deciding whether the 3-M documentation standard is real or performative.
• —Stopping personal technical study because "I am a Chief now." The AEGIS system evolves with every new baseline drop — the FC2 who just came off the SPY-6 or the latest Baseline-10 C-school will outbrief you at CSMMB if you stop reading.
• —Letting an FC1 LPO run a degraded work center because he is "your guy" or "almost a Chief." The CSO and the Weapons Officer see the readiness metric drift first, and the next Chief slate gets read against the gap.
• —Going public with disagreement with the CSO, Weapons Officer, or CO. The disagreement happens behind closed doors; you walk out aligned. The goat locker enforces this without the wardroom asking.
• —Treating the LDO/CWO, STA-21, FCC license, or defense contractor mentoring as a checkbox. The FCs you credential and commission at this rank shape the surface warfare and defense industrial workforce for the next decade — counsel honestly.

The good FCC is the LCPO the CO calls by name and the goat locker defends in the mess. His division's AEGIS combat systems readiness metrics brief without caveats at CSMMB, his FC1s pick up Chief, his NEC pipeline and commissioning track produces credentials the Weapons Officer can name, and his deckplate rigor on 3-M documentation, calibration, and classified system security matches his at-liberty posture. He is on the Senior Chief slate before the CMC has to ask.

You are the senior enlisted combat systems voice in a ship, squadron, or command. The CO names you in the combat readiness brief. NAVSEA and the Type Commander know your name on the slate. The deckplate watches whether you still walk the work centers.

As FCCS or FCCM you run the senior enlisted combat systems posture for a destroyer squadron (DESRON) or surface warfare command staff, a large combatant's entire combat systems department as Command Master Chief (CMC), a NAVSEA program office or Surface Combat Systems Center (SCSC) as a senior enlisted advisor, or a major Fleet Forces or Type Commander staff billet where the path opens. You write fewer eEVALs but they are the ones that pick the next Chief and Senior Chief slate for the rate. You sit at command-team sync as the senior enlisted voice on every enlisted combat systems decision — accession, NEC programming, C-school quota distribution, retention, classified documentation compliance, discipline. You translate NAVSEA, Type Commander, and OPNAV surface warfare maintenance strategy into command-level talent and readiness decisions. You build the next CMC. You start the post-Navy market plan 24-36 months out — AEGIS program support at Bath Iron Works, Raytheon, Lockheed Martin Mission Systems, L3Harris, or Leonardo DRS; federal civilian at NAVSEA or a Surface Combat Systems Center; or defense contractor AEGIS baseline technical representative — because the bench you leave behind decides whether the ship, the squadron, and the goat locker remember your name.

• 01Run a senior-enlisted command climate across a combat systems department or DESRON staff that produces credentialed FCs, advanced NEC pipeline selectees, LDO/CWO commissions, and STA-21 accessions at rates above the Type Commander average.
• 02Brief the CO, Weapons Officer, commodore, or Type Commander on enlisted combat systems readiness and systemic risk — AEGIS baseline posture, NEC billet fill rates, retention cliff, training pipeline throughput — in language the flag officer can defend at the next echelon without rewriting.
• 03Sit on Chief selection board panels, command CMC slates, and senior-enlisted credentialing review boards with the discipline and confidentiality the convening authority requires.
• 04Translate NAVSEA/OPNAV-led surface combat systems maintenance and modernization strategy into enlisted talent management, NEC programming, and training decisions at the unit and across the rate.
• 05Run a real-world INSURV, Type Commander weapons inspection, or combat readiness review as the senior enlisted combat systems voice on scene — and your AAR is what the commodore reads in the lessons-learned.
• 06Run a Red Cross notification, casualty response, or serious-incident follow-through with the dignity the family and the deckplate both require. You are the face they see.

• —OPNAVINST 4790.4 series and the full NAVSEA technical manual library for your platform's AEGIS combat system baseline — you are cited from these more often than you cite them.
• —COMNAVSURFLANT / COMNAVSURFPAC Type Commander maintenance instructions and current NAVADMINs — pull each one as it drops, not from a stale shared drive two deployment cycles old.
• —MILPERSMAN — fluent on enlisted personnel actions at the senior-enlisted threshold; you are in the room for NJP, separation, and high-visibility cases.
• —Senior Enlisted Academy (SEA, Naval War College Newport RI) reading list and CMC / Fleet Master Chief Symposium materials — you consume doctrine and translate it down.
• —NAVSEA Surface Combat Systems Center (SCSC) technical advisor pathway, Raytheon / Lockheed Martin AEGIS program technical representative hiring criteria, and federal civilian GS-series position descriptions — the civilian market the FCs you mentor will enter; know it better than the career counselor does.
• —OPNAVINST 6110.1 — Navy Physical Readiness Program; you are still in standard and you are still walking the flight deck at PT.

• —Senior Enlisted Academy (SEA) fellowship or equivalent senior-enlisted PME complete before competing for command CMC or Force Master Chief slate.
• —Command-level combat systems inspection (INSURV weapons systems portion, Type Commander Operational Readiness Evaluation, or equivalent) passed without senior-enlisted-attributable findings during your tenure.
• —Advanced NEC, LDO/CWO commissioning, STA-21, and defense contractor / federal civilian credential pipeline producing 1+ completion or selectee per year from your command — and the Type Commander can name them.
• —eEVAL profile that the senior rater can defend at command and squadron or TYCOM level — your rated chiefs are picking up Senior Chief and Master Chief on schedule.
• —Zero senior-enlisted-level integrity incidents — financial, fraternization, OPSEC, classified documentation fraud, falsified 3-M records. One ends the career permanently and there is no recovery at this paygrade.

• —Pretending to be the current technical authority on the latest AEGIS baseline or SPY-6 configuration where you are a software version behind. Senior FCs lose credibility the first time the FC2 from the most recent C-school has to correct the FCCM in a readiness brief — own the gap and own the senior FC who fills it.
• —Letting a Chief-led work center drift on 3-M documentation compliance, calibration, or classified system security because "the CSO will catch it." You own the enlisted combat systems execution at the command roll-up; the INSURV inspection finds it under your name.
• —Treating the LDO/CWO, STA-21, NAVSEA advisor, or defense contractor mentoring conversation as transactional. The FCs you credential and commission at FCCM build the surface warfare officer corps and the AEGIS industrial base the Navy and the nation depend on for decades.
• —Going public with disagreement with the CO, Weapons Officer, or commodore. Take it to the office. Walk out aligned. The goat locker and the wardroom both enforce it, and at FCCM the standard is absolute.
• —Confusing the warm-up to retirement with the job. Until you walk out of the formation for the last time, the deckplate is reading which one you are working — and the formation does not forget which FCCM was checking the boxes versus carrying the standard.

The good Master Chief Fire Controlman is the senior enlisted combat systems voice the CO, Weapons Officer, commodore, and Type Commander all name without thinking. His command's AEGIS pipeline produces LDO commissions, STA-21 accessions, advanced NEC holders, and defense contractor and federal civilian credentials at rates the Type Commander quotes in talent management reports; his rated chiefs pick up Senior Chief and Master Chief on schedule; his combat systems inspection posture is the one the INSURV team cites as the standard across the waterfront. When he retires, the NAVSEA program office and the AEGIS defense contractor community already have his number, and the goat locker and the deckplate remember the standard he left — not the position he held.