×
Deadspin | Brandon Pfaadt, D-backs strive to fluster struggling Phillies   Apr 5, 2026; Phoenix, Arizona, USA; Arizona Diamondbacks pitcher Brandon Pfaadt (32) pitches during the first inning at Chase Field against the Atlanta Braves. Mandatory Credit: Arianna Grainey-Imagn Images   Brandon Pfaadt and Taijuan Walker have gotten off to poor starts this season, but they will have another opportunity to get on track Saturday afternoon when the Arizona Diamondbacks visit the Philadelphia Phillies.  Pfaadt (0-0, 6.75 ERA) gave up five runs in six innings against the Detroit Tigers on March 31 in his first start of 2026. The right-hander then failed to make it out of the fifth inning Sunday against the Atlanta Braves, yielding three runs in 4 2/3 frames.  “It was kind of a grinder, but it was an overall team win,” Pfaadt said after his teammates squeaked out a 6-5 victory in 10 innings. “It’s a big, big testament to the type of team that we are.”  Walker (0-2, 9.31 ERA) was pounded in his season debut on March 30, allowing seven runs (six earned) and 10 hits in 4 2/3 innings in a 13-2 loss to the Washington Nationals. His performance was a little better Sunday vs. the Colorado Rockies, who tagged the right-hander for four runs and seven hits — including three homers — in five innings. Colorado won 4-1.  “Rough,” Walker said, assessing his early-season performances. “I feel like the stuff is good. It’s playing up. But when I’m making mistakes, it’s getting hit right now.”  In Friday’s series opener, both starting pitchers suffered through one ugly inning in the game won by Arizona, 5-4.  For Arizona starter Michael Soroka, it was a four-run first that included a three-run homer by Brandon Marsh. That 4-0 lead held up until Philadelphia starter Jesus Luzardo yielded five runs in the fifth, highlighted by two-RBI hits from Ketel Marte and James McCann.  McCann initially came on after Diamondbacks catcher Gabriel Moreno made an early exit due to back soreness.  “One inning, he’s just sitting there minding his own business, and the next inning, he’s calling a game and just immediately impacted the game,” Arizona manager Torey Lovullo said of McCann. “And then he had the big hit that clearly helped us win the game, so props to him.”   Moreno’s status for Saturday’s matinee wasn’t clear when Lovullo met with the media on Friday.   “We’re going to evaluate him tonight, through the course of the morning, and find out what’s going on,” Lovullo said. “So he’s going to be day-to-day at this point.”  The Phillies have some examining to do as well, as they need to take a close look at an offense that has scored in only one of their last 29 innings. After 20 straight scoreless frames to end their trip to San Francisco, the Phillies did not score Friday after their first four batters of the game scored.   “The entire team tonight, a lot of swing-and-miss. That was really our bugaboo,” Philadelphia manager Rob Thomson said after his team struck out 16 times against Soroka and three relievers.   Kyle Schwarber went 0-for-3 with two strikeouts, lowering his batting average to .182. Bryson Stott is batting .179 and Alec Bohm, after going 0-for-4 with three punchouts, is down to .170.  “With Bohmer, he’s just missing,” Thomson said. “I don’t know whether it’s timing or contact point. It could be a number of things.”   Bohm will try to get back in a groove as he faces Pfaadt, who will make his second career start against the Phillies. He allowed seven runs in 4 2/3 innings in a 7-2 loss to Philadelphia last season.  Walker has made two career starts against Arizona — one in each of the last two seasons — and is 0-1 with a 6.75 ERA.  –Field Level Media    #Deadspin #Brandon #Pfaadt #Dbacks #strive #fluster #struggling #Phillies

