David Murray, 43, of Philadelphia, was arrested July 16 and charged with robbery and firearms offenses, according to the township’s release. District Justice Scott Palladino arraigned Murray and set bail at $250,000 cash.

The charges are allegations. The police announcement does not establish a conviction, and it does not say whether Murray entered a plea or whether he remains in custody beyond the arraignment.

What police said happened

The robbery was reported at approximately 7:26 a.m. June 13 at the CVS in the Glenside section of Abington Township. Police said a masked male displayed a handgun, forced an employee into the store’s office area and removed currency from a safe.

The precise location identified by police is the CVS Pharmacy at 2622 Jenkintown Road. The business is used by Glenside residents and workers, making the arrest a significant development for people connected to the local store and the surrounding area. The release, however, does not say that the pharmacy is closed, that customers face an ongoing threat or that the robbery reflects a broader increase in crime.

Investigation and arrest

Investigators from the three agencies worked together to identify Murray, police said. The arrest came July 16, more than a month after the June 13 robbery. The release names Murray as the suspect identified through that investigation but does not provide additional information about how authorities identified him.

It also does not confirm whether property or the handgun was recovered, whether anyone was injured or whether Murray remains at the Montgomery County Correctional Facility. Those details are not established by the approved release.

Police seek information

Authorities are asking anyone with information about the robbery or the investigation to contact Detective Alison Gontowski at 267-536-1113 or agontowski@abingtonpa.gov.

That request is the next publicly identified step in the case. The township announcement does not provide a further court date or another deadline. Additional court or custody information would require confirmation from an appropriate official record.

The inquiry concerns Philadelphia Police Department practices. The commission is asking for public input about how civilians experience these encounters in Philadelphia.

The announcement marks the start of an oversight review, not a completed investigation with conclusions. The available notice does not announce final findings or recommended policy changes.

What the commission is examining

The commission’s announcement identifies “mere encounters” as the focus of its inquiry but does not provide a definition of the term in the approved notice. It also does not state how many complaints or internal case reviews led the commission to begin the review.

Because the matter involves Philadelphia Police Department practices, its scope is citywide rather than limited to a named officer, neighborhood or individual incident. The commission’s notice does not identify particular officers or cases as the subject of its inquiry.

The commission has not stated that any officer violated the law. It also has not announced a final determination about the policing pattern it is examining.

Public input is the announced next step

For now, gathering public input is the next step identified by the commission. The notice asks for information about civilians’ experiences with the encounters under review, while leaving open what findings or recommendations may follow.

No complaint total, case-review total, deadline or timetable for releasing findings was included in the available announcement. That means the public notice establishes the inquiry’s subject and its request for input, but not a schedule for its completion.

The review could bear on police encounter practices, documentation, civilian rights and oversight of the Police Department. Those potential effects are not announced outcomes; the commission has not yet recommended changes.

Separate police record provides recent context

Separately, the Philadelphia Police Department published an official use-of-force incident record on July 9. That record identifies an incident on May 23, 2026, near Kensington Avenue and Hart Lane.

The oversight commission’s July 15 announcement does not identify that May incident record as a basis for the inquiry. The two official notices establish separate recent developments involving police oversight and a department use-of-force record, but the available materials do not state that they are connected.

As the inquiry proceeds, the confirmed next development is the commission’s collection of public input. Any findings, policy recommendations or further details about the complaints and internal reviews would need to be announced separately.

The ruling in Commonwealth v. Steadly, decided July 21, 2026, addresses the evidence required to prove a resisting-arrest charge under Pennsylvania law. The case arose from an encounter involving Philadelphia Police Officer Corey Moore and Steadly following a stop for a minor Motor Vehicle Code violation.

The decision is a statewide criminal-law ruling from Pennsylvania’s highest court. It provides guidance for prosecutors, defense lawyers and trial courts evaluating resisting-arrest cases, particularly when the legality or circumstances of an underlying arrest are contested.

What the court decided

The Supreme Court reversed the Superior Court’s decision, vacated Steadly’s resisting-arrest conviction and vacated the judgment of sentence. The court said the Commonwealth had failed to present evidence sufficient to sustain that conviction on the record before the trial court.

The ruling does not provide a sentence length in the available source material. The court’s action concerned the resisting-arrest conviction and its associated judgment of sentence.

Steadly had been charged with resisting arrest, an offense described in the statutory language discussed by the court as a second-degree misdemeanor. The Supreme Court’s ruling was based on whether the evidence satisfied the elements of that offense in this case; it was not a general ruling on every arrest involving reported bench warrants or every resisting-arrest prosecution.

Philadelphia encounter and reported warrants

