Fire alarm caused by burnt food at Lagoon Avenue, Minneapolis MN
Please note:
This is not an official report. The headline and summary are generated by automated AI systems from public-safety dispatch audio. Always verify with official sources.
Fire & ArsonAs discussed during the dispatch call, fire crews responded to a commercial fire alarm near Lagoon Avenue in Minneapolis. Upon arrival, they found a three-story apartment building with no visible fire. Investigation determined the alarm was caused by burnt food. Engine 22 handled the incident while other units returned to service.
Audio|Heard on: Hennepin MN Fire Dispatch Group Calls
Listen to dispatch call
01:29
Transcript:
00:00
Initial assignment commercial fire alarm, due in.
00:03
Engine eight, engine 22, rescue one, chief one.
00:07
Near Lagoon Avenue.
00:09
Initial assignment commercial fire alarm, due in.
00:13
Engine eight, engine 22.
00:14
Rescue one, chief one.
00:16
Near Lagoon Avenue.
00:18
General fire alarm called in from an alarm company.
00:25
Ladder ten dispatch.
00:26
Fire set.
00:27
We did a callback.
00:36
Initial assignment en route for commercial fire alarm, near Lagoon Avenue.
00:43
Ladder ten arrived near Penn.
00:52
Dispatch, Engine 22 arrives near Lagoon.
00:56
We have a three-story apartment building, nothing showing.
00:59
Engine 22 has command and checking three-story apartment building, command.
01:04
Nothing showing and checking at 1540.
01:07
A house arriving on Lagoon.
01:10
Received, a house arriving at 1540.
01:15
Command on Lagoon.
01:17
This was burnt food.
01:25
Confirmed burnt food.
01:26
Engine 22 will handle.
01:27
Rest of the companies back in service at 1541.
Disclaimer:
This transcript is automatically generated by AI from live dispatch audio. Dispatch communications may include background noise, overlapping speakers, or rapidly evolving situations, and automated transcription may not capture all details or context.
Location mentioned:
Lagoon Ave, Minneapolis, MN 55408
This shows a Google Street View of the area near the location, which might not be the exact address.
Correct
Incorrect
Note:
Auto-generated from live dispatch audio, which may contain errors. Dispatch calls are not confirmed incidents. Always verify with official sources.
