Robert Phillips
Deputy District Attorney (Retired)
“To the barefoot man, happiness is a pair of shoes. To the man with old shoes, it’s a pair of new shoes. To the man with new shoes, it’s a pair of more stylish shoes. And of course, the fellow with no feet would be happy to be barefoot.”
- Good Faith Exception to the Fourth Amendment
- Geofence Search Warrants and California's Electronic Communications Privacy Act
- Geofence Search Warrants and Probable Cause, Particularity, and Breath
- Geofence Search Warrants and an Investigator’s Unfettered Discretion
- Probable Cause and a Suspect’s Use of a Cellphone
To be in compliance with the Fourth Amendment, a search warrant must reflect sufficient probable cause, particularly describing the thing or place to be searched and the property to be seized. The breath of a search warrant application must be limited in scope to those items for which there is probable cause to be seized. Geofence warrants are lawful so long as in compliance with these rules, and while limiting an investigator’s unfettered discretion in deciding whose electronic device to search.
Adbadalla Thabet was tasked with the twice-a-week collection of cash receipts from several of his uncle’s gas stations and depositing those proceeds in a bank in Paramount; a suburb of Los Angeles. Surveillance footage collected at various sites (later viewed by investigators of the Los Angeles Sheriff’s Department) showed that Thabet left his apartment building in Downey at around 7 a.m. on the morning of March 1, 2019, and drove to one of his uncle’s gas stations in Downey to pick up cash proceeds for deposit.
After remaining there for about 15 minutes, he left that gas station at 7:30 a.m. and drove to a second gas station in Bellflower where, at about 9:00 a.m., he met with his brother-in-law. Thabet left this gas station at 9:40 and made a brief stop at a strip mall where he and his brother-in-law inspected some possible income property before Thabet drove to a gas station in Lynwood to pick up the cash receipts from that station.
Thabet drove to the bank in Paramount where surveillance video showed him driving into the parking lot at about 10:30 a.m. That same video showed that he was followed into the parking lot by two other vehicles; a gray and a red sedan. The occupants of the gray and red sedans were observed contacting each other; the driver of the red car having gotten out of his vehicle. The gray car then drove slowly towards Thabet’s parked car while the driver of the red car followed on foot. As Thabet got out of his vehicle, the gray car pulled up next to him. An occupant of that car shot Thabet in the torso, leaving him on the ground as the driver sped away.
The driver of the red car (still on foot) then walked up to Thabet’s body, picked up his backpack containing the gas station receipts, walked back to the red car, and drove away. Thabet died of his injuries. Video surveillance later obtained from the gas stations Thabet had visited that morning showed the same two vehicles at two of those locations leading investigators to the conclusion that they had been following Thabet. The license plate numbers of those two cars, however, were not legible in any of the footage.
In the subsequent investigation, Sheriff’s investigators resorted to what is commonly called a “geofence warrant.” As the preliminary step in obtaining such a warrant, Los Angeles County Sheriff’s Detective Jonathan Bailey (assisted by Romy Haas; a crime analyst for the Sheriff's Department) applied for a search warrant directing Google to identify individuals whose location history data indicated that they were in the vicinity of the same six locations visited by Thabet on the morning of March 1st, including Thabet’s apartment.
In the affidavit supporting the warrant application, Detective Bailey described Thabet's murder as seen on the surveillance footage of the bank parking lot. He further stated that he had viewed surveillance camera footage from several of the other locations Thabet had visited that morning and had seen the gray and red sedans in some of that footage. In the affidavit, Detective Bailey provided a brief overview of the procedures used by Google to track and store location history data, explaining how Google collects data through “Global Position System (GPS) data, cell site/cell tower information, Bluetooth connections, and Wi-Fi access points.” Of significance here, Detective Bailey also included the following in his affidavit: “I know most people in today’s society possess cellular phones and other items (e.g. tablets, watches, laptops) used to communicate electronically. . . . Most people carry cellular phones on their person and will carry them whenever they leave their place of residence.”
In addition, Detective Bailey explained that “(s)uspects involved in criminal activity will typically use cellular phones to communicate when multiple suspects are involved.” Therefore, he concluded, identification of individuals in Thabet's vicinity on the day of the murder would assist investigators in locating the drivers of the vehicles involved in the murder, and who investigators believed had been following Thabet throughout the morning.
The warrant application sought location history data from Google for individuals within six target locations; Thabet’s apartment, the three gas stations he’d visited, the strip mall Thabet and his brother-in-law had stopped at, and the bank in Paramount. The description of each location included either circular or rectangular geographical parameters around the individual locations along with specified time parameters in the middle of which it was known that Thabet (and thus, presumably, the red and gray sedans) had been.
The obtaining of such a warrant (commonly referred to as a “geofence” warrant; AKA; “reverse location” warrant) involves a three-step process. At step one, Google was directed to search location history data for the six designated locations and times, within the parameters as described, and produce an anonymized list of cellphone or similar devices (e.g., iPads, etc.) found within the search areas in the designated timeframes, including the individual times each device was recorded in the search area during the applicable time period. At step two, law enforcement is to review the anonymized list of devices “to remove devices that are not relevant to the investigation, for example, devices that were not in the location for a sufficient period of time.” Law enforcement has the option at this point of requesting that Google provide additional location history information for each identified device even if that information fell outside of the initial geographic and temporal search parameters. At step three, law enforcement would then request identifying information from Google for all devices law enforcement deemed, at the investigator’s discretion, relevant to the investigation based primarily on the number of times a device was noted to be within the targeted locations and time periods. The warrant directed Google to provide this identifying information, as selected by the investigator, without additional legal process.
A Los Angeles superior court judge, acting as a magistrate, signed the geofence search warrant on March 21st. Detective Bailey (with the assistance of the Sheriff’s Crime Analyst Haas) reviewed the anonymized data provided by Google and whittled it down to eight devices that had been at more than just one of the relevant locations, and within the timeframes as provided, on the morning of March 1st.
At Crime Analyst Haas’ request, Google provided the corresponding e-mail addresses for all eight of the identified devices. Detective Bailey and Crime Analyst Haas then drafted additional search warrants related to two of those e-mail addresses, which had been identified as being at the relevant times and locations (including the murder scene) four and three times, respectively.
This information eventually led to the identification of defendants Meza and Meneses as the two people observed in the video at the murder scene. Charged in state court with a special circumstance murder, along with other attached sentencing enhancements, both defendants filed a pre-trial motion pursuant to Pen. Code § 1538.5 to quash and suppress the results of the geofence warrant, challenging the legality of the warrant as used in this case. They also alleged that the geofence warrant did not comply with California’s Electronic Communications Privacy Act (Pen. Code §§ 1546 et. seq.), arguing that it did not adequately identify the target individuals or accounts and applications to be searched.
The trial court denied the defendants’ motions. Meza thereafter pled guilty to first degree murder and Meneses pled no contest to second degree murder, receiving 25- and 15-years to life, respectively. Defendants appealed the denial of their motions.
The Second District Court of Appeal (Div. 7) found the geofence warrant to have been in violation of the Fourth Amendment, but declined to suppress the resulting information obtained anyway under the theory that the detective (and crime analyst) acted in good faith. The basic rules are simple: Searches conducted via the use of a judicially authorized search warrant are presumed to be lawful.
However, such a search warrant and affidavit are required to particularly describe the thing or the place to be searched and the items to be seized. “The manifest purpose of this particularity requirement [is] to prevent general searches. By limiting the authorization to search to the specific areas and things for which there is probable cause to search, the requirement ensures that the search will be carefully tailored to its justifications, and will not take on the character of the wide-ranging exploratory searches the Framers intended to prohibit.” (People v. Amador (2000) 24 Cal.4th 387, 392; Maryland v. Garrison (1987) 480 U.S. 79, 84.)
With these general rules in mind, a court is to examine three main factors: Probable cause, particularity, and over-breath.
(1) Probable Cause: “Probable cause will be found to support the issuance of a warrant if ‘the magistrate had a substantial basis for concluding a fair probability existed that a search would uncover wrongdoing.’” (People v. Westerfield (2019) 6 Cal.5th 632, 659–660.) Defendant argued that Detective Bailey’s warrant was not supported by sufficient probable cause to believe that defendants had cellphones or other electronic implements in their possession when committing this crime. The Court disagreed. Noting that a finding of probable cause requires only that there be a “fair probability” that contraband or evidence of a crime will be found in a particular place (Illinois v. Gates (1983) 462 U.S. 213, 238.), the Court here held that this standard was clearly met. Specifically, as Detective Bailey described in his warrant affidavit, nearly everyone nowadays carries with him a cellphone. It has been held, for instance, that probable cause for a robbery suspect’s cellphone records was shown “[e]ven if nobody knew for sure whether the robber actually possessed a cell phone. . . . (J)udges (are) not required to check their common sense at the door and ignore the fact that most people ‘compulsively carry cell phones with them all the time’” (United States v. James (8th Cir. 2021) 3 F.4th 1102, 1105.) It was reasonable, therefore, for the magistrate in this case to conclude that the perpetrators were carrying cellphones the morning of the murder and (traveling in two separate cars) used them in coordinating their movements.
(2) Particularity: “Particularity is the requirement that the warrant must clearly state what is sought.” (In re Grand Jury Subpoenas Dated Dec. 10, 1987 (9th Cir. 1991) 926 F.2nd 847, 856.) The defendant argued that Detective Bailey’s search warrant lacked sufficient “particularity” to be constitutional. On this issue the Court agreed. As noted by the Court, the “purpose of the ‘particularity’ requirement of the Fourth Amendment is to avoid general and exploratory searches by requiring a particular description of the items to be seized.” (People v. Bradford (1997) 15 Cal.4th 1229, 1296.) However, a warrant affidavit need only be “reasonably specific;” a factor that varies “depending upon the circumstance of the case and the type of items involved.” (People v. Robinson (2010) 47 Cal.4th 1104, 1132.) This requirement is expected only to place a “meaningful restriction upon the objects to be seized.” (People v. Frank (1985) 38 Cal.3rd 711, 724.) “The description in a search warrant must be sufficiently definite that the officer conducting the search ‘can, with reasonable effort ascertain and identify the place intended.’ Nothing should be left to the (“unbridled” or “unfettered”) discretion of the officer.” (People v. Dumas (1973) 9 Cal.3d 871, 880.) In this case, the Court found that the warrant sufficiently described the places to be searched (i.e., Google’s database of users’ location history) and the items to be retrieved from that search (i.e., designated records for users found within the boundaries of certain coordinates at certain times). The particularity requirement was not satisfied in this case, however, because law enforcement was allowed at “step three” of the process (as described above), “with unbridled (or unfettered) discretion,” and without approval of a court magistrate, to request additional information on any of the potentially thousands of users identified without any objective criteria limiting their discretion. Inferring that either the original warrant should have limited the detective’s discretion in making these choices, or a new search warrant should have been obtained seeking the consensus of a magistrate as to specific suspects, the Court found the procedures used here by the detective to be in violation of the Fourth Amendment.
(3) Breadth: “Breadth deals with the requirement that the scope of the warrant be limited by the probable cause on which the warrant is based.” (In re Grand Jury Subpoenas Dated Dec. 10, 1987, supra, 926 F.2nd at pp. 856–857.) “In determining whether a warrant is overbroad courts consider ‘whether probable cause existed to seize all items of a category described in the warrant’ and ‘whether the government could have described the items more particularly in light of the information available to it at the time the warrant issued.’” (United States v. Shi (9th Cir. 2008) 525 F.3rd 709, 731–732.) The Court concluded in this case that Detective Bailey’s geofence warrant ran afoul of both of these requirements. The warrant, for instance, authorized the identification of any individual within six large search areas without any particularized probable cause as to each person or their location. To be constitutional, both the geographical area and the time parameters needed to be seriously limited, minimizing the number of innocent individuals who may be drawn into the warrant’s reach. As an example, the Court cited the first search location; i.e., the area around Adbadalla Thabet’s apartment complex. The warrant as written, with merely a circle drawn around the apartment complex and all the adjoining streets, allowed law enforcement to obtain information on every individual in a seven-and-a-half-acre area over a 75 minute period during the early morning of March 1st. Geographically, rather than drawing a general, all-encompassing circle around the target area, Detective Bailey and Crime Analyst Haas could have used box- or rectangular-shaped parameters covering no more than the street in front of Thabet’s apartment. The same holds true with the other five locations. As for the time parameters, they could have been more limited to the minutes reflected by the timestamp in the surveillance videos, adding only that much time before and after to reflect the possibility that the time stamps in surveillance videos may not be entirely accurate. The Court cited as an example the time period used at one of the gas stations where information was requested for a two hour and ten minute time span. As summarized by the Court: “(I)t is the constitutionally imposed duty of the government to carefully tailor its search parameters to minimize infringement on the privacy rights of third parties.” The warrant here, being too broad, failed to do this.
(4) Good Faith: “(T)he [United States] Supreme Court held that when ‘an officer acting with objective good faith has obtained a search warrant from a judge or magistrate and acted within its scope,’ the ‘marginal or nonexistent benefits’ produced by suppressing the evidence obtained ‘cannot justify the substantial costs of exclusion.’” (United States v. Leon (1984) 468 U.S. 897, 920-922.) In this case, at the time Detective Bailey and Crime Analyst Haas sought the warrant at issue here, there was very little case law (i.e., “a novel investigative tool”) providing them with guidance on the obtaining of a geofence search warrant. As testified, neither Detective Bailey nor Crime Analyst Haas had had much experience writing such a warrant nor conducting the resulting searches. Per the Court, therefore: “Given the dearth of authority directly on point and the novelty of the particular surveillance technique at issue, the officers were not objectively unreasonable in believing the warrant was valid, even if the issue, upon close legal examination, is not a particularly close one.” For this reason, the Court declined to suppress the results of the geofence search warrant or reverse the defendants’ convictions.
(5) California’s Electronic Communications Privacy Act: Defendants complained that the geofence search warrant violated California’s Electronic Communications Privacy Act (or “CalECPA,” at Pen. Code §§ 1546 et seq.) The Court rejected defendants’ arguments. Specifically, the Court held that (1) it is not necessary under CalECPA to specifically target specific individuals or accounts. Rather, CalECPA requires only that a warrant must describe with particularity the information to be seized as is “appropriate and reasonable” to the case at issue. (P.C. § 1546.1(d)(1)) The warrant in this case described the target individuals and accounts with the greatest degree of particularity available to investigators; i.e., individuals whose devices were located within the search boundaries at certain times. There is no requirement in the statute that a suspect’s name or other identifying information be included in the warrant to ensure its validity. (2) The Court further held that the warrant was not defective merely because it failed to specify the “applications and services covered” by the warrant. (See Pen. Code § 1524.3(b)) In a geofence warrant, the government is not seeking data or content related to a particular application or service. Rather, what is sought is the service provider’s (i.e., Google’s) record of all electronic contacts with that device, regardless of which applications or services originated the contact. Accordingly, the failure to name a particular application or service in this instance did not result in a violation of CalECPA. (3) Lastly, the Court rejected the defendants’ argument to the effect that any constitutional infirmities in the warrant create an independent violation of CalECPA. In so ruling, the Court noted simply that, “(t)here is nothing in the cited language that, without more, converts a Fourth Amendment violation into a statutory violation.”
The Court quickly brushes over (in footnote 10) the idea that no warrant (geofence or otherwise) is necessary absent a reasonable expectation of privacy being involved, with the general rule being that information a defendant exposes to pubic view (which would be his geographical location at specific times in this case) waives any privacy violation arguments. (See People v. Robles (2000) 23 Cal.4th 789, 794; and Katz v. United States (1967) 389 U.S. 347, 351.) The prosecutor in this case failed to make this argument, and thus forfeited it.
However, I might suggest that in the future, prosecutors make an “expectation of privacy” argument as an alternative—and in addition to—one highlighting the legality of the warrant affidavit in issue. Note, however, that the Court further cites (again in footnote 10) the U.S. Supreme Court’s case of Carpenter v. United States (2018) 138 S.Ct. 2206, at page 2219, where (as noted by this Court of Appeal) the “United States Supreme Court has suggested that an individual has a right to privacy regarding his or her current and historical location.”
That would be an interesting issue to resolve: Which constitutional concept takes precedence; a person’s lack of privacy rights to anything he or she exposes to public view (including his location within a specific timeframe), or the necessity of a geofence search warrant? But back to the main issues in this case: Geofence warrants are indeed an important tool to use in cases such as this one. Knowing now that we must tighten up the geographical and time parameters, as well as do as much as possible to minimize an investigator’s “unbridled (or “unfettered”) discretion” as to who among the possible suspects he or she is going to concentrate, you now have no excuse for not following the rules.
Good faith will not save the next geofence investigation you might be involved in. I have to assume that geofence warrant classes are also being offered to investigators via P.O.S.T. and other training venues. Also, if you’re interested, I have a list of all the published geofence cases in the country (at least that I could find) that I will gladly send you upon request.
- Use of Deadly Force; Duty to Warn
- Qualified Immunity in a Use-of-Deadly-Force Case
Qualified immunity from civil liability in a case where deadly force is used is not available in a case where discrepancies in the evidence are better left to a jury to decide. A police officer contemplating the use of deadly force has a duty to warn a suspect when at all practicable to do so under the circumstances.
**UPDATE 05/10/2023: On May 4, 2023, this opinion was withdrawn and a rehearing granted upon resignation from the bench by one of the affirming justices and his replacement with another. A change in justices hearing the case apparently is going to reverse this decision and, as a result, grant Officer Agdeppa qualified immunity. However, this occurrence does not change the basic rule that when at all feasible, an officer should warn a suspect when deadly force is about to be used.**
On October 29, 2018, Los Angeles Police Officers Edward Agdeppa (5’1” and 145 pounds) and Perla Rodriquez (5’5”, 145 pounds) responded to a call at a 24-Hour Fitness gym on Sunset Boulevard in Hollywood where it was reported that a person was trespassing and engaging in disruptive conduct. Upon arrival, staff members complained that a “gentleman” was “a little bit irate,” wasn’t listening, and had already hurt a few gym members. He had also apparently assaulted security personnel. Note: The bulk of this summary is taken from the dissenting opinion; the majority having glossed over much of it.
With their body-worn cameras turned on, the officers contacted a naked Albert Dorsey in the shower area of the men’s locker room, enjoying the music being played on his cellphone. Dorsey was 6’1” tall and weighed 280 pounds (almost as much as both officers combined). Over the next two minutes, Dorsey ignored the officers’ repeated demands that he turn off the music, get dressed, and leave the gym.
He instead walked across the room, admired his naked body in a mirror, danced a bit to the music, and slowly dried himself as he defiantly flipped off Officer Agdeppa. After more than four minutes, Officer Agdeppa decided that enough was enough and approached Dorsey to handcuff him from behind. Dorsey, however, pulled away, and the fight was on. The two officers working together were able to get one handcuff on, but that was it. As Dorsey forcefully resisted, attempts to use arm, finger, and wrist locks were unavailing.
During this struggle, Officer Agdeppa was able to broadcast a request for additional units. Dorsey became more combative, knocking both of the officers’ body-cams off their uniforms, thus ending any visual depictions of the fight. The audio remained on, however, recording over the next “three-or-so minutes” the sounds of frequent bangs, crashes, shouts of pain, and other indicia of a violent confrontation. The officers could be heard yelling at Dorsey to stop resisting.
Officer Agdeppa eventually used his Taser in contact mode, cycling it twice into Dorsey’s chest. Officer Rodriquez fired her Taser into Dorsey’s back, activating it for approximately five seconds. She then activated it a second time. Neither Taser had any effect other than to make Dorsey even more combative. Dorsey began “punching at (the officers’) heads and faces while the handcuff attached to his wrist also swung around and struck” them. Punching Officer Agdeppa in the head and face area, the officer was knocked into a wall and to the ground with such force that he suffered (as it was later determined) a concussion, disorienting him and causing him to drop his Taser. After Officer Rodriguez fired her Taser (still attached to Dorsey’s back) for the third time, Dorsey turned on her, knocking her to the ground. Dorsey then straddled Rodriguez, striking her repeatedly in her face and head as he took her Taser away from her.
Regaining some control of himself, Officer Agdeppa looked up to see Dorsey straddling Officer Rodriquez, “pummeling (her) . . . with a flurry of punches,” as she lay on the floor in the fetal position trying to protect her face and head. Officer Agdeppa later noted in his civil deposition he believed that if allowed to continue, Dorsey’s next blow to Officer Rodriguez’s head could kill her. So Officer Agdeppa drew his firearm and shot Dorsey five times.
In his deposition, Officer Agdeppa stated that he “unholstered and drew [his] service weapon” and “gave Dorsey a verbal warning, stating words to the effect that Dorsey needed to stop.” No such warning could be heard on the still-functioning bodycams. All that could be heard over the “chaotic noise” was a man’s voice shouting something unintelligible just before the shots were fired. It was assumed by the Court, therefore, that no final warning was given. Dorsey succumbed to his wounds.
The Los Angeles Board of Police Commissioners did an internal investigation of the shooting, finding there to be some discrepancies between the officers’ accounts of the confrontation and both the physical evidence and the witness’ accounts (i.e., the two security guards who apparently just stood by and watched). The Commissioners also criticized the officers for failing to merely “disengage” when Dorsey first began to resist and wait until additional assistance arrived. As noted above, Officer Agdeppa suffered a concussion. He also had to have the bridge of his nose stitched up. He was unable to return to work for six months and “had further (undescribed) longer-lasting effects.” Officer Rodriguez suffered a swollen left check and right jaw, abrasions on her ear and hands, and a pulled muscle behind her knee.
Albert Dorsey’s mother, Paulette Smith, sued Officer Agdeppa in federal court alleging the unreasonable use of deadly force. Officer Agdeppa filed a motion for summary judgment, claiming qualified immunity. The district (trial) court denied the motion—noting the discrepancies in the different accounts as to what occurred—and ruled that a jury needed to decide liability, if any. Officer Agdeppa appealed.
The Ninth Circuit Court of Appeal affirmed in a split, 2-to-1 decision; the majority agreeing with the district court that Officer Agdeppa was not entitled to qualified immunity. The Court gave two reasons for its decision. First, the Court agreed with the district court in its conclusion that a reasonable jury could reject the officers’ account of the shooting, due to the significant discrepancies between their versions of events and the other evidence in the record. Second, it has long been held that the Fourth Amendment requires officers to warn a suspect before using deadly force, at least when practicable to do so. Officer Agdeppa failed to issue such a warning before shooting Dorsey.
Assuming Officer Agdeppa had in fact actually told Dorsey to “stop,” which itself was contested, such an admonition was insufficient to constitute a warning. Also, per the Court: “(A) jury could find that a reasonable officer in Agdeppa’s position would not have believed that Rodriguez or anyone else was in imminent danger and, thus, would have understood that his use of deadly force violated plaintiff's Fourth Amendment rights.” In reaching these conclusions, the Court noted that it must, on appeal—while considering the issues “de novo”—“assess whether an officer’s use of force was objectively reasonable by weighing ‘the severity of the crime at issue, whether the suspect poses an immediate threat to the safety of the officers or others, and whether he is actively resisting arrest or attempting to evade arrest by flight.’” (Graham v. Connor (1989) 490 U.S. 386, 396.)
These three “Graham factors” are not to be “considered in a vacuum,” but must be weighed “in relation to the amount of force used to effect [the] particular seizure.” (Smith v. City of Hemet (9th Cir. 2005) 394 F.3rd 689, 701; quoting Chew v. Gates (9th Cir. 1994) 27 F.3d 1432, 1441.) A reviewing court must also “take the perspective of the officer on the scene without the benefit of 20/20 hindsight.” “Because deadly force involves a serious intrusion on Fourth Amendment rights, deadly force is reasonable only if the officer has probable cause to believe the suspect poses an immediate and significant threat of death or serious physical injury to the officer or others.” (Italics in original; Gonzalez v. City of Anaheim (9th Cir. 2014) 747 F.3rd 789, 793; quoting Scott v. Henrich (9th Cir. 1994) 39 F.3rd 912, 914.)
Lastly, “summary judgment should be granted ‘sparingly’ in deadly force cases . . . tak(ing) special care to ‘ensure that the officer is not taking advantage of the fact that the witness most likely to contradict his story—the person shot dead—is unable to testify.’” With these rules in mind (but without even discussing the “Graham factors” described above), the Court found too many discrepancies between the officers’ accounts of what happened and the other available evidence to allow the granting of summary judgment. Rather, the case should be allowed to go to a jury to resolve the conflicting evidence. While it was “uncontested that Dorsey posed some danger to the officers’ safety by actively resisting arrest” (italics added), the Court remained critical of Officer Agdeppa for having failed to warn Dorsey that he would be shot if he did not submit. Telling him merely to “stop” (assuming that did in fact happen) was not enough. “Because the officers had tased Dorsey at least five times, a command to ‘stop’ would have done nothing to warn Dorsey that Agdeppa was preparing to ramp up to use deadly force.” Per the Court: “(A) reasonable jury could decide that it was practicable for Agdeppa to give Dorsey a deadly force warning.” For these reasons, the Court agreed with the district court that summary judgment—taking the issues out of the hands of a jury—was inappropriate in this case.
When I graduated from the San Diego Police Department Academy in 1971, I was approximately 5’10½” tall, and weighed somewhere around 170 pounds. Upon giving me my final evaluation, the academy sergeant (Sgt. Mansfield) told me point blank I had to realize that should I be standing in a line with my fellow officers one day when someone calls out for “Officer Milk Toast,” everyone is going to be looking at me. (True story.) Indeed, I remember that in order to make the minimum weight requirement to get hired as a patrol officer in the first place, I had to stuff my face with bananas the day of my initial physical. In those days, female officers—who generally tend to be smaller than their male counterparts—were automatically relegated to investigative or administrative positions. Today, however, police departments as a rule merely require that your height be proportional to your weight; an administrative decision the wisdom of which can be debated another time. As a result, women are now commonly in the field as patrol officers along with their male counterparts. The natural result of all these administrative changes is that we now have officers of all sizes assigned to the uniform patrol division, and who at some point in their respective careers can expect to come up against the uncooperative Albert Dorseys of the world. This is fact of life we just have to live with.
In this case, I have to question the majority’s legal conclusions. First, the Court failed to take into consideration the Graham factors, as described above. Also, as pointed out by the dissenting justice, one might argue that the majority places way too much importance on the necessity of a warning that deadly force is about to be used. Had the majority justices considered the Graham factors and rethought the need for a warning, they might have reached a different conclusion.
Perhaps the only part of this case decision with which I agree is the Police Commission’s conclusion that Officer Agdeppa should have given more thought to “disengaging” with Dorsey and calling for cover once it became apparent that Dorsey was not going to cooperate. But it’s hard to criticize when you’re not there experiencing the turmoil created by Dorsey’s actions first hand. As for the legal necessity to issue a final warning before shooting and killing a suspect, the dissenting opinion justly criticizes the idea that it is clearly established in the law that “in the heat of battle,” an officer “must follow a judge-devised warning script when officer safety is most jeopardized.”
The dissenting opinion makes a credible argument to the effect that under the circumstances that were apparent to Officer Agdeppa—with his partner on the floor, curled up in the fetal position, desperately trying to protect her head from the pounding a 280-pound man was raining down on her—there is no legal duty to delay even the few extra seconds (which could have spelled the difference between life and death for Officer Rodriguez) and issue a “stop or I’ll shoot” warning. Speaking of the dissent, Justice Daniel A. Bress authored a detailed 15-page description of the events (with the majority opinion being a relatively short ten pages long), reaching the contrary conclusion. In his dissent, Justice Bress makes a valid argument that the scenario as occurred here—with two officers in reasonable fear for their very lives—“presents a classic case for qualified immunity.” In so arguing, and as spelled out in much more detail than in the majority opinion, Justice Bress poo-poos the supposed discrepancies in the evidence—noting that they are either non-existent or easily refuted—as well as the idea “that police officers enduring a frenzied onslaught (are) legally required to call a ‘time out’ and issue another warning before they (use) deadly force.” By “another warning,” Justice Bress makes reference to some fourteen times Dorsey earlier ignored commands to submit. Speaking as the former “Officer Milk Toast” (having since “filled out” more than bit over the years), I found Justice Bress’ dissent to be the better reasoned argument.
**UPDATE: On May 4,, 2023: This opinion was withdrawn and a rehearing granted upon resignation from the bench by one of the affirming justices and his replacement with another. A change in justices hearing the case apparently is going to reverse this decision and, as a result, grant Officer Agdeppa qualified immunity. However, this occurrence does not change the basic rule that when at all feasible, an officer should warn a suspect when deadly force is about to be used. **
Expressive Honking and Veh. Code § 27001: Have you ever driven by a group of people on a street corner who are enthusiastically waving banners and flags, with one or two of them holding up signs encouraging you to, “Honk, if you __.” (Fill in the blank with whatever it is the group is promoting.) Assuming you do in fact support whatever it is the demonstrators are advocating, what do you do? You obligingly honk, do you not? Think about it. You have a First Amendment right to express your opinion, just as does those who are encouraging you to honk. And if simply honking your car horn conveys a social, political, or other opinion, what’s so wrong in doing so? Well, California Vehicle Code § 27001 says it is wrong to do so. Section 27001 makes it an infraction to violate its provisions. Specifically; “(a) The driver of a motor vehicle when reasonably necessary to insure safe operation shall give audible warning with his horn. (b) The horn shall not otherwise be used, except as a theft alarm system . . . .” (Italics added) So which takes precedence, your First Amendment right to freedom of expression on some presumably important issue of the day, or a simple state statute that says you’re violating the law when you do so? You would think the former, given the rule that constitutional principles generally take precedence over a state statute. But the Ninth Circuit Court of Appeal says otherwise, at least when it involves balancing the importance of Section 27001 with your constitutional right to express you opinions. In the recent reported decision of Porter v. Martinez (9th Cir. Apr. 7, 2023) 64 F.4th 1112, appellant Susan Porter filed suit arguing that her First Amendment rights had been violated when she was cited for honking her car horn under circumstances similar to those described above. Her ticket was later dismissed; the officer failing to appear when she challenged it in court. Thus having been deprived of her opportunity to say her piece, she sued in federal court. The basis for her lawsuit was that Section 27001, as a violation of the First Amendment, was unenforceable, at least when the honking was done as a means of expressing her opinion. Specifically, Porter sought to block enforcement of Section 27001 against what she called “expressive honking.” In Porter’s view, expressive horn use includes honks not only in “support candidates or causes,” but also to “greet friends or neighbors, summon children or co-workers, or celebrate weddings or victories.” Nice try, Ms. Porter, but no cigar, at least in the opinion of the Ninth Circuit Court of Appeal. After a long dissertation dealing with whether Section 27001 is “content based” or “content neutral” (ultimately finding it to be the latter), a majority of the Court (in a split, 2-to-1 decision) held that Section 27001 “furthers an important or substantial governmental interest” that is “unrelated to the suppression of free expression;” i.e., traffic safety and avoiding the unnecessary startling of other drivers. The majority opinion also found the statute to be “narrowly tailored to further California’s interest in safety regulation,” and that it “leaves ample alternative channels for people to communicate their ideas and messages.” As such, the Court, upon balancing the interests involved, held Section 27001 to be constitutional; the intrusions on Ms. Porter’s First Amendment right to freedom of expression being relatively minor. So does this mean that as a law enforcement officer you should start citing anyone and everyone under all circumstances for their illegal “expressive honking” activities? Probably not. As noted by the Court, even the law enforcement witness in this case who testified as an expert for the State agreed that enforcement of Section 27001 is done “exceedingly rarely.” Good public relations and just plain common sense dictate that this should probably continue as the usual practice, reserving enforcement of Section 27001 for cases where it is clearly being abused and enforcement serves some real benefit.
Livestreaming Contacts with the Police: The majority of the federal Circuit Courts of Appeal have held that a private citizen has a First Amendment right to videotape public officials while performing their duties in public, including, but not limited to, police officers and other law enforcement officers. (E.g., see Gericke v. Begin (1st Cir. 2014) 753 F.3rd 1.) This includes the Ninth Circuit (See Askins v. United States Department of Homeland Security (9th Cir. 2018) 899 F.3rd 1035, 1043-1044.), which oversees the law on federal issues in California. But when that videotaping involves “livestreaming” (i.e., sending out real-time video to anyone who cares to watch), the issues are a bit different. So held the federal Fourth Circuit Court of Appeal in the recent case of Sharpe v. Winterville Police Department (4th Cir. Feb. 7, 2023) 59 F.4th 674. In Sharpe, officers attempted to stop a Dijon Sharpe—a passenger in a vehicle stopped for a traffic violation—from livestreaming the contact. Sharpe later sued the officers individually, as well as the town of Winterville, North Carolina, for attempting to violate his First Amendment right to videotape—and publish in real-time—the contact. The officers’ argument in response was that contrary to merely videotaping a police-citizen contact, livestreaming generates an unnecessary safety issue by potentially encouraging third parties to respond to the scene of an on-going traffic stop. The Court didn’t buy it, finding the officers to be civilly liable. However, in this case, the officers were held to have qualified immunity in that this new rule, as it specifically relates to “livestreaming” a traffic stop, was not clearly established at the time. The case, however, was remanded to the trial court for a determination of whether the Town of Winterville and its police department had a municipal policy regarding livestreaming, and if so, whether they could justify that policy sufficient to overcome a private citizen’s First Amendment protections. Note that Fourth Circuit cases are not binding on California peace officers. Absent a decision from the Ninth Circuit or, better yet, a California Court, a decision from another circuit is entitled only to “great weight” and is considered to be persuasive only. (See People v. Zapien (1993) 4 Cal.4th 929, 989.) But the reasoning in Sharpe makes sense. And the argument that livestreaming creates a potential safety issue for police officers is highly speculative, at best. The Fourth Circuit in Sharpe didn’t buy it. So as long as the person who is doing the livestreaming is not so in-your-face that he or she is physically interfering with your duties as a police officer, my suggestion is to let the person alone. Or, if you prefer (and I’m not telling you to do this), go ahead and seize his camera and/or physically arrest him should he resist, and make some case law for me to report on when you get sued. But before you do that, you might want to read an up-to-date nine-page legal memo I’ve written on the issues raised when persons photograph and/or videotape law enforcement officers in public, as well as whether an officer has a right to seize the camera should the photographing or videotaping capture what might be considered evidence of a crime. This memo is available upon request.
If you wish to make a voluntary financial contribution to help offset the costs of researching, writing, and publishing this Legal Update, please consider subscribing to our Professional Membership. You may also send a direct contribution to the author that conducted this research by clicking here. Your support is greatly appreciated.