×
Caitlin Clark is playing the best basketball of her career  In Tuesday night’s Indiana Fever win over the Seattle Storm, Caitlin Clark was on one. Clark tallied 32 points on 9-14 shooting to go along with 7 assists and 4 rebounds, and the Fever improved to 18-10 on the season.Amid the usual litany of off-court storylines, it’s been a superb on-court season for the Fever star.Clark is averaging 21.5 points per game, the third-most in the league, and 7.9 assists per game, the second-most in the league. (In other words, no single player creates more on offense than she does).She’s also quietly upped her efficiency — in her rookie season (in which she was named to the All-WNBA First Team), she shot 41.7% from the field and 34.4% from three. In her sophomore season (in which she appeared in just 13 games due to a myriad of injuries), she shot worse, hitting 36.7% of her shot attempts and 27.9% of her threes.And, this year, she’s shooting 44.3% from the field and 35.4% from three, both career-highs. While turnovers continue to be an Achilles heel, she’s averaging fewer per game this year (4.7) than in her rookie campaign (5.6).Clark now has the 31st-best true shooting percentage in the WNBA (60.3%), which means she’s been more efficient than a long list of top guards that includes Marina Mabrey, Jackie Young, Chelsea Gray, Allisha Gray, Rhyne Howard, Sabrina Ionescu, Veronica Burton, Courtney Williams, and dozens of others. (Kelsey Plum, Sonia Citron, Kelsey Mitchell, Kayla McBride, Paige Bueckers, and Olivia Miles have all been more efficient, however).It still feels like there’s another gear Clark can reach from beyond the arc — she shot 37.7% from three in college — but even if that doesn’t happen, she’s established herself as one of the league’s best guards just a season removed from a campaign in which she missed time due to groin and ankle injuries.Most importantly, the Fever are winning. They currently have the 5th-best record in the WNBA, but they’re only a game and a half removed from second place, where the Las Vegas Aces currently sit. They have the second-highest point differential in the league (+6), which trails only the Minnesota Lynx. They’re averaging 95.8 points per game, which is 4 more points than the team with the next-highest points per game average (Minnesota).Clark is still just 24 years old — and will likely get a lot better before she peaks. But, as strange as it is to say about the most polarizing player in basketball, she’s quietly already having a career year.  #Caitlin #Clark #playing #basketball #career

Caitlin Clark is playing the best basketball of her career

In Tuesday night’s Indiana Fever win over the Seattle Storm, Caitlin Clark was on one. Clark tallied 32 points on 9-14 shooting to go along with 7 assists and 4 rebounds, and the Fever improved to 18-10 on the season.

Amid the usual litany of off-court storylines, it’s been a superb on-court season for the Fever star.

Clark is averaging 21.5 points per game, the third-most in the league, and 7.9 assists per game, the second-most in the league. (In other words, no single player creates more on offense than she does).

She’s also quietly upped her efficiency — in her rookie season (in which she was named to the All-WNBA First Team), she shot 41.7% from the field and 34.4% from three. In her sophomore season (in which she appeared in just 13 games due to a myriad of injuries), she shot worse, hitting 36.7% of her shot attempts and 27.9% of her threes.

And, this year, she’s shooting 44.3% from the field and 35.4% from three, both career-highs. While turnovers continue to be an Achilles heel, she’s averaging fewer per game this year (4.7) than in her rookie campaign (5.6).

Clark now has the 31st-best true shooting percentage in the WNBA (60.3%), which means she’s been more efficient than a long list of top guards that includes Marina Mabrey, Jackie Young, Chelsea Gray, Allisha Gray, Rhyne Howard, Sabrina Ionescu, Veronica Burton, Courtney Williams, and dozens of others. (Kelsey Plum, Sonia Citron, Kelsey Mitchell, Kayla McBride, Paige Bueckers, and Olivia Miles have all been more efficient, however).

It still feels like there’s another gear Clark can reach from beyond the arc — she shot 37.7% from three in college — but even if that doesn’t happen, she’s established herself as one of the league’s best guards just a season removed from a campaign in which she missed time due to groin and ankle injuries.

