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 131A Field Artillery Technician — overview, pay, training, civilian translation, reviews
131ACW3-CW5

Field Artillery Technician

CW3 to CW5 (Senior Warrant) · Army

WO1–CW2CW3–CW5
HEADS UP

The senior 131A warrant is the FA branch's most technically credentialed fires officer — computations authority, targeting analytics, digital fires architecture — and the battalion or fires brigade's most powerful check on whether the fires plan is executable before the BCT commander receives it. If you are in this tier and you are not actively mentoring junior 131As, building the FA Technician pipeline at your echelon, and briefing limitations with the same directness you bring to capabilities, you are underperforming the seat.

The Honest MOS Read
By CW3, the Army has decided that you are not just technically proficient — you are technically credible at echelon. The WO1/CW2 warrant builds the AFATDS database and validates the fire missions. The CW3-CW5 warrant owns the fires architecture, drives the targeting cycle, and tells the commander what the digital fires picture can and cannot support before the fires plan is presented for approval. The distinction matters because the stakes at this tier are different: you are not preventing a failed workstation from taking a battery offline; you are preventing a fires plan from being briefed to a BCT commander as executable when it is not. The Warrant Officer Advanced Course at Fort Sill is the formal gate for the senior tier. WOAC takes the computational and digital-systems foundation built at the basic level and extends it into the targeting cycle at brigade and operational echelon, the joint fires integration that connects Army fires to air and naval fires through the AFATDS-to-JADOCS linkage, and the senior-warrant leadership model that the Army expects from a CW3+ 131A. The course is not easy, and it is not supposed to be — it is the credential that justifies the level of trust the battalion commander places in the 131A when the fires plan is on the table. At CW3 in a cannon battalion, the primary responsibilities look familiar but the depth is expected to be materially greater than at CW2. You are no longer being developed on the AFATDS database; you are the expert the FDC section calls when the database fails in ways the SOP did not anticipate. You are writing the SOP. You are certifying junior 131As. You are the warrant the battalion fire-direction officer brings into the targeting board to explain why the digital fires solution says what it says. The battalion commander has stopped asking whether you can certify the system — the question now is what you recommend and whether your recommendation accounts for the limitations he needs to brief to the BCT FSCOORD. At CW4 and CW5 in a fires brigade or DIVARTY, the work has expanded to the operational fires level. A fires brigade — the 17th FA Brigade at JBLM, the 18th FA Brigade at Fort Liberty, the 41st FA Brigade in Germany, the 75th FA Brigade at Fort Sill — is a HIMARS and MLRS-heavy formation whose fires architecture is measured in operational-level target sets and long-range precision effects. The 131A at this echelon administers an AFATDS network that connects to theater targeting cells, integrates with JADOCS and the joint targeting architecture, and carries PrSM and GMLRS targeting data at the sensitivity level that operational fires planning requires. The DIVARTY 131A sits at division fires, integrating the targeting cycle for a combined-arms force that may have cannon battalions, HIMARS batteries, CRAM systems, and joint fires assets all feeding the same fires picture. The career arc at this tier is not linear — some 131As stay at the battalion level through multiple assignments and become the institutional experts on digital fires in ABCT or IBCT formations; some move to fires brigade early and build the operational-level targeting experience that makes them competitive for DIVARTY or Corps fires billets; some rotate through JRTC/NTC fires cells as observer-controller-trainers, which is one of the most effective ways to understand what the FA Technician's digital fires architecture looks like when it is stressed in ways the owning unit's SOPs never anticipated. The senior 131A who has been an O/C-T at a CTC knows more failure modes than the one who never left the battalion. The mentor role is non-optional at this tier. The junior 131A who arrived at his first battalion six months ago is watching the CW3 to learn what the career looks like in five years. The FDC NCO bench is watching the CW3+ to understand whether the 131A career is worth the enlisted-to-warrant investment. The battalion commander is watching to determine whether the senior 131A is developing the human capital in the formation or just maintaining the technical systems. Building the pipeline — one junior 131A per assignment cycle with a documented development plan, a clear OER input, and a WOAC nomination in motion — is how the senior 131A warrant justifies the CW4 and CW5 progression.
Career Arc
  • 01CW2 to CW3 board: WOAC (Warrant Officer Advanced Course) completion is the gate; OER profile across the WO1/CW2 years is the input.
  • 02CW3 first tour: battalion FA Technician warrant at increased scope — senior technical certifier, targeting-cycle integration, junior 131A mentorship, FDC NCO development.
  • 03Potential broadening assignment: JRTC/NTC fires O/C-T role, fires brigade 131A billet, or DIVARTY technical fires tour at CW3/CW4.
  • 04CW4 progression: fires brigade FA Technician or DIVARTY digital fires authority; joint targeting integration (JADOCS, JFACC coordination); PrSM/GMLRS-ER targeting data management.
  • 05CW5 capstone billets: DIVARTY or Corps-level fires architecture authority; FA Technician proponency input at the Fires Center of Excellence; mentor to branch at the institutional level.
  • 06Post-retirement market: defense contractor (AFATDS technical support, fires systems integration), GS-13/GS-14 civilian in a fires-systems program office, FA Technician course instructor at Fort Sill.
  • 07CW3 to CW4 at roughly 12 years warrant officer service; CW5 consideration at approximately 18-22 years — the branch bulletin and the HRC warrant officer career manager are the authoritative sources for current timelines.
