We have target processing times for all crash reports. These targets relate to the time taken from the date thatat is the crash report is received by Thethe Transport Agency until the time it is entered in the crash analysis system (CAS).(CAS). Delays in reporting a crash to Thethe Transport Agency, and errors in initial reporting (e.g. an injury crash initially reported as a non-injury crash),crash) may lead to delays in the crash being processed.
The following sections provide more detailed information about the current situation,situation (as at 1 March 2017).31 October 2016). This information will be updated on a quarterly basis, and more frequently if the situation changes significantly.
Fatal crashes
Our target is to process all fatal crashes within one working day of the crash report being received. This target continues to be achieved.
Table 1 - Fatal crashes recorded in CAS, per month (as at1 March 2017)1- Fatal crashes recorded in CAS, per month (as at 31 October 2016)
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Total
2015
23
26
24
28
20
22
26
22
15
31
25
29
291
2016
30
22
25
24
21
23
13
24
22
22
30
26
282
2017
24
10
-
-
-
-
-
-
-
-
-
-
34
Total
77
58
49
52
41
45
39
46
37
53
55
55
607
Injury crashes
Our target is to process all injury crashes (serious and minor injury) within four weeks of the crash report being received.
While there have been some processing delays over the last few months, resourcing has been increased and we are now achieving this target. We expect to continue to achieve this target, and will provide an update if this changes significantly.
While there have been some processing delays over the last few months, resourcing has been increased and we are now achieving this target. We expect to continue to achieve this target, and will provide an update if this changes significantly.
However, as noted in the information on non-injury crashes, we have approximately 21,00022,000 un-processed crash reports. We anticipate that most of these will be non-injury crashes, but we estimate that 2.5% of these may be initiallyany injury crashes incorrectly coded as non-injury andinitially will not be identified as such until the crash is processed.
Table 3 shows that the numbers of injury crashes reported and recorded in CAS in 2016 are lower than those reported for the same months in 2015. We have not yet been able to identify the reason(s) for these lower numbers, although early indications suggest the 2016 injury crash numbers will continue to increase as the processing backlog is cleared. We therefore recommend that some care is taken when using these numbers.
Table 2 - Injury crashes recorded in CAS, per month (as at 1 March 2017)31 October 2016)
JanFebMarAprMayJunJulAugSepOctNovDecTotal
Non-injury crashes
Our target is to process all non-injury crashes within three months of the crash report being received. We are not achieving this target.
The current (March 2017)(November 2016) processing time is approximately eightnine months, and we have approximately 21,00022,000 un-processed crash reports. We anticipate that most of these will be non-injury crashes, but we estimate that 2.5% of these areany injury crashes incorrectly coded initially and will not be identified as such until the crash is processed. Additionalprocessed. Additional resources are addressingbeing recruited to address this backlog, and we expect to achieve our target processing time within the next twelve months.
Table 3 - Non-injury crashes recorded in CAS, per month (as at 1 March 2017)31 October 2016)
JanFebMarAprMayJunJulAugSepOctNovDecTotal
Contact details
If you require more information please contact cas.administrator@nzta.govt.nz