What Uptime Is Actually Worth: Monitoring Airport Escalators, Elevators, and Moving Walkways

Ask an airport facilities director how many escalators they have and you will get an exact number. Ask how many were running yesterday at 3 p.m. and the answer gets vague. That gap is not a failure of competence. It is the predictable result of managing hundreds of conveyance units, spread across millions of square feet, built by different manufacturers across four decades, most of which were installed without any way to report their own status.

The result is an operation that finds out about downtime the same way it did in 1995: someone calls it in. A gate agent, a custodian, a passenger at an information desk. By the time the work order opens, the unit has often been down for an hour or more, and nobody can say exactly how long because there is no record of when it stopped.

The case for monitoring conveyance uptime is usually made as a maintenance argument. That undersells it. The more accurate framing is that uptime data changes four separate things at once: how fast you respond, how you hold vendors accountable, how you defend your accessibility obligations, and how you decide where capital goes. This article walks through each, and what the monitoring layer actually costs.

Table of Contents

• 1. What a Stopped Unit Actually Costs
• 2. The Metric Nobody Tracks: Detection Lag
• 3. Uptime Data Changes the Vendor Conversation
• 4. Elevator Downtime Carries Legal Exposure
• 5. Repeat Offenders Reveal Themselves
• 6. The Failures Nobody Attributes Correctly
• 7. Building the Business Case
• Where to Start

1. What a Stopped Unit Actually Costs

A stopped escalator is not a stopped escalator. It is a stairway that most passengers can still use, a barrier for some, and a bottleneck for everyone during a bank of arrivals. The cost shows up in places that never get attributed back to the equipment.

Passenger flow is the first. Terminal circulation is designed around assumed throughput at specific pinch points. Take one moving walkway out of service in a long connector and the walk time between gates changes materially for every passenger in that concourse. During an irregular operations day, that is the difference between a made connection and a missed one.

The second cost is labor you did not plan for. A down unit in a high-traffic area frequently pulls staff to manage crowding, redirect passengers, or escort travelers who cannot use the alternative route. None of that appears on the maintenance work order, but all of it is real payroll.

The third is reputational and it compounds. Airports are measured on passenger satisfaction surveys, and terminal circulation is one of the categories travelers notice and remember. Concessions revenue is also directly tied to foot traffic patterns. A walkway that has been down for three weeks in a concourse does not just annoy people. It quietly reroutes them past a different set of storefronts.

2. The Metric Nobody Tracks: Detection Lag

Most airport maintenance organizations track mean time to repair. Very few track the interval before that one: the time between when a unit actually stopped and when the maintenance team learned it stopped.

That interval is invisible precisely because nothing measures it. If your detection method is a phone call, then the recorded outage begins at the phone call, and any time before that is simply erased from the record. A unit that stops at 5:40 a.m. and gets reported at 7:15 a.m. shows up in the system as a 90-minute-shorter outage than it was.

This matters for two reasons. First, the total downtime you are reporting to airport leadership is understated, sometimes substantially, which means the case for capital replacement is understated too. Second, detection lag is the single most improvable number in the whole chain. Cutting repair time requires more technicians, more parts inventory, or a better contract. Cutting detection lag to near zero requires a sensor that knows whether a motor is running.

A wireless contact or switch sensor reads run and stop state directly. A current sensor on the drive motor accomplishes the same thing by watching load. Either way, the console knows within seconds, and the alert reaches a supervisor’s phone by SMS, email, or voice call before the first passenger complaint is filed.

3. Uptime Data Changes the Vendor Conversation

Most airports do not maintain their own vertical transportation. They contract it, often to the original equipment manufacturers, across multiple contracts covering different terminals and equipment generations. Those contracts increasingly include availability expectations.

Here is the structural problem: in most airports, the only performance data available in that relationship comes from the vendor. The contractor reports response times and unit availability, and the airport has no independent means of verifying either. That is an uncomfortable position for a contract manager, and it is not a reflection on any particular vendor. It is just bad information architecture.

