• Watch Out for Scammers!

    We've now added a color code for all accounts. Orange accounts are new members, Blue are full members, and Green are Supporters. If you get a message about a sale from an orange account, make sure you pay attention before sending any money!

AB Bullet Drop Formula

strikeeagle1

Private
Full Member
Minuteman
Feb 13, 2017
1,458
1,395
Does anyone know the actual formula used to calculate the output result "Drop (inches)" that appears in the data table generated
by AB Solution software? Thanks.
 
I don't think it's proprietary
[IMG2=JSON]{"data-align":"none","data-size":"full","src":"http:\/\/www.softschools.com\/formulas\/images\/maximum_height_formula_1.png"}[/IMG2]
[IMG2=JSON]{"data-align":"none","data-size":"full","src":"http:\/\/www.softschools.com\/formulas\/images\/maximum_height_formula_2.png"}[/IMG2]



H = maximum height (m)

v0 = initial velocity (m/s)

g = acceleration due to gravity (9.80 m/s2)

θ = angle of the initial velocity from the horizontal plane (radians or degrees)


DocUSMCRetired or BryanLitz am I close?
 
Last edited:
1+ - thanks. I am trying to reconcile output data differences. I was examining a .308 175 SMK @ 2450 fps @ 600 meters with similar atmospherics.
When I use the iPhone AB app and input the variables the data table indicates ~142" of path inches v. AB Solution where I use their custom drag curve for the same round the data table indicates ~ 182" of drop. The TOF's are virtually identical, as are vertical mil holds. I was surprised to see 40" of difference between the two solutions.
 
1+ - thanks. I am trying to reconcile output data differences. I was examining a .308 175 SMK @ 2450 fps @ 600 meters with similar atmospherics.
When I use the iPhone AB app and input the variables the data table indicates ~142" of path inches v. AB Solution where I use their custom drag curve for the same round the data table indicates ~ 182" of drop. The TOF's are virtually identical, as are vertical mil holds. I was surprised to see 40" of difference between the two solutions.

Well there may be something more to it. If the mil holds are the same and velocity is the same the drop should be the same since those are the only 2 variables in this equation. I may have the wrong formula too. I tagged Bryan and Doc, hopefully one of them will see this and give you some feedback.
 
Those formulas referenced above are partial solutions for straight forward rectilinear kinematics. I am pretty sure they are using some calculus based iterative solution sets, but a first-order approximation equation would be useful. As the TOF's are virtually identical, it implies the bullet trajectory is subjected to gravity for similar flight duration thus I was expecting closer bullet drop results.
 
Last edited:
1+ - thanks. I am trying to reconcile output data differences. I was examining a .308 175 SMK @ 2450 fps @ 600 meters with similar atmospherics.
When I use the iPhone AB app and input the variables the data table indicates ~142" of path inches v. AB Solution where I use their custom drag curve for the same round the data table indicates ~ 182" of drop. The TOF's are virtually identical, as are vertical mil holds. I was surprised to see 40" of difference between the two solutions.

Clearly an error. At that distance it's impossible to observe such difference in drop, no matter CDM or not. Are you sure you are not taking drop, in one case and path in the other?
 
Last shot you are exactly correct. I was looking right at the table headings and still didn't see that one was labeled Path and the other Drop. I have been using AB Mobile and Strelok Pro but just began using AB Solutions the other day. Which seems odd that the AB tables would be constructed differently. Now please correct any misunderstanding I have as to bullet drop / path (see below). Bullet Path v. Bullet Drop.png
 

Attachments

  • Screen Shot 2017-09-13 at 6.38.57 PM.png
    Screen Shot 2017-09-13 at 6.38.57 PM.png
    224.6 KB · Views: 78
  • IMG_6629.PNG
    IMG_6629.PNG
    112.5 KB · Views: 57
Last edited:
Strikeeagle1:

I agree, the inconsistency between the terminology in the two programs is very odd to say the least, error prone I'd say. BTW, Path is often confused and incorrectly labeled as Drop, which is, as you posted, another view of the trajectory with just a different baseline reference. Boreline vs sightline. Thanks for sharing the graph it's very helpful and I'm sure many should take a look at it.
 
I am trying to construct a diagram to illustrate most if not all the common ballistic trajectory terms. This is a prototype. Corrections welcomed.

Screen Shot 2017-09-14 at 8.51.12 AM.png
 

Attachments

  • Screen Shot 2017-09-14 at 8.51.12 AM.png
    Screen Shot 2017-09-14 at 8.51.12 AM.png
    112.6 KB · Views: 61
