CrashDNA

Crash data.
Real-world context.

Explore CrashDNA
Texas / City guides
PUBLIC DATA. LOCAL CONTEXT.

Cisco Crash Guide.

Eastland County

Reported crash counts, locations and trends in Cisco.

Records through 2026-09-30 Source: TxDOT public records Prepared 2026-10-17

Choose a period, then select Update guide.

Guide figures: Oct 1, 2025 to Sep 30, 2026. Based on records available through Sep 30, 2026. The map uses a separate calendar year.

Reported crashes66 1.5% fewerCompared with Oct 1, 2024 to Sep 30, 2025
Fatal crashes1 1 more1 vs. 0
Compared with Oct 1, 2024 to Sep 30, 2025
People killed1 1 more1 vs. 0
Compared with Oct 1, 2024 to Sep 30, 2025
People seriously injured1 2 fewer1 vs. 3
Compared with Oct 1, 2024 to Sep 30, 2025

Reported crashes fell 1.5%.

Compared with Oct 1, 2024 to Sep 30, 2025. Counts alone do not tell us how risky a trip is.

Explore the data →
KNOW THE PLACE

Getting around Cisco

Cisco is a city in Eastland County, Texas. Include the place and county when looking up local road notices, especially where another Texas community shares the same name. [1]

Location context, separate from the crash analysis below. Local road descriptions are added only after source review.

Local context sources
  1. U.S. Census Bureau · Texas place/county reference (2026)
  2. TxDOT · how to use DriveTexas for current conditions
THE LOCAL PICTURE

Cisco’s crash picture

From Oct 1, 2025 through Sep 30, 2026, the available records include 66 reported crashes in Cisco. That is 1 fewer than the 67 recorded for the corresponding dates a year earlier—a 1.5% decrease in reported crashes.

Interstate 20 appears repeatedly in the reports, with 14 crashes listed under that road name.

Based on the public TxDOT records included in this guide. Counts describe reported crashes, not risk per trip or why a crash happened. Source, coverage and limitations →

WHERE IT HAPPENS

Explore Cisco’s reported crash locations.

Named areas with the most matching crashes. Choose an area to zoom in.

  1. The ranked areas appear when the map loads.
View the area data ↓

Approximate areas, not verified intersections. The list follows the map filters.

This map uses a calendar year, not the guide’s reporting period. The figures above cover Oct 1, 2025 to Sep 30, 2026 (66 crashes). The count below follows the selected map year and filters.

Loading crash map…

Loading the 2026 map. Records are available through 2026-09-30.

Background map: OpenStreetMap. Map tiles load automatically; your browser sends the provider your IP address and the requested map area.

Map area data & how locations are grouped

Numbers on markers are crash counts. Areas use a 0.002° grid (roughly 180–220 metres across in Texas), not verified intersections. Names use the most common recorded street or intersection-pair label in each area across the loaded history; they are not verified neighborhood boundaries. Several areas may share a road name. Missing-coordinate records remain in the totals.

THE LONGER VIEW

The same month, year over year

Compare seasonal patterns across 2022–2026. Each line is one year. Hollow points and dashed segments mark partial months; gaps are not treated as zero. Historical context stays visible when you change the guide’s reporting period.

20222023202420252026
036811JanFebMarAprMayJunJulAugSepOctNovDecJan 2022: 5 reported crashesFeb 2022: 4 reported crashesMar 2022: 4 reported crashesApr 2022: 2 reported crashesMay 2022: 5 reported crashesJun 2022: 5 reported crashesJul 2022: 6 reported crashesAug 2022: 6 reported crashesSep 2022: 5 reported crashesOct 2022: 11 reported crashesNov 2022: 4 reported crashesDec 2022: 6 reported crashesJan 2023: 4 reported crashesFeb 2023: 4 reported crashesMar 2023: 8 reported crashesApr 2023: 8 reported crashesMay 2023: 4 reported crashesJun 2023: 6 reported crashesJul 2023: 7 reported crashesAug 2023: 7 reported crashesSep 2023: 6 reported crashesOct 2023: 7 reported crashesNov 2023: 2 reported crashesDec 2023: 4 reported crashesJan 2024: 11 reported crashesFeb 2024: 5 reported crashesMar 2024: 4 reported crashesApr 2024: 1 reported crashMay 2024: 3 reported crashesJun 2024: 2 reported crashesJul 2024: 7 reported crashesAug 2024: 8 reported crashesSep 2024: 10 reported crashesOct 2024: 6 reported crashesNov 2024: 8 reported crashesDec 2024: 6 reported crashesJan 2025: 3 reported crashesFeb 2025: 3 reported crashesMar 2025: 3 reported crashesApr 2025: 6 reported crashesMay 2025: 9 reported crashesJun 2025: 2 reported crashesJul 2025: 8 reported crashesAug 2025: 8 reported crashesSep 2025: 5 reported crashesOct 2025: 8 reported crashesNov 2025: 7 reported crashesDec 2025: 4 reported crashesJan 2026: 5 reported crashesFeb 2026: 4 reported crashesMar 2026: 5 reported crashesApr 2026: 5 reported crashesMay 2026: 5 reported crashesJun 2026: 4 reported crashesJul 2026: 7 reported crashesAug 2026: 5 reported crashesSep 2026: 7 reported crashes
View year-over-year monthly data
Reported crashes in the same calendar month across years. * Partial month; — no loaded value.
Month20222023202420252026
Jan541135
Feb44534
Mar48435
Apr28165
May54395
Jun56224
Jul67787
Aug67885
Sep561057
Oct11768—
Nov4287—
Dec6464—
Same-period year-to-date comparison

From January 1 through 2026-09-30, Cisco recorded 47 crashes, compared with 47 over the matching dates a year earlier. The reported counts were equal.

WHEN IT HAPPENS

When crashes are reported.

Oct 1, 2025 to Sep 30, 2026 · Known hours only.

Time of day

04712 AM: 0 reported crashes12 AM1 AM: 0 reported crashes2 AM: 0 reported crashes3 AM: 1 reported crash3 AM4 AM: 0 reported crashes5 AM: 3 reported crashes6 AM: 1 reported crash6 AM7 AM: 2 reported crashes8 AM: 2 reported crashes9 AM: 2 reported crashes9 AM10 AM: 3 reported crashes11 AM: 7 reported crashes12 PM: 6 reported crashes12 PM1 PM: 3 reported crashes2 PM: 7 reported crashes3 PM: 4 reported crashes3 PM4 PM: 4 reported crashes5 PM: 5 reported crashes6 PM: 5 reported crashes6 PM7 PM: 3 reported crashes8 PM: 4 reported crashes9 PM: 1 reported crash9 PM10 PM: 0 reported crashes11 PM: 3 reported crashes
View the data table
Reported crashes by hour
GroupCrashesFatal crashesPeople killedPeople seriously injured
12 AM0000
1 AM0000
2 AM0000
3 AM1000
4 AM0000
5 AM3000
6 AM1000
7 AM2000
8 AM2000
9 AM2000
10 AM3110
11 AM7000
12 PM6000
1 PM3001
2 PM7000
3 PM4000
4 PM4000
5 PM5000
6 PM5000
7 PM3000
8 PM4000
9 PM1000
10 PM0000
11 PM3000

Day of the week

0815Sun: 7 reported crashesSun7Mon: 4 reported crashesMon4Tue: 11 reported crashesTue11Wed: 8 reported crashesWed8Thu: 8 reported crashesThu8Fri: 15 reported crashesFri15Sat: 13 reported crashesSat13
View the data table
Reported crashes by weekday
GroupCrashesFatal crashesPeople killedPeople seriously injured
Sun7000
Mon4000
Tue11000
Wed8000
Thu8000
Fri15001
Sat13110

Month by month

0482025-10: 8 reported crashes10/252025-11: 7 reported crashes2025-12: 4 reported crashes12/252026-01: 5 reported crashes2026-02: 4 reported crashes02/262026-03: 5 reported crashes2026-04: 5 reported crashes04/262026-05: 5 reported crashes2026-06: 4 reported crashes06/262026-07: 7 reported crashes2026-08: 5 reported crashes08/262026-09: 7 reported crashes
View the data table
Reported crashes by month
GroupCrashesFatal crashesPeople killedPeople seriously injured
2025-108000
2025-117001
2025-124000
2026-015000
2026-024000
2026-035000
2026-045000
2026-055000
2026-064110
2026-077000
2026-085000
2026-097000

Selected period; * partial month. Outlined bars mean missing coverage, not zero crashes.

WHO’S INVOLVED

