2 research outputs found

    Sleep-related vehicle crashes on low speed roads

    Get PDF
    BACKGROUND. Very little is known about the characteristics of sleep related (SR) crashes occurring on low speed roads compared with current understanding of the role of sleep in crashes occurring on high speed roads e.g. motorways. To address this gap, analyses were undertaken to identify the differences and similarities between (1) SR crashes occurring on roads with low (≤60 km/h) and high (≥100 km/h) speed limits, and (2) SR crashes and not-SR crashes occurring on roads with low speed limits. METHOD. Police reports of all crashes occurring on low and high speed roads over a ten year period between 2000 and 2009 were examined for Queensland, Australia. Attending police officers identified all crash attributes, including ‘fatigue/fell asleep’, which indicates that the police believe the crash to have a causal factor relating to falling asleep, sleepiness due to sleep loss, time of day, or fatigue. Driver or rider involvement in crashes was classified as SR or not-SR. All crash-associated variables were compared using Chi-square tests (Cramer’s V = effect size). A series of logistic regression was performed, with driver and crash characteristics as predictors of crash category. A conservative alpha level of 0.001 determined statistical significance. RESULTS. There were 440,855 drivers or riders involved in a crash during this time; 6923 (1.6%) were attributed as SR. SR crashes on low speed roads have similar characteristics to those on high speed roads with young (16–24y) males consistently over represented. SR crashes on low speed roads are noticeably different to not-SR crashes in the same speed zone in that male and young novice drivers are over represented and outcomes are more severe. Of all the SR crashes identified, 41% occurred on low speed roads. CONCLUSION. SR crashes are not confined to high speed roads. Low speed SR crashes warrant specific investigation because they occur in densely populated areas, exposing a greater number of people to risk and have more severe outcomes than not-SR crashes on the same low speed roads

    Sleep-related crash characteristics: Implications for applying a fatigue definition to crash reports

    Get PDF
    Sleep-related (SR) crashes are an endemic problem the world over. However, police officers report difficulties in identifying sleepiness as a crash contributing factor. One approach to improving the sensitivity of SR crash identification is by applying a proxy definition post hoc to crash reports. To identify the prominent characteristics of SR crashes and highlight the influence of proxy definitions, ten years of Queensland (Australia) police reports of crashes occurring in ≥100. km/h speed zones were analysed. In Queensland, two approaches are routinely taken to identifying SR crashes. First, attending police officers identify crash causal factors; one possible option is 'fatigue/fell asleep'. Second, a proxy definition is applied to all crash reports. Those meeting the definition are considered SR and added to the police-reported SR crashes. Of the 65,204 vehicle operators involved in crashes 3449 were police-reported as SR. Analyses of these data found that male drivers aged 16-24 years within the first two years of unsupervised driving were most likely to have a SR crash. Collision with a stationary object was more likely in SR than in not-SR crashes. Using the proxy definition 9739 (14.9%) crashes were classified as SR. Using the proxy definition removes the findings that SR crashes are more likely to involve males and be of high severity. Additionally, proxy defined SR crashes are no less likely at intersections than not-SR crashes. When interpreting crash data it is important to understand the implications of SR identification because strategies aimed at reducing the road toll are informed by such data. Without the correct interpretation, funding could be misdirected. Improving sleepiness identification should be a priority in terms of both improvement to police and proxy reporting
    corecore