Last edited:
Drop is the physical drop of the bullet, uncorrected for the line of sight.

Path or Elevation is the firing solution needed to impact the target.

As far as the calculated firing solution, there is more than just drop going on. Our engine makes adjustments to the density of the air based on the bullets change in elevation. For example, if you were to tell the program you are shooting at an upward angle of 15 degrees it would account for the less dense air during the bullets flight and vice versa for downhill shooting. Just as an example of part of the complexity.
 
Last edited:
^^^ Thanks for the response.

Some additional queries.
Is the sum of the Maximum Ordinate plus the drop of the bullet below the optical axis roughly equal to the magnitude of Bullet Drop" ?
Using common gravity kinematics equation for vertical drop, Dy = 1/2*g*t^2 where "t"=TOF -0.05 gives a pretty good first-order approximation of bullet drop magnitude ?
 
Last edited:
^^^ Thanks for the response.

Some additional queries.
Is the sum of the Maximum Ordinate plus the drop of the bullet below the optical axis roughly equal to the magnitude of Bullet Drop" ?
Using common gravity kinematics equation for vertical drop, Dy = 1/2*g*t^2 where "t"=TOF -0.05 gives a pretty good first-order approximation of bullet drop magnitude ?

I don't think so since the real calcs are very involved and far from being that simple as far as I can tell.

BTW, every decent program out there acccounts, in the right way, for slope shooting, Strelok, AE, JBM, iSnipe, etc since all are based on the same engine with minor touches here and there.
 
I don't think so since the real calcs are very involved and far from being that simple as far as I can tell.

BTW, every decent program out there acccounts, in the right way, for slope shooting, Strelok, AE, JBM, iSnipe, etc since all are based on the same engine with minor touches here and there.

A number of them are based on the same type of solver (Point Mass) however to say they are based on the same engine is misleading at best. That would be like saying that a Ferrari Formula 1 V12 currently sitting on a race track is the "same engine" as a 1962 Ford Taunus V4 because they are both "V Blocks". While its true they are both V designs, they are not the same engine.
 
A number of them are based on the same type of solver (Point Mass) however to say they are based on the same engine is misleading at best. That would be like saying that a Ferrari Formula 1 V12 currently sitting on a race track is the "same engine" as a 1962 Ford Taunus V4 because they are both "V Blocks". While its true they are both V designs, they are not the same engine.

Well, I said with minor touches here and there, not "exactly the same" which is pretty much obvious. Just for the sake of comparing "similar if not equal" engines here goes a simple exercise regarding AB and Hornady solvers, in both cases with the following input. Note the 30° slope.

Honestly the minor differences shown here are academic, because we have no real world dope to confirm their respective trueness (which one is better than the other). I still wonder where AB is so different to make it "special" and please no need to mention SD and AJ, it's a moot point not worth a line to comment about for the simple reason they are not part of the 3DOF Point Mass solver that AB or Hornady (or Strelok, JBM, etc) rely upon. I see no evidence whatsoever that either AB or the other solvers (based on the same Point Mass method) are that much different.

Ballistic Coefficient: 0.5
Velocity (ft/s): 3000
Weight (GR): 155
Maximum Range (yds): 2000
Interval (yds): 100
Drag Function (): G1
Sight Height (inches): 1.5
Shooting Angle (Deg.): 30
Zero Range (yds): 100
Wind Speed (mph): 10
Wind Angle (Deg.): 90
Altitude (ft): 0
Pressure (hg): 29.92
Temperature (F): 59
Humidity (%): 0


ABHornady
RangeVelMOAWind MOARangeVelocityMOAWind MOA
030000.00.0030000.00.0
10028040.3-0.61002805-0.31.0
2002617-0.9-1.220026180.91.0
3002437-2.6-1.830024392.62.0
4002265-4.7-2.540022664.73.0
5002099-7.1-3.350021007.13.0
6001940-9.8-4.160019419.84.0
7001789-12.8-5.0700179012.85.0
8001646-16.2-5.9800164716.26.0
9001512-20.1-6.9900151320.07.0
10001390-24.4-8.01000139124.38.0
11001281-29.3-9.21100128129.39.0
12001186-34.9-10.41200118634.810.0
13001109-41.2-11.71300110841.212.0
14001047-48.4-13.01400104648.313.0
1500996-56.4-14.2150099656.314.0
1600953-65.2-15.5160095365.116.0
1700915-75.0-16.8170091674.917.0
1800881-85.7-18.0180088285.518.0
1900850-97.3-19.2190085197.119.0
2000821-109.8-20.42000822109.621.0
 
