Framber Valdez’s Rough Night Ends With Ejection After Hit-by-Pitch
TL;DR
Framber Valdez was ejected in the fourth inning after hitting Trevor Story with a pitch following back-to-back home runs by Willson Contreras and Wilyer Abreu. The incident led to benches clearing and an on-field delay.
Key points
- Framber Valdez was ejected in the fourth inning
- He hit Trevor Story after two home runs
- Willson Contreras and Wilyer Abreu hit back-to-back homers
- Benches cleared after the hit-by-pitch incident
- No prior warning was given before the ejection
Framber Valdez’s Rough Night Ends With Ejection After Hit-by-Pitch
There are times when intent is obvious. A pitcher gives up a long home run, stares down the hitter, gets the ball back and drills the next guy. Nobody needs a courtroom. Everybody in the ballpark knows what happened.
This did not feel quite that clean with Framber Valdez.
Valdez was ejected in the fourth inning Tuesday after hitting Trevor Story following back-to-back home runs by Willson Contreras and Wilyer Abreu. The sequence looked bad on paper. Contreras homered. Abreu followed with another home run. Story was then hit by a pitch. Benches cleared, there was an on-field delay, and third-base umpire Dan Iassogna ejected Valdez, even though there had been no prior warning listed in the game sequence.
That is the part that makes this strange.
The Red Sox had already done damage against Valdez, but the first inning also came with a missed chance for the Tigers to limit it. With two outs and one runner on, Story reached on Zach McKinstry’s fielding error, moving Wilyer Abreu to third. Story then stole second, and Ceddanne Rafaela followed with a three-run home run to right-center field. What could have been a clean escape became a 3-0 Boston lead.
Valdez wasnt pitching at his best, but it was not all clean contact from the beginning. The Tigers gave Boston an extra out, and the Red Sox made them pay for it.
Detroit answered in the bottom half, with Matt Vierling leading off with a home run and Wenceel Pérez adding an RBI single to make it 3-2. For a minute, the game looked like it could settle back down. Instead, Boston pulled away again in the third. Valdez walked Willson Contreras, then allowed five straight hits as the Red Sox stretched the lead to 8-2. Story was in the middle of that rally, singling to right field and later scoring on Andruw Monasterio’s single.
By the time the fourth inning started, Valdez was not protecting a lead, sending an early message or trying to control a tight game. He was getting hit around. The Tigers were already chasing the game. If anything, Detroit needed innings from him more than it needed a pointless confrontation, just after a bullpen game.
The optics, though, were terrible. Contreras opened the fourth with a home run. Abreu followed with another. Then Story was hit by a pitch. That is the kind of sequence that gets everyone’s attention, especially if the hitter reacts and the benches empty.
Still, bad optics are not the same thing as clear intent.
Valdez was frustrated, sure. Any pitcher would be after an error extended the first inning, a three-run homer followed, and Boston kept stacking hits. But frustration is not proof that he was trying to hit Story. His command had already been poor. Boston had already put together long innings against him. The game had already gotten away from him.
That is where Valdez’s reputation probably did him no favors. He has been involved in hit-by-pitch tension before, and when a pitcher with that history hits a batter immediately after back-to-back home runs, umpires are going to view it through a different lens. Fair or not, reputation tends to follow a pitcher to the mound.
But this still felt closer to assumption than proof.
If there had been a warning, the ejection would have been easier to understand. If Valdez had clearly thrown behind Story, stared him down or shown obvious intent, there would not be much debate. Instead, it looked like an umpire read the situation, saw the sequence and made a quick decision.
Maybe that decision was right. Maybe Valdez, had seen enough after two home runs and decided to send a message. Then the reputation that Astros fans have said on social media comes to mind.
The more reasonable read is that this was a bad outing, made worse by defensive mistakes, poor command, Boston’s hard contact and Valdez’s own reputation. The pitch to Story came at the worst possible time, in the worst possible sequence, from a pitcher who probably was not going to get much benefit of the doubt.
That does not mean the ejection was outrageous. It means it felt rushed. Boston had every right to feel like it was on purpose but no warning? Regardless, just frustrating to to watch to know what was going to happen after throwing his first four-seamer of the season.
Valdez did not pitch well enough to earn sympathy for the outing itself. But if the standard is intent, not optics, this one still feels strange. The Tigers were already buried, Boston had already done its damage, and Detroit needed Valdez to keep taking the ball more than it needed him to start a benches-clearing mess.
It looked accidental. It looked ugly. And because it was Framber Valdez, it was treated like something more.
Follow me on "X" @rogcastbaseball
Q&A
Why was Framber Valdez ejected from the game?
Framber Valdez was ejected for hitting Trevor Story with a pitch after consecutive home runs, despite no prior warnings being issued.
What happened during the incident involving Framber Valdez?
After hitting Trevor Story, benches cleared, leading to an on-field delay and Valdez's ejection by the umpire.
Who hit back-to-back home runs before Valdez's ejection?
Willson Contreras and Wilyer Abreu hit back-to-back home runs before Framber Valdez hit Trevor Story with a pitch.
What was the reaction to Valdez hitting Trevor Story?
The reaction included benches clearing and an on-field delay, indicating heightened tensions during the game.