Yearly Traffic Safety Analysis

7 CRASHES IN
ARMSTRONG, IA
2016

All metrics benchmarked against2015

Total crashes in ARMSTRONG, IA increased from 5 in 2015 to 7 in 2016, representing a 40% rise year-over-year. Fatalities remained at 0 in both periods. The most notable shift was the increase in total injuries, which rose from 0 in 2015 to 2 in 2016.

7

40.0%was 5

Total Crash Events

0

Persons Killed

2

Persons Injured

0

Fatal Crash Events

Note: "Persons Killed" (0) counts individual fatalities across all crash events. "Fatal" in the severity table below (0) counts crash events where at least one fatality occurred. A single crash can result in multiple fatalities.

Source: Iowa Crash Data · ArcGIS Open Data · 2016-01-01 to 2016-12-31 · Aggregate counts from crash, person, and vehicle records

Trend Summary

Overall, crash incidents in ARMSTRONG, IA showed an upward trend year-over-year. The total number of crashes rose by 40%, from 5 crashes in 2015 to 7 crashes in 2016. This increase in crashes also corresponded with a rise in injuries, from 0 in 2015 to 2 in 2016.

Vulnerable Road User Casualties

0

Motorists Killed

Prior: 00.0%

2

Motorists Injured

Prior: 0%

Source: Iowa Crash Data · ArcGIS Open Data · 2016-01-01 to 2016-12-31 · Mode classified from person records (driver/passenger → motorist; pedestrian; bicyclist → cyclist; in-line skater / unspecified → other)

When Crashes Happen

The temporal distribution of crashes shifted between 2015 and 2016. The peak day for crashes moved from Friday in 2015, with 2 crashes, to Monday in 2016, also with 2 crashes. The peak hour also changed significantly, with 2 crashes occurring at 8 AM in 2015, while 2 crashes occurred at 1 AM in 2016.

Source: Iowa Crash Data · ArcGIS Open Data · 2016-01-01 to 2016-12-31 · Crash date field aggregated by weekday

Source: Iowa Crash Data · ArcGIS Open Data · 2016-01-01 to 2016-12-31 · Crash time field aggregated by hour (0-23)

Crash Severity Breakdown

Outcome by Severity (Crash Events)

Minor Injury1minor injury crashes14.3%
No Injury6no injury crashes85.7%

Source: Iowa Crash Data · ArcGIS Open Data · 2016-01-01 to 2016-12-31 · KABCO injury classification scale

Severity Distribution (Crash Events)

Source: Iowa Crash Data · ArcGIS Open Data · 2016-01-01 to 2016-12-31 · Most severe injury per crash record

Top Contributing Factors

The leading contributing factors to crashes differed between 2015 and 2016. In 2016, "FTYROW: From stop sign" was the most frequent factor, accounting for 2 crashes. In contrast, 2015 saw "Driving too fast for conditions," "FTYROW: From driveway," "Improper Backing," and "Other (explain in narrative): Other" each listed as a factor in 1 crash, with no single dominant factor.

Officer-Reported Primary Contributing Cause

FTYROW: From stop sign2 (28.6%)
Driver Distraction: Manual operation of an electronic communication device1 (14.3%)
Followed too close1 (14.3%)
FTYROW: At uncontrolled intersection1 (14.3%)
FTYROW: Making left turn1 (14.3%)
Ran off road - left1 (14.3%)

Source: Iowa Crash Data · ArcGIS Open Data · 2016-01-01 to 2016-12-31 · Officer-reported primary contributory cause per crash

Road & Environmental Conditions

Data for weather and lighting conditions were not available for comparison across both periods. For road surface conditions, crashes on dry roads increased from 3 in 2015 to 4 in 2016. Crashes on snowy roads remained consistent at 1 in both years, while 2016 also recorded 1 crash each on ice/frost and slush, conditions not present in the 2015 data.

Weather

Cloudy3 (50.0%)
Clear2 (33.3%)
Fog, smoke, smog1 (16.7%)

Source: Iowa Crash Data · ArcGIS Open Data · 2016-01-01 to 2016-12-31 · Weather condition at time of crash

Lighting

Daylight5 (71.4%)
Dark - roadway lighted1 (14.3%)
Dark - unknown roadway lighting1 (14.3%)

Source: Iowa Crash Data · ArcGIS Open Data · 2016-01-01 to 2016-12-31 · Lighting condition field

Road Surface

Dry4 (57.1%)
Ice/frost1 (14.3%)
Slush1 (14.3%)
Snow1 (14.3%)

Source: Iowa Crash Data · ArcGIS Open Data · 2016-01-01 to 2016-12-31 · Road surface condition field

Vehicles & Demographics

Top Vehicle Makes (15 vehicles)

1
CHEVROLET7 (46.7%)
2
DODGE3 (20%)
3
FORD3 (20%)
4
MERCURY1 (6.7%)
5
PONTIAC1 (6.7%)

