×
The Jets’ NFL Draft process has been chaotic even by their dysfunctional standards  The New York Jets have effectively been on the clock for two months, and it’s unclear if they know what they’re doing on Thursday night. Everyone has known that the Raiders are taking QB Fernando Mendoza with the No. 1 pick since the NFL Scouting Combine in February, which meant the draft effectively starts at No. 2. The issue is that the lead-up to making the pick has been so peppered with so much chaos that it’s impossible to get a bead on what they’re doing.It might be easy to shrug this off as “smokescreen,” which fans tend to do during a nonsensical draft lead up — but there’s public information showing that the Jets might do something very weird with the No. 2 pick. To being with: A trade seems very unlikely. There is one guy seemingly worth making the jump for and that’s Ohio State’s Arvell Reese, who is the No. 1 player on our big board — and also an ideal player for the Jets.Head coach Aaron Glenn is moving the Jets to a 3-4 base defense in his sophomore season, which precipitated the team’s trade with the Titans for T’Vondre Sweat. It’s assumed that the Jets will be using a hybrid front, which has become commonplace in the NFL — and nobody is better equipped in this draft for defensive variability than Reese. The ultimate toolbox player, you can throw him on the edge and get pressure, but also move him inside where he’s a reliable enough box linebacker to play Mike or Will in a different alignment.So what’s the problem? Throughout the process there have been reports out of New York that the Jets were lukewarm on Reese. The organization has no reason to lie about any interest, because they’re in the driver’s seat. In addition, the only way you potentially bait a trade if you aren’t interested in Reese is by feigning interest and getting an offer you can’t refuse, not the other way around. It’s semi-understandable why the Jets have cold feet when it comes to the Ohio State prospect, because he’s not a finished product. There’s work to be done, and his true position isn’t set in stone. That’s worrisome for an organization wanting to compete right now, and doesn’t necessarily have the luxury to spend time developing a player.The lack of interest in Reese caused people to turn their attention to Texas Tech’s David Bailey, who is the next-most obvious pick for the Jets. His position is set as a 3-4 EDGE, he will come in and get pressures immediately, Bailey will help the Jets right now — but give it three years, and he might end up simply being a Top 10 pass rusher, not a transcendent player the way Reese can. Still, that might be good enough to land a reliable building block that Glenn and Co. can count on.“Okay, so the pick is going to be David Bailey,” you might say — except for the fact that the Jets cancelled their Top 30 visit with him. It’s definitely not unheard of to see teams take players without Top 30 visits, but not typically in the Top 5. At the very least, an organization is happy to bring in an intended target just to show them the facilities, have them get used to the culture, get a sense of the player away from the distractions of the Pro Day or the Combine.Now we have two guys who are in play at No. 2, with the Jets giving signals they’re interested in both, and disinterested in equal measure.If you hope to glean information from their Top 30 visits, good luck. A total of 14 visits were spent on players grading from the 5th round, to UDFAs — including five players who weren’t even ranked on Top 500 prospect boards. The team literally cancelled a visit with David Bailey to accommodate a player who won’t be drafted, resting on their laurels of seeing him at the combine and pro day.In the simplest terms: The Jets aren’t operating like any other team in the NFL. That could be a sign of genius as they pull something out of this class we didn’t expect, but being different isn’t always a good thing when it comes to the draft. You might think you’re playing chess while everyone else is playing checkers, but it winds up you were playing Hungry, Hungry Hippos all along.  #Jets #NFL #Draft #process #chaotic #dysfunctional #standards

The Jets’ NFL Draft process has been chaotic even by their dysfunctional standards

The New York Jets have effectively been on the clock for two months, and it’s unclear if they know what they’re doing on Thursday night. Everyone has known that the Raiders are taking QB Fernando Mendoza with the No. 1 pick since the NFL Scouting Combine in February, which meant the draft effectively starts at No. 2. The issue is that the lead-up to making the pick has been so peppered with so much chaos that it’s impossible to get a bead on what they’re doing.

