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
FCE5

Fire Controlman

E-5 (Sergeant) · Navy

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

FC2 (E-5): you are the working senior tech and the de facto LPO of your work center section whether the watchbill says so yet or not. The FC3s under you are watching how you carry the maintenance bench. The NWAE for FC1 and the advanced NEC stack are both live issues. FCC General Radiotelephone Operator License through Navy COOL is the credential the civilian market pays for — start if you have not. The chief is watching whether the section you run produces FC3s who can work without you.

The Honest MOS Read
You are a Petty Officer Second Class in the combat systems department of an AEGIS surface combatant, and the job looks different from this side of the rank line. The FC3 is running the maintenance action; you are the FC2 who reviews the FC3's documentation before QA sees it, signs PQS line items for the FC3s and FCSNs in your section as the qualified witness, owns the fault isolation diagnosis when the complexity exceeds the FC3's authorization level, manages the calibrated test equipment sub-account and classified documentation accountability, and briefs the combat systems status to the Combat Systems Officer when the CSO asks. The LCPO has a section of the ship's combat systems readiness on your name — not as a task list, as an outcome responsibility. If the section's QA rework rate is high, that is your problem. If the FC3's PQS is stalled, that is your problem. If the calibration sub-account has a due-date the LCPO found before you did, that is your problem. On a DDG-51 Arleigh Burke in the middle of a deployment workup, the FC2 is the technician who owns the complex fault isolation. The AN/SPY-1D transmitter fault that the FC3 documented as "BIT returns fault code, replaced LRU, fault recurred" — that one comes to you. You pull the NAVSEA technical manual section for the transmitter assembly, read the fault isolation procedure from the top rather than from where the FC3 stopped, and follow the branching logic to the actual root cause rather than the symptom. The corrective action entry you write names the component, the fault code, the isolation procedure steps, the corrective action authorized under your maintenance level, and the post-action BIT result. The QA inspector who reviews your documentation should be able to reconstruct your diagnosis from what you wrote without calling you. That standard is what separates the FC2 whose section never generates QA trending concerns from the FC2 who finds out about a trend at the Type Commander assessment. The combat systems watch at FC2 on a DDG is not the apprentice watch. You are standing the Anti-Air Warfare Coordinator (ATAWC) or a senior CIC console position at the speed the Tactical Action Officer expects, managing the tactical air picture during fleet exercises and actual operations, and operating the AEGIS combat system in degraded mode when the primary tracking chain faults — because you know the degraded modes before the TAO asks. On a ship in a major fleet exercise or a real-world contingency, the FC2 at the ATAWC console is the technical voice the TAO is relying on for system status calls. You do not learn that job during the evolution. Mentoring is the part of the FC2 job that nobody fully explains before you pick up the crow. The FC3s in your section are building their professional standards off what they watch you do — the same way you watched the FC2 above you. The FC2 who runs clean fault isolation is the floor; the FC2 who also builds the FC3 below him into a sailor who can run clean fault isolation without the FC2 at his shoulder is the one the LCPO is watching for the LPO recommendation. Walking an FC3 through the PQS line items the right way — demonstrating the evolution, verifying the FC3 can perform it independently, signing only when the demonstration meets the standard — is not overhead. It is the main product of the FC2 rank. The NWAE for FC1 is not abstract. The Final Multiple Score at the FC1 advancement level is a competitive number, and the exam score component is the most controllable variable. Pull the current BIB from MyNavyHR and build a documented daily study plan with milestones — not a 'I will study when the tempo allows' intention. The FC2 who walks into the FC1 cycle with eight months of documented study, an EP eEVAL ranking, an NEC in awarded status, and a Surface Warfare device on the blouse has a structural FMS advantage the peer without those components cannot close at exam time. The advanced NEC stack is also live at FC2: the NEC you developed at FC3 or at C-school is the foundation, and the question now is whether a second NEC or an advanced C-school builds the billet access and the civilian market profile the FC2 is going to need in the next chapter of the career, whether that chapter is at FC1 or post-Navy.
Career Arc
  • 01FC2 pin-on: section maintenance authority formalized, FC3 documentation review responsibility assumed, PQS line-item witness authority for FC3s and FCSNs.
  • 02ATAWC or senior CIC console qualification current and standing; the TAO names the FC2 at the watch station, not the watchbill number.
  • 03Complex fault isolation ownership: first three write-ups diagnosed from scratch using the NAVSEA technical manual fault isolation procedure — not the abbreviated version the FC3 tried.
  • 04Section QA rework rate at or below command average; LPO can name the FC3s under the FC2 as sailors who manage their own documentation.
  • 05NWAE for FC1: BIB pulled from current cycle, study log documented and current, LPO briefed on progress at monthly counseling before the advancement window closes.
  • 06Advanced NEC or second C-school in conversation with LCPO; Navy COOL credential (FCC GROL completed or in final exam stage) on the eEVAL bullet.
  • 07Surface Warfare device pinned; Chief Petty Officer board eligibility timeline discussed with LCPO — the FC2 who has the first conversation about the Chief packet before the LCPO brings it up is the FC2 the chief is watching.