Crashes by road-user involvement.

  • Truck / truck-tractor involved14
  • Commercial vehicle involved13
  • Motorcycle involved2
  • Bicycle involved0
  • Pedestrian involved0

Crash counts, not people. Categories overlap—a crash can appear in more than one group.

View involvement & severity details

People killed or injured are totals for the whole crash, not necessarily people in the named travel mode.

Crash involvement categories; do not sum these rows
GroupCrashesFatal crashesPeople killedPeople seriously injured
Truck / truck-tractor involved14000
Commercial vehicle involved13000
Motorcycle involved2000
Bicycle involved0000
Pedestrian involved0000
WHERE REPORTS CONCENTRATE

Roads with the most reports.

  1. Interstate 2014 crashes
  2. Conrad Hilton Boulevard7 crashes
  3. Mile Marker7 crashes
  4. Conrad Hilton3 crashes
  5. East Interstate 203 crashes

Oct 1, 2025 to Sep 30, 2026. Counts, not the chance of a crash on a trip. Street-name variants may split the same corridor. Short road labels are expanded for readability; the tables and CSV preserve recorded labels.

View all road rankings
Top 20 reported road labels by crash count
GroupCrashesFatal crashesPeople killedPeople seriously injured
IH 2014000
CONRAD HILTON BLVD7000
MILE MARKER7001
CONRAD HILTON3000
E IH 203000
CONRAD HILTON BLVD BLVD2000
SH 62000
W IH 202000
2061000
8TH ST1000
AVENUE F1000
BEECH ST1000
E 14TH1000
E 6TH1000
E 8TH ST1000
E FRONTAGE HWY1000
E INTERSTATE 201000
E MILE MARKER1000
ESAT 9TH ST1000
FRONT ST1000
Reported intersection pairs

Only records flagged as intersections with both street names. These are reported labels—not verified geographic intersections.

Top 20 reported street pairs by crash count
GroupCrashesFatal crashesPeople killedPeople seriously injured
8TH ST & CONRAD HILTON BLVD2000
206 & MILE MARKER1000
6TH ST & CONRAD HILTON1000
AVENUE A & E 8TH ST1000
AVENUE F & W 19TH STREET1000
AVENUE G & W 3RD ST1000
AVENUE H & W 10TH ST1000
BEECH & E 14TH1000
BEECH ST & EAST 16TH ST1000
CONRAD HILTON & N ACCESS1000
CONRAD HILTON & N ACCESS RD1000
CONRAD HILTON & W 8TH ST1000
CONRAD HILTON BLVD & INTERSTATE 201000
CONRAD HILTON BLVD & MILE MARKER1000
CONRAD HILTON BLVD BLVD & EAST 8TH ST1000
E 6TH & E 6TH1000
E FRONTAGE HWY & S CONRAD HILTON BLVD1000
FRONT & W 12TH1000
IH 20 & IH 201000
IH 20 & S SH 2061000
SOURCE & ATTRIBUTION

Cite this guide.

Using these figures? Keep the reporting period and source with them.

CrashDNA. Cisco Crash Guide. Cisco — Eastland County, Texas. All reported crashes; selected reporting period 2025-10-01–2026-09-30. Analysis of available public Texas Department of Transportation (TxDOT) crash records. Snapshot prepared 2026-10-17. https://crashdna.com/texas/cisco/

You can also select and copy the citation text above. Figures describe available records, not traffic-adjusted risk or independently verified complete reporting.

Methods, definitions and limitations

Cisco city · Eastland County. Reported city code 76; county codes 67. Current Census place identifier 4815004 (2026 reference). These identifiers reconcile the reported source labels, not independently geocoded historical boundaries.

Source: public Texas Department of Transportation (TxDOT) crash records loaded for this publication. Guide focus: All reported crashes. All displayed totals, historical comparisons, maps, rankings and CSV rows use this cohort. Selected reporting period: exact recorded city label CISCO, Oct 1, 2025 to Sep 30, 2026. Each crash is counted once using its selected current record revision. This is not a metropolitan-area or police-agency-only filter.

Fatal crashes count events; deaths and serious injuries count people. Fatal and serious-injury crash groups use recorded severity codes 4 and 1. A crash can involve multiple vehicle or road-user types. Counts do not control for traffic or pedestrian activity, do not establish fault, and are not crash rates.

