Detroit 911 Non-Response Lawsuit: Ley v. City Of Detroit Raises ADA, FOIA And Police-Priority Questions

BadPD source-check, July 6, 2026: this is an allegation-stage litigation ledger, not a verdict. CourtListener’s public search API confirms Ley v. Detroit, City of, docket number 4:25-cv-13743, in the U.S. District Court for the Eastern District of Michigan. The public metadata lists a November 24, 2025 filing date, federal-question jurisdiction, Judge F. Kay Behm, Magistrate Judge Kimberly G. Altman, Plaintiff Phillip Dean Ley Jr., and defendants or parties including the City of Detroit, Detroit Police Department, Detroit 911 Emergency Communications Center, and Jane Doe parties.

BadPD also reviewed local filing text and OCR from the complaint, response packet, proposed amended complaint, service/default packet, and the City/DPD motion-to-dismiss packet that appears in local OCR as ECF No. 18, filed June 23, 2026. Those files contain private address, phone, family, medical, and witness-contact details. This article does not republish those details. It uses the lawsuit as a public-record accountability lead: what did Detroit 911 do, what did Detroit Police do, what records exist, and why does the City have visible machinery for vehicle enforcement while a resident alleges repeated emergency-service failure at his own home?

The case in one sentence

The complaint and proposed amendment allege that Detroit 911 and Detroit Police repeatedly delayed, refused, or failed to provide meaningful emergency response across an August 20, 2025 stolen-vehicle call, an October 17, 2025 medical emergency involving disability-related communication, an October 19, 2025 public-indecency/no-response call near a young child’s bedroom window, and an October 23, 2025 police encounter involving Officer Byrd 914 and unidentified officers.

That sentence has to be read with the correct legal caution. These are allegations. The City and DPD deny that the complaint states viable claims and, according to the local motion packet OCR, moved to dismiss under Rule 12(b)(6). The City’s arguments, as summarized in the local intake file and response text, include that the Detroit Police Department is not a separate legal entity, that the complaint does not plead a municipal policy or custom under Monell, that due process/equal protection allegations are insufficient, that ADA allegations fail, that state-law claims face immunity and public-duty barriers, and that the FOIA claim is limited or improperly pleaded against DPD.

BadPD’s position is narrower and records-first: if the City is right on any technical pleading point, that still does not answer the public-safety question. Did the calls happen? What did the 911 audio say? Were CAD records created? Was a police car dispatched? What was the priority code? Which operator handled the calls? Was there an address or phone-number note? Did officers arrive? Did bodycam or dashcam record the later police encounter? Did FOIA requests sit unanswered? Those are not vibes. They are public records.

What the complaint alleges

The complaint says the August 20, 2025 incident began with a stolen-vehicle report. The plaintiff alleges he told 911 that he had recent surgery and medical restrictions that prevented him from traveling. He alleges an operator said her hands were tied and transferred him to a non-emergency line. He further alleges a sworn officer then instructed him to call 911 back and ask for a car to be sent, but the response remained delayed. The proposed amended complaint alleges police did not arrive for approximately three to four hours and that the vehicle and property were not recovered.

The October 17, 2025 medical-emergency allegation is the ADA access core of the case. The proposed amended complaint alleges the plaintiff was in extreme pain and needed emergency medical help. It alleges his spouse, described in the filing as deaf or hearing impaired, called 911 as a family member and companion. It alleges the operator’s audio or manner of communication made the call difficult or impossible for the hearing-impaired caller, that a requested communication adjustment was ignored or refused, and that the plaintiff had to take over the call while in medical distress. It further alleges the operator became confrontational, a supervisor delay followed, and assistance was dispatched only after the plaintiff asserted disability-related rights and legal remedies.

The October 19, 2025 allegation is the one that makes the public-safety contrast hard to ignore. The proposed amended complaint says the plaintiff called 911 to report a man urinating outside the bedroom window of the plaintiff’s young child. It alleges the operator took the plaintiff’s name and number, but no officers arrived and no follow-up occurred. BadPD is not publishing the home address, family names, phone numbers, or graphic details. The public point is simple: a resident alleges he called 911 about public indecency at his own home near a child, and Detroit allegedly did not send help.

