Freedom of information (FOI) releases from LFB

This is a disclosure log of London Fire Brigade's responses to freedom of information (FOI) or environmental information regulations (EIR) requests that might be of wider public interest.

If you can't find the information you're looking for, you can make a new FOI request.

Filters

Clear filters

  • Keywords filters

  • Year filters

  • Month filters

869 disclosures

  1. Animal rescue training

    I would like to request information regarding firefighter training for animal rescues, including: * What training firefighters receive in relation to animal and wildlife rescues * Whether there are specialist teams for such incidents * Any guidance, policies, or operational procedures used during animal rescue incidents

    Published: 13 July 2026

  2. Freedom of Information Request – Fire Incident Dataset

    I would like to request information under the Freedom of Information Act 2000 and, where applicable, the Environmental Information Regulations 2004. We are undertaking analysis of fire incidents across the UK, with a particular interest in emerging fire risks such as solar photovoltaic systems, battery energy storage systems, lithium-ion batteries, electric vehicles, e-bikes, e-scooters, and related technologies. However, we would also like to understand these incidents in the broader context of all recorded fire incidents. Please provide the following information for all fire incidents attended by London Fire Brigade between: 1 January 2017 and 31 December 2025 If 2025 data is incomplete or not yet finalised, please provide the latest available data and indicate the date range covered. ROUTING REQUEST If this request has been sent to the wrong mailbox, please forward it to the appropriate Freedom of Information, Environmental Information Regulations, Information Governance, or Data Protection team within your organisation. If your organisation does not hold the requested information, please confirm this and, where possible, advise which public authority is likely to hold it. Please acknowledge receipt of this request and confirm whether it has been forwarded internally or externally. REQUESTED DATASET Please provide one row per incident, where held, with the following fields: Incident_ID_Pseudonymised Related_Primary_Incident_ID Incident_Link_Type Incident_Date_Time Fire_Category Primary_Fire_Subcategory Property_Type Premises_Type Domestic_or_NonDomestic Motive Cause_Category Source_of_Ignition Item_First_Ignited Main_Item_Responsible_For_Spread Relevant_Technology Subcategory Confirmed_or_Suspected Cause_Role Postcode_Unit LAD_Code Easting_Rounded_1km Northing_Rounded_1km Injuries Fatalities Rescues Evacuations Damage_Extent Number_of_Appliances_Attending Incident_Duration_Minutes FIELD DESCRIPTIONS Please interpret these fields as follows, or provide the closest equivalent fields held in your incident recording system. Incident_ID_Pseudonymised: A non-identifying incident reference. Please do not provide original incident numbers if these are considered sensitive. Related_Primary_Incident_ID: Where held, a pseudonymised identifier linking a secondary fire, reignition, duplicate, or related incident to a primary fire or wider incident. Incident_Link_Type: The relationship between linked incidents, for example secondary linked to primary fire, reignition/repeat attendance, duplicate/merged incident, same event/multi-incident scene, exposure fire/spread from another incident, or not linked. Incident_Date_Time: Date and time of the incident, where disclosable. If exact time is too granular, please provide incident date only, month/year, or a broad time band. Fire_Category: Primary fire, secondary fire, chimney fire, or closest equivalent. Primary_Fire_Subcategory: Dwelling, other building, road vehicle, other outdoor, not applicable, or closest equivalent. Property_Type: Broad property or location type. Premises_Type: More specific premises description, where held. Domestic_or_NonDomestic: Domestic, non-domestic, vehicle, outdoor, or unknown. Motive: Accidental, deliberate, unknown, or closest equivalent. Cause_Category: Broad cause category, as recorded. Source_of_Ignition: Recorded source of ignition, where held. Item_First_Ignited: First item or material ignited, where held. Main_Item_Responsible_For_Spread: Main item responsible for fire spread, where held. Relevant_Technology: Any recorded involvement of solar PV, battery storage, lithium-ion batteries, electric vehicles, e-bikes, e-scooters, mobility scooters, vapes, power banks, power tools, waste/recycling batteries, or other relevant emerging technologies. If none is identified, please mark as "None identified". Subcategory: More specific technology/product/component involved, where relevant. Confirmed_or_Suspected: Whether the technology involvement was confirmed, suspected, mentioned only, not applicable, or unknown. Cause_Role: Whether the technology was the cause of fire, suspected cause, item first ignited, source of ignition, contributing factor, present but not causal, exposed to fire, not applicable, or unknown. Postcode_Unit: Full postcode unit, where disclosure is permitted. LAD_Code: Local Authority District code for the incident location. Easting_Rounded_1km: British National Grid easting rounded to the nearest 1km. Northing_Rounded_1km: British National Grid northing rounded to the nearest 1km. Injuries: Number of recorded injuries. Fatalities: Number of recorded fatalities. Rescues: Number of recorded rescues, where held. Evacuations: Number of people evacuated, where held. Damage_Extent: Recorded extent of fire damage or spread, where held. Number_of_Appliances_Attending: Number of fire appliances attending, where held. Incident_Duration_Minutes: Incident duration in minutes, where held. GEOGRAPHIC INFORMATION For each incident, please provide the most granular geographic identifier that can be disclosed. My preference order is: 1. postcode unit; 2. Local Authority District code; 3. rounded easting and northing coordinates to the nearest 1km. I do not require full addresses, house numbers, street names, occupier names, exact coordinates, names of individuals, original incident numbers, or any other directly identifying personal information. If postcode unit is considered too granular for disclosure, please provide LAD_Code and Easting_Rounded_1km / Northing_Rounded_1km instead. RELEVANT TECHNOLOGY CLASSIFICATION Where your records identify or mention relevant technologies, please classify them using your own recorded categories where available. Technologies of interest include, but are not limited to: Solar PV Battery energy storage system Lithium-ion battery Electric vehicle E-bike E-scooter Mobility scooter Power tool battery Mobile phone / tablet / laptop battery Vape / e-cigarette battery Power bank Waste / recycling battery Industrial battery system Unknown rechargeable battery Other technology None identified Unknown Relevant subcategories may include, where held: Domestic rooftop solar PV Commercial rooftop solar PV Ground-mounted solar PV Solar farm Solar inverter Solar panel / module DC isolator DC cabling / connector Solar PV battery storage Domestic battery energy storage system Commercial battery energy storage system Grid-scale battery energy storage system E-bike battery E-bike charger E-bike conversion kit E-scooter battery E-scooter charger Electric vehicle battery Mobility scooter battery Power tool battery Garden tool battery Laptop battery Mobile phone battery Tablet battery Vape / disposable vape Power bank Battery charger Loose battery cells Battery in waste bin Battery in refuse vehicle Battery at recycling centre Unknown battery product Other Unknown If these are not held as structured fields, please do not manually classify every incident. Instead, please provide any relevant structured cause, source of ignition, item first ignited, and free-text-search-derived indicators that are reasonably retrievable within the statutory cost limit. LINKED INCIDENTS Where an incident is recorded as linked to another incident, please provide a pseudonymised linked incident identifier. In particular, where a secondary fire is recorded as associated with, caused by, or linked to a primary fire, please provide the pseudonymised primary fire incident ID in Related_Primary_Incident_ID. If this linkage is not held in a structured format, please mark the field as "Not held" rather than manually deriving it. FORMAT REQUESTED Please provide the data in CSV or Excel format. If possible, please include a brief data dictionary explaining any local codes or categories used. COST-LIMIT ADVICE If providing incident-level data for all fire incidents would exceed the statutory cost limit, please provide advice and assistance on how the request could be refined. In that case, I would be grateful if you could prioritise one of the following options: 1. provide incident-level data only for incidents involving or mentioning the relevant technologies listed above; and/or 2. provide all other fire incidents in aggregated form by year, LAD code, fire category, property type, motive, cause category, injuries and fatalities; and/or 3. provide a reduced date range, beginning with the most recent complete year of data. Please let me know if any part of the request requires clarification.

    Published: 13 July 2026

  3. Fire Safety Audit Report for Discovery Dock East

    This is a request under the Freedom of Information Act 2000.

    1. Please could you provide the most recent Fire Safety Audit report for Discovery Dock Apartments East, 3 South Quay Square, London, E14 9RZ. 2. Please provide any enforcement notices, alteration notices, or prohibition notices issued in relation to this building from January 2023 to present.

    3. Please provide correspondence held by LFB from January 2023 to present relating to fire safety at this building, including (but not limited to) waking watch measures, fire risk assessments, and external wall systems. 4. Please provide any records held by LFB confirming the external wall system or cladding materials for this building, as referenced in the 2023 Fire Safety Audit report.

    Published: 9 July 2026

  4. Academic Inquiry: Data Precision Loss and Field Interpretations in LFB Open Data

    I am a postgraduate student majoring on Urban Spatial Science in University College London. And I ' m planning to analysis the variability of Fire Responds Time as my theysis. I am writing to seek your professional clarification on a few specific issues I encountered within the London Fire Brigade Incident Records and London Fire Brigade Mobilisation Records datasets which were published in LONDON DATASTORE. 1. Systematic Loss of Second-Precision Since 2021 * Within the London Fire Brigade Mobilisation Records open database, I noticed a significant change in data precision. * In the files LFB Mobilisation data from 2021 - 2024 and LFB Mobilisation data 2025 onwards.xlsx, the chronological columns (DateAndTimeMobilised, DateAndTimeMobile, DateAndTimeArrived, DateAndTimeLeft, and DateAndTimeReturned) have lost their second-level precision. * The seconds component for all these timestamps is showing as 00 and automatically rounding up to the nearest minute. Compared to the 2009–2020 datasets, this represents a noticeable loss of granularity. * I suspect this truncation might be an unintended artifact introduced when internal files were compiled or converted into CSV format, as spreadsheet-to-CSV pipelines often drop second-level formats by default. * Could your team please provide the original high-precision .xlsx data for 2021–2024 and 2025 onwards? If this change was intentional due to updated privacy or information governance policies, is there an option for me to formally apply for the precision data under an NDA for academic purposes? 2. Interpretations of Historical vs. Contemporary Timestamps * My study relies on the public response time data from both London Fire Brigade Incident Records and London Fire Brigade Mobilisation Records. * I would like to confirm if the TimeOfCall column in the Incident Records and the DateAndTimeMobilised column in the Mobilisation Records represent different operational stages. * In records spanning 2009–2015, I observed a distinct time gap between TimeOfCall and DateAndTimeMobilised for the same IncidentNumber. I interpreted this gap as the interval between the control room receiving the call and dispatching the station. By combining this gap with TurnoutTimeSeconds and TravelTimeSeconds from the Mobilisation records, so I could calculate a comprehensive response time including call-handling duration. * However, starting from 2016, TimeOfCall and DateAndTimeMobilised become virtually identical, with only a 0 or 1-second difference in a small number of cases. * Did an operational system upgrade after 2016 enable instant dispatching to achieve this near-zero delay? Or was the exact timestamp gap masked for privacy reasons? If it is due to privacy, is it possible to apply to see the original exact gaps for post-2016 data? 3. Data Discrepancies and Mismatch Rows * While performing data linkage via IncidentNumber, I found a minor row mismatch between the two databases. * There are 777 instances in the Incident Records where pumping appliances were deployed, but their IncidentNumber cannot be found or matched in the Mobilisation records. * Conversely, there are 7,980 vehicle deployment logs in the Mobilisation records whose IncidentNumber cannot be matched to any master row in the Incident Records. * Although this discrepancy is very small relative to millions of historical records, I would appreciate it if you could briefly explain the operational or database logging reasons behind these unmatched entries. 4. Discrepancies Between Administrative and Physical First Arrival Times * When executing the dataset match, I cross-referenced the FirstPumpArriving_AttendanceTime column (Incident Records) with the minimum value of AttendanceTimeSeconds across all deployed pumps for the exact same IncidentNumber (Mobilisation records). * I discovered 8,820 instances where these two values do not match. * Does this discrepancy occur because FirstPumpArriving_AttendanceTime represents the time for the appliance that was designated/dispatched first, but due to real-time road conditions or different travel distances, a secondary or subsequent appliance actually arrived at the scene physically earliest? Thank you very much for your time, support, and continuous dedication to maintaining this vital public data resource. I look forward to your professional insights.

    Published: 9 July 2026

  5. Freedom of Information request - Number of fire lifts notified as being out of service i

    Under the FOIA 2000, I would like to know the following: How many fire lifts across all London Boroughs have been reported as being out of service for more than 24 hours in residential buildings in accordance with The Fire Safety (England) Regulations 2022? The average length of the fire lifts being out of service? London Fire Brigades policy on the use of fire lifts during fires in residential buildings.

    Published: 9 July 2026

  6. Freedom of Information Request – Fires in Hospitals Involving Lithium-Ion Battery Products

    Under the Freedom of Information Act 2000, I would like to request information relating to fires involving e-bikes, e-scooters or other lithium-ion battery powered products within hospital premises attended by the London Fire Brigade. Please provide the following information for the last three calendar years (including the current year to date if possible): 1. The total number of incidents attended by the London Fire Brigade involving: * e-bikes * e-scooters * lithium-ion battery powered products where the incident occurred within: * hospitals * NHS premises * healthcare facilities within the London Fire Brigade area. 1. For each incident, where available, please provide: * the date of the incident * the borough/location * the type of premises involved * the type of product involved (if recorded) * whether the product was charging at the time of the fire (if recorded) 1. Please provide the total number of: * fatalities * injuries associated with these incidents. 1. Please confirm whether the London Fire Brigade has issued any operational guidance, recommendations, alerts or correspondence to hospitals or NHS Trusts regarding risks associated with e-bikes, e-scooters or lithium-ion battery products within hospital buildings during this period. 2. Please provide copies of any general guidance, policy documents or fire safety advice issued by the London Fire Brigade relating specifically to lithium-ion battery risks within healthcare settings. If any part of this request is considered too broad or likely to exceed the cost limit, please advise how the scope may be refined. I would prefer the information in electronic format where possible. Thank you for your time and assistance.

    Published: 9 July 2026

  7. Number of chlorine gas/chemical incidents in leisure facilities since 2020

    The number of chlorine/chemical incidents attended in leisure facilities: Clarified as:

    1. ‘Chlorine incident’ - most incidents will normally have a chemical mix creating chlorine gas, but if chemical mix incidents makes it easier for you to get the information

    2. 2020 to date please.

    3. Public leisure facilities and privately run spa facilities please.

    Published: 8 July 2026

  8. FOI request- contracts

    I would like to make a freedom of information request. I am doing a research project investigating call-off contracts in the public sector. I have identified two potential call-off contracts awarded by London Fire Brigade, but I can't find details of the framework agreements they were awarded from, or which lots were used. I have attached an Excel file that contains the information I am looking at. The last two columns ("Title of framework used" and "Further framework info") is where I am missing information. Please could you provide the name of the specific framework agreement or DPS/Dynamic Market used here, as well as the lot used if the framework was divided into lots. If there is any further info which you think would help me locate the framework agreements (e.g., a link to the framework's Contract Finder or FTS listing, the framework provider, or a widely-used reference number such as CCS's RM codes), please use the final column for this. Please use the second column for the relevant lot information. Please note that I have identified these contracts as possible call-off contracts, so some of them might not be. Some could be, for instance, procured directly (without being called off from a framework agreement), or could be themselves notices of the establishment of a framework agreement. Therefore I would kindly ask you to specify in these incidences what kind of procurement was used in the "Title of framework used" column.

    Published: 8 July 2026

  9. Non-fault Accidents

    We shall be pleased if you will advise us the amount paid to repair vehicles in relation to non-fault accidents occurring within the following period and the amounts recovered from third parties. 01/01/23 to 31/12/23 01/01/24 to 31/12/24.

    Published: 7 July 2026

  10. Wildfire response vehicles

    1. Are wildfire response vehicles MDT equipped,what Comms equipment do they have? 2. Handheld main scheme radios make and model?

    Published: 7 July 2026