93 Center Ave.  Westwood, NJ 07675 - 100% Volunteer

December 2006

Dec 31 - 10:25 am (Incident #350) - Report of an alarm sounding from a resident in a dwelling unit. It was determined that the sounding alarm was a distress alarm from an apartment unit.

Dec 30 - 10:02 pm (Incident #349) - Report of an unknown type alarm sounding at a two-family residence. It was determined that the fire alarm panel was producing a local audible alarm indicating system trouble.

Dec 29 - 7:30 pm (Incident #348) - Report of a smoke detector sounding at a private residence. No apparent cause for the detector activation could be determined.

Dec 28 - 7:46 am (Incident #347) - 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.

Dec 27 - 9:32 am (Incident #346) - Report of a possible truck fire at an intersection in the central business district. Upon arrival of fire crews, no incident could be found.

Dec 27 - 7:47 am (Incident #345) - Report of water flowing from underneath a garage door at a private residence. It was determined that a water pipe had broken in the garage creating the water condition.

Dec 25 - 4:55 pm (Incident #344) - Request for the fire department at the scene of a motor vehicle crash/rollover. Fire crews stabilized the vehicles and insured scene safety.

Dec 25 - 3:50 pm (Incident #343) - Request to Emerson for mutual aid assistance to a building fire at a senior residential facility.

Dec 25 - 8:15 am (Incident #342) - Report of spilled food burning on the stove at a private residence. The burning material had been extinguished prior to arrival of fire units.

Dec 25 - 8:11 am (Incident #341) - Fire alarm activation at an apartment complex. It was determined that a power fault was the cause for the alarm activation.

Dec 25 - 7:33 am (Incident #340) - Fire alarm activation at a private residence. It was determined that a smoke detector malfunction was the cause for the alarm.

Dec 24 - 11:47 pm (Incident #339) - Report of a chimney fire at a private residence. It was determined that homeowner was burning large quantities of paper in the fireplace. The fire was out upon arrival of fire units.

Dec 24 - 9:36 pm (Incident #338) - Report of a burning odor at a municipal-owned building. After a thorough search of the building, no cause for the burning odor could be determined.

Dec 24 - 5:00 pm (Incident #337) - Report of a fire in the oven at a private residence. It was determined that food in the oven had burned and created a smoke condition in the residence.

Dec 24 - 12:00 am (Incident #336) - Fire alarm activation at a private residence. It was determined that a smoke detector malfunction was the cause for the alarm.

Dec 22 - 11:13 am (Incident #335) - Fire alarm activation at an apartment complex. It was determined that food was left cooking unattended in an apartment. Fire crews used a fan to ventilate the smoke from the apartment.

Dec 21 - 3:05 pm (Incident #334) - Report of a burning odor in a building in the central business district. It was determined that smoke from a neighboring wood burning stove was the cause for the smoke condition.

Dec 18 - 9:12 pm (Incident #333) - Report of a burning odor in a building in the central business district. It was determined that a towel in a clothes dryer had become caught in the rotating drum and was beginning to burn.

Dec 18 - 5:02 pm (Incident #332) - Report of an unknown burning odor at a building in the central business district. It was determined that a component of a fluorescent lighting fixture in the basement had failed and created a burning odor.

Dec 17 - 11:49 am (Incident #331) - Report of an odor of natural gas in and around a church. It was determined that a natural gas barbeque grill was on allowing gas to flow.

Dec 16 - 6:04 pm (Incident #330) - Report of a possible fire in the wall at a private residence. It was determined that an electrical outlet had failed. Power was disconnected to the outlet and it was recommended that the homeowner contact an electrician.

Dec 15 - 8:43 am (Incident #329) - Fire alarm activation at a private residence. It was determined that a chimney cleaning contractor was the cause for the alarm activation.

Dec 14 - 11:41 am (Incident #328) - Fire alarm activation at a training facility for disabled adults. It was determined that the alarm activation was due to excessive cooking smoke.

Dec 12 - 7:27 am (Incident #327) - Report of an odor of natural gas at a residential facility for the mentally disabled. 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 as a precautionary measure.

Dec 11 - 3:13 pm (Incident #326) - Report of an alarm sounding and a burning odor at an apartment complex. It was determined that an in-the-wall hallway heater had failed and created a smoke condition. Fire units secured the unit by disconnecting the power.

Dec 10 - 8:27 pm (Incident #325) - Fire alarm activation at a private residence. It was determined that a faulty smoke detector head was the cause for the alarm activation.

Dec 7 - 12:52 pm (Incident #324) - Report of a fire alarm sounding at a private residence. It was determined that water was leaking through a smoke detector which caused the activation.

Dec 7 - 7:44 am (Incident #323) - Report of a carbon monoxide detector activation at a mixed-use commercial/residential building in the central business district. Fire crews used a meter to check air quality. Elevated levels of carbon monoxide were detected. The local utility company was requested and responded. It was determined that a failure of the water heater was the cause for the elevated levels.

Dec 5 - 2:09 am (Incident #322) - Report of rubbish burning in the driveway at a private residence. It was determined that a bag  of sawdust had ignited from an earlier discarded cigarette butt that was thought to have been extinguished.

Dec 3 - 6:05 pm (Incident #321) - Report of a natural gas leak at a private residence. It was determined that the call was in another municipality on the same street name.

Dec 2 - 6:40 pm (Incident #320) - Fire alarm activation at a borough-owned facility. It was determined that an apparent alarm malfunction was the cause for the activation.

Dec 2 - 10:48 am (Incident #319) - Report of a fire alarm sounding at a mixed-use commercial/residential building. It was determined that burning incense was the cause for the alarm activation.

Dec 2 - 5:40 am (Incident #318) - Report of a smoke detector sounding in a borough-owned facility. It was determined that a dead/dying battery was the cause for the activation.

Dec 1 - 7:50 am (Incident #317) - Report of an oven fire at a private residence. It was determined that material in the oven had burned while in the self-cleaning mode. Fire crews confirmed no fire extension to the immediate adjacent areas with the use of the thermal imaging camera.

Dec 1 - 7:03 am (Incident #316) - Fire alarm activation at a mixed-use commercial/residential building in the central business district. It was determined that a residential tenant had created a smoke condition while cooking.

November 2006

Nov 30 - 2:47 pm (Incident #315) - Report of a burning odor at a municipal-owned property. It was determined that a copy machine had overheated created a light smoke condition.

Nov 30 - 10:40 am (Incident #314) - Fire alarm activation at a two-family residence. It was determined that water leaking from the second floor apartment flowed through a smoke detector below causing the alarm activation.

Nov 26 - 8:42 am (Incident #313) - Report of a smoke detector sounding at a multi-family dwelling. It was determined that a tenant had removed a smoke detector which began to activate as the battery weakened.

Nov 25 - 1:27 pm (Incident #312) - Fire alarm activation at a senior residential care facility. It was determined that food left unattended in a microwave oven was the cause for the alarm activation.

Nov 25 - 4:58 am (Incident #311) - Report of a carbon monoxide detector sounding in an individual unit at an apartment complex. Fire crews used a meter to check air quality. There were no elevated levels of carbon monoxide present.

Nov 23 - 5:20 pm (Incident #310) - Fire alarm activation at a private residence. The alarm was activated by light cooking smoke.

Nov 23 - 2:05 pm (Incident #309) - Fire alarm activation at a multi-family dwelling. After a thorough search of all apartments, there was no apparent cause for the alarm activation.

Nov 21 - 12:46 am (Incident #308) - Report of a carbon monoxide detector sounding in a dwelling unit at an apartment complex. Fire crews used a meter to check air quality. There were no elevated levels of carbon monoxide detected.

Nov 19 - 1:20 pm (Incident #307) - Report of a carbon monoxide detector sounding in a dwelling unit at an apartment complex. Fire crews used a meter to check air quality. There were no elevated levels of carbon monoxide present. The local utility company was requested to respond as a precautionary measure.

Nov 19 - 2:14 am (Incident #306) - Request by Hillsdale FD to respond to the scene and assist with a building fire.

Nov 15 - 11:40 am (Incident #305) - Report of a fire alarm sounding at a multi-family dwelling in the central business district. After a thorough search of the building, no apparent cause for the alarm activation could be determined.

Nov 14 - 10:28 am (Incident #304) - Fire alarm activation at a pre-school/day-care center. It was determined that a child accidentally pulled the fire alarm.

Nov 13 - 11:25 pm (Incident #303) - Report of a fire alarm sounding at a multi-family dwelling in the central business district. After a thorough search of the building, no apparent cause for the alarm activation could be determined.

Nov 13 - 8:00 pm (Incident #302) - Report of a fire alarm sounding at a multi-family dwelling in the central business district. After a thorough search of the building, no apparent cause for the alarm activation could be determined.

Nov 13 - 7:48 pm (Incident #301) - Report of a carbon monoxide detector activation at a private residence. Fire crews used a meter to check air quality. There were no elevated levels of carbon monoxide detected.

Nov 12 - 7:57 pm (Incident #300) - Fire alarm activation at a private residence. It was determined that burned food on the stove was the cause for the alarm activation.

Nov 12 - 6:49 pm (Incident #299) - Report of a fire alarm sounding at an apartment complex. It was determined that the audible alarm was not a fire alarm.

Nov 11 - 9:22 am (Incident #298) - Fire alarm activation at a mixed-use commercial/residential building in the central business district. It was determined that steam from a shower in a second floor apartment was the cause for the alarm activation.

Nov 9 - 4:40 pm (Incident #297) - 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. The local utility company was requested to respond.

Nov 8 - 7:46 pm (Incident #296) - Request for the FD to respond to a flooding residential area due to a storm. Fire crews assessed a number of residences to verify if flood waters were jeopardizing gas and/or electric and to evaluate the need for evacuation.

Nov 6 - 7:17 pm (Incident #295) - Report of a carbon monoxide detector activation at a private residence. Prior to the arrival of the FD, the alarm was reset and the house was ventilated. The local utility company was requested to respond as a precautionary measure.

Nov 1 - 10:59 am (Incident #294) - Report of smoke coming from a private residence. It was determined that an oil burner contractor was on site repairing a faulty oil furnace and had created a smoke condition during the course of the repair.

October 2006

Oct 29 - 10:20 am (Incident #293) - Report of an odor of gas at an assembly occupancy. It was determined that a pilot light on a gas range had extinguished creating the gas odor. Fire crews used a fan to ventilate the gas odor and requested the local utility company.

Oct 28 - 9:00 pm (Incident #292) - Report of a gas leak at a private residence. It was determined that a downed tree had ruptured a gas line causing a strong odor in the area. The local utility company was requested and responded.

Oct 27 - 4:40 pm (Incident #291) - Report of a carbon monoxide detector sounding in a unit at an apartment complex. Fire crews used a meter to check air quality. There were slightly elevated levels of carbon monoxide present. It was determined that the elevated levels were a result of a tenant servicing a vehicle in the garage below with the engine running.

Oct 27 - 8:04 am (Incident #290) - Report of a smoke condition in the industrial area. It was determined to be steam discharged into the cold morning air from normal facility operations.

Oct 25 - 11:54 am (Incident #289) - Report of smoke detectors sounding at a private residence. It was determined that the smoke detectors were "chirping" indicating dead/dying batteries.

Oct 21 - 9:22 am (Incident #288) - Report of a fire alarm sounding at a private residence. After a thorough search of the residence, no cause for the alarm activation could be determined.

Oct 20 - 10:15 pm (Incident #287) - Report of a fire alarm sounding at a mixed-use residential/commercial building in the central business district. It was determined that a tenant, who had seen a trouble indicator light on the fire alarm panel, erroneously called it in as a fire alarm.

Oct 20 - 9:00 pm (Incident #286) - Request for the fire department to assist the police department with forcible entry into an apartment dwelling unit to assist an elderly resident who had fallen.

Oct 20 - 8:58 pm (Incident #285) - Request for the fire department at a residential facility for the aged and infirmed due to a localized power outage. Fire crews assisted staff with transferring medical equipment to generated power.

Oct 19 - 4:32 pm (Incident #284) - Report of a fire in a private residence. Upon arrival, it was determined that food in the oven had burned creating a smoke condition. Fire crews used a fan to clear smoke from the residence.

Oct 18 - 1:27 am (Incident #283) - Fire alarm activation at a mixed-use residential/commercial building in the central business district. It was determined that

Oct 17 - 5:02 pm (Incident #282) - Report of a carbon monoxide detector sounding in a unit at a condominium complex. Fire crews used a meter to check air quality. There were no elevated levels of carbon monoxide detected. It was determined that dead/dying batteries in the detector was the cause for the alarm activation.

Oct 17 - 11:25 am (Incident #281) - Report of an unknown type burning odor at an eating establishment in the central business district. It was determined that an electrical outlet had shorted out and was overheating. Fire crews disconnected the outlet and performed a thorough search to verify that there was nothing burning within the adjacent wall spaces.

Oct 16 - 11:50 am (Incident #280) - Fire alarm activation at a medical facility. It was determined that dust from a renovation project was the cause for the alarm activation.

Oct 15 - 8:43 pm (Incident #279) - Fire alarm activation at a residential facility for the aged and infirmed. It was determined that the fire alarm pull station was struck maliciously.

Oct 14 - 10:48 pm (Incident #278) - Automatic mutual aid received from Emerson Fire Dept. for a fire alarm activation at a residential facility for the developmentally disabled. It was determined that cooking smoke was the cause for the activation.

Oct 14 - 11:10 am (Incident #277) - Fire alarm activation at a house of worship in the central business district. A pot was found burning unattended on the stove in the kitchen. It was determined that water was being boiled earlier to free wax from candle sconces.

Oct 13 - 4:15 pm (Incident #276) - Fire alarm activation at an elementary school. Upon arrival of fire units, heavy steam was found coming from the boiler room. It was determined that a steam line had ruptured causing the fire alarm to activate. A plumbing contractor was requested and responded.

Oct 12 - 7:02 am (Incident #275) - Request for the fire department at the scene of a motor vehicle crash. Fire crews dispersed an absorbent material to contain spilled fluids on the roadway.

Oct 11 - 6:10 pm (Incident #274) - Request for the fire department at the scene of a motor vehicle crash. Fire crews disconnected the battery cables on one vehicle to stop the sounding horn.

Oct 11 - 3:06 pm (Incident #273) - Report of natural gas flowing from an oven. It was determined that the oven, which was in use, was malfunctioning, allowing gas to escape. Fire crews shut-off the gas valve to the appliance and recommended that the homeowner have a plumbing contractor respond.

Oct 11 - 12:03 pm (Incident #272) - Fire alarm activation at an elementary school. It was determined that a student accidentally struck a fire alarm pull station causing the alarm.

Oct 11 - 5:48 am (Incident #271) - Fire alarm activation at a residential facility for the developmentally disabled. It was determined that cooking smoke was the cause for the alarm activation.

Oct 9 - 9:02 am (Incident #270) - Fire alarm activation at a residential facility for the developmentally disabled. It was determined that excessive use of aerosol spray was the cause for the alarm activation.

Oct 7 - 5:09 am (Incident #269) - Fire alarm activation at an establishment in the central business district. After a thorough search of the facility, no found cause for the alarm activation could be determined.

Oct 6 - 5:10 pm (Incident #268) - Report of a burning odor at an apartment complex. It was determined that a belt was burning on an overloaded washing machine causing the odor.

Oct 5 - 9:15 am (Incident #267) - Fire alarm activation at a residential facility for the aged and infirmed. It was determined that condensation from a HVAC duct dripped down onto a smoke detector head causing the alarm activation.

Oct 4 - 11:23 pm (Incident #266) - Fire alarm activation at an educational facility. After a thorough search of the building, there was no found cause for the alarm activation.

Oct 4 - 3:27 am (Incident #265) - Report of a fire alarm sounding at a building in the central business district. It was determined that an extermination contractor was performing a monthly service and accidentally activated the smoke detectors.

September 2006

Sept 30 - 5:26 pm (Incident #264) - Fire alarm activation at a medical facility. It was determined that a fire alarm pull station was struck in error transmitting the alarm.

Sept 30 - 4:50 pm (Incident #263) - Report of an unknown type item burning in the rear parking lot of an establishment in the central business district. It was determined that an ironing board cover was burning but had been extinguished prior to FD arrival.

Sept 29 - 3:13 pm (Incident #262) - Report of a burning odor with smoke detectors sounding at a building in the central business district. It was determined that a newly installed roof-top HVAC unit was lightly smoking and creating a burning odor. The installation contractor was notified and responded.

Sept 27 - 6:59 am (Incident #261) - Fire alarm activation at a private residence. It was determined that steam from the shower was the cause for the alarm activation.

Sept 26 - 5:25 pm (Incident #260) - Fire alarm activation at a residential facility for the developmentally disabled. It was determined that cooking smoke was the cause for the alarm activation.

Sept 26 - 1:07 pm (Incident #259) - Fire alarm activation at a private residence. It was determined that renovation contractor's were the cause for the false alarm activation.

Sept 26 - 1:06 am (Incident #258) - Report of a carbon monoxide detector activation in a private unit at an apartment complex. It was determined that a dead battery was the cause for the alarm activation.

Sept 26 - 12:16 am (Incident #257) - Fire alarm activation at a private residence. It was determined that the apparent alarm malfunction was due to the lack of system maintenance.

Sept 25 - 4:13 pm (Incident #256) - Report of a burning odor at a multi-tenant medical facility. After a thorough search of the building, no definitive cause for the burning odor could be determined although it was believed to have been from a medical procedure involving hair removal.

Sept 22 - 3:39 pm (Incident #255) - Report of a fire in the kitchen at a private residence. Upon arrival of fire officers, heavy smoke was found inside the residence. It was determined that a pan with cooking oil was left unattended on the stove top. When discovered by the homeowner, the pan was removed to the sink where decorative materials and a portion of the cabinet became involved in fire. The fire was extinguished by police personal prior to the arrival of the fire department.

Sept 20 - 2:48 pm (Incident #254) - Report of a motor vehicle fire. Upon arrival, fire crews found a fire in the engine compartment of the vehicle and promptly extinguished it.

Sept 20 - 1:48 pm (Incident #253) - Request for the fire department at the scene of a motor vehicle crash. Fire crews used hydraulic rescue equipment to remove the driver side door to facilitate victim removal for transportation to a medical facility.

Sept 19 - 8:45 pm (Incident #252) - Fire alarm activation at a borough owned building. It was determined that cooking smoke was the cause for the alarm activation.

Sept 17 - 8:50 am (Incident #251) - Fire alarm activation at a mixed-use commercial/residential building in the central business district. After a thorough search of the building, no cause for the alarm activation could be determined.

Sept 16 - 5:45 pm (Incident #250) - Report of a dumpster fire behind a building in the central business district. Upon arrival of fire units, no fire could be located.

Sept 16 - 10:13 am (Incident #249) - Report of smoke detectors sounding at a private residence. It was determined that the activation was due to dead/dying batteries in the detectors.

Sept 16 - 1:36 am (Incident #248) - Report of a fire in a bathroom ceiling fan at an apartment complex. It was determined that the fan shorted out creating a light smoke condition.

Sept 15 - 8:38 am (Incident #247) - Report of a motor vehicle crash with persons trapped. Fire department operations involved the removal of both the driver and passenger doors to facilitate the removal of two victims for transportation to a medical facility. Emerson FD assisted Westwood fire units.

Sept 14 - 7:15 am (Incident #246) - Fire alarm activation at a food establishment in the central business district. Upon arrival of fire officers, it was determined that food material spilled onto the stove creating a smoke condition.

Sept 13 - 10:05 am (Incident #245) - Report of a fire alarm sounding at a private residence. It was determined that renovation contractors set off the fire alarm with excessive dust.

Sept 12 - 8:11 pm (Incident #244) - Report of a burning odor at a borough-owned building in the central business district. It was determined that the burning odor was from a wood burning appliance being utilized in the immediate vicinity.

Sept 12 - 11:26 am (Incident #243) - Fire alarm activation at a private residence. It was determined that a renovation contractor was the cause for the alarm activation.

Sept 8 - 9:20 am (Incident #242) - Smoke detector activation at a medical facility. It was determined that an electrician was conducting service on the system and accidentally transmitted the alarm.

Sept 7 - 12:45 pm (Incident #241) - Fire alarm activation at a residential facility for the developmentally disabled. It was determined that cooking smoke was the cause for the alarm activation.

Sept 7 - 8:49 am (Incident #240) - Report of an unknown type liquid substance spilled in the roadway creating a vapor cloud. Bergen County HazMat Units were requested and responded. The material was identified by HazMat crews as some type of acid which was quickly neutralized and cleaned-up. Fire crews assisted HazMat crews with decontamination and clean-up.

Sept 6 - 10:48 pm (Incident #239) - Report of a dimmer switch heating and smoking at a private residence. It was determined that the switch had shorted out and overheated. Fire crews disconnected the power to the switch.

Sept 6 - 3:22 pm (Incident #238) - Fire alarm activation at a commercial building in the industrial area. After a thorough search of the building, there was no cause found for the alarm activation.

Sept 3 - 5:29 pm (Incident #237) - Report of smoke detectors sounding at a private residence. It was determined that a localized power outage caused the detectors to activate due to dead back-up batteries in the units.

Sept 3 - 5:14 pm (Incident #236) - Report of wires burning in a tree in front of a private residence. Prior to arrival of fire units, the phase tripped, de-energizing the wires resulting in a localized power outage. No fire in the tree was found.

Sept 3 - 1:12 am (Incident #235) - Fire alarm activation at an apartment complex. It was determined that the alarm activation was a result of a power outage from a heavy storm.

Sept 2 - 11:56 pm (Incident #234) - Report of a carbon monoxide detector activation at a private residence. Fire crews used a meter to check air quality. There were no elevated levels of carbon monoxide detected. The activation was a result of dead/dying batteries in the detector.

Sept 2 - 8:10 pm (Incident #233) - Report of wires burning in a tree in front of a private residence. Upon arrival of fire officers, there was no incident found at the dispatch address.

Sept 2 - 8:04 pm (Incident #232) - Report of wires burning in a tree. Upon arrival of fire units, a primary wire had burned through and dropped to the ground.

Sept 2 - 12:20 pm (Incident #231) - Report of a burning odor at a commercial building. After a thorough search of the building, no cause of the burning odor could be determined.

August 2006

Aug 31 - 7:00 pm (Incident #230) - Report of an odor of natural gas at a building in the central business district. After a thorough search of the building and surrounding buildings, no cause for the gas odor could be determined.

Aug 30 - 8:48 am (Incident #229) - Fire alarm activation at a medical facility. After a thorough search of the building, no cause for the alarm activation could be determined.

Aug 29 - 9:08 am (Incident #228) - Report of a payphone arcing/sparking. An employee of the telephone company, who was removing the payphone, determined the phone to be energized with electric power. The area around the payphone was cordoned off and the local utility company was requested to respond.

Aug 27 - 10:22 pm (Incident #227) - Fire alarm activation at a mixed-use commercial/residential building in the central business district. After a thorough search of the building, there was no found cause for the alarm activation.

Aug 27 - 9:42 pm (Incident #226) - Fire alarm activation at an eating establishment in the central business district. It was determined that smoke from the extinguishment of several candles was the cause for the alarm activation.

Aug 26 - 1:31 pm (Incident #225) - Fire alarm activation at a private residence. It was determined that cooking smoke was the cause for the alarm activation.

Aug 25 - 5:37 am (Incident #224) - Report of wires burning at the top of a utility pole. Upon arrival of fire officers, a series of wires were found to be burning. The FD stood-by and awaited the arrival of the local utility company.

Aug 25 - 10:33 pm (Incident #223) - Fire alarm activation at an eating establishment in the central business district. It was determined that steam from the dish washer was the cause for the alarm activation.

Aug 24 - 10:05 pm (Incident #222) - Fire alarm activation at an eating establishment in the central business district. It was determined that oven cleaning was the cause for the alarm activation.

Aug 24 - 12:05 pm (Incident #221) - Report of a carbon monoxide detector activation at a private residence. Fire crews used a meter to check air quality. There were no elevated levels of carbon monoxide found. It was determined that the alarm activation was due to dead/dying batteries.

Aug 21 - 5:37 am (Incident #220) - Request for the fire department to stand-by for a helicopter landing at a medical facility. The helicopter landed without incident.

Aug 20 - 5:18 pm (Incident #219) - Report of a carbon monoxide detector sounding at a condominium complex. Fire crews used a meter to check air quality. There were no elevated levels of carbon monoxide detected.

Aug 19 - 9:59 pm (Incident #218) - Report of a fire alarm sounding at an apartment complex. After a thorough search of the building, no apparent cause for the alarm activation could be determined.

Aug 19 - 6:09 pm (Incident #217) - Report of water leaking and an alarm sounding in a unit at an apartment complex. It was determined that a sink on the second floor overflowed and leaked through the smoke detector into the apartment below.

Aug 19 - 11:38 am (Incident #216) - Report of a fire alarm sounding at a building in the central business district. After a thorough search of the building, there was no apparent cause for the alarm activation.

Aug 17 - 11:48 pm (Incident #215) - Report of a carbon monoxide detector sounding in a dwelling unit at an apartment complex. It was determined that the battery in the detector was dead/dying.

Aug 16 - 8:46 pm (Incident #214) - Request for the fire department to stand-by for a medivac helicopter landing. After a successful landing at 8:14 pm, the fire department cleared the scene.

Aug 16 - 8:21 pm (Incident #213) - Report of an oven fire at a private residence. It was determined that a small amount of food was burning in the oven. The fire self-extinguished itself. Fire crews used a fan to ventilate a light smoke condition.

Aug 16 - 8:04 pm (Incident #212) - Request for the fire department to stand-by for a medivac helicopter landing. Fire units were cleared as the flight was cancelled due to mechanical problems.

Aug 16 - 7:17 am (Incident #211) - Fire alarm activation at a business in the central business district. It was determined that a flow switch to the sprinkler system had failed causing the alarm activation.

Aug 15 - 7:02 pm (Incident #210) - Report of a carbon monoxide detector activation at a private residence. 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.

Aug 13 - 10:51 pm (Incident #209) - Report of a smoke detector sounding and the odor of smoke at an apartment building. It was determined that the smoke detector was sounding due to a dead/dying battery. The smoke odor was from an unfounded fireplace or outside burning in the area.

Aug 13 - 7:47 am (Incident #208) - Fire alarm activation at a borough-owned facility. It was determined that an electrical fault was the cause for the activation.

Aug 12 - 10:35 pm (Incident #207) - Report of a burning odor in the area of a private residence. It was determined that the odor was from unfounded outdoor burning in the area.

Aug 12 - 8:31 am (Incident #206) - Report of an unidentified odor at a medical facility. Fire crews assisted with evacuation and identifying the source of the odor. It was determined that a valve had burst on a water circulating line releasing water containing a rust inhibitor which caused the odor throughout the building. No injuries were reported.

Aug 10 - 8:47 pm (Incident #205) - Report of a carbon monoxide detector sounding and an odor of gas in an individual dwelling unit at an apartment complex. Upon arrival of fire units, there was no alarm sounding. Fire crews used an air meter to check air quality. There were no elevated levels of carbon monoxide present and no odor of natural gas.

Aug 9 - 6:30 am (Incident #204) - Report of an electrical fire at a private residence. It was determined that an electrical outlet was arcing/sparking when an appliance was unplugged. The breaker to the outlet was turned off and the homeowner was advised to contact an electrician.

Aug 5 - 9:12 am (Incident #203) - Automatic mutual aid assistance received from River Vale FD for an odor of natural gas in a building in the central business district. No odor of gas was detected but a paint odor was present from a recently completed renovation project. The local utility company was requested to respond as a precautionary measure.

Aug 3 - 5:06 pm (Incident #202) - Report of wires burning on a utility pole in front of a building in the central business district. It was determined that a wiring harness running to the underground service had shorted out due to heavy rain. The local utility company was requested to respond.

Aug 3 - 3:04 pm (Incident #201) - Fire alarm activation at an apartment complex. It was determined that recent sprinkler system repairs were the caused for the false alarm activation.

Aug 2 - 1:20 pm (Incident #200) - Report of a possible truck fire in a residential neighborhood. Upon arrival, it was determined that a short circuit had occurred in the wiring to a motor for a hose reel. Fire damage was confined to a wiring harness.

Aug 1 - 11:21 pm (Incident #199) - Report of a burning odor at a private residence. It was determined that water leaking into a floor mounted junction box created a short circuit and the burning odor.

July 2006

July 28 - 12:24 pm (Incident #198) - Report of a person trapped in a stalled elevator at a medical facility. Upon arrival of fire officers, it was confirmed that a single person was trapped in a stalled elevator at the basement level. The power to the elevator was locked out and the doors were manually forced open releasing the uninjured victim.

July 27 - 9:34 am (Incident #197) - Report of an odor of natural gas in a building in the central business district. It was determined that the pilot light in the oven had extinguished allowing gas to escape. The local utility company was requested and responded.

July 26 - 10:17 am (Incident #196) - Report of a fire alarm sounding intermittently at a municipal-owned facility. It was determined that a faulty smoke detector was the cause for the alarm.

July 25 - 6:21 am (Incident #195) - Fire alarm activation at an apartment complex. It was determined that a faulty device was the cause for the activation.

July 24 - 1:21 pm (Incident #194) - Report of a fire in the kitchen in an individual dwelling unit at an apartment complex. Upon arrival of fire crews, the fire had been extinguished by the tenant. The tenant sustained burns to his arm and hand. Fire damage was contained to the stove, countertop, floor, exhaust fan and cabinets.

July 22 - 11:02 am (Incident #193) - Report of an odor of natural gas at a private residence. After a thorough search of the residence and the use of an meter to check air quality, there were no elevated levels of natural gas detected.

July 21 - 4:42 am (Incident #192) - Report of a smoke detector sounding at a private residence. It was determined that the smoke detector system was malfunctioning.

July 20 - 5:55 pm (Incident #191) - Fire alarm activation at a borough-owned building. It was determined that the alarm was activated due to a localized power outage.

July 19 - 7:00 am (Incident #190) - Fire alarm activation at a residential care facility. It was determined that a smoke detector activated due to excessive dust within.

July 18 - 10:49 pm (Incident #189) - Report of a fire in a tree in the rear yard of a private residence. Upon arrival of fire units, the fire was unfounded.

July 18 - 10:25 pm (Incident #188) - Report of a private residence struck by lightning. It was determined that the lightning strike damaged a circuit breaker in the electrical panel in the basement.

July 18 - 7:21 pm (Incident #187) - Fire alarm activation at a municipal-owned building. It was determined that a localized power failure may have been the cause for the alarm activation.

July 18 - 6:30 pm (Incident #186) - Fire alarm activation at a medical facility. It was determined that a localized power failure may have been the cause for the alarm activation.

July 18 - 5:30 pm (Incident #185) - Fire alarm activation at a medical facility. It was determined that a localized power failure may have been the cause for the alarm activation.

July 18 - 4:50 pm (Incident #184) - Fire in telephone wires on a utility pole in a residential neighborhood. It was determined that a localized power failure was most likely the cause for the fire.

July 18 - 4:40 pm (Incident #183) - Fire alarm activation at a municipal-owned building. It was determined that a localized power failure was the cause for the alarm.

July 18 - 1:42 am (Incident #182) - Fire alarm activation at a residential care facility. It was determined that a smoke detector activated due to excessive dust within.

July 15- 8:22 pm (Incident #181) - Request to Washington Twp. for automatic aid assistance coverage during a fire department event. The response was to a fire alarm activation at a residential facility for the developmentally disabled. No cause for the activation was determined.

July 14 - 3:29 pm (Incident #180) - Report of a condition thought to be smoke coming from the rear of an educational facility. It was determined that dust from stone cutting work was mistaken for smoke.

July 14 - 12:20 PM (Incident #179) - Request to River Vale for mutual aid assistance at a house fire. The fire was confined to the exterior of the structure. The cause was a faulty timer to the pool filter.

July 14 - 9:39 am (Incident #178) - Fire alarm activation at an educational facility. Individuals removing older portions of the fire alarm system were the cause for the activation.

July 13 - 2:28 pm (Incident #177) - Fire alarm activation at an eating establishment in the central business district. No cause for the alarm activation was found.

July 13 - 9:15 am (Incident #176) - Report of an odor of gas at an eating establishment in the central business district. Upon arrival, the local utility company was on scene and had stopped the flow of gas from a stove.

July 8 - 5:29 am (Incident #175) - Fire alarm activation at a residential facility for the developmentally disabled. It was determined that cooking smoke was the cause for the activation.

July 7 - 5:05 pm (Incident #174) - Investigation regarding a short circuited electrical outlet with the discharge of a dry chemical fire extinguisher in an educational facility.

July 7 - 12:36 pm (Incident #173) - Request by Hillsdale FD for a ladder truck for mutual aid assistance. The FD was cancelled en route.

July 5 - 12:51 pm (Incident #172) - Fire alarm activation at a commercial building in the central business district. There was no found cause for the alarm activation which was generated out of a business on the first floor.

July 4 - 9:41 am (Incident #171) - Fire alarm activation at an apartment complex. It was determined that a maintenance contractor was sanding within close proximity to a smoke detector.

July 3 - 8:33 am (Incident #170) - Report of a fire alarm sounding at a mixed-use commercial/residential building in the central business district. It was determined that an alarm fault at the panel was the cause for the alarm.

July 1 - 10:25 am (Incident #169) - Fire alarm activation at a mixed-use commercial/residential building in the central business district. The cause of the alarm activation, which was generated from a residential apartment, was undetermined but may have been as a result of steam from a shower.

June 2006

June 29 - 1:20 pm (Incident #168) - Fire alarm activation at a retail establishment in the central business district. It was determined that damage to the telephone line caused the alarm to be transmitted.

June 29 - 8:30 am (Incident #167) - Fire alarm activation at a private residence. It was determined that the smoke detectors were being tested. The resident was unaware that a contract with a central station monitoring company was still in existence.

June 28 - 7:13 pm (Incident #166) - Request for the FD at the scene of a motor vehicle crash. Rescue crews utilized extrication equipment to provide access to a single victim who sustained injuries in the crash.

June 28 - 1:50 pm (Incident #165) - Fire alarm activation at a mixed-use commercial/residential building in the central business district. It was determined that cooking smoke from an eating establishment was the cause for the alarm activation.

June 27 - 3:02 pm (Incident #164) - Fire alarm activation at an educational facility. It was determined that an alarm contractor was performing work on the system and accidentally transmitted the alarm.

June 26 - 8:32 pm (Incident #163) - Report of a burning odor in a mixed-use commercial/residential building in the central business district. After a thorough search of the building, it was determined that a air circulating fan was malfunctioning and creating the smoke condition.

June 26 - 10:02 am (Incident #162) - Report of an attic fan burning at a private residence. It was determined that a whole house attic fan had malfunctioned and created a smoke condition in the residence.

June 26 - 6:01 am (Incident #161) - Fire alarm activation at a mixed-use commercial/residential building in the central business district. It was determined that there was no found cause for the alarm activation.

June 25 - 7:31 pm (Incident #160) - Fire alarm activation at a mixed-use commercial/residential building in the central business district. It was determined that a residential tenant caused the activation by burning food on the stove top.

June 25 - 8:30 am (Incident #159) - Fire alarm activation at a medical facility. It was determined that the fire alarm activated due to a local power outage.

June 24 - 11:08 pm (Incident #158) - Report of a smoke detector sounding in a vacant mixed-use commercial/residential building. It was determined that the smoke detector was sounding due to a dying battery.

June 23 - 11:16 pm (Incident #157) - Request to Emerson for mutual aid assistance at the scene of a downed power wire. Fire units stood-by as crews from the local utility company responded.

June 22 - 12:30 pm (Incident #156) - Fire alarm activation at an eating establishment under construction in the central business district. It was determined that a painting contractor accidentally struck the fire alarm pull station.
 

June 22 - 11:14 am (Incident #155) - Fire alarm activation at a day care center. It was determined that smoke from cooking operations was the cause for the alarm activation.
 

June 21 - 10:30 am (Incident #154) - Fire alarm activation at an eating establishment under construction in the central business district. There was no determined cause for the alarm activation.
 

June 20 - 5:00 pm (Incident #153) - Report of a blue flame visible in the furnace at a private residence. It was determined that the visible flame was from the burner at the base of the furnace operating in the normal fashion.
 

June 19 - 1:00 pm (Incident #152) - Fire alarm activation at a condominium complex. It was determined that contractors performing grinding work generated smoke that activated the smoke detector system.
 

June 18 - 8:40 pm (Incident #151) - Fire alarm activation at a mixed-use commercial/residential building in the central business district. It was determined that a residential tenant created a smoke condition while using the oven.
 

June 16 - 10:25 pm (Incident #150) - Report of a burning odor inside a private residence. After a thorough search of the residence, it was determined that the burning odor was from an outdoor fire pit burning in the neighborhood.

June 15 - 6:33 pm (Incident #149) - Report of an unidentified burning odor at a borough-owned facility. After a thorough search of the building, no source for the burning odor could be found.
 

June 15 - 6:08 pm (Incident #148) - Fire alarm activation at a mixed-use commercial/residential building in the central business district. Mutual aid was requested from the Hillsdale FD due to the fact that Westwood FD was involved at another call.
 

June 15 - 6:00 pm (Incident #147) - Request for the FD at the scene of a motor vehicle crash. The FD removed a door from a vehicle to facilitate the removal of an injured victim.
 

June 14 - 6:10 pm (Incident #146) - Report of a leaking propane tank that was abandoned at a vacant private residence. It was determined that the tank had been turned on. It was promptly shut off by responding police personal.

June 10 - 11:27 am (Incident #145) - Fire alarm activation at a medical facility. It was determined that the facility was conducting a scheduled fire drill and the alarm was inadvertently transmitted by the central station monitoring company.

June 9 - 4:40 pm (Incident #144) - Report of a motor vehicle crash into gasoline pumps at a motor fuel filling station. The FD was requested as a precautionary measure to secure the vehicles and disconnect the batteries.
 

June 8 - 12:21 pm (Incident #143) - Fire alarm activation at a commercial establishment. After a thorough search of the facility, there was no apparent cause for the alarm activation.
 

June 3 - 3:37 pm (Incident #142) - Report of a downed power wire arcing/sparking. The FD stood-by and awaited the local utility companies response.
 

June 1 - 8:28 am (Incident #141) - Report of a fire alarm sounding at a private residence. It was determined that the smoke detector system was malfunctioning.
 

June 1 - 5:12 am (Incident #140) - Report of a fire alarm sounding at a private residence. After a thorough search of the residence, it was determined that the smoke detector system was malfunctioning.
 

May 2006

May 31 - 9:50 am (Incident #139) - Request for the FD at the scene of a motor vehicle crash. Upon arrival of fire officers, it was determined that no FD action was needed.
 

May 29 - 1:40 pm (Incident #138) - Report of a fire alarm sounding in a private residence. After a thorough search of the residence, no cause for the alarm was found.
 

May 26 - 11:46 am (Incident #137) - Fire alarm activation at a mixed-use residential/commercial building in the central business district. It was determined that a fire alarm was maliciously pulled in the basement garage area.
 

May 26 - 9:56 am (Incident #136) - Fire alarm activation at a mixed-use residential/commercial building in the central business district. It was determined that smoke from a plumbing contractor's torch was the cause for the activation.

May 23 - 11:25 pm (Incident #135) - Report of a carbon monoxide detector activation 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 as a precautionary measure.
 

May 23 - 9:00 am (Incident #134) - Report of a fire alarm sounding at a mixed-use commercial/residential building in the central business district. It was determined that smoke generated from a contractor's saw was the cause for the alarm activation.
 

May 22 - 12:50 pm (Incident #133) - Fire alarm activation at a residential
care facility. It was determined that an alarm contractor was performing annual service to the fire alarm system.
 

May 21 - 4:46 pm (Incident #132) - Report of a carbon monoxide detector activation at a multifamily dwelling. Fire crews used a meter to check air quality. There were slightly elevated levels of carbon monoxide present in the first floor apartment. It was determined that excessive use of the oven and stove was the cause for the elevated levels. The local utility company was requested to respond as a precautionary measure.
 

May 20 - 4:16 pm (Incident #131) - Fire alarm activation at an establishment in the central business district. It was determined that the child of an employee accidentally struck the fire alarm pull station transmitting the alarm.
 

May 18 - 10:15 pm (Incident #130) - Fire alarm activation at a medical facility. It was determined that technical problems from a previous fire alarm were the cause for the alarm activation.
 

May 18 - 9:34 am (Incident #129) - Fire alarm activation at a medical facility. It was determined that a sprinkler contractor was the cause for the accidental activation.
 

May 17 - 11:39 pm (Incident #128) - Report of a heavy odor of automobile exhaust in the lobby of an apartment complex. It was determined that the exhaust from an ambulance at the front door filled the lobby creating a potential carbon monoxide condition. Fire crews used a meter to check air quality. There were no elevated levels of carbon monoxide. The lobby was ventilated with an exhaust fan.
 

May 15 - 6:24 pm (Incident #127) - Report of an unknown type odor at a medical facility. It was determined that sewer gas was escaping into the building related to a plumbing problem.
 

May 15 - 5:35 pm (Incident #126) - Report of something burning beneath a deck at a private residence. It was determined that water had entered an exterior electrical power line conduit causing it to short circuit starting a small fire in the surrounding landscape mulch.
 

May 15 - 3:45 pm (Incident #125) - Report of an odor of natural gas at a borough-owned property. After a thorough search of the premises, no odor of gas was detected.
 

May 14 - 1:07 pm (Incident #124) - Fire alarm activation at a private residence. It was determined that water leaking from a toilet on the floor above leaked through the smoke detector on the floor below causing the activation.
 

May 14 - 7:59 am (Incident #123) - Report of a carbon monoxide detector sounding at a private dwelling. Fire crews used a meter to check air quality. There were no elevated levels of carbon monoxide found.
 

May 12 - 11:09 pm (Incident #122) - Fire alarm activation at an apartment complex. It was determined that an earlier plumbing problem caused a water flow alarm with the sprinkler system.
 

May 12 - 10:45 am (Incident #121) - Fire alarm activation at a mixed-use commercial/residential building in the central business district. An apparent alarm malfunction was caused by rooftop rain water leaking into the basement onto the fire alarm panel.
 

May 12 - 10:45 am (Incident #120) - Report of a smoke detector sounding at a private residence. After a thorough search of the residence, no cause for the alarm activation could be found.
 

May 11 - 2:15 pm (Incident #119) - Report of a fire alarm sounding at a commercial establishment under renovation in the central business district. Renovation contractors were the cause of the alarm activation.
 

May 10 - 10:18 pm (Incident #118) - Report of a carbon monoxide detector sounding in a residential dwelling unit at a building in the central business district. Fire crews used a meter to check air quality. There were no elevated levels of carbon monoxide present. It was determined that the detector was malfunctioning.
 

May 10 - 9:10 pm (Incident #117) - Report of a gas leak at a non-owner occupied two family dwelling. It was determined that the pilot light on the stove in the second floor apartment had gone out causing natural gas to leak.
 

May 9 - 5:22 pm (Incident #116) - Fire alarm activation at a residential facility for the developmentally disabled. It was determined that the facility was conducting a fire drill and the alarm was accidentally transmitted.
 

May 8 - 4:16 pm (Incident #115) - Fire alarm activation at a medical facility. It was determined that a person had lit a cigarette in a hallway which caused the smoke detector system to activate.
 

May 8 - 2:51 pm (Incident #114) - Fire alarm activation at a medical facility. It was determined that a maintenance contractor was the cause for the alarm activation.
 

May 6 - 11:33 am (Incident #113) - Fire alarm activation at an apartment complex. It was determined that cooking smoke from an individual apartment was the cause for the alarm activation.
 

May 3 - 3:15 pm (Incident #112) - Fire alarm activation at a residential facility for the developmentally disabled. It was determined that a contractor performing work was the cause for the activation.
 

May 2 - 2:54 pm (Incident #111) - Report of persons trapped in a stalled elevator at a medical facility. Upon arrival of fire officers, it was determined that the individuals had self-extricated.
 

April 2006

March 2006

February 2006