Jump to content
  • Welcome!

    Register and log in easily with Twitter or Google accounts!

    Or simply create a new Huddle account. 

    Members receive fewer ads , access our dark theme, and the ability to join the discussion!

     

CAP or Fozzy?


CarolinaNut

Recommended Posts

break out game for cap against a strong front 7 Vikings def is not as strong as ours but they are no push over either it will be a interesting game. If we win it will set us up for a nice win streak with Falcons, bucks and saints before our bye week .cards will be our next challenge after last years playoff.

Link to comment
Share on other sites

2 minutes ago, PantherPhann89 said:

After Fozzy's last outing, I'd rather see Fozzy get the lions share, CAP a few and Tolbert only on short and or goal line yardage. 

IMO Fozzy deserves quite a few carries on Sun. He averaged 6.25 yds/carry for his 16 attempts, and that's pretty impressive. Alternate him with CAP to try and keep the D off balance. 

Link to comment
Share on other sites

I expect CAP to get the bigger workload.  His pass blocking was a big issue last year and it should be better this year (at least it looked better in preseason).  Look at the 3 games without Stewart last year though.

Week 15 (77 snaps):  CAP (31 snaps) - 14-59 rushing, 2(2 targets)-34 receiving / Fozzy (23) - 2-2, 2(2)-14 / Tolbert (26) - 5-10, 0(0)-0  (Note that Newton was 8-100 rushing this game.  Tolbert got the start)

Week 16 (52):  CAP (20) - 5-49, 1(1)-7 / Fozzy (18*) - 5-32, 2(2)-6 / Tolbert (20) - 2-16, 2(3)-17 (Newton added 7-46 rushing and Cotchery was 1-16 rushing as well.  Fozzy got the start but also left this game with a high ankle sprain and didn't return until the NFC championship game)

Week 17 (64):  CAP (39) - 14-44, 2(2)-17 / Tolbert (37) - 10-59, 1(1)-5 (Newton added 6-10 rushing.  Tolbert got the start)

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


  • PMH4OWPW7JD2TDGWZKTOYL2T3E.jpg

  • Topics

  • Posts

    • If we were a solid winning organization most of us would have no problems with this selection. We would have had a capable starter in place to allow him to be eased into the rotation. If were told prior to the draft that he had been completely cleared health wise, we "probably" wouldn't have a ton of reservations about this selection. If we had picked this young man on Day 3 of the draft most of us would have no problems with this selection because we wouldn't have had to use draft capital to move up and get him. Unfortunately, none of the above were true 1)  We were a terrible team in 2023 and needed an immediate impact player. 2)  He was hurt near the the end of the 2023 NCAA season. We traded up to get him even though we knew he wasn't medically cleared to play in 2024. 3) When training camp started we were hearing stories that the knee wasn't ready. That alone should have raised some red flags. I personally would have red-shirted him in 2024 in order to have him ready for 2025. We had Chubba as our lead back and other guys to fill the #2 and #3 spots on the depth chart. There was no need to rush Brooks unto the field in 2024. Here's our draft history in the 2nd round between 2021 and 2024 2021 TMJ 2022 No draft choice. We picked Matt Corall in round 3 (#94) as our only Day 2 pick. 2023 Jonathan Mingo 2024 Jonathon Brooks. We have taken 4 skill players on Day 2 of the draft for the past 4 years who have contributed absolutely nothing to the offensive side of the football. 3 are no longer on the team. Two of them are no longer in the NFL. One  could possibly never start a game due to a knee injury. This type of poor drafting is why this team has been so bad for the entire decade. 
    • Even limited as he was I still don't think they have replaced his production, and not just the sack stats. The games Clowney missed it was very obvious what his value still was. Risky move but whatever. They only had 32 sacks last year and if that drops then it's going to get ugly. I see the improvement in run stopping but not in pass protect in any way.  
    • I have zero issues with this.  
×
×
  • Create New...