Common Screwups
  • ×Rubber-stamping FC3 maintenance documentation without actually reading it. The FC2's initials on the pre-QA review are a professional representation that the documentation is correct. The QA inspector who finds the error on a closed MRC after the FC2 signed it does not distinguish between the FC3's mistake and the FC2's failure to catch it — the trend lands under the FC2's name at the Type Commander assessment, and the LCPO's eEVAL input reflects the section's rework rate, not just the FC3's.
  • ×Going around the LCPO to the Combat Systems Officer. The combat systems leadership chain runs through the chief; the Command Master Chief hears about it the same watch rotation it happens. One documented instance of bypassing the LCPO to get a result from the CSO tells the goat locker everything it needs to know about whether this FC2 is Chief-material. The Chief board packet feels it at the next ranking.
  • ×NJP or DUI at FC2. The career impact at this rank is immediate and cumulative: advancement flag, eEVAL damage, NEC pipeline freeze, clearance review, section leadership credibility with the FC3s destroyed — and a small-community surface warfare ship where every FC in the department knows the story by the next working day.
  • ×Fraudulent 3-M documentation — signing off a corrective action you did not personally review, or reviewing FC3 documentation so cursorily that you are signing for work you cannot vouch for. The JAGMAN investigation that follows a fraudulent maintenance record on a surface combatant's weapons system names every signature in the chain. The FC2 who signed the pre-QA review is in the chain.
  • ×Letting the NWAE for FC1 become a background concern while the FC2 section runs hot. The advancement slate is tied to a fixed calendar, not to when the deployment workup ends. The FC2 who enters the FC1 cycle without a documented study log is competing against FC2s who built the study habit across the entire FC2 tenure.

A Day in the Life

  • 0530Wake up, check the ship's maintenance management system or any overnight watch report for combat systems write-ups that need the FC2's attention at quarters — a radar fault from a 2AM BIT cycle, a VLS inhibit from an overnight pre-fire check. These are the write-ups the CSO may ask about at the 0800 CSMMB sync.
  • 0600PT formation. The FC2 sets the section's PT standard by showing up and finishing strong, not by falling out or fading at the back. Surface warfare PT on the flight deck or pier is a department-visible event.
  • 0700Post-PT hygiene, chow, utilities on. Review the section's PMS schedule for the day: which MRCs are assigned to FC3s, which require the FC2's witness or authorization level, which require specific system-readiness conditions. Pull the calibration sub-account status — check for anything coming due in the next 30 days.
  • 0800Quarters. FC2-level information includes not just the day's PMS assignments but the combat systems readiness brief input — system availability status, deferred maintenance status, any new write-ups that affect the CSMMB metrics. Take notes and note which FC3 is assigned to which action.
  • 0830Pre-PMS walk of the work center. Verify the FC3s have the correct MRC cards for their assigned actions, that calibrated test equipment is powered on and within calibration for any MRCs requiring measurements, and that any classified documentation for the day's actions is properly signed out. The five-minute pre-PMS walk prevents the three-hour mid-evolution problem.
  • 0900PMS execution block. FC2 manages the section: witness FC3 evolutions that require FC2-level authorization, run independent fault isolation on complex write-ups, review and correct in-progress documentation before it becomes a QA return. The FC2 who is running his own maintenance while also supervising FC3s is managing a production floor, not a single workbench.
  • 1130Pre-chow sub-account check: every tool signed in, calibrated test sets accounted for, no active 3-M actions left mid-execution without a documented status. Brief the FC3s on afternoon assignments before chow.
  • 1300Afternoon block: FC3 PQS line-item demonstrations if the system evolution schedule allows; 3-M documentation review and QA submission for completed morning actions; NWAE study if production pace permits. The FC2 who builds the study habit in the afternoon production block is the FC2 whose daily study log is documented across the deployment.
  • 1500NWAE study: 45-60 minutes, documented in the study log. FC1 advancement cycle is a fixed calendar competition — the FC2 who builds the daily habit now is structurally ahead of the one who plans to study when the tempo allows.
  • 1600End-of-day accountability: all tools signed in, calibrated test sets powered down and logged, classified documentation secured, open 3-M discrepancy statuses updated. Brief the LCPO on section status before end of day — if anything in the section is not where it should be, the LCPO hears it from you, not from the morning's CSMMB brief.
  • 1700Released on non-duty days. If on duty, stand the assigned CIC combat systems watch. FCC GROL prep or Navy COOL portal review for advanced NEC credentialing on personal time — the FC2 who completes a civilian credential before FC1 pin-on has a post-Navy market profile that starts building now.
  • 2000Review next day's PMS schedule and flag any MRCs that require the FC2 to arrange a system-readiness condition or a specific supporting party. The FC2 who shows up at morning quarters with the next day's production already planned is the one the LCPO stops pre-planning for.
  • 2200Lights out. Deployment workup and underway operations extend every block — the FC2 who runs a clean section in port maintains the same standard underway, not because the rhythm stays the same, but because the habits hold under pressure.