Most importantly, the Fever are winning. They currently have the 5th-best record in the WNBA, but they’re only a game and a half removed from second place, where the Las Vegas Aces currently sit. They have the second-highest point differential in the league (+6), which trails only the Minnesota Lynx. They’re averaging 95.8 points per game, which is 4 more points than the team with the next-highest points per game average (Minnesota).

Clark is still just 24 years old — and will likely get a lot better before she peaks. But, as strange as it is to say about the most polarizing player in basketball, she’s quietly already having a career year.

#Caitlin #Clark #playing #basketball #career

In Tuesday night’s Indiana Fever win over the Seattle Storm, Caitlin Clark was on one. Clark tallied 32 points on 9-14 shooting to go along with 7 assists and 4 rebounds, and the Fever improved to 18-10 on the season.

Amid the usual litany of off-court storylines, it’s been a superb on-court season for the Fever star.

Clark is averaging 21.5 points per game, the third-most in the league, and 7.9 assists per game, the second-most in the league. (In other words, no single player creates more on offense than she does).

She’s also quietly upped her efficiency — in her rookie season (in which she was named to the All-WNBA First Team), she shot 41.7% from the field and 34.4% from three. In her sophomore season (in which she appeared in just 13 games due to a myriad of injuries), she shot worse, hitting 36.7% of her shot attempts and 27.9% of her threes.

And, this year, she’s shooting 44.3% from the field and 35.4% from three, both career-highs. While turnovers continue to be an Achilles heel, she’s averaging fewer per game this year (4.7) than in her rookie campaign (5.6).

Clark now has the 31st-best true shooting percentage in the WNBA (60.3%), which means she’s been more efficient than a long list of top guards that includes Marina Mabrey, Jackie Young, Chelsea Gray, Allisha Gray, Rhyne Howard, Sabrina Ionescu, Veronica Burton, Courtney Williams, and dozens of others. (Kelsey Plum, Sonia Citron, Kelsey Mitchell, Kayla McBride, Paige Bueckers, and Olivia Miles have all been more efficient, however).

It still feels like there’s another gear Clark can reach from beyond the arc — she shot 37.7% from three in college — but even if that doesn’t happen, she’s established herself as one of the league’s best guards just a season removed from a campaign in which she missed time due to groin and ankle injuries.

Most importantly, the Fever are winning. They currently have the 5th-best record in the WNBA, but they’re only a game and a half removed from second place, where the Las Vegas Aces currently sit. They have the second-highest point differential in the league (+6), which trails only the Minnesota Lynx. They’re averaging 95.8 points per game, which is 4 more points than the team with the next-highest points per game average (Minnesota).

Clark is still just 24 years old — and will likely get a lot better before she peaks. But, as strange as it is to say about the most polarizing player in basketball, she’s quietly already having a career year.

Source link
#Caitlin #Clark #playing #basketball #career

