Skip to main content
HonestMOS
●InvestigationsCongress made VA disability claims free to file. An entire industry charges veterans anyway — and nobody can stop them.→
←Back to 2651 Intelligence Surveillance Reconnaissance (ISR) Systems Engineer — overview, pay, training, civilian translation, reviews
2651E6

Intelligence Surveillance Reconnaissance (ISR) Systems Engineer

E-6 (Staff Sergeant) · Marines

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

At SSgt you are no longer managing a single collection section — you are the technical authority the intelligence officer calls when the OIC is not available and the collection architecture is broken. The MCSC program office knows your name by now, or it should. If a system update hits the fleet and you are the senior NCO in the element, the program manager's questions land on you. Build the program office relationship before you need it, not during a crisis.

The Honest MOS Read
Staff Sergeant in the 2651 community is the ISR systems element NCO — the senior technical NCO for the element's full collection architecture, typically two to four section chiefs and their organic collection teams. The jump from section chief to SSgt is not a linear increase in the same job. The section chief owned one sensor and the people running it. The SSgt owns the sensor architecture: how the G/ATOR sections integrate their feeds into the C2 network, whether the data link topology the collection management officer built into the operations order is actually executable given current system readiness, and what the element's honest collection capacity is against the intelligence officer's collection plan — not the optimistic capacity, the honest one. The AN/TPS-80 G/ATOR fleet management is where SSgt technical authority becomes concrete. A fleet of two to four G/ATOR systems, each with its own maintenance history, its own fault profile, and its own configuration state, has to be managed as an integrated whole — not as a set of independent section problems. The SSgt who knows the maintenance history of every system in the element's authorization and who can predict which system is the most likely failure risk during the next collection rotation is the SSgt the intelligence officer can plan around. The SSgt who finds out about a system's chronic fault pattern when the system fails during the collection window is the SSgt who is reacting rather than managing. Data link integration is the technical layer that the section-chief billet does not fully develop. At Sgt section chief level, data link management means maintaining the connection between the G/ATOR and the C2 node receiving the collection feed. At SSgt element level, data link management means understanding how multiple collection feeds are integrated into the C2 architecture, where the bandwidth constraints are, what the latency profile looks like across the element's collection network, and how a data link failure on one section's feed affects the intelligence officer's picture. The SSgt who can draw the element's data link topology from memory — which systems feed which nodes, what the redundancy paths are, where the single points of failure are — is the SSgt whose briefing to the intelligence officer on collection architecture sounds like an advisor rather than a maintainer. The sensor-to-command architecture advisory role begins at SSgt. The intelligence officer is not a systems engineer. She knows what intelligence the commander needs; she does not know which combination of organic collection assets, in what employment posture, against which terrain, will satisfy the collection requirement reliably. That translation — from intelligence requirement to sensor employment recommendation — is the SSgt's job. The SSgt who sits in the collection management brief and can say 'that collection requirement against that target type in that terrain calls for two G/ATOR sections in this general posture, with a data link path to the C2 node at this echelon, and here is the degradation tolerance the collection plan should account for' is the SSgt who shapes the collection plan before it becomes an order. The SSgt who waits to receive the plan and execute it is not the senior technical advisor — he is a senior section chief. The MCSC program office liaison relationship is the career differentiator that begins at SSgt. Marine Corps Systems Command manages the AN/TPS-80 G/ATOR program, pushes technical bulletins and software updates to the fleet, and conducts operational assessments of system performance in the field. The program office wants feedback from experienced operators — what the system does in the conditions the test data did not capture, what the configuration changes look like from the section chief's end, where the operator procedures in the technical documentation diverge from what actually works. The SSgt who provides specific, documented, honest operational feedback to the program office — 'this configuration change improved X performance at the cost of Y stability in high-humidity conditions, and here is the data from three collection rotations' — is the SSgt the program manager calls before the next change goes to fleet. That relationship is visible to the FitRep chain and it eventually leads to the program office billet itself, if the SSgt wants it. The FitRep load at SSgt is substantially heavier than at Sgt. Three to four Section A narratives per cycle, each built from monthly counseling notes on Sgt section chiefs who are themselves writing FitReps on their Cpls. The SSgt whose Section A inputs are consistently revised by the reporting senior — the OIC, the intelligence officer, or the battalion S-2 — is the SSgt whose FitRep relationship with the reporting senior deteriorates by cycle two. The Section A that describes what the Sgt section chief did in a specific operational context, with a specific outcome, against a specific collection requirement — rather than the Section A that says the Sgt is an outstanding Marine — is the Section A the reporting senior signs without revision. Build the habit now. The Section A narratives you write on your Sgts are the most visible indicator of your professional writing standard at the GySgt board. The GySgt board conversation starts at SSgt pin-on, not at mid-career. The 2651 GySgt is the MEF or MAGTF-level senior ISR technical advisor — a fundamentally different scope than the element-level SSgt. The SSgt who understands that distinction and is deliberately building the advisory skills, the collection architecture fluency, and the program office relationship that the GySgt billet requires is two years ahead of the SSgt who waits until the GySgt board window to think about it.
Career Arc
  • 01SSgt selection board result — centralized SNCO board, FitRep relative value and PME completion are the primary inputs; 2651 is a small, competitive occfield at every SNCO board.
  • 02Element senior NCO billet assumption — primary enlisted advisor to the OIC on organic sensor collection capability, fleet maintenance status, and collection architecture for two to four section chiefs.
  • 03MCSC program office liaison relationship development — first formal feedback cycle to the AN/TPS-80 G/ATOR program manager; documented operational assessment submitted.
  • 04Staff NCO Academy completion (SNCOAC) — required PME gate for GySgt eligibility; in-residence at MCB Quantico is the standard; schedule before the GySgt board window.
  • 05GySgt board window — centralized selection; FitRep relative value across all SSgt cycles, SNCOAC completion, composite, and conduct; advisory billet quality is the differentiator in the 2651 community.
  • 06Warrant Officer 2610 (SIGINT/Electronic Warfare Warrant Officer) application window — open to SSgts with the right technical and clearance profile; early decision point.
  • 07Post-SSgt assignment billet — FMF element senior NCO, MCSC program office liaison billet, schoolhouse instructor billet, or MEF intelligence staff augment.