Common Screwups
  • ×Approving a fires plan as technically executable when the digital fires architecture has a known limitation that was not briefed to the battalion commander or the BCT FSCOORD. The CW3+ warrant who protects his credibility by omitting a limitation is the one the commander discovers at the targeting board when the joint fires cell asks why the data looks inconsistent.
  • ×DUI / Article 15 / drug positive — terminal for the warrant officer career, terminal for the clearance that makes the job possible, and a visible failure in a branch small enough that the battalion commander at your next assignment already knows.
  • ×Clearance problem that is not proactively managed. The senior 131A warrant who allows a financial, personal-conduct, or foreign-contact issue to develop into a clearance adjudication without getting ahead of it administratively is making a career-ending decision through inaction.
  • ×Failing to build the junior 131A pipeline. The CW4/CW5 who does not actively develop the junior warrants in the formation, who does not write detailed OER inputs, who does not have a WOAC nomination in motion for the eligible CW2 in the battalion — that warrant is leaving the branch weaker and the OER record reflects it.
  • ×Underestimating AFATDS modernization requirements. The Army's fires modernization effort — PrSM integration, potential AFATDS follow-on systems, increased targeting data sensitivity — requires the senior 131A to stay current with the AFATDS technical roadmap. The CW4 who is an expert on the current system but has not read the upgrade documentation before the upgrade arrives is the warrant who becomes a liability instead of an asset during the transition.

A Day in the Life

  • 0530PT or early show for a fires coordination meeting. The senior 131A warrant's day does not start differently from anyone else's — the battalion still runs PT.
  • 0700Hygiene, chow, commute. Overnight review: AFATDS system status log, BCT fires cell overnight messages, any targeting updates from the fires brigade or DIVARTY. By this tier the 131A has learned to read the overnight log before talking to anyone because the log tells you what actually happened while you were asleep.
  • 0800Senior warrant sync with the battalion FDO or fires brigade fires officer. At this tier the conversation is two-directional: the fires officer briefs the operational requirement, the 131A briefs the technical execution and the known limitations. The meeting is short when the system is ready and longer when it is not.
  • 0830AFATDS administration and architecture review — not performing the maintenance tasks directly but reviewing the section sergeant's maintenance log, checking the validation results from the overnight system checks, and identifying anything that needs the 131A warrant's direct attention versus the FDC NCOs' execution.
  • 1000Targeting cycle work if in a fires brigade or DIVARTY billet — D3A execution support, target nomination review, fires synchronization with the BCT fires cell or JFACC targeting staff. At the battalion level this block is technical documentation, SOP maintenance, and FDC section training management.
  • 1100Junior 131A warrant or FDC NCO development — a scheduled development conversation, a technical coaching session on a specific AFATDS function, review of the junior warrant's OER input draft, or a WOAC nomination packet review.
  • 1130Chow.
  • 1300Technical documentation and institutional development — updating the AFATDS technical annex, reviewing the fires brigade or DIVARTY SOP for fires digital architecture, engaging the Fires Center of Excellence on a system compatibility issue, or preparing input for the Fires Symposium agenda.
  • 1430Fires coordination and staff integration — sitting in the BCT or division targeting board if the assignment puts the 131A in that room, coordinating with the G-3 fires officer on upcoming exercise requirements, reviewing the targeting-cycle execution results from the last operation.
  • 1600Senior warrant administrative close-out — OER input updates for any junior warrant in the rating cycle, the systems status brief to the FDO for the next day's fires readiness picture, any personnel or administrative actions that need the 131A's signature.
  • 1700Release when ops tempo allows. Pre-exercise and deployment cycles collapse this — the senior 131A during a CTC train-up block may run evening technical validation sessions with the FDC section.
  • TOC operations (field environment)The senior 131A in a combat or training deployment is in the TOC for the duration of live fires. The schedule belongs to the targeting cycle. System failures receive the 131A's direct attention; everything else is managed through the FDC section and the junior 131A. Keep the commander's fires officer informed, brief limitations when they appear, and do not deliver a technical recommendation you are not prepared to defend in the AAR.

