Seattle sports, on tap daily

Chase Briscoe’s No. 19 Toyota Was Loose and the 123-Point Deficit Is Getting Brutal

trophy logo on gradient background

Written by

in

trophy logo on gradient background
trophy logo on gradient background — Created by the Sports On Tap desk | Source : Sports On Tap (team logos property of their respective owners)

Chase Briscoe was just seven laps away from turning a tough Chase into a massive win at Kansas, but a loose No. 19 Toyota let Kyle Larson snatch back the lead and widen an already brutal championship deficit. Starting way back in 23rd, Briscoe showed incredible drive, working his way through the field to become Larson’s main challenger in the final stage.

He Drove Like a Beast, Then It All Fell Apart

Briscoe’s climb was epic. He finished fourth in Stage 2, showing he had the speed. After the final green-flag pit sequence, he absolutely chased Larson down and took the lead on Lap 238. You could feel the momentum building, like this was going to be the race that turned his championship hopes around.

The No. 19 Just Couldn’t Hold On

But then disaster struck. As the run continued, his No. 19 Toyota became increasingly loose. Larson, sensing the opportunity, pounced and retook the lead on Lap 261. The agony! It got worse, too: contact with the wall cost Briscoe two more positions before the checkered flag waved. He still finished fourth and grabbed 40 points, which is something, but that missed opportunity? It had major championship consequences.

Briscoe is now sitting eighth in the Chase standings with 2,159 points, a staggering 123 points behind Larson, who just had a maximum-points afternoon. With only six races left, Briscoe needs substantial gains quickly. This isn’t over yet, but Kansas just made the road ahead a whole lot steeper.

This article was created with AI assistance and published under Seattle On Tap’s editorial standards. See our Editorial Policy.

Originally reported by Yahoo Sports.

About the author

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *