×
Shubman Gill injury update: Will GT captain play vs Delhi Capitals?  Gujarat Titans skipper Shubman Gill remains a fitness watch ahead of Wednesday’s IPL clash against Delhi Capitals after missing the previous game with a muscle spasm.Gill had sat out the contest against Rajasthan Royals in Ahmedabad, where visuals showed him heavily bandaged around the shoulder and neck area. The concern is not entirely new. The 26-year-old had also dealt with neck spasms during India’s 2025-26 home Test season, raising questions about recurrence and workload management.However, there was a positive update on Tuesday as Gill returned to training.In Gill’s absence, Gujarat Titans pushed Rajasthan Royals to the brink, falling just six runs short while chasing 210. That performance could influence team management’s decision, allowing them the luxury of not rushing their captain back unless he is fully fit.If cleared, Gill will slot straight back into the XI. If not, Titans may once again take the field with Rashid Khan as captainPublished on Apr 08, 2026  #Shubman #Gill #injury #update #captain #play #Delhi #Capitals

Shubman Gill injury update: Will GT captain play vs Delhi Capitals?

Gujarat Titans skipper Shubman Gill remains a fitness watch ahead of Wednesday’s IPL clash against Delhi Capitals after missing the previous game with a muscle spasm.

Gill had sat out the contest against Rajasthan Royals in Ahmedabad, where visuals showed him heavily bandaged around the shoulder and neck area. The concern is not entirely new. The 26-year-old had also dealt with neck spasms during India’s 2025-26 home Test season, raising questions about recurrence and workload management.

However, there was a positive update on Tuesday as Gill returned to training.

In Gill’s absence, Gujarat Titans pushed Rajasthan Royals to the brink, falling just six runs short while chasing 210. That performance could influence team management’s decision, allowing them the luxury of not rushing their captain back unless he is fully fit.

If cleared, Gill will slot straight back into the XI. If not, Titans may once again take the field with Rashid Khan as captain

Published on Apr 08, 2026

#Shubman #Gill #injury #update #captain #play #Delhi #Capitals

Gujarat Titans skipper Shubman Gill remains a fitness watch ahead of Wednesday’s IPL clash against Delhi Capitals after missing the previous game with a muscle spasm.

Gill had sat out the contest against Rajasthan Royals in Ahmedabad, where visuals showed him heavily bandaged around the shoulder and neck area. The concern is not entirely new. The 26-year-old had also dealt with neck spasms during India’s 2025-26 home Test season, raising questions about recurrence and workload management.

However, there was a positive update on Tuesday as Gill returned to training.

In Gill’s absence, Gujarat Titans pushed Rajasthan Royals to the brink, falling just six runs short while chasing 210. That performance could influence team management’s decision, allowing them the luxury of not rushing their captain back unless he is fully fit.

If cleared, Gill will slot straight back into the XI. If not, Titans may once again take the field with Rashid Khan as captain

Published on Apr 08, 2026

Source link
#Shubman #Gill #injury #update #captain #play #Delhi #Capitals

Previous post

Deadspin | Hot-starting Flyers blast Devils to boost playoff chances <div id=""><section id="0" class=" w-full"><div class="xl:container mx-0 !px-4 py-0 pb-4 !mx-0 !px-0"><img src="https://images.deadspin.com/tr:w-900/28679402.jpg" srcset="https://images.deadspin.com/tr:w-900/28679402.jpg" alt="NHL: Philadelphia Flyers at New Jersey Devils" class="w-full" fetchpriority="high" loading="eager"/><span class="text-0.8 leading-tight">Apr 7, 2026; Newark, New Jersey, USA; Philadelphia Flyers right wing Matvei Michkov (39) skates with the puck against the New Jersey Devils during the first period at Prudential Center. Mandatory Credit: Luther Schlaifer-Imagn Images<!-- --> <!-- --> </span></div></section><section id="section-1"> <p>Trevor Zegras and Tyson Foerster both scored a pair of goals for the Philadelphia Flyers, who strengthened their hold on an Eastern Conference playoff spot by beating the New Jersey Devils 5-1 Tuesday in Newark, N.J.</p> </section><section id="section-2"> <p>Zegras’ tallies give him 25 goals for the season, while Foerster, who returned last week after missing four months of action due to an arm injury, now has 13 in 25 games played. Nick Seeler added his third goal of the season.</p> </section><section id="section-3"> <p>Zegras added his 40th assist, and Matvei Michkov assisted on both of Foerster’s. Dan Vladar stopped 23 shots for the Flyers (40-26-12, 92 points), who have won 40 games for the first time since the 2019-20 season.</p> </section><section id="section-4"> <p>Cody Glass scored for the third time in his last four games, with assists from Jonas Siegenthaler and Lenni Hameenaho on the Devils’ lone goal.</p> </section><section id="section-5"> <p>Jacob Markstrom made 14 saves on 18 shots for New Jersey (40-35-3, 83 points), which was eliminated from playoff contention with the regulation loss paired with Ottawa’s win over Tampa Bay.</p> </section><section id="section-6"> <p>The Flyers did their damage early in each of the first two periods. Zegras started the scoring just 1:56 into the game. Travis Sanheim’s circle-to-circle pass set up Zegras, as Markstrom could not recover in time.</p> </section><br/><section id="section-7"> <p>Just 1:42 later, Zegras doubled the Flyers’ lead on a power-play goal. After dishing the puck to Porter Martone at the Devils’ blueline, he crashed the net to tip in the rookie’s shot.</p> </section> <section id="section-8"> <p>Zegras became the second-fastest Flyer to score two goals to start a game. Brian Propp holds the record, netting a pair in the first 1:58 at Calgary on Feb. 27, 1982.</p> </section><section id="section-9"> <p>The Devils would control the rest of the period but only got Glass’ goal with 7:48 left.</p> </section><section id="section-10"> <p>Foerster got his pair in the first five minutes of the second, both coming seconds after the Devils had prime chances.</p> </section><section id="section-11"> <p>Michkov sprung Foerster for a 2-on-1 with Tippett. Foerster kept the puck for himself and made it 3-1 with 17:14 remaining in the period.</p> </section><section id="section-12"> <p>Foerster’s second came after Jesper Bratt’s breakaway chance rang off the crossbar. Moments later, Foerster started a 3-on-2 with Zegras and Michkov and slammed home the puck with 15:02 left.</p> </section><section id="section-13"> <p>The Devils pulled Markstrom with just less than five minutes left. Seeler ended the scoring with 2:51 remaining, scoring his first point since Feb. 26 and first goal since Jan. 15.</p> </section><br/><section id="section-14"> <p>–Field Level Media</p> </section> </div> #Deadspin #Hotstarting #Flyers #blast #Devils #boost #playoff #chances