Deadspin | Brandon Pfaadt, D-backs strive to fluster struggling Phillies
Deadspin | Brandon Pfaadt, D-backs strive to fluster struggling Phillies   Apr 5, 2026; Phoenix, Arizona, USA; Arizona Diamondbacks pitcher Brandon Pfaadt (32) pitches during the first inning at Chase Field against the Atlanta Braves. Mandatory Credit: Arianna Grainey-Imagn Images   Brandon Pfaadt and Taijuan Walker have gotten off to poor starts this season, but they will have another opportunity to get on track Saturday afternoon when the Arizona Diamondbacks visit the Philadelphia Phillies.  Pfaadt (0-0, 6.75 ERA) gave up five runs in six innings against the Detroit Tigers on March 31 in his first start of 2026. The right-hander then failed to make it out of the fifth inning Sunday against the Atlanta Braves, yielding three runs in 4 2/3 frames.  “It was kind of a grinder, but it was an overall team win,” Pfaadt said after his teammates squeaked out a 6-5 victory in 10 innings. “It’s a big, big testament to the type of team that we are.”  Walker (0-2, 9.31 ERA) was pounded in his season debut on March 30, allowing seven runs (six earned) and 10 hits in 4 2/3 innings in a 13-2 loss to the Washington Nationals. His performance was a little better Sunday vs. the Colorado Rockies, who tagged the right-hander for four runs and seven hits — including three homers — in five innings. Colorado won 4-1.  “Rough,” Walker said, assessing his early-season performances. “I feel like the stuff is good. It’s playing up. But when I’m making mistakes, it’s getting hit right now.”  In Friday’s series opener, both starting pitchers suffered through one ugly inning in the game won by Arizona, 5-4.  For Arizona starter Michael Soroka, it was a four-run first that included a three-run homer by Brandon Marsh. That 4-0 lead held up until Philadelphia starter Jesus Luzardo yielded five runs in the fifth, highlighted by two-RBI hits from Ketel Marte and James McCann.  McCann initially came on after Diamondbacks catcher Gabriel Moreno made an early exit due to back soreness.  “One inning, he’s just sitting there minding his own business, and the next inning, he’s calling a game and just immediately impacted the game,” Arizona manager Torey Lovullo said of McCann. “And then he had the big hit that clearly helped us win the game, so props to him.”   Moreno’s status for Saturday’s matinee wasn’t clear when Lovullo met with the media on Friday.   “We’re going to evaluate him tonight, through the course of the morning, and find out what’s going on,” Lovullo said. “So he’s going to be day-to-day at this point.”  The Phillies have some examining to do as well, as they need to take a close look at an offense that has scored in only one of their last 29 innings. After 20 straight scoreless frames to end their trip to San Francisco, the Phillies did not score Friday after their first four batters of the game scored.   “The entire team tonight, a lot of swing-and-miss. That was really our bugaboo,” Philadelphia manager Rob Thomson said after his team struck out 16 times against Soroka and three relievers.   Kyle Schwarber went 0-for-3 with two strikeouts, lowering his batting average to .182. Bryson Stott is batting .179 and Alec Bohm, after going 0-for-4 with three punchouts, is down to .170.  “With Bohmer, he’s just missing,” Thomson said. “I don’t know whether it’s timing or contact point. It could be a number of things.”   Bohm will try to get back in a groove as he faces Pfaadt, who will make his second career start against the Phillies. He allowed seven runs in 4 2/3 innings in a 7-2 loss to Philadelphia last season.  Walker has made two career starts against Arizona — one in each of the last two seasons — and is 0-1 with a 6.75 ERA.  –Field Level Media    #Deadspin #Brandon #Pfaadt #Dbacks #strive #fluster #struggling #PhilliesApr 5, 2026; Phoenix, Arizona, USA; Arizona Diamondbacks pitcher Brandon Pfaadt (32) pitches during the first inning at Chase Field against the Atlanta Braves. Mandatory Credit: Arianna Grainey-Imagn Images

Brandon Pfaadt and Taijuan Walker have gotten off to poor starts this season, but they will have another opportunity to get on track Saturday afternoon when the Arizona Diamondbacks visit the Philadelphia Phillies.

Pfaadt (0-0, 6.75 ERA) gave up five runs in six innings against the Detroit Tigers on March 31 in his first start of 2026. The right-hander then failed to make it out of the fifth inning Sunday against the Atlanta Braves, yielding three runs in 4 2/3 frames.

“It was kind of a grinder, but it was an overall team win,” Pfaadt said after his teammates squeaked out a 6-5 victory in 10 innings. “It’s a big, big testament to the type of team that we are.”

Walker (0-2, 9.31 ERA) was pounded in his season debut on March 30, allowing seven runs (six earned) and 10 hits in 4 2/3 innings in a 13-2 loss to the Washington Nationals. His performance was a little better Sunday vs. the Colorado Rockies, who tagged the right-hander for four runs and seven hits — including three homers — in five innings. Colorado won 4-1.

“Rough,” Walker said, assessing his early-season performances. “I feel like the stuff is good. It’s playing up. But when I’m making mistakes, it’s getting hit right now.”

In Friday’s series opener, both starting pitchers suffered through one ugly inning in the game won by Arizona, 5-4.

For Arizona starter Michael Soroka, it was a four-run first that included a three-run homer by Brandon Marsh. That 4-0 lead held up until Philadelphia starter Jesus Luzardo yielded five runs in the fifth, highlighted by two-RBI hits from Ketel Marte and James McCann.

McCann initially came on after Diamondbacks catcher Gabriel Moreno made an early exit due to back soreness.


“One inning, he’s just sitting there minding his own business, and the next inning, he’s calling a game and just immediately impacted the game,” Arizona manager Torey Lovullo said of McCann. “And then he had the big hit that clearly helped us win the game, so props to him.”

Moreno’s status for Saturday’s matinee wasn’t clear when Lovullo met with the media on Friday.

“We’re going to evaluate him tonight, through the course of the morning, and find out what’s going on,” Lovullo said. “So he’s going to be day-to-day at this point.”

The Phillies have some examining to do as well, as they need to take a close look at an offense that has scored in only one of their last 29 innings. After 20 straight scoreless frames to end their trip to San Francisco, the Phillies did not score Friday after their first four batters of the game scored.

“The entire team tonight, a lot of swing-and-miss. That was really our bugaboo,” Philadelphia manager Rob Thomson said after his team struck out 16 times against Soroka and three relievers.

Kyle Schwarber went 0-for-3 with two strikeouts, lowering his batting average to .182. Bryson Stott is batting .179 and Alec Bohm, after going 0-for-4 with three punchouts, is down to .170.

“With Bohmer, he’s just missing,” Thomson said. “I don’t know whether it’s timing or contact point. It could be a number of things.”

Bohm will try to get back in a groove as he faces Pfaadt, who will make his second career start against the Phillies. He allowed seven runs in 4 2/3 innings in a 7-2 loss to Philadelphia last season.

Walker has made two career starts against Arizona — one in each of the last two seasons — and is 0-1 with a 6.75 ERA.


–Field Level Media

#Deadspin #Brandon #Pfaadt #Dbacks #strive #fluster #struggling #Phillies

Apr 5, 2026; Phoenix, Arizona, USA; Arizona Diamondbacks pitcher Brandon Pfaadt (32) pitches during the first inning at Chase Field against the Atlanta Braves. Mandatory Credit: Arianna Grainey-Imagn Images