Common Screwups
  • ×SNCOAC PME deferred through multiple board cycles because the operational calendar never clears. The GySgt board reads SNCOAC completion as a binary qualifier — complete or not. The SSgt who enters the GySgt board window without SNCOAC is not competitive regardless of FitRep quality. The 2651 occfield has no large reservoir of SSgts; every slot at the GySgt board is contested. Defer SNCOAC twice and watch a peer with identical FitReps but complete PME get selected while your name is deferred for the following cycle.
  • ×NJP, DUI, or UCMJ action at SSgt. At this rank, the UCMJ action removes the element senior NCO billet, generates a clearance review that in most cases results in revocation, and triggers administrative separation under MARCORSEPMAN. The program office relationship you built, the FitRep cycles you invested in, the collection architecture advisory credibility — all of it transfers to someone else. The cleared intelligence SNCO community is small enough that the circumstances of a UCMJ action at SSgt are known across the occfield within a month.
  • ×Section A narratives that attribute outcomes the Sgt section chief did not produce, or that assign section-level credit for element-level or OIC-driven outcomes. The reporting senior at the element level reads FitRep Section A inputs against what actually happened in the collection season. An SSgt who inflates a Sgt's Section A to compensate for a weak FitRep cycle — or to avoid a difficult relative value placement conversation — is misrepresenting the Sgt's performance record to the GySgt board. The GySgt board will compare that Sgt against other Sgts whose Section A narratives are accurate. The inflation is visible when the comparison is made. The SSgt whose Section A inputs require revision is the SSgt whose own FitRep narrative the reporting senior writes carefully.
  • ×Providing an optimistic collection capability assessment to the intelligence officer because the honest assessment would require hard conversations about maintenance status or system readiness. The collection plan built on optimistic capability assessments fails in the collection window, and the intelligence officer traces the failure back to the SSgt's assessment. The SSgt who told the intelligence officer the element could support a four-section simultaneous collection architecture when two of the four systems had open maintenance work orders is on record with that assessment. Tell the intelligence officer what the element can actually do. Let her and the S-2 make the risk decision. The honest SSgt who says 'two sections fully ready, two sections degraded, here is the impact' is having a harder conversation than the one who says 'four sections ready.' The honest SSgt is also the one the intelligence officer trusts at the next planning cycle.
  • ×Allowing clearance reportable matters among the section chiefs to go unescalated because the matter seems minor or the SSgt wants to handle it internally. At SSgt, you are the senior NCO in the element; when a Sgt section chief has a reportable matter — foreign contact, financial delinquency, legal incident — the reporting chain runs through you to the unit security manager. The SSgt who delays that reporting to protect the Sgt's career is the SSgt who explains the delay to the battalion security officer when the matter surfaces in the periodic reinvestigation. Self-report immediately. Route the Sgt to the security manager the same day. That is the job.

A Day in the Life

  • 0500Wake. Phone check for section chief group chat — any overnight system faults, watch incidents, or personnel issues across the element. Before the daily schedule starts, you already know the element's maintenance posture better than anyone who will brief it to you.
  • 0530PT formation. You take accountability for the element and report to the OIC. Any missing section chief is your problem to explain before the OIC asks.
  • 0545–0700Unit PT. You set the physical standard for the element. On element-led PT days, you built the plan and the section chiefs execute it. After PT, the section chiefs take accountability of their sections and report up the chain — the administrative reflex you established at section chief level is now the element's standard.
  • 0700–0830Hygiene, chow. Before morning colors, the fleet management board is in your head: which systems had overnight issues, which section chief's maintenance log should you pull before the morning formation, which open work orders are approaching risk to the collection calendar.
  • 0830Morning formation. OIC gives the element's plan for the day. You brief the section chiefs; they brief their operators. No section chief should be asking the OIC questions that belong to you.
  • 0900–1100Element-level work — collection management brief prep for the afternoon meeting with the intelligence officer, fleet management board update from the section chiefs' morning maintenance reports, FitRep Section A draft for the Sgt whose cycle is due, or MCSC technical bulletin implementation review with the section chiefs. You are supervising the section chiefs' work, not performing the section-level tasks.
  • 1100–1130Element administration — fleet status board updated, open work orders reviewed, training report data aggregated from the section chiefs. The OIC reviews the element's posture at midday; the board should reflect current status before that review.
  • 1130–1300Chow. The SSgt at the SNCO table. The OIC and the intelligence officer are nearby. The collection management advisory relationship is built in these conversations as well as in the formal brief. The SSgt who is talking shop with the intelligence officer at chow is the SSgt building the advisory relationship that the GySgt billet requires.
  • 1300–1400Collection management brief preparation or brief execution with the intelligence officer. This is the element senior NCO's primary advisory event. Bring the fleet readiness data, the collection architecture options, and the honest capability assessment.
  • 1400–1530Monthly counseling cycle with section chiefs — composite score review, FitRep awareness brief, SSgt board mechanics, specific 90-day development plan for each Sgt. SNCOAC coursework if enrolled in pre-course distance education.
  • 1530–1630Final formation. OIC gives next day's plan. Sensitive items — all TS/SCI-associated hardware and media across all sections — verified through the section chiefs before you sign the element accountability log.
  • 1630Liberty call on normal garrison schedule. The liberty standards brief to the section chiefs is a weekly event — not optional based on whether anything has happened recently. Something always happens eventually.
  • 1700–2000Personal time — SNCOAC coursework, GySgt board candidacy management, WO 2610 application research if applicable, program office feedback report drafting, FitRep Section A drafts for section chiefs. The SSgt who uses personal time to close the GySgt board gaps is the SSgt who is competitive when the board window opens.
  • 2000–2200If a section chief called with a Marine welfare issue — financial, legal, personal, behavioral health — you are engaged. You do not handle it for the section chief; you verify the section chief is routing it through the correct channel (MCCS PFMP, Legal Assistance, Chaplain, Branch Medical behavioral health) and has documented the routing. The section chief who handles the Marine welfare issue correctly and documents it does not need the SSgt to manage it. The section chief who buries the problem needs a different kind of conversation.
  • COLLECTION OPERATION / DEPLOYMENTThe garrison schedule does not apply. You are managing the element's collection architecture: which sections are on the rotation, which systems are being rested for maintenance, which data link paths are primary and which are fallback. You brief the intelligence officer on capability changes in real time. You sleep when the OIC rotates you. You do not relax the sensitive item accountability standard because operations are high-tempo — that is specifically when items go missing.

Weekly Cadence

Monday is the element senior NCO's planning and administrative day. The OIC's weekly plan comes out at Friday's final formation; Monday you build the element execution plan — which section chief runs which training event, what the collective task standard is, what the collection management brief requires, and what the FitRep and counseling cycle demands this week. Brief the section chiefs before 0930. The element whose SSgt is still building the week's plan at 1000 Monday is the element the OIC notices. Tuesday through Thursday is the training and operational tempo. Element-level collection management briefings to the intelligence officer, section-chief-led T&R evaluation lanes with the SSgt supervising rather than doing, fleet management reviews with the section chiefs, technical bulletin implementation training, and the MCSC program office feedback cycle when a rotation has just concluded. The SSgt who runs the week's training events and can brief the OIC at end of week on what each section chief demonstrated, what the T&R completion progress was, and what the gap looks like against the next evaluation event is managing the element's training program. The one who reports 'training went well' is not. Friday is the administrative cycle — element sensitive item inventories verified through the section chiefs, fleet management board updated with the week's maintenance actions, FitRep Section A drafts reviewed before submission to the reporting senior, monthly counseling sessions with each section chief. The Friday counseling session is the element senior NCO's most consequential weekly administrative event. Each Sgt section chief leaves the counseling session knowing exactly where his FitRep profile stands against the SSgt board criteria, what the one or two highest-leverage development actions are, and what the specific timeline is for each. The SSgt who runs clean Friday counseling sessions builds section chiefs who are not surprised by the SSgt board outcome. The one who has general conversations about development is surprised by section chiefs who are surprised by the board. Collection operations and deployment cycles collapse the garrison calendar without collapsing the administrative requirements. FitRep Section A notes, counseling entries, T&R tracking, sensitive item accountability, and program office feedback cycles do not pause because the element is forward. They happen in the margins of the watch schedule and the collection rotation. The SSgt who keeps contemporaneous notes during operations rather than reconstructing them after the unit returns is the SSgt who produces administratively defensible documentation. Reconstruction from memory is not documentation — it is a best guess about what happened.

Key Skills — How to Drill Each

  1. 01
    Manage the element's full G/ATOR fleet — maintenance history tracking, fault pattern analysis, configuration state management, and pre-deployment readiness certification across all systems in the authorization.
    Build a fleet management board that shows every system in the element's equipment authorization: serial number, last PM event, open work orders, current fault code history, configuration state (current technical bulletin applied or not), and last full readiness certification date. Update it weekly from the section chiefs' maintenance reports. The SSgt who can answer 'which system in the element has the highest probability of failure during the next 30-day collection rotation' from the board data — rather than from intuition — is the SSgt managing the fleet as a technical program. The program manager at MCSC who receives an operational readiness report from this element will receive specific fault history data and configuration performance observations, not a summary of 'systems are generally in good shape.' That level of fleet management discipline is the foundation of the program office liaison relationship.
  2. 02
    Brief the intelligence officer and the collection management officer on the element's organic ISR collection capability, current readiness posture, collection architecture options, and the honest operational impact of degraded systems — before the collection plan is finalized, not after.
    The collection management brief at SSgt level is an advisory consultation, not a status report. Before the intelligence officer finalizes the collection plan for the next operation, the SSgt should be in the room with the collection architecture options mapped: which sensor employment postures can satisfy the stated collection requirements, what the data link topology looks like for each option, what the maintenance risk is against each posture given current fleet readiness, and what the fallback is if a system fails mid-rotation. Prepare for this conversation by reading the collection requirements the intelligence officer has submitted and thinking through them against documented system capabilities. The SSgt who walks into the collection management brief knowing the requirements and having already analyzed the feasibility is the SSgt who shapes the plan. The one who shows up to receive the plan has already ceded the advisory role.
  3. 03
    Write FitRep Section A narratives for Sgt section chiefs that survive the battalion FitRep board without revision — observed behavior, action-result-impact structure, relative value placement calibrated against the section chief's actual performance.
    The monthly counseling notes on each Sgt are the raw material. Every counseling session, write down what the Sgt did — in what collection operation context, with what outcome, against what standard — and keep the notes chronologically. When the FitRep cycle arrives, the Section A comes from those notes, not from memory or general impression. The Section A for the strongest performing Sgt in the element should describe the specific collection operations he led, the specific outcomes he produced, and the specific ways his performance exceeded the standard — not that he is an outstanding section chief. The reporting senior who reads that Section A and can match it against his own observation of the Sgt's performance will sign it without revision. The Section A the reporting senior revises is the Section A that does not match observable reality. Keep the counseling notes current and the Section A will write itself.
  4. 04
    Receive, assess, and implement MCSC technical bulletins and software configuration changes — evaluate operational impact, build the section chief training plan, and provide documented feedback to the program office on fleet performance.
    When a technical bulletin arrives from MCSC, the SSgt's job is three sequential actions: first, read it and assess the operational impact (does this change affect collection performance, maintenance procedures, or data link behavior in ways that require immediate training?); second, brief the section chiefs on the change and build the implementation training timeline before any system is modified; third, collect performance data from the section chiefs after implementation and submit a documented operational assessment to the program office within 30 days. The program manager uses that feedback. The SSgt who submits a two-paragraph assessment that describes specific performance changes — measured against specific collection parameters in specific operational conditions — is the SSgt who gets a call from the program manager before the next bulletin is released. That relationship is built one feedback cycle at a time.
  5. 05
    Mentor Sgt section chiefs on FitRep Section A writing, Sergeants Course preparation, SSgt board mechanics, and the program office advisory skills that distinguish a GySgt-competitive 2651 from a peer who can run a section but cannot advise an intelligence officer.
    Monthly counseling with each Sgt section chief must include the FitRep awareness component — show the Sgt his current FitRep profile, what the relative value placement looks like across cycles, what the SSgt board selection rate for 2651 has been in recent MARADMIN data, and what the gap is between where the Sgt stands and where he needs to be. For the collection management advisory skill specifically, the SSgt mentors by bringing the Sgt section chief into the pre-operation collection management brief as an observer, then as a participant, then as the primary briefer while the SSgt sits in the back. The Sgt who has briefed the intelligence officer on collection capability three times before the SSgt board window does not need the SSgt to tell him how to do it — he has done it.
  6. 06
    Advise the OIC on Warrant Officer 2610 pipeline suitability for section chiefs with the right technical and clearance profile — and make an honest self-assessment of whether the WO pipeline is the right path for your own career.
    The Warrant Officer 2610 (SIGINT/Electronic Warfare Warrant Officer) pipeline requires a technical background consistent with the 2651 skill set, a TS/SCI clearance, and strong endorsement from the commanding officer. The application window is open to SSgts and GySgts. The honest assessment for any 2651 SSgt considering the WO pipeline: the WO billet is a technical advisory role that operates at the operational and theater level, not the section chief or element level. The 2651 SSgt who is drawn to the technical depth — the sensor architecture, the collection management advisory role, the program office interface — and who wants to spend a 20-to-25-year career operating at that technical advisory level should examine the WO 2610 pipeline seriously. The SSgt who views WO as a promotion alternative because the GySgt board is competitive should think more carefully — the WO community is its own career trajectory with its own demands. Talk to warrant officers before the application window.