Weekly Cadence

The shore-based week at FC2 is structured around the PMS cycle and the combat systems readiness reporting cadence. Monday is the planning day: the week's MRC assignments come off the ship's maintenance management system after weekend stand-down, any write-ups from weekend operations are in the 3-M queue, and the FC2's section accountability — calibration sub-account, classified documentation, FC3 PQS status — is reconciled at the start of the week, not at the end. The FC2 who shows up Monday with Friday's sub-account already closed and the FC3 training status already updated is the one the LCPO can skip in the morning planning conversation because the section is already self-managing. Tuesday through Thursday are the production core. PMS execution runs in the morning block; the FC2 divides time between independent fault isolation work, FC3 documentation review, and PQS witness demonstrations. The CSMMB reporting input for the combat systems readiness brief is built from real-time data across the production week — the FC2 who tracks the section's PMS completion rate and deferred maintenance count in real time never scrambles to produce accurate numbers at the weekly brief. Thursday typically carries a department-level maintenance sync or a QA trend review where the section's rework data is visible — the FC2 whose section is below the command average is the one the LCPO points to as the standard at that brief. Friday is close-out: PMS completions reconciled, calibration due-dates flagged for the coming weeks, open write-ups status-updated, and the monthly counseling input prepared for the LCPO meeting. The FC2 who brings a section training status update, a calibration sub-account status, and a NWAE study log update to the monthly counseling is delivering the three data points the LCPO needs to write the eEVAL input. Deployed operations and workup cycles compress this rhythm — the watch rotation and maintenance production cycle define the week rather than a fixed calendar. The difference between the FC2 who thrives in that environment and the one who loses ground is the documentation and calibration discipline that was built in garrison. Deployed habit equals garrison habit under pressure.

