ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

The FBI Could Have Stopped the Orlando Shooter, Why Didn't They?

Updated on June 21, 2016
FBI Director Paul Comey with Obama
FBI Director Paul Comey with Obama

The FBI can add people to the gun background check database on the recommendation of psychiatrists, mental health institutions and family members. Yet either it did not add the Orlando shooter Omar Mateen as a precaution, or it ignored the red flag raised as he attempted to purchase a weapon. Mateen had been of such concern to the FBI for his radical views that it interviewed him at least three times, and placed him on a watchlist for a period of time, according to the FBI.

A CNN report states:

“Individuals can also be added to the NICS index outside of potential gun sales, on the recommendation of psychiatrists, mental health institutions and family members.”

Mateen bought the high-capacity, high-velocity semi-automatic Sig Sauer rifle legally, according to the FBI, requiring him to enter and pass the background check in the FBI's databases, principally the National Instant Criminal Background Check System (NICS) Index.

The news makes it implausible if not impossible that the FBI did not know, or could not have known, that the shooter was attempting to buy a weapon.

From Trump to Hillary we now hear cries of outrage that terror suspects on watchlists should not be allowed to buy guns, as if that were the problem. But that is not the problem. The problem is that a former terror watch suspect sailed through the FBI's own background check databases.

No rights would be violated by this precaution, which would not deny the subject the right to buy a weapon, and alert agents that a person of concern was attempting to buy arms. This would enable the investigation to be reopened and agents to spring into action.

The Orlando shooter had radical jihadi literature on his hard-drive, which would have been found had he been investigated coming up the the FBI's databases as trying to buy a gun. The FBI would also have found out that the shooter had made repeat trips to Disneyland, long seen as a potential terrorist target. This would have built a prosecutable case for conspiracy to commit terrorism. Mentally disturbed dupes have been prosecuted for far less, in the FBI's many well-reported entrapment schemes. In contrast to these, Mateen acted on his own, so far as we know, and the main help he got was the FBI doing nothing.

Aurora, Fort Hood, San Bernardino, Killeen, Newtown, we know the list goes on of mass shootings in which high velocity rifles were used.

Congress and the media are looking the other way and playing dumb by asking the wrong questions. Why weren't agents alerted by the background check?

After the Boston Marathon bombing it turned out the FBI knew Tamerlan Tsarnaev all along, that he was interviewed, and on a watchlist. That time they said the name was spelled differently in the terror database than on Tsarnaev's passport when he re-entered the country from Chechnya. This time it's the FBI which would have entered the name itself.

The question is not whether persons on a watchlist should be allowed their Second Amendment rights. The question is what exactly is going on at the FBI?


This website uses cookies

As a user in the EEA, your approval is needed on a few things. To provide a better website experience, uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at:

Show Details
HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
LoginThis is necessary to sign in to the HubPages Service.
Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
AkismetThis is used to detect comment spam. (Privacy Policy)
HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the or domains, for performance and efficiency reasons. (Privacy Policy)
Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
MavenThis supports the Maven widget and search functionality. (Privacy Policy)
Google AdSenseThis is an ad network. (Privacy Policy)
Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
Index ExchangeThis is an ad network. (Privacy Policy)
SovrnThis is an ad network. (Privacy Policy)
Facebook AdsThis is an ad network. (Privacy Policy)
Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
AppNexusThis is an ad network. (Privacy Policy)
OpenxThis is an ad network. (Privacy Policy)
Rubicon ProjectThis is an ad network. (Privacy Policy)
TripleLiftThis is an ad network. (Privacy Policy)
Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)
ClickscoThis is a data management platform studying reader behavior (Privacy Policy)