DUI in Philadelphia After a Traffic Stop Was the Stop Legal

In a Philadelphia DUI case, the legality of the stop is often the first and most important question. A traffic stop is a constitutional seizure under both the Fourth Amendment and Article I, Section 8 of the Pennsylvania Constitution. If the stop was illegal at the outset, the defense may seek suppression of everything that followed, including the officer’s observations, statements, field sobriety evidence, and in the right case, chemical-test evidence. Pennsylvania law is especially important here because it draws a sharp line between two kinds of vehicle stops: investigatory stops, which may be supported by reasonable suspicion, and stops for completed, non-investigable Vehicle Code violations, which generally require probable cause. In DUI cases, that distinction matters a great deal because “erratic driving” may justify a brief investigation for impairment, while a completed technical violation often requires more.

The other recurring issue is duration. Even a lawful stop can become unlawful if police prolong it beyond the time reasonably needed to address the traffic mission without new, independent reasonable suspicion. The U.S. Supreme Court’s decision in Rodriguez v. United States and the Third Circuit’s post-Rodriguez cases, especially United States v. Green and United States v. Clark, are central here. They require courts to identify the moment when the stop was measurably extended and then ask whether police had enough additional suspicion by that point.

In Philadelphia practice, video evidence can be decisive, but it is not automatic and it is not perfect. The Philadelphia Police Department’s body-worn-camera directive requires activation during vehicle and pedestrian investigations and requires officers to note in reports when an incident was captured. At the same time, Philadelphia oversight audits have found that policy compliance is imperfect, which means gaps, late activation, and missing footage can become important suppression and credibility issues.

The governing law

The constitutional framework begins with a simple point: stopping a car is a seizure. Pennsylvania’s Constitution protects people in their “persons, houses, papers and possessions” from unreasonable searches and seizures, and the U.S. Supreme Court has long treated traffic stops as Fourth Amendment seizures as well.

Pennsylvania’s stop statute is 75 Pa.C.S. § 6308(b). It authorizes a stop when an officer has reasonable suspicion that a Vehicle Code violation “is occurring or has occurred” so the officer may check documents or secure information necessary to enforce the title. But Pennsylvania appellate courts have not read that language to mean that reasonable suspicion is always enough. In Commonwealth v. Chase and the en banc Superior Court decision in Commonwealth v. Feczko, Pennsylvania courts explained that when the suspected offense is one that can be meaningfully investigated after the stop, reasonable suspicion may suffice. When the suspected offense is a completed, non-investigable Vehicle Code violation, the stop generally requires probable cause. Feczko expressly quotes Chase on this point and is one of the clearest client-facing ways to explain the rule.

That distinction maps neatly onto DUI litigation. If police suspect DUI, a stop can be investigatory because the officer may confirm or dispel impairment by observing odor of alcohol, speech, eyes, coordination, admissions, and other indicators after contact. But if the stop is based only on a completed technical traffic offense that needs no further investigation, Pennsylvania law usually demands probable cause, not just a hunch.

Federal law overlaps but is not identical in emphasis. The Third Circuit holds that the Terry reasonable-suspicion standard applies to routine traffic stops and evaluates the stop objectively. Under Whren, an officer’s ulterior motive usually does not matter if there was an objective legal basis for the stop. In other words, a “pretextual” stop is usually still constitutional if the officer actually had a valid traffic basis. That is why in suppression litigation the defense must focus on the facts the officer can truly articulate, not just on what the officer may have been hoping to find.

One more foundational point matters in Philadelphia DUI cases: police cannot simply stop cars at random because they want to “check things out.” Absent a lawful checkpoint program or a specific basis for the seizure, discretionary spot checks are unconstitutional. That principle comes from Delaware v. Prouse and remains important whenever the stop report is vague or untethered to any real Vehicle Code event.

The stop/arrest line also matters. A brief roadside detention to investigate suspected DUI can rest on reasonable suspicion, but a custodial arrest and post-arrest procedures require probable cause. In practice, that means the Commonwealth must be able to justify both stages: first, why the car was stopped; second, why the driver was escalated from investigation to arrest. If one stage fails, important evidence may fall with it.

How courts evaluate common stop justifications

Equipment violations

Equipment-based stops are common because they look simple on paper: a broken rear light, a nonworking plate light, a windshield obstruction, or an allegedly unlawful tint. Pennsylvania’s Vehicle Code does require rear lighting, including stop lamps and a license-plate light, and it restricts windshield obstructions that materially impair the driver’s view. But “simple on paper” does not mean “automatic in court.” Officers still must articulate concrete facts that fit the statute being invoked.

The best Pennsylvania example is Commonwealth v. Holmes on rearview-mirror obstructions. The Supreme Court held that it is not enough for an officer to say merely that “something” was hanging from the mirror. The officer must articulate facts supporting the inference that the object materially obstructed vision, because the statute does not ban all hanging objects. That case is valuable in Philadelphia DUI practice because officers sometimes use air fresheners, placards, or mirror items as the original stop basis and only later pivot to intoxication. If the initial equipment theory collapses under Holmes, the rest of the case may be vulnerable.

