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
FCE6

Fire Controlman

E-6 (Staff Sergeant) · Navy

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

FC1 is where the Chief board is not a future question — it is the active work your LCPO is doing on your behalf right now, whether you know it or not. The eEVAL profile you build across this tour, the combat systems readiness numbers you defend at CSMMB, and the FCs you develop into NEC pipeline candidates are the record the board reads. The ship does not care about your intent; it reads your numbers.

The Honest MOS Read
Fire Controlman First Class Petty Officer (FC1, E-6) is the lead petty officer billet of a combat systems work center aboard a DDG-51 Arleigh Burke destroyer, a CG-47 Ticonderoga cruiser, or a NAVSEA / Type Commander shore combat systems billet. The anchors are not yet on the collar, but the work is Chief work already. You run 8-20 FCs — FC2s, FC3s, and FCSNs — who are the hands-on maintainers and operators of the ship's AEGIS combat systems: the AN/SPY-1D or AN/SPY-6 Air and Missile Defense Radar, the Mk 99 Fire Control System, the Mk 41 Vertical Launch System and the SM-2/SM-3/SM-6 missile complement, the CIWS Mk 15, the Surface Ship Defense Suite, and the computing environment that ties the tactical picture together in CIC. You do not touch every piece of gear personally — you train, supervise, and sign for the people who do, and you own the accountability for every maintenance action, calibrated test set, and classified system document in your work center at the LPO level. The Combat Systems Maintenance Management Board (CSMMB) is the weekly reckoning. Your division officer and the Combat Systems Officer (CSO) sit across from you with the readiness numbers — PMS completion rates, system availability percentages, deferred maintenance count, NEC billet fill status — and the numbers either defend themselves or they do not. The FC1 whose numbers require narrative repair at CSMMB is the FC1 the CSO stops trusting by the second cycle. The FC1 whose numbers are clean and whose explanations for any amber metric include a timeline and a backup mode is the FC1 the CSO briefs to the Weapons Officer and the CO without editing. That is the difference between the FC1 who sits the Chief board from a position of strength and the one who sits it hoping the eEVAL profile survived the tour. The eEVAL you write for your FC2s and FC3s is the most consequential writing assignment of your FC1 tour. The sailor you rank first in a peer group, you rate as Early Promote, and describe in specific, measurable terms is the sailor whose advancement trajectory you own. The eEVAL that uses generic language, ranks first in a group of one, or inflates every trait to the top of the scale helps nobody — least of all the sailor, who will compete on that record against FC2s whose LPOs wrote honestly. Write the truth, rank honestly, and defend the ranking when the CO's EVAL board pushes back. That is Chief-quality work. Outside the readiness metrics and eEVALs, the FC1's work is mentoring. The FC2 who needs a nudge toward the advanced NEC pipeline. The FC3 who is smart enough for an FCC General Radiotelephone Operator License and does not know it. The sailor in the back of the work center who is academically qualified for STA-21 or the LDO/CWO surface warfare commissioning pipeline but has never heard it named in a mentoring conversation. These conversations happen in the maintenance bay and in the passageway, not in a scheduled counseling session — because the best FCs will not wait for the appointment. The FC1 who has these conversations honestly, and who follows up on them, is the FC1 whose work center pipeline produces credentials the Weapons Officer can name when the Type Commander asks. The Chief selection board reads your record, not your intentions. Every work center metric, every eEVAL, every award, every school, every qual is the record. Build it every day of the FC1 tour — the board reads it in about four hours.
Career Arc
  • 01FC1 pin-on via NWAE advancement from FC2 — the eEVAL profile, the NEC credentials, and the warfare device were the floor to get here.
  • 02LPO assignment in a combat systems work center (SPY radar division, Mk 41 VLS section, CIWS/SSDS division, fire control section, or AEGIS computing environment) — 3-M documentation and readiness metrics are now your name.
  • 03Chief board packet construction across the tour — the LCPO is editing the record you are building; the eEVAL profile is the backbone; warfare qualifications and school credentials are the supporting structure.
  • 04Advanced NEC completion or in-pipeline; FCC General Radiotelephone Operator License pursued or complete; mentoring output producing at least one FC per year toward NEC, commissioning, or defense contractor credentialing.
  • 05CSMMB-level readiness defense routine — PMS completion, deferred maintenance, system availability, calibration, classified documentation posture are weekly deliverables, not inspection prep.
  • 06Chief selection board slate — the FC1 who sat the board from a strong position prepared across the entire FC1 tour, not in the six weeks before the package closed.
  • 07Post-selection: CPO Academy and the goat locker transition, LCPO billet as FCC in a combat systems division.
