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
FCE4

Fire Controlman

E-4 (Specialist/Corporal) · Navy

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

FC3 (E-4): the crow means the QA inspector holds your 3-M documentation to a technician standard, not an apprentice standard. You own a section of the combat systems maintenance bill and the FC2 is reviewing your work — not running it for you. The C-school and NEC direction conversation is now serious: pull the current NEC source-rating NAVADMIN before quoting any specific code to your LCPO or your career counselor.

The Honest MOS Read
You are a Petty Officer Third Class on an AEGIS-equipped surface combatant. The crow changed the job. The FCSN was learning how maintenance worked and watching the FC2 do the hard call; the FC3 is the technician who does the maintenance, makes the call, documents the call, and puts the signature on the corrective action entry that the QA inspector then reviews as a professional product. The FC2 is still there — as a supervisor, a reviewer, and the senior technical authority when the fault is above your authorization level — but the daily maintenance execution at your work center section is yours. The seat at FC3 on a DDG-51 Arleigh Burke or CG-47 Ticonderoga depends on your NEC track, but the maintenance program structure is the same regardless: you execute Planned Maintenance System (PMS) Maintenance Requirement Cards on the combat systems components in your assigned work center section — AN/SPY-1D or AN/SPY-6 radar components, Mk 99 Fire Control System assemblies, Mk 41 VLS cells and launcher equipment, CIWS Mk 15 systems, or AEGIS computing hardware — and you document every action in the ship's 3-M system in accordance with OPNAVINST 4790.4. The MRC tells you what to do. Your job is to follow it without skipping steps, document it without ambiguity, and get it past QA without a return-for-rework. A zero-rework rate is the FC3 maintenance standard the LCPO is grading against. In CIC, FC3 is the qualified watchstander. Your combat systems watch qualification is signed; the watch supervisor does not correct you for basic procedure errors because you do not make them. On a ship conducting a major fleet exercise or a deployment workup, the CIC picture is live and the Tactical Action Officer is not distinguishing between the FC3's first exercise watch and his fortieth. The contact reporting, track management, system status reporting, and degraded-mode responses you practiced in the PQS process are the responses you execute under real time pressure. The FC3 who treats every exercise watch like the actual evaluation is the one the TAO calls by name when the real casualty happens. The fault reporting responsibility at FC3 is the technical skill that separates the FC3 the LPO trusts from the FC3 the LPO micro-manages. When a combat system component writes up a fault — a radar transmitter BIT failure, a Mk 99 tracking loop fault, a VLS cell inhibit — the FC3's job is to identify the fault at the component level, report it to the FC2 with the correct technical language and the correct maintenance chain, and document the fault report in the 3-M system before the watch supervisor asks. Not after. The FC3 who catches a combat system discrepancy and has the preliminary fault report in the 3-M system before the FC2 arrives is the FC3 the ship runs on. The C-school and NEC pipeline decision is no longer theoretical at FC3. The detailing system is not waiting for you to decide — billets are filled by sailors who have submitted packets, and the sailor who has not submitted a packet gets the billet the Navy needs filled. Pull the current NEC source-rating NAVADMIN from MyNavyHR, identify the one or two FC-series NECs that make sense for your work center assignment and your longer-term interest, and bring that conversation to the LCPO at the next monthly counseling with the NAVADMIN already read. The FC3 who walks in having done that preparation gets a productive conversation. The FC3 who walks in saying "I heard there was a C-school for the SPY radar" gets the version of that conversation that does not help him. Navy COOL is funding FCC General Radiotelephone Operator License exams and electronics certifications right now. The FCC GROL study material overlaps with the NWAE BIB content — particularly the radio communications and electronics theory sections. Forty-five minutes of GROL study is forty-five minutes of NWAE study. The FC3 who completes the GROL before the FC2 advancement cycle closes has a credential the civilian electronics market recognizes alongside the eEVAL bullet the LCPO writes. Neither requires waiting for shore duty to pursue.
Career Arc
  • 01FC3 pin-on: work center section assignment formalized, 3-M documentation signed as technician-of-record — QA holds the standard from day one of the crow.
  • 02CIC watch qualification current and standing at the assigned console without supervision; watchbill contribution visible to the combat systems department at the section level.
  • 03Fault reporting skill: first three combat system component fault reports submitted to the 3-M system with correct technical language, correct maintenance chain notification, and QA-clean documentation.
  • 04NWAE for FC2: BIB pulled from current cycle, study plan documented, LPO briefed on progress at monthly counseling before the advancement window closes.
  • 05NEC pipeline packet in conversation with LCPO and career counselor; current NEC source-rating NAVADMIN read before any specific code is quoted.
  • 06Surface Warfare device (SW) qualification in progress; PQS submission timeline discussed with the senior FC at the first opportunity.
  • 07FCC GROL exam pursued through Navy COOL funding or personal study; eEVAL bullet documenting credentialing progress visible by the FC2 advancement cycle.
