Browsing: Fumble

You can drop your clubs and you can drop your score, but as it turns out, it’s pretty hard to do both. That’s what Ryo Hisatsune learned in unusually painful fashion on Sunday afternoon at the Australian Open.

Hisatsune was grinding through the end of a challenging week at Royal Melbourne when he reached the green on the 8th hole, a long par-4. From the greenside, he faced a classic Australian sandbelt golf shot: A testy chip off a firm lie into a green protected by big swales.

But as luck would have it, the chip would be the leastof Hisatsune’s concerns on the 8th hole. His biggest issue? A fait accomplibetween his 56-degree and gravity.

As he walked to his pitch shot, Hisatsune’s caddie Taiga Tabuchi handed him his wedge. But then, as Hisatsune stepped to address his ball, something went wrong: His club slipped through his hands and fell to the ground, striking his golf ball and sending it skittering a few feet in the other direction.

Now, in some instances, this kind of indiscretion would be little more than cause for a chuckle. Under Rule 9.4 of the Rules of Golf, players are permitted to replace their ball without penalty if such action happens on the putting surface or teeing area, if it occurs during the search for a lost ball, or if a “reasonable action” caused the ball to move, like removing a loose impediment or retrieving another ball.

But, because Hisatsune’s hiccup wasn’t covered under these actions, the penalty was slightly more severe than “replace and forget it.” Hisatsune was assessed a one-shot penalty and instructed to return his ball to its original position.

The bad news for Hisatsune is that his club fumble made a difficult par all but impossible. After receiving confirmation from a rules official, he chipped onto the green and quickly tidied away a double-bogey 6 — his first of two such big numbers on a Sunday afternoon that ended his day and weekend at 6 over, in a tie for 51st.

The good news was that the damage was over almost instantly. Hisatsune was able to return his ball to its original position and continue on his round with only a one-shot penalty.

And perhaps a better grip on his wedges.

Washington Commanders quarterback Jayden Daniels took responsibility for a fourth-quarter fumble that played a significant role in Washington’s 25-24 road loss to the Chicago Bears on Monday night.

According to Nicki Jhabvala of The Athletic, Daniels said: “I just lost the ball. Completely my fault. Didn’t give [running back] Bill [Croskey-Merritt] a chance, so it’s my fault.”

With just over three minutes remaining in the game, the Commanders had a third-and-1 at the Chicago 40-yard line while leading by two points, and Daniels attempted to hand the ball off to his rookie running back.

However, the ball hit the ground on the exchange, and Bears cornerback Nahshon Wright jumped on it for the fumble recovery.

Close-up replays on the ABC broadcast showed the ball slipping out of Daniels’ hands before he could make a clean handoff to Croskey-Merritt, resulting in the fumble.

The conditions undoubtedly made the handoff more difficult than usual, as both teams dealt with rain throughout the game.

After the fumble, the Washington offense never saw the ball again. Quarterback Caleb Williams took control for the Bears and authored a nine-play, 36-yard drive that resulted in embattled kicker Jake Moody hitting a 38-yard field goal for the win as time expired.

Daniels had some great moments in Monday’s game, throwing for 211 yards and three touchdowns, and rushing for another 52 yards, but he also made some key mistakes.

On top of the fumble, Daniels threw an interception and took three sacks on the night.

That would normally be attributed to the trials and tribulations of a young quarterback, but Daniels’ performance as a rookie last season put him on a pedestal compared to other signal-callers of his experience level.

En route to being named NFL Offensive Rookie of the Year and earning a Pro Bowl berth, Daniels completed 69.0 percent of his passes, while throwing for 3,568 yards, 25 touchdowns and nine picks. He also rushed for 891 yards and six scores.

On top of that, Daniels led the Commanders to their first playoff berth since 2020 and took them all the way to the NFC Championship Game.

Daniels is off to another strong statistical start with 875 passing yards, seven touchdowns and one interception, and 176 yards on the ground through four starts. However, he has gone just 2-2, and the Commanders are 3-3 overall, as Daniels previously missed two starts due to injury.

There is plenty of time for Daniels and the rest of the Commanders to regroup and get back on track, but they allowed a winnable game to slip through their hands Monday, both literally and figuratively.

Source link

Arizona Cardinals running back Emari Demercado owned up to his costly turnover in Sunday’s 22-21 loss to the Tennessee Titans.

With Arizona leading by 15 points in the fourth quarter, Demercado got loose for what initially looked like a 72-yard touchdown run. Unfortunately for he and the Cardinals, he started his celebration prematurely. He lost possession before crossing the goal line, and the ball went out of the end zone for a touchback.

