Adot has released Crash Facts 2014 in early June (of 2015), as usual/expected; and I received the database from them very promptly. I have updated the graphical crash map so it now has data from 2009-2014 for ped-MV and bike-MV crashes.
The overall number of crashes ticked up (unless otherwise stated, all figures are year-over-year; 2013 vs. 2014; and are as was published in Crash Facts 2014 when it was published June 2015):
- number of MV crashes: 107,477 vs. 109,554 up modestly 1.93% 
- all Fatalities: 844 vs. 774 sharp drop of 8.83% 
- Total Injuries: 50,389 vs. 50,890 almost flat at up 0.99% 
The two most closely-watched traffic safety metrics, the number of fatalities per 100M Vehicle Miles Traveled (VMT), and per 100K population are not yet available but even after the sharp drop will remain worse for Arizonans than for the US overall.
The results for cyclists showed improvement compared to 2013 but are rather unexplainable —
- the number of bike-MV crashes: 2,039 vs. 1742 . down sharply, 15% 
- number of cyclists injured: 1,679 vs. 1459 down sharply 13% 
- The number of fatalities at 28 was one fewer than the last year’s 29 — but there’s still something unresolved about 2013 fatalities that I’m guessing won’t get straightened out until the FARS final 2013 gets released, normally in December of 2015. In any event the average yearly toll has been about 24. Fatalities, being relatively rare, have quite wide variation, making it hard to discern trends. For example in the most recent 10 year period there have been as many as 36 (in 2005) and as few as 18 (last year). More details on each AZ fatality here.
Longer Trends for cyclist/ped
I have a spreadsheet that tracks # of cyclist injuries and fatalities for 2001-2014. The number of cyclists injured this past year, 1,459, is well below the 14-year average of 1,616; This drop is a notable mystery.
More broadly, we have no good exposure data; though we can say in that time (which reflects 2001 thru 2013), the population of AZ has grown 24% and driving has increased 19%. AzStats.xls (current as of 2014 data) or web-viewable on google drive (the google drive version only current thru 2013). Also see the section on long-term trends section of last year’s 2013-data roundup.
The Drop in reported Cyclist Crashes?
(these numbers vary slightly, and will be a tiny bit higher, from those published, but you get the idea) Why the drop? Here is a 6 year history… I wanted to check city-by-city, below presented inelegantly is the year-over-year list.
The drop was very broad-based, virtually all larger agencies reports significant declines — Chandler, Gilbert, Glendale, Mesa, Phoenix, Scottsdale, Tempe, Tucson. Only Flagstaff saw any increase (it was a small change), among the larger agencies. Why?
|2013||LAKE HAVASU CITY||9|
|2014||LAKE HAVASU CITY||1|
SELECT IncidentYear,count(*) FROM ( 2012_incident AS i JOIN 2012_person AS p_bike ON i.IncidentID = p_bike.IncidentID) LEFT OUTER JOIN LOVCity ON i.CityId = LOVCity.id WHERE p_bike.ePersonType = 'PEDALCYCLIST' GROUP BY 1;
SELECT IncidentYear, LOVCity.name ,count(*) FROM ( incident AS i JOIN person AS p_bike ON i.IncidentID = p_bike.IncidentID) LEFT OUTER JOIN LOVCity ON i.CityId = LOVCity.id WHERE p_bike.ePersonType = 'PEDALCYCLIST' AND (IncidentYear=2013 OR IncidentYear=2014) GROUP BY 2,1; by the way, to get incident counts (instead of person counts) for all years, for all cities do: SELECT LOVCity.name, IncidentYear ,count(*) FROM incident i LEFT OUTER JOIN LOVCity ON i.CityId = LOVCity.id WHERE EXISTS (SELECT 1 FROM unit u WHERE u.IncidentID=i.IncidentID AND u.eUnitType IN ('PEDALCYCLIST')) GROUP BY 1, 2;
Note about published vs. database: the database I have isn’t updated (it’s frozen as of June of the year following) and incidents continue to trick in over the next year…
 per database vs. published; 2013 figure is 103 greater than database; this is typically due to a small number of incidents that trickle in after the database is frozen. The 2014 number, happily matches.
select count(1) from 2014_incident; => 107374, 109554
 totals match, which is slightly misleading, e.g. pedalcyclists for 2013 were revised, meaning some other category had to change.
SELECT count(1) FROM 2014_person WHERE eInjuryStatus LIKE "FATAL%"; => 844 , 774
 per database vs. published; 2013 figure is 92 greater than database. The 2014 number matches exactly. Point of order: they don’t count fatalities as injuries.
select count(1) from 2014_person WHERE InjuryStatus BETWEEN 2 AND 4; => 50297, 50890
 the 2013 figure matches exactly, which seems odd/wrong/unlikely because of stragglers. The 2014 figure matches exactly as expected
SELECT count(*) FROM 2014_incident i WHERE EXISTS (SELECT 1 FROM 2014_unit u WHERE u.IncidentID=i.IncidentID AND u.eUnitType IN ('PEDALCYCLIST')); => 2039, 1742 note: now can use the synthetic flags in incident table, so this is equivalent query: SELECT count(*) FROM 2014_incident i WHERE sF_Bicycle;
 the 2013 figure matches exactly, which seems odd/wrong/unlikely. While the 2014 figure is 7 higher than the database, which is also odd because 2014 numbers should agree.
select count(1) from 2014_person WHERE InjuryStatus BETWEEN 2 AND 4 AND ePersonType = 'PEDALCYCLIST'; => 1679, 1466