Common Screwups
  • ×Fraudulent 3-M maintenance entry — signing off a corrective action that was not personally performed or directly observed. One documented instance of fraudulent maintenance documentation at FC3 is a JAGMAN investigation. The investigation names every technician in the documentation chain. 'The FC2 told me it was done' is not a defense the UCMJ accepts, and post-service background checks and clearance renewals both surface JAGMAN findings.
  • ×NJP or DUI. At FC3 the career consequences stack: advancement flag, eEVAL damage, NEC pipeline closed, clearance review opened. An alcohol-related NJP on a surface combatant is the single most common career-ending event in the FC rate at this tier, and the community on a DDG is small enough that every FC in the ship knows the story.
  • ×A documented security violation — mishandled classified combat systems documentation, unescorted CIC access, OPSEC-relevant social media post. The commanding officer of a surface combatant does not accept 'I didn't realize' for a classified space violation. The investigation is in the record and clearance renewal boards read the record.
  • ×Incomplete MRC execution on a safety-critical combat system component — closing the maintenance action with steps skipped because the evolution seemed routine. The incomplete action exists on the equipment. The next casualty traces back to the last maintenance action and the last signature.
  • ×Missing the FC2 advancement slate because the NWAE preparation was treated as background noise. The Final Multiple Score is a fixed competition — every FC3 who is building the study habit consistently is taking FMS advantage from the FC3 who is not. Missing a slate is not a temporary setback; it pushes the entire advancement timeline and the NEC billet access that follows.

A Day in the Life

  • 0530Wake up. Check the ship's maintenance management system for any overnight write-ups that affect the work center's morning evolution — a VLS inhibit, a SPY BIT fault on an overnight system watch, a CIWS self-test anomaly. These are the write-ups the FC2 will ask about at 0800 quarters.
  • 0600PT formation on the pier or the flight deck. Surface warfare PT is visible — the combat systems department head can see the flight deck formation from the bridge wing. Run days are the days to run strong, not to pace yourself to the back of the pack.
  • 0700Post-PT hygiene, chow, utilities on. Pre-quarters review: pull the MRC cards for today's scheduled PMS actions in the work center, check calibrated test equipment due dates against the sub-account log, review any overnight write-ups against the technical manual fault codes.
  • 0800Quarters. LCPO puts out the plan of the day. FC3-level assignments come from the FC2: work center PMS actions, CIC watchbill slots, any training evolutions. Note the assignments and the timing requirements for each.
  • 0830Work center clean-up and pre-PMS equipment verification. Any calibrated test set required for the day's MRCs is powered on and verified against the calibration log before the MRC starts. The FC3 who starts an MRC and discovers mid-step that the test set is out of cal is the FC3 who has to stop the evolution and explain to the FC2 why.
  • 0930PMS execution block. Run the assigned MRCs on the combat systems components in the work center section — step by step, MRC card in hand, every step logged as completed. Post-action BIT verification documented before submitting to 3-M. Document completed before end of the morning block, not at end of day.
  • 1130Chow. Sub-account tool check before stepping away — every calibrated test tool accounted for and signed in. The FC3 who leaves a calibrated test set unsigned out on a chow break is the subject of the afternoon accountability drill and the FC2's counseling note.
  • 1300Afternoon block: CIC watch qualification stand or combat systems training evolution if on the watchbill; otherwise continuation of PMS execution or 3-M documentation completion and QA submission. NWAE study during any production downtime — BIB section for the day, documented in the study log.
  • 1500NWAE study: 45-60 minutes, BIB section, study log updated with date and duration. The FC3 who builds this daily habit is the one whose documented study log the LCPO defends at the FC2 advancement worksheet review.
  • 1600End-of-day work center accountability: all tools signed in, calibrated test sets powered down and logged, any open 3-M discrepancies status-updated, classified documentation secured. The FC2 end-of-day walk-through should find the work center in a state the LCPO can inspect without warning.
  • 1700Released on non-duty days. If on duty, stand the assigned combat systems watch in the rotation. FCC GROL study or COOL portal review for exam scheduling — the FC3 who uses one evening hour on credentialing five days a week enters the FC2 cycle with a completed credential the peer without the habit does not have.
  • 2000Personal time. Check the ship's schedule for tomorrow: underway operations, PMS actions requiring system conditions not available in port, any early-morning evolutions that require a pre-dawn setup. The FC3 who arrives at morning quarters already knowing tomorrow's production requirements is the one the FC2 stops pre-briefing.
  • 2200Lights out. Underway operations and deployment workup cycles extend every block — maintenance runs longer, watch sections are longer, and the documentation backlog builds if the FC3 does not stay current. Garrison habits determine underway performance.

