Skip to main content
HonestMOS
●InvestigationsHow EUCOM shelved a tax break for 9,000 troops in Poland — for five years.→
←Back to FC Fire Controlman — overview, pay, training, civilian translation, reviews
FCE7

Fire Controlman

E-7 (Sergeant First Class) · Navy

E1–E3E-4E-5E-6E-7E8–E9
HEADS UP

The anchor pin changes everything. The night before you put on the anchors, you are the best FC1 on the ship. The morning after, you are the worst Chief — and the mess runs on that humility until you earn the right to walk it back. CPO Academy is not a formality; it is the institutional recalibration that makes a Chief out of a first class, and the goat locker will know whether you showed up or went through the motions.

The Honest MOS Read
Fire Controlman Chief Petty Officer (FCC, E-7) is the LCPO billet for a combat systems division aboard an Arleigh Burke destroyer or Ticonderoga-class cruiser, and the single most important leadership seat in the FC rate's surface warfare career structure. The Weapons Officer knows your name before the division officer does. The Combat Systems Officer calls you on the phone, not your division officer, when the SPY radar writes up a fault forty minutes before an AEGIS readiness event. The CO reads the ship's combat systems posture through the lens of whether the FCC has the division under control — and the goat locker enforces the standard the wardroom sees. The LCPO job on a DDG combat systems division is three things simultaneously. First, it is the technical authority seat: the FCC is the senior enlisted FC who understands the AN/SPY-1D or AN/SPY-6 Air and Missile Defense Radar, the Mk 99 Fire Control System, the Mk 41 VLS, the CIWS Mk 15, and the AEGIS computing environment at the system level — not just the component level. The FC2s and FC3s understand their assigned work centers; the FCC understands how the combat system works together, how a fault in the SPY radar transmitter group cascades into a fire control tracking loop problem, and how to brief the department head on weapon system availability in terms the Weapons Officer can carry to the CO. Second, it is the personnel leadership seat: the FCC writes the eEVALs that pick the next FC1 and FCC advancement slate, mentors the next NWAE cycle and NEC pipeline, manages the division's retention, counsels sailors through the finance and personal problems that eventually surface in work-center performance, and owns the division's family readiness posture during deployment. Third, it is the institutional seat: the FCC is a member of the chief's mess, the goat locker that sets the command's enlisted leadership standard. The mess is not ceremonial. It is a working leadership platform, and the FCC who treats it as a reward for good work at FC1 has not understood the transition. The Combat Systems Maintenance Management Board is the FCC's weekly accountability surface. PMS completion rates, deferred maintenance counts, system availability percentages by work center, calibration compliance, NEC billet fill — the FCC defends these numbers to the CSO every week without the division officer rewriting them. The numbers are not a report of what the FCs did; they are the FCC's assertion of what the division is capable of. The FCC whose numbers are clean, whose deferred maintenance has a timeline and a mitigation, and whose system availability is in the upper tier of the department is the FCC the CSO stops managing actively. The FCC whose numbers are questionable gets managed actively — and the active management shows up in the EVAL profile. INSURV and the Type Commander Operational Readiness Evaluation are the high-stakes tests. INSURV (Board of Inspection and Survey) inspects the combat systems in detail — the maintenance records, the technical documentation, the calibration status, the classified system security posture, and the operational readiness of each installed system. The FCC does not hide from the INSURV team; he walks with them, knows where every discrepancy lives in the 3-M system, and has an explanation for every finding before the inspector writes it down. The Type Commander weapons inspection is the same pattern at the operational readiness level. The FCC whose division passes INSURV and the ORE without senior-enlisted-attributable findings is the FCC the Weapons Officer mentions by name in the debrief. That debrief becomes the eEVAL narrative. The Senior Chief board packet starts the day the anchors go on, not the year before the eligibility window opens. Every eEVAL in the FCC tenure, every award, every school credential, every INSURV outcome, every pipeline selectee is the packet. The FCC who builds the packet across the tour rather than assembling it in the final six weeks is the FCC who sits the Senior Chief board with a record that reads itself.
Career Arc
  • 01FCC pin-on via CPO selection board — CPO Academy transition at the Naval Station or Fleet concentration area nearest the command, and the chief's mess integration that follows.
  • 02LCPO assignment in a combat systems division (SPY radar, VLS/weapons systems, CIWS/SSDS, fire control, or AEGIS computing environment) — the CSMMB readiness brief is now yours.
  • 03First INSURV, Type Commander weapons inspection, or ORE as LCPO — the assessment outcome under your watch is the first major entry in the Senior Chief packet.
  • 04eEVAL cycle as senior rater — the FCs you rank and rate Early Promote are the ones whose advancement trajectory you own; the stack you defend at the CO's EVAL board is the stack the advancement board reads.
  • 05Advanced NEC maintained; pipeline producing LDO/CWO commissions, STA-21 accessions, FCC licenses, and NEC credentials at rates the Weapons Officer can name.
  • 06Sea-tour relief and shore duty rotation (schoolhouse at NTTC Dam Neck, NAVSEA technical billet, recruiter senior leadership, DESRON staff combat systems seat) — the career broadening the Senior Chief board notes.
  • 07Senior Chief selection board eligibility — the complete FCC eEVAL record, CPO Academy completion, warfare qualifications, school credentials, and pipeline output are the board's material.
