MGM Resorts questions revised timeline of Las Vegas massacre – ‘We believe what is currently being expressed may not be accurate’

Clark County Sheriff Joe Lombardo discusses the Route 91 Harvest festival mass shooting at the Las Vegas Metropolitan Police Department headquarters in Las Vegas, Monday, Oct. 9, 2017. Law enforcement authorities on Monday made a significant change to the timeline of the mass shooting, saying the gunman shot a hotel security guard before he opened fire on concertgoers. (Erik Verduzco/Las Vegas Review-Journal via AP)

By MICHAEL BALSAMO,  Associated Press 10/11 – A day after authorities revised the timeline of events on the night of the Las Vegas mass shooting, the hotel where the gunman was staying is casting doubt on the changes.

Police said earlier this week that they believe Stephen Paddock shot a hotel security guard through the door of his high-rise hotel suite six minutes before he unleashed a barrage of bullets into a crowd at a musical performance below. The injured guard ran down a hall using his radio and possibly a hallway phone to call for help, reporting he had been shot in the leg.That account differs dramatically from the one police gave last week: that Paddock ended his hail of fire on the crowd, where 58 people were killed and hundreds injured, in order to shoot through his door and wound the unarmed guard, Jesus Campos.But late Tuesday, the company that owns the Mandalay Bay hotel casino questioned the new timeline.

“We cannot be certain about the most recent timeline,” said Debra DeShong, a spokeswoman for MGM Resorts International. “We believe what is currently being expressed may not be accurate.”

Las Vegas police did not respond Tuesday night to questions about the hotel’s statement or whether investigators stand behind the revised timeline released earlier in the week.

The revised timeline raises questions about whether better communication could have allowed officers to respond more quickly and take out the gunman before the attack. It remains unclear if police ever received a call for help from the injured guard.

“This changes everything,” said Joseph Giacalone, a professor at John Jay College of Criminal Justice and a former New York City police sergeant. “There absolutely was an opportunity in that timeframe that some of this could’ve been mitigated.”

Nicole Rapp, whose mother was knocked to the ground at the Route 91 Harvest Festival and trampled by panicked concertgoers as bullets rained from above, said she’s “having a hard time wrapping my head around” why police changed the timeline of the shooting.

“It’s very confusing to me that they are just discovering this a week later,” she said. “How did we not know this before? It’s traumatic for the victims and their families not to be sure of what happened.”

Undersheriff Kevin McMahill said on Tuesday that the guard had been responding to a door alarm on the hotel’s 32nd floor when he heard an odd drilling sound.

Paddock had power tools and was trying to drill a hole in a wall, perhaps to mount another of the security cameras he set up around him, or to point a rifle through, but he never completed the work, Clark County Sheriff Joe Lombardo said. He also drilled holes and bolted a metal bar to try to prevent the opening of an emergency exit door near his room.

As the guard notified maintenance and security of the stairwell issue, several single shots were fired into the hallway before he shot again, unloading more than 200 rounds at the guard and a maintenance man, McMahill said. Campos, the security guard, was struck in the leg and injured, police said.

Campos reported to hotel security dispatchers that he was shot before Paddock opened fire on the crowd, Assistant Sheriff Tom Roberts told The Los Angeles Times on Tuesday.

It wasn’t clear exactly what time Campos called for help or if the hotel had relayed the information about the shooting to police. Las Vegas police did not respond to questions from The Associated Press about whether hotel security or anyone else in the hotel called 911 to report the hallway shooting.

“Our officers got there as fast as they possibly could and they did what they were trained to do,” another Las Vegas assistant sheriff, Todd Fasulo, said Tuesday.

The six minutes that transpired between the hallway shooting and the start of the gunman’s fusillade wouldn’t have been enough time for officers to stop the attack, said Ron Hosko, a former FBI assistant director who has worked on SWAT teams. Rather than rush in without a game plan, police would have been formulating the best response to the barricaded gunman, he said.

“Maybe that’s enough time to get the first patrolman onto the floor but the first patrolman is not going to go knock on that customer’s door and say ‘What’s going on with 200 holes in the door?'” Hosko said.

McMahill defended the hotel and said the encounter that night between Paddock and the security guard and maintenance man disrupted the gunman’s plans. Paddock fired more than 1,000 bullets and had more than 1,000 rounds left in his room, the undersheriff said.