Key Skills — How to Drill Each

  1. 01
    Own a complex combat system fault from 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 — system back in readiness status and 3-M documentation closing QA-clean before the next evolution.
    The complex fault isolation starts at the NAVSEA technical manual section for the system and the specific fault code or symptom — not at the LRU shelf. Read the full fault isolation procedure before touching the hardware; the branching logic at step 3 may determine that the root cause is not the component the FC3 initially suspected. Document each isolation step as completed and the result observed so that the corrective action entry reconstructs the diagnostic path without requiring a verbal explanation. The post-action BIT result is documented before closing the discrepancy — the 3-M system does not accept a corrective action that has no BIT verification, and the QA inspector who asks 'how do you know the fix worked' deserves an answer that is in the documentation. The FC2 who can do this on a major AEGIS system component without calling the LCPO in for technical backup is the FC2 the combat systems officer trusts to run the section unsupervised.
  2. 02
    Review 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.
    The pre-QA review is not a signature ritual. Read the corrective action entry against the MRC procedure: does the description match the work performed, is the technical reference correct, is the post-action BIT result documented, is the WUC and job sequence number accurate. When you find an error, explain to the FC3 what the specific provision requires and why — not just 'fix this.' The FC3 who understands why the documentation standard exists is the one who stops making the same type of error. The FC3 who gets corrections without explanation continues making the same error in different formats. Your rework rate is the section's rework rate; building the FC3's documentation skill is the only sustainable way to maintain a clean rate.
  3. 03
    Brief a combat system discrepancy to the Combat Systems Officer or Weapons Officer — what the system was doing, what the fault indicates, what the fix timeline is, and what the backup mode is in the interim.
    The CSO brief is a decision-support product, not a technical monologue. The officer who receives the brief needs to answer: can the ship conduct the scheduled mission profile with this system in its current condition, what is the timeline to restoration of full capability, and what backup mode is available if restoration takes longer than expected. Translate the technical fault into operational terms: 'the Mk 99 FCS tracking loop has a fault that puts it in degraded mode — backup tracking is available through the backup fire control mode, and the expected restoration timeline from the fault isolation underway is four hours, assuming the replacement module is in the spares locker.' That brief takes ninety seconds and gives the CSO everything he needs to advise the TAO. The FC2 who walks in and starts with fault codes and technical manual references has already lost the room.
  4. 04
    Run a section training plan that keeps FC3s progressing on PQS, NWAE study, and practical proficiency without requiring the LCPO to supervise every milestone.
    Build the training plan at the section level: for each FC3, know their current PQS line-item completion status, their NWAE BIB study progress, and their practical qualification gaps. Put the plan on a calendar with specific milestones — not a 'we will get to it' intention — and bring the section training status to the monthly counseling with the LCPO before the LCPO asks. The FC3s under you should be visibly ahead of the peer cohort in PQS completion and NWAE study progress — that is the visible evidence the LCPO uses to describe the section's training production at the department head's readiness brief. The FC2 who lets a FC3's PQS stall for two months without intervening is leaving the section's training output on the LCPO's plate.

Manuals & References — What Chapters Matter

  • OPNAVINST 4790.4 series — Ships' 3-M Systems Procedures Manual
    At FC2 you enforce the 3-M QA provisions your FC3s execute inside, which means knowing the QA sections at the level the quality assurance division uses them — not just the sections your own maintenance actions fall under. When you return an FC3's documentation for rework, you should be able to name the specific OPNAVINST 4790.4 provision the entry violated, not just that it 'looks wrong.' The QA inspector who audits the section's documentation asks the FC2 to explain the correction, not the FC3.
  • NAVSEA technical manuals for your ship's AEGIS combat system components (SPY-1D or SPY-6, Mk 99 FCS, Mk 41 VLS, CIWS Mk 15)
    At FC2 you own the technical content of the fault isolation procedures for your work center's systems — you are the senior technician the FC3 calls when the fault isolation procedure branches to a step beyond the FC3's authorization level. Know the fault isolation sections for the three systems you are most likely to be called on: where the fault tree branches, what the symptom-to-component mapping looks like, and what the authorized corrective action is at your maintenance level versus what requires NAVSEA authorization. The FC2 who can navigate the technical manual fault isolation for the primary systems in the section without asking the LCPO is the technical authority the CSO signs behind.
  • Combat Systems Readiness Manual (CSRM) for your hull
    The CSRM governs the combat systems maintenance management board (CSMMB) reporting metrics the FC2 contributes to, the CIC watchstanding procedures at the ATAWC level, and the casualty response procedures the FC2 briefs to the CSO. At FC2 the CSRM is the governance document you execute against, not just the document the LCPO quotes at weekly briefs. Know the PMS completion rate calculation, the system availability metric definition, and the deferred maintenance reporting threshold — because the CSO asks those questions with the FC2 in the room.
  • NAVPERS 18068 Vol II + current NEC source-rating NAVADMIN
    At FC2 you are mentoring FC3s through their NEC pipeline conversations. The advice you give must come from the current source-rating NAVADMIN — not from memory of your own NEC conversation three years ago. Pull the current NAVADMIN before any NEC counseling session so the pipeline information you give is accurate for this cycle. An FC3 who acts on NEC advice you gave from a superseded NAVADMIN and misses a pipeline window because the eligibility criteria changed will remember whose advice they followed.

Standards — How to Hit Each

  • Section QA rework rate at or below command average — FC2's name is on the documentation the FC3s produce after the pre-QA review.
    Track the section's rework rate yourself — do not wait for the QA division to produce the trend report. Every time a closed 3-M action comes back from QA, document the specific provision violated, the correction made, and the root-cause habit the FC3 needs to change. If the same type of error comes back twice from the same FC3, the next correction is a documented counseling entry, not just a re-do. The QA trend report the Type Commander uses at the assessment is built from the same data you can see in real time — the FC2 who sees the trend forming and intervenes early never shows up on the assessment finding.
  • NWAE for FC1 prep: study log documented and current, BIB pulled from the current cycle, LPO briefed on progress at monthly counseling.
    Pull the current BIB from MyNavyHR the week it publishes for the current cycle. Set a study calendar with specific daily section targets — 45-60 minutes, documented by date and section covered. Bring the log to the monthly counseling with the LCPO. The FMS at the FC1 advancement level is a real competition: the FC2 who can show the LCPO a dated study log the LCPO can defend at the advancement worksheet review has a structural advantage. The FC2 who says 'I have been reviewing the material' and cannot produce a log is the FC2 whose advancement worksheet review includes a question mark.
  • NEC awarded or current, advanced NEC in conversation with LCPO; Surface Warfare device pinned and current.
    The NEC you developed at FC3 is the foundation. At FC2 the question is whether a second advanced NEC or a follow-on C-school builds the billet access and civilian market profile you will need in the next chapter — whether that chapter is at FC1 or post-Navy. Bring that conversation to the LCPO with the current source-rating NAVADMIN already read: here are the NECs I have, here is what the NAVADMIN says about the next logical C-school, here is how I think it maps to the billets I want at FC1. The LCPO who receives a prepared pipeline conversation can act on it. The LCPO who receives a vague 'what should I do next' conversation will give you the standard counseling instead of the honest one.
  • eEVAL trait average and ranking supporting EP or MP recommendation; LCPO knows the FC2's standing before the evaluation board opens.
    The eEVAL ranking is set by cumulative record across the period — section QA rework rate, FC3 PQS production, NWAE study progress, NEC pipeline activity, watch qualification current, warfare device on the blouse, and zero integrity incidents. Talk to the LCPO at every monthly counseling about ranking position relative to peers. Do not be surprised by the eEVAL outcome — ask the LCPO directly where you stand in the section ranking at the midpoint of the evaluation period and at the end. The FC2 who is surprised by the evaluation outcome was not having the counseling conversation.

Technical Mistakes — Concrete Consequences

  • Rubber-stamping FC3 documentation without actually reading it — initialing the pre-QA review as a signature ritual rather than a substantive review.
    The QA inspector finds the error on the closed discrepancy and the trending report shows the work center's rework rate climbing under the FC2's section. The FC2's initials are on the reviewed documentation; the finding is under the FC2's name at the Type Commander assessment, not the FC3's. More consequentially, the FC3 who submits an error that the FC2 should have caught has learned that the pre-QA review is procedural, not substantive — and the next submission has the same error. The section's documentation standard is exactly what the FC2 enforces by actually reviewing, not by initialing.
  • Chasing an AEGIS combat system fault with LRU replacement instead of fault isolation procedure — replacing components until the symptom stops.
    An LRU-swapped 'fix' that does not trace back to a documented fault isolation procedure creates a supply system problem and a quality assurance problem simultaneously. The removed LRU goes to the depot, passes NFF, and returns to the shelf. The symptom recurs at the next exercise because the root cause component was never correctly identified. The combat systems readiness brief now has a trending fault the CSO is asking about, the supply officer is asking about the NFF return, and the QA division is asking who ran the fault isolation. The FC2 whose section is generating NFF returns and recurring faults for the same system is the FC2 the LCPO has a different conversation with.
  • Working outside maintenance authorization level on an AEGIS subsystem because the FC2 is confident in the diagnosis.
    The authorization chain on a surface combatant's AEGIS combat system exists because the system has cascading dependencies — an authorized adjustment to one subsystem can require coordinated action across the fire control computing environment, the radar alignment, and the engagement software that only the NAVSEA technical authority can sanction. The Type Commander and NAVSEA both ask who authorized the work when the casualty board convenes after an unauthorized modification produces a system behavior change. The FC2's confidence in the diagnosis does not transfer legal responsibility off the technician who executed the unauthorized action.
  • Letting calibration slip on work center test equipment because the ship is deployed and the depot turnaround is slow.
    Out-of-cal test equipment contaminates every measurement the section produced since the last valid calibration date. The QA review of the contaminated period requires reopening every closed maintenance action that involved a measurement from the out-of-cal set — a workload that falls on the FC2's section and surfaces under the FC2's name at the ISIC maintenance assessment. Build phone reminders at 90 days before each due date, establish a routing protocol with the calibration lab or tender, and hand the LCPO a calibration schedule rather than a surprise finding.
  • Going around the LCPO to the Combat Systems Officer or the Weapons Officer on a section issue.
    The combat systems leadership chain runs through the chief; the Command Master Chief hears about a bypass the same watch rotation it happens. The goat locker discusses it. The CSO and the Weapons Officer, who were the recipients of the bypass, note it. The FC2's Chief packet — which the LCPO is building or will be building — reflects whether the FC2 understands how the chain is supposed to work. One documented bypass tells the goat locker what it needs to know about whether this FC2 is ready to be a Chief.