Brandon Pfaadt and Taijuan Walker have gotten off to poor starts this season, but they will have another opportunity to get on track Saturday afternoon when the Arizona Diamondbacks visit the Philadelphia Phillies.

Pfaadt (0-0, 6.75 ERA) gave up five runs in six innings against the Detroit Tigers on March 31 in his first start of 2026. The right-hander then failed to make it out of the fifth inning Sunday against the Atlanta Braves, yielding three runs in 4 2/3 frames.

“It was kind of a grinder, but it was an overall team win,” Pfaadt said after his teammates squeaked out a 6-5 victory in 10 innings. “It’s a big, big testament to the type of team that we are.”

Walker (0-2, 9.31 ERA) was pounded in his season debut on March 30, allowing seven runs (six earned) and 10 hits in 4 2/3 innings in a 13-2 loss to the Washington Nationals. His performance was a little better Sunday vs. the Colorado Rockies, who tagged the right-hander for four runs and seven hits — including three homers — in five innings. Colorado won 4-1.

“Rough,” Walker said, assessing his early-season performances. “I feel like the stuff is good. It’s playing up. But when I’m making mistakes, it’s getting hit right now.”

In Friday’s series opener, both starting pitchers suffered through one ugly inning in the game won by Arizona, 5-4.

For Arizona starter Michael Soroka, it was a four-run first that included a three-run homer by Brandon Marsh. That 4-0 lead held up until Philadelphia starter Jesus Luzardo yielded five runs in the fifth, highlighted by two-RBI hits from Ketel Marte and James McCann.

McCann initially came on after Diamondbacks catcher Gabriel Moreno made an early exit due to back soreness.

“One inning, he’s just sitting there minding his own business, and the next inning, he’s calling a game and just immediately impacted the game,” Arizona manager Torey Lovullo said of McCann. “And then he had the big hit that clearly helped us win the game, so props to him.”

Moreno’s status for Saturday’s matinee wasn’t clear when Lovullo met with the media on Friday.

“We’re going to evaluate him tonight, through the course of the morning, and find out what’s going on,” Lovullo said. “So he’s going to be day-to-day at this point.”

The Phillies have some examining to do as well, as they need to take a close look at an offense that has scored in only one of their last 29 innings. After 20 straight scoreless frames to end their trip to San Francisco, the Phillies did not score Friday after their first four batters of the game scored.

“The entire team tonight, a lot of swing-and-miss. That was really our bugaboo,” Philadelphia manager Rob Thomson said after his team struck out 16 times against Soroka and three relievers.

Kyle Schwarber went 0-for-3 with two strikeouts, lowering his batting average to .182. Bryson Stott is batting .179 and Alec Bohm, after going 0-for-4 with three punchouts, is down to .170.

“With Bohmer, he’s just missing,” Thomson said. “I don’t know whether it’s timing or contact point. It could be a number of things.”

Bohm will try to get back in a groove as he faces Pfaadt, who will make his second career start against the Phillies. He allowed seven runs in 4 2/3 innings in a 7-2 loss to Philadelphia last season.

Walker has made two career starts against Arizona — one in each of the last two seasons — and is 0-1 with a 6.75 ERA.

–Field Level Media

Source link
#Deadspin #Brandon #Pfaadt #Dbacks #strive #fluster #struggling #Phillies

Previous post

The Chicago Sky just signed the most unlikely player <figure> <img alt="" data-caption="SEATTLE, WA - SEPTEMBER 16: Skylar Diggins #4 of the Seattle Storm shoots a free throw during the game against the Las Vegas Aces during Game Two Round One of the 2025 WNBA Playoffs on September 16, 2025 at Climate Pledge Arena in Seattle, Washington. NOTE TO USER: User expressly acknowledges and agrees that, by downloading and or using this photograph, User is consenting to the terms and conditions of the Getty Images License Agreement. Mandatory Copyright Notice: Copyright 2025 NBAE (Photo by Alika Jenner/NBAE via Getty Images) | NBAE via Getty Images" data-portal-copyright="NBAE via Getty Images" data-has-syndication-rights="1" src="https://platform.sbnation.com/wp-content/uploads/sites/2/2026/04/gettyimages-2235294782.jpg?quality=90&strip=all&crop=0,0,100,100" /> <figcaption> SEATTLE, WA – SEPTEMBER 16: Skylar Diggins #4 of the Seattle Storm shoots a free throw during the game against the Las Vegas Aces during Game Two Round One of the 2025 WNBA Playoffs on September 16, 2025 at Climate Pledge Arena in Seattle, Washington. NOTE TO USER: User expressly acknowledges and agrees that, by downloading and or using this photograph, User is consenting to the terms and conditions of the Getty Images License Agreement. Mandatory Copyright Notice: Copyright 2025 NBAE (Photo by Alika Jenner/NBAE via Getty Images) | NBAE via Getty Images </figcaption> </figure> <p class="has-text-align-none">One of the biggest free agents on the market has a new home, as Skylar Diggins is heading to Chicago. The 7x WNBA All-Star, Olympic Gold Medalist, and 4x First Team All-WNBA selection is moving on from the Seattle Storm after two seasons.</p> <p class="has-text-align-none">This is Diggins’s fourth WNBA franchise — she started her career with the Tulsa Shock, which ultimately became the Dallas Wings. Then she moved to Phoenix before coming to Seattle, and will now land in Chicago.</p> <figure class="wp-block-embed is-type-rich is-provider-twitter wp-block-embed-twitter"><div class="wp-block-embed__wrapper"> <blockquote class="twitter-tweet" data-dnt="true"><p lang="en" dir="ltr">Breaking: 7x WNBA All-Star Skylar Diggins has signed with the Chicago Sky, the team has announced.<br><br>Diggins has signed a two-year deal with the team, sources told ESPN. <a href="https://t.co/yQbO7I8g6K">pic.twitter.com/yQbO7I8g6K</a></p>— Alexa Philippou (@alexaphilippou) <a href="https://twitter.com/alexaphilippou/status/2043012138533335160?ref_src=twsrc%5Etfw">April 11, 2026</a></blockquote> </div></figure> <h2 class="wp-block-heading has-text-align-none">Grading Skylar Diggins to the Chicago Sky: B+</h2> <p class="has-text-align-none">Skylar’s time in Seattle saw her average about 15 points per game through two seasons, which is solid. She has room to return to her former stats on a Sky team that will be focused around her as a scorer, too. If Vandersloot comes back at some point in the season from ACL recovery, Diggins can slot into an off-ball role, but she’s also comfortable bringing the ball up.</p> <p class="has-text-align-none">The Sky’s reluctance to fully go into rebuild/development mode <a href="https://www.sbnation.com/wnba/1109757/angel-reeses-time-in-chicago-is-officially-over">after trading Angel Reese</a> is helped by the amount of cap space they now have, which is obviously a factor in getting Diggins. They are putting all their eggs in one basket, though, given that they don’t have the rights to their first-round picks for the next two seasons, in two VERY strong draft classes.</p> <p class="has-text-align-none">Ultimately, this move didn’t immediately shift the Sky’s championship odds much, either. <a href="https://sportsbook.fanduel.com/navigation/wnba">They are still tied for second-worst championship odds</a> in the WNBA at +40,000, but only time will tell if this surprising direction change will pay off in the long run.</p> <p class="has-text-align-none"></p><script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script> #Chicago #Sky #signed #player

