Category: Fire & Safety

  • Fire Alarm Notification Circuit Load and Voltage-Drop Testing

    Fire Alarm Notification Circuit Load and Voltage-Drop Testing

    A notification appliance circuit can appear healthy at the panel yet deliver insufficient voltage at its farthest device during alarm. Commissioning should verify the installed load, conductor path, synchronization and power-source behavior under realistic worst-case conditions.

    Establish the design baseline

    Record the circuit class, conductor size, route length, appliance model, candela or sounder settings and power-supply rating. Compare the installed device count with the approved calculation. Field changes can increase current without appearing in the original drawing.

    Identify boosters, isolators, end-of-line components and any shared pathways. The test plan should state which output pattern will create the highest load and which environmental or battery assumptions apply.

    Measure at the critical point

    Place the system in alarm and measure voltage at the supply and at the electrically farthest notification appliance. Test the actual programmed pattern, including synchronized strobes and temporal sounders. Confirm that each device remains within its listed operating range.

    A no-load continuity measurement is not a substitute for an alarm-state test. Loose terminals, undersized conductors and unexpected splices may only become visible when current increases.

    Include secondary power and synchronization

    Repeat required checks with the system operating from secondary power under the conditions defined by the design and applicable code. Observe whether boosters transfer correctly and whether strobes remain synchronized across power-supply boundaries.

    Where multiple circuits serve one visible area, verify that timing differences do not create confusing patterns. Confirm audibility and visibility separately; acceptable circuit voltage does not prove that the notification objective is met in the occupied space.

    Document defects and retest

    Record panel voltage, end-device voltage, current, appliance settings, battery condition and test time. Link each measurement to a circuit identifier and drawing revision. Corrective actions may include repairing connections, redistributing loads or installing an approved power supply.

    Retest after adding appliances, changing settings, replacing batteries or altering circuit routing. Integrate the results with wider Fire Detection & Automatic Fire Protection maintenance records so future technicians can compare performance rather than relying on a simple pass label.

    Use measurements for lifecycle maintenance

    Trend end-of-line voltage and alarm current across recurring tests. Gradual movement can reveal battery degradation, added appliances or deteriorating connections before a circuit reaches its operating limit. Store readings with the panel configuration and approved drawing revision.

    After corrective work, repeat the worst-case alarm pattern from normal and secondary power. Verify that trouble signals clear normally and that no device remains disabled or bypassed. Maintenance evidence should identify the instrument, calibration status and technician so measurements remain comparable.

    Include representative ambient conditions and occupied-area constraints in the record. Review open deficiencies with the responsible fire-alarm designer or service organization, assign a due date and confirm closure through a witnessed retest rather than an administrative note alone.

    Reference sources

  • Oakland Apartment Fire Injures Four and Displaces About 70 Residents

    Oakland Apartment Fire Injures Four and Displaces About 70 Residents

    A three-alarm fire in a four-story East Oakland apartment building injured four residents and displaced about 70 people, according to local reporting based on fire-department information. The incident began shortly after midnight in the 5100 block of Bancroft Avenue, with smoke and flames visible from all four floors when crews arrived.

    Crews carried out rescues during escalation

    The response grew to a third alarm within minutes and involved about 65 firefighters. Crews rescued several occupants while others evacuated independently. Three adults and a nine-year-old child were taken to hospital for smoke inhalation and other injuries. No firefighter injuries were reported, and the fire was brought under control in a little over an hour.

    Officials described extensive damage, and the 21-unit building was red-tagged as uninhabitable. Emergency housing support was being arranged with assistance from the Red Cross. The cause remained under investigation at the time of reporting.

    Multi-unit incidents test several safeguards

    Apartment fires place simultaneous demands on detection, alarm audibility, protected escape routes, compartmentation and fire-service access. Post-incident reviews should examine whether alarms reached every occupied area, how smoke affected exits and whether resident accountability supported rescues. SectechMedia follows these engineering issues in its fire and life-safety coverage.

    Sources

  • Fire Alarm Ground-Fault Isolation and Circuit Restoration Testing

    Fire Alarm Ground-Fault Isolation and Circuit Restoration Testing

    A ground fault occurs when a supervised fire-alarm conductor makes an unintended connection to earth or grounded metal. The panel may continue operating while reporting trouble, but the fault can reduce supervision reliability and complicate a second fault. Troubleshooting should preserve life-safety coverage and produce evidence that the repaired circuit is stable.

    Start with impairment control

    Notify the responsible parties before disconnecting circuits or devices. Define compensating measures, monitoring arrangements and restoration responsibilities. Troubleshooting should not quietly leave notification appliances, initiating devices or communication paths unavailable.

    Record the panel message, affected node, time and recent work. Moisture, damaged insulation, pinched cables, contaminated devices and incorrect shielding are common contributors. A history of intermittent trouble can help narrow the environmental cause.

    Divide the circuit methodically

    Use approved drawings and isolate sections in a controlled sequence. Observe when the fault clears, then narrow the search within that branch. Avoid random disconnection because it can create additional trouble states and make the original condition harder to reproduce.

    Inspect junction boxes, outdoor devices, cable entries and locations affected by construction or water. Shield and drain conductors require particular attention because an unintended bond can produce confusing measurements.

    Verify the repair under operating conditions

    After correcting the cause, reconnect the circuit and confirm that the panel returns to normal. Operate representative devices beyond the repair point, verify notification or control outputs and confirm remote annunciation and monitoring communication.

    Intermittent faults may disappear when a box is opened or a cable is moved. Where practical, repeat the conditions that previously triggered the trouble and monitor the circuit long enough to establish stability.

    Close the impairment with evidence

    The service record should identify the affected circuit, isolation steps, cause, repair, test devices and final panel state. Update drawings if field wiring differed from the documentation. Remove temporary bypasses and confirm that all disabled points are restored.

    Ground-fault management is part of the broader Fire & Safety maintenance program. The objective is not merely to silence a trouble buzzer; it is to restore supervision, device operation and reliable fault reporting without leaving hidden changes in the system.

    Prevent repeat faults

    Review the repair with recent construction, cleaning, weather and water-ingress records. If several circuits show similar trouble, investigate shared pathways, power supplies and bonding practices rather than treating every alarm as an isolated cable defect.

    Trend ground-fault frequency, duration and affected location. Repeated short-lived faults deserve investigation even when the panel returns to normal before a technician arrives. Photographs, meter readings and the exact isolation sequence improve the next response and help determine whether cable replacement or environmental remediation is justified.

    Include restored supervision and monitoring confirmation in the closeout record. A stable normal condition should be observed at the panel and remote receiving point before the impairment is formally released.

    Reference sources

  • Michigan Plastics Plant Fire Disrupts Power Near South Haven

    Michigan Plastics Plant Fire Disrupts Power Near South Haven

    A major fire at East Jordan Plastics near South Haven, Michigan, spread from plastic pallets stored outside the facility into the factory and disrupted electrical service in parts of the community. Local reporting said smoke was visible for miles as multiple fire agencies responded.

    Propane explosions complicated the response

    South Haven Area Emergency Services said early propane explosions threw tanks into the air while crews worked the third-alarm incident. At least six agencies participated in the response. Employees evacuated safely, and no injuries had been reported in the initial public information.

    The fire’s proximity to critical electrical infrastructure added a second operational problem. The City of South Haven said an electric transmission feed was cut because the incident threatened a municipal utility substation. Power restoration depended on progress toward containment, and the public was asked to stay away from the area.

    Industrial incidents can cross system boundaries

    The event illustrates why industrial emergency planning must account for stored materials, pressurized containers, utility dependencies and access for mutual-aid crews. Detection and suppression systems are important, but pre-incident surveys, isolation plans and coordination with energy providers can determine how far consequences spread beyond a facility. SectechMedia follows related engineering risks in its fire and safety coverage.

    Sources

  • Smoke Detector Sensitivity Testing and Contamination Maintenance

    Smoke Detector Sensitivity Testing and Contamination Maintenance

    A smoke detector can remain connected and report normal communications while its sensing chamber becomes contaminated or its response drifts. Maintenance must therefore look beyond panel connectivity. Sensitivity testing, device diagnostics and environmental history provide evidence that a detector remains within its approved operating range.

    Understand what the system reports

    Addressable detectors may provide a sensitivity value, contamination level or maintenance alert. The meaning of those values is manufacturer-specific and must be interpreted with the approved documentation. A percentage or bar graph should not be converted into a pass decision without knowing the reference range and compensation method.

    Some devices automatically compensate for gradual contamination. Compensation can preserve performance for a period, but it is not unlimited and should not be treated as a substitute for cleaning or replacement. Record when the device approaches a maintenance threshold and whether the panel reports that state to operators.

    Test within an approved maintenance program

    Use methods permitted by the applicable code, authority and manufacturer. Functional aerosol testing confirms that smoke can enter the chamber and generate an alarm, while sensitivity testing evaluates the response threshold. Those are related but different questions, so one result should not be used to claim that both were tested.

    Coordinate impairment controls before testing. Notify monitoring parties, protect occupants and restore all disabled outputs after the work. The record should identify the detector, location, method, result, tester, equipment and any corrective action.

    Investigate the environmental cause

    Repeated contamination may indicate dust, construction activity, steam, aerosols, insects or unsuitable air movement. Cleaning the detector without addressing the environment can produce a cycle of nuisance alarms and early failure. Compare maintenance history across nearby devices to identify a local pattern.

    Confirm that detector type and placement remain suitable after room-use changes. A space converted into a workshop, kitchen or high-airflow area may need a design review rather than repeated adjustment. Settings should not be widened simply to silence alarms unless the change is engineered, approved and documented.

    Use trends to plan replacement

    Track devices that repeatedly approach contamination limits, fail sensitivity checks or require frequent cleaning. Trending supports risk-based replacement and helps identify batches exposed to similar conditions. It also distinguishes a single defective device from a broader environmental or design problem.

    Close maintenance by verifying normal panel state, remote annunciation, monitoring communication and updated records. Smoke-detector assurance supports the wider Fire & Safety program by proving that connected devices remain capable of performing their detection function, not merely responding on the network.

    Maintenance analytics should support, not replace, required inspection and testing. Assign responsibility for reviewing contamination trends and overdue work orders, and ensure technicians can trace every device result to its physical location. Any detector removed for service should remain controlled so that an untested device is not returned to the wrong address.

    Reference sources

  • Fire Alarm Loop Fault Isolation and Network Survivability

    Fire Alarm Loop Fault Isolation and Network Survivability

    A fire alarm system may appear normal at the control unit while a single cable fault threatens a large part of the detection or notification path. Loop isolators, redundant communications and supervised circuits are intended to limit that impact, but their value depends on design, placement and testing. Acceptance should prove what remains operational after realistic faults.

    Map the intended fault boundaries

    Start with drawings that show signaling-line circuits, notification circuits, isolators, network nodes, power supplies and interfaces. Identify which devices are expected to remain available after an open circuit, short circuit or node loss. The drawing should match the installed field route, not only the tender design.

    Fault isolation is affected by physical topology. Devices on both sides of an isolator may not fail in the way an operator expects if the cable route, address sequence or return path changed during construction. Record fire compartments, risers and critical functions so the test can assess consequence as well as device count.

    Test faults under controlled conditions

    Introduce approved test faults one at a time using a documented method that protects people and equipment. Confirm the control unit identifies the correct circuit or segment, annunciators receive the condition and unaffected devices continue to operate. Measure how long isolation and restoration take and whether repeated faults produce additional loss.

    An open circuit, short circuit and network communication failure can have different effects. Test representative locations, including boundaries near isolators and remote power supplies. Where a fault could disable a safety function, coordinate compensating measures and restore the system immediately after the evidence is collected.

    Verify interfaces and degraded operation

    Fire alarm systems often control doors, smoke control, elevators, suppression interfaces and monitoring connections. A field loop may retain detectors while losing an interface module that supports another life-safety action. The acceptance matrix should therefore verify required cause-and-effect behavior in the degraded state.

    Confirm that off-site monitoring receives fault and restoration events with correct timestamps. Networked panels should maintain required indications when a peer node or communications link is unavailable. Cybersecurity controls must not block supervised traffic, while maintenance access should remain authenticated and logged.

    Preserve evidence for maintenance

    Close the test with updated drawings, device lists, software versions, fault results and unresolved limitations. Operators need plain-language information about which area is affected by a reported fault and what temporary action is required. A generic trouble message without location or consequence is difficult to manage safely.

    Repeat selected tests after rewiring, expansion, firmware changes or unexplained communication faults. Fire network survivability supports the wider Fire & Safety program by making single-fault behavior visible before an emergency exposes it.

    Coordinate testing with the authority having jurisdiction and the site’s impairment procedure where required. Notify affected occupants and monitoring parties before the exercise, then confirm that normal supervision has been fully restored.

    Reference sources

  • UL FSRI Updates Evidence-Based Structural Firefighting Course

    UL FSRI Updates Evidence-Based Structural Firefighting Course

    UL’s Fire Safety Research Institute has updated its Evidence-Based Structural Firefighting course to connect current fire-dynamics research with operational decision-making. The free online course was updated on September 22 and is designed for both firefighters and personnel responsible for training, policy and procedural consistency.

    New search-and-rescue and hazard content

    FSRI says the revision adds lessons built around 12 tactical considerations from its search-and-rescue research. It also expands guidance on coordinating search, rescue, suppression and ventilation before, during and after fire control. Additional material addresses implementation of NFPA 1700 guidance and emerging hazards including photovoltaic systems and battery fires.

    The course page lists 151 minutes of instruction covering fire science, construction, heat transfer and personal protective equipment, suppression, ventilation, search and rescue, and implementation. It includes a final assessment and certificate of completion. The program is educational guidance rather than a universal incident playbook; departments still need to adapt tactics to staffing, construction, water supply, local procedures and incident conditions.

    From research to operating guidance

    The practical challenge is translating fire research into repeatable training and standard operating guidance without treating one tactic as appropriate for every structure. FSRI’s accompanying fireground playbook is intended to help departments organize evidence-based considerations for their own operations. SectechMedia follows related developments in its Fire & Safety channel.

    Sources

  • Unauthorized Drones Interrupt Aerial Firefighting at California’s Timber Fire

    Unauthorized Drones Interrupt Aerial Firefighting at California’s Timber Fire

    Unauthorized drones have disrupted aerial firefighting around California’s Timber Fire, forcing pilots to suspend or redirect operations while unidentified aircraft were inside restricted airspace. The incident was highlighted in September 22 coverage after local authorities had issued temporary flight restrictions for the Timber and Plaskett fires in Monterey County.

    Why a small drone can halt an air operation

    Firefighting aircraft often work at low altitude, in smoke and close to terrain. A drone that is difficult to see can create a collision hazard for helicopters and fixed-wing tankers, so incident commanders may ground aircraft even when no impact has occurred. The result can remove reconnaissance, water-drop and retardant-drop capacity during a fast-changing emergency.

    Temporary flight restrictions are therefore an operational safety control, not merely an administrative boundary. Public messaging, geofencing information, remote identification and rapid reporting can help reduce accidental incursions, while counter-UAS decisions still have to comply with aviation and communications law.

    Security and resilience lesson

    The Timber Fire disruption illustrates the link between counter-UAS and airspace security and emergency-response continuity. Agencies need clear detection, identification and escalation procedures so that drone reports can be assessed quickly without creating additional risk to responders or the public.

    Sources

  • Fire Alarm Cause-and-Effect Matrix Testing Explained

    Fire Alarm Cause-and-Effect Matrix Testing Explained

    A fire alarm cause-and-effect matrix defines what the building should do when a specific input or combination of inputs occurs. A smoke detector may initiate evacuation signals, release doors, recall elevators, stop air-handling equipment and notify a monitoring center. Testing the detector alone does not prove that this sequence works.

    What the matrix should contain

    The matrix normally lists initiating events on one axis and required outputs on the other. Inputs may include automatic detectors, manual call points, sprinkler flow, supervisory signals and faults. Outputs can include notification zones, smoke-control commands, fire-door release, elevator interfaces, suppression release logic and messages to external monitoring.

    The document must reflect the approved fire strategy and applicable code requirements. It should identify delays, coincidence logic, dependencies and exceptions. Generic text such as “all systems operate” is not testable. Each expected action needs an observable result and a responsible discipline.

    Prepare an integrated test

    Before testing, confirm that the matrix version matches the installed programming and current building layout. Coordinate fire alarm, mechanical, elevator, door, suppression and monitoring contractors. Notify occupants and authorities as required, establish impairment controls and prevent an unintended emergency response.

    Tests should be planned so that inputs and outputs are observed at their real interfaces. A software indication at the fire panel is not proof that a damper moved or a door released. Where testing a physical action is unsafe or impractical, the alternative method and limitation should be documented.

    Test sequences, failures and recovery

    Verify single inputs, combined inputs and reset behavior. Confirm that priorities are correct when fire and security commands conflict. Door access control, for example, must not prevent the required life-safety release. Check how the system behaves during communication loss, disabled points and power transfer.

    Recovery matters as much as activation. After reset, equipment should return to the intended state without leaving doors, fans or interfaces in an unsafe condition. Operators need a clear indication when a field device requires manual restoration.

    Include negative tests where they can be performed safely. A supervisory input should not start an evacuation sequence unless the approved design calls for it, and an isolated output should generate a visible impairment rather than failing silently.

    Evidence and change control

    Record the test input, expected output, observed result, time, witness and defect. Screenshots can support the record but should not replace signed field observations. Defects must be corrected and the affected sequence retested; broad statements that a problem was “resolved” are insufficient.

    Any later change to fire logic, access control, elevators or smoke control should trigger matrix review. This discipline connects fire detection and automatic protection with the systems it commands. A tested matrix provides evidence that the building responds as a coordinated life-safety system rather than a collection of individually functional components.

    Reference sources

  • Streamlight Launches Hazard-Rated Side-Mounted Firefighter Helmet Light

    Streamlight Launches Hazard-Rated Side-Mounted Firefighter Helmet Light

    Streamlight has introduced the SL-SideSaddle HAZ-LO, a side-mounted helmet light aimed at firefighting and rescue work in locations where equipment may need a hazardous-location rating. International Fire and Safety Journal reported the launch on 21 September.

    Helmet-mounted lighting as safety equipment

    A helmet light keeps both hands available and can illuminate the direction in which the wearer is looking. Side mounting is intended to reduce interference with other helmet components, but fit must be assessed with the complete ensemble, including face protection, communications equipment and breathing apparatus. A light that catches on equipment or changes helmet balance can create a new problem.

    Hazardous-location suitability should be confirmed against the exact certification and operating environment rather than inferred from the product name. Users also need to follow battery, charging and inspection instructions. Damage to seals or housings can invalidate assumptions made at procurement.

    Deployment considerations

    Fire services should test beam pattern, controls and glove usability under realistic visibility conditions. Equipment checks should be incorporated into routine readiness procedures, including battery state and secure attachment. The product sits within a broader emergency and life-safety system in which personal lighting supports, but does not replace, team communications and scene illumination.

    Sources