It might be easy to shrug this off as “smokescreen,” which fans tend to do during a nonsensical draft lead up — but there’s public information showing that the Jets might do something very weird with the No. 2 pick. To being with: A trade seems very unlikely. There is one guy seemingly worth making the jump for and that’s Ohio State’s Arvell Reese, who is the No. 1 player on our big board — and also an ideal player for the Jets.

Head coach Aaron Glenn is moving the Jets to a 3-4 base defense in his sophomore season, which precipitated the team’s trade with the Titans for T’Vondre Sweat. It’s assumed that the Jets will be using a hybrid front, which has become commonplace in the NFL — and nobody is better equipped in this draft for defensive variability than Reese. The ultimate toolbox player, you can throw him on the edge and get pressure, but also move him inside where he’s a reliable enough box linebacker to play Mike or Will in a different alignment.

So what’s the problem? Throughout the process there have been reports out of New York that the Jets were lukewarm on Reese. The organization has no reason to lie about any interest, because they’re in the driver’s seat. In addition, the only way you potentially bait a trade if you aren’t interested in Reese is by feigning interest and getting an offer you can’t refuse, not the other way around. It’s semi-understandable why the Jets have cold feet when it comes to the Ohio State prospect, because he’s not a finished product. There’s work to be done, and his true position isn’t set in stone. That’s worrisome for an organization wanting to compete right now, and doesn’t necessarily have the luxury to spend time developing a player.

The lack of interest in Reese caused people to turn their attention to Texas Tech’s David Bailey, who is the next-most obvious pick for the Jets. His position is set as a 3-4 EDGE, he will come in and get pressures immediately, Bailey will help the Jets right now — but give it three years, and he might end up simply being a Top 10 pass rusher, not a transcendent player the way Reese can. Still, that might be good enough to land a reliable building block that Glenn and Co. can count on.

“Okay, so the pick is going to be David Bailey,” you might say — except for the fact that the Jets cancelled their Top 30 visit with him. It’s definitely not unheard of to see teams take players without Top 30 visits, but not typically in the Top 5. At the very least, an organization is happy to bring in an intended target just to show them the facilities, have them get used to the culture, get a sense of the player away from the distractions of the Pro Day or the Combine.

Now we have two guys who are in play at No. 2, with the Jets giving signals they’re interested in both, and disinterested in equal measure.

If you hope to glean information from their Top 30 visits, good luck. A total of 14 visits were spent on players grading from the 5th round, to UDFAs — including five players who weren’t even ranked on Top 500 prospect boards. The team literally cancelled a visit with David Bailey to accommodate a player who won’t be drafted, resting on their laurels of seeing him at the combine and pro day.

In the simplest terms: The Jets aren’t operating like any other team in the NFL. That could be a sign of genius as they pull something out of this class we didn’t expect, but being different isn’t always a good thing when it comes to the draft. You might think you’re playing chess while everyone else is playing checkers, but it winds up you were playing Hungry, Hungry Hippos all along.

#Jets #NFL #Draft #process #chaotic #dysfunctional #standards

The New York Jets have effectively been on the clock for two months, and it’s unclear if they know what they’re doing on Thursday night. Everyone has known that the Raiders are taking QB Fernando Mendoza with the No. 1 pick since the NFL Scouting Combine in February, which meant the draft effectively starts at No. 2. The issue is that the lead-up to making the pick has been so peppered with so much chaos that it’s impossible to get a bead on what they’re doing.

It might be easy to shrug this off as “smokescreen,” which fans tend to do during a nonsensical draft lead up — but there’s public information showing that the Jets might do something very weird with the No. 2 pick. To being with: A trade seems very unlikely. There is one guy seemingly worth making the jump for and that’s Ohio State’s Arvell Reese, who is the No. 1 player on our big board — and also an ideal player for the Jets.