Next post

CSK vs DC IPL 2026: Sanju Samson slams maiden century for Chennai Super Kings <div id="content-body-70851595" itemprop="articleBody"><p>After three single-digit scores, Sanju Samson smashed a century for the first time in Chennai Super Kings (CSK) colours against Delhi Capitals (DC) at the M.A. Chidambaram Stadium on Saturday.</p><p>Samson reached the landmark in just 52 balls. His innings got CSK to a commanding total of 212 for two.</p><p>The 31-year-old was able to find his rhythm from ball one, and took the bowlers to all parts of the park. Samson smashed 15 fours and four sixes in his unbeaten knock of 115.</p><p>Samson’s century was the fourth of his career, having scored two centuries during his time with Rajasthan Royals and another one for Delhi Daredevils.</p><p class="publish-time" id="end-of-article">Published on Apr 11, 2026</p></div> #CSK #IPL #Sanju #Samson #slams #maiden #century #Chennai #Super #Kings

Kyle Shanahan was involved in a car accident shortly before training camp began. That is the lone fact we know with certainty. What began as a seemingly routine traffic incident, one that should have made minor waves, has turned into a quagmire as numerous layers of attempted cover-ups, media favors, and altered facts have quickly transformed a snowball into an avalanche of speculation.

The most bizarre element of all this is: Why? The official version of the incident is really quite benign, ostensibly saying that Shanahan was distracted, looking for his dropped phone and caused an accident. It’s reckless and dumb, but something that happens thousands of times every day across the United States. If that is truly what happened, then why have the 49ers and everyone in their orbit gone to such profound lengths to hide the details of what occurred, treating the incident with the same gravity as an international incident, rather than a serious fender bender?

The first report and sign of tampering

On July 14 police responded to a traffic accident involving San Francisco 49ers head coach Kyle Shanahan in Palo Alto, California. Shanahan was driving a Tesla, and crossed over the center line into oncoming traffic, at which point he was involved in a head-on collision with a 21-year-old who was driving an SUV.

The young driver was reportedly unharmed, but Shanhan sustained numerous injuries, including a concussion, broken ribs, and a head laceration, which required stitches.

It’s here that things get bizarre, because for the next 11 days there is no mention of the accident by anyone. Local news had nothing about the accident, 49ers team beat writers say nothing, and it isn’t until July 25 — a full 11 days after the accident that the Niners release a statement. Two minutes later ESPN posted an official write-up of the news, seemingly indicating that they had the story early, but held it while waiting for the 49ers to release their statement.

Tim Kawakami, 49ers beat writer for the San Francisco Standard says he knew about the accident prior to the 49ers’ statement as well, but decided not to share any information because he didn’t have the full story.

This raised huge questions about access journalism when it comes to NFL teams. It’s certainly understandable to wait for the full details of a significant event, like a death or an arrest — but Kawakami had extremely weak excuses for not reporting basic details, or digging to find out more. Instead he spent the bulk of the 25th attacking people on Twitter who challenged why he didn’t report on the team he covers, instead waiting to echo ESPNs nation write up.

At best it looked like a sloppy job, at worst there was speculation that the 49ers asked Kawakami not to report on the accident, and he obliged.

Incorrect records and clarification

There is an online database of every significant traffic accident that occurs in the state of California. People began looking into these records in the wake of the Shanahan news, trying to garner more information about an incident which the team seemingly worked to cover up.

The official crash records named the other party at fault in the accident, essentially absolving Shanahan of responsibility. It’s unclear how anyone in law enforcement could have found another party at fault when it was the 49ers coach who crossed the center line and struck a vehicle in the ongoing lane.

Shanahan held a meeting with a small group of reporters in his office, where he clarified that the database entry was incorrect, accepted blame for the accident, and explained that it was his fault for searching for his phone. This meeting was behind closed doors, unrecorded, and reportedly contained many comments which were off the record, adding to questions about the nature of this whole mess.

