ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

Why the Police Were Unable To Catch Jack the Ripper

Updated on June 19, 2010
Credit: an untrained eye
Credit: an untrained eye

The police were unable to catch the Ripper for many reasons. Perhaps the biggest and most significant was the fact that the police at the time were not prepared to deal with such a murderer and lacked the methods and forensic science to catch him. The lack of leads, the built up area of the crime scene, hoax letters to the press and the fact that the murders appeared to be random and unpredictable all made the police task harder to the point only a mistake by the murderer would have lead to him being caught.

In 1888 the metropolitan police were not trained or prepared on how to handle a major murder case such as the Ripper murders. Forensic science at the time was very basic, footprints being the most advanced part of the police science.  There was a lack of detectives and the few detectives that there were did not have the methods to carry out an investigation on a large scale. Considering all of this the police did carry out a massive investigation, questioning thousands of people and arresting many suspects. In the end, however, this proved fruitless.

The Ripper was clearly a very cunning killer and made it very hard for the police to catch him. He left no evidence on the scenes of the murder giving the police nothing to trace back to him. There was also no obvious motive other than the targeting of prostitutes, which suggested the murderer was not gaining in any way from the murders. All the murders were committed on strangers, unlike the majority of murders, so there was no link between the murderer and his victims, making it harder to catch him. Also, the murders appeared to be unplanned and random, giving the police no clues as to when he would strike next.

The area where the murders were carried out, Whitechapel, did not help the police efforts. The many small alleyways made escape from a murder scene relatively easy. The murders were always carried out at night, making it harder still to even witness the murders, indeed one victim on being discovered was not even realised to be dead because of the dark. On top of this many people in Whitechapel did not have a permanent residence and came and left the area frequently, there were also many foreigners in the area all of which would have made police investigations harder.

The fact that the victims were all prostitutes made the police investigation harder still. Prostitutes would have seen many strangers often making them easier victims for the Ripper. Attitudes of many people at  the time meant that they believed that the victims deserved to be murdered, these people would have been unlikely to help the police with their investigations. Many witnesses who may have been with the prostitutes were also unlikely to come forward to help, even if they had useful evidence as it would have meant admitting they had been with the prostitute, something many would have not been prepared to do.

Another major hindrance to the police was the large numbers of hoax letters which were sent to the press claiming to be the murderer. The police had to sort though these to find any that may have been genuine and the following up of leads would have been a large waste of police time, which could have otherwise have been spent tracing the murderer.

working

This website uses cookies

As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com 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: https://corp.maven.io/privacy-policy

Show Details
Necessary
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 googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
Features
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)
Marketing
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.
Statistics
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)