Head coach Aaron Glenn is moving the Jets to a 3-4 base defense in his sophomore season, which precipitated the team’s trade with the Titans for T’Vondre Sweat. It’s assumed that the Jets will be using a hybrid front, which has become commonplace in the NFL — and nobody is better equipped in this draft for defensive variability than Reese. The ultimate toolbox player, you can throw him on the edge and get pressure, but also move him inside where he’s a reliable enough box linebacker to play Mike or Will in a different alignment.

So what’s the problem? Throughout the process there have been reports out of New York that the Jets were lukewarm on Reese. The organization has no reason to lie about any interest, because they’re in the driver’s seat. In addition, the only way you potentially bait a trade if you aren’t interested in Reese is by feigning interest and getting an offer you can’t refuse, not the other way around. It’s semi-understandable why the Jets have cold feet when it comes to the Ohio State prospect, because he’s not a finished product. There’s work to be done, and his true position isn’t set in stone. That’s worrisome for an organization wanting to compete right now, and doesn’t necessarily have the luxury to spend time developing a player.

The lack of interest in Reese caused people to turn their attention to Texas Tech’s David Bailey, who is the next-most obvious pick for the Jets. His position is set as a 3-4 EDGE, he will come in and get pressures immediately, Bailey will help the Jets right now — but give it three years, and he might end up simply being a Top 10 pass rusher, not a transcendent player the way Reese can. Still, that might be good enough to land a reliable building block that Glenn and Co. can count on.

“Okay, so the pick is going to be David Bailey,” you might say — except for the fact that the Jets cancelled their Top 30 visit with him. It’s definitely not unheard of to see teams take players without Top 30 visits, but not typically in the Top 5. At the very least, an organization is happy to bring in an intended target just to show them the facilities, have them get used to the culture, get a sense of the player away from the distractions of the Pro Day or the Combine.

Now we have two guys who are in play at No. 2, with the Jets giving signals they’re interested in both, and disinterested in equal measure.

If you hope to glean information from their Top 30 visits, good luck. A total of 14 visits were spent on players grading from the 5th round, to UDFAs — including five players who weren’t even ranked on Top 500 prospect boards. The team literally cancelled a visit with David Bailey to accommodate a player who won’t be drafted, resting on their laurels of seeing him at the combine and pro day.

In the simplest terms: The Jets aren’t operating like any other team in the NFL. That could be a sign of genius as they pull something out of this class we didn’t expect, but being different isn’t always a good thing when it comes to the draft. You might think you’re playing chess while everyone else is playing checkers, but it winds up you were playing Hungry, Hungry Hippos all along.

Source link
#Jets #NFL #Draft #process #chaotic #dysfunctional #standards

Previous post

Sanju Samson scores second century of IPL 2026 <div id="content-body-70898540" itemprop="articleBody"><p>Sanju Samson on Thursday scored his second century of the IPL 2026 season during Chennai Super Kings’ match against Mumbai Indians at the Wankhede Stadium.</p><p><b>ALSO READ: <a href="https://sportstar.thehindu.com/cricket/ipl/most-hundreds-in-ipl-record-stats-virat-kohli-sanju-samson-mi-vs-csk-ipl-2026/article70898534.ece" target="_self">Most hundreds in IPL: Sanju Samson enters top 5 five with fifth century during MI vs CSK</a></b></p><p>The 31-year-old completed his ton in 54 balls with the help of 10 fours and six sixes. Samson’s innings helped his team post 207 for six in 20 overs.</p><p>His first hundred in the season came against Delhi Capitals, when he scored an unbeaten 115 off just 56 balls. Samson now has five centuries in the tournament. Only three other batters have scored more hundreds than him.</p><p class="publish-time" id="end-of-article">Published on Apr 23, 2026</p></div> #Sanju #Samson #scores #century #IPL

Next post