Moving violations

Lane-use and signal violations are also classic stop justifications. Pennsylvania requires that a vehicle be driven as nearly as practicable within a single lane and that the driver use an appropriate signal before turning, changing lanes, or entering the traffic stream from a parked position. Those statutes give police real authority, but courts still ask whether the officer actually observed facts amounting to the violation and whether the applicable standard was probable cause or reasonable suspicion.

In Feczko, the court upheld the stop where the officer observed repeated movement over lane lines, concluding that the officer had probable cause to believe Section 3309(1) had been violated. The opinion is especially useful because it explains why some traffic facts are enough for a completed-lane violation even when the officer did not explicitly testify that the stop was “for DUI.” If the video really shows repeated centerline or fog-line incursions, the Commonwealth often argues that probable cause existed for the lane offense itself.

But the defense should resist broad generalizations. Not every drift, touch, or correction equals a valid stop. Older Pennsylvania decisions, including Commonwealth v. Gleason, show judicial skepticism when the driving described is slight, brief, or not clearly tied to danger. Gleason arose under the pre-amendment statute and therefore used a different doctrinal frame, but it remains a useful cautionary reminder that minor, equivocal driving facts do not automatically establish a lawful stop.

Erratic driving and suspected DUI

This is where the law becomes most favorable to the Commonwealth. Pennsylvania appellate decisions routinely recognize that weaving, repeated line crossings, unusual speed changes, or other erratic driving can justify a brief investigatory stop for DUI because further roadside investigation may reveal the decisive evidence of impairment. Feczko explains this logic directly, and later cases continue to repeat it.

For the defense, the key question is whether the officer’s stated basis really sounds like suspected impairment or instead sounds like a completed Motor Vehicle Code offense dressed up after the fact. If the report says “the vehicle briefly touched the fog line once,” that may be litigated very differently from “the vehicle repeatedly weaved across lane markers at 1:30 a.m. and nearly struck oncoming traffic.” Pennsylvania law is fact-specific here, and suppression often turns on the exact driving the video does or does not show.

Odor and post-stop observations

Odor of alcohol usually does not justify the initial stop because the officer ordinarily does not smell alcohol until after approaching the car. But once detected during a lawful stop, odor of alcohol can justify expanding the encounter into a DUI investigation, especially when paired with admissions, slurred speech, red or glassy eyes, or poor coordination. That is one reason stop legality and stop duration must be analyzed separately. A stop can start lawfully for a lane violation and then expand lawfully into DUI if new facts emerge before the traffic mission is complete.

Odor of marijuana deserves a narrower and more careful treatment. Pennsylvania’s appellate courts have made clear that marijuana odor is not a stand-alone basis for probable cause to search a vehicle after the Medical Marijuana Act, though it remains a relevant factor in the totality of the circumstances. That principle comes from Commonwealth v. Barr. Although Barr is a search case rather than a pure DUI-stop case, its logic matters whenever police try to convert odor alone into a broader criminal investigation. A Philadelphia DUI defense lawyer should be alert to officers who blur the line between a DUI inquiry and a generalized evidence search.

Video and paperwork are often where the case turns

Philadelphia is a body-camera city. PPD Directive 4.21 requires officers to maintain body-worn cameras in standby mode, activate them before responding to calls for service and during all law-enforcement-related encounters, and specifically record vehicle or pedestrian investigations. The directive also requires officers to note in the patrol log or later reports that the event was captured. For defense counsel, that creates a straightforward next question in almost every DUI case: where is the first footage of the claimed driving behavior, the approach to the car, the interaction, and the alleged signs of impairment?

The same directive creates an equally important nuance. In most cases, officers are allowed to review their own BWC footage when preparing incident reports and related documentation, and the directive says reports prepared after review should reflect that they are based on both the officer’s observations and later video review. That means discrepancies between a report and video can cut in more than one direction. Sometimes video disproves the report. Other times the report looks unusually polished because it was drafted after the officer knew exactly what the camera captured. Either way, the timing of review, report drafting, and supplemental paperwork matters.

Philadelphia oversight materials confirm that real-world compliance is imperfect. A 2026 city audit reported that, among officers who did record, only 53 percent followed the directive’s core requirements, including proper activation from standby mode and recording the full incident. Earlier city oversight materials similarly emphasize auditing compliance with Directive 4.21. That matters because missing first-contact footage, delayed activation, unexplained gaps, or silence during a crucial part of the encounter may not be incidental. In the right case, they can support cross-examination, impeachment, or a suppression theory tied to credibility and burden.