Deadspin | Jose Soriano, possibly in final game with Angels, faces Brewers  May 16, 2026; Anaheim, California, USA;  Los Angeles Angels pitcher Jose Soriano (59) pitches during the first inning against the Los Angeles Dodgers at Angel Stadium. Mandatory Credit: Kiyoshi Mio-Imagn Images   Los Angeles Angels right-hander Jose Soriano can match his career high in wins when he faces the Milwaukee Brewers in the second game of their three-game series on Saturday night in Anaheim, Calif.    Soriano (9-6, 3.29 ERA), rumored to be on the trading block heading into Monday’s trade deadline, won a career-best 10 games last season while also losing 11 games. It will be just his second career start against the Brewers. The first one didn’t go well.    Soriano’s final start of the 2025 season came Sept. 17 at Milwaukee when he was charged with the loss in a 9-2 setback. He allowed three runs on two hits and two walks in just 1 1/3 innings and left after taking a line drive with a 107.4 mph exit velocity by Jake Bauers off his right forearm.    Soriano walked off the field under his own power after that comebacker and X-rays of the arm were negative afterward, but he didn’t pitch again the rest of the season.    Soriano will be sad to see the calendar flip to August after a July that saw him go 1-1 in four starts with a 2.74 ERA. He allowed just 14 hits and seven earned runs in 23 innings with 16 strikeouts and comes in off a 4-3 victory at San Francisco on Sunday where he allowed one unearned run on three hits over five innings while striking out five.    “I thought he was really good today,” Angels manager Kurt Suzuki said after the game.     Left-hander Robert Gasser (3-4, 4.71), who never has faced the Angels, will try to give Milwaukee the series win. He is 3-1 with a 3.92 ERA in his last seven starts with 33 strikeouts in 39 innings pitched.    Gasser, who was obtained by the Brewers from the San Diego Padres on Aug. 1, 2022, as part of a trade for reliever Josh Hader, comes in off an 8-5 win over the Colorado Rockies on Saturday that saw him allow two runs on five hits in six innings with no walks and four strikeouts.    Milwaukee started a stretch of 17 games in 17 days with a 6-2 victory in Friday’s series opener. Brice Turang and Jake Bauers both homered during a five-run fifth inning, and rookie left-hander Shane Drohan allowed two runs on four hits over six innings to pick up the win.    It was Drohan’s fourth consecutive start of six-plus innings with six-plus strikeouts.     “He was fantastic,” Milwaukee manager Pat Murphy said of Drohan, postgame. “He was in control. This is a tough lineup for him to navigate with all the righties, and he did a great job. This kid has been, I don’t know how many in a row, but this has been probably six or seven in a row that he’s been in the sixth (inning). He’s kept us in every game he’s pitched.”    “Super impressive,” Bauers said of Drohan. “The guy is stone cold. He’s stone cold in the clubhouse, he’s stone cold in the dugout and he’s stone cold on the mound. I don’t know how he does it. It’s a pleasure to watch him pitch and work behind him.”  -Field Level Media    #Deadspin #Jose #Soriano #possibly #final #game #Angels #faces #BrewersMay 16, 2026; Anaheim, California, USA; Los Angeles Angels pitcher Jose Soriano (59) pitches during the first inning against the Los Angeles Dodgers at Angel Stadium. Mandatory Credit: Kiyoshi Mio-Imagn Images

Los Angeles Angels right-hander Jose Soriano can match his career high in wins when he faces the Milwaukee Brewers in the second game of their three-game series on Saturday night in Anaheim, Calif.

Soriano (9-6, 3.29 ERA), rumored to be on the trading block heading into Monday’s trade deadline, won a career-best 10 games last season while also losing 11 games. It will be just his second career start against the Brewers. The first one didn’t go well.

Soriano’s final start of the 2025 season came Sept. 17 at Milwaukee when he was charged with the loss in a 9-2 setback. He allowed three runs on two hits and two walks in just 1 1/3 innings and left after taking a line drive with a 107.4 mph exit velocity by Jake Bauers off his right forearm.

Soriano walked off the field under his own power after that comebacker and X-rays of the arm were negative afterward, but he didn’t pitch again the rest of the season.

Soriano will be sad to see the calendar flip to August after a July that saw him go 1-1 in four starts with a 2.74 ERA. He allowed just 14 hits and seven earned runs in 23 innings with 16 strikeouts and comes in off a 4-3 victory at San Francisco on Sunday where he allowed one unearned run on three hits over five innings while striking out five.

“I thought he was really good today,” Angels manager Kurt Suzuki said after the game.


Left-hander Robert Gasser (3-4, 4.71), who never has faced the Angels, will try to give Milwaukee the series win. He is 3-1 with a 3.92 ERA in his last seven starts with 33 strikeouts in 39 innings pitched.

Gasser, who was obtained by the Brewers from the San Diego Padres on Aug. 1, 2022, as part of a trade for reliever Josh Hader, comes in off an 8-5 win over the Colorado Rockies on Saturday that saw him allow two runs on five hits in six innings with no walks and four strikeouts.

