Separate target finding from shot correction
A counter-battery task can fail at two different points: the working target location may be wrong, or the firing solution may be wrong for a correctly located target. Diagnose those separately so a bad map reference is not mistaken for a bad elevation input.
- Target not visible or not confirmed: return to the mission wording, observation point, and two-reference trace.
- Target area is plausible but the round is consistently long or short: inspect range, map scale, and elevation state.
- Target area is plausible but the round is left or right: inspect the observation point and lateral reference.
- Results change direction between shots: stop changing multiple inputs and repeat one controlled record.
First answer 'where is the working target?' Then answer 'what changed the impact?'
Use a three-pass fault check
Pass one checks the mission and target identity. Pass two checks the map measurement and observation point. Pass three checks the shell and firing inputs. Keep the passes separate so each result narrows the fault instead of adding another guess.
- Pass one: write the exact task context and the target reference used.
- Pass two: preserve map scale, both references, and the working intersection.
- Pass three: record shell, elevation state, range, and impact classification.
When the mission does not complete
Do not assume that a near miss or an unverified target effect counts as completion. Record what the interface visibly confirms, then check whether the task requires a specific target, shell, order, or follow-up state in the current build.
Current-build boundary
Exact counter-battery target locations, completion triggers, shell requirements, and numeric corrections remain pending direct testing. This page provides a fault-isolation route and points to the source material; it does not copy a fixed mission solution from another guide.