Weekly Cadence

The shore-based week at FC3 is anchored around the PMS cycle and the combat systems readiness report rhythm. Monday opens with the week's MRC assignments published after weekend stand-down: the FC2 assigns work center actions at morning quarters, flight schedule write-ups from weekend operations are in the 3-M queue, and the FC3 arrives with the prior week's documentation closed out and the sub-account reconciled. The FC3 who needs Monday morning to catch up on Friday's paperwork is already behind the LCPO's mental scheduling. Tuesday through Thursday are the production core. PMS MRCs execute in the morning; CIC watch qualifications and training evolutions schedule around system availability in the afternoon; and the QA submission cycle runs daily — documentation submitted at end-of-day, QA returns flagged the following morning, root cause corrected before the same type of documentation gets submitted again. The combat systems department readiness brief typically has a weekly sync where the FC2 contributes the work center's PMS completion rate and any deferred maintenance. The FC3 whose section's numbers require explanation at that brief is the FC3 the CSO asks about by name. Friday is close-out and planning: PMS completions reconciled, calibration due dates flagged for the coming week, outstanding write-ups status-updated in the 3-M system, and the monthly counseling touch-point with the LPO if the schedule allows. The FC3 who brings a study log update and a NEC direction update to that conversation is demonstrating professional self-management at a level the eEVAL will reflect. When the ship enters a deployment workup or goes underway for an extended period, the entire garrison schedule compresses into the watch rotation and the maintenance production cycle — the flight schedule does not slow for the work center's PMS board, and the FC3's documentation quality under underway tempo is the visible standard the LCPO cites at the next eEVAL board.

Key Skills — How to Drill Each

  1. 01
    Execute a PMS MRC on an AEGIS combat system component — SPY radar, Mk 99 FCS, Mk 41 VLS, or CIWS — and document the corrective action in the ship's 3-M system without a QA return-for-rework.
    Before executing the MRC, read the entire card: every step, every special tool requirement, every note and caution. Do not start the maintenance evolution with open questions — if a step is unclear or requires a system condition you have not verified, ask the FC2 before starting the work, not during it. Halfway through a VLS cell inspection is not the time to discover that step 7 requires the missile fire control system to be in a specific inhibit configuration. During execution, keep the MRC card in hand and check off each step as completed. After execution, write the corrective action entry before closing the work center for the day — the entry is most accurate when the evolution is fresh. Read the entry back against the MRC before submitting: the work center supervisor, the WUC, the corrective action description, and the post-action BIT result all match the work you did.
  2. 02
    Identify and report a combat system fault at the component level — radar transmitter fault, fire control loop failure, VLS cell inhibit — with correct technical language and the correct maintenance reporting chain before the watch supervisor asks.
    The combat system fault report is a documented communication product, not a conversation. When a system BIT returns a fault code, when a watchstander reports an anomalous reading, or when a maintenance evolution surfaces a discrepancy, the FC3's first action is to identify the fault in the applicable technical manual: what component, what fault code, what the fault indicates at the system level. The second action is to notify the FC2 — with the component designation, the fault code or symptom description, and the immediate impact on system readiness stated clearly. The third action is the 3-M discrepancy entry. The FC3 who runs these three steps in sequence before the watch supervisor has to ask is the FC3 the combat systems team counts on. The FC3 who mentions a fault code in passing to the FC2 and hopes someone else documents it is the FC3 whose name appears on the preliminary inquiry when the fault escalates.
  3. 03
    Stand a CIC console watch at the ATAWC or equivalent station without a correction from the watch supervisor — report contacts, track changes, and system alerts by the ship's procedures.
    The watch qualification board was the standard. Every watch after the board is held to the same standard — not a looser version because you are now qualified, and not a higher version because an exercise is running. The watch procedures are documented in the CSRM and the ship's standing watch instructions; know them well enough that you can respond to a watch supervisor query with an accurate answer in five seconds, not a searching pause. The FC3 who treats every watch as a performance to a standard — not a habit drift — is the watchstander the TAO asks for by name during a real-world exercise. That reputation is worth more than any single watch performance.
  4. 04
    Operate the combat system in degraded-mode configuration during a training evolution — know which backup modes exist for the SPY, Mk 99, and CIWS when the primary chain faults.
    Degraded-mode operations are documented in the CSRM and the applicable AEGIS technical manuals. Know the degraded modes for the systems in your work center section before you need them under time pressure: if the SPY radar primary chain faults during an exercise, what is the backup sensor mode; if the Mk 99 fire control loop loses tracking, what is the manual engagement fallback; if the CIWS self-test failure occurs mid-exercise, what is the combat systems officer's expected briefing requirement. Walk through the degraded-mode procedures with the FC2 during a maintenance evolution before the fleet exercise — the FC3 who has rehearsed the degraded-mode response is the one the watch supervisor turns to when the primary chain faults in the middle of an actual engagement evolution.