Career Decisions at This Rank

  • FC1 advancement cycle — FMS building strategy and whether the section record supports EP recommendation
    The FC1 advancement slate is smaller than the FC2 slate and the pool of competitors includes every FC2 in the competitive group who has been building the FMS components across their FC2 tenure. The exam score is the most controllable variable — the FC2 who has a documented daily study log across eight months enters the NWAE with a structural advantage the last-month crammer cannot close. The eEVAL component is the second most controllable: the section QA rework rate, the FC3 PQS production, the warfare device, the NEC status, and the monthly counseling record all feed the eEVAL input the LCPO writes. The FC2 who has been having the monthly counseling conversation about ranking position is never surprised by the eEVAL outcome — and the eEVAL that is not a surprise is the eEVAL the FC2 can make accurate decisions from. If the ranking is not EP-competitive, the FC2 who knows that fact six months before the evaluation board opens has six months to change it.
  • Advanced NEC or second C-school — deepen the current track or broaden to a second pipeline
    The NEC decision at FC2 is more strategic than the FC3 decision because the billet market for FC1 and FCC is defined by NEC-coded positions. An advanced NEC in the same track deepens the expertise and improves the billet match at the senior end of the sea tour cycle — the SPY-6 AMDR advanced C-school, for example, builds toward the NAVSEA program office billets and the Type Commander staff positions that flow from the AEGIS modernization program. A second NEC in a complementary track — fire control combined with radar, or VLS combined with CIWS — broadens the billet access and builds the multi-system technical profile that defense contractors value in post-service hiring. The honest analysis requires pulling the current source-rating NAVADMIN and reading the actual billet demand numbers for each NEC, not the mess deck impression of which pipeline has the best reputation.
  • Chief Petty Officer board preparation — start now or wait until FC1
    The answer is start now. The Chief board evaluates the entire service record across the FC2 and FC1 tenure, not just the FC1 eEVAL. The FC2 who starts the Chief packet conversation with the LCPO at FC2 is the FC2 who is building the record consciously across the entire period. The specific components — eEVAL profile, warfare device status, NEC pipeline, awards, community involvement — are year-round accumulation, not a semester of work before submission. The FC2 who has the conversation late may find that a two-year gap in community involvement or an undone warfare qualification requires a patch that takes longer than the timeline allows. The LCPO who receives 'I want to be a Chief' from an FC2 who has been demonstrating Chief-level work for two years has a different packet to write than the LCPO who receives the same statement from an FC2 who has not been building the record.

How the Seat Varies by Unit Type

  • DDG-51 Arleigh Burke (AEGIS SPY-1D/SPY-6)
    The Arleigh Burke at FC2 is where the full weight of the combat systems section leadership lands. The deployment cycle on a DDG is real — 7-9 months with a 6-12 month workup before the ship leaves. At FC2 on a DDG you are running the section through the workup phase (where every subsystem gets tested against fleet readiness standards), the deployment (where the maintenance tempo runs at maximum), and the post-deployment maintenance period (where deferred work comes due). The FC2 who built strong documentation and calibration discipline during workup maintains it through deployment without degradation. The FC2 who was cutting corners during workup finds the deployment tempo exposes every gap.
  • CG-47 Ticonderoga cruiser (AEGIS-equipped)
    The Ticonderoga at FC2 carries a larger combat systems department than the DDG with a slightly bigger FC section. The AEGIS architecture is the same philosophy, and the 3-M maintenance program runs under OPNAVINST 4790.4 identically. The cruiser's older AEGIS baseline means the FC2 is working with legacy hardware in some cases — the fault isolation experience on older SPY-1A/B components builds a deep system understanding that SPY-6 AMDR hardware knowledge supplements rather than replaces. The larger department size also means more FC3 and FCSN development responsibility for the FC2, and the LCPO section is managing a bigger people picture at the counseling level.
  • LCS (different combat systems, smaller crew)
    An LCS assignment at FC2 means a smaller crew with broader individual accountability and a combat systems suite that varies by mission module rather than the standardized AEGIS architecture. The FC2 on an LCS runs the section with fewer bodies and takes on maintenance responsibility that would be distributed across more technicians on a DDG. The tradeoff is that the AEGIS-specific depth the NEC market values most highly is thinner on an LCS — the FC2 who plans to transition to defense contractor AEGIS support work needs the sea tour record that shows deep AEGIS system maintenance experience. An LCS tour can provide excellent leadership development at the FC2 level while building a resume that the hiring manager for an AEGIS program support position needs supplemented.
  • NAVSEA/TYCOM shore staff billet
    A NAVSEA or Type Commander shore staff billet at FC2 provides exposure to surface warfare maintenance policy, AEGIS program management, and fleet-level readiness reporting at the level that informs every ship's combat systems program. The FC2 at a staff billet is seeing how Type Commander assessments are built, how NEC programming decisions are made, and how the AEGIS baseline modernization program affects the ships in the fleet. The tradeoff is hands-on technical depth: the peer who was on a DDG the same period has more fault isolation hours and a more competitive deployment record at the FC1 advancement cycle. Come back from the staff tour with a professional relationship network and a career counseling perspective the sea-tour peer does not have.
  • ASHORE: FRS/schoolhouse instructor at Dam Neck
    The NTTC Dam Neck FC rate instructor tour at FC2 is a significant credential — teaching AEGIS combat systems content to A-school students and C-school pipeline students requires the depth of understanding that only the fleet maintenance experience provides, and the instructional skill built in a schoolhouse environment is distinct from the watchstanding and maintenance skill the fleet builds. The eEVAL in the schoolhouse reflects instructional contribution, student completion rates, and curriculum improvement rather than ship-level metrics. Come back from the instructor tour with a completed FCC GROL, a Navy COOL credential stack, and an NWAE study program that used the stable shore schedule to its full advantage — and the peer who was on a DDG the same period will not be ahead of you at the FC1 advancement worksheet review.

What Good Looks Like at This Rank

The good FC2 is the technician the Combat Systems Officer calls when the SPY radar writes up a fault two hours before an AEGIS readiness event and the clock is running. He goes to the NAVSEA technical manual fault isolation section for that specific transmitter assembly fault code, reads the procedure from the top, and follows the branching logic to a call he can document with supporting evidence — not a call based on what the last fault isolation of a similar symptom turned out to be. His corrective action entry is specific enough that the QA inspector can reconstruct the diagnosis from the documentation without calling him. The discrepancy closes clean. The system is back in full readiness status with a real fix, or it is correctly reported degraded with a documented backup mode and a realistic restoration timeline the CSO can brief to the TAO. His FC3s are visible to the LCPO for the right reasons: their PQS line items are progressing because the FC2 identified which ones were ready and scheduled the witness demonstrations rather than waiting for the FC3 to ask. Their 3-M documentation comes through his pre-QA review and into QA without a return because the FC2 reviewed the documentation substantively — and when an error came back, the explanation the FC2 gave the FC3 addressed the root cause, not just the specific entry. The section's QA rework rate has been below the command average for two consecutive quarters. The LCPO named it at the last combat systems department brief without being asked. His NWAE study log is a dated record spanning the last eight months, sitting on the shelf in his berthing and available to show the LCPO at any counseling. The log covers the current BIB sections with documented daily duration — not a set of sticky notes and a half-read PDF. He is not surprised by his eEVAL ranking because he asked the LCPO directly at the midpoint counseling where he stood relative to the peer FC2s in the section, and the answer was specific enough to act on. His FCC GROL is complete. His NEC is awarded. His Surface Warfare device is on the blouse. The Chief packet conversation started three months ago when the FC2 brought it up, not when the LCPO did. That is the FC2 the LCPO is building the recommendation letter around.