Common Screwups
  • ×DUI, NJP, or Article 15 at FC1 — the Chief board's first filter is integrity. One NJP at E-6 does not just delay selection; in a competitive rate it ends it. The surface warfare community is small, the board reads the record, and the FC1 who carries a page-13 or NJP into the selection window is asking the board to defend a choice no sitting Chief would make for their own work center.
  • ×Falsifying 3-M documentation or certifying a maintenance action that was not performed. A fraudulent maintenance entry on a combat system — SPY radar, Mk 41 VLS, CIWS — is not a paperwork violation. It is a safety-of-ship concern and a JAGMAN trigger. The FC1 who signs for work that was not done, or who allows an FC2 to do it in his work center, owns the investigation and the career consequence equally.
  • ×Going around the LCPO to the CSO or the XO on a personnel or readiness matter. The combat systems leadership chain runs through the chief mess, and the CMC and the Weapons Officer hear about the bypass within the same watch rotation. The pattern read on the Chief board is 'not yet a Chief' — not a leadership quality, a disqualification.
  • ×Financial mismanagement at FC1 — debt, garnishments, or a security-clearance financial adjudication at this paygrade draws command attention. The CMC and the CO sit in the Chief board with that on the record, and the board cannot defend what the CO reads as a reliability risk at the system access level the FC1 holds.
  • ×Treating the eEVAL cycle as an administrative formality. The FC1 who writes generic eEVALs, ranks everyone in a peer group of one, or inflates every trait produces a record the advancement board reads as padded. The FC2 you should have ranked first missed a cycle because the writing was not honest. That is a career consequence you inflicted on a sailor you were supposed to protect.

A Day in the Life

  • 0530PT formation on the flight deck or pier. The FC1 LPO is visible at PT — not because the LCPO is watching, but because the FC2s and FC3s in the work center read the division's readiness standards off the LPO's personal ones. The FC1 who sandbags PT is the same FC1 who signs calibration records without checking them.
  • 0700Hygiene, breakfast, muster. Division quarters on the mess deck: accountability pass, safety brief if any scheduled evolution involves energized systems or confined spaces, uniform of the day confirmation, any command announcements. The LPO runs quarters — not the division officer. The FCs read the ship's operational climate off quarters.
  • 0800Work center open. Pre-maintenance brief with the senior FC2 and the work center supervisor: today's PMS schedule, any carry-over corrective maintenance from yesterday, calibration items due this week, any evolution requiring CIC access coordination with the watch. Assign sailors to jobs. If there is a ship-scheduled AEGIS combat system readiness event this week, this brief includes a readiness check of the applicable systems.
  • 0830-1100Maintenance execution and work center supervision. The FC3s and FCSNs are running MRCs; the senior FC2 is supervising the complex fault isolation; you are spot-checking documentation, walking the QA chain before actions close, validating calibrated test equipment is being used correctly, and catching the discrepancy before it goes to QA. Between spot-checks: eEVAL drafting, pipeline mentoring conversations, CSMMB prep if the weekly board is tomorrow.
  • 1100-1300Chow. The FC1 eats with the LPO peer group aboard ship — first class mess when available, or common mess on smaller combatants. This is where information moves: NAVADMIN drops, detailer news, school slot openings, Chief board scuttlebutt. The FC1 who eats at his desk alone knows less than the one at the mess table.
  • 1300-1500Afternoon maintenance window. Complex corrective actions, QA closure on morning MRCs, classified system documentation reconciliation, calibrated test set accountability sweep. If there is a CIC watch to stand this afternoon, the FC1 relieves on time and runs the watch section without requiring the TAO to manage the combat systems picture.
  • 1500-1630CSMMB or weekly readiness sync with the division officer. PMS completion rate, deferred maintenance status, system availability, NEC billet fill — numbers only, no narrative. The FC1 who walks into this meeting with the numbers validated is the one who walks out without corrections. Sensitive item accountability before end of work day: tool control register reconciliation, classified document log check.
  • 1630-1800Work center close-out. FC2 and FC3 briefs out of any incomplete work; carry-over tracked in the maintenance log; tomorrow's PMS schedule assigned. The LPO signs off the work center log, confirms the watch is set and the space is secured correctly, and clears for liberty. If a sailor has a personal issue — finance, family, disciplinary — this is when the LPO hears about it before the LCPO does. Handle it at the LPO level if it can be handled there.
  • 1900-2100Off-duty: family if ashore, study if in NWAE prep window or FCC license prep. The FC1 who is serious about the Chief board is working the BIB or the eEVAL draft or the pipeline packet during this window, not because the LCPO assigned it, but because the board reads the output.