“I made a mistake. There’s really no excuse,” Demercado told reporters after the game. “I was obviously emotional. It was a big play, but I just got to be smarter.”

The third-year back added he’s not going to think about the play any longer than he needs to.

“You just have to,” he said. “Can’t get it back. Nothing I can do about it, so why keep holding on to it?”

It’s almost certainly game over if the Cardinals jump ahead by 22 points with less than 13 minutes to play. Instead, the Titans got a major lifeline.

Tennessee got touchdowns on its next two drives, and Joey Slye connected on a 29-yard field goal as time expired to give his team its first win.

Demercado’s fumble wasn’t the sole reason for Arizona’s late collapse, and the football gods seemed to be tipping the scales in favor of the Titans. You don’t often see a defensive interception turn into an offensive touchdown, which is what happened during the frenzied fourth quarter.

With a losing skid that now sits at three games, Arizona will hope its luck in Week 6 improves as it hits the road to play the red-hot Indianapolis Colts.

Source link

Pakistan spurned an easy run out chance against Bangladesh in the 5th over (Image via X/@FarziCricketer) Pakistan endured an embarrassing moment of chaos in the field during Bangladeshâ€s chase in their Asia Cup Super 4s clash on Thursday, when a straightforward run-out chance went begging in the fifth over. Shaheen Afridi had just started a new spell when Bangladesh were 23/1.Towhid Hridoy cut his strike to backward point. Saim Ayub dived brilliantly to stop the ball and threw it to the bowlerâ€s end, where Saif Hassan was stranded almost halfway down the pitch. But no one was backing up. The fielder at the receiver’s end then failed to collect cleanly, allowing Saif to run back to safety.Ayub, who had done all the hard work, looked visibly frustrated. Pakistan skipper Salman Agha too, was not impressed with the way his team let an easy wicket chance slip in this must win match.Watch the hilarious mix up here The grand escape, however, lasted just one delivery. On the very next ball, Hridoy went for a reckless hit across the line and mistimed it poorly. This time, Ayub made no mistake, as settled under it to complete the catch. Shaheen had his second wicket and finally something to smile about after the confusion of the previous delivery. Earlier in the match, Pakistanâ€s batting line-up faltered again under pressure. Bangladeshâ€s bowlers Taskin Ahmed (3/28), Mustafizur Rahman (1/33) and Rishad Hossain (2/18) controlled the innings as Pakistan ended at 135 for eight. Sahibzada Farhan (4) became Taskinâ€s 100th T20I wicket, while Saim Ayubâ€s run of low scores continued with his fourth duck. Fakhar Zaman (13), Hussain Talat (3) and Salman Ali Agha (19) also fell cheaply.

Poll

Which aspect of Pakistan’s game needs the most improvement?

But even that recovery was quickly overshadowed by the bizarre run-out blunder, as this moment summed up Pakistanâ€s struggles in this high-stakes encounter.

Source link

Baltimore Ravens running back Derrick Henry said he was “at a loss for words” after his third fumble of the 2025 NFL season contributed to a 38-30 defeat to the Detroit Lions.

“It’s just crazy,” he told reporters. “Three fumbles [in three games] straight. I’m trying every day to fix the problem that just keeps occurring. I’m my worst critic, so I’m not going to try to beat myself up too much. But it’s hard not to when it’s consecutive and consistent [instances] of me doing the same thing.”

Henry also apologized to his teammates, coaches and Ravens fans:

The Ravens trailed the Lions by four points when the five-time Pro Bowler coughed the ball up on his own 21-yard line. Detroit secured the recovery, which set up a 45-yard field goal by Jake Bates to make it a 31-24 game with 6:35 on the clock.

A similar scene played out in Week 1. Henry fumbled in the fourth quarter as the Buffalo Bills were mounting a 15-point comeback en route to a 41-40 win. He was just as contrite on that occasion as well.

Monday’s result was down to more than the costly turnover.

Baltimore’s defense allowed 426 yards to the Lions. The backfield tandem of David Montgomery and Jahmyr Gibbs combined for 218 yards and four touchdowns on the ground.

In the second quarter, the Ravens came away with zero points from a 1st-and-goal at the 3-yard line, and failing to score proved consequential in hindsight.

The offense also had an opportunity to tie the game after Bates’ field goal. A three-and-out put the ball back in the Lions’ hands and they pulled away with Montgomery’s 31-yard touchdown run.

It’s easy to zero in on Henry because he made such an obvious mistake. The Ravens coaches will have plenty to nitpick when they go over the game film.

Source link