The police response was … weird

Police acknowledged that Shanahan was at fault, blaming the incorrect entry in the crash database on a “clerical error.” This raised even more questions, because it was revealed that police elected not to charge or cite Shanahan at the scene, using “officer discretion.” While certainly within their right to determine whether or not a citation is issued, this raised even more questions. It’s highly unlikely that an accident of this severity would have resulted in no police response had it involved an ordinary citizen, and the accident taking place in Northern California certainly raised eyebrows if Shanahan got preferential treatment exclusively because he is the coach of the football team.

Compounding matters was the June 30th decision from the Palo Alto police department to bury all information regarding the accident. The California Post and TMZ reportedly asked the police for body cam footage of the incident, but were told by police that all video, audio, and the crash report itself was being withheld and kept private. The excuse from police was that they were protecting the other party, regardless whether or not Shanahan wanted the information released.

This is a level of secrecy typically withheld for much, much larger incidents. It seemingly adds another layer to the whole situation that make it appear if numerous people from a variety of angles were all colluding to ensure information didn’t go public about what happened with the traffic accident.

We don’t know, because parties with a vested interest don’t want us to know. The details of this accident are being intentionally withheld or buried, but it’s unclear what the motive is. We’re left with the only public account coming from Shanahan, filtered through a select group of hand-picked journalists he invited into his office. The police are closing ranks and explaining why Shanahan wasn’t cited, while having excuses when it comes to an incorrect database entry as well as body-worn camera footage of the incident.

While we don’t precisely know why so many people are going to lengths to cover up what happened, we do know that what has unfolded has been incredibly unorthodox. It’s not normal to have an NFL team run DeflateGate-level interference over a traffic accident, especially one that only harmed the driver at fault. While the incident as reported by Shanahan was careless, it’s fairly minor — especially considering he is okay now.

The explanation of this could be extremely simple: Perhaps the 49ers just wanted Shanahan to have privacy for some time to recover from his injuries, which is fine — but the layers of complicit behavior in towing this line really add room for rampant speculation. It’s not up to the 49ers to get to control the message, which it appears they were able to do. Even now the 49ers could come out at say this was the case.

There is something about this accident that is being withheld from the public. Information is likely to come out sooner or later, but until then we’re left with what should have been a minor issue getting blown up into a mammoth mystery.

#Kyle #Shanahans #car #accident #transformed #NFLs #biggest #mystery">Kyle Shanahan’s car accident has transformed into the NFL’s biggest mystery  Kyle Shanahan was involved in a car accident shortly before training camp began. That is the lone fact we know with certainty. What began as a seemingly routine traffic incident, one that should have made minor waves, has turned into a quagmire as numerous layers of attempted cover-ups, media favors, and altered facts have quickly transformed a snowball into an avalanche of speculation.The most bizarre element of all this is: Why? The official version of the incident is really quite benign, ostensibly saying that Shanahan was distracted, looking for his dropped phone and caused an accident. It’s reckless and dumb, but something that happens thousands of times every day across the United States. If that is truly what happened, then why have the 49ers and everyone in their orbit gone to such profound lengths to hide the details of what occurred, treating the incident with the same gravity as an international incident, rather than a serious fender bender?The first report and sign of tamperingOn July 14 police responded to a traffic accident involving San Francisco 49ers head coach Kyle Shanahan in Palo Alto, California. Shanahan was driving a Tesla, and crossed over the center line into oncoming traffic, at which point he was involved in a head-on collision with a 21-year-old who was driving an SUV.The young driver was reportedly unharmed, but Shanhan sustained numerous injuries, including a concussion, broken ribs, and a head laceration, which required stitches.It’s here that things get bizarre, because for the next 11 days there is no mention of the accident by anyone. Local news had nothing about the accident, 49ers team beat writers say nothing, and it isn’t until July 25 — a full 11 days after the accident that the Niners release a statement. Two minutes later ESPN posted an official write-up of the news, seemingly indicating that they had the story early, but held it while waiting for the 49ers to release their statement.Tim Kawakami, 49ers beat writer for the San Francisco Standard says he knew about the accident prior to the 49ers’ statement as well, but decided not to share any information because he didn’t have the full story.This raised huge questions about access journalism when it comes to NFL teams. It’s certainly understandable to wait for the full details of a significant event, like a death or an arrest — but Kawakami had extremely weak excuses for not reporting basic details, or digging to find out more. Instead he spent the bulk of the 25th attacking people on Twitter who challenged why he didn’t report on the team he covers, instead waiting to echo ESPNs nation write up.At best it looked like a sloppy job, at worst there was speculation that the 49ers asked Kawakami not to report on the accident, and he obliged.Incorrect records and clarificationThere is an online database of every significant traffic accident that occurs in the state of California. People began looking into these records in the wake of the Shanahan news, trying to garner more information about an incident which the team seemingly worked to cover up.The official crash records named the other party at fault in the accident, essentially absolving Shanahan of responsibility. It’s unclear how anyone in law enforcement could have found another party at fault when it was the 49ers coach who crossed the center line and struck a vehicle in the ongoing lane.Shanahan held a meeting with a small group of reporters in his office, where he clarified that the database entry was incorrect, accepted blame for the accident, and explained that it was his fault for searching for his phone. This meeting was behind closed doors, unrecorded, and reportedly contained many comments which were off the record, adding to questions about the nature of this whole mess.The police response was … weirdPolice acknowledged that Shanahan was at fault, blaming the incorrect entry in the crash database on a “clerical error.” This raised even more questions, because it was revealed that police elected not to charge or cite Shanahan at the scene, using “officer discretion.” While certainly within their right to determine whether or not a citation is issued, this raised even more questions. It’s highly unlikely that an accident of this severity would have resulted in no police response had it involved an ordinary citizen, and the accident taking place in Northern California certainly raised eyebrows if Shanahan got preferential treatment exclusively because he is the coach of the football team.Compounding matters was the June 30th decision from the Palo Alto police department to bury all information regarding the accident. The California Post and TMZ reportedly asked the police for body cam footage of the incident, but were told by police that all video, audio, and the crash report itself was being withheld and kept private. The excuse from police was that they were protecting the other party, regardless whether or not Shanahan wanted the information released.This is a level of secrecy typically withheld for much, much larger incidents. It seemingly adds another layer to the whole situation that make it appear if numerous people from a variety of angles were all colluding to ensure information didn’t go public about what happened with the traffic accident.We don’t know, because parties with a vested interest don’t want us to know. The details of this accident are being intentionally withheld or buried, but it’s unclear what the motive is. We’re left with the only public account coming from Shanahan, filtered through a select group of hand-picked journalists he invited into his office. The police are closing ranks and explaining why Shanahan wasn’t cited, while having excuses when it comes to an incorrect database entry as well as body-worn camera footage of the incident.While we don’t precisely know why so many people are going to lengths to cover up what happened, we do know that what has unfolded has been incredibly unorthodox. It’s not normal to have an NFL team run DeflateGate-level interference over a traffic accident, especially one that only harmed the driver at fault. While the incident as reported by Shanahan was careless, it’s fairly minor — especially considering he is okay now.The explanation of this could be extremely simple: Perhaps the 49ers just wanted Shanahan to have privacy for some time to recover from his injuries, which is fine — but the layers of complicit behavior in towing this line really add room for rampant speculation. It’s not up to the 49ers to get to control the message, which it appears they were able to do. Even now the 49ers could come out at say this was the case.There is something about this accident that is being withheld from the public. Information is likely to come out sooner or later, but until then we’re left with what should have been a minor issue getting blown up into a mammoth mystery.  #Kyle #Shanahans #car #accident #transformed #NFLs #biggest #mystery