Weekly Cadence

Monday is the planning day. The weekend brought a maintenance backlog on any ship that ran an underway evolution — fault reports, PMS deferrals, calibration issues that surfaced during the weekend watch. The FC1 hits the work center at 0800 with the 3-M system open on the maintenance terminal and the week's PMS schedule assigned to names before the first MRC is pulled. The CSMMB brief is usually Thursday or Friday; the numbers that brief there are built this week. Every deferred maintenance item, every open corrective action, every calibration due-date is on the planning board by Monday noon. Tuesday and Wednesday are execution days — maintenance runs, CIC watches, training evolutions if scheduled. The FC1 is moving between the maintenance deck and CIC, checking documentation quality before it closes, signing QA actions, supervising fault isolation on any open casualty. Training is not a scheduled event on most DDG combat systems divisions; it happens in the gaps. The FC1 who uses a slow Tuesday afternoon to run a degraded-mode combat system training session with the FC3s is the LPO whose sailors are operationally ready when the TAO needs them. Thursday is administrative day — eEVAL drafts, pipeline paperwork, classified documentation reconciliation at scale, pre-CSMMB number validation. The FC1 validates every readiness metric against the source data before Thursday afternoon so the CSMMB brief on Friday is not built from memory. Friday is the CSMMB brief, command-level weekly readiness reporting, and command release. The FC1 who walks into Friday's brief with clean, validated numbers and a clear explanation for any amber trend is the FC1 the CSO is no longer personally tracking by mid-deployment. Underway and deployment cycles compress the garrison cadence into watch sections and maintenance windows. The rhythm shifts: maintenance runs between CIC watches, CSMMB happens at sea over the ship's internal network or at the weekly wardroom-and-mess brief. What does not compress is the accountability standard. The calibration register, the classified documentation log, and the 3-M closure quality do not get easier under deployment OPTEMPO — they require more active attention from the LPO, not less. The FC1 who tightens the accountability standard when the ship pulls out of port is the FC1 the LCPO does not worry about in the deployment eEVAL window.

