Field Artillery Technician

You are the FA battalion's digital brain and computations authority. The FDC NCOs run the floor; you are the warrant who tells the battalion commander whether the fire-control solution is correct before the first round leaves the tube.

You came up through the 13B, 13F, 13R, or 13M enlisted pipeline and you just completed the Warrant Officer Basic Course at Fort Sill under the 428th Field Artillery Brigade and the Fires Center of Excellence — roughly 17 weeks of FA Technician Course instruction covering fire-direction computations, AFATDS system administration, fire support coordination measures, digital systems integration, and the targeting-cycle vocabulary (D3A) at the technical depth the officer-basic course does not reach. You sit inside the battalion or brigade fire-direction element, operating and administering AFATDS, validating fire missions mathematically, integrating AMDWS (Advanced Field Artillery Tactical Data System and Air and Missile Defense Workstation) data feeds, and certifying the digital fires architecture before the battalion goes to the field. You are the battalion commander's go-to authority on whether the fire-control solution is right. In garrison you manage the AFATDS network, maintain digital-system documentation, build the database prior to exercises, run the systems check against FM 3-09 and ATP 3-09.24 standards, and write the battalion's digital-systems SOPs. In the field you live in the TOC, own the FDC digital architecture, validate missions in real time, troubleshoot system faults under fire, and keep the AMDWS data current so the BCT can see the whole fires picture.

• 01Administer and troubleshoot AFATDS at the database-administrator level — build the unit database from scratch, manage the message editor, diagnose system faults, recover a crashed workstation mid-exercise without pulling the battalion off mission.
• 02Validate fire-direction computations manually against the digital solution — quadrant, charge, deflection, fuze setting — to confirm the AFATDS output is correct before fire-for-effect.
• 03Build and maintain the digital fires architecture for the battalion — AFATDS network topology, message routing, AMDWS integration, radio communications interface — and document it in a technical annex the FDC NCOs can execute.
• 04Apply all fire support coordination measures (FSCL, CFL, NFA, RFA, ACA, SHORAD ID) inside AFATDS with zero input errors — a wrong FSCM in the system is a blue-on-blue waiting to happen.
• 05Certify the FDC section's digital readiness prior to live-fire events and CTC rotations — every firing element confirmed in the net, every radar interface validated, every database field scrubbed.
• 06Translate digital-system failures into actionable mission-degraded solutions — manual-fallback procedures, analog redundancy, BCS cross-check — so the battery keeps shooting when the network goes down.

