York County, Pennsylvania
York County incidents, made clear.
Search the latest public incident snapshot, explore approximate location context, and understand what has appeared across the captured archive—all in one independent community resource.
Delayed snapshot
Source time: Jul 27, 1:45 AM ET
Useful ways to explore
Start with the question you have.
Review York County, PA traffic incidents, municipality records, archive patterns, and update feeds without digging through a long source table.
01
Check recent traffic listings
02See captured traffic records from the last 24 hours before a commute or trip.
Open traffic view →Look up a municipality
03Choose a township, borough, or York City to narrow the full searchable archive.
Choose a location →Compare archive patterns
04Switch between 7 days, 30 days, and the captured period to inspect descriptive counts.
Explore charts →Follow the update feed
Use the RSS feed in a compatible reader for a lightweight stream of captured records.
Open RSS feed →Full archive search
Find the record you need.
Search every stored record by call type, road, intersection, municipality, or box number. Results are paged for a faster, shorter mobile experience.
Incident list
Showing 71–80 of 132
Newest matching records first. Times are Eastern.
Fire response
Source: Fire
Archived
Jul 9, 6:39 PM
Fire incident
Category-only archive record; a detailed source type was not retained.
LOUCKS RD near SUSQUEHANNA TRL N, ARSENAL RD / PENNSYLVANIA AVE MANCHESTER TWP
Traffic response
Source: Traffic
Archived
Jul 9, 6:02 PM
Traffic incident
Category-only archive record; a detailed source type was not retained.
ARSENAL RD near COURT ALY / N QUEEN ST MANCHESTER TWP
Traffic response
Source: Traffic
Archived
Jul 9, 7:52 AM
Traffic incident
Category-only archive record; a detailed source type was not retained.
LOUCKS RD near PENNSYLVANIA AVE / SUSQUEHANNA TRL N, ARSENAL RD MANCHESTER TWP
Traffic response
Source: Traffic
Archived
Jul 9, 7:28 AM
Traffic incident
Category-only archive record; a detailed source type was not retained.
BOARD RD near CHURCH RD MANCHESTER TWP
Traffic response
Source: Traffic
Archived
Jul 8, 8:20 PM
Traffic incident
Category-only archive record; a detailed source type was not retained.
TURNBERRY CT near DEAD END / DETWILER DR MANCHESTER TWP
Traffic response
Source: Traffic
Archived
Jul 8, 7:06 PM
Traffic incident
Category-only archive record; a detailed source type was not retained.
N GEORGE ST near KEYSTONE DR, HAYSHIRE DR / HAYSHIRE DR MANCHESTER TWP
Traffic response
Source: Traffic
Archived
Jul 8, 2:34 PM
Traffic incident
Category-only archive record; a detailed source type was not retained.
CHURCH RD near DERRY CT MANCHESTER TWP
Fire response
Source: Fire
Archived
Jul 7, 8:17 PM
Fire incident
Category-only archive record; a detailed source type was not retained.
LUCY LN near WILLOW RIDGE DR / CASPIAN DR MANCHESTER TWP
Fire response
Source: Fire
Archived
Jul 7, 6:21 PM
Fire incident
Category-only archive record; a detailed source type was not retained.
BLACKBRIDGE RD near GRIM LN, WOODLAND VIEW DR / FLOUR MILL RD W MANCHESTER TWP
Fire response
Source: Fire
Archived
Jul 7, 5:06 PM
Fire incident
Category-only archive record; a detailed source type was not retained.
PAULOWNIA LN near BITTERNUT BLVD / DUXBURRY DR MANCHESTER TWP
Approximate map
Location context, not scene guidance
The incident list is the complete accessible view. Map points load only when this view is opened.
Map ready when you areOpen Map on mobile or scroll this panel into view on desktop.
Approximate street/intersection pointMunicipality-area group
Explore the captured archive
Patterns you can inspect.
Showing the latest 30 captured calendar days. Choose a period, inspect a bar, or open a category or municipality in the incident explorer.
Records over time
Daily captured records
Mon, Jul 27, 2026: 2 captured records.
Source categories
What was listed
Municipalities
Where records were listed
Site-derived groups
Detailed incident mix
Traffic response
1,235 57.2%Fire response
776 35.9%Vehicle crash
58 2.7%Traffic complaint
22 1%Motorist assistance
12 0.6%Alarm
9 0.4%Structure fire
8 0.4%Road condition
8 0.4%Public safety
8 0.4%Electrical / utility
7 0.3% Detailed source type available for 6.7% of records in this view. Category-only archive records are never assigned a guessed subtype.
Time-of-day pattern
7 PM
177 captured records were listed during this hour in the selected period. Times are Eastern.
Read these as captured archive counts, not a safety score. Seven- and 30-day charts end on the newest captured date. A zero means no records were captured for that period; it does not prove no incidents occurred. The public source can be delayed, incomplete, corrected, or differently classified over time, and population, road volume, call handling, and unlisted activity are not controlled for. Some older records retain only a broad source category because their detailed type was not captured; the site labels those records instead of inferring a subtype.
Verified public resources
Know where to go next.
Incident awareness is only one layer. Use official sources for alerts, travel conditions, weather, and preparedness guidance.
01
York County Emergency Management
02Official local emergency management information and alert guidance.
York County government511PA travel conditions
03Official road conditions, restrictions, traffic incidents, cameras, and alerts.
PennDOTYork weather & hazards
04Forecasts, watches, warnings, and hazardous-weather information.
National Weather ServiceReady PA preparedness
Make a plan, gather supplies, understand alerts, and prepare your household.
Commonwealth of PennsylvaniaIf a call is nearby
Stay informed. Stay clear. Let responders work.
- Do not approach an incident scene for a better view.
- Never use approximate map points to bypass a closure.
- Use 511PA and official instructions for travel decisions.
- Call 911 only for emergencies—not for incident details.
About the project
Built independently for a better-informed York County.
Sponsor York 911 Online began as an independent incident-reposting project. Version 2.1 turns the public feed into a more useful civic resource: detailed source incident types when available, a searchable archive, honest location context, transparent freshness, safety guidance, and links to authoritative information.
This site is not a newsroom, dispatch center, government service, or complete record of emergency activity. It preserves public source entries as captured and adds descriptive organization—not verification or official interpretation.
Straight answers
Questions people should ask.
Is Sponsor York 911 Online an official York County website?
No. This is an independent, unofficial community project. The incident records come from the public York County WebCAD source, but this website is not operated by or affiliated with York County government, its 911 center, or any emergency service.
How current is the incident information?
A scheduled process checks the public source about every four minutes when it is healthy. The page always shows the stored source time and a Current, Delayed, or Unavailable label so old data is not presented as live.
Are the map markers exact?
No. Locations are approximate public-awareness context. Street/intersection geocodes are not scene verified. Records without a usable geocode are grouped at a clearly labeled municipality-area anchor based on the 2025 U.S. Census TIGERweb internal point; that anchor is not a scene location. Records without a reliable municipality are kept in the list and not pinned. Never use a marker to approach a scene or bypass a closure.
Why do some older records only say Fire incident or Traffic incident?
York WebCAD publishes both a broad source category and a detailed incident type. A past duplicate-header parsing issue captured only the broad category for part of the archive. Those records are labeled category-only rather than guessing a structure-fire, crash, or other subtype that the stored data cannot prove. New snapshots use the detailed source field.
Why can a call change or disappear?
Public CAD entries can be updated, corrected, reclassified, delayed, duplicated, removed, or cleared as responders work. The archive reflects what the public source listed at the time it was collected, not a final incident report.
Can I rely on this site during an emergency?
No. Call 911 for emergencies and follow instructions from public officials. This project is for general awareness and historical context, not dispatch, navigation, reporting, or emergency decision-making.
How is this independent project funded?
Hosting and project work are supported by voluntary donations and clearly labeled paid sponsors. Sponsors do not control incident records, rankings, safety guidance, or how the public source is presented.
Paid sponsor · Founding Partner
Alibi Tattoo
Alibi Tattoo is the first Founding Partner helping keep York County Incident Repeater online, readable, mobile-friendly, and useful for the community.
Visit Alibi TattooLocal partnership opportunities
Put your support behind a useful York County resource.
Businesses and community organizations can support hosting, archive storage, safety-resource reviews, and ongoing improvements through clearly labeled placements.
Local sponsor placementReach residents through a clearly labeled supporter card.Preparedness spotlightsSupport useful seasonal education without changing official guidance.Data and media collaborationFund custom summaries, visuals, or embeddable public-interest tools while the underlying source stays transparent.Editorial independenceIncident records, rankings, and safety guidance are never for sale.
Ask about sponsorship
Keep the resource independent
Community-supported, locally managed.
Donations help cover hosting, maps, storage, monitoring, and the work behind a clear and reliable experience.
Support with PayPaldonate@sponsoryork911.online