Manuals & References — What Chapters Matter

  • NAVMC 3500.20 — Intelligence/Electronic Warfare Training and Readiness Manual (SSgt-level collective tasks and element-level standards)
    At SSgt you are managing the T&R program for multiple section chiefs and their operators — the T&R manual is the document you use to set the element's training standard and to evaluate the section chiefs' section-level training programs. Pull the SSgt-level collective task list and the section-chief collective tasks, and build the element T&R board showing every Marine's qualification status across all sections. The element T&R completion rate is a monthly metric the OIC and the intelligence officer review; the SSgt who brings the T&R board to the monthly training brief with gap analysis and a specific completion schedule is the SSgt managing the qualification program. The one who reports 'training is ongoing' is not.
  • MCWP 2-26 — MAGTF Intelligence Operations
    At SSgt, MCWP 2-26 is the framework you use to advise the intelligence officer on collection architecture, not just to understand the collection management process. Own the chapters on collection requirements management, the intelligence production cycle, and the integration of organic and non-organic collection assets at the MEF and MAGTF level. The collection management brief the SSgt gives the intelligence officer references the same doctrinal framework the intelligence officer is using to build the collection plan — when the SSgt speaks the collection management language fluently, the intelligence officer hears an advisor, not a systems maintainer.
  • FM 3-55 — Information Collection
    The joint information collection framework is the language of every joint task force and coalition ISR synchronization meeting the SSgt will participate in. At element-senior-NCO level, the 2651 SSgt is regularly interfacing with Army ISR elements, joint collection management officers, and coalition ISR integration teams where the common doctrinal language is FM 3-55 rather than MCWP 2-26. The SSgt who can translate between the USMC collection management framework and the joint framework without deferring to the OIC is the SSgt who represents the element's capabilities in joint venues. Read the collection synchronization, collection asset management, and tasking authority chapters.
  • JP 2-01 — Joint Intelligence Support to Military Operations
    The joint intelligence enterprise — JISE, DIA collection management, national-level tasking authority — is the operational context for the element's organic collection mission at MEF and MAGTF level. The SSgt who understands how organic ISR collection fits into the joint collection architecture is the SSgt who can brief the collection management officer on where the element's collection fills a gap that non-organic assets cannot cover, and where national collection assets could relieve the section chiefs' operational burden. That level of architecture understanding is what distinguishes the element senior NCO from a promoted section chief.
  • DoD 5240.1-R — Procedures Governing the Activities of DoD Intelligence Components
    At SSgt, the legal compliance standard for collection is the element's standard — not just your personal standard. Every collection activity the section chiefs execute falls under your authority as the senior technical NCO. DoD 5240.1-R covers the oversight and approval requirements for different collection activity types, the reporting chain for collection activities that approach legal boundaries, and the compliance posture the element must maintain for external oversight reviews. The SSgt who briefs the OIC on a collection activity's legal compliance profile — rather than leaving the OIC to identify potential issues — is the SSgt the OIC trusts with independent collection planning authority.
  • MCO 1610.7 — Performance Evaluation System
    At SSgt you are writing FitRep Section A narratives for multiple Sgt section chiefs simultaneously, and the relative value placement decisions you make affect the GySgt board outcomes for each of them. Read the relative value placement guidance chapter carefully — not for the mechanics of how the marks work, but for the responsibility the SSgt bears to calibrate the FitRep profile across the element consistently. The SSgt who places every Sgt at the same relative value to avoid making hard comparisons is not using the FitRep system correctly. The GySgt board will make the comparison anyway. Calibrate the placements honestly, document the rationale in the counseling notes, and the FitRep cycle will produce defensible results.
  • MCO 1400.32 — Marine Corps Promotion Manual (SNCO board mechanics)
    Pull the SNCOAC completion requirement, the GySgt board input criteria, and the centralized selection board mechanics before your first GySgt board window. The 2651 GySgt board is a centralized competitive selection event where the board reads FitRep relative value across all SSgt cycles, SNCOAC completion, composite score, and conduct record. The SSgt who understands the board mechanics before the board window is building his record deliberately — managing FitRep relative value trajectory, scheduling SNCOAC, and tracking the GySgt selection rate for 2651 from current MARADMIN data. Pull the current MARADMIN before asking the OIC where you stand.