Weekly Cadence

The senior 131A warrant's week is shaped by the targeting cycle and the command training schedule more than by the digital systems maintenance cycle, which by this tier is a managed process rather than a personal execution task. Monday starts with the fires officer's weekly firing's readiness brief — the 131A feeds the digital fires status, the targeting-cycle readiness, and any known system limitations. Tuesday through Thursday are the execution block: targeting work if in a fires brigade or DIVARTY billet, battalion FDC section training if in a cannon battalion, junior warrant and FDC NCO development on a scheduled calendar. Friday is often the administrative and professional development day — OER inputs reviewed, WOAC nomination status checked, Fires Center of Excellence coordination if a system update or SOP change is in progress. The 131A who treats Friday as a rest day is the one whose junior warrants learn that the senior warrant does not take professional development seriously. Pre-exercise and pre-deployment periods compress everything. Six weeks out: AFATDS database build begins, architecture review initiated. Four weeks out: full validation cycle, interface testing, degraded-operations rehearsal with the FDC section. Two weeks out: pre-exercise systems check, technical certification signed. At the rotation site: the senior 131A is in the TOC for live fires and available for every firing batteries' digital fires issue that the junior 131A cannot resolve independently. The senior warrant's value in this environment is not in doing the work — it is in knowing what the work should look like and correcting it when it does not.

Key Skills — How to Drill Each

  1. 01
    Own the targeting cycle at battalion or brigade level — D3A execution, target nominations, attack guidance matrix, sensor-to-shooter timeline — and translate it into AFATDS-executable fire orders.
    Build the targeting-cycle familiarity during every battalion targeting board and BCT fires coordination meeting you attend. The senior 131A who understands the targeting cycle at the operational level — not just the digital mechanics but the decision authority, the proportionality calculation, the TSO timeline — is the warrant the fires officer trusts with the fires plan before it reaches the commander. Read JP 3-60 and the FA branch targeting publications at the chapter-and-section level, not the overview level.
  2. 02
    Certify the digital fires architecture for the battalion or fires cell — AFATDS network, AMDWS integration, JBC-P fires interface, link to BCT targeting tools — before every rotation and troubleshoot it in real time.
    The senior 131A's pre-rotation validation should be more rigorous than the junior 131A's, not less. Build a validation procedure that tests every interface in the architecture, not just the nodes you expect to cause problems. The CTC rotation that fails because of an AFATDS-to-JADOCS interface issue that nobody tested is the rotation that produces the O/C-T finding and the brigade commander's AAR comment. The interface that nobody tested is always the one that fails.
  3. 03
    Mentor junior 131A warrants and the FDC NCO bench through technical course follow-on, digital systems certification, and collective-tasks training.
    Mentorship is a skill, not a disposition. Build a specific development plan for each junior 131A warrant in the formation: where they are technically, what they need to develop for the CW3 board, what the WOAC nomination timeline looks like, and what the next assignment should accomplish. Have the development conversation on a calendar — not once at in-processing but quarterly. The FDC NCO mentorship is different: the senior 131A who earns the section's respect explains the technical work rather than doing it, and makes the section chief's job easier rather than bypassing it.
  4. 04
    Brief the battalion commander, BCT FSCOORD, or DIVARTY commander on digital fires readiness, targeting posture, and known system limitations.
    Brief limitations with the same confidence you brief capabilities. The commander who hears about a AFATDS-JADOCS interface limitation for the first time during a targeting board debrief is not the commander who trusted the 131A warrant — he is the commander who was surprised by the 131A warrant. The senior warrant who has a clean habit of briefing both what the system can do and what it cannot is the one the fires officer puts on the commander's calendar.
  5. 05
    Integrate joint targeting data — JP 3-60 nomination packages, TSO timelines, PID standards, proportionality judgments — at the operational level.
    This skill develops at the fires brigade and DIVARTY level, not at the battalion level. The senior 131A who wants to build this competency should explicitly request an assignment in a fires brigade fires cell or DIVARTY targeting element, and should read JP 3-60 and the Army's targeting publications (ATP 3-60) before reporting. The targeting-cycle vocabulary is learnable; the judgment required to apply it under time pressure in a joint fires environment requires the repetitions that only operational-level assignment provides.