Common Screwups
  • ×Fraternization — the FCC who develops an inappropriate relationship with a subordinate FC or an officer in the wardroom has ended the Senior Chief packet before it opens. The goat locker and the wardroom both pull back immediately, the CMC acts without hesitation, and the rate's senior enlisted community does not protect a fraternization finding at the Chief level. It is terminal.
  • ×Falsifying 3-M documentation or allowing it to happen in the division without accountability. The FCC who signs a closed MRC for a system maintenance action that was not performed — or who knows an FC1 LPO did it and does not act — owns the JAGMAN investigation outcome. On an AEGIS combat system, a fraudulent maintenance closure is not paperwork fraud; it is a safety-of-ship concern the CO and INSURV team treat with corresponding gravity.
  • ×Financial mismanagement — garnishments, creditor calls to the command, debt-to-income ratios that affect the security clearance adjudication. At FCC, the command's security officer, the CMC, and the CO are all in the loop on financial integrity. The FCC with a documented financial reliability concern cannot be trusted with the weapon system access and classified system custody the LCPO billet requires. The Senior Chief board reads the security clearance record.
  • ×Going public with a disagreement — with the CSO, the Weapons Officer, the CO, or the CMC. The goat locker standard is absolute: the disagreement happens in the office; you walk out aligned. The FCC who breaks this read loses the confidence of the mess before the wardroom reacts. Once the mess stops defending an FCC in the goat locker, the career trajectory changes in ways the EVAL profile does not fully capture.
  • ×Coasting through the FCC tour on the reputation built at FC1. The Senior Chief board reads the FCC eEVAL profile, the LCPO readiness metrics, the division's inspection outcomes, and the pipeline pipeline selectees. The FCC who rests on a strong FC1 record without building a strong FCC record discovers the gap when the board returns 'Did not select' on the first look. There is no graceful way to explain to a deckplate FCC why the best FC1 on the ship didn't make Senior Chief.

A Day in the Life

  • 0515Up before formation. Phone check for overnight command notifications — AEGIS system casualty, sailor in a personal crisis, NAVSEA or TYCOM message that drops overnight, CMC message. The FCC is the first enlisted combat systems call at 0530 if something is wrong. Know before quarters.
  • 0530Command PT on the pier or flight deck. The FCC runs with the division some mornings and solo-lifts others; the rhythm is visible. The FC3 who is watching whether the Chief's PT standards match the PT standards the Chief enforces on the work center will draw the correct conclusion either way. Wednesdays are typically command-run days with the CO and CMC leading the formation.
  • 0700Hygiene, breakfast, dress uniform inspection mirror. 0715: goat locker sync with the CMC and peer FCCs/LCPOs before division quarters. The CMC runs the daily chiefs' mess check-in; the FCC knows what the command wants from the division today before walking into quarters and before the division officer shows up.
  • 0730Division quarters on the mess deck. Accountability, safety brief for any energized or confined-space maintenance evolutions, uniform of the day, command announcements. The FCC runs quarters — the division officer observes and stands alongside but does not run it. The FCs read the command's climate at quarters more accurately than from any other daily evolution.
  • 0800-1100Work center maintenance execution. The FCC is moving between work centers — spotting the FC2's fault diagnosis on the SPY transmitter group, checking the QA chain on the MRC the FC3 is closing, validating calibrated test set usage in the Mk 41 VLS work center, walking the AEGIS computing environment compartment for classified system document posture. Pre-CSMMB number validation if the weekly board is tomorrow. eEVAL drafting in the gaps.
  • 1100-1300Chow in the chiefs' mess. The goat locker is a working leadership conversation — what the CMC heard from the CO this morning, what the wardroom is focused on this week, what the DESRON senior enlisted read on the command, what the pipeline candidates in the mess need from the peer chiefs. The FCC who eats lunch at his desk is the Chief who knows less than the one at the mess table.
  • 1300-1600Afternoon maintenance window, eEVAL and award writing, pipeline mentoring conversations with FC1 LPOs, classified documentation reconciliation, NAVSEA/TYCOM policy update reads. If there is a CIC watch to stand this afternoon, the FCC relieves on time and runs the watch section as the senior FC voice — the TAO should not have to manage the combat systems picture.
  • 1600-1730Pre-close-out readiness sweep. Walk the work centers with the senior FC1: every open corrective maintenance action, every calibration due-date in the next seven days, every deferred maintenance item against its timeline. Classified documentation posture. Tool control reconciliation across every work center. The FCC signs the division's end-of-day log when the sweep is complete, not before.
  • 1730-1900CMC and division officer sync on anything that moved during the day. Discipline issues, sailor personal problems, readiness concerns that will affect tomorrow's PMS execution, any NAVSEA or TYCOM message that requires command action. The FCC who closes the day with the CMC and the division officer is the FCC whose chain does not surprise the next echelon.