Manuals & References — What Chapters Matter

  • OPNAVINST 4790.4 series — Ships' 3-M Systems Procedures Manual
    At FC3 you are signing corrective action entries as the technician of record. The OPNAVINST 4790.4 provisions that govern who can sign which type of maintenance action, what a valid corrective action entry looks like, and what the QA review chain requires are the provisions you are accountable to every time you close a 3-M discrepancy. Know the QA provisions in the section that applies to your work center's maintenance authorization level — the QA inspector who returns your documentation is quoting a specific provision, and the FC3 who understands which provision was violated fixes the root cause rather than just the specific entry.
  • NAVSEA technical manuals for your ship's installed AEGIS combat system components (SPY-1D or SPY-6, Mk 99 FCS, Mk 41 VLS, CIWS Mk 15)
    At FC3 you own the technical content of the MRCs you execute — not just the steps. The applicable NAVSEA technical manual sections for your work center's equipment tell you what the component does, what the fault modes look like, and what the corrective action is authorized to be. The FC3 who reads the technical manual sections for his three most common maintenance actions understands why each step exists. The FC3 who executes MRCs without reading the manual is the one whose fault report to the FC2 sounds uncertain when the system behaves unexpectedly.
  • Combat Systems Readiness Manual (CSRM) for your hull
    The CSRM governs your CIC watchstanding procedures, degraded-mode operations, and combat systems casualty response. At FC3 the CIC watch qualification is signed — the CSRM is the document your watch procedures come from, and the watch supervisor who corrects a watchstander is citing the CSRM. Read the sections that apply to your assigned console's watch responsibilities and the degraded-mode procedures for the primary systems in your work center section before every major exercise.
  • NAVPERS 18068 Vol II + current NEC source-rating NAVADMIN
    The NEC catalog tells you what C-school pipelines exist in the FC rate. The current source-rating NAVADMIN tells you which NECs are being awarded this cycle, what the eligibility criteria are, and what the school quota availability looks like. Pull the current NAVADMIN from MyNavyHR before the NEC conversation with your LCPO — the NAVADMIN a shipmate quoted from two years ago may describe a pipeline that has since changed eligibility requirements or had its quota reduced. The FC3 who brings the current NAVADMIN to the counseling conversation controls the information quality of his own career discussion.