“I can tell you I’m confident that he was not able to fully execute his heinous plan and it certainly had everything to do with being disrupted,” McMahill said. He added: “I don’t think the hotel dropped the ball.”

___

Associated Press writers Ken Ritter and Sally Ho in Las Vegas, Anita Snow in Phoenix and Sadie Gurman in Washington contributed to this report.

https://www.apnews.com/3baab82c8c264d858d899dca69906edd/Hotel-questions-revised-timeline-of-Las-Vegas-massacre

___

For complete coverage of the Las Vegas shooting, click here: https://apnews.com/tag/LasVegasmassshooting

Copyright 2017 The Associated Press. All rights reserved. This material may not be published, broadcast, rewritten or redistributed

 

Posted in: Investigations, Mass Casualty Attacks, Police, SWAT, Tactics

Leave a Reply

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

three × 3 =

Terms of Use for Posting Comments

Terms of Use

This site (the “Site”) is operated and maintained by Law Enforcement Education Foundation, Corporation (“Company”). Throughout the Site, the terms “we”, “us” and “our” refer to Company.  The words “user,” “you” and “your” as used herein refer to you.

Please read these terms and conditions of use (“Terms of Use”) carefully before contributing content. If you do not agree to these Terms of Use, please do not contribute content. Your use of the Site is subject to the Terms and Conditions found here .

By contributing content to the Site, you represent and warrant that you are at least eighteen (18) years old and that you have read and understand these Terms of Use and any amendments thereto and agree to be bound by them. If you are not at least eighteen (18) years old or you do not agree and accept these Terms of Use, you are prohibited from contributing content.

From time to time, we may permit users to submit content to the Site.  You hereby acknowledge and agree that by submitting remarks, comments, suggestions, ideas, graphics, feedback, edits, concepts, comments, photographs, illustrations and other materials (other than personal information and/or registration information) through the Site (individually and collectively, “Submissions”), you (i) grant us a nonexclusive, royalty-free, perpetual, transferable, irrevocable and fully sub-licensable right to use, reproduce, modify, adapt, translate, distribute, publish, create derivative works from and publicly display and perform such Submissions throughout the world in any media, now known or hereafter created, without attribution to you; (ii) grant us the right to pursue at law any person or entity that violates your and/or our rights in your Submissions; and (iii) forever waive any and all of your rights, including but not limited to moral rights, if any, in and to your Submissions, including, without limitation, any all rights or requirements of attribution or identification of you as the author of the Submission or any derivative thereof.  We reserve the right to remove any of your Submissions from the Site, in whole or in part, without notice to you, for any reason or no reason.

Submissions are made voluntarily. Any submissions which include personally identifiable information are subject to our Privacy Policy found here .  You may not upload or otherwise publish content on the Site that (i) is confidential to you or any third party; (ii) is untrue, inaccurate, false or other than an original work of your authorship; (iii) that relates to or impersonates any other person; (iv) violates the copyright, trademark, patent or other intellectual property rights of any person or entity; (v) contains any content, personally identifiable information or other information, or materials of any kind that relate or refer to any other person or entity other than the provider of the products, goods or services to which the Submission relates; or (vi) violates any law, or in any manner infringes or interferes with the rights of others, including but not limited to the use of names, information, or materials that (A) libel, defame, or invade the privacy of any third party, (B) are obscene or pornographic, (C) are harmful, threatening, offensive, abusive, harassing, vulgar, false or inaccurate, racially, sexually, ethnically or are otherwise objectionable or otherwise contrary to the laws of any place where such Submissions may be accessed; (D) constitute personal attacks on other individuals; (E) promote criminal, immoral or illegal activity; (F) promote or advertise any person, product or service or solicit funds; or (G) are deemed confidential by any contract or policy.

You are solely responsible for any Submissions you make and their accuracy. We take no responsibility and assume no liability for any Submissions posted by you or any third party.

Unless approved by us in writing in advance, you agree not to: (i) provide or create a link to the Site; or (ii) create any frames at any other sites pertaining to any of the content located on the Site.

We reserve the right, in our discretion, to update, change or replace any part of these Terms of Use for Posting Comments by posting updates and/or changes to our Site.  It is your responsibility to check this page periodically for changes.  Your continued use of, and/or access to the Site, following the posting of any changes to these Terms of Use for Posting Comments, constitutes your acceptance of those changes.