I should have said that this is a KE calculator and all you need to know is Arrow/Bullet weight and FPS. And That formula should say KE=(MV^2)/2

 

Hey...if it requires the indivudual to actual speed numbers in, rather than relying on the OL calculators...it is going to be a whole lot more accurate than those OL calculators that people rely on. :thumbs_up

 

Yes you do need to know the Actual FPS for this to work. I also forgot on the sheet to put that this is KE in Ft-Lbs, which should be standard

 

No one is interested it is FREE

 

I tried to open it but it said the formula was to long an I could not get it to work

 

I'm not sure what’s wrong I downloaded it to another comp. from here and it seemed to work I am using Microsoft 2007 but I saved it as a 97. Is it working for anyone else?

 

Holy crap. I ran it and it said my set up is only 51 ke? I knew it wasnt alot but thought it was closer to 60? Im shooting a 370 grain arrow 275fps.

 

Ya maybe I should check the math again OnTarget says 62#

 

I ran it and I got the "blue screen of death". Now my computer is telling me to kill myself!

 

sounds interesting, but ive had great results from backcountry bowhunting(google search archery fps calculator), and as long as my bow is shooting its ibo(most do), its accurate w/in a few fps

 

Kinetic Energy = speed*speed*arrow weight / 450240.

If your bow is shooting 300fps with a 400 grain arrow, your kinetic energy is 79.9ft/lbs of kinetic energy.

 

worked for me. Says if I'm shooting 260 fps and my arrow is 370 grains total i have 43.9ft/lbs of KE.

Now the problem is every other calculator says 55.6ft/lbs of KE..so i think your order of operations is wrong somewhere

 

The calculator/formula I posted ends up with 55.6ft/lbs of kinetic energy. You must have calculated wrong.

 

Ek = (1/2)mv^2...

v = 260fps (79.25mps)
m = 0.0239756kg

Ek = 75.28676 Joules = 55.5286645 foot pounds

 

Yep my math is off, had the right formula just used the wrong form of measurement I was using pounds and mph guess I should have looked into this better. Sorry, may try to fix if anyone is interested.