×
Deadspin | Dustin May’s best outing of season leads Cardinals past Red Sox  Apr 10, 2026; St. Louis, Missouri, USA;  St. Louis Cardinals right fielder Jordan Walker (18) heads to third base and then home in the fifth inning against the Boston Red Sox at Busch Stadium. Mandatory Credit: Tim Vizer-Imagn Images   Dustin May pitched six solid innings as the St. Louis Cardinals edged the visiting Boston Red Sox 3-2 on Friday in the opener of a three-game weekend series.  Jordan Walker went 2-for-4 with a run to help lead St. Louis, which had an 8-5 advantage in hits and won its third straight game. Ramon Urias crossed the plate twice, and Jose Fermin knocked in the decisive run in the fifth inning.  May (1-2), who entered the game with a 15.95 ERA through two starts, allowed two runs (one earned) on four hits and no walks. He struck out four.  Riley O’Brien pitched a 1-2-3 ninth to post his fourth save out of the Cardinals’ bullpen, which allowed just one hit across three scoreless innings.  Wilyer Abreu went 2-for-4 and Trevor Story drove in a run and stole home for the Red Sox, whose two-game winning streak ended.  In the St. Louis second inning, Ramon Urias ripped a leadoff double off Ceddanne Rafaela’s glove in deep center field, and the Cardinals loaded the bases with no outs. Boston starter Connelly Early limited the damage to just a single run, which scored on Victor Scott II’s sacrifice fly.  Early ended the inning with a strikeout, just as he did in each of his four full frames. The southpaw threw 86 pitches in his 4 1/3-inning stint, striking out five while allowing one run on five hits and two walks.   After May set the Red Sox down in order for his first 1-2-3 inning of the season in the third, the Red Sox moved in front with a two-run fourth.  Masataka Yoshida led off with a line single to right, and after Abreu’s one-out hit, Story plated the tying run on a fielder’s-choice grounder. Story advanced to second on a throwing error on the play, and he moved to third on Marcelo Mayer’s single before sliding home safely on a successful double steal.  Early departed after retiring the leadoff batter in the fifth, but the next three batters reached against Zack Kelly. St. Louis got a game-tying RBI single to left from Thomas Saggese, who entered the game after Masyn Winn got hit by a pitch. A wild pitch from Kelly moved put two runners into scoring position, and Fermin’s sacrifice fly made it a 3-2 lead.  Kelly (0-1) yielded two runs in two-thirds of an inning.  May retired the last seven hitters he faced before reliever Ryne Stanek continued that trend in the seventh. Rafaela opened the eighth with a double inside the right field line, and Boston had runners on the corners with one out, but JoJo Romero stranded them.  –Field Level Media   #Deadspin #Dustin #Mays #outing #season #leads #Cardinals #Red #Sox

Deadspin | Dustin May’s best outing of season leads Cardinals past Red Sox
Deadspin | Dustin May’s best outing of season leads Cardinals past Red Sox  Apr 10, 2026; St. Louis, Missouri, USA;  St. Louis Cardinals right fielder Jordan Walker (18) heads to third base and then home in the fifth inning against the Boston Red Sox at Busch Stadium. Mandatory Credit: Tim Vizer-Imagn Images   Dustin May pitched six solid innings as the St. Louis Cardinals edged the visiting Boston Red Sox 3-2 on Friday in the opener of a three-game weekend series.  Jordan Walker went 2-for-4 with a run to help lead St. Louis, which had an 8-5 advantage in hits and won its third straight game. Ramon Urias crossed the plate twice, and Jose Fermin knocked in the decisive run in the fifth inning.  May (1-2), who entered the game with a 15.95 ERA through two starts, allowed two runs (one earned) on four hits and no walks. He struck out four.  Riley O’Brien pitched a 1-2-3 ninth to post his fourth save out of the Cardinals’ bullpen, which allowed just one hit across three scoreless innings.  Wilyer Abreu went 2-for-4 and Trevor Story drove in a run and stole home for the Red Sox, whose two-game winning streak ended.  In the St. Louis second inning, Ramon Urias ripped a leadoff double off Ceddanne Rafaela’s glove in deep center field, and the Cardinals loaded the bases with no outs. Boston starter Connelly Early limited the damage to just a single run, which scored on Victor Scott II’s sacrifice fly.  Early ended the inning with a strikeout, just as he did in each of his four full frames. The southpaw threw 86 pitches in his 4 1/3-inning stint, striking out five while allowing one run on five hits and two walks.   After May set the Red Sox down in order for his first 1-2-3 inning of the season in the third, the Red Sox moved in front with a two-run fourth.  Masataka Yoshida led off with a line single to right, and after Abreu’s one-out hit, Story plated the tying run on a fielder’s-choice grounder. Story advanced to second on a throwing error on the play, and he moved to third on Marcelo Mayer’s single before sliding home safely on a successful double steal.  Early departed after retiring the leadoff batter in the fifth, but the next three batters reached against Zack Kelly. St. Louis got a game-tying RBI single to left from Thomas Saggese, who entered the game after Masyn Winn got hit by a pitch. A wild pitch from Kelly moved put two runners into scoring position, and Fermin’s sacrifice fly made it a 3-2 lead.  Kelly (0-1) yielded two runs in two-thirds of an inning.  May retired the last seven hitters he faced before reliever Ryne Stanek continued that trend in the seventh. Rafaela opened the eighth with a double inside the right field line, and Boston had runners on the corners with one out, but JoJo Romero stranded them.  –Field Level Media   #Deadspin #Dustin #Mays #outing #season #leads #Cardinals #Red #SoxApr 10, 2026; St. Louis, Missouri, USA; St. Louis Cardinals right fielder Jordan Walker (18) heads to third base and then home in the fifth inning against the Boston Red Sox at Busch Stadium. Mandatory Credit: Tim Vizer-Imagn Images

