• If you are being asked to change your password, and unsure how to do it, follow these instructions. Click here

Flattest shooting database

fseaman.js

Well-Known Member
Joined
Dec 20, 2024
Messages
171
Location
Missouri USA
With "flattest" xxx being very popular thread type, and a personal interest, I want to make a database of searching "flattest" xxx. Along the lines of Ammoguide but with the specific goal of recording and being able to search the "flattest" xxx.

It's just an entertainment thing same as our discussions of which is flattest for xxx. This is an "old programmer" needs something to do project while it's fluffy cold and nothing more. It may never happen. It may be a stupid idea and I change my mind. Right now it's just a spreadsheet.

Years ago I wanted to break the "mile per second" barrier. It's hard, a mile per second is 5280 fps. . Not sure I want to put in the work and expense but I'm interested in the subject and how it ties into "flattest" xxx.

Most of the information to store is very straight forward, chambering/caliber, yardage, drop, time of flight. Some other things are who submitted it, factory, handload, standardized or wildcat, etc..

I want to include "Point Blank Range" but this is a bit of a snag. I don't want to recalculate every time someone searches, so I want to use a fixed size for the PBR circle or what JBM calls "Vital Zone Radius". It would be to easy to make non-sense of the data if the "Vital Zone Radius" was always different.

What "Vital Zone Radius" should I standardize on?
What searchable information would you want to see.
 
"Flattest" is a relative term, as a specific distance would need to be a parameter for all submissions.
I can think of several calibers and loads that are fairly flat to 300 or 400 yards, but they aren't the best at 600, 800 or 1,000 yards.
 
For searchable, I'd probably want available factory loads to have public "vetting." It would be cool if people could post their actual FPS vs what's on the box.

I'm guessing 257 Weatherby and the 6.5-300 Weatherby are going to be the top two for factory ammo for anything resembling a point blank range circle.

I can imagine some insanely off the chart numbers if there was a reloaded ammo database with non vetted data being uploaded. Exotic hand turned bullets in wildcats.

I wonder what a bullet would actually have to leave the barrel at to cover a full mile in one second. Since they instantly start slowing, the answer is well above 5,280 fps.

IMG_1227.jpeg
 
Last edited:
fseaman.js,

Sounds like a fun project. Everything I have is a wildcat firing Hammer bullets. Are you interested in this?
Yes. I wan't all valid data in the database. If someone wants to use to make a go of that chambering or try to beat it in that "class" that's cool.

Wildcats, factory loads, user loads should all be "categories" to compare.
 
"Flattest" is a relative term, as a specific distance would need to be a parameter for all submissions.
I can think of several calibers and loads that are fairly flat to 300 or 400 yards, but they aren't the best at 600, 800 or 1,000 yards.
That's the point. If someone wants to know the "flattest" 224 to 300 yards, it's a search. If they want to compare wildcat to standardized, it's a search. If they want to compare PBR, it's a search. Um, PBR being a challenge because what "Vital Zone Radius" to use. I like 2" radius but I'll take suggestions.

I don't want to calculate anything on the fly. All the velocities, drops and time of flight would be precalculated as part of the database entry. Just do them all from 100 to 1000. After 1000 it gets a little "odd" for flattest, though if I do it "right" it would just be data. I'm used to multi-dimensional databases. It's been a minute but it's just new versions of the old stuff. Progress vs mySQL.
 
Top