Pitt women fall to Georgia Tech in bid for consecutive ACC victories
Hoping to win back-to-back conference games for the first time in three years, the Pitt women's basketball team instead lost 77-66 to Georgia Tech on Monday at Petersen Events Center.
After trailing 43-30 at halftime, the Panthers opened the second half shooting 2 of 8 from the field. With just more than 10 minutes to go, the Yellowjackets held a 60-40 lead, and though the Panthers made it a 10-point game with just over three minutes remaining, that was as close as they got.
In what has been a struggle all year, Pitt (10-12, 2-6 ACC) couldn't find consistency with its offense and shot 32.4 percent from the field and 5 of 20 from 3-point range.
“Sometimes, I feel like a broken record,” coach Suzie McConnell-Serio said. “It just seems to come down a lot of times to the same thing, and that's just not being efficient enough on the offensive end, knocking down shots and capitalizing on opportunities — from layups to open 3s.”
Georgia Tech (14-8, 4-5 ACC) senior Tyaunna Marshall, the third-leading scorer in the ACC averaging 19.1 points, finished with 23. Freshman Kaela Davis had 16 points and 10 rebounds, and sophomore Aailyah Whiteside scored 18 points off the bench for the Yellowjackets, who had lost two in a row.
Marquel Davis led Pitt with 20 points and five assists. Asia Logan had 13 points and nine rebounds, and Brianna Kiesel finished with 11 points.
Brittany Gordon made a 3-pointer to cut Georgia Tech's lead to 62-49 with eight minutes remaining, and Davis scored on a layup to close the lead to 11. Georgia Tech's Roddreka Rogers answered with a layup to end an 0-for-7 drought, and the Yellowjackets maintained their double-figure lead the rest of the way.
The Panthers were looking to build off a 67-65 win over Boston College on Thursday. Kiesel's first career game-winner with 3 seconds left gave the Panthers their first home conference win since Feb. 15, 2011, which also was the last time they won back-to-back conference games.
“I think it's frustrating, obviously, to lose, but in order for us to win, everyone has to contribute,” Davis said. “All of us have to have somewhat of a good game to come out with the ‘W.' ”
Show commenting policy
TribLive commenting policy
You are solely responsible for your comments and by using TribLive.com 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.