Deadspin | Streaking Cubs ride offense into finale vs. sinking Phillies <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/28789710.jpg" srcset="https://images.deadspin.com/tr:w-900/28789710.jpg" alt="MLB: Philadelphia Phillies at Chicago Cubs" class="w-full" fetchpriority="high" loading="eager"/><span class="text-0.8 leading-tight">Apr 22, 2026; Chicago, Illinois, USA; Chicago Cubs center fielder Pete Crow-Armstrong (4) hits an RBI single against the Philadelphia Phillies during the eighth inning at Wrigley Field. Mandatory Credit: Patrick Gorski-Imagn Images<!-- --> <!-- --> </span></div></section><section id="section-1"> <p>Searching for a four-game sweep of the reeling Philadelphia Phillies, the host Chicago Cubs will have an opportunity to extend their winning streak to nine games on Thursday afternoon.</p> </section><section id="section-2"> <p>Should that be the case, the Cubs will have their longest such run since they won 11 in a row from July 31-Aug. 12, 2016.</p> </section><section id="section-3"> <p>Manager Craig Counsell’s club hasn’t allowed more than four runs in any of the eight wins, and the offense has recorded back-to-back seven-run outputs. Pete Crow-Armstrong had three hits in Wednesday’s 7-2 victory to increase his batting average 22 points to .247, while Michael Busch connected on his first home run after going deep 34 times a season ago.</p> </section><section id="section-4"> <p>“I think that’s what makes you a good offense,” Counsell said. “You’re never going to have all nine guys rolling at the same time. If you have enough good hitters in there, you expect a group of them to be seeing it well and swinging it well at one time. Some of the guys that are off to a little bit of a slower start had big nights (on Wednesday). That’s how I think a good offense should work.”</p> </section><section id="section-5"> <p>Hoping to finish the homestand at 7-0, right-hander Edward Cabrera (2-0, 2.38 ERA) will look to continue to make a good impression in his fifth start with Chicago. After a January trade from the Miami Marlins, Cabrera has allowed just six earned runs in 22 2/3 innings for his new club.</p> </section><section id="section-6"> <p>Cabrera went six innings last time out, surrendering three runs on eight hits in a 12-4 victory over the New York Mets. Cabrera has leaned on his changeup as a go-to pitch, throwing it 36.6% of the time through four starts.</p> </section><section id="section-7"> <p>“The changeup has to start in the zone for him,” Counsell said of Cabrera. “It doesn’t have to finish in the zone, but it’s got to start in the zone. That’s when he’s really good. It’s not always a strike, but getting that changeup over the plate is important, because he’s going to get swings out of the zone on it.”</p> </section><br/><section id="section-8"> <p>Cabrera is 2-2 with a 3.57 ERA in eight career starts against the Phillies.</p> </section> <section id="section-9"> <p>Philadelphia, which has been outscored 19-7 in the series, saw its losing skid extend to eight games on Wednesday, It’s the Phillies’ longest such streak since 2018.</p> </section><section id="section-10"> <p>Despite sharing a spot with the New York Mets (8-16) for the worst record in the National League, the Phillies are far from ready to throw in the towel.</p> </section><section id="section-11"> <p>“Baseball is a long season and we’ve got a long way to go,” manager Rob Thomson said. “I think there’s a lot of frustration here, but at the same time, these guys know we have a talented group. We just have to stay after it and keep fighting. This is a talented group.”</p> </section><section id="section-12"> <p>Left-hander Cristopher Sanchez (2-2, 1.59) will make the start for Philadelphia, bringing the NL’s third best ERA and second most strikeouts (39) into action.</p> </section><section id="section-13"> <p>Despite a dazzling start to his sixth big-league campaign, Sanchez suffered his second loss in his past three appearances against the Atlanta Braves on Saturday. Sanchez allowed three unearned runs in six innings in a 3-1 setback, a duel with Sale.</p> </section><section id="section-14"> <p>Sanchez has faced the Cubs three times, compiling a 1-1 record and a 7.36 ERA in the matchup. He threw six innings of six-hit, two-run ball in a 13-7 win over the Chicago Cubs on April 13.</p> </section><section id="section-15"> <p>–Field Level Media</p> </section></div> #Deadspin #Streaking #Cubs #ride #offense #finale #sinking #Phillies

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