A voice alarm system that fails during an actual emergency isn't found out during the emergency — it's found out three months earlier at a weekly test that got skipped, or a standby amplifier that never actually kicked in during a fault simulation. Terminal PA/VA systems sit at the exact intersection of life safety and daily operations: the same speakers announcing gate changes are the ones expected to broadcast intelligible evacuation instructions to thousands of passengers during a fire event, and BS 5839-8 and NFPA 72 both treat that dual role with a testing regime stricter than most airports' internal logs actually reflect. The standard requires weekly call-point activation tests, annual intelligibility measurements, N+1 amplifier redundancy so no single failure drops sound below spec in any zone, and battery backup capable of 24 hours standby followed by a full 30-minute alarm. This guide covers the testing cadence, the redundancy standard, and the audit-ready record-keeping a modern airport CMMS should be handling automatically. Schedule a Demo to see OxMaint track PA/VA test compliance zone by zone across your terminal.
Aviation · Terminal Life Safety · PA/VA CMMS Guide 2026
Best Airport PA/VA Maintenance Software: The 2026 Compliance Guide
Weekly zone tests, annual intelligibility checks, and N+1 amplifier redundancy — the BS 5839-8 / NFPA 72 standard for terminal voice alarm, and how to keep the audit trail airtight.
Weekly
Required call-point activation test confirming broadcast in correct zones
N+1
Standby amplifier redundancy standard — no zone may drop below 6dB of target
24 hr + 30 min
Required battery backup: standby followed by full alarm broadcast
Annual
Full intelligibility measurement required at commissioning and each annual inspection
The PA/VA Testing Cadence — What's Actually Required, and When
These intervals aren't optional best practice — they're the baseline BS 5839-8 and NFPA 72 both build around. Start a free workspace and set every one of these on an auto-scheduled recurring PM.
Weekly
Activate at least one call point or panel test alarm — confirm correct message broadcasts in the correct zone.
Quarterly
Battery condition check, amplifier fault-indication test, control panel circuit verification.
Semiannual
Notification appliance functional testing — every speaker checked for audibility across covered zones.
Annual
Full intelligibility measurement, standby amplifier failover test, and complete device-by-device inspection.
Zone Redundancy — Why "One Speaker Down" Should Never Mean "One Zone Silent"
The redundancy requirement is specific: the failure of any single amplifier must not drop sound level in any zone below 6dB of the design target, and the standby unit must switch over automatically — no manual intervention.
1
Primary Amplifier Fails
Fault generates an indication at both the system controller and the fire alarm panel.
→
2
Standby Takes Over
Automatic switchover — the standby unit must carry the full load of any one failed amplifier.
→
3
Zone Stays Within Spec
Sound level in the affected zone never drops more than 6dB below the design target.
A Skipped Weekly Test Is Invisible — Until an Auditor Asks for the Log
OxMaint auto-generates the weekly, quarterly, semiannual, and annual PA/VA tasks per zone, flags any missed test before it becomes a compliance gap, and exports the full record in one click.
What an Auditor Actually Asks For
These are the records a BS 5839-8 / NFPA 72 audit routinely requests first — and the ones a spreadsheet consistently struggles to produce quickly.
1
Weekly Test Log Per Zone
Proof every zone was activated weekly, not just the panel as a whole.
2
Annual Intelligibility Report
The measured result, not just a checkbox confirming "tested."
3
Battery Backup Verification
Confirmed 24-hour standby plus 30-minute full alarm capacity, logged per test cycle.
4
Standby Amplifier Failover Proof
A logged test confirming automatic switchover actually occurred, not just that it's installed.
Paper Compliance Log vs. OxMaint
"
We had a strong weekly test habit at the panel level, but when an auditor asked us to prove every individual zone had actually been activated that week — not just that someone pressed a test button somewhere — we couldn't produce it cleanly. Moving zone-by-zone testing into a system that time-stamps each one changed that conversation completely at our next inspection, and it surfaced two zones that had quietly been skipped for months.
Terminal Facilities Manager · Mid-Size International Airport
Frequently Asked Questions
How often must a terminal voice alarm system be tested?
BS 5839-8 requires a weekly test activating at least one call point or panel-initiated test alarm, confirming the correct message broadcasts in the correct zone. Full intelligibility measurement is required only at commissioning and at each annual inspection.
What is the amplifier redundancy requirement for voice alarm systems?
The standard requires that the failure of any single amplifier must not drop the sound level in any zone below 6dB of the design target, with an automatic standby amplifier switchover — no manual intervention required.
What battery backup capacity is required?
The system must sustain 24 hours of standby power followed by a full 30-minute alarm broadcast at full load, powering all amplifiers, the system controller, and all active speakers.
Does NFPA 72 apply the same testing intervals as BS 5839-8?
Not identically — NFPA 72 sets its own schedule ranging from quarterly to semiannual and annual testing, plus additional requirements like two-year smoke detector sensitivity testing, but both codes share the same underlying principle of documented, interval-based verification by qualified personnel.
Can OxMaint track PA/VA compliance separately for each terminal zone?
Yes. Each zone is logged as its own asset with its own weekly, quarterly, semiannual, and annual test schedule, so a missed test in one zone is flagged independently rather than hidden inside a facility-wide average.
What happens if an intelligibility test result comes back below spec?
A failing intelligibility result should trigger an immediate corrective work order — commonly re-aiming or adding speakers, addressing acoustic interference, or replacing a degraded amplifier — followed by a re-test before the zone is considered compliant again.
Stop Reconstructing PA/VA Compliance the Week Before an Audit.
OxMaint auto-schedules every weekly, quarterly, semiannual, and annual PA/VA test by zone, flags missed tests instantly, and exports a full audit package in one click.