Key Skills — How to Drill Each

  1. 01
    Run a work center combat systems training plan that produces NEC-progressing, NWAE-advancing FCs without the LCPO managing every milestone.
    Build the training plan as a living document: FC2 names mapped to their current NEC pipeline status, NWAE study window, PQS signature progress, and next qualification milestone. Review it weekly with your senior FC2 and brief it monthly to the LCPO. The FC1 who can tell the LCPO exactly where every sailor is without consulting a spreadsheet built at the start of the deployment is the FC1 the LCPO stops tracking manually — because he trusts the answer.
  2. 02
    Defend the division's combat systems readiness metrics at CSMMB without the CSO rewriting your numbers.
    The numbers brief themselves if you validate them personally the day before CSMMB. Walk every open MRC in the 3-M system. Walk every deferred maintenance entry. Check calibration due-dates on every test set in the work center. If a number is amber or red, brief it with a timeline and a backup mode before the CSO asks. The FC1 who shows up to CSMMB with a story to explain the numbers is the FC1 whose readiness brief gets annotated with the CSO's corrections — and the Weapons Officer reads those corrections.
  3. 03
    Manage calibrated test equipment accountability and classified system documentation at the LPO level — clean at every no-notice inspection.
    Set a weekly rhythm: Friday before knock-off, the senior FC2 pulls a full inventory of calibrated test sets against the tool-control register and verifies calibration due-dates. You spot-check three random items from the register. The classified system documentation log gets reconciled against the access-control register. You sign off. The ISIC maintenance assessment and the Type Commander weapons inspection arrive unannounced; the LPO whose work center is in shape on a random Tuesday is the LPO whose inspection ends before lunch.
  4. 04
    Translate a complex multi-system AEGIS fault into weapon system availability language the CSO and the TAO both understand.
    The fault brief has four parts: what the system was doing when the fault appeared, what the fault indicates at the component level, what the timeline is to return the system to full readiness (with the repair step and the part status if needed), and what the backup mode is in the interim. Rehearse this format with your senior FC2s before the deployment — the first time you brief it should not be during an actual AEGIS system casualty with the TAO watching the clock.
  5. 05
    Write an eEVAL for an FC2 or FC3 that the CO's EVAL board can defend and the advancement board reads as honest.
    Start with measurable outcomes: fault resolutions, 3-M documentation accuracy, training milestones, qualification completions, NEC progress, any duty-section performance under a real evolution or inspection. Rank the sailor accurately against peers. Write the trait marks to the actual performance, not to where you want the sailor to go. The eEVAL that says exactly what the sailor did is the eEVAL the board trusts; the eEVAL that says the sailor is remarkable without a single measurable fact is the eEVAL the board reads as the FC1's writing quality problem.
  6. 06
    Mentor an FC2 through an advanced NEC C-school packet, FCC license prep, or commissioning program application from idea to submission.
    The mentoring conversation starts with an honest assessment of the sailor's qualifications and the program's actual requirements — not the rumors from the mess deck. Pull the current NEC source-rating NAVADMIN for the specific C-school. Pull the current LDO/CWO selection board NAVADMIN or the STA-21 program requirements from MyNavyHR before you quote any number. Then track the milestones with the sailor — not for them. The FC1 who does the work for the sailor produces a sailor who cannot survive the board. The FC1 who coaches the sailor through the work produces a commissioning candidate.

Manuals & References — What Chapters Matter

  • OPNAVINST 4790.4 series — Ships' 3-M Systems Procedures Manual.
    The maintenance program your entire work center runs inside. Fluent through the QA provisions, tool control requirements, documentation standards, and maintenance authorization levels at FC1/LPO visibility. The 3-M audit at the next Type Commander assessment reads the LPO's signature chain; know the instruction before the assessor does.
  • NAVSEA technical manuals for your ship's AEGIS combat system baseline (SPY-1D or SPY-6 series, Mk 99 FCS, Mk 41 VLS, CIWS Mk 15).
    At FC1, you are the technical authority the CSO signs behind on work center discrepancies and corrective actions. Know the governing tech manuals for the specific installed baseline on your hull — the SPY-6 tech manual library on a Flight III DDG is different from the SPY-1D library on a Flight IIA. Pull the applicable NAVSEA volumes through your ship's CSRM references, not from a shared drive from the last command.
  • Combat Systems Readiness Manual (CSRM) for your hull — the command-level governance document that ties together PMS, watchstanding, and casualty response procedures.
    The CSRM is the document you defend at CSMMB. Read it completely during work center check-in — not just the sections that apply to your division. The INSURV inspection team and the Type Commander readiness assessor read the CSRM before they board the ship; the LPO who cannot cite the applicable section during the walk-through is the LPO the assessor writes up.
  • NAVPERS 18068 Vol II + the current NEC source-rating NAVADMIN — pull from MyNavyHR before quoting any specific NEC code.
    You are mentoring FC2s and FC3s through NEC pipeline decisions that affect their entire career trajectory. The NEC source-rating requirements, C-school quotas, and billet fill priorities change with each NAVADMIN cycle. The LPO who advises a sailor on a NEC pipeline based on a two-year-old NAVADMIN sends that sailor into a conversation with the detailer equipped with wrong information.
  • MILPERSMAN — articles governing enlisted advancement, retention, separation, NJP, and personnel actions at FC1 visibility.
    You are in the room for personnel conversations at FC1 visibility level — the FC3 with a retention decision, the FC2 with an NJP recommendation, the sailor requesting a hardship transfer. Know the MILPERSMAN article before you speak. The LPO who quotes policy from memory without checking the current article and is wrong loses the sailor's trust in the conversation where it matters most.
  • FCC General Radiotelephone Operator License (FCC GROL) from the Federal Communications Commission and NAVEDTRA series / Navy COOL program.
    The FCC GROL is a real civilian credential the Navy COOL program funds and the LCPO notes on the EVAL. At FC1, you are mentoring your FCs through it — which means you should hold it yourself, or be actively pursuing it. The FCC Part 8 examination series (Elements 1, 3, and 8 for the GROL + Radar Endorsement) is the credential that follows an FC to the defense contractor market and the federal civilian market beyond the Navy.