Curious why the 30 degree slope and G1 parameters were chosen for comparison.
 
Curious why the 30 degree slope and G1 parameters were chosen for comparison.

The basic purpose of the example was to debunk hype, said here before.

Any drag function will show the same output when doing the comparison, G1, G7 or else. G1 was chosen for no special reason. The reason behind the 30° slope was because, as it was stated before, AB is somehow "special" in the way it solves for uphill or downhill shooting making the necessary compensations for the incline. Well, truth be said, it's not. Period.
 
Well, I said with minor touches here and there, not "exactly the same" which is pretty much obvious. Just for the sake of comparing "similar if not equal" engines here goes a simple exercise regarding AB and Hornady solvers, in both cases with the following input. Note the 30° slope.

Honestly the minor differences shown here are academic, because we have no real world dope to confirm their respective trueness (which one is better than the other). I still wonder where AB is so different to make it "special" and please no need to mention SD and AJ, it's a moot point not worth a line to comment about for the simple reason they are not part of the 3DOF Point Mass solver that AB or Hornady (or Strelok, JBM, etc) rely upon. I see no evidence whatsoever that either AB or the other solvers (based on the same Point Mass method) are that much different.
Ballistic Coefficient: 0.5
Velocity (ft/s): 3000
Weight (GR): 155
Maximum Range (yds): 2000
Interval (yds): 100
Drag Function (): G1
Sight Height (inches): 1.5
Shooting Angle (Deg.): 30
Zero Range (yds): 100
Wind Speed (mph): 10
Wind Angle (Deg.): 90
Altitude (ft): 0
Pressure (hg): 29.92
Temperature (F): 59
Humidity (%): 0
ABHornady
RangeVelMOAWind MOARangeVelocityMOAWind MOA
030000.00.0030000.00.0
10028040.3-0.61002805-0.31.0
2002617-0.9-1.220026180.91.0
3002437-2.6-1.830024392.62.0
4002265-4.7-2.540022664.73.0
5002099-7.1-3.350021007.13.0
6001940-9.8-4.160019419.84.0
7001789-12.8-5.0700179012.85.0
8001646-16.2-5.9800164716.26.0
9001512-20.1-6.9900151320.07.0
10001390-24.4-8.01000139124.38.0
11001281-29.3-9.21100128129.39.0
12001186-34.9-10.41200118634.810.0
13001109-41.2-11.71300110841.212.0
14001047-48.4-13.01400104648.313.0
1500996-56.4-14.2150099656.314.0
1600953-65.2-15.5160095365.116.0
1700915-75.0-16.8170091674.917.0
1800881-85.7-18.0180088285.518.0
1900850-97.3-19.2190085197.119.0
2000821-109.8-20.42000822109.621.0

I input the information, given what you provided in to our solver. As you can see, the firing solution you provided, and the results given the same inputs you provided are not the same. Since firing direction was not supplied, I have also zeroed out any Coriolis Effect in this demonstration. The difference here is roughly 3 2/3rd moa. Screen Shots provided here:

[IMG2=JSON]{"data-align":"none","data-size":"full","src":"https:\/\/s6.postimg.org\/x6hnq1nxd\/image.png"}[/IMG2]

[IMG2=JSON]{"data-align":"none","data-size":"full","src":"https:\/\/s6.postimg.org\/45dbgn3hd\/image.png"}[/IMG2]


 
Last edited:
Let me clarify some points that I see as important info for the sake of fairness. BTW, I'm not trying to diminish AB, it's a fair program, just not particularly outstanding, it's just another Point Mass solver, not any better. That's all there is about the purpose after the exercise.

