A parking-garage gate can strike a vehicle, cyclist, or pedestrian in a matter of seconds. The first photograph may show the damage while leaving the central question unanswered: what caused the gate to move at that moment?
The answer may lie in several systems. Video can show the approach. An access record may identify a credential or payment. A controller may record a command or fault. Maintenance records may explain an earlier problem. Preserve those records before a reset, repair, or routine overwrite removes part of the sequence.
Identify the equipment before describing a malfunction
Record the garage, entrance or exit lane, direction of travel, date, and approximate time. A gate number, nearby sign, parking ticket, or photograph can distinguish one lane from another. Identify whether the device was a barrier arm, rolling door, sliding gate, or another mechanism.
Obtain the manufacturer, model, serial number, installation information, and operating instructions where available. Ask which sensors and safety devices were installed and how the system was configured. Do not assume that two gates with similar appearances detect the same objects or use the same closing sequence.
Photograph warning signs, signals, ticket machines, mirrors, pedestrian entrances, and sightlines from a safe location. Note whether a sign or alternate route was visible from the person’s actual approach. Preserve the original photographs, including their dates, rather than relying only on cropped copies.
Build the sequence across several records
A useful event record begins before the gate moves and continues through the response. It should identify the previous vehicle, the injured person’s approach, any payment or access attempt, the gate’s movement, impact, and subsequent intervention. Leave uncertain times marked as estimates until the records can be compared.
Scroll horizontally to see all columns. Use the arrow keys when the table is focused.
| Record | Useful evidence | Limit to investigate |
|---|---|---|
| Original surveillance video | Position, gate movement, warnings, and the preceding traffic | The camera may not show a sensor, operator, or blind spot. |
| Access and payment logs | Credential use, ticket processing, and transaction times | A recorded authorization does not prove the person’s precise physical position. |
| Controller and fault records | Recorded commands, faults, resets, or overrides if the equipment retains them | The entry’s meaning depends on the model, settings, and system documentation. |
| Service history | Complaints, adjustments, replaced parts, tests, and return to service | A completed work order may not explain what was tested or whether a problem recurred. |
| Physical condition and damage | Contact locations, displaced components, and vehicle or gate damage | Post-event damage may differ from the condition that caused the movement. |
Check whether the clocks on the video, access system, and incident report agree. Save the basis for any adjustment. A controller’s close command and a camera’s first visible movement may reflect different events as well as different clocks.
Request the original video covering the approach and aftermath, any necessary playback software, and available export information. Identify the relevant cameras promptly. The building owner, garage operator, security vendor, and equipment contractor may hold different records.
Find who controlled the gate and knew about the problem
Louisiana Civil Code article 2317.1 addresses responsibility of an owner or custodian for damage caused by a thing’s defect. It requires proof of knowledge or what reasonable care should have revealed, preventability through reasonable care, and failure to exercise that care. A gate strike alone does not establish each element.
Obtain agreements identifying who operated the garage, maintained the gate, responded to faults, and could change settings or take the lane out of service. Compare those duties with service calls, complaints, inspection notes, and communications. A recurring premature closure complaint may be relevant, but establish that it involved this gate and a comparable problem.
For work by an outside contractor, identify the particular inspection, installation, adjustment, or repair under examination. Determine what the contractor undertook and what evidence connects its work to the incident. The maintenance company’s name on a sticker does not supply that connection.
Document repairs and test competing explanations
Safety repairs should be documented, not delayed to keep hazardous equipment operating. When feasible, preserve the removed component, the configuration before changes, service notes, and photographs. Record who reset or tested the system and what changed.
Do not try to reproduce the impact by standing under the gate or defeating a sensor. Testing should be planned by qualified personnel with appropriate safeguards. A successful cycle after repair does not by itself establish how the equipment behaved before repair.
Compare possible explanations with the evidence: a detection problem, an override, a power interruption, movement behind another vehicle, or entry into a vehicle lane. Avoid assigning fault from a single still image. Witnesses should describe what they actually saw, including whether they observed the approach or arrived afterward.
Our guides to witness observations and collision evidence explain how accounts, video, and damage records can be compared. The Baton Rouge premises liability practice investigates control, notice, and dangerous property conditions.
Editorial & Legal Accuracy Notice (Louisiana)
Equipment behavior, applicable duties, and responsibility depend on the particular gate, records, and incident.