Estime's TD

[will6786]

from what i and a few others have been told by brisly they should limit him on punt and kick return. here is what brisly said the other reciever didnt block him so he started runnin early plus i was tired from punt return and kick return

 

[TheCusian]

But he didn't catch him. That's the difference between Estime's wheels versus some of the other WRs we've had in recent years--that play becomes a touchdown instead of getting caught from behind at the 20. He also made a smart "cut" at the very end to take away the DBs angle.

But no question--that WF defensive back [#25] was FAST.

Lemon, Sales, and West all get caught at the 30.

 

[LeMoyneCuse]

Wow. Talk about a hijacked thread.

 

[Alsacs]

Estime wasn't getting caught.

 

[dollarbill44]

we have a whole conversation about why we play soft corner, and here is one about our fastest player almost getting caught. he also got caught on jet sweep in the 1st quarter by a DE. BE is fast, and fast enough for most plays. we play soft corner because our Dbs are slower than the other teams WR. teams play press on our WR and play physical too.

He didn't get "caught" by the DE. He couldn't make it around the guy. I was disappointed in real time, but when I saw the replay, he would have had to run out of bounds to get around the guy. There is a big difference between getting caught and not being able to go around someone who had too much penetration. The DE made a good play. It's as simple as that.

But, if you want to make the argument that our fastest players are slower than the DEs on Wake, I guess I can't stop you.:noidea:

 

[SUfanNC]

If these are the issues we need to worry about than I like it!

 

[dollarbill44]

Wow. Talk about a hijacked thread.

Dungey made a helluva throw on that play, though some here were making a point (in another thread) that the pass was "behind" Estime.Oh Lord

I am excited about Dungey. I just cringe when he gets hit hard on running plays, because I don't want to revisit last year's QB carousel.

 

[upperdeck]

He didn't get "caught" by the DE. He couldn't make it around the guy. I was disappointed in real time, but when I saw the replay, he would have had to run out of bounds to get around the guy. There is a big difference between getting caught and not being able to go around someone who had too much penetration. The DE made a good play. It's as simple as that.

But, if you want to make the argument that our fastest players are slower than the DEs on Wake, I guess I can't stop you.:noidea:

no the point is he is faster than he is quick. Phillips gets around that corner.. go watch the Miller run against VT. he ran backwards to get around the DE. thats what real speed/quickness is.

 

[StanCuse44]

Lemon, Sales, and West all get caught at the 30.

Fwiw: Lemon ran a 4.59 at the NFL Combine. (I would've guessed a slower time than that for him.)

 

[StanCuse44]

I think BE's speed is more suited over forty yards rather than 100.

From Syr...com:
"...
Estime and the rest of his SU teammates were timed in the 40-yard dash at practice on Monday. He posted a video of his run on Instagram before later taking it down. He wrote that he was clocked at 4.42 seconds — a mark only 12 players beat at the 2014 NFL Draft Combine."
----
He fast.

 

[TheCusian]

Fwiw: Lemon ran a 4.59 at the NFL Combine. (I would've guessed a slower time than that for him.)

I hear ya. But I don't remember a play like that from him. He always seemed to get caught when he had to run after the catch. I love Lemon - but he was more skill, route running, hands, and moxie - than speed.

 

[xc84]

I love it when our players are "almost caught".

 

[StanCuse44]

I hear ya. But I don't remember a play like that from him. He always seemed to get caught when he had to run after the catch. I love Lemon - but he was more skill, route running, hands, and moxie - than speed.

Yeah. Lemon definitely easily gets caught on that play. Like someone else posted, probably at the 30-yd line.

 

[NineOneSeven]

Smaller, shorter strides. Built for shorter distances.

#25 was a big dude, big strides, and fast. Built for further distances once he got caught up to speed. Josh Gordon like.

 

[GoCuse14]

If the Wake Forest defender dived, he probably could have tripped him up just short of the end zone.

but he didn't. he scored. lots of nit picking going on.

 

[RICuse44]

If the Wake Forest defender dived, he probably could have tripped him up just short of the end zone.

If ifs and buts were candy and nuts we would all have a Merry Christmas- Coach Mac

 

[orangeinohio]

but he didn't. he scored. lots of nit picking going on.

Yeah, I'm not nitpicking and I'm not commenting on Estime's speed.
I've watched the game a couple times and I've seen the highlights about ten times. I noticed that it looks like the WF CB probably could have tripped him up and possibly prevented a TD if he dived.
If you disagree with that observation, that's fine.

 

[GoCuse14]

Yeah, I'm not nitpicking and I'm not commenting on Estime's speed.
I've watched the game a couple times and I've seen the highlights about ten times. I noticed that it looks like the WF CB probably could have tripped him up and possibly prevented a TD if he dived.
If you disagree with that observation, that's fine.

sorry...the nit picking comment was more just in general...not intended to be directed at you.

 

[GoCuse08]

Yeah, I'm not nitpicking and I'm not commenting on Estime's speed.
I've watched the game a couple times and I've seen the highlights about ten times. I noticed that it looks like the WF CB probably could have tripped him up and possibly prevented a TD if he dived.
If you disagree with that observation, that's fine.

I disagree...did you see the other camera angle from the front? While the defender got fairly close he wasn't as close at it looks from behind.

 

[Chip]

Yeah, I'm not nitpicking and I'm not commenting on Estime's speed.
I've watched the game a couple times and I've seen the highlights about ten times. I noticed that it looks like the WF CB probably could have tripped him up and possibly prevented a TD if he dived.
If you disagree with that observation, that's fine.

Yeah, it was just a little nerve wracking, and maybe it was the camera angle. Was thinking of McFarlane's run against them last year. Things like that rarely seem to work out for us. Maybe a corner is turned.

 

[orangeinohio]

I disagree...did you see the other camera angle from the front? While the defender got fairly close he wasn't as close at it looks from behind.

I've seen a couple angles.
Maybe Estime's move at the end foiled any chance of getting tripped up.
Regardless, it worked out pretty nicely.

 

[CusefanATL]

anyone complaining about someone simply pointing out the the brisley bear got out run is crazy. The wake defender was simply faster on that play.

And it was a straight line run until the end. If the brisley bear didnt cut back to the right at the end, he may have been tripped up similar to running from an actual bear, must run in criss crosses. Our Brisley bear took the perfect angle that required the longest distance for the wake guy to make up (which the wake guy was certainly making up distance) and then took it back to the right because he knew the wake guy couldnt react at full speed.

Its not an insult to say Brisley almost got run down. Its not like Brisley was at full speed when he caught the ball anyway. It was an awkward play. and he scored.

 

[orangenirvana]

Tim Lane and Andre Fontenette would have scored much easier.

 

[44doubledees]

Estime wasn't getting caught.

Favorite moment from the sidelines in that game after Donnie Simmons TD and they cut to Floyd Little and he spins around and gives a slap on Donnie's helmet, "way to go Donnie!". Gotta love Floyd!

 

[Jake]

FWIW, Whugham ran down #6 on the tunnel screen that looked like 6. They scored anyway, but I loved the hustle. Kids get caught a lot.