|
November 2007
Nov 2 - 5:01 am
(Incident #290) - Report of a smoke condition at
a private residence. It was determined that the oil furnace "back-fired"
creating a light smoke condition.
Nov 3 - 10:31 pm
(Incident #291) - Report of a fire alarm
sounding at a two-family dwelling. It was determined that dead/dying
batteries in a detector was the cause for the alarm activation.
Nov 4 - 11:53 am
(Incident #292) - Request for the FD to assist
at the scene of a motor vehicle crash. Fire crews stabilized the vehicles
to facilitate victim removal by EMS personal.
Nov 5 - 4:54 pm
(Incident #293) - Fire alarm activation at an
apartment complex. It was determined that a portion of a sprinkler pipe
ruptured causing a water leak to the third floor laundry room.
Nov 6 - 5:35 am
(Incident #294) - Fire alarm activation at a
mixed-use commercial/residential property in the central business
district. It was determined that water leaking through a smoke detector
was the cause for the alarm activation.
Nov 7 - 2:31 pm
(Incident #295) - Fire alarm activation at an
apartment complex. It was determined that sprinkler contractors were
performing repairs and were the cause for the alarm activation.
Nov 7 - 4:30 pm
(Incident #296) - Fire alarm activation at an
apartment complex. It was determined that recent repairs were the cause
for the alarm activation.
Nov 8 - 8:17 am
(Incident #297) - Fire alarm activation at a
private residence. An apparent alarm malfunction was the cause for the
alarm activation.
Nov 9 - 2:14 pm
(Incident #298) - Carbon monoxide alarm
activation at a private residence. Fire crews used a meter to check air
quality. Elevated levels of carbon monoxide were present. The local
utility company was requested to respond.
Nov 9 - 3:42 pm
(Incident #299) - Fire alarm activation and
report of a fire at a senior residential complex. A fire, which was
discovered by maintenance personal, was found burning behind a wall in the
laundry room. A failed electrical outlet caused the fire. The fire was
promptly extinguished by fire crews and maintenance personal.
Nov 12 - 9:29 am
(Incident #300) - Report of an odor of natural
gas at a fraternal organization building. It was determined that a pilot
light on the range top was extinguished and allowed small quantities of
natural gas to escape.
Nov 12 - 6:26 pm
(Incident #301) - Report of a possible oven fire
at a private residence. It was determined that the oven was inadvertently
placed into the self-cleaning mode causing it to heat and smoke
excessively.
Nov 12 - 8:23 pm
(Incident #302) - Fire alarm activation at an
eating establishment in the central business district. A smoke detector in
a heating duct was activated when the establishment started their heat for
the first time this season. management silenced the alarm and failed to
evacuate patrons.
Nov 14 - 6:56 pm
(Incident #303) - Request to the Borough of
Hillsdale to assist their FD with a large natural gas leak at an
educational facility.
Nov 15 - 10:20
am (Incident #304) - Request to the Borough of
Hillsdale to assist their FD with a large natural gas leak at an
educational facility.
Nov 16 - 6:15 pm
(Incident #305) - Report of a natural gas leak
at a sports club facility in the central business district. It was
determined that a pressure relief valve at the exterior meter released a
small quantity of gas.
Nov 17 - 3:15 pm
(Incident #306) - Fire alarm activation at a
mixed-use retail/residential building in the central business district.
Burned food on the stove was the cause for the alarm activation.
Nov 20 - 5:15 pm
(Incident #307) - Report of a gas leak at a
private residence. It was determined that a child inadvertently turned the
stove on without getting proper ignition. Fire crews used large fans to
ventilate the residence.
Nov 23 - 3:48 pm
(Incident #308) - Report of a smoke detector
activation at a private residence. An apparent system malfunction was the
cause for the alarm activation.
Nov 23 - 5:05 pm
(Incident #309) - Fire alarm activation at a
mixed-use residential/commercial building in the central business
district. It was determined that a microwave oven, with food products
inside, was inadvertently turned-on for an unspecified period of time
creating a smoke condition and activating the fire alarm system.
Nov 25 - 7:15 pm
(Incident #310) - Report by a plumbing
contractor of elevated levels of carbon monoxide at a private residence.
Fire crews used a meter to check air quality. Due to the fact that the
plumber secured the furnace and opened doors and windows, there were no
elevated levels of carbon monoxide detected. The local utility company was
requested to respond.
Nov 27 - 5:16 am
(Incident #311) - Report of an electrical switch
smoking at a private residence. Fire crews removed the switch and secured
the wires. It was recommended that the homeowner contact an electrical
contractor.
Nov 28 - 12:10
pm (Incident #312) - Report of a smoke condition
at a retail establishment in the central business district. It was
determined that a fluorescent light fixture ballast had failed creating a
burning odor and smoke condition. Fire crews secured the power to the
fixture, removed it from the ceiling and verified that there was no fire
extension to surrounding materials or structural components.
Nov 30 - 3:35 pm
(Incident #313) - Report of an odor of natural
gas at a mixed-use commercial/residential building in the central business
district. It was determined that a gas pipe outside the building was
damaged allowing the flow of gas. The local utility company was requested
and responded.
October 2007
Oct 2 - 8:11 am
(Incident #272) - Request for the FD at the
scene of a motor vehicle crash. Fire crews used extrication tools to
remove car doors to facilitate victim removal by EMS personal.
Oct 3 - 8:42 am
(Incident #273) - Report of an odor of propane
coming from an eating establishment. After a thorough search of the eatery
and adjoining businesses, it was determined that a malfunctioning stove
was the cause for the leak.
Oct 3 - 2:02 pm
(Incident #274) - Report of a vehicle leaking
gasoline in a parking lot. It was determined that a single vehicle had
leaked a small quantity of gasoline. The owner was advised and was to have
the vehicle towed to a repair facility.
Oct 5 - 1:21 pm
(Incident #275) - Request for the FD at the
scene of a motor vehicle crash. Fire crews stabilized the vehicles and
assisted EMS crews.
Oct 7 - 4:21 pm
(Incident #276) - Report of a water leak at a
business establishment. Fire crews secured the source of the leak and
advised the tenant to contact the building owner and a plumbing
contractor.
Oct 9 - 11:43 am
(Incident #277) - Report of a carbon monoxide
alarm sounding at a private residence. Fire crews used a meter to check
air quality. There were no elevated levels of carbon monoxide detected.
Oct 10 - 4:17 pm
(Incident #278) - Fire alarm activation at a
pre-school. It was determined that a young child inadvertently activated a
fire alarm pull station.
Oct 13 - 7:46 pm
(Incident #279) - Report of a smoke detector
activation at a private residence. No further information available.
Oct 16 - 10:10
pm (Incident #280) - Report of a carbon monoxide
alarm sounding at a private residence. Fire crews used a meter to check
air quality. Slightly elevated levels of carbon monoxide were detected.
The local utility company was requested and responded.
Oct 17 - 9:00 pm
(Incident #281) - Report of a carbon monoxide
alarm sounding at a private residence. Fire crews used a meter to check
air quality. Slightly elevated levels of carbon monoxide were detected.
The local utility company was requested and responded.
Oct 19 - 3:43 pm
(Incident #282) - Report of a carbon monoxide
alarm sounding at a private residence. Fire crews used a meter to check
air quality. There were no elevated levels of carbon monoxide present.
Oct 21 - 10:22
pm (Incident #283) - Fire alarm activation at a
medical facility. After a thorough search of the building, no apparent
cause for the alarm activation could be determined.
Oct 26 - 4:01 pm
(Incident #284) - Fire alarm activation at an
apartment complex. It was determined that alarm contractors, working on
the system, were the cause for the activation.
Oct 26 - 10:41
pm (Incident #285) - Request for the FD to
stand-by at the scene of a downed power line.
Oct 28 - 3:50 am
(Incident #286) - Fire alarm activation at an
educational facility. After a thorough search of the building, no apparent
cause for the alarm activation could be determined.
Oct 29 - 1:13 am
(Incident #287) - Report of a motor buzzing at
an apartment complex. It was determined that a tenant, annoyed by the
buzzing noise and getting no satisfaction from building management, called
the FD for help.
Oct 29 - 6:45 pm
(Incident #288) - Fire alarm activation at a
private residence. It was determined that cooking smoke was the cause for
the alarm activation.
Oct 31 - 4:00 pm
(Incident #289) - Report of an odor of natural
gas at a private residence. It was determined that a removed gas clothes
dryer was the cause for the leak.
September 2007
Sep 3 - 2:55 am
(Incident #248) - Report of smoke detectors
sounding at a private residence. After a thorough search of the premises,
no apparent cause for the sounding alarm could be determined.
Sep 3 - 3:05 pm
(Incident #249) - Request for the fire
department at the scene of a motor vehicle crash. Fire crews stabilized
the vehicle and disconnected the battery to ensure scene safety.
Sep 5 - 8:19 pm
(Incident #250) - Report of a carbon monoxide
detector sounding at a private residence. Fire crews used a meter to check
air quality. There were no elevated levels of carbon monoxide present.
Sep 6 - 7:50 pm
(Incident #251) - Report of a possible fire at a
private residence. Fire crews encountered a light smoke condition in a
bedroom and used the thermal imaging camera to locate the source of fire.
It was determined that a wet item of clothing was dripping onto an
extension cord plug which shorted out and began to melt prior to the
circuit breaker tripping.
Sep 7 - 11:12 pm
(Incident #252) - Fire alarm activation at a
borough-owned building. Dust in an HVAC duct was the cause for the alarm
activation.
Sep 8 - 11:48 am
(Incident #253) - Report of a smoldering fire in
landscape mulch at an apartment complex. Fire crews used water
extinguishers to extinguish a small fire.
Sep 8 - 12:07 pm
(Incident #254) - Report of a fire alarm
sounding at a house of worship. It was determined that a pot on the stove,
used for melting candle wax, had been left unattended.
Sep 8 - 9:58 pm
(Incident #255) - Fire alarm activation at a
borough-owned building. Dust in an HVAC duct was the cause for the alarm
activation.
Sep 10 - 5:54 am
(Incident #256) - Fire alarm activation at a
borough-owned building. Dust in an HVAC duct was the cause for the alarm
activation.
Sep 11 - 12:04
pm (Incident #257) - Report of a burning odor in
the rear of a store in the central business district. It was determined
that an adjacent store had spilled some material onto a stove causing the
burning odor.
Sep 13 - 9:56 am
(Incident #258) - Fire alarm activation at an
apartment complex. It was determined that the motor to an overloaded
washing machine had overheated causing a smoke condition.
Sep 14 - 11:05
am (Incident #259) - Request for the fire
department at the scene of a motor vehicle crash involving a motor cycle
which was leaking gasoline.
Sep 14 - 12:48
pm (Incident #260) - Report of a carbon monoxide
detector sounding at a private residence. Fire crews used a meter to check
air quality. There were no elevated levels of carbon monoxide detected. A
dead/dying battery in the detector was the apparent cause for the alarm.
Sep 16 - 9:00 pm
(Incident #261) - Report of a trash receptacle
fire adjacent to the railroad tracks in the central business district.
Fire crews promptly extinguished the fire, the cause of which was
determined to be suspicious.
Sep 17 - 9:30 am
(Incident #262) - Fire alarm activation at a
private residence. It was determined that an alarm contractor was the
inadvertent cause for the alarm activation.
Sep 17 - 11:07
am (Incident #263) - Fire alarm activation at a
senior care residence. It was determined that smoke from unattended
popcorn in a microwave was the cause for the alarm activation.
Sep 17 - 6:07 pm
(Incident #264) - Report of smoke detectors
sounding at an apartment complex. An apparent malfunction of the system
was the cause for the activation.
Sep 18 - 3:19 am
(Incident #265) - Report of smoke detectors
sounding at an apartment complex. An apparent malfunction of the system
was the cause for the activation.
Sep 19 - 9:58 pm
(Incident #266) - Fire alarm activation at an
eating establishment in the central business district. The activation was
due to excessive steam.
Sep 22 - 2:18 pm
(Incident #267) - Request for the fire
department to stand-by at the scene of a downed power line. The local
utility company was requested and responded.
Sep 22 - 8:00 pm
(Incident #268) - Report of a fire alarm
sounding at a business office in the central business district. After a
thorough search of the building, no apparent cause for the alarm could be
determined.
Sep 27 - 11:25
am (Incident #269) - Report of a person trapped
inside a stalled elevator at a medical office building. Fire crews secured
the elevator car and safely removed the trapped victim who was uninjured.
Sep 27 - 11:40
pm (Incident #270) - Fire alarm activation at a
bank in the central business district. It was determined that an apparent
alarm malfunction was the cause for the activation.
Sep 28 - 2:29
am (Incident #271) - Fire alarm activation at a
bank in the central business district. It was determined that an apparent
alarm malfunction was the cause for the activation.
August 2007
Aug 1 - 10:34 am
(Incident #222) - Report of an electrical panel
arcing/sparking at a department store. No dangerous conditions were found
by fire officers. Management requested an electrician respond.
Aug 3 - 10:30 am
(Incident #223) - Report of an unknown type odor
in a department store. After a thorough search of the building, no cause
for the odor could be determined.
Aug 3 - 9:23 pm
(Incident #224) - Request for the fire
department to stand-by for downed power lines due to a passing storm.
Aug 4 - 4:20 pm
(Incident #225) - Fire alarm activation at an
assembly occupancy. It was determined that water from a leaking roof
dripped through a smoke detector causing the alarm activation.
Aug 4 - 5:40 pm
(Incident #226) - Report of a power line
arcing/sparking where contacting tree branches. Fire crews stood by and
awaited the local utility companies response.
Aug 6 - 2:51 pm
(Incident #227) - Fire alarm activation at a
religious educational facility. It was determined that a contractor was
the cause for the alarm activation.
Aug 7 - 7:17 am
(Incident #228) - Fire alarm activation at a
mixed-use commercial/residential building in the central business
district. It was determined that steam from a shower was the cause for the
alarm activation.
Aug 7 - 1:44 pm
(Incident #229) - Fire alarm activation at a
private residence. It was determined that dust from a renovation
contractor was the cause for the alarm activation.
Aug 9 - 8:27 am
(Incident #230) - Fire alarm activation at a
private residence. It was determined that cooking smoke was the cause for
the alarm activation.
Aug 9 - 10:52 am
(Incident #231) - Fire alarm activation at a
private residence. It was determined that dust from a renovation
contractor was the cause for the alarm activation.
Aug 10 - 10:49
am (Incident #232) - Fire alarm activation at a
mixed-use commercial/residential building in the central business
district. It was determined that dust from a renovation contractor was the
cause for the alarm activation.
Aug 11 - 7:52 pm
(Incident #233) - Request for the fire
department at the scene of a motor vehicle crash. Fire crews were no
longer needed and were cancelled en route.
Aug 11 - 11:17
pm (Incident #234) - Report of a fire alarm
sounding at a private residence. After a thorough search, no apparent
cause for the alarm activation could be determined.
Aug 12 - 10:44
am (Incident #235) - Report of a pick-up truck
fire in front of a private residence. Upon arrival of fire units, the
small fire had been extinguished.
Aug 15 - 8:35 am
(Incident #236) - Fire alarm activation at a
medical office. It was determined that renovation contractors were the
cause for the alarm activation.
Aug 17 - 3:34 am
(Incident #237) - Report of a burning odor
inside a private residence. It was determined that an electrical short
occurred within the refrigerator, creating the burning odor.
Aug 17 - 3:54 am
(Incident #238) - Report of a smoke detector
sounding in an individual dwelling unit at an apartment complex. Upon
arrival of fire crews, the detector was sounding "warning - low battery".
The building superintendent was advised to change the battery.
Aug 19 - 9:24 pm
(Incident #239) - Report of a carbon monoxide
detector sounding in an individual dwelling unit at an apartment complex.
It was determined that a lack of detector maintenance was the cause for
the alarm activation.
Aug 23 - 10:13
am (Incident #240) - Request for the fire
department rescue crew for a pedestrian pinned underneath a motor vehicle.
Fire crews used air bags and jacks to lift the vehicle off of the victim,
who was transported to a trauma center with life-threatening injuries.
Aug 24 - 6:04 am
(Incident #241) - Fire alarm activation at a
medical facility. After a thorough search of the building, no apparent
cause for the alarm activation could be determined.
Aug 25 - 10:12
am (Incident #242) - Fire alarm activation at a
private residence. After a thorough search of the residence, no apparent
cause for the detector activation could be determined.
Aug 25 - 10:49
am (Incident #243) - Fire alarm activation at a
residential care facility for the developmentally disabled. It was
determined that excessive cooking smoke was the cause for the alarm
activation.
Aug 25 - 8:10 pm
(Incident #244) - Smoke detector activation at a
private residence. It was determined that an apparent detector malfunction
was the cause for the activation.
Aug 26 - 11:09
pm (Incident #245) - Request for the fire
department for persons trapped in a stalled elevator at a medical
facility. Maintenance staff immediately freed the entrapped persons and
the fire department was cancelled prior to responding.
Aug 27 - 7:36 am
(Incident #246) - Fire alarm activation in a
mechanical room at the rear of a strip mall. It was determined that a
telephone dialer line had malfunctioned transmitting the alarm.
Aug 28 - 10:52
am (Incident #247) - Fire alarm activation at a
mixed-use residential/commercial building in the central business
district. It was determined that a fire sprinkler contractor was on site
performing a system inspection and the alarm was inadvertently
transmitted.
July 2007
July 1 - 6:05 am (Incident #197) -
Report of a fire alarm sounding at an apartment complex. Upon arrival, it
was determined that there was a confirmed fire in an oven in a dwelling
unit. Fire crews safely evacuated all affected tenant's and the fire was
promptly extinguished.
July 2 - 1:57 am (Incident #198) -
Report of smoke detectors sounding at a private residence. An apparent
alarm malfunction was the cause for the alarm activation.
July 2 - 8:32 pm (Incident #199) -
Report of an odor of natural gas at a commercial building in the central
business district. It was determined that the odor was a fan belt burning
on a compressor to an HVAC unit on the side of the building.
July 3 - 2:30 pm (Incident #200) -
Report of a fire alarm sounding at a public school. After a thorough
search of the building, it was determined that the alarm activation was
due to a malfunction.
July 3 - 3:57 pm (Incident #201) -
Fire alarm activation at a condominium complex. It was determined that
dust from a repair contractor was the cause for the alarm activation.
July 4 - 3:30 am (Incident #202) -
Request for the fire department to the Borough of Emerson for mutual aid
assistance at a fire in a private residence. Fire crews assisted Emerson
FD with extinguishment, salvage and overhaul.
July 5 - 9:41 am (Incident #203) -
Report of a fire alarm sounding at a public school. It was determined that
an alarm contractor was on site performing testing on the system and
failed to notify central dispatch.
July 7 - 6:24 pm (Incident #204) -
Report of a brush fire in a wooded area at a county park facility. Fire
crews used several water extinguishers to put out a small fire.
July 9 - 10:50 am (Incident #205) -
Fire alarm activation at a series of commercial occupancies. After a brief
investigation, it was determined that an apparent alarm malfunction was
the cause of the activation.
July 9 - 8:48 pm (Incident #206) -
Report of a power line arcing/sparking on top of a utility pole in front
of a private residence. The local utility company was requested to
respond.
July 10 - 12:27 am (Incident #207) -
Fire alarm activation at a private residence. After a thorough search of
the residence, no cause for the alarm activation could be determined.
July 10 - 5:58 pm (Incident #208) -
Report of an odor of natural gas inside a private residence. Fire crews
used a meter to check air quality. There were no elevated levels of
natural gas detected. The local utility company was requested to respond.
July 11 - 2:35 am (Incident #209) -
Report of a fire in a kitchen at an apartment complex. Upon arrival, a
moderate smoke condition was found in a dwelling unit on the fifth floor.
It was determined that a wooden cutting board was left on the range top
burner which was inadvertently turned on.
July 11 - 4:57 pm (Incident #210) -
Fire alarm activation at a day care center. It was determined that a
two-year-old inadvertently activated a fire alarm pull station.
July 13 - 7:57 pm
(Incident #211) - Request for the fire department at the scene of a
motor vehicle crash. A single driver had to be extricated from one of the
vehicles.
July 14 - 11:43 pm
(Incident #212) - Report of smoke detectors sounding at a private
residence. Upon arrival of fire units, the detectors were no longer
sounding. A burning odor was noted outside of the residence.
July 15 - 4:09 am
(Incident #213) - Report of a dumpster fire at a borough-owned
facility. It was determined that a 40 cu. yd. dumpster containing yard
waste was found smoldering and was promptly extinguished by fire crews.
July 17 - 11:10 am
(Incident #214) - Report of a vehicle smoking in the industrial area.
It was determined that steam was mistaken for smoke while the car was
overheating.
July 17 - 4:01 pm
(Incident #215) - Fire alarm activation at an eating establishment in
the central business district. An apparent alarm malfunction was the cause
for the activation.
July 18 - 2:21 pm
(Incident #216) - Fire alarm activation at a condominium complex. It
was determined that smoke from a plumbing contractor’s torch caused the
alarm system to activate.
July 20 - 3:18 pm
(Incident #217) - Fire alarm activation at a medical facility. The
alarm was accidentally activated by a maintenance individual testing keys
to a fire alarm pull station.
July 23 - 6:38 pm
(Incident #218) - Report of an odor of natural gas inside a private
residence. It was determined that a young child inadvertently turned the
gas on at the stove. Fire crews used an air meter to check the level’s of
natural gas and a fan to ventilate the structure.
July 30 - 1:06 pm
(Incident #219) - Fire alarm activation at a condominium complex. An
apparent system malfunction was the cause for the alarm activation.
July 30 - 2:47 pm
(Incident #220) - Fire alarm activation at a condominium complex. It
was determined that a painting contractor accidentally struck a fire alarm
pull station.
July 31 - 10:39 pm
(Incident #221) -
Report of a carbon monoxide alarm sounding at a private residence. It was
determined that an apparent malfunction was the cause
June 2007
June 4 - 3:37 am (Incident #181) -
Fire alarm activation at a health care/medical facility. After a thorough
search of the building, no cause for the alarm activation could be
determined.
June 4 - 11:47 am (Incident #182)
- Fire alarm activation at an establishment in
the central business district. It was determined that a fire alarm
contractor was on site testing the alarm system.
June 6 - 7:56 pm (Incident #183) -
Report of an odor of burning electrical at a private residence. After a
thorough search of the residence, it was determined that a refrigerator
compressor motor was overheating. The unit was unplugged and it was
recommended that the homeowner call an appliance repair company.
June 8 - 7:42 pm (Incident #184) -
Fire alarm activation at a manufacturing facility in the industrial area.
It was determined that a malfunction was the cause for the alarm
activation.
June 9 - 2:13 pm (Incident #185) -
The FD was requested for mutual aid assistance to River Vale for a fire in
a private residence.
June 12 - 1:39 pm (Incident #186)
- Report of a natural gas leak at a
manufacturing facility in the industrial area. It was determined that a
fork lift ruptured a natural gas line to a heating unit. The gas was shut
off and the building was ventilated naturally.
June 13 - 1:53 pm (Incident #187)
- Report of a transformer arcing/sparking on top
of a utility pole. Upon arrival of fire units, no hazardous condition
could be found.
June 13 - 8:10 pm (Incident #188)
- The FD was requested for mutual aid assistance
to River Vale for a fire in a private residence.
June 18 - 7:36 pm (Incident #189)
- Fire alarm activation at a residential care
facility for the developmentally disabled. It was determined that
excessive cooking smoke was the cause for the alarm activation.
June 20 - 12:44 am (Incident #190)
- Fire alarm activation at a health care/medical
facility. After a thorough search of the building, no cause for the alarm
activation could be determined.
June 20 - 11:14 pm (Incident #191)
- Report of a fire alarm sounding at a
residential care facility for the developmentally disabled. It was
determined that a fire alarm pull station had been broken causing the
alarm to activate.
June 26 - 5:35 pm (Incident #192)
- Report of an odor of natural gas coming from
an oven at a private residence. Fire crews used a meter to check air
quality. There were no elevated levels of natural gas present and the oven
appeared to be operating properly.
June 27 - 4:25 pm (Incident #193)
- Report of smoke detectors sounding after at a
private residence after a nearby lightning strike. After a careful search
of the residence, nothing was determined to have been affected by the
strike.
June 27 - 4:42 pm (Incident #194)
- Report of a possible electrical fire at a
private residence. It was determined that the resident had been working on
a computer when a nearby lightning strike occurred, causing him to receive
an electric shock. There was no fire and the resident's injury was minor.
June 27 - 11:22 pm (Incident #195)
- Report of a fire in a lighting fixture on the exterior of a private
residence. Fire crews extinguished a small fire in an exterior light
containing a bird's nest.
June 28 - 11:20 am (Incident #196) - Fire alarm activation at
gas/service station. An apparent alarm malfunction was the cause for the
alarm activation.
May 2007
May 2 - 12:35 pm (Incident #162) -
Fire alarm activation at an elementary school. It was determined that a
student accidentally struck the fire alarm pull station.
May 4 - 2:03 pm (Incident #163) -
Fire alarm activation at an apartment complex. It was determined that a
contractor was cutting wood in a hallway which allowed sawdust to activate
the smoke detectors.
May 5 - 4:51 pm (Incident #164) -
Report of a fire in a bar-b-que at a private residence. Upon arrival of
fire units, it was determined that only the food was burning which was
extinguished by the homeowner.
May 6 - 10:20 pm (Incident #165) -
Report of smoke in an individual dwelling unit at an apartment complex. It
was determined that a tenant attempted to reheat food in a plastic
container on the stove-top.
May 8 - 12:38 pm (Incident #166) -
Fire alarm activation at a building in the central business district. It
was determined that an employee was using a hair dryer within close
proximity to a smoke detector which caused the alarm activation.
May 11 - 11:10 am (Incident #167)
- Report of an explosion and smoke in the area
of an electric utility sub-station. Upon arrival, nothing could be
located.
May 15 - 7:07 pm (Incident #168) -
Report of a possible car fire in the roadway. Upon arrival, it was
determined that an oil leak had created a smoke condition.
May 18 - 7:24 pm (Incident #169) -
Report of heavy smoke in the area of a private residence. It was
determined that the homeowner had just lit an outdoor fire pit.
May 19 - 1:25 pm (Incident #170) -
Report of a fire in a building in the industrial area. A fire was
confirmed in the office space of an operating business. Fire was visible
upon arrival of fire officers. Fire crews extinguished the fire, the cause
of which remains under investigation. Mutual aid assistance at the scene
was provided by Woodcliff Lake FD, Emerson FD and River Vale FD.
May 19 - 10:27 pm (Incident #171)
- Fire alarm activation at an eating
establishment in the central business district. It was determined that hot
grill plates were put into a water filled sink creating a stem condition
that activated the smoke detector system.
May 21 - 7:30 pm (Incident #172) -
Report of a fire in a three-family dwelling. It was determined that food
cooking on the stove was left unattended and created a smoke condition.
Fire crews efforts were hampered by the tenant not being forthcoming as to
the cause of the smoke.
May 22 - 8:04 pm (Incident #173) -
Report of a carbon monoxide detector sounding at
a private residence. It was determined that a dead/dying battery was the
cause for the detector activation.
May 22 - 8:19 pm (Incident #174) -
Fire alarm activation at an apartment complex. It was determined that an
apparent alarm malfunction was the cause for the alarm.
May 25 - 8:25 pm (Incident #175) -
Report of an arcing electrical transformer on a utility pole. Fire units
investigated the report and cleared the scene after requesting the local
utility company respond.
May 26 - 6:07 pm (Incident #176) -
Report of a burning odor in a business establishment. After a thorough
search of the premises, no cause for the burning odor could be found.
May 27 - 10:05 am (Incident #177)
- Report of a fire in the kitchen area of a
medical facility. Upon arrival of fire units, the fire had been
extinguished by employees. The fire was contained to an area adjacent to a
gas cooking appliance.
May 27 - 4:34 pm (Incident #178) -
Report of a fire in a cigarette butt receptacle on the sidewalk in the
central business district. The fire was extinguished by employees of the
adjacent business.
May 31 - 8:24 am (Incident #179) -
Fire alarm activation at a mixed-use residential/commercial building in
the central business district. It was determined that steam from a shower
was the cause for the alarm activation.
May 31 - 1:13 pm (Incident #180) -
Fire alarm activation at a residential facility for the developmentally
disabled. It was determined that a water valve that was mistakenly opened
in the basement caused the sprinkler alarm to sound causing the alarm.
April 2007
April 4 - 1:36 pm (Incident #083)
- Report of a vehicle on fire in the parking lot
of a medical facility. Upon arrival of fire units, a fire was found
burning in the driver's side mirror housing. The fire was promptly
extinguished and the owner notified. It appears that an electrical short
was the cause of the fire.
April 5 - 1:09 pm (Incident #084)
- Report of a carbon monoxide detector
activation in tan individual dwelling unit at an apartment complex. It was
determined that the detector was sounding due to dead/dying batteries.
April 5 - 1:42 pm (Incident #085)
- Fire alarm activation at an eating
establishment in the central business district. It was determined that the
alarm was activated during a testing procedure for newly installed fire
protection equipment.
April 7 - 2:38 pm (Incident #086)
- Request for the fire department at the scene
of a motor vehicle crash for possible leaking gasoline. The liquid leaking
was not gasoline and it was determined to have been non-hazardous.
April 8 - 8:30 pm (Incident #087)
- Report of a fire alarm sounding at a
multi-family dwelling. It was determined that cooking smoke from a first
floor tenant caused the alarms to activate.
April 9 - 1:07 am (Incident #088)
- Report of a burning odor and smoke condition
at a private residence. It was determined that a plastic utensil made
contact with the heating element in the dishwasher during the drying
cycle.
April 10 - 7:08 pm (Incident #089)
- Request to Woodcliff Lake for mutual aid
assistance for a fire at a private residence. The fire department was
cancelled prior to responding.
April 12 - 12:56 pm (Incident
#090) - Request for the fire department for a
person with their hand caught in a garage door at a private residence.
Initial responding fire personnel assisted on-scene police officers in
extricating the victim, who was then promptly transported to a local
medical facility.
April 12 - 5:42 pm (Incident #091)
- Fire alarm activation at a residential
facility for the developmentally disabled. It was determined that
excessive cooking smoke was the cause for the alarm activation.
April 15 - 5:54 pm (Incident #092)
- Report of heavy smoke coming from a private
residence. It was determined that a scrap piece of plastic was mistakenly
burned in the fireplace causing a smoke condition and a burning odor in
the area.
April 15 - 8:41 pm (Incident #093)
- Fire alarm activation at an educational
facility. It was determined that rain water was leaking into the basement
onto an electrical panel and the fire alarm telephone dialer box.
April 15 - 9:28 pm (Incident #094)
- Report of a fire alarm activation at a
commercial office in the central business district. It was determined that
the boiler ran dry and ignited paper material stored on top which created
a smoke condition.
April 15 - 9:40 pm (Incident #095)
– April 16 – 9:35 am (Incident #134) – The
Westwood Fire Department responded to multiple calls for assistance during
this period as a result of a nor’easter which passed through the region.
There were numerous responses for burning odor’s, smoke conditions and
furnace/electrical problems associated with flooded basements from the
excessive rains. Additionally, assistance was provided with evacuation
from several private residence’s.
April 16 – 11:08 am (Incident
#135) - Fire alarm activation at a commercial
building in the central business district. It was determined that a
malfunctioning smoke detector was removed by the tenant causing the alarm
to activate.
April 16 – 11:50 am (Incident
#136) – Fire alarm activation at an apartment
complex. It was determined that excessive smoke from cooking caused the
alarm system to activate.
April 16 – 12:45 pm (Incident
#137) – Fire alarm activation at a commercial
building in the central business district. It was determined that an alarm
contractor was servicing the alarm system and failed to notify central
dispatch.
April 16 – 3:03 pm (Incident #138)
– Fire alarm activation at a commercial building
in the central business district. It was determined that the Building
Dept. was performing an acceptance test on a range hood suppression system
and failed to notify central dispatch.
April 16 – 3:10 pm (Incident #139)
- Report of a possible furnace problem
associated with a flooding basement from excessive rains.
April 16 – 3:25 pm (Incident #140)
- Fire alarm activation at a condominium
complex. It was determined that the alarm activation was as a result of
flood water damage to an alarm panel.
April 16 – 4:24 pm (Incident #141)
- Report of a possible furnace problem
associated with a flooding basement from excessive rains.
April 16 – 6:28 pm (Incident #142)
- Fire alarm activation at a condominium
complex. It was determined that the alarm activation was as a result of
flood water damage to an alarm panel.
April 16 – 7:18 pm (Incident #143)
– Report of a carbon monoxide incident at a
private residence. It was determined that the exhaust from an operating
gasoline powered water pump created high levels of carbon monoxide within
the residence.
April 17 – 5:52 am (Incident #144)
- Report of a possible furnace problem
associated with a flooding basement from excessive rains.
April 17 – 11:04 am (Incident
#145) - Fire alarm activation at a condominium
complex. It was determined that the alarm activation was as a result of
flood water damage to an alarm panel.
April 17 – 12:40 pm (Incident
#146) – Report of an unknown type odor at a day
care facility. After a thorough search of the premises, no determination
could be made as to the cause of the unidentified odor.
April 17 – 6:24 pm (Incident #147)
– Fire alarm activation at a condominium
complex. It was determined that the alarm activation was as a result of
flood water damage to an alarm panel.
April 18 – 3:00 pm (Incident #148)
– Fire alarm activation at an educational
facility. It was determined that the alarm activation was due to a system
malfunction.
April 18 – 3:12 pm (Incident #149)
- Report of a possible furnace problem
associated with a flooding basement from excessive rains.
April 19 - 10:28 am (Incident
#150) - Report of a fire alarm sounding at an
apartment complex. It was determined that excessive smoke from cooking
caused a smoke detector to activate.
April 19 - 2:34 pm (Incident #151)
- Report of a smoke detector sounding at a
private residence. It was determined that a candle was producing excessive
smoke which caused the detector activation.
April 21 - 6:04 pm (Incident #152)
- Report of a burning odor with a possible gas
oven malfunction at a private residence. It was determined that the gas
oven was in the cleaning mode and was functioning as intended.
April 22 - 4:29 pm (Incident #153)
- Report of smoke detectors sounding in a
mixed-use retail/residential building in the central business district. It
was determined that an alarm malfunction was the cause for the alarm
activation.
April 23 - 12:25 pm (Incident
#154) - Report of a fire alarm sounding at a
religious education facility. It was determined that the alarm activation
was due to a malfunction.
April 23 - 5:16 pm (Incident #155)
- Fire alarm activation at a private residence.
It was determined that a renovation contractor was the cause for the alarm
activation.
April 27 - 8:16 pm (Incident #156)
- Report of a fire at a private residence. Upon
arrival of fire units, the fire, which was in an exterior lighting
fixture, had been extinguished.
April 28 - 9:12 am (Incident #157)
- Fire alarm activation at a storage facility in
the industrial area. It was determined that a floor grinding process was
the cause for the alarm activation.
April 28 - 11:21 am (Incident
#158) - Report of an odor of natural gas at a
borough owned building. Fire crews used a meter to check air quality.
There were no elevated levels of natural gas detected.
April 28 - 12:40 pm (Incident
#159) - Fire alarm activation at an apartment
complex. It was determined that a fire sprinkler on the third floor
ruptured causing a water condition.
April 28 - 5:44 pm (Incident #160)
- Fire alarm activation at a private residence.
It was determined that excessive cooking smoke was the cause for the alarm
activation.
April 29 - 4:52 pm (Incident #161)
- Request for the FD to stand-by at a motor
vehicle crash with an overturned vehicle.
March 2007
Mar 4 - 4:31 pm
(Incident #064) - Report of a water leak in the basement of a retail
business. Fire crews checked the utilities to verify that they weren't
compromised by water.
Mar 6 - 7:49 am
(Incident #065) - Fire alarm activation at a educational facility.
After a thorough search of the building, no found cause for the alarm
activation could be determined.
Mar 6 - 2:48 pm
(Incident #066) - Report of smoke detectors sounding at a private
residence. After a thorough search of the residence, no cause for the
smoke detector activation could be determined.
Mar 9 - 6:10 pm
(Incident #067) - Report of smoke detectors sounding at a private
residence. It was determined that the basement smoke detector was laden
with dust which was the cause for the activation.
Mar 10 - 8:01 am
(Incident #068) - Report of a possible fire in a wall at a private
residence. It was determined that a normally operating hot water pipe
behind the wall was the cause for the warm spot.
Mar 10 - 1:30 pm
(Incident #069) - Fire alarm activation at house of worship
educational facility. It was determined that cooking smoke was not being
properly ventilated due to a blockage in the ventilation shaft.
Mar 10 - 10:21 pm
(Incident #070) - Report of a fire alarm sounding at a mixed-use
residential/commercial building in the central business district. It was
determined that excessive cooking smoke was the cause for the alarm
activation.
Mar 12 - 6:30 pm
(Incident #071) - Fire alarm activation at an apartment complex. It
was determined that excessive cooking smoke in an apartment was the cause
for the alarm activation.
Mar 14 - 6:46 am
(Incident #072) - Report of a fire alarm sounding at a mixed-use
residential/commercial building in the central business district. After a
thorough search of the building, no cause for the alarm activation could
be determined.
Mar 15 - 5:22 am
(Incident #073) - Report of a fire in a manufacturing facility in the
industrial area. It was determined that a candle left burning in an office
ignited an adjacent plastic plant. Fire damage was contained to the plant,
carpet and a near-by bookshelf.
Mar 16 - 7:18 pm
(Incident #074) - Fire alarm activation at an apartment complex. It
was determined that a tenant placed a plastic dinner tray over on
operating burner of an electric range. Fire damage was contained to the
tray and range-top with smoke damage throughout the kitchen area.
Mar 16 - 7:22 pm
(Incident #075) - Report of a fire in a light fixture in the parking
lot of a building in the central business district. Upon arrival of fire
officers, the fire was found to have self-extinguished.
Mar 18 - 12:12 pm
(Incident #076) - Fire alarm activation at a financial institution in
the central business district. The alarm activation was determined to be
false as a result of a "trouble fault" within the system.
Mar 19 - 6:44 pm
(Incident #077) - Report of smoke detectors sounding at a mixed-use
commercial/residential building in the central business district. It was
determined that one of the commercial tenant's was burning incense which
caused the smoke detector system to activate.
Mar 20 - 1:11 pm (Incident #078) -
Report of smoke detectors sounding at a private residence. It was
determined that an occupant was burning incense and herbs which crested an
excessive smoke condition.
Mar 21 - 10:57 am (Incident #079)
- Fire alarm activation at a religious
educational facility. It appears that a young child pulled the fire alarm
on the way out the door.
Mar 21 - 10:44 pm (Incident #080)
- Report of an electrical fire in a dwelling
unit at an apartment complex. It was determined that a light fixture was
arcing and sparking. Fire crews disconnected the fixture and capped the
wires.
Mar 25 - 5:34 pm (Incident #081) -
Report of a fire in the kitchen area of a medical facility. Upon arrival
of fire units, the fire had been extinguished by employees. The fire was
contained to an area adjacent to a gas cooking appliance.
Mar 28 - 7:25 pm (Incident #082) -
Fire alarm activation at a private residence. It was determined that the
homeowner accidentally activated the system at the alarm panel upon
entering the residence.
February 2007
Feb 3 - 1:33 am (Incident #030) -
Fire alarm activation at a mixed-use residential/commercial building in
the central business district. It was determined that the alarm sounded
due to a detector malfunction.
Feb 4 - 9:38 am (Incident #031) -
Fire alarm activation at a mixed-use residential/commercial building in
the central business district. It was determined that the alarm sounded
due to a detector malfunction.
Feb 5 - 7:57 am (Incident #032) -
Fire alarm activation at a mixed-use residential/commercial building in
the central business district. It was determined that the alarm sounded
due to a detector malfunction.
Feb 5 - 11:06 am (Incident #033) -
Fire alarm activation at a mixed-use residential/commercial building in
the central business district. It was determined that the alarm sounded
due to an apparent alarm malfunction.
Feb 5 - 2:57 (Incident #034) -
Report of a smoke
detector sounding in a vacant dwelling unit at an apartment complex. It
was determined that dead/dying batteries were the cause for the alarm.
Feb 5 - 3:40 pm (Incident #035) -
Fire alarm activation at a private residence. It was determined that the
alarm activated due to a detector malfunction.
Feb 5 - 6:02 pm (Incident #036) -
Report of a fire at a private residence. Upon arrival, a fire was found
burning in a garbage can along the side of the building. It was determined
that discarded fire place ashes were placed in a garbage can without being
properly extinguished.
Feb 6 - 2:55 am (Incident #037) -
Report of a smoke detector sounding in a vacant dwelling unit at an
apartment complex. It was determined that the activation was due to a
faulty detector.
Feb 6 - 7:41 am (Incident #038) -
Report of a fire alarm activation at a mixed-use residential/commercial
building in the central business district. After a thorough search of the
building, no apparent cause for the alarm activation could be determined
Feb 7 - 6:06 am (Incident #039) -
Report of a fire alarm sounding at a residential care facility for the
developmentally disabled. It was determined that cooking smoke was the
cause for the alarm activation.
Feb 7 - 7:17 am (Incident #040) -
Report of a fire alarm sounding at a mixed-use residential/commercial
building in the central business district. After a thorough search of the
building, there was no found cause for the alarm activation.
Feb 7 - 9:43 am (Incident #041) -
Fire alarm activation at
a mixed-use residential/commercial building in the central business
district. It was determined that an ongoing alarm malfunction was the
cause.
Feb 7 - 12:15 pm (Incident #042) -
Carbon monoxide alarm sounding at a private residence. Fire crews used a
meter to check air quality. There were elevated levels of carbon monoxide
present which were a result of a car warming-up in the attached garage.
Feb 7 - 2:42 pm (Incident #043) -
Report of smoke detectors sounding at a private residence. It was
determined to be a faulty smoke detector in the attic area.
Feb 8 - 10:21 am
(Incident #044) - Report of smoke detectors sounding at a private
residence. It was determined that the detector in the attic area was in
need of maintenance.
Feb 8 - 11:24 am
(Incident #045) - Fire alarm activation at an apartment complex. It
was determined that a malfunction of the sprinkler system was the cause
for the alarm.
Feb 8 - 11:36 am
(Incident #046) - Report of a fire alarm activation at a private
residence. It was determined that an apparent malfunction was the cause
for the alarm activation.
Feb 10 - 8:01 am
(Incident #047) - Report of a water leak inside a private residence.
Fire crews shut-off the water at the meter. The local water, gas and
electric utility companies responded and shut-off their respective
utilities. The building department responded and posted the residence as
an unsafe structure.
Feb 10 - 12:14 pm
(Incident #048) - Carbon monoxide alarm activation at a private
residence. Fire crews used a meter to check air quality. There were
elevated levels of carbon monoxide present. The local utility company was
requested and responded. No fault was found with the appliances and it was
determined that a car left running in the garage was the cause for the
elevated levels.
Feb 10 - 1:27 pm
(Incident #049) - Report of smoke detectors sounding at a private
residence. It was determined that a basement smoke detector was
malfunctioning causing the alarm.
Feb 10 - 7:17 pm
(Incident #050) - Report of smoke detectors sounding at a private
residence. It was determined that smoke from a recently extinguished
candle was the cause for the detector activation.
Feb 12 - 4:46 pm
(Incident #051) - Fire alarm activation at a financial institution in
the central business district. It was determined that an alarm contractor
was making a repair and did not notify the central station monitoring
company.
Feb 14 - 4:20 pm
(Incident #052) - Fire alarm activation at a condominium complex. It
was determined that a pot of cooking oil on a stove in a dwelling unit was
inadvertently left on which created a smoke condition.
Feb 15 - 10:31 am
(Incident #053) - Report of a carbon monoxide alarm sounding at a
private residence. Fire crews used a meter to check air quality. There
were no elevated levels of carbon monoxide present. Detector maintenance
procedures were explained to the homeowner.
Feb 15 - 10:40 pm
(Incident #054) - Request for mutual aid assistance to Woodcliff Lake
for a FAST team on a structure fire at a strip mall.
Feb 15 - 11:38 pm
(Incident #055) - Report of a fire alarm sounding at an apartment
complex. It was determined that the audible alarm was a medical alert
alarm bell ringing in the lobby.
Feb 19 - 3:55 am
(Incident #056) - Fire alarm activation at an apartment complex. No
fire was found in the area of the alarm activation. It was determined that
an alarm malfunction was the cause.
Feb 19 - 4:43 am
(Incident #057) - Fire alarm activation at an apartment complex. No
fire was found in the area of the alarm activation. It was determined that
an alarm malfunction was the cause.
Feb 19 - 10:18 pm
(Incident #058) - Report of a smoke detector activation at a private
residence. It was determined that a dead/dying battery in a detector was
the cause for the alarm.
Feb 24 - 12:23 pm
(Incident #059) - Report of a fire in an oven at an apartment complex.
Upon arrival of fire units, the fire had been extinguished. Fire crews
used a fan to ventilate smoke from the dwelling unit.
Feb 25 - 5:08 pm
(Incident #060) - Fire alarm activation at a mixed-use
commercial/residential building in the central business district. Although
there was an activated smoke detector in a dwelling unit kitchen, there
was no smoke present. The proximity of the smoke detector to the stove may
be a contributing factor.
Feb 26 - 4:04 pm
(Incident #061) - Report of an odor of natural gas at a private
residence. Fire crews used a meter to check air quality. There were no
levels of natural gas detected.
Feb 28 - 6:44 pm
(Incident #062) - Fire alarm activation at a private residence. It was
determined that cooking smoke was the cause for the alarm activation.
Feb 28 - 10:22 pm
(Incident #063) - Fire alarm activation at an eating establishment in
the central business district. It was determined that an employee
accidentally struck a pull station.
January 2007
Jan 1 - 6:50 am (Incident #001) -
Report of smoke in the area of private residences. After a search of the
area, it was determined that smoke from a chimney was the cause.
Jan 2 - 9:53 pm (Incident #002) -
Fire alarm activation at a mixed-use office/residential building in the
central business district. After a thorough search of the building, no
cause for the alarm activation could be determined.
Jan 4 - 7:53 pm (Incident #003) -
Report of a fire alarm sounding and smoke in the building at a mixed-use
commercial/residential building in the central business district. It was
determined that a residential tenant on the second floor created an
excessive smoke condition while cooking.
Jan 5 - 12:22 pm (Incident #004) -
Request for the fire department to stand-by while police unit's
investigated a suspicious device.
Jan 7 - 9:38 am (Incident #005) -
Report of a carbon monoxide alarm sounding in a dwelling unit at an
apartment complex. Fire crews used a meter to check air quality. There
were slightly elevated levels of carbon monoxide present. The local
utility company was requested to respond.
Jan 8 - 5:46 am (Incident #006) -
Request for the fire department to respond to Emerson for mutual aid
assistance at a house fire.
Jan 9 - 9:58 am (Incident #007) -
Report of a carbon monoxide alarm sounding at a private residence. Fire
crews used a meter to check air quality. There were no elevated levels of
carbon monoxide detected. The local utility company was requested to
respond.
Jan 12 - 3:39 pm (Incident #008) -
Report of a car fire. Upon arrival, heavy smoke and fire was coming from
the vehicle. The car was being test-driven by a local mechanic who had
just completed repairs to the vehicle
Jan 13 - 6:40 am (Incident #009) -
Fire alarm activation at a residential facility for the developmentally
disabled. It was determined that unattended cooking was the cause for the
alarm activation.
Jan 13 - 1:19 pm (Incident #010) -
Report of a burning odor and a light smoke condition at a mixed-use
residential/commercial building. It was determined that a fuel oil
contractor had just completed a repair to the furnace which created a
light smoke condition and an odor of fuel oil.
Jan 16 - 10:37 am (Incident #011) -
Fire alarm activation at a private residence. It was determined that light
smoke from cooking was the cause for the alarm activation.
Jan 17 - 1:25 pm (Incident #012) -
Report of a smoke condition in an individual dwelling unit at a condo
complex. It was determined that a toaster failed to operate properly
burning to food within.
Jan 17 - 4:21 pm (Incident #013) -
Report of a grease fire in the kitchen at a private residence. Upon
arrival, the fire, which appeared to be minor, had self-extinguished.
Jan 18 – 9:48 am (Incident #014) –
No information
Jan 18 – 3:01 pm (Incident #015) –
No information
Jan 20 - 9:09 am (Incident #016) -
Fire alarm activation at a residential facility for the developmentally
disabled. It was determined that an alarm malfunction was the cause for
the smoke detector activation.
Jan 21 - 7:56 am (Incident #017) -
Report of a carbon
monoxide alarm sounding at a private residence. Fire crews used a meter to
check air quality. Slightly elevated levels of carbon monoxide were
detected. The local utility company was requested to respond.
Jan 21 - 9:56 am (Incident #018) -
Report of a carbon monoxide alarm sounding in an individual dwelling unit
at an apartment complex. Fire crews used a meter to check air quality. No
elevated levels of carbon monoxide were detected. The local utility
company was requested to respond.
Jan 21 - 9:53 pm (Incident #019) -
Report of a carbon monoxide alarm sounding in an individual dwelling unit
at an apartment complex. Fire crews used a meter to check air quality. No
elevated levels of carbon monoxide were detected. The activation was a
result of an improper battery installation.
Jan 23 - 5:30 pm (Incident #020) -
Report of an odor of natural gas in a residential area. Upon arrival of
fire officers, no odor could be detected.
Jan 23 - 6:57 pm (Incident #021) -
Report of a fire alarm sounding in an individual dwelling unit at an
apartment complex. It was determined that cooking smoke from the oven was
the cause for the alarm activation.
Jan 23 - 8:14 pm (Incident #022) -
Report of a smoke detector sounding in the individual dwelling unit at an
apartment complex. It was determined that the alarm activation was due to
cooking smoke.
Jan 26 - 3:45 pm (Incident #023) -
Mutual aid request to the Borough of Emerson for assistance at a possible
house fire.
Jan 27 - 2:20 pm (Incident #024) -
Report of a broken water pipe in a private residence. Fire crews secured
the water leak and evaluated the household utilities.
Jan 27 - 8:54 pm (Incident #025) -
Fire alarm activation at a private residence. It was determined that the
smoke detectors activated from cooking smoke.
Jan 28 - 3:37 pm (Incident #026) -
Report of an odor of natural gas outside of a medical facility. It was
determined to have been an ongoing issue which was under the care of
facility maintenance and the local utility company.
Jan 28 - 4:36 pm (Incident #027) -
Report of a water leak
in a vacant private residence. Fire crews secured the water at the meter
and shut-off the electric at the main panel.
Jan 31 - 10:19 am (Incident #028) -
Fire alarm activation at a health club facility in the central business
district. It was determined that an apparent malfunction was the cause for
the alarm activation.
Jan 31 - 8:00 pm (Incident #029) -
Report of a possible fire in the walls at a private residence. It was
determined that the use of a plumbers torch had started a fire within a
concealed wall space. The homeowner extinguished the fire prior to the
arrival of fire units.
|