The October 23, 2025 allegation concerns Officer Byrd 914. The proposed amended complaint alleges Byrd shoved the plaintiff outside the home and that other officers refused to identify themselves. The response packet says video evidence exists, but this article is not posting or characterizing that video beyond the court-filed allegation. The clean public-record demand is bodycam, dashcam, officer-identification records, dispatch logs, reports, complaint history, and preservation of any citizen video that the plaintiff chooses to file or publish later.

ADA access is not an optional customer-service feature

There is a reason the ADA portion matters beyond this one household. The U.S. Department of Justice says Title II covers telephone emergency service providers and other state and local government entities. DOJ guidance says 911 systems must provide direct, equal access to people with disabilities who use TTY/TDD technology and that equal access includes response time, response quality, hours of operation, and other features. The guidance also says procedures, training, testing, and equipment matter because emergency access is life-safety access.

Federal regulation also matters. 28 CFR 35.160 says a public entity must take appropriate steps to ensure communications with applicants, participants, members of the public, and companions with disabilities are as effective as communications with others. It defines a companion as a family member, friend, or associate of an individual seeking access to a public service when that person is an appropriate person for the public entity to communicate with. 28 CFR 35.162 says telephone emergency services, including 911 services, must provide direct access to individuals using TDDs and computer modems.

That does not mean the plaintiff automatically wins. It means Detroit should have a record showing what its 911 effective-communication procedures are, how operators are trained, what accessibility equipment and protocols are used, how supervisors respond when a caller reports communication difficulty, and whether call-taker conduct matched the policy. If the City believes the call did not create an ADA issue, it should say so with the call recording, CAD notes, training record, and policy. If the record shows the plaintiff was forced to take over an emergency call because communication with a hearing-impaired companion failed, Detroit has a serious access problem to answer.

The vehicle-enforcement contrast

The user’s broader point is that Detroit can move with paperwork and enforcement machinery when vehicles, towing, auctions, and violations are involved, while this lawsuit alleges the same system failed to provide basic household emergency response. That contrast should be handled carefully. It is not proof by itself. It is a records question about municipal priorities.

Detroit’s official Police Department page lists police towing fees, pay vehicle towing fees, report vehicle theft, report crime, submit crime tips, police policies, and records. Detroit’s official event pages continue to list DPD vehicle auctions, including a June 26, 2026 abandoned-vehicle auction with cash-only terms, bidder rules, vehicle-removal deadlines, storage-fee warnings, and a restriction that law-enforcement personnel may not bid on a vehicle they themselves seized, their command seized, or that they had involvement with or foreknowledge of.

The City also has a formal Towing Rate Commission process. Its 2025 presentation to the Board of Police Commissioners lists police-authorized towing, storage fees, administrative fees, and towing-related city standards. That kind of bureaucracy proves Detroit knows how to build detailed operational systems around vehicles. The same level of detail should exist around 911 access, response times, public-indecency calls, stolen-vehicle response, officer identification, and FOIA production.

Detroit and Wayne County also have a long public record of vehicle-seizure fights. The Institute for Justice’s Detroit civil-forfeiture case challenged Wayne County vehicle forfeiture practices. IJ says the case involved residents whose cars were seized and held through civil forfeiture even when owners were not accused of wrongdoing. Separately, the Sixth Circuit’s January 7, 2026 decision in Nationwide Recovery, Inc. v. City of Detroit involved DPD towing permits and suspected tow-company misconduct. The Sixth Circuit affirmed nominal damages after concluding that the City deprived Nationwide of process but that after-acquired evidence would have justified termination.

Those vehicle cases do not prove Ley’s allegations. They do prove that Detroit-area vehicle enforcement, towing, impound, forfeiture, and process questions are not imaginary. They are litigated, documented, and expensive. So when a Detroit resident alleges a stolen-vehicle call took hours, a public-indecency call got no police, and FOIA requests for those records did not receive timely production, the right answer is not institutional shrugging. The right answer is the record.