1) The first exercise was run with the AB program that came with the book. (superseded?)
2) In your examples AJ was factored in. Not in my sample (see below)
3) Hornady run did not accounted for the zero range, same option as in JBM ( I think Hornady should revise this asap)
4) In the following example I have corrected AB output for AJ
5) Once again, I don't see any significant difference between AB and JBM or Nimoh, so the claim that AB is somewhat "special" is quite over-exaggerated in my opinion.
Ballistic Coefficient0.500Muzzle Velocity3000 fps
Bullet Weight155 grainsZero Range100 y
Bullet Diameter0.308 inchesSight Height1.50 inches
Bullet Length1.240 inchesTwist Rate10.00 inches
Wind Speed10.00 mphHeading0 degrees
Wind Direction3 o'clockInclination30 degrees
Pressure29.92 inHgTarget Speed0 mph
Humidity0 % RHAir Density0.07654 lb/ft^3
Form Factor0.467Stability Factor (Sg)2.230
ABJBMNimoh
RangeTOFVelocityElevationWindageRangeTimeVelocityDropWindageRangeTimeVelocityDropWindage
(y)(s)(fps)(moa)(moa)(yd)(s)(ft/s)(MOA)(MOA)(yd)(s)(ft/s)(MOA)(MOA)
00.03000.0-0.40.000.03000.00.00.000.03000.00.00.0
1000.12805.00.3-0.61000.12805.30.30.61000.12806.20.30.6
2000.22618.0-0.9-1.22000.22619.7-0.91.22000.22620.5-0.91.2
3000.32441.0-2.6-1.83000.32442.1-2.61.83000.32442.1-2.61.8
4000.52270.0-4.7-2.44000.52272.1-4.72.54000.52270.5-4.72.5
5000.62108.0-7.1-3.15000.62109.2-7.13.25000.62105.6-7.13.2
6000.71952.0-9.8-3.86000.71953.7-9.84.06000.71947.7-9.84.0
7000.91804.0-12.8-4.57000.91805.8-12.74.97000.91797.4-12.84.9
8001.11665.0-16.2-5.38001.11666.2-16.15.88001.11655.6-16.15.8
9001.31535.0-19.9-6.29001.31535.8-19.96.89001.31523.4-19.96.8
10001.51415.0-24.2-7.110001.51415.7-24.17.810001.51402.6-24.27.9
11001.71308.0-29.0-8.111001.71307.4-28.98.911001.71295.1-29.19.0
12001.91214.0-34.4-9.112001.91212.5-34.310.112001.91202.9-34.610.2
13002.21135.0-40.5-10.113002.21132.6-40.511.313002.21127.7-40.811.5
14002.51071.0-47.4-11.214002.51067.8-47.312.614002.51067.8-47.812.7
15002.71019.0-55.1-12.215002.71015.4-55.013.815002.81018.8-55.513.9
16003.0976.0-63.6-13.216003.0971.7-63.515.016003.1977.1-64.115.1
17003.4937.0-72.9-14.117003.4933.8-72.916.217003.4940.4-73.516.3
18003.7904.0-83.1-15.118003.7900.1-83.217.418003.7907.0-83.817.5
19004.0873.0-94.2-15.919004.0869.3-94.318.619004.0876.2-94.918.6
20004.4845.0-106.1-16.820004.4840.8-106.419.720004.4847.3-106.819.7
 
Last edited:

The first table that was published clearly said Hornady, and matched the results that I was able to pull from Hornady's website. While the AB Table did not. AJ was factored in (see in the table where you -0.3 at your zero range). Hornady didn't account for the zero range? AJ is present in both solutions. You can clearly see the table lines up, with a zero range of 100 yards. How did you "correct" the AB output for AJ? Did you simply remove the wind to see how the results changed?

In your second example, I simply went to the last number. Which is 106.1, however I did provide a screen shot of the solution which shows uncorrected for AJ it should be 105.93. Small difference, but when the numbers don't match, it calls in to question the other information. No need to worry about breaking it down, when the information doesn't line up in either case by looking at only 3 numbers in the data.
 
The first table that was published clearly said Hornady, and matched the results that I was able to pull from Hornady's website. While the AB Table did not. AJ was factored in (see in the table where you -0.3 at your zero range). Hornady didn't account for the zero range? AJ is present in both solutions. You can clearly see the table lines up, with a zero range of 100 yards. How did you "correct" the AB output for AJ? Did you simply remove the wind to see how the results changed?

In your second example, I simply went to the last number. Which is 106.1, however I did provide a screen shot of the solution which shows uncorrected for AJ it should be 105.93. Small difference, but when the numbers don't match, it calls in to question the other information. No need to worry about breaking it down, when the information doesn't line up in either case by looking at only 3 numbers in the data.

Of course it's Hornady, no mistake here. Just read my comment about how I think it's working. You can try that yourself.

I don't have the AB package, which, as posted, shows essentialy the same solution as the free online one. In the AB package you can clearly see that Drop was adjusted by AJ. So, what I did was just to remove it. Nothing fancy. I think my notes were clear enough, if not let me know.

BTW, unfactoring AJ is extremely simple and it's not wind-related.
 
Last edited: