Slot Machine Malfunctions and Falsely Displays a $166M Payout

Written by Haylie | Thursday, November 12th, 2009

The Seminole Tribe of Florida operates a slew of reputable, land-based American Indian casinos across the state of Florida, but they might need to do a little maintenance on their slot machines. It has been reported that a Daytona Beach, Florida resident, Bill Seebeck, who had traveled to the casino, was about $80 into his slot session when he heard the jackpot alarms go off on the game he was playing. What would have otherwise meant a payout of $2,500 or less, was actually quite a shock and seemingly traumatic event for the shaken up slots player.

What is now being referred to as a “machine malfunction” was at one point a $166 million jackpot payout owed to Seebeck when $1,666,666.65 flashed on the gaming screen in front of him after he whole-heartedly spun the reels. His heart raced and his enthusiasm grew as he believed he had won this massive amount that would have been the biggest jackpot to have ever been paid out anywhere, ever, the largest being no more than a $4 million linked progressive jackpot.

Once Seebeck came back down to planet Earth, it was explained to him by casino officials that the particular machine he was playing had obviously malfunctioned, as the max jackpot for that machine on a maximum bet could have only been a mere $2,500. Seebeck then allegedly mentioned bringing lawyers into the picture, which apparently panicked the casino operators, who immediately tried to right the situation. Seebeck was ultimately rewarded with an undisclosed amount of money in order to eradicate the potential unpleasant situation.

It has been confirmed that the glitch within the computer of the slot machine game is being investigated by the slot’s manufacturer and by the casino, as well. Both parties hope to prevent this sort of mishap from occurring again.

Other Related Articles

• Seneca Nations of Indians Announces Monticello Casino

Got Something to Say? Leave a Comment

You must be You are now logged in and can post a comment.