Weekly Cadence

Monday sets the division. The FCC walks the work centers at 0800 with the work week's PMS schedule assigned to names, every carry-over maintenance action from the weekend reviewed, and the CSMMB brief due this Friday already in draft form. The weekly LCPO sync with the FC1 LPOs runs Monday morning — not because it has to be Monday, but because the division's execution quality for the rest of the week is set in that thirty-minute conversation. Every FC1 knows by Monday noon what the week's priorities are, what the CSMMB will ask about, and what the Friday close-out will look like. The FCC who runs a predictable Monday runs a predictable week; the FCC who runs a reactive Monday runs a reactive week and briefs the CSO reactively on Friday. Tuesday through Thursday are execution and supervision days — maintenance runs, CIC watches if the ship is underway or conducting alongside training, training evolutions if scheduled. The FCC is not behind the console running the fault isolation; the FC2 runs the fault isolation and the FC1 LPO supervises it. The FCC is the technical authority who reviews the outcome, validates the documentation, and asks the question the FC2 has not asked yet. Thursday afternoon is the CSMMB pre-validation sweep: the FCC walks every work center with the senior FC1, checks every number against the 3-M source data, and builds the Friday brief from what the maintenance record actually says, not from what the FC1 reported Monday. If a number will be amber on Friday, the FCC calls the CSO Thursday evening — the CSMMB brief contains no surprises for the department. The second weekly rhythm is the goat locker. The chief's mess meets as a working leadership group — not every day formally, but the FCC is present in the mess at chow, at the CMC's daily sync, at the peer leadership conversations the CMC runs. The FCC who shows up to the mess meetings and leaves immediately is the Chief the mess identifies as not yet integrated. The FCC who stays for the working conversation, contributes to the mess's collective leadership problems, and leaves when the business is done is the Chief the mess defends when the wardroom asks questions about the division. On underway days and deployment, the tempo compresses: maintenance runs between watches, CSMMB happens over the ship's network, and the mess meets in a smaller space with less time. The disciplines do not compress — the calibration register, the classified documentation, and the eEVAL writing standard hold regardless of the ship's schedule.

