FOIA + Public Records
Data for Safer Streets.
Public records are most useful when people can see both the data that has been released and the information still being requested. Select a city below to review verified results, partial productions, public-data referrals, or the current response status of an active Mantis Motion Labs records request.
Austin, Texas
Micromobility crash-level records
Official Austin Crash Report Data portal records filtered where units_involved = “Micromobility.” Austin identifies this as an umbrella category that can include devices such as hoverboards and one-wheel devices.
DATA AVAILABLE
Classification follow-up active
79Total records
2011–2026Coverage
72026 YTD
14Highest annual count · 2025
Annual micromobility-classified crash records
201112013120154201632017320185201932020320212202282023132024122025142026 YTD7
Current limitation: MML is still seeking clarification on Austin’s device classifications. Published totals reflect the City dataset’s existing “Micromobility” field rather than a Mantis-created reclassification.
Chicago, Illinois
CPD + CFD micromobility records received
Chicago Police supplied two partial data tables: a keyword-search case-report production and a separate crash-record production. Chicago Fire supplied annual e-scooter incident totals. MML is publishing the released row counts while continuing to challenge missing incident-level classifications and completeness.
PARTIAL DATA
PAC appeals active
1,857CPD case-report rows
3,127CPD crash rows
1,634CFD e-scooter incidents · annual totals
2023–Jun 2026CPD production coverage
CFD annual e-scooter incident totals
20221962023180202436820256302026 partial260
Important: The CPD report rows, CPD crash rows, and CFD annual totals are different record sets and must not be added together as a single unique-incident total. CPD request P183912 / PAC 95258 and CFD request L142149-060826 / PAC 95243 remain under follow-up because key device, severity, and incident-level detail is still incomplete.
San Diego, California
Fatal-collision public records under classification review
San Diego released responsive records and public crash-data resources for request 26-7550. MML is reviewing the vehicle-type dictionary and classification fields before publishing a micromobility-specific total.
RECORDS RELEASED
Classification review
TBAMicromobility total · under review
TBADevice-specific breakdown
RELEASEDResponsive records status
REVIEWClassification status
Current review status
ProductionReceivedPublic dataLinkedVehicle dictionaryReceivedClassification follow-upPending
MML will not publish a micromobility total until the released collision fields and vehicle-type classifications are reconciled. This prevents a broad bicycle, vehicle, or fatal-collision count from being mislabeled as a micromobility figure.
Washington, D.C.
Traffic-data source supplied; micromobility breakdown TBA
MPD closed request R011853-072926 by directing MML to its public traffic-data resources. MML is evaluating whether those sources contain the device classifications and crash-level detail needed for the requested micromobility analysis.
PUBLIC DATA REFERRAL
Completeness review
TBAMicromobility total
TBADevice classification
PUBLICData access status
REVIEWCompleteness status
Current request status
Agency responsePublic data referralCrash-level reviewIn progressDevice fieldsBeing evaluated
A public-data referral does not automatically mean the requested micromobility fields are available. MML is reviewing the source before deciding whether a narrower request or appeal is necessary.
Atlanta, Georgia
Micromobility crash records requested
Atlanta Police assigned open-records request OR 26-14861 and estimated that responsive records could require up to 28 business days to search and prepare. No publishable data production has been received yet.
PROCESSING
Estimated response window active
TBATotal records · awaiting production
TBACoverage · awaiting production
TBA2026 count
PROCESSINGAgency status
Current request status
RequestOR 26-14861StatusProcessingTargetAround Sept. 10
No numerical total is displayed because Atlanta has not yet produced the requested dataset. TBA will be replaced only after MML receives and validates responsive records.
Boston, Massachusetts
Awaiting substantive public-records response
Boston acknowledged request R-2026-667 and identified a 10-business-day response target. That target passed without a substantive response or extension, so MML sent an overdue status follow-up on August 14.
FOLLOW-UP SENT
Response overdue
TBATotal records · awaiting response
TBACoverage
TBA2026 count
OVERDUEResponse status
Current request status
RequestR-2026-667Follow-upSent Aug. 14CheckpointAug. 19
No total is available for publication until Boston provides responsive data or a public-data source that can be validated against the request.
Miami, Florida
Micromobility records request awaiting production
Miami acknowledged request W077341-072826, but no production, estimate, extension, or clarification followed the initial acknowledgement. MML sent a status follow-up on August 14.
AWAITING RESPONSE
Status follow-up sent
TBATotal records · awaiting production
TBACoverage
TBA2026 count
WAITINGAgency response
Current request status
RequestW077341-072826Follow-upSent Aug. 14CheckpointAug. 19
TBA indicates the agency has not yet supplied data that MML can responsibly summarize on this page.
Dallas, Texas
Micromobility records request awaiting production
Dallas acknowledged request D027685-072726, but no responsive dataset, estimate, ruling notice, or clarification followed. MML sent a status follow-up on August 14.
AWAITING RESPONSE
Status follow-up sent
TBATotal records · awaiting production
TBACoverage
TBA2026 count
WAITINGAgency response
Current request status
RequestD027685-072726Follow-upSent Aug. 14CheckpointAug. 19
No numerical total is displayed until Dallas produces responsive records or directs MML to a suitable public dataset.
Los Angeles, California
Micromobility crash request under statutory extension
LAPD request 26-14253 remains open. The Department invoked unusual circumstances and extended its determination period while searching, collecting, and reviewing records across separate Department entities.
EXTENDED
Determination due Aug. 24
TBATotal records · awaiting determination
TBACoverage
TBA2026 count
AUG. 24Current determination date
Current request status
Request26-14253Status14-day extensionReview dateAug. 24
MML is waiting through the stated extension period before requesting another status update. No data total has been published.
Minneapolis, Minnesota
Classification and data-source review reopened
Minneapolis reopened request DR26_010825 after MML’s clarification. City staff are investigating the exact City and DVS data sources and any existing classification documentation relevant to the requested micromobility records.
INVESTIGATING
Request reopened
TBATotal records
TBAMicromobility classification
REOPENEDRequest status
AUG. 20Next checkpoint
Current request status
RequestDR26_010825StatusReopenedReviewCity/DVS sources
The request is active again, but the City has not yet supplied a validated micromobility-specific dataset. Totals remain TBA.
Phoenix, Arizona
Citywide request requires a location or grid
Phoenix Police advised that the citywide search is too broad and requires a specific location or grid. MML is narrowing the request to a defined precinct/search area before production can proceed.
CLARIFICATION REQUIRED
Narrowed scope needed
TBATotal records
TBACoverage
TBA2026 count
ACTIONScope clarification
Current request status
RequestR038614-072926StatusClarification requiredNext stepNarrow search area
No Phoenix total is available because the agency has not yet run the narrowed search. Publishing a zero or estimated count at this stage would be misleading.
New Orleans, Louisiana
Micromobility records request remains open
New Orleans request 26-16022 remains active with its response date moved to August 31, 2026. A second routed public-safety request is also being tracked separately.
EXTENDED
Due date Aug. 31
TBATotal records · awaiting production
TBACoverage
TBA2026 count
AUG. 31Current due date
Current request status
Primary request26-16022StatusExtendedDue dateAug. 31
No data production has been validated yet, so the public-facing metrics remain TBA until responsive records are received.
Reading the data: Counts reflect the fields, definitions, and classifications supplied by each agency. “TBA” means a requested total is not yet available for responsible publication because MML is awaiting production, validating the records received, or seeking clarification. Results should not be treated as directly comparable across jurisdictions until device definitions, injury severity, record types, and reporting practices are aligned.
