Skip to main content

Report: NBA fines LaMelo Ball $60k for Bam Adebayo trip, postgame cursing

Danby: Daniel Hager04/16/26DanielHagerOn3

Charlotte Hornets guard LaMelo Ball has been fined $35,000 for his trip of Miami Heat forward Bam Adebayo in Tuesday night’s NBA Play-In Game, ESPN’s Shams Charania reported.

Ball was also fined $25,000 for cursing postgame. In total, that’s a $60,000 fine for the former NBA All-Star. The Hornets will face off against the loser of Wednesday night’s Eastern Conference Play-In Game between the Orlando Magic/Philadelphia 76ers for the No. 8 seed in the East.

Early in the second half of Tuesday night’s game, Adebayo attempted to save a ball from going out of bounds. It appeared as if Ball then swiped at Adebayo’s feet, which led to the Heat star falling flat on his back. He did not return to the game, and the Heat went on to lose 127-126 in overtime.

“I apologize on that one,” Ball said postgame. “I got hit in the head, didn’t really know where I was, but I’mma check on him and see if he’s okay and everything.”

One reporter took the questioning even further, asking Ball if the action was on purpose. Ball says he has not yet watched the video. 

“I haven’t even seen it,” Ball said. “Like I said, I got hit in the head, didn’t even know where I was. But just playing basketball. Like I said, sorry. Was just playing basketball.”

Hornets-Heat crew chief explained why play didn’t go to review

Pool reporter Rod Boone of the Charlotte Observer asked crew chief Zach Zarba why the play did not go to a review. Zarba said because there was no stoppage, there wasn’t a window to head to the monitor.

“The play wasn’t whistled in real time,” Zarba said. “Play continued with a fast break. And because play wasn’t stopped immediately, and there was no whistle on the play, the window to review the play was closed. Play was stopped, after a change of possession, and then a time out. So, by rule, our window to review that play then is closed.”

However, Zarba said the crew reviewed the play at halftime, as is standard procedure. As for whether the play should have gone to the flagrant, it now goes to the league office for a final decision.

“At this point, that goes to league operations, and they’ll make a determination on that in the coming days,” Zarba said. “So, they will make that determination and go from there.”

Ball has now been assessed a retroactive flagrant for the play, but will be available for Thursday night’s game.

On3’s Nick Schultz contributed to this article.