伊人直播

Publishing Incident Recording System data on the fire and rescue service at an incident level:

Frequency of release: Annual

First publication: 30 January 2020

Latest update: 25 July 2024

Forthcoming releases: Home Office statistics release calendar

Home Office responsible statistician: Helene Clark

Press enquiries: pressoffice@homeoffice.gov.uk

Telephone: 0300 123 3535

Public enquiries: firestatistics@homeoffice.gov.uk

1. Background

Data quality

Incident records in the Incident Recording System (IRS) are the responsibility of, and quality assured by, fire and rescue services (FRSs). The Home Office and the FRSs are working on improving the data within the IRS and reducing possible inconsistencies. Having said that, the IRS was not designed with record level datasets in mind so we are aware of some possible inconsistencies and there may well be other issues.

IRS incident records are a judgement call of the lead fire officer at the time of the incident. The quality of the information provided by fire and rescue services is variable and its accuracy cannot be guaranteed, especially at a record level. For instance, some records involve estimation by those in attendance.

Dataset rationale

The Home Office has received requests from users of non-fire incident level datasets to complete the suite of this type of incident. Users can achieve this by combining the data from the 鈥淣on-fire incidents: medical and collaborating incidents鈥�, 鈥淣on-fire incidents: other non-fire incidents鈥� and 鈥淣on-fire incidents: road traffic collisions鈥� incident level datasets.

The non-fire incident datasets 鈥渇looding and water rescue incidents鈥�, 鈥渁nimal assistance鈥� and 鈥渂ariatric assistance鈥� give more specific detailed information on these incidents.

The Home Office has, and will continue to, engage with stakeholders, such as statistical users and FRSs, to gauge opinion on the most useful datasets to publish.

Dataset definition

The road traffic collisions dataset covers non-fire incidents attended by FRSs in England that they defined as 鈥渞oad traffic collisions鈥�. Incidents that are road vehicle fires are not included. The Home Office only has jurisdiction for fire policy in England and therefore has published incident data for England only.

The data in this dataset is consistent with records that reached the IRS by 15 May 2024.

---

2. Variable by variable - scene setting

The fire and rescue service (FRS) in which the incident took place, not necessarily the FRS which responded. Occasionally an FRS will respond to an incident 鈥渙ver the border鈥�, and because of this users should be careful about making general comments about particular FRSs as some incidents may have been attended by other FRSs. This dataset only covers incidents that took place in England.

