vBCms Comments
Welcome To Hunting Country
General Hunting Forums
Archery & Bowhunting
Shooting Sports
Manufacturers' Corner
Firearms
Classifieds
Not Hunting / General Chit Chat
1.) Bob Peck - 10/23/2017
What I thought was a 25 yard shot turned out to be 37 when I ranged it afterward and the Nikon range finder factoring in elevation. Funny thing is when I paced off the distance from the bottom of the tree to the impact it was 22 yards.
It looked like a rock solid shoulder hit with a Rage 2-blade Extreme launching from a Bowtech Guardian at 62lbs draw weight. The doe bounded off with the arrow and lighted nock bouncing up and down in the early morning light. I could have sworn I heard the final crash 50+ yards into the thick stuff. At a bare minimum I did watch the doe's body crashing through the woods and ping ponging off of trees.
I waited 1.5 hours just in case there was another shot opportunity. Nothing. I packed up and got down all cocky that I did what I practiced all year for. I took a knee as is my custom and thanked God for a great hunt and asked for a quick recovery. I was already dreaming of donating my first deer of the season (another custom).
[B][SIZE=2]The impact showed a line of fur in the direction the doe took off. It looked to me like some of the fur had been "cut" possibly by the huge cutting diameter of the broadhead[/SIZE][/B]
[B][SIZE=2]One tuft of fur had a drop or two of blood[/SIZE][/B]
[B][SIZE=2]Finding the blood trail entering into the thick stuff was time consuming and this is all I found near where the doe entered the woods. The spatter clearly from a moving deer.[/SIZE][/B]
[B][SIZE=2]Then nothing. Absolutely nothing. 1.5 hours later I resorted to a grid search and found what was left of my arrow about 20 yards in from the single drop. No nock. No broadhead.[/SIZE][/B]
[B][SIZE=2]Never in 45 years of bowhunting have I seen such a thing with regard to the arrow shaft. The broadhead had to be in bone to cause it to rip out of the shaft and sever the ferrule. You can see what's left of the ferrule inside the shaft. I have no idea why the nock was ripped out of the carbon/aluminum on the other end.[/SIZE][/B]
[B][SIZE=2]Lots of frustrating searching for the trail eventually revealed this large spot where the doe must have paused for some time (120 yards)[/SIZE][/B]
[B][SIZE=2]10 yards from this large spot was a few drops where the trail went 100% cold[/SIZE][/B]
3.5 hours later and grid search upon grid search within 20 yards then expanded to 50 revealed nothing. I took up the search again that evening with no recovery.
Of course we bowhunters replay everything over and over but I went a step further. I wanted to know not just speculate. I have never done this before but I brought a block target into the woods and placed it on the impact location, climbed in the tree and took aim again assuming a 20-yard shot. (I use a red dot heads up display vs. pins). Again, it ranged at 37 yards but paced off from the bottom of the tree at 22. When I adjusted the shot for 37 vs 20 I was dead on. Crap! I was right but oh so wrong. Based on the results of these test shots and measuring down on a full size 3D target in the backyard I don't believe I hit shoulder where I was aiming. I believe I hit just below the shoulder and in the top part of the leg but not into the chest cavity. Not a fatal hit. A chip shot turned into a bad shot and what had to be a very painful wounding. :bang:
It got dark and I decided to look for the lighted nock which was surely in the vicinity where I found the arrow shaft. Nope. Nothing.
Sometimes too much information is not a good thing. No need for sympathy. Honest. It's happened to all of us at one time or another. Wounding absolutely sucks and definitely not what we seek but we all know it comes with the territory. What is done is done and I cannot unring the bell.
You could say I should have ranged every possible shot from the tree and know my distances BEFORE I launch an arrow and you'd be right. I'm ashamed to admit I've been hunting from this particular tree for 11 years and have shot more from this honey hole that I can count. I had this or so I thought.
The moral of the story is no matter the years of experience remembering to focus on the mental aspect of our sport is just as important as the mechanical and form aspects.
Had I not been cocky and allowed overly confident musings running through my head *during* the shot the end result may have been different but then again ...
It looked like a rock solid shoulder hit with a Rage 2-blade Extreme launching from a Bowtech Guardian at 62lbs draw weight. The doe bounded off with the arrow and lighted nock bouncing up and down in the early morning light. I could have sworn I heard the final crash 50+ yards into the thick stuff. At a bare minimum I did watch the doe's body crashing through the woods and ping ponging off of trees.
I waited 1.5 hours just in case there was another shot opportunity. Nothing. I packed up and got down all cocky that I did what I practiced all year for. I took a knee as is my custom and thanked God for a great hunt and asked for a quick recovery. I was already dreaming of donating my first deer of the season (another custom).
[B][SIZE=2]The impact showed a line of fur in the direction the doe took off. It looked to me like some of the fur had been "cut" possibly by the huge cutting diameter of the broadhead[/SIZE][/B]
[B][SIZE=2]One tuft of fur had a drop or two of blood[/SIZE][/B]
[B][SIZE=2]Finding the blood trail entering into the thick stuff was time consuming and this is all I found near where the doe entered the woods. The spatter clearly from a moving deer.[/SIZE][/B]
[B][SIZE=2]Then nothing. Absolutely nothing. 1.5 hours later I resorted to a grid search and found what was left of my arrow about 20 yards in from the single drop. No nock. No broadhead.[/SIZE][/B]
[B][SIZE=2]Never in 45 years of bowhunting have I seen such a thing with regard to the arrow shaft. The broadhead had to be in bone to cause it to rip out of the shaft and sever the ferrule. You can see what's left of the ferrule inside the shaft. I have no idea why the nock was ripped out of the carbon/aluminum on the other end.[/SIZE][/B]
[B][SIZE=2]Lots of frustrating searching for the trail eventually revealed this large spot where the doe must have paused for some time (120 yards)[/SIZE][/B]
[B][SIZE=2]10 yards from this large spot was a few drops where the trail went 100% cold[/SIZE][/B]
3.5 hours later and grid search upon grid search within 20 yards then expanded to 50 revealed nothing. I took up the search again that evening with no recovery.
Of course we bowhunters replay everything over and over but I went a step further. I wanted to know not just speculate. I have never done this before but I brought a block target into the woods and placed it on the impact location, climbed in the tree and took aim again assuming a 20-yard shot. (I use a red dot heads up display vs. pins). Again, it ranged at 37 yards but paced off from the bottom of the tree at 22. When I adjusted the shot for 37 vs 20 I was dead on. Crap! I was right but oh so wrong. Based on the results of these test shots and measuring down on a full size 3D target in the backyard I don't believe I hit shoulder where I was aiming. I believe I hit just below the shoulder and in the top part of the leg but not into the chest cavity. Not a fatal hit. A chip shot turned into a bad shot and what had to be a very painful wounding. :bang:
It got dark and I decided to look for the lighted nock which was surely in the vicinity where I found the arrow shaft. Nope. Nothing.
Sometimes too much information is not a good thing. No need for sympathy. Honest. It's happened to all of us at one time or another. Wounding absolutely sucks and definitely not what we seek but we all know it comes with the territory. What is done is done and I cannot unring the bell.
You could say I should have ranged every possible shot from the tree and know my distances BEFORE I launch an arrow and you'd be right. I'm ashamed to admit I've been hunting from this particular tree for 11 years and have shot more from this honey hole that I can count. I had this or so I thought.
The moral of the story is no matter the years of experience remembering to focus on the mental aspect of our sport is just as important as the mechanical and form aspects.
Had I not been cocky and allowed overly confident musings running through my head *during* the shot the end result may have been different but then again ...
2.) DParker - 10/23/2017
I'm sorry to hear this one turn out that way, Bob. I'm dreading the day when the odds catch up with me and make me have this experience too. The only reason it hasn't happened yet is that I don't get nearly as many shooting opportunities as most of you guys do (I never saw a single deer last season, and I haven't seen one yet this season either, in spite of having been out 4 times so far). It sounds like you did everything you could to effect a recovery.
I do have a question about your distances though. You said you ranged the target at 37 yds. I took that to mean 37 yds directly from your shooting position in your tree stand to the target on the ground. Is that correct? And then you ranged the distance from the base of the tree to the target at 22 yds. A little back-of-the-napkin (OK, OK, I cheated and used a calculator) trig puts your stand about 29 yds, 2.24 ft...or a hair over 89 feet...up in the tree. So either I'm misinterpreting something in your description, or you're trying to get a nosebleed...or you're taking some really long steps when pacing the distance on the ground. My money says I'm reading something wrong. Do I win?
I do have a question about your distances though. You said you ranged the target at 37 yds. I took that to mean 37 yds directly from your shooting position in your tree stand to the target on the ground. Is that correct? And then you ranged the distance from the base of the tree to the target at 22 yds. A little back-of-the-napkin (OK, OK, I cheated and used a calculator) trig puts your stand about 29 yds, 2.24 ft...or a hair over 89 feet...up in the tree. So either I'm misinterpreting something in your description, or you're trying to get a nosebleed...or you're taking some really long steps when pacing the distance on the ground. My money says I'm reading something wrong. Do I win?
3.) Swamp Fox - 10/23/2017
I'm not following several items. You held for 37 but hit lower than expected? The target confirmed you were on at 37, i.e., what your rangefinder told you? I don't know what the explanation can be for such a variance on horizontal vs. line of sight distances, except very severe angles (and I mean VERY severe to be that far off). Have you verified your rangefinder on flat ground?
I've had a nock or two pop out at impact. Sounds like yours partially came out and then all the running and bouncing tipped 'er out. Probably right about bone and the business end of the arrow.
I've had one or two leg shots or low brisket shots like that. Similar blood trails, sparse sign, one or two beds, etc.
Not much you can do about it. I've never seen the evidence that you can recover a deer like that, even with a dog. I think she'll live to swing by the stand another day. Doesn't make it suck any less, though.
I've had a nock or two pop out at impact. Sounds like yours partially came out and then all the running and bouncing tipped 'er out. Probably right about bone and the business end of the arrow.
I've had one or two leg shots or low brisket shots like that. Similar blood trails, sparse sign, one or two beds, etc.
Not much you can do about it. I've never seen the evidence that you can recover a deer like that, even with a dog. I think she'll live to swing by the stand another day. Doesn't make it suck any less, though.
4.) Swamp Fox - 10/23/2017
[QUOTE=DParker;52571]... trig puts your stand about 29 yds, 2.24 ft...or a hair over 89 feet...up in the tree...[/QUOTE]
Or at least above the target, in the case of a steep slope ... But kudos for doing the calculation ... I wasn't gonna do it! ...LOL...
Or at least above the target, in the case of a steep slope ... But kudos for doing the calculation ... I wasn't gonna do it! ...LOL...
5.) bluecat - 10/23/2017
Sorry Bob, I know that is something that is running through your mind constantly.
When I was reading this I was wondering about the math myself as there isn't usually that big a disparity between bow to target and horizontal distance. You must have some mighty large paces.
When I was reading this I was wondering about the math myself as there isn't usually that big a disparity between bow to target and horizontal distance. You must have some mighty large paces.
6.) bluecat - 10/23/2017
x(2) + y(2) = hypotenus (2)
22 (2) + y (2) = 37 (2)
484 + y(2) = 1369
y(2) = 885
y = 29.74 yards (up in tree)
89.24 feet up tree
Yep, DP is on to something.
22 (2) + y (2) = 37 (2)
484 + y(2) = 1369
y(2) = 885
y = 29.74 yards (up in tree)
89.24 feet up tree
Yep, DP is on to something.
7.) Swamp Fox - 10/23/2017
Not that it matters, but as long as we're on an archery topic:
This is the second story I've heard about this Rage head. This one's 2.3 inches for the blades and the story I'm referring to mentioned 2 inches. Not sure if that's casual usage or really a smaller model.
[url]http://www.ragebroadheads.com/x-treme-100-grain/[/url]
Anyhoo, that story also involved a shot with far less than ideal penetration. I don't recall bone being involved, or any other circumstances, so take that for what it's worth.
Maybe people are having great luck with it on deer and big game; I don't know. It doesn't exactly strike me as a hot knife through butter, though.
This is the second story I've heard about this Rage head. This one's 2.3 inches for the blades and the story I'm referring to mentioned 2 inches. Not sure if that's casual usage or really a smaller model.
[url]http://www.ragebroadheads.com/x-treme-100-grain/[/url]
Anyhoo, that story also involved a shot with far less than ideal penetration. I don't recall bone being involved, or any other circumstances, so take that for what it's worth.
Maybe people are having great luck with it on deer and big game; I don't know. It doesn't exactly strike me as a hot knife through butter, though.
8.) Swamp Fox - 10/23/2017
[QUOTE=bluecat;52575]x(2) + y(2) = hypotenus (2)
22 (2) + y (2) = 37 (2)
484 + y(2) = 1369
y(2) = 885
y = 29.74 yards (up in tree)
89.24 feet up tree
Yep, DP is on to something.[/QUOTE]
My head hurts.
Here's how I cope: If you play with the numbers, the only way you get more than a "negligible" difference between distance ranged from elevation vs. horizontal distance at most bowhunting ranges (Eastern, anyway) is if something is very out of whack, like height or measuring error.
22 (2) + y (2) = 37 (2)
484 + y(2) = 1369
y(2) = 885
y = 29.74 yards (up in tree)
89.24 feet up tree
Yep, DP is on to something.[/QUOTE]
My head hurts.
Here's how I cope: If you play with the numbers, the only way you get more than a "negligible" difference between distance ranged from elevation vs. horizontal distance at most bowhunting ranges (Eastern, anyway) is if something is very out of whack, like height or measuring error.
9.) bluecat - 10/23/2017
Exactly, normally it's not a large enough difference to matter unless you are in the nose-bleed section.
Popcorn, peanuts, Frosty Malt, Dr. Pepper here...
Popcorn, peanuts, Frosty Malt, Dr. Pepper here...
10.) DParker - 10/23/2017
[QUOTE=Swamp Fox;52577]My head hurts.
Here's how I cope: If you play with the numbers, the only way you get more than a "negligible" difference between distance ranged from elevation vs. horizontal distance at most bowhunting ranges (Eastern, anyway) is if something is very out of whack, like height or measuring error.[/QUOTE]
Exactly. Hence my assumption that either we're misinterpreting something, or Bob fat-fingered one of the numbers....or he's 9 feet tall, which is throwing off his ground distance pacing. I mean, I've heard legends.
Here's how I cope: If you play with the numbers, the only way you get more than a "negligible" difference between distance ranged from elevation vs. horizontal distance at most bowhunting ranges (Eastern, anyway) is if something is very out of whack, like height or measuring error.[/QUOTE]
Exactly. Hence my assumption that either we're misinterpreting something, or Bob fat-fingered one of the numbers....or he's 9 feet tall, which is throwing off his ground distance pacing. I mean, I've heard legends.
11.) bluecat - 10/23/2017
12.) Swamp Fox - 10/23/2017
LOL ...
13.) Bob Peck - 10/23/2017
[QUOTE=DParker;52571]You said you ranged the target at 37 yds. I took that to mean 37 yds directly from your shooting position in your tree stand to the target on the ground. Is that correct? [/QUOTE] Yes. Correct. The Nikon range finder I use compensates for angle and supposedly delivers the "true" distance from the target. 4 sections of ladder rack @ 5' per section puts me approximately 20'+ up.
[QUOTE=DParker;52571]And then you ranged the distance from the base of the tree to the target at 22 yds. [/QUOTE]
Nope. I didn't range with optics from the base of the tree. I paced it off at very moderate steps old school style. I tried to range with the Nikon but the terrain had a contour where I couldn't get an accurate reading.
[QUOTE=DParker;52571]My money says I'm reading something wrong. Do I win?[/QUOTE] Possibly. It has occurred to me that the technology in my hand may be failing or inaccurate. Then again this honestly might just flat out might be a combination of the usual suspects like bad shot, deflection and distance miscalculation.
Went back again this morning for another go and then the wind picked up and it started raining hard. Looked overhead for turkey vultures but nada.
[QUOTE=DParker;52571]And then you ranged the distance from the base of the tree to the target at 22 yds. [/QUOTE]
Nope. I didn't range with optics from the base of the tree. I paced it off at very moderate steps old school style. I tried to range with the Nikon but the terrain had a contour where I couldn't get an accurate reading.
[QUOTE=DParker;52571]My money says I'm reading something wrong. Do I win?[/QUOTE] Possibly. It has occurred to me that the technology in my hand may be failing or inaccurate. Then again this honestly might just flat out might be a combination of the usual suspects like bad shot, deflection and distance miscalculation.
Went back again this morning for another go and then the wind picked up and it started raining hard. Looked overhead for turkey vultures but nada.
14.) Bob Peck - 10/23/2017
[QUOTE=Swamp Fox;52572]I'm not following several items. You held for 37 but hit lower than expected? [/QUOTE]
Nope. Held at 20 and ranged AFTER the shot at 37.
[QUOTE=Swamp Fox;52572]Have you verified your rangefinder on flat ground?[/QUOTE]
I did this summer in July but not recently. I guess I'll give that a try.
[QUOTE=Swamp Fox;52572]I've had a nock or two pop out at impact. Sounds like yours partially came out and then all the running and bouncing tipped 'er out. [/QUOTE]Yes. It's happened to me too but the nock end of the arrow didn't end up a clean cut look like it does just prior to insertion of the nock. The aluminum was ripped like the broadhead end. You might be right with all the bouncing around and slamming into trees the shaft tore on both ends. The section of arrow I found was only 11" of a 29" shaft.
[QUOTE=Swamp Fox;52572]I think she'll live to swing by the stand another day.[/QUOTE]
I've got enough cameras scattered around so I hope to catch some stills or video.
Nope. Held at 20 and ranged AFTER the shot at 37.
[QUOTE=Swamp Fox;52572]Have you verified your rangefinder on flat ground?[/QUOTE]
I did this summer in July but not recently. I guess I'll give that a try.
[QUOTE=Swamp Fox;52572]I've had a nock or two pop out at impact. Sounds like yours partially came out and then all the running and bouncing tipped 'er out. [/QUOTE]Yes. It's happened to me too but the nock end of the arrow didn't end up a clean cut look like it does just prior to insertion of the nock. The aluminum was ripped like the broadhead end. You might be right with all the bouncing around and slamming into trees the shaft tore on both ends. The section of arrow I found was only 11" of a 29" shaft.
[QUOTE=Swamp Fox;52572]I think she'll live to swing by the stand another day.[/QUOTE]
I've got enough cameras scattered around so I hope to catch some stills or video.
15.) DParker - 10/23/2017
[QUOTE=Bob Peck;52593]Yes. Correct. The Nikon range finder I use compensates for angle and supposedly delivers the "true" distance from the target.[/quote]
Ah, OK...I'm familiar with those types of range finders. So then it's doing the trig already, which means that what it gives you is not line-of-sight distance from you to the target, but the distance from the base of the tree you're in (assuming a tree that's more-or-less perpendicular to the ground) to your target (assuming more-or-less level ground...or at least assuming that your target is at the same altitude as the base of your tree). Or what they call "true horizontal distance". But given your later comment about a rise that prevented you from using the range finder while on the ground I'm going to guess that the 2nd assumption above might not be valid.....which is an inherent weakness of angle-compensating range finders. They don't know the relative altitude of your current location vs that of your target, and just assume that lines between you, the ground and the target all form a right triangle (or at least close enough to one for government work). In most cases that good enough. But if there's a significant slope in between the base of your tree and the target that can really throw off the calculated angle-compensated range.
[QUOTE=Bob Peck;52593]4 sections of ladder rack @ 5' per section puts me approximately 20'+ up.[/quote]
If the angle-compensated horizontal distance reported by your range finder was correct (and it sounds like it probably wasn't, given what you say about the non-level ground), that would put your direct line-of-site range at less than 2 ft greater than the true horizontal distance, which means that the angle compensation should have been essentially meaningless. It would also mean that you pacing that distance off as 22 yds confirms that you are, in fact, the Jolly Green Giant. :-)
But if the ground between your tree and the doe was as non-level as it sounds (again, unless I'm misinterpreting things) then your range finder gave you a bogus horizontal distance, which would account for the outside-the-kill-zone hit even if you made a perfect shot based on what you thought the true horizontal distance was.
[QUOTE=Bob Peck;52593]It has occurred to me that the technology in my hand may be failing or inaccurate.[/quote]
If my conclusion is correct then the information it gave you was inaccurate...not because of a malfunction, but simply due to the aforementioned inherent limitation of angle-compensating range finders not being able to take significantly non-level ground into account.
[B]Edited to add the following, and my response to it, that you posted after I started typing all that mess above:[/B]
[quote]Nope. Held at 20 and ranged AFTER the shot at 37.[/quote]
OK, I missed that too. In that case we might be looking at distance miscalculation on the part of your pacing as well, though quite possibly also largely attributable to the uneven ground.
Maybe you need to move to TX, or NE or one of the other flat-as-a-pancake states where simpletons like me don't have to deal with that sort of complexity. :grin:
Ah, OK...I'm familiar with those types of range finders. So then it's doing the trig already, which means that what it gives you is not line-of-sight distance from you to the target, but the distance from the base of the tree you're in (assuming a tree that's more-or-less perpendicular to the ground) to your target (assuming more-or-less level ground...or at least assuming that your target is at the same altitude as the base of your tree). Or what they call "true horizontal distance". But given your later comment about a rise that prevented you from using the range finder while on the ground I'm going to guess that the 2nd assumption above might not be valid.....which is an inherent weakness of angle-compensating range finders. They don't know the relative altitude of your current location vs that of your target, and just assume that lines between you, the ground and the target all form a right triangle (or at least close enough to one for government work). In most cases that good enough. But if there's a significant slope in between the base of your tree and the target that can really throw off the calculated angle-compensated range.
[QUOTE=Bob Peck;52593]4 sections of ladder rack @ 5' per section puts me approximately 20'+ up.[/quote]
If the angle-compensated horizontal distance reported by your range finder was correct (and it sounds like it probably wasn't, given what you say about the non-level ground), that would put your direct line-of-site range at less than 2 ft greater than the true horizontal distance, which means that the angle compensation should have been essentially meaningless. It would also mean that you pacing that distance off as 22 yds confirms that you are, in fact, the Jolly Green Giant. :-)
But if the ground between your tree and the doe was as non-level as it sounds (again, unless I'm misinterpreting things) then your range finder gave you a bogus horizontal distance, which would account for the outside-the-kill-zone hit even if you made a perfect shot based on what you thought the true horizontal distance was.
[QUOTE=Bob Peck;52593]It has occurred to me that the technology in my hand may be failing or inaccurate.[/quote]
If my conclusion is correct then the information it gave you was inaccurate...not because of a malfunction, but simply due to the aforementioned inherent limitation of angle-compensating range finders not being able to take significantly non-level ground into account.
[B]Edited to add the following, and my response to it, that you posted after I started typing all that mess above:[/B]
[quote]Nope. Held at 20 and ranged AFTER the shot at 37.[/quote]
OK, I missed that too. In that case we might be looking at distance miscalculation on the part of your pacing as well, though quite possibly also largely attributable to the uneven ground.
Maybe you need to move to TX, or NE or one of the other flat-as-a-pancake states where simpletons like me don't have to deal with that sort of complexity. :grin:
16.) Swamp Fox - 10/23/2017
I can't even imagine trying to pace horizontal distance if there's much of a slope. Maybe the 10th Mountain Division has a way to do it, but as a flatlander with a little time humping up and down the hollers, I wouldn't expect it can be done with any great accuracy.
I'm probably only about 90% accurate about 85% of the time to 25 yards on *level* ground, LOL.
Put that in your calculator and smoke it!
I'm probably only about 90% accurate about 85% of the time to 25 yards on *level* ground, LOL.
Put that in your calculator and smoke it!
17.) Jon - 10/24/2017
Bob, was the nock end cracked? I thought I saw a mark on it.
Sorry you lost one, seems like a hard upper leg shot that would break the broadhead off and have minimal blood like that.
Sorry you lost one, seems like a hard upper leg shot that would break the broadhead off and have minimal blood like that.
18.) Swamp Fox - 10/24/2017
Unless I'm misinterpreting the pics the way I misinterpreted the initial post, I think I see one nock end pic that's very clean except for a rip in the aluminum down the side of the shaft, and another nock end pic that's very ragged. :cf: So one combination of pics indicates (to me) the arrow was broken in two pieces -- which doesn't jibe with Bob's salvage measurements and the pic of the arrow broken all the way down at the ferrule --and another combination indicates an arrow broken in three places, in sync with the measurement.
I'm starting to think it was Colonel Mustard in the solarium with the lead pipe. :pop:
I'm starting to think it was Colonel Mustard in the solarium with the lead pipe. :pop:
19.) Bob Peck - 10/24/2017
[QUOTE=Jon;52610]Bob, was the nock end cracked? I thought I saw a mark on it.[/QUOTE]
Yes. Nock end picture above.
Based on all that was left, 11" of a 29" shaft and the fact that the broadhead end broke off with a piece of the ferrule in it I can only assume:
a. the missing 18" of arrow with fletching and nock is somewhere on the forest floor
b. the broadhead is buried securely in the bone
[QUOTE=Jon;52610]Sorry you lost one, seems like a hard upper leg shot that would break the broadhead off and have minimal blood like that.[/QUOTE]
That's what I'm thinking. I reasoned there was no pneumothorax or chest penetration because the broadhead was caught up in bone.
Yes. Nock end picture above.
Based on all that was left, 11" of a 29" shaft and the fact that the broadhead end broke off with a piece of the ferrule in it I can only assume:
a. the missing 18" of arrow with fletching and nock is somewhere on the forest floor
b. the broadhead is buried securely in the bone
[QUOTE=Jon;52610]Sorry you lost one, seems like a hard upper leg shot that would break the broadhead off and have minimal blood like that.[/QUOTE]
That's what I'm thinking. I reasoned there was no pneumothorax or chest penetration because the broadhead was caught up in bone.
20.) Jon - 10/24/2017
Tough buggers as you know. The doe I shot last week had a smashed shoulder that was completely healed (wrong of course) and she was getting along just fine on 3 legs. I can only guess that it was a car and not a bullet that did it based on no scar.
21.) Bob Peck - 10/24/2017
P.S I'm gonna be in this tree Friday morning. I'll shove a branch into the ground on the impact spot (maybe with a little trail tape on it) range it from the ground and from the stand. I'll take some more pics so our Deer CSI unit can have more accurate trajectory information. Based on my test shots from that stand last week and the distance miscalculation I'm nearly positive this was an upper leg (not shoulder) hit.
22.) DParker - 10/24/2017
[QUOTE=Bob Peck;52621]I'll take some more pics so our Deer CSI unit can have more accurate trajectory information.[/QUOTE]
I'll be standing by with my forensic sunglasses of justice.
I'll be standing by with my forensic sunglasses of justice.
23.) bluecat - 10/24/2017
I'll be boning up on some trig and getting a fresh bag of cheetos.
24.) Jon - 10/24/2017
I'll be hunting.....
25.) billy b - 10/24/2017
Sorry Bob, knowing you tells me that you did everything you could to make a clean shot and secondly everything you could to recover her. It has happened to most of us if we hunted enough.
26.) Bob Peck - 10/25/2017
[QUOTE=billy b;52638]Sorry Bob, knowing you tells me that you did everything you could to make a clean shot and secondly everything you could to recover her. [/QUOTE] Thank you sir. The empathy is much appreciated. Hope you're doing well or at least making a go of it!