Standards — How to Hit Each

  • Chief board packet construction underway with the LCPO's eye on every eEVAL, award, and qualification — the record is being built across the tour, not assembled in the final six weeks.
    Set a quarterly packet review conversation with your LCPO. Bring a current record brief from MyNavyHR. Know where every eEVAL sits in the retention period, what warfare qualifications are current, what school credits are on the record, and what awards have been submitted versus pending. The FC1 who shows up to the final pre-board conversation and discovers a gap that has been open for two years has only themselves to blame.
  • Work center QA rework rate at or below command average — your signature is on the documentation your FC2s and FC3s produce after you review it.
    Review every closed MRC before it goes to QA. Not a spot-check — every one. The MRC step that was skipped, the corrective action that is vague, the system impact statement that is missing — these are the findings the QA officer writes under the LPO's name at the next assessment. The FC1 whose section rework rate is in the bottom tier of the department is the FC1 the CSO stops worrying about.
  • Advanced NEC maintained, current, and verified against the current source-rating NAVADMIN — not from memory or from a shipmate's recollection.
    Pull the current NEC source-rating NAVADMIN from MyNavyHR every six months and verify your own NEC currency requirements. Some NECs have periodic refresher requirements; some have currency-maintenance requirements tied to C-school or practical certification. The LPO who loses NEC currency mid-tour without noticing has a gap on the record the detailer sees before the LCPO does.
  • Pipeline output — advanced NEC, FCC license, commissioning application, or defense contractor credential — producing at least one completion or selectee per year from your work center.
    Name the sailor at the start of each year who is the best candidate for the pipeline you intend to support. Brief that name to the LCPO at the first quarterly packet review. Track the milestones monthly. If the sailor falls off the path, have the honest conversation and name the next candidate. The FC1 whose work center produces zero pipeline completions per year across a two-year tour is the FC1 the Weapons Officer cannot brief to the Type Commander on workforce development.
  • Chief Petty Officer selection board readiness built across the year — the eEVAL profile, warfare qualifications, awards, and school credits are the floor for the board to work from.
    The Chief board is a paper review of your entire record. Every eEVAL in the retention period, every award, every school, every qualification. The FC1 who treats each of these as an annual event to prep for is always behind; the FC1 who treats the record as the daily output of the FC1 tour shows up to the packet review with nothing left to chase.

Technical Mistakes — Concrete Consequences

  • Briefing combat systems readiness numbers at CSMMB without personally validating them against the 3-M system and the PMS schedule the morning before.
    The CSO catches the discrepancy the first time, annotates the brief, and the Weapons Officer sees the annotation. The second time, the FC1 brief is reviewed before the CSMMB meeting instead of at it. By the third instance the FC1's readiness numbers are considered unreliable by the department head, which is the worst possible read to carry into the Chief selection window.
  • Delegating calibrated test equipment accountability or classified system documentation custody to a senior FC2 without a formal hand-off and a reconciliation process.
    When the FC2 transfers mid-deployment, the accountability gap surfaces under the LPO's name at the next ISIC maintenance assessment. One missing calibration record or one unreconciled classified document access log is enough to generate a finding that follows the LPO's record into the Chief board review.
  • Confusing seniority with current technical depth on a new AEGIS baseline — SPY-6, a new AEGIS Baseline software drop, or an updated Mk 41 VLS cell configuration.
    The FC2 who just completed the relevant C-school outbriefs the FC1 on the specific system capability at the CSMMB readiness review. The Weapons Officer and the CSO note who knew the system and who did not. The correct response at FC1 is to acknowledge the gap, defer to the current-trained FC2, and get into the coursework. The response that damages the Chief packet is to fake depth and get corrected in front of the department.
  • Going around the LCPO to the CSO or the XO on a personnel matter, a readiness concern, or a disciplinary question.
    The CMC hears about it within the same watch rotation. The pattern reads to the Chief board as a sailor who does not understand the chief mess — which, at the FC1 selection window, is exactly the wrong signal. The chain runs through the chief; if the chief is the problem, the CMC is the next step, not the CSO.
  • Treating FCC license, LDO/CWO, or STA-21 commissioning mentoring conversations as administrative checkboxes rather than career-changing work.
    The FC who gets a checkbox mentoring conversation produces a half-prepared commissioning package that does not survive the board. The FC who gets an honest, milestone-tracked mentoring conversation produces the surface warfare officer the Navy needs and the credential that makes the Weapons Officer mention the FC1's name at the Type Commander workforce development brief. The gap in outcomes is entirely the LPO's investment.

Career Decisions at This Rank

  • Chief board timing — compete at first look, or work the record another year?
    The Chief board reads your complete eEVAL record, not just the most recent cycle. First-look selectees typically have a multi-year eEVAL profile that demonstrates sustained performance at the top of the peer group, consistently updated warfare qualifications, advanced NEC credentials, and a work center pipeline that the readiness numbers support. If your record has a weak cycle — a year where the readiness metrics were not there, an eEVAL where the ranking reads flat — an additional year to rebuild the profile may produce a stronger packet than competing and not selecting. Talk to your LCPO honestly; the CMC reads board results by name.
  • Advanced NEC track — fire control, SPY radar systems, Mk 41 VLS weapons systems, or AEGIS computing environment?
    The NEC you hold shapes which C-schools you attend, which billets you fill as an LCPO after making Chief, and which defense contractor and federal civilian slots are available after retirement. Pull the current NEC source-rating NAVADMIN and the billet fill data from COMNAVPERSCOM before committing to a pipeline. The SPY radar and fire control NECs fill billets on every AEGIS platform; the VLS and computing environment NECs fill more specialized but critically needed billets. Talk to an FCC who is already running the track you are considering — not a shipmate who heard about it on the mess deck.
  • LDO/CWO Surface Warfare commissioning packet vs staying the senior enlisted track.
    The Limited Duty Officer (LDO) and Chief Warrant Officer (CWO) surface warfare electronics/combat systems programs access candidates from the senior E-6/E-7 pool with strong eEVAL profiles, warfare qualifications, advanced technical credentials, and command recommendations. If you are a top-ranked FC1 with an EP eEVAL profile and a strong warfare record, the commissioning path is genuinely open. The question is not whether you can be selected — it is whether the officer track is the right one for you. LDO and CWO officers carry different authorities and different pressures than senior enlisted FCs; the pay is comparable to senior Chief at the mid-grade officer level. Talk to an FC-rate LDO or CWO officer who made the transition before you finalize the packet.
  • Shore duty NAVSEA or combat systems schoolhouse billet vs continuing the sea-duty combat systems LPO track.
    The FC career alternates sea and shore duty. The shore duty options at FC1 range from schoolhouse instructor at NTTC Dam Neck, recruiter, NAVSEA technical representative billet, or a depot-level maintenance command. Each affects the Chief board package differently. An instructor billet at Dam Neck or a NAVSEA billet builds the institutional credential and the professional network the senior FCCS and FCCM billets depend on. A recruiter tour takes you off the combat systems maintenance track but builds personnel management skills the Chief board notes. Talk to your detailer with specific billet names, not categories.
  • FCC license and defense contractor market preparation vs treating the Navy retirement as the primary financial plan.
    The FC1 who plans to retire from the Navy should be aware that the defense contractor market for AEGIS-trained, NEC-credentialed FCs with a combat systems maintenance background and an FCC license is genuinely active. Raytheon, Lockheed Martin Mission Systems, L3Harris, Leonardo DRS, and the NAVSEA contractor community hire retiring FCs at competitive rates. The FC1 who starts the FCC license at E-6 and maintains it through the career has a civilian credential the Navy's retirement calculator does not include. Start the license early — the GROL plus Radar Endorsement exam series is achievable at E-6 on the Navy COOL program's funding.