Detroit 911 has been under public scrutiny before

This case also does not emerge in a vacuum. WXYZ’s 2019 investigation reported that thousands of high-priority Detroit police calls had left people waiting 30 minutes or more, with hundreds waiting longer than an hour during the period reviewed. The station reported that its investigation triggered 109 individual 911 response investigations, discipline for at least 32 employees, and new policies for lengthy response-time review. WXYZ also reported remarks from then-Board of Police Commissioners Chairman Willie Bell acknowledging that Detroit was falling short in many areas.

That is background, not proof of the 2025 allegations. But background matters because the Ley lawsuit alleges the same public concern in a fresh, household-level form: when a Detroiter calls for help, can the resident rely on 911, or does the resident need a lawsuit, video, FOIA requests, and public pressure before anyone explains what happened?

Detroit’s own open-data portal has a police serviced 911 calls dataset describing police emergency response calls for service in the city since September 20, 2016. BadPD wants the city to connect the lawsuit’s dates and call types to the raw data, CAD records, priority codes, dispatch notes, unit availability, and final dispositions. The data exists somewhere. The question is whether the public can see enough of it to test the complaint.

The motion to dismiss does not answer the facts

The local response packet says Defendants filed their Rule 12 motion on June 23, 2026 and asked for dismissal with prejudice. At a pleading stage, a motion to dismiss does not decide what really happened. It argues that even if the complaint’s well-pleaded facts are accepted for pleading purposes, the legal claims are insufficient. That procedural posture matters.

If Detroit says DPD is not a separate suable entity, the public can understand that as a municipal caption issue. It does not make the 911 audio disappear. If Detroit says the complaint did not plead a policy or custom, the next question is whether the plaintiff should be allowed to amend and whether records show repeated failures. If Detroit says the ADA claim is wrongly framed because it relies on a spouse’s hearing impairment, 28 CFR 35.160’s companion language is immediately relevant. If Detroit says no retaliation or equal-protection claim is plausible, the call logs, dispatch notes, and address flags become the test.

BadPD is not giving legal advice and is not predicting how Judge Behm or Magistrate Judge Altman will rule. The accountability point is separate from the litigation prediction: Detroit should not be able to dodge the public-record question by winning a technical pleading fight. Emergency calls, bodycam, dashcam, CAD logs, complaint follow-up, officer identities, and FOIA logs are still the public ledger.

What is confirmed, alleged, pending, and disputed

Confirmed by public docket metadata: CourtListener’s public search API shows Ley v. Detroit, City of, case number 4:25-cv-13743, filed November 24, 2025, in the Eastern District of Michigan. It lists federal-question jurisdiction, Judge F. Kay Behm, Magistrate Judge Kimberly G. Altman, plaintiff Phillip Dean Ley Jr., and parties including the City of Detroit, Detroit Police Department, Detroit 911 Emergency Communications Center, and Jane Doe parties. It also shows RECAP documents listed but unavailable through the public API result at access time.

Alleged in local filing text reviewed by BadPD: delayed or refused stolen-vehicle response on August 20, 2025; disability-related communication failure during an October 17, 2025 medical emergency; no police response to an October 19, 2025 public-indecency call near a young child’s bedroom window; an October 23, 2025 Officer Byrd 914 incident; four November 16, 2025 FOIA requests allegedly not timely answered; and failure to provide meaningful follow-up after complaints.

Confirmed by public official sources: Detroit’s public website lists police towing fees, vehicle-theft reporting, crime reporting, DPD vehicle auctions, DPD policies, and police records resources. ADA.gov and 28 CFR sections 35.160 and 35.162 place public emergency telephone service access and effective communication within Title II’s accessibility framework. DOJ’s 2003 complaint and the Civil Rights Litigation Clearinghouse document an older federal oversight era involving DPD, which is relevant history but not proof of current facts.