Manuals & References — What Chapters Matter

  • FM 3-09 — Field Artillery Operations
    The branch doctrine document the senior 131A treats as the operating framework rather than an orientation document. The fires coordination, targeting, and digital fires C2 chapters describe the environment the CW3+ 131A operates in daily. Know the chapter structure well enough to point a junior warrant to the relevant section when he asks a technical question.
  • ATP 3-09.24 — Techniques for the Field Artillery Cannon Battalion
    The senior 131A is expected to be the battalion's technical expert on this document — not to have read it but to be able to teach it. The FDC procedures and digital integration annexes are the 131A's operational territory. The senior warrant who cannot answer questions from this document without opening it is not the technical authority the battalion commander thinks he is.
  • JP 3-09 — Joint Fire Support and JP 3-60 — Joint Targeting
    Required at the fires brigade and DIVARTY level. The joint fires integration work the senior 131A carries at CW4/CW5 connects to the joint targeting architecture these publications describe. JP 3-60 in particular is the framework for the D3A cycle at the operational level — the nomination packages, the TSO timeline, the positive identification standard, the proportionality judgment that the fires brigade or DIVARTY 131A must understand to support the targeting board.
  • ATP 3-09.60 — Multiple Launch Rocket System and HIMARS Operations
    Essential at the fires brigade level. HIMARS targeting data, safety template construction, rocket fires coordination in the AFATDS architecture — these differ from cannon fires in ways that matter for database management and fires integration. The CW3+ 131A who is assigned to a fires brigade and has not read ATP 3-09.60 before reporting is starting behind.
  • DA PAM 600-3 — Officer Professional Development and Career Management (Warrant Officer chapter)
    The senior 131A is responsible for the career development of junior 131As in the formation. DA PAM 600-3 is the framework — WOAC timing, assignment sequencing, the CW3/CW4 board criteria, the functional-area designator options at the senior end of the career. Know this document well enough to advise a junior warrant on career decisions without sending him to HRC for information you should already have.

Standards — How to Hit Each

  • WOAC complete and technical depth reflected in a CW3+ OER profile built on technical outputs.
    WOAC is the formal gate but the OER profile is what the CW4 board reads. Build the record on the things that are verifiable and meaningful: zero live-fire system failures traced to database or configuration on your watch, AFATDS documentation that the gaining unit uses after you leave, junior 131A warrants who received WOAC nominations during your assignment, FDC section certification rates that the battalion commander cited in the training brief.
  • Digital fires certification clean across every unit assignment — targeting-cycle execution accuracy, junior-131A mentorship production, FDC certification rates.
    Keep a professional development log. Document every pre-exercise validation, every live-fire certification, every AFATDS system failure and its resolution, every junior warrant you mentored and the outcome. The CW4 board reads the OER but the institutional memory of the senior 131A's career is in the formation's readiness record. Make the record legible.
  • CW4/CW5: contribution to the FA Technician community at the institutional level — Fires Symposium participation, AFATDS modernization input, instructorship at the Fires Center of Excellence if the assignment allows.
    The senior 131A warrant who has never engaged the institutional fires community is leaving a gap in the branch's technical development. Fires Symposium (Fort Sill, typically annual) is where the 131A community discusses system limitations, doctrine gaps, and modernization requirements. The CW4/CW5 who attends and contributes is investing in the branch; the one who does not attend is coasting on the branch's investment in him.