In the selected reporting period, 3 records lack usable Texas-range coordinates for Oct 1, 2025 to Sep 30, 2026 (the guide period, not the separate map year); 0 lack a usable hour; 5 lack a usable road label. 41 records are not assigned a usable intersection pair (including non-intersection crashes). Unknown categories remain in totals but not narrative rankings. Coordinates are not independently verified.

Latest 12 months means the latest available calendar month plus the preceding 11 months, clipped to loaded coverage; an unfinished final month is partial. Year to date means January 1 through the latest loaded date in that year, not through today. Historical charts and the map use the wider loaded history (Jan 1, 2022 to Sep 30, 2026); the monthly year-over-year chart shows up to five recent years. Map year, crash-type and outcome filters apply only to the map and its linked area table. Every matching record with coordinates contributes; there is no top-100 cap. Map locations are approximate grid centres, not exact crash sites. Area names use reported road labels, not verified neighborhoods. CSV contains aggregate tables, not individual crash records.

Loaded extraction intervals span the selected period. Source intervals do not guarantee complete reporting. New reports and amendments can change earlier months. Prepared 2026-10-17T22:07:38.106Z. Approved snapshots change only after an editor publishes an update.

Source extraction intervals
  • 2022-01-01 – 2022-03-01 · extracted 20260910100040
  • 2022-03-02 – 2022-04-26 · extracted 20260910100040
  • 2022-04-27 – 2022-06-22 · extracted 20260910100040
  • 2022-06-23 – 2022-08-22 · extracted 20260910100040
  • 2022-08-23 – 2022-10-16 · extracted 20260910100040
  • 2022-10-17 – 2022-12-08 · extracted 20260910100040
  • 2022-12-09 – 2022-12-31 · extracted 20260910100040
  • 2023-01-01 – 2023-02-27 · extracted 20260910100112
  • 2023-02-28 – 2023-04-24 · extracted 20260910100112
  • 2023-04-01 – 2023-04-24 · extracted 20260910100112
  • 2023-04-25 – 2023-06-19 · extracted 20260910100112
  • 2023-06-20 – 2023-08-17 · extracted 20260910100112
  • 2023-08-18 – 2023-10-12 · extracted 20260910100112
  • 2023-10-13 – 2023-12-05 · extracted 20260910100112
  • 2023-12-06 – 2023-12-31 · extracted 20260910100112
  • 2024-01-01 – 2024-02-29 · extracted 20260828124847
  • 2024-03-01 – 2024-04-26 · extracted 20260828124847
  • 2024-04-27 – 2024-06-22 · extracted 20260828124847
  • 2024-06-23 – 2024-08-22 · extracted 20260828124847
  • 2024-08-23 – 2024-10-16 · extracted 20260828124847
  • 2024-10-17 – 2024-12-09 · extracted 20260828124847
  • 2024-12-10 – 2024-12-31 · extracted 20260828124847
  • 2025-01-01 – 2025-03-05 · extracted 20260910100224
  • 2025-03-06 – 2025-05-01 · extracted 20260910100224
  • 2025-05-02 – 2025-06-29 · extracted 20260910100224
  • 2025-06-30 – 2025-08-29 · extracted 20260910100224
  • 2025-08-30 – 2025-10-23 · extracted 20260910100224
  • 2025-10-24 – 2025-12-16 · extracted 20260910100224
  • 2025-12-17 – 2025-12-31 · extracted 20260910100224
  • 2026-01-01 – 2026-03-03 · extracted 20260910100333
  • 2026-03-04 – 2026-04-30 · extracted 20260910100333
  • 2026-05-01 – 2026-06-27 · extracted 20260910100333
  • 2026-06-28 – 2026-08-29 · extracted 20260910100333
  • 2026-08-30 – 2026-08-31 · extracted 20260910100333
  • 2026-09-01 – 2026-09-30 · extracted 20261010194744

Download selected-period CSV · Download all-history CSV

CSV download
A table file you can open in a spreadsheet. Downloads contain grouped counts, not individual crash reports.
Crash count versus risk
A count tells you how many crashes were reported. Without knowing how much people drove, walked or cycled, it cannot tell you how likely a crash was on a trip.
Location identifiers and severity codes
These are source-system labels used to match places and classify recorded outcomes. They are not independent proof of a city boundary or the cause of a crash.
Back to top ↑

Public records. A clearer local picture.

Explore the patterns in another Texas community.

Explore another city →