Standards — How to Hit Each

  • QA-clean 3-M documentation: zero return-for-rework on closed maintenance actions over a deployment cycle.
    Build the documentation review habit before submission, not after the return. Before submitting any closed discrepancy to QA: re-read the corrective action entry against the MRC step by step, verify the WUC and job sequence number are accurate, verify the post-action BIT result is documented, verify the applicable technical reference is cited. The FC3 who reviews his own documentation before submitting catches the error the QA inspector would have caught — the difference is whether the QA rework shows up under your name on the Type Commander assessment trend report. Two reworks of the same documentation type tells QA that the first correction did not fix the root cause; fix the habit.
  • NWAE for FC2 prep: BIB pulled from current cycle, study plan documented, LPO briefed on progress at monthly counseling.
    Pull the BIB from MyNavyHR as soon as it is published for the current cycle. Compare it against the prior cycle's BIB: what sections are new, what material shifted weighting. Build a study calendar with specific weekly sections — not a 'study when I have time' intention — and log the date, section, and duration each study session. Bring the log to the monthly counseling. The LCPO who sees a documented study progression can defend it at the advancement worksheet review. The LCPO who sees a blank log cannot. The FC2 advancement slate is competitive; every FMS point the LCPO can defend at the worksheet review matters.
  • NEC pipeline packet in conversation with LCPO; Surface Warfare device in progress.
    The NEC direction conversation should happen at the monthly counseling within the first six months at FC3. Pull the current source-rating NAVADMIN, identify one or two NECs that make sense for your work center and interests, and bring both the NAVADMIN and a written preference to the counseling — not a verbal request. The LPO who receives a written NEC preference with the relevant NAVADMIN already read can act on it immediately. The LPO who receives a verbal 'I heard there was a C-school' conversation puts it in the 'follow up when I have time' pile. The Surface Warfare device PQS timeline should also be discussed at the same counseling: the FC3 who pins the SW device before the FC2 advancement cycle has an eEVAL bullet the FC3 without it does not.
  • PRT Good Medium or better; BCA in standard through the FC3 tenure.
    Three run days and two strength days per week is the baseline that supports a PRT Good Medium result at the test date without peaking for the test. Surface warfare ships run PT on the pier or the flight deck in port; the combat systems division chief watches the PT formation. The FC3 who trains consistently outperforms the FC3 who peaks for the semi-annual test under OPNAVINST 6110.1 by the third or fourth cycle — the body gets faster and stronger with consistent work, not with test-week surges. The Good High result in a competitive eEVAL ranking adds FMS points the FC3 who ran Good Medium does not have.

Technical Mistakes — Concrete Consequences

  • Closing a combat system MRC without performing every step — skipping a step because the failure mode looked obvious or because the evolution was running late.
    The incomplete maintenance action exists on the equipment. The next time that component writes up a fault, the 3-M system traces the last maintenance action to the last signature — yours. If the skipped step was a safety check, a torque verification, or a post-maintenance BIT, the component may be operating outside the technical manual's safe operating parameters without anyone knowing it. The Type Commander maintenance assessment identifies incomplete MRC actions by work center and by technician. The FC3 whose name is on an incomplete safety-relevant maintenance action does not separate that cleanly from the investigation.
  • Signing off a corrective action you did not personally perform or directly observe — co-signing a job a peer described from the passageway.
    One documented instance of fraudulent maintenance documentation at FC3 is a JAGMAN investigation. The investigation names every signature in the documentation chain: the FC3 who signed, the FC2 who reviewed it, and the work center supervisor. 'He told me the job was done' is not a defense the UCMJ accepts. The investigation finding is in the permanent record, surfaces at security clearance renewal, and follows the sailor into any federal employment application. A career can survive a lot of things. A JAGMAN finding for fraudulent records is not reliably one of them.
  • Improvising a combat system fault response outside maintenance authorization — reseating a module, adjusting a cable connection, or cycling a power state on a system without completing the applicable MRC or clearing it with the FC2 first.
    The AEGIS combat system has cascading subsystem dependencies. An unauthorized adjustment to a radar transmitter group can affect the fire control loop tracking performance; an unauthorized cable reseat in the AEGIS computing environment can affect system initialization behavior the next time the combat system is powered from cold. The Type Commander and NAVSEA both ask who authorized the work when the system casualty report is filed. The FC3's answer of 'I thought I was helping' does not change the casualty report outcome or the preliminary inquiry finding.
  • Letting test equipment calibration due-dates slip because the ship is underway and the parts cycle is slow.
    Out-of-calibration test equipment invalidates every measurement made since the last valid calibration date. Every combat system maintenance action that involved a measurement from that out-of-cal set is suspect. The QA review required to determine which actions need to be reopened and re-verified creates a workload that falls on the work center — specifically on the FC3 who held the sub-account. The Type Commander assessment identifies the out-of-cal finding under the work center name and the last responsible signature.
  • Posting OPSEC-relevant content from the ship's combat systems spaces — CIC console displays, VLS cell configurations, SPY radar alignment photos, weapon system readiness states, ship departure dates.
    The ship's security officer and PAO conduct social media sweeps. Adversary intelligence collection follows surface combatant accounts. A photo of a CIC display with a track picture, a VLS deck with cell configuration visible, or a departure port post with a ship identification creates a reportable security incident the same day the sweep identifies it. The commanding officer of an AEGIS combatant treats weapon systems OPSEC violations as a command-level incident — not a counseling topic. The FC3 whose name is on the incident report carries it through every clearance renewal and federal employment application.