Preview — The Next Rank

FC1 (E-6) is the LPO. When you put on the chevrons of a First Class Petty Officer in the FC rate, the combat systems work center section is yours — not as a delegated area of responsibility, but as the seat the Combat Systems Officer and the LCPO hold you accountable for at the weekly CSMMB brief. The FC2 was the senior technician the FC3 called for complex fault isolation; the FC1 is the senior technical voice the CSO calls before calling the chief. The eEVALs you write as FC1 for FC2s and FC3s are the eEVALs that determine who competes on the next advancement slates — and the FC1 whose eEVAL writing is honest and specific is the FC1 the LCPO trusts to run the section without daily check-ins. The Chief board becomes a concrete timeline, not a distant aspiration. The FC1 who arrives at the Chief selection board with a record that reads itself — eEVAL profile that is EP or MP consistently, NEC awarded and current, Surface Warfare device on the blouse, no integrity gaps, a pipeline that produced NEC holders and credentialed sailors at FC2 and FC3 — is the FC1 the board promotes. The FC1 who arrives at the Chief board with gaps in the record that require explanation is competing against sailors who did not have the gaps. Start building the Chief board record the day you pick up FC1. What you cannot fully see from FC2 is how much the FC1 job is about the combat systems readiness narrative rather than individual fault isolation. The FC2 runs a fault. The FC1 runs the section's readiness metrics and the CSMMB brief and the section's role in the ship's overall combat readiness posture. The transition from doing the work to owning the section's outcome is the real change between FC2 and FC1 — and the FC2 who already runs his section like an FC1, without the LCPO having to track the milestones, is the FC2 the chief is watching for that promotion.
FAQ

FC E5 — Frequently Asked Questions

Q01What does a E5 FC (Fire Controlman) actually do?
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.
Q02What's the most important thing to know as a E5 FC?
FC2 (E-5): you are the working senior tech and the de facto LPO of your work center section whether the watchbill says so yet or not.
Q03What does a typical day look like for a E5 FC?
Time-blocked day at the E5 FC rank tier: 0530 Wake up, check the ship's maintenance management system or any overnight watch report for combat systems write-ups that need the FC2's attention at quarters — a radar fault from a 2AM BIT cycle, a VLS inhibit from an overnight pre-fire check. These are the write-ups the CSO may ask about at the 0800 CSMMB sync, 0600 PT formation. The FC2 sets the section's PT standard by showing up and finishing strong, not by falling out or fading at the back. Surface warfare PT on the flight deck or pier is a department-visible event, 0700 Post-PT hygiene,…
Q04What mistakes get E5 FC soldiers fired or relieved?
Rubber-stamping FC3 maintenance documentation without actually reading it. The FC2's initials on the pre-QA review are a professional representation that the documentation is correct. The QA inspector who finds the error on a closed MRC after the FC2 signed it does not distinguish between the FC3's mistake and the FC2's failure to catch it — the trend lands under the FC2's name at the Type Commander assessment, and the LCPO's eEVAL input reflects the section's rework rate, not just the FC3's;…
Q05What career decisions matter most at the E5 FC rank tier?
FC1 advancement cycle — FMS building strategy and whether the section record supports EP recommendation — The FC1 advancement slate is smaller than the FC2 slate and the pool of competitors includes every FC2 in the competitive group who has been building the FMS components across their FC2 tenure. The exam score is the most controllable variable — the FC2 who has a documented daily study log across eight months enters the NWAE with a structural advantage the last-month crammer cannot close. The eEVAL component is the second most controllable: the section QA rework rate,…
Q06What's next after E5 for a FC (Fire Controlman) in the Navy?
FC1 (E-6) is the LPO.
Q07What manuals and regulations does a E5 FC need to know cold?
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.

Based on 14 tips from 0 contributors

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