On Thursday, November 5, 2026, in West Philadelphia, a uniformed Philadelphia Police Department officer handcuffed Jerald Bridges outside a store near 54th and Berks streets and released him with a disorderly-conduct citation. Hours later, the same officer returned in a marked PPD SUV to 54th and Arlington streets, confronted Bridges on a residential property over the claim that Bridges had “liked” the officer’s daughter’s Instagram pictures, shoved him, and repeatedly swatted at a bystander’s phone until it fell to the ground. A bystander filmed it. The Philadelphia Police Department has confirmed, on the record, that it is reviewing the interaction, and the investigation stood open at the last reporting this file rests on. That is the documented core of this file, and it is enough: the physical acts are not one side’s say-so — they are on the footage itself.
Two disciplines govern everything that follows, and they print here, on the file’s face. First: the officer has no name on the record. The department has not identified him; no outlet has named him; no discipline and no charge has been announced. He appears in this file by role only — “the officer” — and the individual file this library would ordinarily build is gated until a primary source identifies him (§06). Second: the fact the confrontation turns on is disputed. Bridges admits his friends commented on the officer’s Instagram photos that day; he denies, on the record, ever liking the daughter’s pictures. The only support for the daughter-likes is an anonymous source whose evidence has never been published. The dispute prints as a dispute, in the same breath as the accusation, everywhere it appears in this file (§02).
One more fence, stated once and held throughout: the officer’s daughter is a bystander to this story. She is never named, described, or pictured in this file, no account handle is given, and her age is not established on the record — this file states none. She appears by role only, because the confrontation cannot be told without the accusation that caused it.
The first encounter is reported — it rests on Bridges’s account, given to 6ABC and carried consistently by the outlets that covered the story; the citation itself has not been produced to this file, and its court disposition is an open pull (§07). Bridges and several other men were waiting for food outside a store near 54th and Berks streets when an officer told him to move. Bridges’s account: “He told me to move, and I told him, I said, ‘I’m waiting for my food.’ He said, ‘You’re not moving fast enough, I’m gonna give you a (code violation notice).’ I said, ‘Alright.’ When I started to walk off, he grabbed me and put me in handcuffs.”
Bridges says he was ticketed and placed in the back of a police cruiser; NBC10’s reporting characterizes the detention as for disorderly conduct, ending in release with a citation. Bridges also filmed part of this first encounter — and video obtained by 6ABC appears to show the same officer swat at Bridges’s phone in the first encounter as well (PhillyVoice, summarizing 6ABC). The phone, in other words, enters this story twice.
Two facts of description, carried because the reporting carries them and for no other reason: Bridges is a Black man; the officer is a white man, visible in the footage. No outlet reports any racial statement by the officer, and none is alleged in any account this file rests on.
Between the encounters sits the fact this whole story turns on — and it is unresolved on the record. What is admitted: in the hours after the citation, Bridges’s friends found the officer’s Instagram account and commented on his Halloween costume photos. Bridges, to 6ABC: “He had a clown outfit on for Halloween, and they said, ‘That outfit suits you.’” Bridges says no one commented about or disrespected the officer’s daughter.
What is denied: that anyone liked the daughter’s pictures. Bridges, to NBC10, on the record: “That didn’t happen. I did not like photos of his daughter. I don’t know his daughter.” Against the denial stands a single counter-claim: an unnamed source told NBC10 it had evidence that, within an hour of the citation, Bridges liked several of the daughter’s photos. That evidence has never been published. The two accounts cannot both be true, and nothing on the record pulled settles which one is.
How the post that brought this story here handled that dispute is itself part of the record. FIRE’s on-screen card hedges correctly — “reportedly liking hers” — but FIRE’s own post summaries flatten the hedge away, describing the men as engaging with the accounts “by commenting and liking photos” as settled fact. That unhedged version fails: it asserts the story’s central disputed fact. This file carries the dispute in the same breath as the accusation, every time — including this paragraph.
The second encounter is documented — it is on the banked bystander footage, and every outlet that covered the story describes the same acts. The officer returned to the area of 54th and Arlington streets in a marked PPD SUV; a second officer appears to remain seated in the vehicle, and only one officer confronts anyone. The SUV stops; the officer gets out and crosses toward the men on a residential property. A man is heard: “Don’t come on this property.” The officer, advancing: “You want to ‘like’ my daughter’s pictures?” The answer: “Nobody ‘liked’ your daughter’s picture, bro.”
Then the acts the camera settles. The officer shoves Bridges. He starts to walk away, notices the bystander filming, and says: “Record all you want.” He then swats at the phone repeatedly until it falls to the ground, and leaves. The shove, the words, the swatting, and the fall are visible and audible in the footage itself — graded DOCUMENTED, not alleged. What the footage does not show is any damage to the phone: the fall is documented; no source on the record reports the phone was damaged, and the original poster’s claim that it was is graded in the sources view, where it belongs — as an unsupported claim, not a fact.
The legal frame around those acts is context, printed as context and not as a finding about this officer. Philadelphia sits in the Third Circuit, where the right to record police performing their duties in public is established precedent (Fields v. City of Philadelphia, 3d Cir. 2017), and engaging with public social-media posts is protected expression — the position FIRE’s explainer advances, and standard First Amendment doctrine. Whether this officer’s conduct was retaliation is the subject of the open department investigation and has no official finding. This file makes none.
The gravest claim in circulation about November 5 is Bridges’s allegation — his alone, and printed here as exactly that. Bridges told NBC10 the officer threatened him: “I’m scared to be near him. He said he was going to put a bullet in my head. I don’t want to be near him. I’m scared. That’s the honest to God truth.”
What the footage does to that claim: nothing either way — and that is the point. The alleged threat is not intelligible in the audio of the circulating footage as transcribed; the transcription of the confrontation carries the repeated accusation, the denials, profanity, and then noise after the phone is swatted. NBC10’s own coverage, as relayed, notes the same limit: the video does not establish whether the alleged threat was made, but Bridges maintains that the officer threatened him. One attribution variance rides with the claim and is recorded without adopting either version: one secondary account reports that the person who recorded the encounter told NBC10 the officer allegedly threatened to shoot him — whether that is a second allegation or a garbled relay of Bridges’s is not found on the record.
So the claim stands where the record leaves it: a named complainant’s on-record allegation, uncorroborated by the footage, neither proven nor disproven by anything this file holds. It prints in this file only inside this section and its sources entry — never as a headline, never as a fact.
The footage was first shared by the Facebook page “NO GUN ZONE Incorporated for Philadelphia” and spread across platforms. On Friday, November 6, 2026, the Philadelphia Police Department confirmed it was aware of the video and reviewing the interaction. The department’s statement, quoted verbatim by PhillyVoice: “The Philadelphia Police Department is aware of the video and the concerns raised regarding the interaction. The circumstances surrounding the incident are being reviewed. As such, we are unable to provide further comment at this time.” On Wednesday, November 11, the department said the investigation was ongoing and declined further comment. The Fraternal Order of Police Lodge 5 declined to comment, citing the open investigation.
The posture prints exactly as documented, and no further. As of the last reporting this file rests on (November 12–14, 2026): the investigation is open; the officer has not been publicly identified; no discipline has been announced; no charges have been filed against anyone arising out of the second encounter. Anything beyond that — an outcome, a name, a sanction — is not on the record, and this file does not supply it. The investigation watch is this file’s first open item (§07).
Every individual file in this library rests on an identified officer with a verifiable record. This officer has no name on the record, and this file will not invent or adopt one. The identification gate is a primary source: a PPD statement, a court record, or department discipline naming him. Until one lands, he is “the officer” — and the circulating attempt to name him shows exactly why the gate exists. An Instagram news summary of this story describes it as involving “Philadelphia police officer Gerald Bridges.” That identification fails, twice over: the spelling is wrong, and the role is wrong. Jerald Bridges is the civilian who was shoved — the complainant, not an officer. The summary hands the officer the victim’s name, corrupted. It is recorded here, inside this correction, so that no reader of this file ever repeats it as fact.
Two further attributions ride at their grades and no higher. The original poster attributes the officer to the “19th District” — the geography is consistent (the district’s own advisory council documents activity at this intersection), but PPD has not confirmed his assignment, and the attribution prints as the poster’s claim, not a fact. And a single secondary summary of the television coverage labels the officer “off-duty” — against accounts describing a uniformed officer arriving in a marked vehicle who had performed patrol functions hours earlier, with no department statement on duty status. His duty status is not established, in either direction, and this file states neither. The second officer, seated in the SUV, is attributed no conduct in any account and is not a subject of this file.
This file prints its open items in the open. Each pull below closes one, and the file will be updated at this same address when the paper lands.
The PPD investigation (§05): its outcome, any Internal Affairs finding, any discipline or criminal referral — and, above all, the official identification of the officer. That identification is the trigger for the individual file gated at §06; until it lands, this situation file is the whole of the library’s record on November 5.
The disposition of Bridges’s November 5 disorderly-conduct citation in the Philadelphia courts — the first encounter’s paper trail, not found in any source this file rests on (§01).
Whether the officer was body-worn-camera equipped, and whether department footage of either encounter exists and is released or obtainable by records request. The bystander’s camera is, so far, the only camera on the record.
The 6ABC Action News account is used in this file as relayed by PhillyVoice and other outlets; the segment itself, read directly, is an outstanding pull, and any variance it carries folds into this file in place.
Every file in the Public Court Records series, in one place. Counties: St. Joseph, Elkhart, Marshall and Allen in Indiana; Berrien and Cass in Michigan; Middlesex in Massachusetts; Sussex in New Jersey. Every file is free, forever.
Every material claim in this file traces to a record below. Reporting is credited to the outlet that did it. Where a source could not be reached in full, the file says so on its face. Last checked November 15, 2026.
The bystander recording of the second encounter, as carried in the post of record: the marked PPD SUV’s arrival, the repeated accusation (“You want to ‘like’ my daughter’s pictures?”), the denial, the shove, “Record all you want,” the repeated swatting and the phone’s fall. The physical acts at §03 grade DOCUMENTED from this footage. The audio was transcribed locally (faster-whisper, base pass, garble flagged); no threat language is intelligible anywhere in it (§04). Media SHA-256 42f1d690…, banked at the intake.
The PPD statement quoted verbatim (§05); the timeline — confirmation Friday, November 6, investigation ongoing Wednesday, November 11; FOP Lodge 5’s declination; Bridges’s first-encounter account via 6ABC, including the 6ABC-obtained video appearing to show the same officer swat at Bridges’s phone in the first encounter (§01); and its transcription of the confrontation exchange (§03).
The confrontation account; Bridges’s denial (“I did not like photos of his daughter. I don’t know his daughter”); the anonymous source’s unpublished-evidence counter-claim (§02); Bridges’s threat allegation and NBC10’s own note that the video does not establish it (§04); and the first sharing of the footage by “NO GUN ZONE Incorporated for Philadelphia,” with that poster’s claims graded at the corrections card below.
Bridges’s first-encounter account in his own words (§01) and the cruiser footage, as quoted and summarized by PhillyVoice and other outlets. Disclosure: the 6ABC article itself could not be opened by the intake lane; its account is used here as relayed, and the direct read is open pull 16-04.
The 38-second explainer these files answer (Foundation for Individual Rights and Expression). Its six on-screen cards hedge the disputed fact correctly (“allegedly,” “reportedly”); its post summaries do not — the unhedged version, presenting the daughter-likes as settled, fails as stated (§02). Its First Amendment framing (cards 4 and 6; the caption) is the organization’s advocacy position and legal context, graded as such at §03 — not a finding about this officer.
The Third Circuit precedent establishing the right to record police performing their duties in public — the legal context at §03. Whether this officer’s conduct violated that right or was retaliation is the subject of the open department investigation; no authority has ruled, and this file does not.
(1) “Philadelphia police officer Gerald Bridges” (a circulating Instagram summary): FAILED — wrong spelling, wrong role; Jerald Bridges is the civilian complainant (§06). (2) The poster’s claim that the filmer’s phone was broken when it fell: NOT FOUND — the fall is documented; the breakage is reported by no source (§03). (3) The poster’s claim that the officer unlawfully entered the property: ALLEGED — the footage shows the approach after “Don’t come on this property”; no authority has ruled on its lawfulness. (4) “Assault” as a charge or legal conclusion against the officer: NOT FOUND — the shove is documented; no charge has been announced. (5) Event dates of November 6 or November 7 in aggregator summaries: FAILED — the incident was Thursday, November 5, 2026. (6) The “off-duty” label (one secondary summary): NOT ESTABLISHED in either direction (§06).
This file is built photoless, by fence. The officer is unidentified; the footage circulates only inside the poster’s edited explainer (text cards, watermark, the officer’s face blurred by the editor); news stills of the confrontation are identity-less and were not banked for use; and no image of the officer’s daughter exists in the reporting or may be sought. The full verdict and the opening it waits on are recorded in this file’s PHOTO.md.