Source: Iowa Crash Data · ArcGIS Open Data · 2016-01-01 to 2016-12-31 · Vehicle unit records

3 persons with unknown or unrecorded age excluded from age chart.

Sex Distribution (9 persons with recorded sex)

Male8 (88.9%)
100.0%prior 4
Female1 (11.1%)
-66.7%prior 3

Source: Iowa Crash Data · ArcGIS Open Data · 2016-01-01 to 2016-12-31 · Person-level records linked to crash events

Data Sources & Methodology

Primary Data Source

All crash data in this report is sourced from Iowa Crash Data, accessed programmatically via the ArcGIS Open Data API (SODA). This dataset contains official police-reported motor vehicle traffic crash records maintained by the reporting jurisdiction's law enforcement agency. Records are published to the open data portal by the municipality and are subject to the portal's terms of use.

Data Retrieval

  • Access method: ArcGIS Open Data API (SoQL queries)
  • Data format: Structured JSON via REST API
  • Record types queried: Crash events, person records, and vehicle unit records
  • Date filter applied: 2016-01-01 through 2016-12-31
  • Report generated: September 9, 2026

Data Coverage

  • Reporting period: 2016-01-01 through 2016-12-31 (366 days)
  • Geographic scope: ARMSTRONG, IA
  • Total crash records analyzed: 7
  • Total persons involved: 15
  • Total vehicles involved: 15

Analytical Methodology

  • Severity classification: Uses the KABCO injury scale (K=Fatal, A=Incapacitating injury, B=Non-incapacitating injury, C=Possible injury, O=No injury/property damage only), the standard classification in U.S. Model Minimum Uniform Crash Criteria (MMUCC). Severity is assigned per crash event based on the most severe injury in that crash. A single fatal crash (K) may involve multiple fatalities; therefore the "Persons Killed" count in the headline KPIs may differ from the "Fatal" crash count in the severity breakdown.
  • Contributing factors: Reflect the officer-determined primary contributory cause recorded at the time of the crash report. These are preliminary determinations and may not reflect final investigation findings.
  • Hit-and-run classification: Based on the hit-and-run indicator field in the official crash report, as determined by the responding officer at the scene.
  • Temporal analysis: Day-of-week and hour-of-day distributions are computed from the crash date/time timestamp in each record.
  • Demographics: Age and sex distributions are drawn from person-level records linked to each crash event. A single crash may involve multiple persons.
  • Vehicle data: Make information is drawn from vehicle unit records linked to each crash event.
  • AI commentary: Narrative sections are generated by Google Gemini (large language model) based on the structured data. Commentary is descriptive, not predictive, and should not be interpreted as expert opinion.

Limitations & Disclaimers

  • Only crashes reported to and documented by law enforcement are included. Minor incidents, unreported crashes, and near-misses are not captured in this dataset.
  • Data reflects conditions at the time of the initial police report and may be subject to subsequent corrections, reclassifications, or supplements by the reporting agency.
  • Open data portal records may experience a publication lag - recently occurring crashes may not yet appear in the dataset at the time of report generation.
  • AI-generated commentary is produced by a large language model and is intended to highlight patterns in the data. It does not constitute legal, medical, or professional analysis.
  • Percentages are calculated from reported data and are subject to rounding.

Non-Affiliation Disclosure

This report is produced independently by ThatCarHitMe.com (Injuria.ai). It is not affiliated with, endorsed by, or produced in partnership with any law enforcement agency, municipal government, state department of transportation, or the National Highway Traffic Safety Administration (NHTSA). Data is sourced from publicly available government open data portals.

Data License

The underlying crash data is provided under the municipality's Open Data Terms of Use and is made available to the public for unrestricted use. This analysis and report is © 2026 Injuria.ai and may be cited with attribution using the suggested citation below.

Corrections & Feedback

If you believe any data in this report is inaccurate or have questions about our methodology, please contact: data@injuria.ai. We are committed to accuracy and will issue corrections promptly.

Suggested Citation

ThatCarHitMe.com (Injuria.ai). "ARMSTRONG, IA Crash Intelligence Report: 2016." Published September 9, 2026. Reporting period: 2016-01-01 to 2016-12-31. Data source: Iowa Crash Data, ArcGIS Open Data. Available at: https://thatcarhitme.com/crash-data/iowa/armstrong/2016-annual-report

About the Publisher

ThatCarHitMe.com is a crash data intelligence platform developed by Injuria.ai, a legal technology company specializing in traffic safety analytics. We aggregate and analyze publicly available government crash data to produce structured intelligence reports for communities, researchers, journalists, and legal professionals. Our reports combine programmatic data retrieval from official open data portals with AI-assisted narrative analysis.

Questions about this report's data or methodology: data@injuria.ai

ThatCarHitMe.com · An Injuria.ai Company