Standards — How to Hit Each

  • Staff NCO Academy (SNCOAC) graduate — required PME gate for GySgt board eligibility; in-residence at MCB Quantico is the standard.
    Schedule the SNCOAC in-residence slot through the unit S-3 training cell 90 days before the course drop date. Build the coverage plan for the element's collection operations during the SNCOAC attendance window before the slot is confirmed — the OIC who approves the attendance needs to know the element's mission readiness does not depend on the SSgt's physical presence during the course. SNCOAC at Quantico is a residential course that develops the staff-level planning and advisory skills the GySgt billet requires; it is not a correspondence-equivalent. The GySgt board for 2651 is competitive enough that an incomplete SNCOAC is a visible gap against peers with complete PME records.
  • 1st-Class PFT and CFT — the element's average is visible to the battalion commanding officer through the unit health-of-the-force report.
    At SSgt, fitness is a leadership metric as well as a personal one. The element whose SSgt consistently scores 1st-Class on both tests has a different fitness culture than the element whose SSgt scores 2nd-Class. The battalion commanding officer's health-of-the-force review looks at fitness averages by unit — the element that drags the battalion's average is visible to the CO in ways that generate a conversation the intelligence officer has with the OIC and then the OIC has with the SSgt. Train the CFT events specifically; the ammunition can lift and the maneuver under fire sequence are the events where 2651 SSgts most commonly drop from 1st-Class to 2nd-Class after the Sgt tour. They are also the events most directly tied to the physical demands of sensor site occupation and displacement.
  • TS/SCI clearance maintained with no reportable incidents going unreported — and element-level clearance reporting culture that the section chiefs have absorbed.
    At SSgt, the clearance reporting standard is yours and the element's simultaneously. Build a clearance reporting culture in which every section chief knows that self-reporting a reportable matter through the chain immediately — before it surfaces in a periodic reinvestigation — is the standard procedure, not an option. Brief the clearance reporting requirement at every new section chief's check-in counseling. The SSgt who has a section chief with an unresolved reportable matter that surfaces during a periodic reinvestigation, and who cannot demonstrate that the reporting chain was running through the SSgt, is the SSgt who explains to the battalion security officer why the matter was not escalated.
  • Element T&R completion rate at the battalion standard — the OIC and the battalion intelligence officer see the monthly T&R report.
    Track the element's T&R completion rate across all sections on a monthly basis, with a gap analysis and a specific completion schedule for every overdue event. The element that enters a collection rotation with T&R gaps is the element the collection management officer does not assign the complex collection requirements. The OIC who reviews the monthly T&R report and sees a current plan with a specific completion schedule for every gap is the OIC who can brief the battalion intelligence officer on the element's collection readiness with confidence. Build the section chiefs' T&R management habits so the element-level report aggregates clean data from section-level tracking, rather than the SSgt reconstructing the section chiefs' T&R status at the monthly review.
  • Program office operational feedback submitted to the MCSC AN/TPS-80 G/ATOR program manager after every significant collection rotation or technical bulletin implementation.
    Schedule the program office feedback submission as a standing agenda item after every collection rotation that generates useful performance data. The feedback format the program manager finds most useful is specific: system identifier, operational condition (terrain, weather, operational tempo), performance observed versus expected, fault history during the rotation, and any procedural deviations from the technical documentation that produced better or worse results than documented. Two paragraphs of specific, measured feedback submitted consistently is more valuable to the program manager than a comprehensive report submitted once a year. The SSgt who makes the program office feedback submission a routine — rather than a special effort — is the SSgt who builds the program office relationship without the administrative burden of a major report.