Key Skills — How to Drill Each

  1. 01
    Run an LCPO's division of FCs — accountability, readiness, training, discipline, family, finance — with a weekly cadence the CSO and Weapons Officer can predict and trust.
    Establish the division rhythm on day one of the tour: weekly LCPO sync with the FC1 LPOs (Monday morning, no agenda exceptions), Tuesday through Thursday maintenance execution and supervision, Thursday pre-CSMMB number validation with the senior FC1, Friday CSMMB brief. The FCC whose division operates on a predictable cadence is the FCC the CSO does not call between CSMMB meetings. The one who runs the division reactively fields calls from the CSO's office on Wednesday afternoon.
  2. 02
    Defend division combat systems readiness metrics at command-level CSMMB — PMS completion, deferred maintenance trend, system availability, calibration compliance, NEC billet fill — without the numbers being rewritten by the CSO or department head.
    Validate every metric against the 3-M source data the Thursday before CSMMB. Walk the work centers with the senior FC1 Thursday afternoon. Every deferred maintenance item gets a timeline and a mitigation mode before Friday morning. If a number will not be clean by Friday, the FCC calls the CSO Thursday evening — not Friday in the brief. The CSMMB brief should contain no surprises for the department. Surprises in the brief are surprises the Weapons Officer carries to the CO, and the CO heard about them after the department head.
  3. 03
    Walk a real-world INSURV preparation cycle or Type Commander weapons inspection as the senior enlisted combat systems voice on scene — your AAR is what the Weapons Officer briefs up the chain.
    Start the INSURV preparation twelve months out: 3-M documentation audit by work center, calibration compliance sweep, classified system security posture check, tech manual currency verification against the installed AEGIS baseline, PMS schedule completeness audit. The inspection team walks in with the ship's maintenance record; the FCC who knows every open discrepancy before the inspector does is the LCPO who controls the inspection narrative. Write the AAR the same week the inspection concludes, while the findings are current — the Weapons Officer's debrief to the commodore is built from it.
  4. 04
    Mentor four to six FC1 LPOs into Chief-board-competitive candidates; produce at least one LDO/CWO commissioning packet, STA-21 application, FCC license completion, or NEC pipeline selectee per year.
    Run quarterly packet review conversations with every FC1. Pull each sailor's record brief from MyNavyHR. Know where every eEVAL sits in the retention period, what school credits are on the record, what pipeline milestones are pending. The FCC who knows each FC1's board eligibility window twelve months ahead is the FCC whose division produces selectees on schedule. The FCC who learns about a board window at the sixty-day mark is the FCC who sends sailors into the board under-prepared.
  5. 05
    Operate as the senior enlisted combat systems voice during a deployment contingency or AEGIS combat readiness event — including the call to brief the CO when the ship's readiness posture has shifted.
    The LCPO brief to the CO during an AEGIS system casualty has four elements: the system affected, the current readiness state of the affected weapon, the timeline and repair path, and the backup mode during the repair interval. Rehearse the brief format with the FC1 LPOs before deployment. The FCC who has run the brief in rehearsal delivers it clearly under pressure. The FCC who improvises under pressure during a real AEGIS casualty with the TAO watching the clock is the FCC the CO stops calling first.
  6. 06
    Translate NAVSEA, Type Commander, and OPNAV surface warfare maintenance strategy into deckplate decisions the FCs implement without rewording the message.
    Read the COMNAVSURFLANT and COMNAVSURFPAC Type Commander maintenance instruction updates as they drop. Translate the policy change into a work center procedure adjustment the FC1 can brief the FC2s on without the FCC in the room. The LCPO who acts as the translation layer between fleet policy and deckplate execution is the LCPO whose division is never behind the policy cycle. The LCPO who lets policy changes sit in the shared drive until the assessment team asks is the LCPO whose division absorbs the finding.

Manuals & References — What Chapters Matter

  • OPNAVINST 4790.4 series — Ships' 3-M Systems Procedures Manual.
    The maintenance program the entire division runs inside. At FCC/LCPO, fluent across QA provisions, tool control, documentation standards, and maintenance authorization levels — the FCC enforces these across every work center under the LCPO signature. Pull the current revision from the Navy Doctrine Library; the INSURV team uses the current version.
  • NAVSEA technical manual library for your ship's AEGIS combat system baseline — SPY-1D or SPY-6, Mk 99 FCS, Mk 41 VLS (MK-41 VLS Technical Manual series), CIWS Mk 15.
    At FCC/LCPO, you are the technical authority the CSO signs behind on work center discrepancies and corrective actions. Know which NAVSEA technical manual volumes govern the specific installed baseline on your hull — the SPY-6 library on a Flight III DDG is different from the SPY-1D library on a Flight IIA. Request the governing volumes list from your hull's Combat Systems Readiness Manual.
  • Combat Systems Readiness Manual (CSRM) for your hull.
    The governance document you defend and execute at command level. The FCC who reads the CSRM completely during the LCPO check-in period knows the inspection standard, the maintenance authorization limits, and the command-level reporting requirements before the first CSMMB brief. The INSURV team reads the CSRM before they board the ship.
  • COMNAVSURFLANT / COMNAVSURFPAC Type Commander maintenance instructions and current NAVADMINs — pull each one as it drops.
    The fleet-level policy that governs your division's maintenance program and readiness reporting. The FCC who reads each TYCOM instruction update on the day it drops is the FCC whose division is never behind the policy cycle at the next assessment. Stale instructions on the shared drive are an inspection finding.
  • MILPERSMAN — fluent on the articles governing enlisted advancement, retention, separation, NJP, fraternization, and personnel actions at FCC/LCPO visibility.
    You are in the room for personnel actions at Chief-level authority. Know the MILPERSMAN article before you speak to the sailor about it. The LCPO who quotes policy incorrectly and then has to walk it back loses the sailor's confidence in the conversation where the stakes are highest.
  • CPO 365 guidance, Senior Enlisted Academy reading list, and Chief's Mess transition curriculum.
    The institutional framework the goat locker operates from. The FCC who reads the CPO 365 material and the SEA reading list is the Chief the CMC can put in front of a junior sailor, a family readiness group, or the Type Commander's senior enlisted staff with confidence. The goat locker enforces the standard; the reading list is how you know the standard before the mess tests you against it.

