Predicted speed
282.8 fps
74.0 ft-lb · 0.523 slug-ft/s
Predicted speed
282.8 fps
74.0 ft-lb · 0.523 slug-ft/s
Target margin
+9.0 ft-lb
Against the 65.0 ft-lb goal
Required speed
265.0 fps
Needed for 416.7 gr at the current energy goal
Test arrow
416.7 gr
27.00 g · 29.0 in · 14.37 gr/in
1. Start With What You Measured
Each tab is one real arrow build with one real chrono result.
2. Enter The Build You Want To Test
This is the setup you are considering right now.
Tools
Use this when you want to translate grains to grams or check gr/in fast.
Status
Measured profiles auto-save locally. Export JSON whenever you want a portable snapshot.
3. Read The Answer
Best projected result is pinned at the top, then the full comparison table follows.
Best current profile
282.8 fps · 74.0 ft-lb · 27.00 g measured arrow
| Profile | Measured | Test result | KE | Margin |
|---|---|---|---|---|
| 278.8 fps 71.9 ft-lb | 282.8 fps +4.0 fps from measured | 74.0 ft-lb 0.523 momentum | +9.0 ft-lb |
This isolates finished arrow weight while keeping the chosen draw weight, draw length, and let-off fixed.
The dashed line is the energy goal. Profiles above it clear the target at that weight.
These equations are fixed. If mass and speed are known, energy and momentum come directly from the formulas below.
Kinetic energy
Velocity is squared, so small FPS changes can move KE sharply.
Momentum
Momentum scales linearly with both mass and speed.
Required speed
For the current test build, the threshold is 265.0 fps.
Each profile is a measured anchor. The model starts from that measured chrono result and then moves away from it using tunable sensitivities.
Measured profile The stored combination of draw weight, draw length, arrow length, arrow weight, let-off, and chrono speed.
gr/in Finished arrow grains divided by finished arrow length. This helps compare density across builds.
gpp Finished arrow grains divided by draw weight. This is still shown because many hunters use it as a floor check.
Advanced settings Model sensitivities and chart range live there so the main page stays focused on normal decision work.
The page is intentionally split into the common user path: enter measured data, enter the test build, then read the projected answer.