The elevator passed inspection.
The maintenance company investigated the complaints.
The equipment had been repaired and modernized over decades.
Then someone was injured. But what elevator was actually involved?
Applying the Failure Path Framework to a class of cases that often looks simpler than it is.
A woman steps out of an elevator. Another passenger selects a floor. The doors close on the woman's head and neck.
In Mayfield v. Mavrakis, that apparently straightforward incident became years of litigation involving maintenance records, witness testimony, competing experts, and disputed evidence about the elevator's condition.
The case raises an important question, but not necessarily the obvious one.
Before asking what went wrong with an elevator, do we know exactly what elevator we're examining?
Elevators can remain in service for decades. During that time, controllers may be modernized, door operators replaced, safety devices added, and mechanical components repaired. Different parts of the same system may have different histories and different applicable requirements.
The records describing that system may be scattered among property owners, maintenance contractors, inspectors, manufacturers, and regulatory authorities.
A passed inspection can be meaningful. So can a clean fault log, an unresolved complaint, or a mechanic's inability to reproduce a reported condition. Those observations don't necessarily contradict one another. They may describe different parts of the equipment, different operating states, or different moments in its history.
This issue of Field Signal applies the Failure Path Framework to several elevator cases, examining how equipment history, operating sequences, incomplete information, and premature assumptions can shape an investigation before the underlying mechanism is understood.
The Historical Stack — Why an elevator may contain components from different generations, with alterations and modernization affecting its configuration and potentially its applicable requirements.
The Component Versus the System — How a functioning safety sensor doesn't necessarily establish that every upstream component controlling its operation is functioning reliably.
The Problem of Opposite Symptoms — Why two apparently contradictory complaints may be unrelated, or may justify examining shared equipment and control logic before deciding.
The Timing of Observation — How an elevator's condition can change during its operating sequence, and why an inspection performed at one moment may not establish what occurred at another.
The Meaning of a Passed Inspection — What certificates, maintenance records, fault logs, callbacks, and user reports actually establish, and where their evidentiary limits may lie.
The Hindsight Test — How to distinguish information reasonably available before an injury from patterns assembled only after the outcome is known.
The Distributed Information Problem — Why no single owner, mechanic, inspector, manufacturer, or attorney may possess the complete equipment history and operational record.
The Failure Path Framework — How to recognize meaningful friction in an explanation, widen the investigation when justified, and avoid making every elevator incident unnecessarily complicated.
This issue is relevant to plaintiff and defense attorneys, premises liability professionals, elevator consultants, forensic engineers, building owners, property managers, insurers, risk professionals, and professionals responsible for elevator maintenance and inspection.
It's particularly useful for those examining elevator injury claims, maintenance and modernization histories, disputed inspection evidence, intermittent conditions, equipment configuration, and the relationship between technical findings and legal theories.
Yeagers Consulting brings over thirty-five years of construction, accessibility, and built-environment expertise to the Human-Use Lens and the daily lived experience of navigating commercial spaces across the full range of mobility and sensory need. Frank Yeager lives in the gaps: the space between what systems promise and what they deliver. That's where people get hurt. That's where he works.