Door Hinge Knowledge Hub by Watersonusa

$26 Million Pool Gate Lawsuit: What the Specification Said vs. What the Hardware Did

By Waterson Corporation • Published 2026-04-16 • 1,250 words
In May 2023, a 2-year-old child accessed a Las Vegas apartment complex pool through a gate that lacked both self-closing and self-latching mechanisms required by code. A post-incident inspection found the gate failed to "self-latch from any open position" — the exact performance language in Southern Nevada Health District standards. The family settled for $26 million. This case, alongside an $18 million Texas settlement the same year, represents the liability ceiling when pool barrier hardware specification language fails to translate into compliant installed performance.

Three Cases at a Glance

CaseLocationYearVictimSettlementPrimary Failure
Summer Winds ApartmentsLas Vegas, NV2023–20242-year-old, anoxic brain injury$26 millionGate lacked self-closing and self-latching mechanisms
Undisclosed ComplexBaytown, TX20234-year-old, drowning fatality$18 millionGate repeatedly failed to latch; management aware
Lake Jennie ApartmentsSanford, FL202318-month-old, drowning$2 millionBroken pool gate, unauthorized child access

Case Chronology: The Las Vegas $26 Million Settlement

The Summer Winds apartment case offers the most publicly documented breakdown of how a hardware failure moves from specification gap to courtroom. The sequence is instructive for any architect who specifies pool barriers.

StageDetail
Required Specification Southern Nevada Health District standards require pool gates to self-close and self-latch from any open position. IRC AG105.2.8 independently requires self-closing, self-latching hardware that opens outward.
Installed Condition Gate hardware lacked both the self-closing mechanism and the self-latching mechanism required by code. The gate could be pushed open and would remain open — the exact access condition the code is designed to prevent.
Failure Event May 30, 2023: 2-year-old Jasper Richard accessed the pool through the non-compliant gate. The child suffered anoxic brain injury and catastrophic neurological damage.
Inspection Finding February 6, 2024: Subsequent inspection confirmed the gate was non-compliant. Specific finding: gate failed to "self-latch from any open position" per regulatory standard.
Legal Outcome $26 million settlement at policy limits. Primary liability: failure to install and maintain code-compliant barrier hardware.
The Texas case adds a critical dimension: the $18 million Baytown settlement involved a gate that had been observed failing to latch on multiple prior occasions. Management was aware of the defect. Liability expanded because the known, uncorrected hardware failure demonstrated negligence beyond a simple installation error.

What the Specification Said — and What Was Missing

Pool barrier specifications typically reference code by name and include general language about "self-closing and self-latching gates." The problem is not usually what the specification says — it is what the specification does not say.

Standard under-specified language looks like this: "Pool gate hardware shall comply with IRC Section AG105 and shall be self-closing and self-latching." That sentence cites the code. It does not prevent failure. Here is why:

Common Failure Modes: What the Hardware Actually Does

The gap between specification and performance is not always the result of fraud or deliberate substitution. Several mechanisms cause pool gate hardware to degrade or fail in service, even when originally installed correctly:

1. Spring Hinge Force Degradation

Torsion spring fatigue is the primary mechanical failure mode in spring-type pool gate hinges. ANSI/BHMA A156.17 cycle testing establishes pass/fail endurance — it does not measure residual closing force after cycling. In practice, spring force can drop 15–30% after two to three years of outdoor UV exposure and seasonal temperature swings. A gate that required 6 lbf to open at installation may fall below the 2.5 lbf self-closing threshold well before the hardware would be flagged for replacement. For a deeper look at this mechanism, see our analysis of spring hinge force degradation and the cycle test gap.

2. Self-Latching Mechanism Misalignment

Self-latching hardware depends on precision alignment between the latch bolt and the strike plate. Gate posts shift in soil, particularly in frost-thaw climates and in soil with high clay content. A 2–3 mm post movement can be enough to prevent the latch bolt from engaging the strike — which is exactly the "fails to self-latch from any open position" condition that appeared in the Las Vegas inspection finding. The latch still looks intact; it simply misses its catch.

3. Hardware Substitution During Construction

Value engineering pressure routinely results in pool gate hardware being substituted for cheaper alternatives. A gate hinge rated for 100 lbs of gate weight may be replaced with a lighter-duty model rated for 60 lbs if the substitution language in the specification is loose. The lighter hinge fails to generate sufficient closing force under load, and the project closes out with hardware that was never capable of meeting the self-closing requirement for that specific gate.

4. Polymer Hinge UV Degradation