Two minutes later ESPN posted an official write-up of the news, seemingly indicating that they had the story early, but held it while waiting for the 49ers to release their statement.

Tim Kawakami, 49ers beat writer for the San Francisco Standard says he knew about the accident prior to the 49ers’ statement as well, but decided not to share any information because he didn’t have the full story.

This raised huge questions about access journalism when it comes to NFL teams. It’s certainly understandable to wait for the full details of a significant event, like a death or an arrest — but Kawakami had extremely weak excuses for not reporting basic details, or digging to find out more. Instead he spent the bulk of the 25th attacking people on Twitter who challenged why he didn’t report on the team he covers, instead waiting to echo ESPNs nation write up.

At best it looked like a sloppy job, at worst there was speculation that the 49ers asked Kawakami not to report on the accident, and he obliged.

Incorrect records and clarification

There is an online database of every significant traffic accident that occurs in the state of California. People began looking into these records in the wake of the Shanahan news, trying to garner more information about an incident which the team seemingly worked to cover up.

The official crash records named the other party at fault in the accident, essentially absolving Shanahan of responsibility. It’s unclear how anyone in law enforcement could have found another party at fault when it was the 49ers coach who crossed the center line and struck a vehicle in the ongoing lane.

Shanahan held a meeting with a small group of reporters in his office, where he clarified that the database entry was incorrect, accepted blame for the accident, and explained that it was his fault for searching for his phone. This meeting was behind closed doors, unrecorded, and reportedly contained many comments which were off the record, adding to questions about the nature of this whole mess.

The police response was … weird

Police acknowledged that Shanahan was at fault, blaming the incorrect entry in the crash database on a “clerical error.” This raised even more questions, because it was revealed that police elected not to charge or cite Shanahan at the scene, using “officer discretion.” While certainly within their right to determine whether or not a citation is issued, this raised even more questions. It’s highly unlikely that an accident of this severity would have resulted in no police response had it involved an ordinary citizen, and the accident taking place in Northern California certainly raised eyebrows if Shanahan got preferential treatment exclusively because he is the coach of the football team.

Compounding matters was the June 30th decision from the Palo Alto police department to bury all information regarding the accident. The California Post and TMZ reportedly asked the police for body cam footage of the incident, but were told by police that all video, audio, and the crash report itself was being withheld and kept private. The excuse from police was that they were protecting the other party, regardless whether or not Shanahan wanted the information released.

This is a level of secrecy typically withheld for much, much larger incidents. It seemingly adds another layer to the whole situation that make it appear if numerous people from a variety of angles were all colluding to ensure information didn’t go public about what happened with the traffic accident.

We don’t know, because parties with a vested interest don’t want us to know. The details of this accident are being intentionally withheld or buried, but it’s unclear what the motive is. We’re left with the only public account coming from Shanahan, filtered through a select group of hand-picked journalists he invited into his office. The police are closing ranks and explaining why Shanahan wasn’t cited, while having excuses when it comes to an incorrect database entry as well as body-worn camera footage of the incident.

While we don’t precisely know why so many people are going to lengths to cover up what happened, we do know that what has unfolded has been incredibly unorthodox. It’s not normal to have an NFL team run DeflateGate-level interference over a traffic accident, especially one that only harmed the driver at fault. While the incident as reported by Shanahan was careless, it’s fairly minor — especially considering he is okay now.