Pending records: 911 audio, CAD records, dispatch notes, priority codes, call-taker IDs, supervisor notes, address flags, police unit availability, stolen-vehicle report records, public-indecency call disposition, bodycam/dashcam, officer identities, complaint-intake logs, commissioner or police-commissioner follow-up notes, FOIA request logs, FOIA response letters, and any court-filed amended complaint or response accepted by the docket.

Disputed or not yet independently verified: every incident detail remains allegation-stage unless proven by records or admitted by the City. BadPD has not independently verified the citizen video in this article. BadPD is not publishing witness contact information, family names, minor details beyond the minimum public-safety description, address, phone numbers, medical specifics beyond what is necessary to describe the ADA claim, or any private court-upload credentials.

Records Detroit should preserve and produce

First, Detroit should preserve all 911 audio, text-to-911 records if any, CAD records, dispatch notes, operator notes, supervisor notes, call-transfer logs, and unit-status logs for the listed dates. If Detroit says a call was not emergent, coded differently, or handled properly, the record should show it.

Second, Detroit should identify the operators and supervisors involved in the August 20, October 17, and October 19 calls. If privacy rules prevent public naming at this stage, the court can use protective procedures. But the identities should not remain permanently hidden if they are necessary to test ADA training, retaliation, and non-response allegations.

Third, DPD should preserve bodycam, dashcam, officer-identification records, incident reports, radio traffic, and internal review materials tied to Officer Byrd 914 and the unidentified officers. If officers refused to identify themselves, that should be treated as a policy-compliance issue, not an informal misunderstanding.

Fourth, Detroit should produce a clean FOIA ledger: the four request dates, request numbers, public body routing, statutory due dates, extensions if any, fee notices if any, denials if any, productions if any, and the reason for any non-response. FOIA failures often hide operational failures. That is why this article treats FOIA as a core accountability lane, not a paperwork sideshow.

Fifth, Detroit should disclose whether the plaintiff’s address or phone number had any internal flags, notes, complaints, prior calls, nuisance labels, enforcement notes, or officer-safety notations. The proposed amended complaint alleges continuing limited 911 service. If there is an address-level explanation, the plaintiff and the court need to know it. If there is no such explanation, the City should say that too.

The public-interest frame

The issue is not whether Detroit can enforce vehicle rules. It can. The issue is whether the same city that can run towing systems, auction vehicles, set storage fees, route reports, and publish bidder rules can also provide reliable emergency access when a resident calls about a stolen car, medical distress, public indecency near a child, and officer conduct. Public safety is not only enforcement against residents. It is also service to residents.

Detroit should not be allowed to have one level of precision for collecting towing fees and another level of vagueness for answering emergency-service allegations. If the City has records that disprove the allegations, produce them. If the records support the allegations, fix the system. If the records are missing, that is its own accountability story.

BadPD’s editorial position is direct: the public should watch this case because it asks a basic government question. Does Detroit 911 treat emergency access as a right people can rely on, or as a discretionary service that depends on who calls, what the operator thinks, and whether the resident has the stamina to keep calling, file FOIA requests, and sue?

What BadPD will track next

BadPD will track the docket for the motion-to-dismiss ruling, any accepted amended complaint, any response or reply filings, any order on service/default issues, and any discovery order tied to 911 records. BadPD will also watch for City admissions, denials, or evidence in the docket. If Detroit produces call recordings, CAD logs, bodycam, dashcam, or FOIA records, those records should be summarized with date, source, and privacy redactions.

BadPD will also build the Detroit 911 accountability checklist around this case: call date, call type, priority code, operator, supervisor, dispatch time, arrival time, no-response explanation, records produced, ADA communication issue, bodycam/dashcam status, officer ID status, complaint follow-up, and FOIA response. That is the format residents need when they say the system picks and chooses who gets help.