Standards — How to Hit Each

  • CPO Academy / Chief's Mess transition complete; standing as a Chief in the mess at the deckplate level — not a Chief in title alone.
    CPO Academy is the institutional recalibration the transition requires. Show up ready to be changed, not to endure the process. The FCC who approaches CPO Academy as a formality arrives at the goat locker as a first class petty officer in Chief anchors — and the mess identifies this within the first week. The FCC who approaches it as the institutional transition it is arrives at the goat locker as a Chief. The deckplate knows the difference.
  • Division QA rework rate, calibration compliance, classified documentation audit posture, and INSURV/ORE weapons inspection posture defensible at CSO and CO level every cycle.
    Each of these is a weekly discipline, not an inspection-prep activity. Build them into the Monday planning cycle and the Friday close-out routine. The FCC whose division metrics are in shape on a random Tuesday is the FCC whose INSURV ends in the morning. The FCC whose metrics are prepared for the inspection and degraded after it is the FCC the next inspection team catches.
  • Advanced NEC maintained and current — verify currency requirements against the current source-rating NAVADMIN, not from memory.
    Pull the NEC source-rating NAVADMIN every six months and verify the currency requirements for your own NEC and for every NEC held by FCs in the division. Some NECs have refresher or recertification requirements tied to C-school or practical evaluation. The FCC who discovers mid-tour that his own NEC lapsed has a personnel record problem and a credibility problem simultaneously.
  • Pipeline producing 1+ LDO/CWO commission, STA-21 selection, FCC license completion, or defense contractor/federal civilian credential path selectee per year — and the Weapons Officer can name them.
    Name the candidate at the start of the year. Track the milestones. When the Weapons Officer asks the FCC how many sailors the division has in the commissioning pipeline, the answer should include a name, a program, and a timeline — not a general description of the mentoring environment. The Type Commander workforce development brief asks for names; the FCC who can provide them is the FCC the Weapons Officer briefs the commodore about.
  • Zero Chief-level integrity incidents — fraternization, financial mismanagement, OPSEC breach, falsified 3-M records, classified system accountability fraud.
    Binary at this rank. The FCC who holds the Chief integrity standard permanently builds the record the CMC and the goat locker defend at every board. The FCC who compromises it once — even in a gray area the wardroom might have navigated differently — loses the goat locker's defense and the career with it. When the gray area appears, take it to the CMC before acting. That is what the mess is for.

Technical Mistakes — Concrete Consequences

  • Mistaking the goat locker for a private club and treating the Chief's Mess transition as a credential rather than a leadership standard.
    The FCs who watch the FCC enter the mess every morning are deciding in real time whether the 3-M documentation standard, the calibration discipline, and the eEVAL honesty are real leadership commitments or performed ones. The FCC who brings the FC1's sense of personal technical entitlement into the mess is the Chief the CMC corrects behind closed doors and the mess does not defend publicly. The EVAL profile reflects the correction; the Senior Chief board reads it.
  • Stopping personal technical study on the AEGIS system because 'I am a Chief now.'
    The FC2 who just returned from the SPY-6 or latest Baseline-10 AEGIS systems C-school outbriefs the FCC on the specific platform capability at the CSMMB readiness review, and the CSO notes who knew the system. The FCC who acknowledges the gap honestly and asks the FC2 to lead the technical presentation maintains authority; the FCC who fakes depth and gets corrected in front of the department loses it. The AEGIS baseline evolves with every software drop; a Chief who stops reading is a Chief who stops being the technical authority by the second deployment.
  • Allowing an FC1 LPO to run a degraded work center because 'he is almost a Senior Chief' or 'he just needs time.'
    The CSO sees the readiness metric drift first, and the Weapons Officer hears about it from the CSO before the FCC brings it up. The pattern read at the next EVAL board is that the LCPO does not hold his FC1s to standard — which is precisely the leadership responsibility the Chief anchors represent. The FCC who allows work-center drift under a peer-level FC1 and does not correct it is the FCC whose own eEVAL narrative includes the caveat the department head inserted.
  • Going public with disagreement with the CSO, Weapons Officer, CO, or CMC.
    The goat locker and the wardroom both enforce this at the Chief level, and the enforcement does not wait for a formal counseling. The FCC who breaks alignment in a passageway conversation, at the CSMMB table, or in a department brief loses the confidence of both the mess and the wardroom simultaneously. The consequences are institutional — the mess stops defending the FCC's decisions to the wardroom, the wardroom stops bringing the FCC into the command team's confidence, and the Senior Chief board reads a flat eEVAL narrative where a senior rater's endorsement used to be.
  • Treating LDO/CWO, STA-21, FCC license, and defense contractor mentoring as a pipeline checkbox rather than the most consequential leadership investment of the FCC tour.
    The FCs who receive a checkbox mentoring conversation produce commissioning packages that do not survive the first board review, NEC pipeline packets with missing documentation, and FCC license exam results that required no real preparation. The FCs who receive honest, milestone-tracked mentoring become the surface warfare officers, the NEC-credentialed senior FCs, and the defense contractor AEGIS technical advisors the Navy and the industrial base depend on for decades. The FCC's mentoring legacy is the one the rate's senior enlisted community quotes when they describe what kind of Chief he was.