The explanation of this could be extremely simple: Perhaps the 49ers just wanted Shanahan to have privacy for some time to recover from his injuries, which is fine — but the layers of complicit behavior in towing this line really add room for rampant speculation. It’s not up to the 49ers to get to control the message, which it appears they were able to do. Even now the 49ers could come out at say this was the case.

There is something about this accident that is being withheld from the public. Information is likely to come out sooner or later, but until then we’re left with what should have been a minor issue getting blown up into a mammoth mystery.

#Kyle #Shanahans #car #accident #transformed #NFLs #biggest #mystery">Kyle Shanahan’s car accident has transformed into the NFL’s biggest mystery

Kyle Shanahan was involved in a car accident shortly before training camp began. That is the lone fact we know with certainty. What began as a seemingly routine traffic incident, one that should have made minor waves, has turned into a quagmire as numerous layers of attempted cover-ups, media favors, and altered facts have quickly transformed a snowball into an avalanche of speculation.

The most bizarre element of all this is: Why? The official version of the incident is really quite benign, ostensibly saying that Shanahan was distracted, looking for his dropped phone and caused an accident. It’s reckless and dumb, but something that happens thousands of times every day across the United States. If that is truly what happened, then why have the 49ers and everyone in their orbit gone to such profound lengths to hide the details of what occurred, treating the incident with the same gravity as an international incident, rather than a serious fender bender?

The first report and sign of tampering

On July 14 police responded to a traffic accident involving San Francisco 49ers head coach Kyle Shanahan in Palo Alto, California. Shanahan was driving a Tesla, and crossed over the center line into oncoming traffic, at which point he was involved in a head-on collision with a 21-year-old who was driving an SUV.

The young driver was reportedly unharmed, but Shanhan sustained numerous injuries, including a concussion, broken ribs, and a head laceration, which required stitches.

It’s here that things get bizarre, because for the next 11 days there is no mention of the accident by anyone. Local news had nothing about the accident, 49ers team beat writers say nothing, and it isn’t until July 25 — a full 11 days after the accident that the Niners release a statement. Two minutes later ESPN posted an official write-up of the news, seemingly indicating that they had the story early, but held it while waiting for the 49ers to release their statement.

Tim Kawakami, 49ers beat writer for the San Francisco Standard says he knew about the accident prior to the 49ers’ statement as well, but decided not to share any information because he didn’t have the full story.

This raised huge questions about access journalism when it comes to NFL teams. It’s certainly understandable to wait for the full details of a significant event, like a death or an arrest — but Kawakami had extremely weak excuses for not reporting basic details, or digging to find out more. Instead he spent the bulk of the 25th attacking people on Twitter who challenged why he didn’t report on the team he covers, instead waiting to echo ESPNs nation write up.

At best it looked like a sloppy job, at worst there was speculation that the 49ers asked Kawakami not to report on the accident, and he obliged.

Incorrect records and clarification

There is an online database of every significant traffic accident that occurs in the state of California. People began looking into these records in the wake of the Shanahan news, trying to garner more information about an incident which the team seemingly worked to cover up.

The official crash records named the other party at fault in the accident, essentially absolving Shanahan of responsibility. It’s unclear how anyone in law enforcement could have found another party at fault when it was the 49ers coach who crossed the center line and struck a vehicle in the ongoing lane.

Shanahan held a meeting with a small group of reporters in his office, where he clarified that the database entry was incorrect, accepted blame for the accident, and explained that it was his fault for searching for his phone. This meeting was behind closed doors, unrecorded, and reportedly contained many comments which were off the record, adding to questions about the nature of this whole mess.

The police response was … weird

Police acknowledged that Shanahan was at fault, blaming the incorrect entry in the crash database on a “clerical error.” This raised even more questions, because it was revealed that police elected not to charge or cite Shanahan at the scene, using “officer discretion.” While certainly within their right to determine whether or not a citation is issued, this raised even more questions. It’s highly unlikely that an accident of this severity would have resulted in no police response had it involved an ordinary citizen, and the accident taking place in Northern California certainly raised eyebrows if Shanahan got preferential treatment exclusively because he is the coach of the football team.

Compounding matters was the June 30th decision from the Palo Alto police department to bury all information regarding the accident. The California Post and TMZ reportedly asked the police for body cam footage of the incident, but were told by police that all video, audio, and the crash report itself was being withheld and kept private. The excuse from police was that they were protecting the other party, regardless whether or not Shanahan wanted the information released.

This is a level of secrecy typically withheld for much, much larger incidents. It seemingly adds another layer to the whole situation that make it appear if numerous people from a variety of angles were all colluding to ensure information didn’t go public about what happened with the traffic accident.

We don’t know, because parties with a vested interest don’t want us to know. The details of this accident are being intentionally withheld or buried, but it’s unclear what the motive is. We’re left with the only public account coming from Shanahan, filtered through a select group of hand-picked journalists he invited into his office. The police are closing ranks and explaining why Shanahan wasn’t cited, while having excuses when it comes to an incorrect database entry as well as body-worn camera footage of the incident.

While we don’t precisely know why so many people are going to lengths to cover up what happened, we do know that what has unfolded has been incredibly unorthodox. It’s not normal to have an NFL team run DeflateGate-level interference over a traffic accident, especially one that only harmed the driver at fault. While the incident as reported by Shanahan was careless, it’s fairly minor — especially considering he is okay now.

The explanation of this could be extremely simple: Perhaps the 49ers just wanted Shanahan to have privacy for some time to recover from his injuries, which is fine — but the layers of complicit behavior in towing this line really add room for rampant speculation. It’s not up to the 49ers to get to control the message, which it appears they were able to do. Even now the 49ers could come out at say this was the case.