Technical Mistakes — Concrete Consequences

  • Accepting section chiefs' fleet readiness reports without personally verifying the two or three systems with chronic fault histories before a collection rotation begins.
    The section chief who reports a system as fully mission-capable because the last BIT passed, without noting that the system has generated intermittent fault codes on three of the last five cold-starts, is telling the SSgt what the SSgt needs to hear for the deployment timeline to hold. The SSgt who signs off on the pre-deployment readiness certification based on the section chiefs' verbal reports — rather than personally walking the fault histories on the highest-risk systems — is the SSgt who certifies the readiness and explains the collection gap to the intelligence officer when the chronic-fault system fails on night two of the rotation. Personally verify the two or three systems in the worst condition. The section chiefs manage the rest.
  • Giving the intelligence officer an element collection capability assessment that does not account for the maintenance risk on degraded systems.
    The collection plan that assumes four fully mission-capable collection sections and instead receives two fully capable and two degraded sections fails mid-rotation in predictable ways. The intelligence officer who built the collection plan on the SSgt's assessment — and who briefed the commanding officer that the collection requirement would be satisfied — has to explain the gap. The SSgt who gave the optimistic assessment is named in that explanation. The assessment that says 'two sections fully capable, two sections with open work orders that may affect extended-range detection during the rotation, here is the contingency' is harder to deliver but survivable when the prediction turns out to be accurate. The optimistic assessment that turns out to be wrong is not survivable at the same career level.
  • Delaying a technical bulletin implementation because the collection calendar is full and it will be disruptive.
    Technical bulletins from MCSC carry implementation timelines. When a technical bulletin with a 30-day implementation deadline is delayed to 60 days because the SSgt decided the collection calendar could not accommodate the downtime, the program manager's configuration tracking database shows a fleet element that is not in compliance with the published configuration standard. The OIC who receives a program office inquiry about implementation compliance and has to ask the SSgt why the deadline was missed is not having a technical conversation. The element that cannot find 48 to 72 hours across a 30-day window to implement a technical bulletin is not managing its collection calendar — it is allowing the collection calendar to manage the element. Schedule the implementation window before the deadline.
  • Missing a Sgt section chief's clearance reportable matter because the SSgt did not build the reporting culture.
    The section chief who has a foreign national contact, a financial delinquency, or a legal incident and does not self-report because the section chief has never been briefed that immediate self-reporting is the expectation is a section chief whose matter will surface in the periodic reinvestigation. When it does, the investigation asks the SSgt whether the section chief was briefed on the clearance reporting requirement at check-in. If the SSgt cannot produce the counseling record showing the reporting brief was given, the investigation notes that the element's reporting culture was not established by the SSgt. The counseling entry at check-in that documents the clearance reporting brief is the administrative record the investigation reads.
  • Allowing a Sgt section chief to brief the intelligence officer on collection capability without preparation, because the SSgt is confident the Sgt knows the answer.
    The Sgt who briefs the intelligence officer with imprecise or inaccurate capability language — 'we can probably support that collection requirement' rather than 'we can support detection of moving ground targets at ranges up to X kilometers in open terrain with this confidence level, with these degradation caveats' — commits the element to a capability it may not have. The intelligence officer builds the collection plan on what the Sgt said. The SSgt is the Sgt's chain of command. The collection plan failure traces to the SSgt's decision to send the Sgt to the briefing unprepared. Prepare the Sgt — walk through the collection requirement, rehearse the capability language, know what the honest answer is before the Sgt walks into the room.

Career Decisions at This Rank

  • Staff NCO Academy in-residence versus distance education — managing the slot against the element's collection schedule
    SNCOAC in-residence at MCB Quantico is the GySgt board standard, and the management problem is identical to the problem the Sgt faced with Sergeants Course: the collection calendar always has a reason to defer PME. The SSgt who defers SNCOAC through two collection rotations and one deployment cycle will watch a peer with an identical FitRep profile but complete PME get selected while the SSgt is carried to the next cycle. Identify the SNCOAC course drop date 90 days out, build the coverage plan for the element's collection mission during the residential attendance, and get the OIC's approval in writing before the registration window closes. The collection mission will survive six weeks without the SSgt if the section chiefs are properly developed — and if the section chiefs are not properly developed, that is the SNCOAC attendance preparation problem the SSgt should have been solving for the previous year.
  • Warrant Officer 2610 application — at SSgt the window is open and the technical profile fits
    The WO 2610 (SIGINT/Electronic Warfare Warrant Officer) pipeline requires the technical depth, the clearance profile, and the systems advisory experience that a well-developed 2651 SSgt carries. The application requires a commanding officer endorsement, a physical fitness record consistent with continued service, a current TS/SCI clearance, and a technical background review. The honest career comparison: the 2651 SSgt who pursues the WO 2610 track transitions into a warrant officer career that operates at the operational and theater level as a technical advisor — fundamentally different from the GySgt/MSgt/SgtMaj enlisted leadership trajectory. The WO is not a promotion out of the enlisted difficulty; it is a career change into a different community with different demands, different autonomy, and different post-service market positioning. Warrant officers in the SIGINT/EW space are highly employable in the cleared contractor and IC civilian markets after service. The SSgt who is drawn to the technical advisory role at the theater level and is less drawn to the formation leadership and personnel management work of the GySgt and MSgt tracks should examine the WO 2610 application honestly. Talk to 2610 Warrant Officers at your current command before submitting the package.
  • MCSC program office liaison billet versus FMF continuation for the next SSgt assignment
    The MCSC program office liaison billet for the AN/TPS-80 G/ATOR becomes available to SSgts and GySgts who have built the program office relationship through consistent operational feedback and technical credibility. The program office billet is a Washington, D.C.-area or Quantico-area assignment; it is not a collection operations billet, and the operational pace is fundamentally different from a FMF element senior NCO tour. The honest career calculation: the SSgt who takes a program office liaison billet between FMF tours builds the acquisition and systems engineering exposure that makes the GySgt level's advisory role more technically credible — and that makes the DIA civilian, NSA civilian, and defense contractor markets more accessible after service. The SSgt who does back-to-back FMF tours without a program office billet is operationally credible but may be narrower in the advisory skills the GySgt billet requires. One program office tour in the SSgt-to-GySgt window is the standard the senior ISR NCOs recommend.
  • EAS into the DIA civilian or defense contractor market versus indefinite reenlistment to GySgt
    The 2651 SSgt with a current TS/SCI, six to eight years of G/ATOR and ground sensor experience, and a clean clearance record is entering the federal civilian and defense contractor market at the most favorable career point. DIA GS-12/GS-13 systems analyst billets, NSA technical GG-12/GG-13 positions, and defense contractor ISR systems integration roles (General Dynamics IS, Northrop Grumman Mission Systems, L3 Technologies) are all accessible with this profile. The cleared contractor market pays substantially more than SSgt base pay; the federal civilian market offers long-term stability with the clearing benefit that the SSgt has already paid for with years of careful clearance maintenance. The honest comparison with the GySgt track: the GySgt ISR advisory role and the MSgt/SgtMaj institutional contribution are different kinds of career significance than the cleared contractor or federal civilian track. Both are legitimate. The SSgt who wants to continue leading Marines and shaping the ISR collection architecture at the institutional level stays in. The SSgt who has completed the leadership obligation and wants to operate at the technical advisory level in a civilian context has a strong market. Neither choice is failure — both choices require honest self-assessment about which environment and which type of work fits the individual.
  • GySgt board fork — troop leadership track (1stSgt / SgtMaj) versus occupational SME track (MSgt / senior ISR advisor) — begins to take shape at SSgt
    The GySgt-to-MSgt/1stSgt fork in the 2651 community is the same fork it is in any SNCO community, but the technical nature of the MOS makes the occupational SME track more distinct and more institutionally valuable than in most MOS communities. The 1stSgt track (GySgt to 1stSgt to SgtMaj) is a troop leadership trajectory — company-level formations, Marine welfare, retention and personnel management, the SgtMaj of the Marine Corps sphere of influence. The MSgt track (GySgt to MSgt to MGySgt) in the 2651 community runs through senior ISR advisor billets, the schoolhouse faculty, MARFORINT senior systems advisory positions, and national intelligence center advisory roles. The SSgt who is drawn to the formation, the counseling cycle, and the institutional leadership work is building toward 1stSgt. The SSgt who is drawn to the technical advisory depth and the intelligence community interface is building toward MSgt. The fork is not final at SSgt — it rarely is — but the SSbt who has thought about it and can articulate the preference to the OIC at counseling is ahead of the one who has not. The GySgt assignment cycle will reflect the preference, for better or worse.

