This app builds a Surface Danger Zone on the map from standard range-safety tables and your firing geometry. Calculations use metric internally; choose how you want numbers displayed.
Engine and ammo database remain metric. Only labels and form conversion change.
The Learn tour tab has acronyms, modes, residual energy vs Distance X, and a step-by-step walkthrough. Full write-up: Residual energy & SDZ.
Table rows supply regulatory Distance X and ricochet geometry. A ballistic profile (BC, muzzle velocity, bullet weight, and drag function G1 or G7) unlocks metro-adjusted Distance X, Side view trajectory, and residual-energy curves. Profiles are your estimates — not certificates. Default planning still uses table Distance X. This app never authorizes a shot.
This app never authorizes a shot. Identify the target and what is beyond it.
Step 1 of 9
A Surface Danger Zone (SDZ) is the ground area that may be endangered by projectiles, ricochets, or fragments when a weapon is fired. Military range-safety tables (for example DA PAM 385-63) publish standard dimensions by ammunition type and impact medium (earth/water vs steel/concrete).
This app draws that zone on a map from your firing point (FP), true heading, left/right field-of-fire, and the selected ammo table row. It is a planning aid — not permission to fire and not a substitute for identifying your target and beyond.
If your catalog row has no · BC / Trajectory-ready badge, add a custom profile:
diameter, weight (grains), BC, and muzzle velocity. Pick G1 or
G7 to match how the BC was published (do not mix a G7 BC with the G1 drag
setting). Mass enables residual energy on Side view; BC+MV enable the trajectory itself.
Metro modes still respect the table floor unless you explicitly allow under-table. Planning
aid only — identify your target and beyond.
Toggle layers under “Map layers.” Risk analysis needs a computed SDZ first.
Save blinds, stands, camps, parking, and gates as My places (brown pins). Use a place as FP, or set FP elsewhere and still keep places on the map for awareness.
After Compute SDZ, the app checks whether any of these fall inside the red danger envelope:
Example: FP at the truck, heading through the timber, “North creek blind” inside the red polygon → you get a named conflict message. Clear people from that blind before any shot.
Live markers are green with an orange border. Conflict checks still use your computed SDZ — if a live hunter is inside your fan, you are warned. They must compute their own SDZ from their FP for their own awareness.
Research often debates whether an SDZ should end at maximum range (where the bullet can still reach the ground) or at a range where residual kinetic energy / velocity drops below some “harm” threshold.
Those are different questions. Presence (can the projectile still be there?) is not the same as severity (how hard might it hit?). Regulatory Table Distance X is a third idea: a policy envelope from the ammo table (for example DA PAM–style dimensions), not a live energy solve.
Open Side view to compare Table X, the max-range trajectory, residual energy, and terrain on one chart.
On Android Chrome, use the Install button when the browser offers it.
Centerline of firing line · true heading · max-range elev
KE markers (planning only): 200 J · substantial residual 85 J · NATO-era residual 17 J · skin rule-of-thumb
Max-range elevation is not a hunting zero. Height is AGL above FP ground MSL. Brown fill is DEM (or mock). Teal residual-energy curve and the three KE markers are research planning aids only: 200 J · substantial residual (more punch still left), 85 J · NATO-era residual (often cited in older literature), 17 J · skin rule-of-thumb (folklore, not reliable). They do not redefine Table Distance X, do not mean “safe beyond,” and ignore ricochet, eyes, fragments, and luck. Not fire control.
Saved on this device.