Playing its biggest game in years, Pitt arrived at Heinz Field Thursday night hoping to establish itself as the favorite in the ACC Coastal race.
Instead, North Carolina put out notice that the road to the conference championship game might run through Chapel Hill.
The Tar Heels rode a fast start and stifling finish to a 26-19 win, tempering Pitt’s early season success in Pat Narduzzi’s first season on the sideline.
“That was a tough one out there,” Narduzzi said. “I told the kids afterwards, you’ve got to play great for 60 minutes. I think as a football team overall, we started slow. I think we played a little bit better in the second half.”
North Carolina jumped out to a 20-3 halftime lead, and was able to hold on as Pitt made a few stop-and-start comeback attempts after the break.
Pitt’s defense rose to the occasion in the second half, holding the Tar Heels to just six points after the break, but the Panthers’ offense just couldn’t find a rhythm to get back in the game.
Read More
“I don’t know if were in rhythm all day, to be honest with you,” Narduzzi said.
Pitt found the end zone for their first touchdown of the game with 4:10 left in the their quarter when Qadree Ollison capped off a 13-play, 75-yard drive with a four-yard touchdown run that cut the score to 23-13.
They added another touchdown on a six-yard pass from quarterback Nate Peterman to Scott Orndoff with 46 seconds left to make it a one-score game, but couldn’t recover the ensuing onside kick to get a chance at the tie.
While Pitt’s methodical offense was perfect for grinding out late wins against Georgia Tech and Syracuse in recent weeks, it struggled playing from behind after the Tar Heels’ fast start.
Quarterback Nate Peterman finished 27 of 42 for 262 yards, but took five sacks. The running back duo of Qadree Ollison and Chris James combined for 98 yards on the ground, but the Panthers couldn’t find the big play needed to spark a comeback.
“There are a few plays in the fourth quarter I wish I could have back because I think I could put our team in a better position to win,” Peterman said.
Pitt had a chance to turn the momentum in a major way earlier in the second half, too. The Panthers blocked a punt that gave them the ball at the North Carolina 15-yard line, but two runs and a sack led Pitt to a 3-and-out of its own, and the Panthers were forced to settle for a 29-yard Chris Blewitt field goal to make the score 20-6.
“We knew we had to get touchdowns in the red zone, and with the special teams putting us in a good position, we’ve got to come away with seven there,” Peterman said.
It wasn’t the first time Pitt failed to take advantage of a big opportunity Thursday night.
The Panthers opened the game with a 14-play drive that ate up 8:19 of clock, but were forced to settle for a 44-yard Chris Blewitt field goal. North Carolina answered back with a field goal of its own on the next drive, and Pitt never led again.
“Tough to win a game kicking field goals,” Narduzzi said.
The Tar Heels pulled ahead early in the second quarter, when North Carolina quarterback Marquise Williams hit Ryan Switzer for a 71-yard touchdown pass.
William vexed the Pitt defense all game. He completed 14 of 23 passes for 270 yards and two touchdowns, and added 52 yards on the ground. Most importantly, he always seemed to make a play when North Carolina needed it.
For the second year in a row, Pitt couldn’t seem to bring Williams down in key situations. The Panthers didn’t register a sack on the afternoon, making the third consecutive in which they’ve struggled getting pressure on the quarterback.
“Sometimes [the pass rush] was good and we missed tackles, sometimes [the pass rush] was awful,” Narduzzi said.
Even with the loss, Pitt is by no means out of the ACC Coastal race. The Panthers play Duke (6-1, 3-0 ACC) in two weeks, and the Tar Heel face the Blue Devils next week. If the Panthers can win in Durham and Duke takes down the Tar Heels, Pitt is right back in the mix.
Sam Werner: swerner@post-gazette.com and Twitter @SWernerPG





Comments
Welcome to Post-Gazette subscriber-only commenting community. Please review our community guidelines.