How the Seat Varies by Unit Type

  • Active component ISR element — Marine Unmanned Aerial Vehicle Squadron (VMU) or MEF Intelligence Group
    The VMU SSgt element senior NCO operates in a collection-tempo-driven environment where the element's system readiness posture is under continuous pressure from the supported maneuver unit's operational cycle. The VMU collection operations pace is higher than most other 2651 unit types; the SSbt who manages the fleet through a sustained MEU workup cycle without a collection gap develops fleet management skills the lower-tempo billet does not demand. The MIG SSbt element senior NCO operates at a higher staff interface level — the collection management planning cycle at MEF level is more complex and more joint than at the battalion level, and the SSbt who works the MEF intelligence staff's collection requirements process is building the advisory skills the GySgt level requires faster than the battalion-level SSbt.
  • Radio Battalion ISR element
    Radio Battalion SSbt element senior NCOs manage a field-portable, high-operational-tempo collection architecture where the systems are regularly broken down for movement and reinitialized in austere conditions. The fleet management challenge at Radio Battalion is maintenance-in-austere-conditions: systems that fail in the field, with limited maintenance support available, in a collection window that cannot wait for garrison-level maintenance response. The SSbt who builds the section chiefs' organic troubleshooting depth — so that the element can resolve organizational-level faults forward rather than evacuating systems rearward — is the SSbt who has prepared the element for Radio Battalion's actual operational demand. The advisory relationship with the intelligence officer at Radio Battalion is closer to the collection operations cycle than in MIG billets; the SSbt is advising on capability in real time, not in planning cycles.
  • MCSC program office liaison billet
    The SSbt or GySgt in the MCSC AN/TPS-80 G/ATOR program office liaison billet is working in an acquisition and sustainment context rather than a collection operations context. The daily work is technical bulletin development review, operator feedback integration into configuration change packages, operational assessment coordination with FMF elements, and program management interface with the contractors (General Dynamics, specifically — they are the AN/TPS-80 OEM). The operational pace is different from FMF; the access to the system's design, configuration, and sustainment architecture is significantly deeper. The SSbt who returns to FMF after a program office liaison billet can advise the intelligence officer and the OIC at a level of system architecture depth that the FMF-only SSbt cannot match. The program office billet is a career investment, not a break from operational work.
  • Forward-deployed element — III MEF Okinawa or MARFORACT element
    The III MEF Okinawa or forward-deployed element SSbt operates in an Indo-Pacific contingency posture context where the collection requirements reflect real regional intelligence needs rather than exercise scenarios. Partner-force exercises with the Korean Marine Corps, Japan Ground Self-Defense Force, and Philippine Marines generate joint ISR integration requirements the CONUS-based SSbt does not encounter. The collection architecture brief the SSbt gives the intelligence officer in an Okinawa billet may include liaison with Japanese intelligence elements or Korean Marine ISR coordination — a joint advisory dimension that is different from the MEF-level U.S.-only collection management process. Unaccompanied tour status for most SSbt-level assignments at III MEF — verify current policy. The operational credibility of the III MEF tour is real; the family separation cost is also real.
  • Schoolhouse instructor billet — Intelligence School or MOS school system
    The 2651 SSbt schoolhouse instructor billet is a curriculum development and instruction role — building the next generation of 2651 operators, Cpls, and Sgts against the NAVMC 3500.20 task standards. Schoolhouse SSbts develop instructional skills and curriculum design experience that the FMF-only SSbt does not carry, and the instructional credibility feeds directly into the program office liaison relationship (the program manager values the operator trainer's perspective on what the fleet actually knows how to do). The downside: schoolhouse billets can create a perception of distance from current FMF operational context if the instructor does not maintain currency through FMF augmentation or temporary assignment during collection rotations. The best schoolhouse SSbts maintain FMF contacts who keep them current on what has changed in the collection operations since the last FMF tour.

What Good Looks Like at This Rank

The good 2651 SSgt is the element senior NCO the intelligence officer calls when the OIC is at a staff meeting and the collection architecture question cannot wait — not because the SSgt is filling in, but because the SSgt's answer is the one the intelligence officer trusts. The answer the SSgt gives is the honest one: which systems are fully capable, which are degraded, what the operational impact is in terms the S-2 can act on, and what the risk is in the collection plan the intelligence officer is building against a 72-hour rotation. That answer is delivered in two minutes because the SSgt has been tracking the fleet's maintenance history and the data link topology all week, not because the SSgt prepared for this specific question. The intelligence officer who has worked with this SSgt for one deployment cycle stops treating the collection management brief as a reporting event. She starts treating it as a planning conversation. The section chiefs under this SSgt are on GySgt-competitive trajectories because the SSgt invested in the monthly counseling the same way he invested in the collection operation — with specific preparation, accurate data, and an honest assessment of where each Sgt stands against the SSgt board criteria. The Sgt whose Section A narrative this SSgt writes describes what the Sgt did in specific operational contexts, and the reporting senior signs it without revision. The relative value placement across the element's Sgts is calibrated honestly rather than uniformly inflated — the Sgt who performed best is placed correctly, the Sgt who needs to develop has a counseling record that explains why the placement is where it is. The battalion FitRep board does not revise this SSgt's Section A inputs. The MCSC program manager has this SSgt's contact information because the operational feedback the element submits after every significant collection rotation is specific, measured, and useful for configuration design decisions. When the program office is assessing whether a new configuration change produces the intended performance improvement in field conditions, they call this SSgt — not the OIC, not the battalion S-2 — because the SSgt's data is the data that reflects what the system actually does in the rain on day three of a collection rotation. That relationship is visible to the FitRep chain. The OIC who writes this SSgt's FitRep narrative has watched the program office call the SSgt directly, and the Section A that results from that observation is the kind that GySgt boards act on.

Preview — The Next Rank

GySgt is the MEF or MAGTF-level senior ISR technical advisor rank in the 2651 community — the enlisted seat at the staff-level collection management table, the NCO the MEF G-2 calls when the organic ISR collection architecture needs to be evaluated against a complex intelligence requirement. The transition from element senior NCO to senior advisor is the transition from managing a collection element's technical readiness to advising the intelligence staff on what organic ISR can and cannot do against the threat the commander is facing. The GySgt's advisory relationship with the intelligence officer is a different kind of professional relationship than the SSbt's. At SSbt, you are advising the OIC and the collection management officer at the battalion or regiment level — a relatively confined audience. At GySgt, you are advising the MEF G-2 or the MAGTF intelligence officer — an audience that briefs the commanding general. The collection architecture assessment the GySgt delivers is the assessment the intelligence officer brings to the commander's collection planning brief. The GySgt who gives an accurate assessment — honest about capability and limitation, specific about degradation tolerance and risk — is the GySgt whose assessment the intelligence officer quotes verbatim. The one who gives an optimistic assessment to avoid difficult conversations with the commanding general's staff is the one whose assessment fails under operational scrutiny. Post-service positioning at GySgt in the 2651 community is fundamentally different from most MOS communities. The GySgt with a current TS/SCI, 14 to 16 years of ground ISR systems experience, a program office relationship, and a track record of accurate collection advisory work is entering the DIA civilian GS-13/14, NSA technical GG-13, and defense contractor ISR systems integration markets at a significant premium to most enlisted veterans. General Dynamics — the AN/TPS-80 OEM — recruits 2651 GySgts and MSgts specifically. The value is not the general military experience; it is the specific combination of operational system experience, collection management advisory depth, and cleared workforce qualification. The GySgt who has built that profile deliberately — through the program office relationship, the joint ISR architecture fluency, and the collection advisory credibility — is walking into a post-service market that does not require transition assistance to navigate.
FAQ

2651 E6 — Frequently Asked Questions

Q01What does a E6 2651 (Intelligence Surveillance Reconnaissance (ISR) Systems Engineer) actually do?
You run the enlisted side of an ISR systems platoon or serve as the senior NCO for a multi-section ISR element — managing two to four section chiefs, their Marines, and the collective readiness of the collection systems across all of them.
Q02What's the most important thing to know as a E6 2651?
At SSgt you are no longer managing a single collection section — you are the technical authority the intelligence officer calls when the OIC is not available and the collection architecture is broken.
Q03What does a typical day look like for a E6 2651?
Time-blocked day at the E6 2651 rank tier: 0500 Wake. Phone check for section chief group chat — any overnight system faults, watch incidents, or personnel issues across the element. Before the daily schedule starts, you already know the element's maintenance posture better than anyone who will brief it to you, 0530 PT formation. You take accountability for the element and report to the OIC. Any missing section chief is your problem to explain before the OIC asks, 0545–0700 Unit PT. You set the physical standard for the element. On element-led PT days,…
Q04What mistakes get E6 2651 soldiers fired or relieved?
SNCOAC PME deferred through multiple board cycles because the operational calendar never clears. The GySgt board reads SNCOAC completion as a binary qualifier — complete or not. The SSgt who enters the GySgt board window without SNCOAC is not competitive regardless of FitRep quality. The 2651 occfield has no large reservoir of SSgts; every slot at the GySgt board is contested.…
Q05What career decisions matter most at the E6 2651 rank tier?
Staff NCO Academy in-residence versus distance education — managing the slot against the element's collection schedule — SNCOAC in-residence at MCB Quantico is the GySgt board standard, and the management problem is identical to the problem the Sgt faced with Sergeants Course: the collection calendar always has a reason to defer PME. The SSgt who defers SNCOAC through two collection rotations and one deployment cycle will watch a peer with an identical FitRep profile but complete PME get selected while the SSgt is carried to the next cycle. Identify the SNCOAC course drop date 90 days out,…
Q06What's next after E6 for a 2651 (Intelligence Surveillance Reconnaissance (ISR) Systems Engineer) in the Marines?
GySgt is the MEF or MAGTF-level senior ISR technical advisor rank in the 2651 community — the enlisted seat at the staff-level collection management table, the NCO the MEF G-2 calls when the organic ISR collection architecture needs to be evaluated against a complex intelligence requirement.
Q07What manuals and regulations does a E6 2651 need to know cold?
NAVMC 3500.20 — Intelligence/EW T&R Manual (platoon-level collective tasks you are building training against across multiple sections).; MCWP 2-26 — MAGTF Intelligence Operations (at SSgt you start shaping how the ISR collection plan is built, not just executing it; you need to understand the whole intelligence operations framework).; FM 3-55 — Information Collection (joint ISR doctrine;…

This playbook has no tips yet. Be the first to share what you know.

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