Dustin May pitched six solid innings as the St. Louis Cardinals edged the visiting Boston Red Sox 3-2 on Friday in the opener of a three-game weekend series.

Jordan Walker went 2-for-4 with a run to help lead St. Louis, which had an 8-5 advantage in hits and won its third straight game. Ramon Urias crossed the plate twice, and Jose Fermin knocked in the decisive run in the fifth inning.

May (1-2), who entered the game with a 15.95 ERA through two starts, allowed two runs (one earned) on four hits and no walks. He struck out four.

Riley O’Brien pitched a 1-2-3 ninth to post his fourth save out of the Cardinals’ bullpen, which allowed just one hit across three scoreless innings.

Wilyer Abreu went 2-for-4 and Trevor Story drove in a run and stole home for the Red Sox, whose two-game winning streak ended.

In the St. Louis second inning, Ramon Urias ripped a leadoff double off Ceddanne Rafaela’s glove in deep center field, and the Cardinals loaded the bases with no outs. Boston starter Connelly Early limited the damage to just a single run, which scored on Victor Scott II’s sacrifice fly.


Early ended the inning with a strikeout, just as he did in each of his four full frames. The southpaw threw 86 pitches in his 4 1/3-inning stint, striking out five while allowing one run on five hits and two walks.

After May set the Red Sox down in order for his first 1-2-3 inning of the season in the third, the Red Sox moved in front with a two-run fourth.

Masataka Yoshida led off with a line single to right, and after Abreu’s one-out hit, Story plated the tying run on a fielder’s-choice grounder. Story advanced to second on a throwing error on the play, and he moved to third on Marcelo Mayer’s single before sliding home safely on a successful double steal.

Early departed after retiring the leadoff batter in the fifth, but the next three batters reached against Zack Kelly. St. Louis got a game-tying RBI single to left from Thomas Saggese, who entered the game after Masyn Winn got hit by a pitch. A wild pitch from Kelly moved put two runners into scoring position, and Fermin’s sacrifice fly made it a 3-2 lead.

Kelly (0-1) yielded two runs in two-thirds of an inning.

May retired the last seven hitters he faced before reliever Ryne Stanek continued that trend in the seventh. Rafaela opened the eighth with a double inside the right field line, and Boston had runners on the corners with one out, but JoJo Romero stranded them.

–Field Level Media

#Deadspin #Dustin #Mays #outing #season #leads #Cardinals #Red #Sox

Apr 10, 2026; St. Louis, Missouri, USA; St. Louis Cardinals right fielder Jordan Walker (18) heads to third base and then home in the fifth inning against the Boston Red Sox at Busch Stadium. Mandatory Credit: Tim Vizer-Imagn Images

Dustin May pitched six solid innings as the St. Louis Cardinals edged the visiting Boston Red Sox 3-2 on Friday in the opener of a three-game weekend series.

Jordan Walker went 2-for-4 with a run to help lead St. Louis, which had an 8-5 advantage in hits and won its third straight game. Ramon Urias crossed the plate twice, and Jose Fermin knocked in the decisive run in the fifth inning.

May (1-2), who entered the game with a 15.95 ERA through two starts, allowed two runs (one earned) on four hits and no walks. He struck out four.

Riley O’Brien pitched a 1-2-3 ninth to post his fourth save out of the Cardinals’ bullpen, which allowed just one hit across three scoreless innings.

Wilyer Abreu went 2-for-4 and Trevor Story drove in a run and stole home for the Red Sox, whose two-game winning streak ended.

In the St. Louis second inning, Ramon Urias ripped a leadoff double off Ceddanne Rafaela’s glove in deep center field, and the Cardinals loaded the bases with no outs. Boston starter Connelly Early limited the damage to just a single run, which scored on Victor Scott II’s sacrifice fly.

Early ended the inning with a strikeout, just as he did in each of his four full frames. The southpaw threw 86 pitches in his 4 1/3-inning stint, striking out five while allowing one run on five hits and two walks.

After May set the Red Sox down in order for his first 1-2-3 inning of the season in the third, the Red Sox moved in front with a two-run fourth.

Masataka Yoshida led off with a line single to right, and after Abreu’s one-out hit, Story plated the tying run on a fielder’s-choice grounder. Story advanced to second on a throwing error on the play, and he moved to third on Marcelo Mayer’s single before sliding home safely on a successful double steal.