For now, the public takeaway is limited but important. The case is real. The public docket metadata exists. The allegations are specific enough to demand records. Detroit’s official vehicle/towing machinery is visible and documented. ADA emergency-communication duties are real. The remaining question is whether Detroit can show, with records, that it treated this household’s emergency calls the way a city is supposed to treat emergency calls.

Local Filing Materials Reviewed By BadPD

BadPD reviewed local copies and extracted text of the original complaint packet, response in opposition to the City/DPD motion to dismiss, proposed amended complaint, service/default materials, and OCR of the City/DPD motion-to-dismiss packet. Those local files contain private address, phone, family, medical, and witness-contact information and are not linked or republished here. The public article uses them only as allegation-stage court-record material and redacts private details.

Source Trail

• CourtListener public search API: Ley v. Detroit, City of (Case filed November 24, 2025; accessed July 6, 2026) – Public docket metadata confirming case name, docket number 4:25-cv-13743, E.D. Michigan, federal-question jurisdiction, Judge F. Kay Behm, Magistrate Judge Kimberly G. Altman, parties, filing date, and unavailable RECAP documents.
• CourtListener public docket page (Accessed July 6, 2026) – Public docket landing page for the case; used with CourtListener API output and local filing text.
• City of Detroit Police Department page (Accessed July 6, 2026) – Official DPD page listing police services including report vehicle theft, police towing fees, pay vehicle towing fees, report crime, crime tips, records, policies, and public mission statements.
• Detroit Police Vehicle Auction event, 7D's Towing (June 26, 2026 event; accessed July 6, 2026) – Official example of DPD vehicle-auction activity, bidder conditions, vehicle removal rules, and law-enforcement bidding restrictions.
• City of Detroit Towing Rate Commission presentation to BOPC (June 25, 2025 presentation; accessed July 6, 2026) – Official city towing-rate record showing police-authorized towing standards, fees, storage, administrative fees, and stolen-vehicle recovery fee discussion.
• Detroit Open Data: Police Serviced 911 Calls (Accessed July 6, 2026) – City data portal page describing police emergency response calls for service in Detroit since September 20, 2016.
• ADA.gov: Access for 9-1-1 and Telephone Emergency Services (Last updated February 28, 2020; accessed July 6, 2026) – U.S. Department of Justice guidance on Title II coverage of telephone emergency services, direct/equal access, response time, response quality, procedures, training, and testing.
• 28 CFR 35.160, effective communication (Accessed July 6, 2026) – Regulatory text requiring public entities to make communications with members of the public and companions with disabilities as effective as communications with others.
• 28 CFR 35.162, telephone emergency services (Accessed July 6, 2026) – Regulatory text stating that telephone emergency services, including 911 services, must provide direct access to individuals using TDDs and computer modems.
• DOJ 2003 complaint against City of Detroit and DPD (Filed June 12, 2003; accessed July 6, 2026) – Historical federal civil-rights complaint alleging DPD pattern/practice issues, inadequate training, supervision, complaint handling, force review, arrests, and detention conditions. Used as history, not proof of current Ley allegations.
• Civil Rights Litigation Clearinghouse: U.S. v. City of Detroit (Accessed July 6, 2026) – Case-history source on the 2003 DPD consent-judgment era and later compliance/monitoring developments.
• WXYZ 7 Action News: Detroit 911 response delays investigation (Published 2019; accessed July 6, 2026) – Historical local investigation documenting long waits for high-priority Detroit police responses and resulting internal investigations/discipline. Used as background, not proof of the Ley complaint.
• Institute for Justice: Detroit civil forfeiture case (Case filed February 5, 2020; accessed July 6, 2026) – Civil-liberties case page on Wayne County/Detroit vehicle forfeiture allegations and property-rights litigation. Used to contextualize vehicle-seizure distrust, not as proof of current Ley allegations.
• Justia: Nationwide Recovery, Inc. v. City of Detroit (Sixth Circuit decision January 7, 2026; accessed July 6, 2026) – Published towing-program due-process case involving DPD towing permits, suspected tow-company misconduct, and nominal-damages ruling after process failure. Used as public context for Detroit towing governance.