According to the opinion, Moore stopped Steadly for a minor Motor Vehicle Code violation. During the encounter, a dispatcher reported that two bench warrants had been issued in Steadly’s name. Police then attempted to arrest him.

The Supreme Court reviewed the evidence used to support the subsequent resisting-arrest charge. The available account does not provide a complete factual record of the physical encounter, and the court’s conclusion turned on the evidence presented at trial rather than on a broad finding about police conduct.

The decision does not establish that police may never make an arrest when bench warrants are reported. Nor does the ruling characterize Steadly as cleared of every allegation arising from the encounter. Its direct result was the reversal of the lower appellate ruling and the vacatur of the resisting-arrest conviction and sentence.

Statutory elements at issue

Pennsylvania’s resisting-arrest statute requires proof that a person acted with intent to prevent a public servant from making a lawful arrest or carrying out another duty. The statute also requires circumstances involving either a substantial risk of bodily injury to the public servant or another person, or conduct that requires substantial force to overcome the resistance.

Those requirements were central to the Supreme Court’s analysis. The court determined that, under the particular facts and trial evidence in Steadly’s case, the prosecution had not met its burden of proof for the resisting-arrest conviction.

The ruling therefore offers a framework for assessing the statutory elements in future cases, while remaining tied to the evidentiary record before the court. Prosecutors must prove the offense’s required intent and the statute’s substantial-risk or substantial-force component; defense lawyers and trial courts may look to the decision when disputes arise over whether that proof was supplied.

What happens next

The Supreme Court’s disposition reversed the Superior Court and vacated the conviction and judgment of sentence. The approved source material does not identify any further hearing, remand proceeding or deadline in the case.

CPOC says the project is aimed at how these interactions are defined, coded, and documented in Philadelphia, including whether body-worn camera material is available for oversight review later.

What CPOC launched, and when

On July 15, 2026, CPOC announced it was launching an inquiry into a pattern of police interactions referred to as “mere encounters,” following complaints and internal case reviews about how civilians experience these encounters in Philadelphia.

Two days later, on July 17, CPOC posted a resident-facing project page explaining what a “mere encounter” is and how Philadelphians can participate.

What counts as a “mere encounter” (in CPOC’s framing)

CPOC describes a “mere encounter” as a voluntary interaction between police and a civilian. In CPOC’s description, the civilian “should be free to leave” and can decline to answer questions.

CPOC contrasts this with a “stop,” which it says requires reasonable suspicion and specific, articulable facts that would lead a reasonable officer to believe a person is involved in criminal activity.

What Philadelphia Police Directive 12.8 says about the “mere encounter” level

Philadelphia Police Department Directive 12.8 describes “three levels” of police-citizen interactions. For “Mere Encounter,” it describes a consensual interaction where an officer may ask questions and generally engage in conversation.

Under that directive, officers may ask for identification, but the citizen is under no obligation to engage or provide identification. The directive also states that refusal to comply with requests and conversations does not, by itself, provide the officer with additional suspicion.

What CPOC is asking the Police Department for

CPOC says it is requesting information from the Philadelphia Police Department specifically tied to encounters coded as “mere encounters.” In CPOC’s words, that includes:

• Data on encounters labeled “mere encounters,” and
• Body-worn camera video associated with those coded encounters.

In its July 15 announcement, CPOC also reported figures from a limited dataset it reviewed: it said “mere encounters” accounted for roughly 6% of police incidents over a recent six-month period from December 2024 to June 2025 (in the scope reviewed). It also said correctly tagged and linked body-worn camera video was available for only about 21% of those interactions.

What residents are being asked to do

CPOC is inviting Philadelphians who have experienced a “mere encounter” (or who know someone who has) to share their story through the survey linked from CPOC’s project materials.

CPOC is also organizing community workshops across neighborhoods. CPOC says workshops will include “Know your rights” training and group discussion, and that residents can request workshop information by emailing cpoc@phila.gov.

Why the coding and camera question matters

This inquiry is not only about what residents say happened during an encounter. It’s also about what police records reflect afterward — including whether body-worn camera footage is correctly tagged, linked, and available for oversight review.

CPOC is asking residents to participate while it collects data and experiences, and it says it plans to publish findings once the project is complete.

What to watch next

As CPOC gathers responses, residents may want to keep an eye out for future updates on what data and footage the commission receives from the Police Department for encounters coded as “mere encounters,” and what CPOC reports after its review is complete.

Sources

• CPOC project launch (July 15, 2026): includes the dataset numbers and what CPOC is requesting
• Philadelphia Police Directive 12.8: “Mere Encounter” definition