Career Decisions at This Rank

  • NEC C-school pipeline commitment — which FC-series NEC, and when to submit the packet
    The NEC decision at FC3 is the first career fork with real long-term consequences because the NEC defines the billet pool you compete in for the rest of your sea tours. SPY radar track NECs (the AN/SPY-1D and the newer AN/SPY-6 systems) build toward the senior AEGIS sensor maintenance billets and translate directly into defense contractor positions at Raytheon and Lockheed Martin who support AEGIS radar fielding, depot maintenance, and ship alterations. Fire control track NECs follow the Mk 99 Fire Control System and the AEGIS engagement chain — the technical depth here builds toward the combat systems maintenance manager roles at the senior enlisted level and into the naval systems test and evaluation contractor market. Mk 41 VLS and weapons systems NECs address the weapon system launch authority roles that every surface combatant needs and that Bath Iron Works, Huntington Ingalls, and similar primes value in post-service hiring. Pull the current source-rating NAVADMIN, read the specific NEC entries in NAVPERS 18068, talk to FC2s and FC1s in each pipeline across your work center, and make the packet decision on real information rather than mess-deck reputation.
  • FC2 advancement cycle — first NWAE or re-compete after a missed slate
    The FC2 advancement slate is competitive by Navy Enlisted Classification code group. The Final Multiple Score combines exam score, eEVALs across the period, time-in-rate, awards, and education — and every component compounds. The FC3 who approaches the NWAE cycle with a documented study log the LCPO can defend, an EP or MP eEVAL recommendation, a NEC pipeline in motion, and a Surface Warfare device on the blouse has a structurally stronger FMS than the peer without those components. Missing the first slate is not terminal — many FC2s are selected on the second or third attempt — but every missed slate pushes the NEC-coded sea tour timing, the billet access that follows, and the shore duty cycle that comes after. Build the FMS components in parallel, not sequentially.
  • Reenlistment at end of first obligation — with or without Selective Reenlistment Bonus
    The FC3 reenlistment window typically opens around 36 months into a four-year obligation. The SRB for the FC rate is NEC-dependent, zone-dependent, and manning-dependent — pull the current SRB NAVADMIN before any conversation with the career counselor, because the bonus figures change each cycle. The honest calculation is: base pay progression plus BAH plus SRB net of taxes, against the civilian market value of a 23-24 year-old with AEGIS combat systems experience, a Secret clearance, and — ideally — an FCC GROL and a NEC. The FC3 who separates at end of first obligation with a NEC, a COOL credential, and a Surface Warfare device is entering a defense contractor market that can translate those credentials into a job title and a salary. The FC3 who separates without the credentials is entering a market that respects the military background but cannot quantify it. The strongest stay argument is the FC3 on track for FC2 advancement with a clear NEC pipeline and an AEGIS technical background that gets more valuable — not less — with each additional deployment.