Career Decisions at This Rank

  • Senior Chief board timing — first look, or work the record another cycle?
    The Senior Chief board reads the complete FCC eEVAL record, the LCPO readiness metrics, the INSURV and ORE inspection outcomes, and the pipeline selectees. First-look selectees have a multi-year FCC profile that is consistently strong, with defensible readiness metrics, a real inspection outcome under the FCC's watch, and a documented pipeline output. If any of these is weak — a first INSURV that went poorly before the FCC had time to rebuild the division, a readiness metric trend that corrected over the tour but started low — an additional cycle may produce a stronger packet. The CMC knows which way the board will read your record; ask honestly and take the answer.
  • Shore duty after the first sea tour as FCC — schoolhouse, NAVSEA billet, DESRON staff, or recruiting duty?
    The shore duty rotation shapes the Senior Chief packet more than most FCC-level sailors realize. An instructor billet at NTTC Dam Neck builds the institutional credential and the depth on current AEGIS curriculum the Senior Chief board reads as evidence of technical stewardship. A NAVSEA technical billet builds the program-management and defense-industry network the FCCS and FCCM billets depend on. A DESRON staff combat systems seat builds the multi-ship readiness perspective the Type Commander reads at the senior enlisted advisor level. Recruiting duty builds the personnel management depth the CMC track requires. Talk to an FCCS who has been through the shore rotation you are considering before committing.
  • LDO/CWO surface warfare electronics commissioning vs continuing the senior enlisted FC track.
    The LDO/CWO accession window for FCC-level sailors is genuinely competitive if the eEVAL profile is EP-weighted, warfare qualifications are current, and the command endorsement is strong. The question is whether the officer track's authority structure and career constraints match what the FCC wants from the last fifteen years of service. LDO and CWO officers carry different career gates (O-4/CWO4 selectivity, command-qualification requirements, joint duty requirements) than the senior enlisted FC track. Talk to an FC-rate LDO or CWO-5 who made the transition from FCC; ask specifically about the year-three and year-seven career moments that are different from the senior enlisted track.
  • CMC track vs DESRON/TYCOM senior combat systems staff chief track vs NAVSEA program office senior enlisted.
    At FCCS, the next-level billet decision sets the career's final phase. CMC at a surface combatant command is the apex enlisted leadership billet for the surface warfare community; the CMC owns the entire command's enlisted climate, discipline, retention, and family readiness — with the FC rate as one component, not the whole scope. DESRON or Type Commander senior combat systems staff chief focuses the technical authority of the FCCS on multi-ship readiness rather than single-command enlisted climate. NAVSEA program office senior enlisted builds the defense-industry relationship and the acquisition credentialing the post-Navy contractor market pays for. Talk to sitting FCCSs in each billet type before the detailer conversation. Each track is distinct; knowing which one fits the FCC's actual strengths before the orders package arrives is the work the career planner will not do.
  • Post-Navy market preparation — defense contractor, NAVSEA civil service, or second career timeline.
    The AEGIS-trained FCC with an advanced NEC, a combat systems LCPO tour, an INSURV outcome on the record, and an active FCC General Radiotelephone Operator License is genuinely marketable to the AEGIS defense contractor community — Raytheon, Lockheed Martin Mission Systems, L3Harris, Leonardo DRS, and the NAVSEA Surface Combat Systems Center civilian workforce. Federal civil service at NAVSEA as a GS-11 to GS-13 combat systems program analyst or technical representative is a direct translation of the LCPO's work. The FCC who starts the post-Navy preparation conversation with a cleared-contractor recruiter at the ten-year mark — not the twenty-year mark — is the FCC who knows which credentials to prioritize during the FCC and FCCS tours. Start the FCC license before the Senior Chief board if you have not already.

How the Seat Varies by Unit Type

  • DDG-51 AEGIS (FC1 LPO → FCC LCPO, combat systems)
    The operational standard for the entire FC rate. The Arleigh Burke's combat systems division structure — SPY radar, VLS, CIWS, fire control, computing environment — is the LCPO environment the Senior Chief board reads as the defining measure of an FCC's tenure. A DDG LCPO tour during a CSG deployment with a clean INSURV outcome is the packet the board can defend without annotation. The CSMMB frequency is weekly, the ORE standard is rigorous, and the CIC watch section pace during a real-world contested-air-defense evolution is the operational context that separates DDG FCC experience from every other platform assignment.
  • CG-47 Ticonderoga (aging platform, pre-decom window)
    The Ticonderoga-class cruiser's end-of-service period creates a unique LCPO environment: older AEGIS hardware (SPY-1B, legacy computing baseline), heavier corrective maintenance load than a newer DDG, and a ship whose mission value is genuine even as the platform approaches decommissioning. The FCC whose division maintains a Tico's combat systems in INSURV-competitive posture through the final years of commissioned service has demonstrated a maintenance leadership depth that newer platforms do not test the same way. The legacy tech manual library, the parts sourcing challenges, and the command culture of a crew committed to the end of a platform are all on the FCC's record when the board reads it.
  • LCS (different combat systems architecture, small crew)
    The LCS's combat systems structure — no SPY radar, no Mk 41 VLS, mission-module-dependent strike and defense capability — makes the FCC billet experience fundamentally different from an AEGIS combatant. The small crew means the FCC's division is smaller and the FCC's voice reaches the commanding officer more directly; the trade-off is less AEGIS system depth and a readiness brief structure based on mission module readiness rather than CSMMB-standard availability percentages. An FCC who has both an LCS tour and a DDG tour on the record is genuinely versatile; an FCC with only an LCS tour applying for a DESRON AEGIS staff billet will be compared against peers who have more SPY and VLS maintenance hours.
  • NAVSEA/TYCOM shore combat systems billet
    The NAVSEA program office or Type Commander surface combat systems staff billet takes the FCC off the operational deckplate and onto the program side — requirements development, technical baseline management, fleet-wide maintenance policy oversight, and acquisition support for AEGIS modernization programs. The professional network built at NAVSEA Washington or SURFLANT/SURFPAC technical staff opens the post-Navy AEGIS defense contractor and civil service market in a way the operational sea tours alone do not. The Senior Chief board reads a NAVSEA tour as institutional credibility at the program level; the goat locker and the CMC read it as the FCC who spent time understanding where the fleet policy comes from, not just executing it.
  • NAWCWD/Dam Neck schoolhouse instructor
    NTTC Dam Neck is the production pipeline for the Fleet's FCs. An FCC instructor billet means running the AEGIS systems, Mk 41 VLS, CIWS, and fire control curriculum in the schoolhouse lab environment — owning the course content, grading the students, and producing the FCs the Fleet needs with the technical foundation the sea-tour LCPO will build on. The FCC who instructs at Dam Neck for two years knows the AEGIS curriculum at a systematic depth that pure operational maintenance experience does not always produce. The Senior Chief board reads an instructor tour as evidence of the communication and training-development competencies the LCPO role at scale demands. The trade-off: the schoolhouse's maintenance environment is controlled and educational; it is not the unscheduled casualty response of a deployed DDG.

What Good Looks Like at This Rank