Technical Mistakes — Concrete Consequences

  • Approving a fires plan as executable when a known digital fires limitation was not briefed.
    The targeting board debrief surfaces the limitation. The BCT FSCOORD asks why the fires plan did not account for it. The battalion commander learns that the technical authority he trusted to brief limitations withheld one. The OER conversation is short and the senior warrant's career in that command is shorter.
  • Allowing the AFATDS database to persist between unit rotations without a full scrub.
    Legacy FSCMs, outdated call signs, wrong grid references — all invisible until the first fire mission of the rotation fails to route to the correct firing element or crosses a coordination line that the database shows as active and the current overlay shows as lifted. The senior 131A who arrived at the CTC rotation with a stale database does not brief the commander that the database was his problem; he discovers it when the O/C-T asks why the first mission failed.
  • Delegating the computations authority to the FDC section without performing the independent check.
    The FDC section chief is an excellent NCO but the computations authority is the 131A's signature on the certification. When the investigation finds a fire-direction error that the 131A's independent check would have caught, the investigation names the warrant who certified the data. 'The section chief said it was right' does not appear in the findings as a mitigating factor.
  • Treating AFATDS modernization as a future problem.
    The Army's fires modernization timeline is not slow. PrSM has a specific targeting data architecture. Potential AFATDS follow-on systems will have integration requirements the current system does not. The CW4/CW5 who is not current on the AFATDS technical roadmap is the senior warrant who gets surprised by a system transition that the program office and the Fires Center of Excellence have been briefing for two years. Surprise at the senior-warrant level is not an excuse — it is a finding.

Career Decisions at This Rank

  • Remaining at the battalion level versus pursuing a fires brigade or DIVARTY assignment for the CW3/CW4 tour.
    A second or third battalion assignment deepens the 131A's cannon-fires computations expertise and makes the warrant the most authoritative technical voice in the battalion, but it can also create a narrow career record if the only environment on the OER is the cannon-battalion FDC. The fires brigade or DIVARTY assignment exposes the senior warrant to the operational fires level — HIMARS targeting, joint fires integration, D3A at the theater level — and is the assignment that produces the CW4/CW5 who can brief the division commander. The question is whether the warrant is ready: a CW3 who has run two clean CTC rotations and a deployment is ready. One who has had one garrison-heavy tour and one rotation is probably better served by another battalion assignment first.
  • JRTC/NTC observer-controller-trainer tour versus an operational fires assignment.
    The O/C-T tour at JRTC or NTC is one of the most effective ways a senior 131A can build a comprehensive understanding of the FA Technician failure modes across the force — you watch every unit's digital fires architecture stress under the CTC environment, and you see every variant of the problem set that only one battalion's perspective produces. The trade-off is that the O/C-T tour is not in a brigade fires cell or DIVARTY targeting environment, and the CW4 who has been an O/C-T but has never touched a HIMARS targeting database may have gaps in the operational fires skillset. The right sequencing — battalion, fires brigade, then O/C-T, or battalion, O/C-T, then DIVARTY — is worth the conversation with the HRC warrant officer career manager.
  • CW5 and the post-retirement transition: federal civilian service, defense contracting, or FA Technician course instruction.
    The senior 131A's post-retirement market is specific but real. AFATDS technical support contracts exist through the prime contractor maintenance structure; the warrant who spent a career building expertise on the system and its successors is the one the contractor wants in the seat. Federal civilian service in a fires-systems program office — the Fort Sill-based programs, the relevant PMs at PEO Missiles and Space, the G-3 fires staffs — rewards the senior warrant's targeting-cycle and systems-integration knowledge in a GS-13/GS-14 billet. FA Technician course instruction at Fort Sill is the option that keeps the warrant inside the institutional Army after retirement, building the next generation of 131As. Start the transition conversation 36 months before retirement, not 12.
  • Engaging the AFATDS modernization process versus waiting for the upgrade to arrive.
    The Army's fires modernization is real, active, and accelerating — PrSM is fielded, LRHW/Dark Eagle programs are in test and development, and the AFATDS follow-on architecture discussions are ongoing at the Fires Center of Excellence and in the relevant program offices. The senior 131A who is engaged with the modernization process — attending the Fires Symposium, reading the program update briefs, coordinating with the Fires Center on doctrine and technical manual gaps — is positioned to be the technical authority when the new system arrives at the battalion. The warrant who waits for the upgrade to arrive is the one who becomes the most experienced person in the room on a system the battalion is about to stop using.