How the Seat Varies by Unit Type

  • DDG-51 AEGIS (FC1 LPO → FCC LCPO, combat systems)
    The Fleet standard. The Arleigh Burke class is the FC rate's primary operational platform — the AN/SPY-1D radar on Flight IIA hulls and the AN/SPY-6 on Flight III hulls, the Mk 41 VLS with SM-2/SM-3/SM-6 loadouts, CIWS Mk 15, and the AEGIS computing environment in CIC. FC1 LPO work on a DDG during a deployment workup and a CSG deployment is the record the Chief board reads most often. The CSMMB frequency is weekly; the INSURV readiness posture is a year-round standard; the CIC watch section pace during a CSG deployment is the operational context the senior FCC and FCCM billets are built from. If you make Chief on a DDG, you know the operational baseline the entire rate is built around.
  • CG-47 Ticonderoga (aging platform, pre-decom window)
    The Ticonderoga-class cruiser is in the end of its commissioned service life; decommissioning timelines are driven by hull condition and Navy modernization program decisions. FC1 work on a Tico involves the SPY-1B radar, the legacy AEGIS computing environment, and the full Mk 41 VLS strike and air-defense loadout — on hardware that is older and requires more corrective maintenance than the DDG-51 baseline. The 3-M documentation load is heavier because older systems break more often. The Chief board reads a Tico tour's maintenance complexity as genuine technical depth. When the platform is gone, the FC1 who held the SPY-1B in readiness through the end-of-service period has a maintenance history the SPY-6-era sailors will not have.
  • LCS (different combat systems architecture, small crew)
    The Littoral Combat Ship's combat systems architecture is fundamentally different from the AEGIS DDG/CG baseline — no SPY radar, no VLS, surface and mine warfare mission packages that swap in and out depending on the assigned mission. FC1 work on an LCS involves smaller crew dynamics (fewer FCs in the division), mission module integration, and a command structure where the FC1's technical voice carries more directly to the commanding officer than on a larger combatant. The trade-off: the depth of exposure to the SPY radar and VLS maintenance that builds the Chief board record on a DDG is not available on an LCS. If the goal is the standard AEGIS-centered FC Chief track, the LCS tour should be balanced with at least one AEGIS platform tour.
  • NAVSEA/TYCOM shore combat systems billet
    FC1s at NAVSEA Washington or a Type Commander staff combat systems seat work program management, technical requirements development, maintenance policy oversight, and fleet readiness analysis rather than hands-on maintenance. The professional network built at NAVSEA is the one that opens the post-Navy market with defense contractors and federal civilian billets. The Chief board reads a NAVSEA tour as institutional credibility; the CMC and the rate community know which FC1s went to NAVSEA and came back with a different kind of depth. The trade-off is the same as any shore tour: you are not on the deckplate during the shore assignment, and the Chief board distinguishes sea-duty operational depth from shore-duty institutional depth.
  • NAWCWD/Dam Neck schoolhouse instructor
    NTTC Dam Neck (Virginia Beach, VA) is the primary FC A-school and C-school production pipeline for the Fleet. An FC1 instructor billet at Dam Neck means you are training the next generation of FCs on AEGIS systems, Mk 41 VLS, CIWS, and fire control fundamentals in a controlled lab environment. The professional development impact is genuine — you master the curriculum by teaching it. The Chief board reads an instructor tour as evidence of communication and training skills that the LCPO role requires. The trade-off: the operational tempo of teaching a lab course is not the operational tempo of a deployed DDG, and the readiness metrics you defend at a schoolhouse are student throughput metrics, not combat systems availability percentages.

What Good Looks Like at This Rank

