ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

Case / Legal Brief for Adams V. Williams ( 407 U.S. 143 ( 1972 ))

Updated on July 16, 2012

Intro

This case deals with Adam Versus Williams Case number 407 U.S. 143 . I will be posting a Case brief below on how to summarize this case.

case brief

Case: Adams V. Williams Citation:

407 U.S. 143 (1972)

Illustration: This case deals with whether officers had a reliable information to perform a search and seizure on the suspect.

Facts: Police Sgt. John Connolly was on car patrol early in the morning in a high crime area in Bridgeport, Connecticut. At approximately 2:15 A.M. a person know to Sgt. Connolly informed him that an individual in a nearby vehicle was carrying narcotics, and a gun at his waist. Sgt. Connolly called for backup, and proceeded to the vehicle where he tapped on the window, and asked Robert Williams to open the door, instead he had rolled down the window, where Sgt Connolly had reached in and removed the loaded gun from the waist of Mr. Williams. After a search was done once officers arrived, substantial amount of drugs, and another weapon was found inside the car.

Prior Proceedings: The history is as follows. Robert Williams was convicted in a Connecticut State court of illegal possession of a handgun, as well as possession of heroin. The conviction was affirmed by the Supreme Court of Connecticut. The U.S. Supreme Court denied Certiorari. Williams’ petition for federal habeas corpus relief was denied by the District Court and by a divided panel of the Second Circuit, but on rehearing en banc the Court of Appeals granted relief. The Supreme Court, reverses based on the police officers actions.

Opinion: The United States Supreme Court reversed the decision of the Court of Appeals granting relief to Mr Williams. Their decision solely relies on the fact that Sgt. Connolly’s search and seizure conformed to the standards the court has laid down in Terry V. Ohio, therefore it was reversed. That the officer received reliable information from a known informant, that allowed him to have probable cause to search Mr. Williams for a known weapon on his waist.

What could change the case: The case could have been changed if the officer did not have a statement from the informant with a direct location of the said weapon. If it was merely known that there was a weapon, and not a location, this could have changed the ruling in the case.

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)