How the Seat Varies by Unit Type

  • Cannon battalion (ABCT — M109A7 PIM)
    The PIM is the Army's most digitally integrated self-propelled howitzer, with an on-board fire-control computer that integrates directly with AFATDS at the gun-system level. The CW3+ 131A at an ABCT battalion is managing an AFATDS architecture that includes gun-system interface layers that do not exist in towed-artillery formations. Software version management across the PIM fleet and the AFATDS workstations is a recurring technical challenge; the senior warrant who has not read the PIM technical manuals and the interface specification documents is working from incomplete data.
  • HIMARS battery or fires brigade fires cell
    HIMARS targeting is qualitatively different from cannon targeting: greater range, higher target sensitivity, more complex airspace deconfliction, and a targeting data architecture that connects to theater-level fires cells. The CW3+ 131A at a fires brigade is administering an AFATDS network with operational-level target data and coordinating with the JFACC targeting staff on airspace and fires synchronization. The battalion-level computations work is a foundation; this environment requires the operational fires vocabulary and the joint targeting framework on top of it.
  • DIVARTY fires cell
    At DIVARTY, the senior 131A is the technical fires authority for a division's fires architecture — multiple cannon battalions, HIMARS batteries, counter-rocket-artillery-mortar systems, and joint fires assets all feeding the same digital fires picture. The targeting cycle is operational, the AFATDS network is large and complex, and the briefing audience is the DIVARTY commander and the division G-3 fires officer. The senior 131A at this echelon who has not previously served in a fires brigade or the equivalent is going to have a steep learning curve on the scale and complexity of the operational fires architecture.
  • JRTC or NTC fires cell observer-controller-trainer
    The O/C-T billet at a CTC puts the senior 131A in a position to see every rotation unit's digital fires architecture stressed under the CTC environment. The value is unique: no single operational assignment produces the breadth of failure-mode exposure that an O/C-T tour provides. The trade-off is that the billet is evaluative rather than operational — the 131A is watching and coaching, not certifying fires for the supported commander. The O/C-T warrant who comes back to an operational assignment brings an understanding of what goes wrong across the force that peers who never had the O/C-T experience do not have.
  • Fires Center of Excellence institutional assignment (Fort Sill)
    An institutional assignment at the Fires Center of Excellence — FA Technician course instructor, doctrine writer, AFATDS technical advisor — is a materially different experience from operational fires. The environment is academic and developmental rather than operational, the audience is junior warrants and FA branch leadership rather than battalion commanders, and the product is course content and doctrine rather than certified fires plans. The senior 131A who does an institutional tour and returns to the operational force brings a different kind of expertise: they know what the doctrine says and where the doctrine does not match the field reality.

What Good Looks Like at This Rank

The good CW3+ 131A is not the most technically impressive person in the room — he is the most technically reliable. There is a difference. The impressive warrant explains the system with sophistication and detail. The reliable warrant certifies the system correctly, documents the certification, briefs the limitations with the same confidence he briefs the capabilities, and produces the same quality output at 0200 in a sandstorm that he produces at 1400 in a garrison conference room. Reliability is the criterion the battalion commander uses when deciding whether to brief the BCT FSCOORD that the digital fires picture is ready. What good looks like in practice at the battalion level: the AFATDS documentation is current and readable by the FDC section chief without the 131A in the room. The pre-exercise validation found the interface problem two weeks before the rotation started, fixed it, and briefed it to the FDO before the battalion commander asked. The junior 131A warrant has a development plan that includes a WOAC nomination timeline and a career-development conversation on the calendar. The FDC section chief trusts the 131A's technical judgment enough to call before the 131A's phone rings with the FDO on the other end. At the fires brigade or DIVARTY level, good looks different in scope but identical in discipline. The targeting cycle produces fires plans that the FSCOORD submits to the BCT or division commander without a technical hold. The joint fires integration — AFATDS to JADOCS, fires-cell coordination with the JFACC targeting staff — is documented and tested before the operational period. The PrSM or GMLRS targeting data is accurate, the proportionality judgment is defensible, and the fires plan accounts for both what the digital architecture can execute and what the limitations of the system require the commander to accept as residual risk. The senior 131A who can brief 'here is what the digital fires architecture can do, here is what it cannot, here is the residual risk, here is the mitigation' in a joint fires targeting board is the warrant the fires officer needs on his left when the commander asks the hard question.

