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!

     

Week 1 vs 49ers - "Game at a Glance" Summary


KB_fan

Recommended Posts

It's been a busy few days and I just had a chance to finalize my work on a graphic look at the Panthers vs. 49ers game this past Sunday, specifically what I call a "game at a glance" representation of the drive charts for the game.

Here are the drive charts for both teams side by side.  I'll post the individual teams' charts below, along with some commentary.  But basically, these drive charts this week are the story of the game.  There is ONE WORD that can summarize the Panthers:  OPPORTUNISTIC!!  More on that below.

2017_wk1_drivechart.thumb.png.417e8a6b83b21f25af453af9d9edcf20.png

 

 

 

Link to comment
Share on other sites

Panthers Drive Chart:

Wk1_Drives_Panthers.png.212e5569f25bf14e4cc7a25d649e032c.png

 

Pay close attention to the starting / ending positions of the Panthers drives and the outcome.

On all 4 drives the Panthers started beyond their own 40, they scored.

On 5 of 6 drives into SF territory the Panthers scored.

On both takeaways (SF turnovers), the Panthers scored.

On their two giveaways (Panthers turnovers), the Panthers defense STOPPED the 49ers from scoring.

THIS IS OPPORTUNISTIC FOOTBALL.  VERY MUCH REMINISCENT of 2015!  The defense gave the Panthers offense short fields on several occasions, and the Panthers offense capitalized.

 

Look how different the summary looks for the 49ers below:

 

Link to comment
Share on other sites

1 minute ago, Daeavorn said:

Something that worries me is that we didn't get a score on any drive that started in our territory. Only one that even barely counts is the one that started on our 45. I dont want our scoring to be dependant on creating turnovers.

I was just posting something similar. The defense really won this game hands down. Let's all hope Cam continues to get healthy and shake off the rust...because once the Panthers start playing better teams, this formula won't work as well.

Link to comment
Share on other sites

San Francisco Drive Chart:

Wk1_Drives_49ers.png.b235397250e8effb2109a39753499931.png

So, the 49ers got into Panthers Territory 5 times, but scored only ONCE.

Even on the drive that San Francisco STARTED in Panthers territory, the Panthers defense succeeded in a goal line stand, stopping SF at the 1.

SF could not capitalize on either of the Panthers 2 giveaways.

Also, note the importance of some of the Panthers field goals.  SF started 5 of its drives following kickoffs - all of which Gano booted through the end zone.  So, generally they were starting their drives from the 25 or close to it.  They only had 2 drives the entire game in which they started beyond their own 30 yard line, whereas the Panthers had 4 such drives and scored on all of them.

FIELD POSITION MATTERS!

Link to comment
Share on other sites

5 minutes ago, Daeavorn said:

Something that worries me is that we didn't get a score on any drive that started in our territory. Only one that even barely counts is the one that started on our 45. I dont want our scoring to be dependant on creating turnovers.

Not true.

We scored on two drives starting in our own territory.   Panthers drive 7 and Panthers drive 9.  Both Field Goals.

Link to comment
Share on other sites

I agree our defense won this game, but you truly can't dismiss the Panthers offense either.  Look at the nearly 7 minute drive (drive 9) in the 3rd Q. and the nearly 9 minute drive to end the game.  The Panthers offense totally controlled the field / controlled the clock, took away any chance for SF to get back in the game.

Loved it.

Link to comment
Share on other sites

32 minutes ago, KB_fan said:

Not true.

We scored on two drives starting in our own territory.   Panthers drive 7 and Panthers drive 9.  Both Field Goals.

Starting from their own 45 barely counts as starting in their own territory...that's great field position.

Link to comment
Share on other sites

I'm not trying to argue against the fact that it would be great to score when starting from our own 20.  Some games you won't get turnovers and need to be able to move the ball and score on LONG drives.  I get that!

That, in fact is exactly what Panthers did in their pivotal week 6 win against Seattle in 2015 - the game I maintain set up the 15-1 season.  Here's the Panthers' drive chart for that game (I happen to have my 2015 gamebook spreadsheet open right before me to that week, so it's fresh in my mind.)

2015_wk6_atSeattle.png.1414baabe57126cf6a1a9fda6a704ac0.png

Seattle NEVER turned over the ball.

Panthers only started once beyond their own 40...  10 of 13 drives started from the Panthers own 20 or less!

And yet, the Panthers found a way to win.  FOUR 80 yard TD drives.  It was incredible...

Yeah, I'd love to see a few more of those sometime.

But I certainly won't complain when through our defensive prowess or our opponents' stupid mistakes we get spotted 20 yards or more on a bunch of drives and get a lot of short fields!

Link to comment
Share on other sites

26 minutes ago, JB82887 said:

2015 - Week 1 vs Jaguars... Cam Newton was 18/31 for 175 yards with 1 TD and 1 INT and heated up as the season progressed.  Things will click so long as this oline remains adequate.  

That game was almost the picture perfect definition of an UN-OPPORTUNISTIC offense:

2015_wk1_atJAX.png.4889275fca088cdf28922a7330f90a8e.png

Not counting the drives that were just kneel downs to end the half / the game:

Panthers were unable to score following all 3 drives where they started beyond their own 40 (drive 2, drive 9, drive 11).

The offense failed to score following two takeaways (drive 4, drive 11).  The defense however did score with a pick 6.

Fortunately the Panthers offense was able to score on 3 drives from the CAR 7, CAR 30 and  CAR34.

That Jags game was a game where the team had to work hard to win in spite of a number of excellent field position opportunities - so almost the opposite of this seasons opener vs. San Francisco.

Link to comment
Share on other sites

Archived

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


  • PMH4OWPW7JD2TDGWZKTOYL2T3E.jpg

  • Topics

  • Posts

    • I think they are holding back to see what they have in the young guys, but I think it's a near certainty at some point they will bring someone else in. Right now (assuming we keep 5 CBs which is normal), the top 5 IMO are: 1) Jaycee Horn 2) Mike Jackson 3) Chau Smith-Wade 4) Shemar Bartholomew  5) Akayleb Evans   Obviously Jaycee is the alpha in that room and paid as such. Need him to stay healthy and continue to play at a Pro-Bowl level. Mike Jack did pretty well all things considered last year, and they gave him lower-level starter money. Fair deal for both sides.  Smith-Wade showed some promise as a slot CB. I think low-key he's a lock for the team. Different size and skill set than the other CBs. Shemar Bartholomew was the most sought after waiver claim last preseason. Was 5th CB most and inactive most of last year. Had a few defensive and ST snaps. Nothing of note good or bad but too small a sample size to make any judgment. Akayleb Evans was a 2022 4th Rounder for the Vikings. Has started 19 games (including Week 18 for the Panthers) in his career and played in 43. Was pretty good in 2023 before getting injured and falling down the depth chart last year. There's some other guys on the outside looking in, but until they show more in training camp I dont see anyway they make the 53. And only Jaycee, Mike Jack, and Smith-Wade are locks to make this roster IMO.  
    • Was just reading the Ask the Old Guy story on the team's website and was shocked to see that only two 2nd Rounders have signed so far, 30 of them haven't. That isn't normal, the Texans really screwed things up for the rest of the league, no other explanation that I can think of for 30 of the 32 picks to still be unsigned at this point.
    • They need to address CB before season starts. This is not going to cut it. 
×
×
  • Create New...