Next post

Deadspin | Reds avoid near-blanking, force extras to stun Marlins <div id=""><section id="0" class=" w-full"><div class="xl:container mx-0 !px-4 py-0 pb-4 !mx-0 !px-0"><img src="https://images.deadspin.com/tr:w-900/28679060.jpg" srcset="https://images.deadspin.com/tr:w-900/28679060.jpg" alt="MLB: Cincinnati Reds at Miami Marlins" class="w-full" fetchpriority="high" loading="eager"/><span class="text-0.8 leading-tight">Apr 7, 2026; Miami, Florida, USA; Cincinnati Reds starting pitcher Andrew Abbott (41) pitches against the Miami Marlins in the first inning at loanDepot Park. Mandatory Credit: Rhona Wise-Imagn Images<!-- --> <!-- --> </span></div></section><section id="section-1"> <p>The Cincinnati Reds — scoreless against Sandy Alcantara until the ninth inning — rallied to defeat the host Miami Marlins 6-3 in 10 innings on Tuesday night.</p> </section><section id="section-2"> <p>Cincinnati tied the score in the ninth on a two-out wild pitch by Anthony Bender, and the Reds took control in the 10th on Nathaniel Lowe’s go-ahead RBI single and Matt McLain’s two-run double.</p> </section><section id="section-3"> <p>Alcantara, who was removed after 95 pitches, took a tough-luck no-decision as his 30-inning streak of not allowing an earned run was broken in the ninth.</p> </section><section id="section-4"> <p>He allowed just three hits — two singles and one double — plus two walks and two runs in 8 1/3 innings, striking out six. Miami started the ninth with a 2-0 lead, and both runs were scored while Bender was on the mound.</p> </section><section id="section-5"> <p>Marlins center fielder Jakob Marsee, who entered the game batting just .105, went 2-for-4 with one walk, two runs and a career-high four stolen bases. In 65 previous major league games, Marsee had stolen only 15 bases.</p> </section><section id="section-6"> <p>Reds starter Andrew Abbott took a no-decision, allowing six hits, two walks and two runs in 5 1/3 innings.</p> </section><br/><section id="section-7"> <p>Alcantara retired Cincinnati’s first 12 batters before Miami native Sal Stewart singled to open the fifth.</p> </section> <section id="section-8"> <p>Meanwhile, the Marlins opened the scoring in the fourth. The rally started with leadoff batter Agustin Ramirez’s blistering 113-mph double that was nearly caught by left fielder Spencer Steer, who retreated only to have the ball deflect off the top of his glove.</p> </section><section id="section-9"> <p>Next, Marsee tried a sacrifice bunt that turned into a single when he beat the throw at first. That put runners on the corners, and Miami cashed in with Otto Lopez’s RBI groundout. Marsee, who had stolen second base, scored on another RBI groundout, this one by Heriberto Hernandez.</p> </section><section id="section-10"> <p>The Reds tied the score in the ninth. With one out and none on, the Reds chased Alcantara after McLain’s double and Elly De La Cruz’s walk. Bender allowed a double steal, and Stewart delivered a sacrifice fly to spoil the shutout. Bender then bounced a wild pitch, allowing De La Cruz to score from third.</p> </section><section id="section-11"> <p>In the top of the 10th, the biggest hits were Lowe’s 106-mph single to center that made it 3-2 and McLain’s 386-foot drive to left for a pair of insurance runs.</p> </section><section id="section-12"> <p>Graham Ashcraft allowed one run in the bottom half on a fielder’s choice before a game-ending double play.</p> </section><section id="section-13"> <p>–Field Level Media</p> </section></div> #Deadspin #Reds #avoid #nearblanking #force #extras #stun #Marlins

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