Preview — The Next Rank

If CW5 is the destination, the next level is institutional rather than operational. The CW5 FA Technician warrant is typically in a Corps fires cell, a DIVARTY, or an institutional billet at the Fires Center of Excellence — the seat where the branch's technical fires expertise is converted into doctrine, course content, and mentorship of the next generation of 131As. The operational fires work at this level is the same in kind as the CW3/CW4 work but different in scale: the targeting cycle is at the Corps or Theater level, the AFATDS architecture spans a joint fires enterprise, and the briefing audience is a Corps or theater fires officer who expects the 131A warrant to brief both the capability and the known limitations without being prompted. More concretely, the approach to the CW5 milestone looks like this: a clean OER record with documented technical certification outputs across every assignment, at least one institutional contribution to the FA Technician community (Fires Symposium presentation, doctrine input, course development), a pipeline of junior 131A warrants with WOAC nominations and development plans attributed to the senior warrant's mentorship, and an active relationship with the HRC warrant officer career manager who is managing the assignment sequence that produces CW5-ready candidates. The transition conversation — what happens after retirement — starts here, not at the 12-months-to-go mark. The senior 131A who begins building the post-retirement network during the CW4/CW5 years has options. The one who starts at the 12-months-out mandatory counseling does not.
FAQ

131A CW3-CW5 — Frequently Asked Questions

Q01What does a CW3-CW5 131A (Field Artillery Technician) actually do?
By CW3 you have survived at least one CTC rotation, one deployment cycle (or its equivalent in training rigor), and the Warrant Officer Advanced Course.
Q02What's the most important thing to know as a CW3-CW5 131A?
The senior 131A warrant is the FA branch's most technically credentialed fires officer — computations authority, targeting analytics, digital fires architecture — and the battalion or fires brigade's most powerful check on whether the fires plan is executable before the BCT commander receives it.
Q03What does a typical day look like for a CW3-CW5 131A?
Time-blocked day at the CW3-CW5 131A rank tier: 0530 PT or early show for a fires coordination meeting. The senior 131A warrant's day does not start differently from anyone else's — the battalion still runs PT, 0700 Hygiene, chow, commute. Overnight review: AFATDS system status log, BCT fires cell overnight messages, any targeting updates from the fires brigade or DIVARTY. By this tier the 131A has learned to read the overnight log before talking to anyone because the log tells you what actually happened while you were asleep,…
Q04What mistakes get CW3-CW5 131A soldiers fired or relieved?
Approving a fires plan as technically executable when the digital fires architecture has a known limitation that was not briefed to the battalion commander or the BCT FSCOORD. The CW3+ warrant who protects his credibility by omitting a limitation is the one the commander discovers at the targeting board when the joint fires cell asks why the data looks inconsistent; DUI / Article 15 / drug positive — terminal for the warrant officer career,…
Q05What career decisions matter most at the CW3-CW5 131A rank tier?
Remaining at the battalion level versus pursuing a fires brigade or DIVARTY assignment for the CW3/CW4 tour — A second or third battalion assignment deepens the 131A's cannon-fires computations expertise and makes the warrant the most authoritative technical voice in the battalion, but it can also create a narrow career record if the only environment on the OER is the cannon-battalion FDC. The fires brigade or DIVARTY assignment exposes the senior warrant to the operational fires level — HIMARS targeting, joint fires integration,…
Q06What's next after CW3-CW5 for a 131A (Field Artillery Technician) in the Army?
If CW5 is the destination, the next level is institutional rather than operational.
Q07What manuals and regulations does a CW3-CW5 131A need to know cold?
FM 3-09 — Field Artillery Operations (read it end-to-end; the targeting, coordination, and fires C2 chapters are the 131A's operating environment).; ATP 3-09.24 — Techniques for the Field Artillery Cannon Battalion (the FDC bible; the senior 131A knows this document at the chapter-and-section level, not the concept level).; JP 3-09 — Joint Fire Support; JP 3-60 — Joint Targeting (required at CW4/CW5 when the seat is fires brigade or DIVARTY and the targeting chain connects to joint effects).

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