ROAD FATALITIES INVOLVING HEAVY VEHICLES
IN SOUTH AUSTRALIA


OCTOBER 2007


Date of Issue: 1 Nov 2007


DateTimeVehicle(s) InvolvedCrash TypeNo. Of
Fatalities
Post
code
Road

Heavy Vehicle Fatalities - 2004 to 2007
2004 2005 2006 2007
Month
January1200
February2312
March1321
April2033
May3010
June2010
July7511
August1403
September1121
October1210
November000
December213
Total232115








 

Fatal Crashes

OCTOBER
2006
Year to Date
2006
OCTOBER
2007
Year to Date
2007
Vehicles
Single Vehicle-2-2
Multiple Vehicle110-8
Total112-10
Fatalities
Single Fatality112-9
Multiple Fatalities---1
Total112-10





Explanatory Notes
  1. This publication contains details of the number of road fatalities and road fatal crashes involving Heavy Vehicles that occurred in South Australia during OCTOBER 2007 together with comparable figures for some earlier periods. Figures relating to the current year are provisional and may be subject to revision.
  2. Caution should be exercised in interpreting the statistics in the publication in light of the size of the numbers and the short time period involved.
  1. A fatal road crash occurs if a road crash results in the death of any person involved in the crash.
  2. A fatal crash is any road crash which results in one or more fatalities.
  3. In this publication, "Adelaide" means the Adelaide Statistical Division.
  4. Enquiries regarding these statistics or related publications should be directed to Road Crash Information Unit on (08) 8343 2854.

Runtime Error

Server Error in '/WebTeamAttachments' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>