Due to data protection issues, and in line with other datasets, we have merged Isles of Scilly data with Cornwall, as the number of road traffic collisions attended by the FRS in Isles of Scilly is minimal [there were 3 between the financial year 2012 to 2013 and the financial year 2023 to 2024.

Figures for Dorset and Wiltshire, who merged into one FRS on 1 April 2016, are presented merged.

Figures for Hampshire and Isle of Wight, who merged into one FRS on 1 April 2021, are presented merged.

The standard National Statistics code (E Code) of the fire and rescue service (FRS) in FRS_TERRITORY. In this case the code for Cornwall has been used for the Cornwall and Isles of Scilly combined FRS.

A financial year runs from 1 April to 31 March. Record level information is published from the financial year 2012 to 2013; although the IRS began in April 2009, road traffic collision incidents are not available in a consistent manner until this point. Incidents are allocated to a financial year depending on the time of the call, which is usually collected through automatic systems. For example, an incident where the call was made at 23.59 on 31 March 2013 but the incident was closed at 01.34 on 1 April 2013 would be allocated to the financial year 2012 to 2013 not the financial year 2013 to 2014.

A calendar year runs from 1 January to 31 December. Record level information is published from the financial year 2012 to 2013; although the IRS began in April 2009, road traffic collisions are not available in a consistent manner until this point. Incidents are allocated to calendar year depending on the time of the call, which is usually collected through automatic systems. For example, an incident where the call was made at 23.59 on 31 December 2012 but the incident was closed at 01.34 on 1 January 2013 would be allocated to 2012 not 2013. It should be noted that figures for 2012 will be lower because only records from 1 April 2012 are included in the dataset - this is also true of the latest financial year published.

The month the incident took place. This would return 鈥淒ecember鈥� for 25 December 2015.

Because the month variable is not in chronological order when sorted, this code has been added. Month 1 is January, month 2 is February, for instance. This would return 鈥�12鈥� for 25 December 2015.

The day of the month the incident took place, this would return 鈥�25鈥� for 25 December 2015.

The date the incident took place. This would return 鈥�25/12/2015鈥� for 25 December 2015.

The day of the week (for example, Monday) the incident took place. This would return 鈥淔riday鈥� for 25 December 2015.

---

3. Variable by variable - situation

Incidents are categorised into one of the 4 following locations - dwelling, other building, road vehicle or outdoors.

4. Variable by variable - the incident

Incidents are categorised into one of these 9 types:

1. Extrication of person(s)
2. Release of persons(s)
3. Make vehicle safe
4. Make scene safe
5. Wash down road
6. Medical assistance only
7. Advice only
8. Stand by - no action
9. Other

The number of extrications from the incident recorded as 鈥淒ashboard Roll鈥�.

Information on the type of extrication method for around 100 incidents from the financial year 2012 to 2013 to the financial year 2020 to 2021 for Road Traffic Collisions is believed to have circumvented quality assurance checks in the Incident Recording System. Therefore, the number of these 鈥淒ashboard Roll鈥� incidents have been recorded as N/A.

The number of extrications from the incident recorded as 鈥淩oof removal鈥�.

Information on the type of extrication method for around 100 incidents from the financial year 2012 to 2013 to the financial year 2020 to 2021 for Road Traffic Collisions is believed to have circumvented quality assurance checks in the Incident Recording System. Therefore, the number of these 鈥淩oof removal鈥� incidents have been recorded as N/A.

The number of extrications from the incident recorded as 鈥淩oof flap (vehicle on side)鈥�.

Information on the type of extrication method for around 100 incidents from the financial year 2012 to 2013 to the financial year 2020 to 2021 for Road Traffic Collisions is believed to have circumvented quality assurance checks in the Incident Recording System. Therefore, the number of these 鈥淩oof flap (vehicle on side)鈥� incidents have been recorded as N/A.

The number of extrications from the incident recorded as 鈥淏 Post Rip鈥�. This involves the B post, which is the dividing post between the front and rear doors of a car, being cut to remove it from the structure of the car to allow safe access a casualty inside.

Information on the type of extrication method for around 100 incidents from the financial year 2012 to 2013 to the financial year 2020 to 2021 for Road Traffic Collisions is believed to have circumvented quality assurance checks in the Incident Recording System. Therefore, the number of these 鈥淏 Post Rip鈥� incidents have been recorded as N/A.

The number of extrications from the incident recorded as 鈥淪ide removal (vehicle on roof鈥�.

Information on the type of extrication method for around 100 incidents from the financial year 2012 to 2013 to the financial year 2020 to 2021 for Road Traffic Collisions is believed to have circumvented quality assurance checks in the Incident Recording System. Therefore, the number of these 鈥淪ide removal (vehicle on roof)鈥� incidents have been recorded as N/A.

The number of extrications from the incident recorded as 鈥淥ther space creation鈥�.

Information on the type of extrication method for around 100 incidents from the financial year 2012 to 2013 to the financial year 2020 to 2021 for Road Traffic Collisions is believed to have circumvented quality assurance checks in the Incident Recording System. Therefore, the number of these 鈥淥ther space creation鈥� incidents have been recorded as N/A.

---

5. Variable by variable - resourcing

The total number of FRS vehicles that attended the incident. This includes all types of vehicle, for example hazardous materials units, fire boats and canteen vans would be included in this total. Large numbers are grouped for ease of use and to reduce the personal data risk of incidents being matched across datasets. For example, there is likely to be few incidents attended by 47 vehicles and this could be matched to other datasets containing this variable but grouping these in the 鈥�15 or more鈥� grouping makes this impossible.

Because some of the options in the vehicles variable contains letters (for example, 15 or more) this code has been added after feedback from users to aid analysis. 99 is used for 鈥渄on鈥檛 know鈥�.

The number of FRS personnel that attended the incident on fire service appliances or by other means (for example, their own vehicle, on foot). Large numbers of personnel are grouped for ease of use and to reduce the personal data risk of incidents being matched across datasets. For example, there are likely to be few incidents attended by 147 officers and this could be matched to other datasets containing this variable but grouping these in the 鈥�40 or more鈥� grouping makes this impossible.

Because some of the options in the personnel variable contains letters (for example,. 40 or more) this code has been added after feedback from users to aid analysis. 99 is used for 鈥渄on鈥檛 know鈥�.

The time of the call is defined as when first call was received to Command and Control. If the call was received by one FRS and relayed to another, then the time of the call to the first FRS is used. Both of these variables are usually collected through automatic systems.

Because all of the options in the response time variable contains letters (for example, 1 to 2 mins) this code has been added after feedback from users to aid analysis. 99 is used for 鈥渄on鈥檛 know鈥�.

An incident is closed when the last FRS appliance, vehicle or officer left the scene of the incident. Both of these variables are usually collected through automatic systems.

Because all of the options in the time at scene variable contains letters (for example, 0 to 15 mins) this code has been added after feedback from users to aid analysis.

---

6. Variable by variable - outcomes

This records whether the incident involved at least one fatality or one casualty from the incident. Due to data protection considerations no more detailed information on casualties and fatalities is given.

To be consistent with published statistics, the variable combines all 鈥渇atalities鈥� and all 鈥渘on-fatal casualties鈥�.

Casualties include those with injuries requiring hospital attention, those requiring first aid at the scene and those given advice to have precautionary checks (whether they then take that advice or not).