How the Seat Varies by Unit Type

  • DDG-51 Arleigh Burke (AEGIS SPY-1D/SPY-6)
    The Arleigh Burke is where most FC3s execute their first sea tour, and the deployment cycle is real: 7-9 month deployments with a pre-deployment workup period that runs 6-12 months before the ship leaves. At FC3 on a DDG, you are executing PMS MRCs on the AN/SPY-1D or AN/SPY-6 radar components under the FC2's supervision, standing CIC combat systems watches during exercises and actual operations, and writing up fault reports on a system that the ship's combat readiness depends on. The high ops tempo of a deploying DDG is where maintenance documentation discipline gets tested — the flight schedule does not slow for the work center's paperwork, and the FC3 who has built the documentation habit in port maintains it under deployment pressure without dropping the standard.
  • CG-47 Ticonderoga cruiser (AEGIS-equipped)
    The Ticonderoga cruisers are larger platforms than the DDG-51 and carry a bigger combat systems department with a slightly larger work center staff. The AEGIS architecture — SPY-1A/B, Mk 99 FCS, Mk 41 VLS — is the same system philosophy as the DDG, and the maintenance program runs under the same OPNAVINST 4790.4 framework. The FC3 on a Ticonderoga generally gets more exposure to the full combat systems maintenance scope earlier in the tour because the larger department distributes the work center sections differently. The flip side: the Ticonderoga's AEGIS baseline is older than the DDG-51 Flight III SPY-6 equipped ships, so the NEC skills developed on a CG translate most directly into the legacy AEGIS fleet maintenance market rather than the newer SPY-6 AMDR market.
  • LCS (different combat systems, smaller crew)
    An LCS assignment at FC3 means a significantly smaller crew and a combat systems suite that varies by mission module — the surface warfare mission module brings the AN/SPS-77 Sea Giraffe radar and 30mm gun system rather than the AEGIS SPY/Mk 41 architecture the FC rate is built around. The smaller crew means the FC3 gets maintenance and watch responsibilities earlier and more independently than a DDG peer, but the AEGIS-specific proficiency that defines the FC rate's NEC and billet market is thinner. For the FC3 planning a defense contractor career centered on AEGIS systems, an LCS tour at this tier is a breadth experience rather than a depth experience.
  • NAVSEA/TYCOM shore staff billet
    A shore staff billet for an FC3 at a Type Commander or NAVSEA program office is uncommon but exists for specific NEC-coded requirements. If the billet comes up in a first sea-tour assignment cycle, it typically means the command needs a specific technical skill set. The advantage is schedule stability and exposure to fleet-level maintenance policy and program management above the ship level. The disadvantage is the same as any shore tour at this tier: the hands-on AEGIS maintenance proficiency that the sea tour builds is absent, and the peer who spent the same period on a DDG comes back with more fleet experience and a more competitive deployment record.
  • ASHORE: FRS/schoolhouse instructor at Dam Neck
    The NTTC Dam Neck schoolhouse and similar FC rate training commands occasionally carry FC3 billets as instructor assistants or course support staff. This is a shore duty environment rather than a sea tour environment and is not a typical first duty station, but it can appear as a shore duty rotation after the first sea tour. The FC3 instructor assistant role rewards the sailor who has the technical depth to support classroom instruction on AEGIS systems — it also provides the schedule stability to complete the FCC GROL, COOL credentials, and NWAE study that the deployed ship schedule compresses. The tradeoff is the same as any early shore duty: come back to the fleet with a credential stack the sea tour peers do not have, or the early shore tour becomes a career debt.

What Good Looks Like at This Rank

The good FC3 is the technician the FC1 sends to troubleshoot the combat system write-up that came back twice — the intermittent SPY radar transmitter BIT fault, the Mk 99 tracking loop anomaly that tests good at static and writes up at operating temperature, the VLS cell inhibit that the pre-fire checklist identified and nobody can reproduce on the bench. He goes back to the applicable NAVSEA technical manual section for that component, reads the fault isolation procedure from the top rather than from where the last technician stopped, and follows the diagnostic branching logic to a call he can document with supporting evidence. His corrective action entry names the component, the fault code or symptom, the isolation procedure followed, the corrective action taken, and the post-action BIT result. The QA inspector can reconstruct the diagnosis from the documentation without calling the FC3. The write-up closes clean. His CIC watch is the watch the TAO does not think about. The good FC3 at his assigned console handles contact reports, track status changes, and system alerts by procedure — no pause before the query response, no scanning the watchbill for who to ask. During a degraded-mode exercise when the primary tracking chain faults, he knows the backup mode because he walked through the CSRM procedure with the FC2 during a maintenance evolution two weeks before the exercise, not because he is reading it for the first time on the watch log. The watch supervisor who has the good FC3 at a console during a real-world engagement evolution is not supervising the FC3 — he is using him. His LCPO can name his NEC pipeline direction, his study log update, and his eEVAL ranking without looking at a file — because the monthly counseling conversation includes all three, every time, delivered by the FC3, not extracted by the LPO asking. The FCC GROL is in progress through Navy COOL. The Surface Warfare device PQS has a completion date the senior FC signed off on at the last counseling. The advancement worksheet review does not produce surprises because the FC3 has been having the conversation that prevents them. That is what the LCPO is building when he calls the FC3's name at the FC2 advancement slate recommendation meeting.

Preview — The Next Rank

