Airports and transport hubs: emergency sound maintained around a live operation

What brings a transport operator to this page?

A fault on the control room display that nobody could trace to a circuit, or say how long it had been there. A retender where the reports list visits, not readings. Thin records for a system that has grown with every refurbishment. And, where the premises are in scope, the communication procedure under Martyn's Law, expected to commence in spring 2027 with no date set (SIA update, 11 September 2026), which an existing PAVA may be able to deliver. What the Act asks of venues.

Which standards apply at an airport or transport hub?

BS 7827:2019 covers large public buildings and venues, which includes major transport hubs, and recommends a risk assessment dividing the site into voice-alarm zones and emergency-sound-system zones (BS 7827:2019, Clause 4.1). The connection to fire detection decides which standard each zone follows, not the building. A zone triggered by fire detection follows BS 5839-8:2023: fault indication within 100 s (BS 5839-8:2023, Clause 10.1), servicing at intervals not exceeding six months (Clause 40.1), and annual activities including every loudspeaker circuit impedance measured and compared with the previous year's (Clause 40.2). A zone whose emergency broadcast is independent of fire detection follows BS EN 50849:2017, a specification whose provisions are requirements, including fault indication within 100 s (Clause 5.3) and a power supply that depends on whether the building is evacuated on mains failure (Clause 5.6).

Above both, BS 7827 recommends fault monitoring in three tiers: a generic fault to the fire system, zone-level faults for the control room, and component-level diagnostics for the technician, every fault logged with the time it occurred and the time it cleared (Clause 18). That keeps diagnostic detail away from the control room during an incident, and gives the technician more to work from than a single fault lamp.

What does a maintenance visit have to prove in a live terminal?

That the system as it stands today works, zone by zone, and that the record shows it: control equipment, amplifiers and the loudspeaker circuits, not just the panel; changeover to standby power demonstrated, not assumed; the fault log read against the logbook, so a fault that cleared itself between visits is still a finding.

Does your fire contractor already service the PAVA? Then the last report should list an impedance reading for every loudspeaker circuit, next to last year's. If it does not, they cannot be shown to have been measured. Every visit produces a record you could present to a regulator, insurer, or incident investigator today.

Between visits, BS 5839-8 recommends a call-out agreement for the repair of faults and damage (Clause 41.2); like-for-like replacement is repair, not modification. The technician who finds the fault does not price the fix. Repairs are quoted separately, so nothing is gained by missing a fault.

Where this has been done

Gatwick Airport. Emergency sound systems across one of the UK's busiest international airports, where system failure during an incident is not an abstract risk. On the complete PAVA system, ProAudium supports the airport's own Life Safety Systems (LSS) team with maintenance and technical support.

Which service does a transport hub need first?

A fault on a live system needs the circuit found and the fix quoted separately: fault-finding and repairs. The scheduled visits that stop the next one are voice alarm maintenance.

Start the conversation. Five fields, or 01273 034 630. Start the conversation