Independent, vendor-neutral status data resolves it. When the airport has its own timestamped record of when each unit stopped, when it came back, and how many times it cycled in between, quarterly performance reviews stop being a negotiation over recollections. They become a review of a shared record. Airports that have deployed this consistently report that the conversation changes character entirely, and usually within one contract cycle.

There is a related benefit worth naming. Equipment from different manufacturers reports through different proprietary platforms, if it reports at all. Older units report through nothing. Maintenance teams end up logging into several systems and manually aggregating to produce a single performance picture. A vendor-neutral condition monitoring layer sits above all of that and produces one view of the entire installed base regardless of who built each unit or what decade it was built in.

4. Elevator Downtime Carries Legal Exposure

Escalators and moving walkways are convenience infrastructure. Elevators are frequently the only accessible route, and that changes the legal character of an outage.

Under the ADA, public entities are required to maintain accessible features of their facilities in operable working condition. The rule at 28 CFR 35.133 states the obligation plainly, and it explicitly permits isolated or temporary interruptions for maintenance and repair. A parallel obligation applies to public accommodations under Title III. The regulation does not set a specific number of hours, and a short outage handled promptly is not the concern.

The exposure comes from two patterns. One is a prolonged outage on a unit that is the only accessible path to a gate area, a ticketing level, or a parking structure. The other, less obvious and more common, is a repeated pattern of outages on the same unit without evidence of a durable fix. In both cases, the practical question that gets asked afterward is the same: what did the airport know, when did it know it, and what did it do about it.

Continuous monitoring does not make an airport compliant. Nothing purchased makes an airport compliant. What it does is produce the record that answers those three questions, and it shortens the interval that creates the exposure in the first place. Knowing an accessible elevator is down at 4 a.m. rather than at 9 a.m. is five hours of risk you no longer carry.

5. Repeat Offenders Reveal Themselves

Every airport has them. The escalator in the connector that goes down every few weeks. The elevator in the parking garage that everyone jokes about. They persist because the failures are individually small, each one gets a service call, each service call closes, and nobody assembles the pattern.

Continuous status logging assembles the pattern automatically. Once you have twelve months of run and stop history across the installed base, the ranking is unambiguous. You can see which units account for a disproportionate share of total downtime, which ones fail on a schedule that correlates with peak passenger load, and which ones have been degrading steadily rather than failing randomly.

That ranking is the single most useful input to a capital planning conversation. Replacement and modernization budgets for vertical transportation are large, competitive, and typically justified with equipment age and anecdote. Age is a weak proxy. A well-maintained thirty-year-old unit can outperform a poorly specified twelve-year-old one. Downtime hours per unit per year is the metric that actually reflects what the equipment is costing you, and it is only available if something has been counting.

6. The Failures Nobody Attributes Correctly

Some of the most common causes of conveyance downtime are not conveyance problems at all, which is exactly why they persist.

Machine room temperature. Modern elevator controllers are microprocessor-based and heat sensitive. ASME A17.1 requires machine rooms to be kept within the temperature and humidity range specified by the equipment manufacturer, with that range posted in the room, and building codes generally require a dedicated ventilation or air conditioning system serving that space, with a default range around 55 to 90 degrees Fahrenheit where no manufacturer specification exists. When the dedicated mini-split serving a machine room fails, the room climbs, and the controller faults out. The elevator gets the service call. The air conditioner gets nothing, so the same failure recurs next month. A single ambient temperature sensor in each machine room catches this class of failure permanently, and it is arguably the highest return per sensor in the entire deployment.

Pit and shaft water. Elevator pits are required to be kept dry. In practice, groundwater intrusion, sprinkler discharge, wash-down runoff, and failed sump pumps all put water where it does not belong. The resulting damage is expensive, the outage is long, and the discovery is usually late. Wireless water detection in pits and adjacent equipment spaces turns a multi-day repair into a maintenance ticket.

