Pitt notebook: Chryst was playing for TD late in Duke loss |

Pitt notebook: Chryst was playing for TD late in Duke loss

Chaz Palla | Trib Total Media
Pitt running back James Conner stiff-arms Duke's Breon Borders in the fourth quarter Saturday, Nov. 1, 2014, at Heinz Field. The Blue Devils won 51-48 in two overtimes.

Pitt coach Paul Chryst said Wednesday he wanted to break the tie against Duke with a touchdown in the final 22 seconds of the fourth quarter, a decision that ultimately forced kicker Chris Blewitt to attempt — and miss — a 26-yard field goal from the right hash mark.

Blewitt hooked it wide left, and Pitt (4-5, 2-3) ended up losing 51-48 in double overtime Saturday, eliminating any realistic chance of winning the ACC Coastal Division and lessening hopes for a bowl bid.

“At that point there were 22 seconds left, still had a timeout. We were still trying to see if we could win it without having to kick a field goal,” said Chryst, aware Pitt had allowed a kickoff return for a touchdown earlier in the second half.

But quarterback Chad Voytik, who was tackled in bounds after a 3-yard run to the right, said the intention wasn’t to score a touchdown.

“No, I don’t think so,” he said. “We were just trying to run the clock down for the field goal.”

Perhaps Chryst’s wish to score a touchdown didn’t reach Voytik, who had finished an 11-yard run on the previous play. Chryst said he wanted Voytik to get out of bounds, run another play to center the football with the uprights, call a timeout and kick the field goal with a comfortable amount of time on the clock.

“If you say you would like to have one spot to kick a field goal, you would say you would like it in the middle,” Chryst said.

“When it doesn’t work, obviously, you are susceptible to being second-guessed, and I get it. And so be it.”

Miller’s take

Former NFL punter and holder Josh Miller, who spent 12 years with the Steelers, Patriots and Titans, said he felt bad for Blewitt.

“He will make that kick 99 times out of a 100,” Miller said. “We just saw the one.”

He added, “Not an easy kick that close and wide.”

Punishing runner

Duke coach David Cutcliffe said some of his players were forced to leave the game with injuries after colliding with Pitt running back James Conner.

“We had a couple of defensive backs who came out of the game early after tackling him, but a better word is attempting to tackle him,” Cutcliffe said.

Cutcliffe said he was even more impressed when he watched video of the game Sunday morning.

“Our guys played hard,” he said. “They hit him. They got in some licks. But not only were we sore, but he was probably sore.

“He is playing as well as any back in the country.”

Conner leads the nation in total rushing yards (1,342) and is fourth in average yards per game (149.1)

Next game

Kickoff for Pitt’s first game against North Carolina in Chapel Hill since 1998 will be 12:30 p.m. Nov. 15.

Both teams are 4-5, and the loser will be all but eliminated from bowl eligibility.

The game will be televised by WTAE-4.

Jerry DiPaola is a staff writer for Trib Total Media. Reach him at [email protected] or via Twitter @JDiPaola_Trib.

TribLIVE commenting policy

You are solely responsible for your comments and by using you agree to our Terms of Service.

We moderate comments. Our goal is to provide substantive commentary for a general readership. By screening submissions, we provide a space where readers can share intelligent and informed commentary that enhances the quality of our news and information.

While most comments will be posted if they are on-topic and not abusive, moderating decisions are subjective. We will make them as carefully and consistently as we can. Because of the volume of reader comments, we cannot review individual moderation decisions with readers.

We value thoughtful comments representing a range of views that make their point quickly and politely. We make an effort to protect discussions from repeated comments either by the same reader or different readers

We follow the same standards for taste as the daily newspaper. A few things we won't tolerate: personal attacks, obscenity, vulgarity, profanity (including expletives and letters followed by dashes), commercial promotion, impersonations, incoherence, proselytizing and SHOUTING. Don't include URLs to Web sites.

We do not edit comments. They are either approved or deleted. We reserve the right to edit a comment that is quoted or excerpted in an article. In this case, we may fix spelling and punctuation.

We welcome strong opinions and criticism of our work, but we don't want comments to become bogged down with discussions of our policies and we will moderate accordingly.

We appreciate it when readers and people quoted in articles or blog posts point out errors of fact or emphasis and will investigate all assertions. But these suggestions should be sent via e-mail. To avoid distracting other readers, we won't publish comments that suggest a correction. Instead, corrections will be made in a blog post or in an article.