The good FC1 is the LPO the LCPO trusts to run the combat systems work center through a seven-month deployment without a daily check-in. His CSMMB brief runs three minutes because every number is clean and every amber metric comes with a timeline and a backup mode he briefed before the CSO asked. His 3-M documentation closes QA-clean on the first submission. His calibration register is reconciled every Friday. His classified documentation log has never had a discrepancy. His work center has not had a senior-enlisted-attributable finding in the Type Commander's last two assessments. The CSO does not ask questions about his section — which is the highest form of confidence a division officer gives a first class. His FCs are advancing. The FC2 he ranked first and rated EP two cycles ago just pinned FC1 and is already talking to the LCPO about the Chief board. The FC3 he steered toward the advanced NEC pipeline completed C-school last deployment and came back as the division's most current technician on the specific AEGIS subsystem the ship is struggling with. The sailor in the back of the work center who nobody thought was a commissioning candidate is six months into the STA-21 application process because the FC1 had the conversation, tracked the milestones, and told the truth about every requirement. The Weapons Officer knows these names because the FC1 made the Weapons Officer know them. His Chief packet reads itself. The eEVAL profile across the FC1 tour is consistent, honestly written, defensibly ranked, and filled with specific outcomes rather than generic praise. The warfare qualifications are current. The FCC license is on the record. The awards reflect real accomplishments documented at the time they happened, not reconstructed before the board closed. When the CMC sits across from him at the pre-board conversation, the question is not whether the record is competitive. The question is what billet he wants after the CPO Academy.

Preview — The Next Rank

The gold fouled anchors on the FCC's collar represent a structural change in authority, not an incremental advancement. As LCPO of a combat systems division on a DDG or CG, the FCC owns enlisted combat systems execution from the deckplate up — the FC1 LPOs report to the FCC, the work center readiness metrics roll up to the FCC, and the Combat Systems Officer's first call on an AEGIS casualty goes to the FCC, not the FC1. The eEVALs the FCC writes determine which FC1s sit the Chief board from a position of strength and which ones wait. The FCC who writes honestly, ranks accurately, and defends the stack at the command EVAL board is the LCPO who builds the next generation of FCCs. What surprises most new FCCs is the degree to which the job is personnel leadership rather than technical execution. The CSMMB brief is still the weekly reckoning, but the FCC is no longer the one validating every MRC before it closes — the FC1 LPOs carry that accountability, and the FCC's job is to develop FC1s who do not need daily supervision to do it. The CPO Academy transition sets the foundation: the goat locker is a working leadership institution, not a perk, and the CMC expects the FCC to contribute to the mess's collective leadership standard from the first week. The FCC who arrives at the goat locker thinking the anchors mean the hard work is done is the one the mess corrects without waiting for the wardroom to notice.
FAQ

FC E6 — Frequently Asked Questions

Q01What does a E6 FC (Fire Controlman) actually do?
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.
Q02What's the most important thing to know as a E6 FC?
FC1 is where the Chief board is not a future question — it is the active work your LCPO is doing on your behalf right now, whether you know it or not.
Q03What does a typical day look like for a E6 FC?
Time-blocked day at the E6 FC rank tier: 0530 PT formation on the flight deck or pier. The FC1 LPO is visible at PT — not because the LCPO is watching, but because the FC2s and FC3s in the work center read the division's readiness standards off the LPO's personal ones. The FC1 who sandbags PT is the same FC1 who signs calibration records without checking them, 0700 Hygiene, breakfast, muster. Division quarters on the mess deck: accountability pass, safety brief if any scheduled evolution involves energized systems or confined spaces, uniform of the day confirmation,…
Q04What mistakes get E6 FC soldiers fired or relieved?
DUI, NJP, or Article 15 at FC1 — the Chief board's first filter is integrity. One NJP at E-6 does not just delay selection; in a competitive rate it ends it. The surface warfare community is small, the board reads the record, and the FC1 who carries a page-13 or NJP into the selection window is asking the board to defend a choice no sitting Chief would make for their own work center; Falsifying 3-M documentation or certifying a maintenance action that was not performed.…
Q05What career decisions matter most at the E6 FC rank tier?
Chief board timing — compete at first look, or work the record another year? — The Chief board reads your complete eEVAL record, not just the most recent cycle. First-look selectees typically have a multi-year eEVAL profile that demonstrates sustained performance at the top of the peer group, consistently updated warfare qualifications, advanced NEC credentials, and a work center pipeline that the readiness numbers support. If your record has a weak cycle — a year where the readiness metrics were not there,…
Q06What's next after E6 for a FC (Fire Controlman) in the Navy?
The gold fouled anchors on the FCC's collar represent a structural change in authority, not an incremental advancement.
Q07What manuals and regulations does a E6 FC need to know cold?
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.

Based on 14 tips from 0 contributors

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