• —FM 3-09 — Field Artillery Operations (the branch doctrine spine; the 131A warrant reads the fires C2 and targeting chapters more than any other).
• —ATP 3-09.24 — Techniques for the Field Artillery Cannon Battalion (FDC procedures, digital integration, the battalion fires cycle).
• —ATP 3-09.50 — The Field Artillery Cannon Battery (battery-level fire-direction procedures; the 131A lives and dies by this document in the field).
• —TC 3-09.81 — Field Artillery Manual Cannon Gunnery (the mathematical foundation; if the AFATDS output disagrees with the manual solution, the manual is your ground truth).
• —ATP 3-09.32 — Fire Support for the Brigade Combat Team (the targeting and FSCM framework the 131A operates within).
• —AR 350-1 — Army Training (training management; the 131A writes and manages the FDC section's collective-task training requirements).

• —FA Technician Course complete at Fort Sill (428th FA Brigade, Fires Center of Excellence) — the technical credential that makes you the battalion's computational authority.
• —AFATDS certification — the battalion fire-direction system configured, tested, and documented before every major exercise; zero first-round system failures at a CTC rotation for causes traced to database or configuration.
• —Warrant Officer Basic Course (WOBC) complete; WOE (Warrant Officer Evaluation) profile across the junior technician career built on technical outputs: system uptime, fire-mission accuracy rate, digital-integration readiness reports.
• —Security clearance current and adjudicated — AFATDS and AMDWS handle classified fire-control and targeting data; a lapsed clearance pulls you off the systems that define your career.
• —ACFT pass at warrant officer standard; 131A warrants operate under the same physical standards as the rest of the FA force.

• —Pushing a fire-for-effect mission without validating the digital solution against the manual check. AFATDS is accurate when the database is right; it faithfully propagates errors when it is not — and the 15-6 names the warrant who approved the data.
• —Letting the AFATDS database go stale between exercises. A database built for the last CTC rotation with wrong grids, wrong call signs, or outdated FSCM entry is how a fire mission hits the wrong grid in the first 30 minutes of a rotation.
• —Treating AMDWS interface failures as "the radio guys' problem." The fires and air-defense integration is owned by the 131A — if the SHORAD track data is not flowing into the fires picture, that is your system to fix, not the ADA warrant's.
• —Bypassing the FDC chief to go directly to the battery commander when the digital system fails. The FDC NCO chain runs the floor; your job is to solve the technical problem and brief the chain, not to own the radio.
• —Signing off the pre-exercise systems check without running the full message-editor validation. A missed required field in the AFATDS database is invisible until the unit is in the field and the fire mission fails to route.

The good junior 131A is the warrant the battalion fire-direction officer and the battalion commander walk past without stopping, because if the digital system were broken, the FA Technician would have already briefed it. Their AFATDS database is built, validated, and documented before the battalion moves to the assembly area; their FDC NCOs can back-brief the system architecture without coaching; and the BCT fires cell names their battalion as "digital-ready" on the pre-rotation slide.

You are the battalion's technical conscience and the targeting cycle's computational authority. The battalion commander signs the fire orders; you are the warrant who tells him whether the targeting solution, the fire plan, and the digital architecture are legally and mathematically sound before he signs anything.

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. You have shifted from administering the system to owning the battalion's technical fires certification — computations authority, targeting analytics, fire support coordination integration, and the digital fires architecture that connects AFATDS to the BCT fires picture, the AMDWS air-defense feed, and the joint targeting chain (F3EAD). You sit at battalion or brigade fires cell level. At battalion: you are the technical certifier for all fire missions, the AFATDS network authority, the fire-direction training manager, and the officer the battery commanders call when the system is broken and time is short. At brigade fires cell: you extend the targeting cycle — target nominations, D3A execution, digital-integration of all fires assets (cannon, rocket, mortars, CAS, naval fires when applicable) into a single synchronized fires picture. Senior 131As (CW4/CW5) sit at division artillery (DIVARTY), at fires brigade (the FA brigade at echelon-above-division — HIMARS and MLRS-heavy formations), or at Corps-level fires cells where the targeting cycle is measured in joint effects against operational-level targets. You write the battalion's digital fires SOP, you certify new 131As arriving from the FA Technician Course, you mentor the FDC NCO bench, you build the FA Technician pipeline into the brigade, and you brief the brigade commander on digital fires readiness with the same directness you brought to the battalion-level work — because the BCT commander's expectation of the 131A did not change; the stakes just got larger.

• 01Own the targeting cycle at battalion or brigade level — D3A (Decide, Detect, Deliver, Assess) execution, target nominations into the BCT targeting board, attack guidance matrix inputs, sensor-to-shooter timeline management — and translate it into AFATDS-executable fire orders.
• 02Certify 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 when the architecture fails during a live-fire event.
• 03Validate fire-direction computations for all cannon fires at battalion level (and rocket fires at brigade level) — manual check against digital solution, charge selection, fuze selection for the target type, safety-T card — as the computations authority the battalion commander relies on.
• 04Mentor junior 131A warrants and the FDC NCO bench through the FA Technician technical course follow-on, the digital-systems certification, and the battalion's collective-tasks training program.
• 05Brief the battalion commander, BCT FSCOORD, or DIVARTY commander on digital fires readiness, targeting-cycle posture, and known digital-system limitations in language that translates into a decision without requiring the briefer to repeat himself.
• 06Integrate joint targeting data (JP 3-60, JP 3-09) into the battalion or fires-brigade fires cell — nomination packages, TSO (Time Sensitive Targeting) timelines, positive identification standards, proportionality judgments — at the operational level a CW4/CW5 is expected to carry without coaching.

• —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).
• —ATP 3-09.60 — Multiple Launch Rocket System and HIMARS Operations (the fires-brigade and senior 131A seat includes rocket-fires integration).
• —ATP 3-09.32 — Fire Support for the Brigade Combat Team (the BCT fires cycle is the frame around which the 131A's daily work is organized).
• —DA PAM 600-3 — Officer Professional Development and Career Management (Warrant Officer chapter); the current HRC FA warrant officer career branch bulletin for 131A professional development milestones.

• —Warrant Officer Advanced Course (WOAC) complete; the technical depth the Army expects from a CW3+ 131A is the advanced-course output, not the basic-course output.
• —Digital fires certification track across every unit assignment — zero CTC rotations where digital-system failure was traced to a configuration or database error the 131A signed off on.
• —Targeting-cycle certification at the appropriate echelon — battalion, fires brigade, DIVARTY, or Corps — with a documented record of fires plans that executed cleanly against the BCT or division targeting board requirements.
• —Evaluation report (OER, Warrant Officer equivalent) profile reflecting technical fires outputs: system readiness rates, targeting-cycle execution accuracy, junior-131A mentorship production, FDC certification rates.
• —For CW4/CW5 at senior fires billets: attendance at fires-branch professional forums (Fires Symposium, FA School senior-leader events) and demonstrated ability to brief DIVARTY or Corps commanders on digital fires modernization (AFATDS follow-on systems, PrSM targeting integration, LRHW/Dark Eagle operational data requirements).

• —Delegating the computations authority to the FDC NCOs without performing the independent check. The 131A's signature is on the technical fires certification; if the FDC chief's numbers were wrong and the 131A did not catch it, that is the 131A's finding in the AAR.
• —Allowing the AFATDS database to persist between unit rotations without a full scrub. Grid data, call-sign data, FSCM entries, and radio-interface configurations that were valid for the last CTC rotation are data-poisoning hazards for the next one — the senior warrant who inherits a dirty database and launches anyway owns the first-round failure.
• —Treating the junior 131A warrant as purely technical support and not as a leader being developed. The CW3+ is the mentor the junior warrant is watching; the 131A who does not write thoughtful OER inputs, have career-development conversations, and push the junior warrant into stretch billets is leaving the branch weaker.
• —Confusing being the technical authority with being the tactical authority. The battalion fire-direction officer or BCT FSCOORD makes tactical decisions; the 131A provides technical certification. When those two roles collapse into one, the battalion commander loses a check — and checkride-equivalent audits of fire missions have found exactly this failure pattern.
• —Building a fires plan for a new system (PrSM, LRHW, GMLRS-ER) without reading the applicable AFATDS technical manual updates and the system's targeting-data requirements. Senior 131As who build fires plans using legacy-system assumptions on new-system hardware create mission failures that are invisible until the round does not show up where the targeting solution said it would.

The good senior 131A is the technical fires warrant the battalion commander puts in the TOC before any live-fire event — not because the FDC NCOs cannot run the floor, but because when the 131A has signed the technical certification, everyone in the chain sleeps a little better before H-hour. Their AFATDS database is documented, testable, and auditable. Their FDC NCO bench can explain every field in the AFATDS message editor without paging the warrant. The junior 131As they mentor arrive at their first CTC rotation knowing what the database needs to look like before the battalion crosses the line of departure. At the brigade fires cell or DIVARTY, the good senior 131A is the warrant the targeting board relies on to tell them whether the fires plan is technically executable before the BCT commander receives it. They know where the digital integration fails between systems, they have already built the fallback, and they brief both the capability and the limitation with equal directness. The targeting officer who only briefs what the system can do and never briefs what it cannot is the one the commander finds out about when the first TSO mission fails to execute on timeline.