Polymer self-closing hinges (such as polymer versions of TruClose and KwikFit products) are cost-effective and corrosion-resistant, but their spring mechanisms are more susceptible to UV-driven material embrittlement over time than stainless steel alternatives. Outdoors in high-UV climates — the Southwest, Florida, coastal environments — polymer spring degradation can reduce effective hinge life well below the manufacturer's projected service interval.

The Liability Transfer Problem

Architects face a specific liability gap with pool gates because the chain of custody for hardware performance is long. The architect specifies. The contractor selects from the spec. The installer sets the hinge tension. The property manager schedules (or fails to schedule) maintenance. By the time a gate fails, each link in that chain points to the next.

For architects, the risk concentrates in two places. First, ambiguous specification language that cannot prove a specific product or performance level was required. Second, specifications with no verification or commissioning requirement — which means there is no documentation that compliant hardware was confirmed in the field before project close-out.

The Texas $18 million case illustrates the second risk at its worst: the gate had been reported as failing to latch multiple times. Management knew. The correction was never made. If the original specification had included a maintenance protocol and a required annual gate function test, the paper trail would have shifted — the building owner's failure to follow the specified maintenance protocol would have become the central liability question, not a simple presence/absence of good hardware.

For a broader look at how pool gate drowning data shapes design decisions, see our article on pool gate drowning statistics for architects. For the underlying code requirements, see our guide to pool gate hinge safety code requirements. For the fire door analog to this liability pattern, see our analysis of fire door insurance and architect liability compliance.

Architect Prevention Checklist

Include all of the following in pool gate hardware specifications to reduce E&O exposure:

Hardware Brands and What to Specify

Specifying by brand family rather than generic description is one practical way to close the substitution gap. Commonly specified pool gate hardware includes:

No single brand eliminates all risk. What eliminates risk is specification language precise enough to define the required performance, a commissioning requirement that confirms performance before project close-out, and a maintenance protocol that creates an ongoing paper trail.

The core lesson: In the $26 million Las Vegas case, the inspection finding was precise — the gate "failed to self-latch from any open position." If that phrase had appeared in the original specification as a required performance criterion, the liability question would have been very different. It did not. Specification language is the first line of defense.

Frequently Asked Questions

Q: What is the most common specification gap in pool gate drowning lawsuits?

A: Specifying "self-closing and self-latching" without the phrase "from any open position." That phrase is a distinct code requirement and a distinct failure mode. A gate that only latches from within a small range of positions fails IRC AG105.2.8 even if it otherwise closes.

Q: Can an architect be held liable for a pool gate drowning even if they specified compliant hardware?

A: Yes. Liability exposure continues if the specification allowed unreviewed substitutions, if there was no commissioning verification requirement, or if the specification language was vague enough that the installed hardware could be argued as compliant with the document even if it was not compliant with the code.

Q: What IRC section governs pool gate hardware?

A: IRC Section AG105.2.8 requires pool gates to be self-closing, self-latching, and to open outward away from the pool. Latch placement must be at least 54 inches above grade if the gate can be reached from the pool side, or placed on the pool side if the gate is more than 54 inches tall. State codes often add to these requirements.

Q: What is the difference between a self-closing gate and a self-latching gate?

A: Self-closing means the gate returns to the closed position automatically when released. Self-latching means the latch engages automatically when the gate closes. They are independent mechanisms. Both are required by pool barrier code. A gate with a failed latch can self-close but remain unlocked — exactly the failure mode at the center of the Las Vegas case.

Q: What hardware brands are used for code-compliant pool gates?

A: Commonly specified: TruClose and KwikFit (D&D Technologies), D&D MagnaLatch, and Waterson hydraulic gate hinges. All offer products designed for self-closing and self-latching compliance. The specific model must match the gate weight and size, and the specification must prohibit substitution with lighter-duty alternatives.

Q: How does spring hinge degradation create ongoing liability after project completion?

A: Spring hinges lose closing force over time through torsion spring fatigue, UV exposure, and thermal cycling. A gate that was compliant at installation may fall below the self-closing threshold within 2–3 years. If the specification includes an annual maintenance and testing protocol, the property owner's failure to test creates clear liability for them rather than the architect. Without that protocol in the specification, the liability chain is less clear.

Need Pool Gate Hardware That Closes Reliably Over Time?

Waterson hydraulic gate hinges regulate closing force mechanically, without springs that degrade. Architects and specifiers: contact us for specification language and product selection support for pool barrier applications.

Request Specification Support
Sources & Research Basis

Case information is drawn from publicly reported settlements and news coverage. Dollar amounts reflect settlement figures as reported by plaintiffs' counsel and local media. This article is for informational purposes and does not constitute legal advice. Research verified April 16, 2026.