Early departed after retiring the leadoff batter in the fifth, but the next three batters reached against Zack Kelly. St. Louis got a game-tying RBI single to left from Thomas Saggese, who entered the game after Masyn Winn got hit by a pitch. A wild pitch from Kelly moved put two runners into scoring position, and Fermin’s sacrifice fly made it a 3-2 lead.

Kelly (0-1) yielded two runs in two-thirds of an inning.

May retired the last seven hitters he faced before reliever Ryne Stanek continued that trend in the seventh. Rafaela opened the eighth with a double inside the right field line, and Boston had runners on the corners with one out, but JoJo Romero stranded them.

–Field Level Media

Source link
#Deadspin #Dustin #Mays #outing #season #leads #Cardinals #Red #Sox

Previous post

PBKS vs SRH, IPL 2026: Punjab Kings’ batters overpower Sunrisers Hyderabad to continue unbeaten run <div id="content-body-70851327" itemprop="articleBody"><p>Just hours after the Artemis II crew splashed down from their historic journey around the moon, a few willow-wielders took guard at the Maharaja Yadavindra Singh Stadium as if they were determined to send some cricket balls back into the lunar orbit.</p><p>A mammoth 442 runs were plundered by the Punjab Kings and Sunrisers Hyderabad batters, at the end of which PBKS triumphed by six wickets.</p><p>While Abhishek Sharma’s 28-ball 74 (5×4, 8×6) proved the launchpad for SRH’s 219 for six, Priyansh Arya (57, 20b, 5×4, 5×6), Prabhsimran Singh (51, 25b, 4×4, 4×6) and Shreyas Iyer (69 n.o., 33b, 5×4, 5×6) ensured PBKS remained unbeaten in IPL 2026.</p><p>SRH left-arm wrist-spinner Shivang Kumar bowled with gumption (three for 33) and priced out the PBKS top-order, but the damage had been done before he was introduced in the seventh over.</p><p>While Abhishek’s half-century came off 18 balls, Priyansh’s came two deliveries faster. It took the SRH openers 3.4 overs to breach the 50-run mark; their counterparts did it in 3.3.</p><p>The blistering start made the rest of the run chase a formality as skipper Shreyas took the side home with seven deliveries to spare.</p><p><b>ALSO READ: <a href="https://sportstar.thehindu.com/cricket/ipl/lucknow-super-giants-vs-gujarat-titans-ipl-2026-lsg-v-gt-match-preview-ekana/article70850769.ece" target="_self">IPL 2026: Resurgent Lucknow Super Giants looks for a win at home against Gujarat Titans</a></b></p><p>Earlier, Arshdeep Singh’s 10-ball second over went for 24 runs, as Abhishek punished anything in his arc with elan.</p><p>Part-time bowler Shashank Singh proved to be the unlikely circuit-breaker after the 105-run PowerPlay.</p><p>The gentle medium-pacer repaid the faith shown by Shreyas by having Travis Head (38, 23b, 5×4, 1×6) and Abhishek caught in the deep.</p><p>After being 120 for no loss in eight overs, the SRH innings decelerated.</p><p>Arshdeep’s 14th over saw two contrasting fielding efforts. While Marcus Stoinis dropped Heinrich Klaasen at long-off, Marco Jansen ran to his right and plucked the ball out of thin air with his outstretched right hand to send back Ishan Kishan.</p><p>The nonchalance of the whole exercise saw Arshdeep cover his mouth and sit down in disbelief, though the crowd’s reaction was to stand up and applaud.</p><p>Later, Klaasen tossed his bat in the air out of frustration after his scratchy innings (39, 33b, 1×4, 1×6). Perhaps he knew that his knock would come back to haunt his team.</p><p>The PBKS willow-wielders made sure of it.</p><p class="publish-time" id="end-of-article">Published on Apr 11, 2026</p></div> #PBKS #SRH #IPL #Punjab #Kings #batters #overpower #Sunrisers #Hyderabad #continue #unbeaten #run

Next post

IPL 2026 — Sanju Samson hits first fifty for Chennai Super Kings <div id="content-body-70851488" itemprop="articleBody"><p>Sanju Samson on Saturday scored his maiden half century for five-time champion Chennai Super Kings during the side’s IPL 2026 match against Delhi Capitals at the M.A. Chidambaram Stadium.</p><p>The 31-year-old was traded in by CSK from Rajasthan Royals ahead of the season, in place of Ravindra Jadeja and Sam Curran.</p><p>Samson picked boundaries against Mukesh Kumar, Auqib Nabi, Lungi Ngidi, T. Natarajan and Axar Patel as he raced away to a 26-ball half century.</p><p>This was the 27th fifty for Samson in the IPL. He had scored 19 for RR and another seven for Delhi Capitals. Samson also has three centuries under his belt.</p><p class="publish-time" id="end-of-article">Published on Apr 11, 2026</p></div> #IPL #Sanju #Samson #hits #fifty #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