Connect with us

Sports

Breece Hall injury update: Jets RB ruled out vs. Lions

Published

on

Advertisement

The New York Jets cut into their deficit against the Detroit Lions, but lost star running back Breece Hall for the game in the process. Hall suffered a thigh injury on a second-and-goal run in the fourth quarter, and the Jets’ medical staff ruled him out following an evaluation in the sideline medical tent.

Hall ran toward the sideline on the short-yardage play and hit the ground hard on a tackle by Lions linebacker Trevor Nowaske. Most of Hall’s weight landed on his right hip area.

The Jets trailed by 14 points at the time of the injury but closed the drive with a touchdown. They eventually tied the game at 24 to erase a two-touchdown deficit and pulled off the comeback without Hall in the lineup.

Hall handled 13 carries for 32 yards and caught three passes for an additional 23 yards before he exited the contest. He entered Week 2 as the Jets’ leader in yards from scrimmage with 131 on the ground and 79 through the air, and he was one of three players to log a rushing touchdown in the early part of the season.

Advertisement

Any time that Hall misses will force the Jets to operate without their most effective offensive weapon. Hall stands among the NFL’s most prolific pass-catchers at the running back position. He ranked in a tie for third on the team in receptions across the season’s first two games.

Braelon Allen leaped into a larger role upon Hall’s exit. New York’s No. 2 running back is familiar with the increased workload, as he shouldered additional weight in 2024 when Hall battled a knee injury. Allen missed the majority of the 2025 season due to a knee injury of his own, though, and is now two years removed from that promising rookie campaign in which he started two games and totaled 334 rushing yards and two touchdowns.

Advertisement

Source link

Continue Reading
Click to comment

You must be logged in to post a comment Login

Leave a Reply

Sports

Noah Gragson disappointed after mechanical woes at Kansas Speedway

Published

on

Noah Gragson’s strong run at Kansas Speedway ended with an engine failure during the NASCAR Hollywood Casino 400. The Front Row Motorsports driver had been running around the top 20 after making progress in his No. 4 Ford, but a mechanical problem ended his race early, leaving him with a disappointing result.

Gragson started 21st after the starting lineup was set by the qualifying metric. He had an average running position of 28.58 and lost spots during the Stage 1 pit stops, but a good adjustment helped him recover from 26th to 18th in Stage 2. That progress ended on Lap 114 when the No. 4 Ford engine failed. He was running 20th at the time and said on the radio:

“Blew up.”

FRM No. 4 team immediately acknowledged his effort to keep the car under control:

Advertisement

“Good job hanging on to it.”

Noah Gragson replied:

“Thanks. Good car. Sh**ty result. Thanks for the effort today.”

Noah Gragson’s No. 4 Ford went sideways on the inside line before producing a large amount of smoke as he moved into Turns 1 and 2. He managed to avoid spinning and did not collect anyone, for the first incident-led caution in the race.

The restart that followed then produced a major incident involving Carson Hocevar in the middle of a multi-car crash. Gragson’s race, however, was already over, with his No. 4 officially listed as a DNF on Lap 152.


Noah Gragson reacts after the Kansas DNF

Noah Gragson with a Front Row Motorsports member at Pocono. Source: GettyNoah Gragson with a Front Row Motorsports member at Pocono. Source: Getty
Noah Gragson with a Front Row Motorsports member at Pocono. Source: Getty

Noah Gragson’s Kansas result comes after Front Row Motorsports announced on August 14 that he would return to the No. 4 Ford for the 2027 NASCAR Cup Series season, with options to extend beyond next year. The contract extension came during a difficult season for Gragson, who entered Kansas 31st in the standings with 376 points.

Since the announcement, Gragson had finished 18th at Richmond and 10th at New Hampshire, his second-best result. He then finished 32nd at Daytona, 33rd at Darlington, 16th at Gateway and 16th at Bristol before the Kansas DNF. Asked whether there was any indication of the engine problem, Gragson said:

Advertisement

“We were pretty good. Just proud of everybody at Front Row Motorsports and on the Long John Silver’s car. We kind of struggled here in the spring, and we’ve been showing a lot of progress into the last couple of weeks. We were 16th at Bristol, and we’re having a strong showing today, running 17th around there, 16th. So we’re entering in on it. Just unfortunate, but it’s the way it goes sometimes.”

Noah Gragson‘s post-race comments showed that the No. 4 FRM team had made progress compared with its spring Kansas performance. Despite the engine failure, he felt the car had enough speed to run around the middle of the top 20. He will now look to recover on his home track next week at Las Vegas Motor Speedway.