Milwaukee started a stretch of 17 games in 17 days with a 6-2 victory in Friday’s series opener. Brice Turang and Jake Bauers both homered during a five-run fifth inning, and rookie left-hander Shane Drohan allowed two runs on four hits over six innings to pick up the win.

It was Drohan’s fourth consecutive start of six-plus innings with six-plus strikeouts.

“He was fantastic,” Milwaukee manager Pat Murphy said of Drohan, postgame. “He was in control. This is a tough lineup for him to navigate with all the righties, and he did a great job. This kid has been, I don’t know how many in a row, but this has been probably six or seven in a row that he’s been in the sixth (inning). He’s kept us in every game he’s pitched.”

“Super impressive,” Bauers said of Drohan. “The guy is stone cold. He’s stone cold in the clubhouse, he’s stone cold in the dugout and he’s stone cold on the mound. I don’t know how he does it. It’s a pleasure to watch him pitch and work behind him.”


-Field Level Media

#Deadspin #Jose #Soriano #possibly #final #game #Angels #faces #Brewers">Deadspin | Jose Soriano, possibly in final game with Angels, faces Brewers  May 16, 2026; Anaheim, California, USA;  Los Angeles Angels pitcher Jose Soriano (59) pitches during the first inning against the Los Angeles Dodgers at Angel Stadium. Mandatory Credit: Kiyoshi Mio-Imagn Images   Los Angeles Angels right-hander Jose Soriano can match his career high in wins when he faces the Milwaukee Brewers in the second game of their three-game series on Saturday night in Anaheim, Calif.    Soriano (9-6, 3.29 ERA), rumored to be on the trading block heading into Monday’s trade deadline, won a career-best 10 games last season while also losing 11 games. It will be just his second career start against the Brewers. The first one didn’t go well.    Soriano’s final start of the 2025 season came Sept. 17 at Milwaukee when he was charged with the loss in a 9-2 setback. He allowed three runs on two hits and two walks in just 1 1/3 innings and left after taking a line drive with a 107.4 mph exit velocity by Jake Bauers off his right forearm.    Soriano walked off the field under his own power after that comebacker and X-rays of the arm were negative afterward, but he didn’t pitch again the rest of the season.    Soriano will be sad to see the calendar flip to August after a July that saw him go 1-1 in four starts with a 2.74 ERA. He allowed just 14 hits and seven earned runs in 23 innings with 16 strikeouts and comes in off a 4-3 victory at San Francisco on Sunday where he allowed one unearned run on three hits over five innings while striking out five.    “I thought he was really good today,” Angels manager Kurt Suzuki said after the game.     Left-hander Robert Gasser (3-4, 4.71), who never has faced the Angels, will try to give Milwaukee the series win. He is 3-1 with a 3.92 ERA in his last seven starts with 33 strikeouts in 39 innings pitched.    Gasser, who was obtained by the Brewers from the San Diego Padres on Aug. 1, 2022, as part of a trade for reliever Josh Hader, comes in off an 8-5 win over the Colorado Rockies on Saturday that saw him allow two runs on five hits in six innings with no walks and four strikeouts.    Milwaukee started a stretch of 17 games in 17 days with a 6-2 victory in Friday’s series opener. Brice Turang and Jake Bauers both homered during a five-run fifth inning, and rookie left-hander Shane Drohan allowed two runs on four hits over six innings to pick up the win.    It was Drohan’s fourth consecutive start of six-plus innings with six-plus strikeouts.     “He was fantastic,” Milwaukee manager Pat Murphy said of Drohan, postgame. “He was in control. This is a tough lineup for him to navigate with all the righties, and he did a great job. This kid has been, I don’t know how many in a row, but this has been probably six or seven in a row that he’s been in the sixth (inning). He’s kept us in every game he’s pitched.”    “Super impressive,” Bauers said of Drohan. “The guy is stone cold. He’s stone cold in the clubhouse, he’s stone cold in the dugout and he’s stone cold on the mound. I don’t know how he does it. It’s a pleasure to watch him pitch and work behind him.”  -Field Level Media    #Deadspin #Jose #Soriano #possibly #final #game #Angels #faces #Brewers

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

Post Comment