Mechanical degradation. Escalator and moving walkway drives, gearboxes, and step chains announce themselves before they fail. Vibration amplitude trending upward against an established baseline for that specific unit is one of the most reliable early warnings in rotating machinery, and motor current drifting up over weeks tells a similar story about increasing mechanical resistance. Neither is visible to a technician on a scheduled walk-through, because the change is gradual and the reference point is a number nobody wrote down.

Upstream power. Voltage anomalies and phase issues on the supply side produce conveyance faults that get diagnosed as conveyance failures. Monitoring the electrical supply at the unit separates the two.

7. Building the Business Case

The economics here are unusual because the monitoring layer is inexpensive relative to what it is monitoring. A single escalator modernization is a six-figure capital project. Monitoring the entire installed base is not.

A representative Swift Sensors configuration covering two escalators and a pump runs about $1,070 in year one including hardware and the monitoring plan, and $225 per year thereafter. Set that against the things it is working to avoid: labor hours spent on physical inspection rounds, service disruptions that damage passenger perception, avoidable equipment damage, and the cost of discovering problems late rather than early.

The deployment characteristics matter as much as the price in an operating terminal. Sensors are smaller than a credit card and run six to eight years on two AAA lithium batteries. They communicate over Bluetooth 5 to a gateway supporting up to 150 sensors within a 500 foot radius, so a concourse is typically covered by very few gateways. With an optional cellular module, sensor data reaches the cloud console without touching the airport network, which removes the IT review that stalls many terminal technology projects. And because nothing needs to be wired, installation does not require closing a concourse or scheduling around passenger traffic.

Maintenance leaders at major airports describe the value in fairly plain terms. One maintenance services manager at a major international airport put it as a relatively simple add-on to their conveyance systems that gave them visibility they never had before, letting them address escalator or moving walkway issues before they caused major backups. That is the whole proposition. Not prediction, not analytics. Knowing sooner.

Where to Start

You do not need to instrument everything at once, and airports that try usually stall. A workable sequence:

• Start with run and stop status on your highest-traffic units. Status alone, with no condition monitoring, eliminates detection lag and starts building the downtime history you will need for every later argument.
• Add every accessible-route elevator next. These carry the regulatory exposure. Prioritize the ones that are the sole accessible path to a gate area, ticketing level, or parking deck.
• Put a temperature sensor in every elevator machine room. Low cost, high yield, and it catches a failure mode that is currently being misattributed to the elevator.
• Add water detection to pits and equipment rooms. Cheap insurance against the most expensive category of avoidable damage.
• Layer vibration and current monitoring onto your known repeat offenders. Once you have downtime rankings, you will know exactly which units justify the extra instrumentation.
• Report uptime by unit, monthly, to leadership. The data only changes decisions if it reaches the people making them.

Swift Sensors supports this progression with wireless contact and switch sensors for run and stop status, vibration amplitude sensors for mechanical condition, voltage and current sensors for electrical load, ambient temperature and humidity sensors for machine rooms, water detection for pits, and a universal analog adapter that brings legacy instrumentation into the same console. Everything reports into one cloud platform with configurable alerts, historical trend analysis, automated reports, and an API for pushing data into an existing work order or asset management system. You can see the full airport picture on our airport monitoring page, or review deployment requirements on the system components page.

The Underlying Point

Conveyance equipment in airports is expensive, heavily used, highly visible, and, in most terminals, almost entirely unobserved between scheduled inspections. The industry has largely accepted that as normal because the alternative used to mean running conduit through an active terminal.

It does not mean that anymore. The gap between what an airport spends on this equipment and what it knows about this equipment is now a choice rather than a constraint. Closing it does not require a modernization program or an integration project. It requires putting something on the machine that can tell you whether it is running, and then paying attention to what it says.

Talk to Us About Your Terminal

If you are working through conveyance uptime, vendor performance reporting, or accessible route monitoring across your terminals, we would be glad to walk through what a first deployment looks like. Ask a question, request a demo, or get a quote on the Swift Sensors contact page. If you think it cannot be monitored, tell us about it. We might surprise you.