There is something about this accident that is being withheld from the public. Information is likely to come out sooner or later, but until then we’re left with what should have been a minor issue getting blown up into a mammoth mystery.

#Kyle #Shanahans #car #accident #transformed #NFLs #biggest #mystery
CWG 2026 LIVE updates from Glasgow: India wins three gold, three silver, one bronze  Can’t believe we are nearing the close of this edition of the Friendly Games already. Nevertheless, here is how the Indian athletes are placed today:ATHLETICS AND PARA ATHLETICS2:35 p.m. – Men’s Shot Put F57 Final (medal event) – Soman Rana, Shubham Juyal2:40 p.m. – Men’s Triple Jump Final (medal event) – Praveen Chithravel, Selva Prabhu Thirumaran2:50 p.m. – Men’s 1500m T54 Final (medal event) – Ramesh Shanmugam3 p.m. – Women’s 10,000m Race Walk Final (medal event) – Priyanka, Ravina11:35 p.m. – Men’s Pole Vault Final (medal event) – Dev Kumar Meena, Kuldeep Kumar12:15 a.m. (August 2) – Men’s 5000m Final (medal event) – Gulveer Singh1:50 a.m. (August 2) – Mixed 4x400m Relay Final – India (Vishal TK, Rajesh Ramesh, Rashdeep Kaur, Ansa Babu, Neeru Pathak)BOWLS3:50 p.m. – Men’s Pairs Sectional Play, Section B Round 5 – India (Navneet Singh, Dinesh Kumar) vs England (Nick Brett, Jamie Walker)10:20 p.m. – Women’s Singles Sectional Play, Section C Round 5 – Nayanmoni Saikia vs Bridget Herselman (South Africa)11:45 p.m. – Men’s Pairs Semifinals – India (Subject to qualification)BOXING3:30 p.m. – Women’s 54kg Final (medal event) – Preeti Pawar vs Scarlett Savannah Delgado (Canada)3:45 p.m. – Women’s 57kg Final (medal event) – Jaismine Lamboria vs Michaela Walsh (Northern Ireland)4:45 p.m. – Men’s 55kg Final (medal event) – Jadumani Singh Mandengbam vs Jye Dixon (Australia)9 p.m. – Women’s 51kg Final (medal event) – Sakshi Chaudhary vs Ruby White (England)9:15 p.m. – Women’s 60kg Final (medal event) – Priya Ghanghas vs Marie-Bathoul Al-Ahmadieh (Canada)9:30 p.m. – Women’s 70kg Final (medal event) – Arundhati Choudhary vs Chantelle Reid (England)9:45 p.m. – Women’s 75kg Final (medal event) – Lovlina Borgohain vs Emma-Sue Greentree (Australia)10 p.m. – Men’s 60kg Final (medal event) – Sachin Siwach vs Tryagain Morning Ndevelo (Namibia)10:15 p.m. – Men’s 80kg Final (medal event) – Ankush Panghal vs Dimeji Shittu (England)10:30 p.m. – Men’s +90kg Final (medal event) – Narender Berwal vs Damar Thomas (England)JUDO3:30 p.m. onwards – Women’s -63kg, Round of 16 – Unnati Sharma vs Lamulela Magagula (Eswatini)3:30 p.m. onwards – Men’s -90kg, Round of 16 – Karanjit Singh Maan vs Elliott Connolly (New Zealand)3:30 p.m. onwards – Men’s -81kg, Quarterfinal – Harsh Tokas vs Odysseas Georgakis (Cyprus)3:30 p.m. onwards – Women’s -70kg, Quarterfinal – Inunganbi Takhellambam vs TBD (To be decided)8:30 p.m. onwards – Women’s -63kg, Medal Rounds – Unnati Sharma (Subject to qualification)8:30 p.m. onwards – Men’s -90kg, Medal Rounds – Karanjit Singh Maan (Subject to qualification)8:30 p.m. onwards – Men’s -81kg, Medal Rounds – Harsh Tokas (Subject to qualification)8:30 p.m. onwards – Women’s -70kg, Medal Rounds – Inunganbi Takhellambam (Subject to qualification)TRACK CYCLING AND PARA TRACK CYCLING2:30 p.m. – Men’s Sprint Qualifying – David Beckham Elkatohchoongo, Ronaldo Singh Laitonjam, Rojit Singh Yanglem3:27 p.m. – Men’s Sprint 1/8 Finals – David Beckham Elkatohchoongo, Ronaldo Singh Laitonjam, Rojit Singh Yanglem (Subject to qualification)4:03 p.m. onwards – Men’s Sprint Quarterfinals – David Beckham Elkatohchoongo, Ronaldo Singh Laitonjam, Rojit Singh Yanglem (Subject to qualification)4:19 p.m. – Men’s 10km Scratch Race Qualifying Round – Dinesh Kumar, Harshveer Singh Sekhon7:38 p.m. – Men’s Sprint Semifinals – David Beckham Elkatohchoongo, Ronaldo Singh Laitonjam, Rojit Singh Yanglem (Subject to qualification)10:02 p.m. onwards – Men’s Sprint Finals – David Beckham Elkatohchoongo, Ronaldo Singh Laitonjam, Rojit Singh Yanglem (Subject to qualification)10:50 p.m. – Men’s 10km Scratch Race Final – Dinesh Kumar, Harshveer Singh Sekhon (Subject to qualification)  #CWG #LIVE #updates #Glasgow #India #wins #gold #silver #bronze

Post Comment