In practice, lawyers should compare at least six things: the timestamp of activation; whether the video begins before or after the emergency lights; whether lane markers or traffic conditions are visible; whether the audio captures alleged admissions; whether the officer narrates the reason for deactivation when recording stops early; and whether the written report’s description of impairment matches the contemporaneous footage. Those are not technicalities. In a close DUI stop case, they are often the case.

Suppression strategy and likely remedies

Pennsylvania’s suppression procedure is formal and powerful. Rule 578 requires pretrial requests for relief to be raised in a single omnibus pretrial motion unless justice requires otherwise, and Rule 581 specifically authorizes a motion to suppress evidence allegedly obtained in violation of the defendant’s rights. Rule 581 further places the burden on the Commonwealth to go forward with the evidence and to establish that the challenged evidence was not obtained in violation of the defendant’s rights. The rule also requires the judge to place findings of fact and conclusions of law on the record.

Timing matters. Pennsylvania practice materials and rule commentary describe omnibus pretrial motions as due within 30 days of arraignment, subject to recognized exceptions. In local Philadelphia practice, counsel should also pay close attention to case-specific scheduling orders, the Criminal Division’s compiled local rules and assignment materials, and the current e-filing and motions procedures published by the First Judicial District.

In a Philadelphia DUI stop case, the strongest suppression arguments usually fall into four buckets.

The first is that there was no lawful basis for the stop at inception. That can mean no real lane violation, no actual equipment defect, no reliable basis for a document stop, or an officer’s inability to articulate facts that fit the statute cited. Holmes is the classic obstruction case; Feczko and Chase frame the probable-cause versus reasonable-suspicion question for vehicle stops generally.

The second is that police used the wrong standard. A common example is a stop justified in court as if it were a DUI investigation when the stop report and testimony actually describe only a completed technical offense. If there was “nothing further to investigate,” Pennsylvania law generally required probable cause at the moment of seizure.

The third is unlawful prolongation. Under Rodriguez, Green, and Clark, the defense should identify the “Rodriguez moment” when the traffic mission was, or should reasonably have been, complete. If questioning, waiting, dog-sniff activity, or unrelated investigation continued beyond that point without new reasonable suspicion, the extension was unlawful. That framework applies even in cases that eventually become DUI cases, because officers sometimes use a minor traffic stop as a holding pattern while they probe for broader criminal evidence.

The fourth is the connection between the unlawful stop and the later DUI evidence. Pennsylvania’s implied-consent statute, 75 Pa.C.S. § 1547, authorizes chemical testing when an officer has reasonable grounds to believe a person drove in violation of the DUI statute, 75 Pa.C.S. § 3802. But that statutory testing regime does not cure an unconstitutional seizure. If the stop or detention was unlawful, later observations and testing may be vulnerable as fruits of that illegality. In many DUI cases, suppression of the stop-stage evidence can materially weaken or end the prosecution.

The practical remedy is usually an order suppressing specific evidence, not a generic declaration that the police acted improperly. But in real life, suppression often drives the result. If the Commonwealth loses the reason for the stop, the post-stop observations, or the chemical-test evidence, the case may be reduced substantially or dismissed.

Practical advice for clients during and after a stop

If you are stopped in Philadelphia, pull over safely, keep your hands visible, and provide the documents the officer lawfully requests. Do not argue roadside about case law, and do not try to “explain away” your drinking with statements like “I only had two drinks” or “I’m fine to drive.” Those admissions are often more damaging than people realize.

What you should do is preserve information. As soon as you safely can, write down the time, location, weather, traffic conditions, what the officer said was the reason for the stop, whether there was bodycam activation before contact, whether passengers heard the same things, whether there were witnesses, and whether your car had any actual mechanical issue. Save ride-share receipts, bar or restaurant receipts, toll records, text messages, call logs, GPS history, and names of passengers. If you have a medical, orthopedic, neurological, or anxiety-related condition that could affect balance, speech, or appearance, document that for counsel immediately.

If you are charged, get counsel involved early enough to demand preservation of video and to evaluate the stop before deadlines pass. In a DUI case, the difference between “unfortunate facts” and “suppressible evidence” often lies in details that disappear fast.

Attorney checklist and quick comparison

A defense lawyer evaluating a Philadelphia DUI stop should ask, at minimum:

• What exact statute did the officer claim justified the stop?

• Was the alleged violation investigatory or a completed technical offense?

• Did the officer truly have reasonable suspicion or probable cause under the correct Pennsylvania standard?

• What is the earliest video, and does it actually show the claimed violation?

• When was the stop measurably extended beyond the traffic mission?

• What new facts, if any, existed before that extension?

• When did the officer first claim to notice alcohol, marijuana, slurred speech, glassy eyes, or admissions?

• Did the officer review bodycam before writing the report?

• Is the report inconsistent with timestamps, audio, or lighting conditions?

• What evidence is a direct fruit of the stop and later detention?

The following comparison is a useful client-facing shorthand: