A Taco Bell customer allegedly shot an employee multiple times for giving him the incorrect amount of change for his order.
Doll McLendon, 67, is accused of opening fire inside the fast food restaurant after getting angry in the drive-thru, according to the Charlotte-Mecklenburg Police Department.
McLendon began shooting into the restaurant from the outside on Saturday night and then fled, police said.
The employee was rushed to a hospital with life-threatening wounds. He is a 54-year-old man, WSOC reported.
Cops used surveillance footage from the restaurant on Albemarle Road in Charlotte, North Carolina, and witness statements for information on McLendon’s vehicle.
Officers later found a vehicle appearing to be McLendon’s and arrested him outside his home.
In light of the shooting, police urged the public to not respond with violence when upset in similar situations.
‘If you can take the time to take a deep breath, take a step back, regardless of what it is, and have a genuine conversation with somebody, as opposed to being in your feelings or being upset with whatever you have going on,’ said Maj Torri Tellis on Monday.
Taco Bell stated they were ‘shocked to hear that this happened’.
‘We understand that the franchise owner and operator of this location is working with the local authorities in their investigation and will be offering support to all team members present,’ the company told Fox Business.
McLendon has been charged with attempted murder and discharging a weapon in occupied property.
‘Small things like not getting the right change or not getting the right food is not worth killing or shooting someone for sure,’ another customer, Jazmyn Jackson, told WSOC.
The shooting happened the same day that a McDonald’s customer, Elizar Ravelo, 64, turned himself in to cops for burning a manager at a Miami Springs restaurant with hot coffee after arguing over a penny.
Get in touch with our news team by emailing us at webnews@metro.co.uk.
For more stories like this, check our news page.
from News – Metro https://ift.tt/ceXyGIx
0 Comments