The good FCC is the LCPO the CO names when the Weapons Officer asks who runs the best combat systems division in the squadron. His division's AEGIS readiness metrics brief without caveats at CSMMB every week — not because the FCC is managing the presentation, but because the FCs have internalized the standard. His QA rework rate is in the bottom tier of the department. His calibration register has not had an expired test set since the tour started. His classified documentation log has never had a discrepancy the inspector found before the FCC did. The INSURV team walked his division and found nothing they did not already know about. The Type Commander weapons inspection ended before lunch. His FC1 LPOs are advancing. The one he ranked first and rated Early Promote two cycles ago just selected for FCC. The FC2 he steered toward the advanced AEGIS systems NEC came back from C-school as the division's current technical authority on the SPY-6 baseline and outbriefs the FCC on specific subsystem configurations — and the FCC lets him brief it, stands behind him in the room, and takes the outcome to the Weapons Officer as the FCC's achievement, not the FC2's. The sailor in the back of the division who was academically qualified for STA-21 but had never heard it named in a mentoring conversation is two cycles into the commissioning application process because the FCC pulled the current program requirements, walked through every milestone, and told the truth about everything that would make it harder. The Weapons Officer can name every pipeline candidate in the division because the FCC made the Weapons Officer name them. The Senior Chief board packet reads as a tour that was built from the first day of the FCC tour, not assembled in the final quarter. Every eEVAL in the FCC retention period is specific, honestly ranked, and filled with measurable outcomes. The INSURV outcome is in the record. The LCPO steady-state readiness narrative is in the record. The pipeline output is in the record. The CPO Academy completion is in the record. The advanced NEC currency is current. The FCC license is on the record if the sailor earned it before making Chief, or in-progress if the FCC started it during the LCPO tour. The CMC does not have to argue for the FCC at the Senior Chief board — the record argues for itself, and the CMC's endorsement is the confirmation the board needed, not the explanation it required.

Preview — The Next Rank

The FCCS anchors represent a different kind of authority shift than the FCC pin. The FCC owned a combat systems division and the FCs in it. The FCCS owns the enlisted combat systems posture for a DESRON, a large combatant's entire combat systems department as Command Master Chief, a NAVSEA program billet, or a major Fleet Forces or Type Commander staff seat — and the FCC bench beneath the FCCS is now five, ten, or twenty FCCs rather than one work center of FC2s. The eEVALs the FCCS writes determine which FCCs sit the Master Chief board from a position of strength. The readiness metrics the FCCS defends are squadron-level or program-level metrics, not division-level ones. The CSMMB brief the FCCS attends is the commodore's brief, not the CSO's. What surprises most new FCCSs is the degree to which the job is rate stewardship rather than ship stewardship. The FCCS at a DESRON staff does not own a single ship's combat systems division; he owns the enlisted FC posture across a multi-ship squadron and is the senior enlisted voice the commodore calls when the squadron's readiness brief has a combat systems question. The FCCS at a NAVSEA billet does not own a division at all; he owns the program side — requirements, policy, acquisition — and the warfighters who will use the systems being programmed are downstream. The FCCS who misses this shift and continues to run the LCPO playbook at the senior chief level is the FCCS whose Senior Chief tour reads flat on the Master Chief packet. The one who recognizes the shift and builds the DESRON-or-program-level authority is the FCCS the rate names for the CMC/COB diamond or the NAVSEA senior advisor seat.
FAQ

FC E7 — Frequently Asked Questions

Q01What does a E7 FC (Fire Controlman) actually do?
The job changes more between FC1 and FCC than at any other promotion in the rate.
Q02What's the most important thing to know as a E7 FC?
The anchor pin changes everything.
Q03What does a typical day look like for a E7 FC?
Time-blocked day at the E7 FC rank tier: 0515 Up before formation. Phone check for overnight command notifications — AEGIS system casualty, sailor in a personal crisis, NAVSEA or TYCOM message that drops overnight, CMC message. The FCC is the first enlisted combat systems call at 0530 if something is wrong. Know before quarters, 0530 Command PT on the pier or flight deck. The FCC runs with the division some mornings and solo-lifts others; the rhythm is visible.…
Q04What mistakes get E7 FC soldiers fired or relieved?
Fraternization — the FCC who develops an inappropriate relationship with a subordinate FC or an officer in the wardroom has ended the Senior Chief packet before it opens. The goat locker and the wardroom both pull back immediately, the CMC acts without hesitation, and the rate's senior enlisted community does not protect a fraternization finding at the Chief level. It is terminal; Falsifying 3-M documentation or allowing it to happen in the division without accountability.…
Q05What career decisions matter most at the E7 FC rank tier?
Senior Chief board timing — first look, or work the record another cycle? — The Senior Chief board reads the complete FCC eEVAL record, the LCPO readiness metrics, the INSURV and ORE inspection outcomes, and the pipeline selectees. First-look selectees have a multi-year FCC profile that is consistently strong, with defensible readiness metrics, a real inspection outcome under the FCC's watch, and a documented pipeline output. If any of these is weak — a first INSURV that went poorly before the FCC had time to rebuild the division,…
Q06What's next after E7 for a FC (Fire Controlman) in the Navy?
The FCCS anchors represent a different kind of authority shift than the FCC pin.
Q07What manuals and regulations does a E7 FC need to know cold?
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.

Based on 14 tips from 0 contributors

Published by the Honest MOS Editorial DeskVerified against DoD/.gov sourcesUpdated May 2026Editorial standards