FC2 (E-5) is the working senior technician and the first tier where the LCPO explicitly delegates technical authority over a section of the combat systems maintenance bill. As FC2 you are not the technician working under the FC2's review — you are the FC2 reviewing the FC3's work before it goes to QA, signing PQS line items for the FC3s and FCSNs below you, managing the calibration sub-account and classified documentation accountability at the section level, and briefing the combat systems fault status to the Combat Systems Officer when the CSO asks. The FC3 who understood that the documentation standard was real, that the fault reporting chain mattered, and that the NEC pipeline decision had long-term consequences has been building toward FC2 execution the entire time. The NWAE for FC1 becomes the career anchor of the FC2 tenure. The advancement competition does not get easier — the FC2 slate is smaller and the pool of competitors includes FC3s who came up through the same NEC pipeline you did, with the same eEVAL inputs and the same exam material. The FC2 who walks into the FC1 advancement cycle with a documented study log, an EP eEVAL ranking, a NEC in awarded status, and a Surface Warfare device has a structural FMS advantage. The FC2 who reads the BIB two months before the cycle closes is competing against the FC2 who has been studying for eight months. What you cannot fully see from FC3 is how much of the FC2 job is teaching rather than doing. The FC3s and FCSNs in your section are watching how you carry the maintenance bench the way you watched the FC2 above you. The FC2 who runs clean fault isolation, produces clean documentation, and gets the section's QA rework rate below the command average is the floor. The FC2 who builds the FC3 underneath him into a sailor the LCPO can trust is the one the chief is watching for the LPO recommendation.
FAQ

FC E4 — Frequently Asked Questions

Q01What does a E4 FC (Fire Controlman) actually do?
You own a section of the combat systems maintenance bill — the SPY radar work center, the Mk 99 fire control work center, the Mk 41 VLS, the CIWS, the SSDS suite, or the computing environment depending on your ship and your NEC track — and you execute scheduled maintenance under the FC2 or FC1's supervision.
Q02What's the most important thing to know as a E4 FC?
FC3 (E-4): the crow means the QA inspector holds your 3-M documentation to a technician standard, not an apprentice standard.
Q03What does a typical day look like for a E4 FC?
Time-blocked day at the E4 FC rank tier: 0530 Wake up. Check the ship's maintenance management system for any overnight write-ups that affect the work center's morning evolution — a VLS inhibit, a SPY BIT fault on an overnight system watch, a CIWS self-test anomaly. These are the write-ups the FC2 will ask about at 0800 quarters, 0600 PT formation on the pier or the flight deck. Surface warfare PT is visible — the combat systems department head can see the flight deck formation from the bridge wing. Run days are the days to run strong, not to pace yourself to the back of the pack,…
Q04What mistakes get E4 FC soldiers fired or relieved?
Fraudulent 3-M maintenance entry — signing off a corrective action that was not personally performed or directly observed. One documented instance of fraudulent maintenance documentation at FC3 is a JAGMAN investigation. The investigation names every technician in the documentation chain. 'The FC2 told me it was done' is not a defense the UCMJ accepts, and post-service background checks and clearance renewals both surface JAGMAN findings; NJP or DUI.…
Q05What career decisions matter most at the E4 FC rank tier?
NEC C-school pipeline commitment — which FC-series NEC, and when to submit the packet — The NEC decision at FC3 is the first career fork with real long-term consequences because the NEC defines the billet pool you compete in for the rest of your sea tours. SPY radar track NECs (the AN/SPY-1D and the newer AN/SPY-6 systems) build toward the senior AEGIS sensor maintenance billets and translate directly into defense contractor positions at Raytheon and Lockheed Martin who support AEGIS radar fielding, depot maintenance, and ship alterations.…
Q06What's next after E4 for a FC (Fire Controlman) in the Navy?
FC2 (E-5) is the working senior technician and the first tier where the LCPO explicitly delegates technical authority over a section of the combat systems maintenance bill.
Q07What manuals and regulations does a E4 FC need to know cold?
OPNAVINST 4790.4 series — Ships' 3-M Systems Procedures Manual; the maintenance program you run every evolution inside.; NAVSEA technical manuals for your ship's installed AEGIS combat system components (SPY-1D or SPY-6 series, Mk 99 FCS, Mk 41 VLS, CIWS Mk 15) — your LPO will assign the volumes governing your work center.; Combat Systems Readiness Manual (CSRM) for your hull — the command-level governance document that ties together your PMS, watchstanding, and casualty response procedures.

Based on 14 tips from 0 contributors

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