Archived · Investigation · Reviewed October 9, 2026
Piggly Wiggly gate access and code review
A retained courtesy-notice report records a locked-gate concern alongside a passed inspection. What evidence explains the closure?
Overview
This case starts with the approved one-page Codes Compliance report for the gate at 3101 Jefferson Avenue. It keeps the inspector’s note and the recorded case disposition together, while asking for the reviewed enforcement and inspection records that could explain the permanent fix and closure decision.
Source notes
This case uses one approved historical courtesy-notice report. It does not establish the full enforcement history, current gate condition, a legal accessibility violation or an unresolved present hazard. Private resident details and unapproved documents are excluded.
2 of 2 reviewed records. Source links and release indexes are identified separately from archived copies.
Archived file · June 9, 2026
Codes Compliance report CRTNTC-2024-1414 — Piggly Wiggly gate
City courtesy-notice report concerning gate access at the Piggly Wiggly business property.
Source link · Date not specified
13VAC5-52-220, § 1010.2
13VAC5-52-220, § 1010.2. Official publisher text.
Timeline
Dates follow the cited records; document dates are labeled separately.
September 3, 2024
Gate concern and passed inspection appear in the same report
Inspector Cynthia Evans records a shopper’s report of being unable to enter and later exit through the locked gate. The inspector says she found a lock on the gate and calls for a permanent fix. The same report lists a passed courtesy-notice inspection at 4:29 p.m. and a case opened and closed that day as ‘In Compliance.’ It does not explain how those entries were reconciled.
June 9, 2026
A historical report copy is retained
The archived report bears a June 9, 2026 print date. Its complaint, inspection and closure entries describe September 2024 events; the print date is not a new inspection or a finding about present conditions.
References
Gate operation and the recorded closure
For gates serving the means of egress, Virginia’s fire code ties operation and maintenance to the applicable building code. The September 2024 notice records a locked-gate concern and a same-day passed inspection. The approved egress layout and closure rationale are needed to assess how that rule applies here.
The cited 2021 SFPC text is verified from the official complete chapter. Gate classification, applicable construction edition and the September 2024 enforcement basis remain unconfirmed; this is conditional context, not a retroactive or current violation finding.
Authorities and context
- Virginia · Virginia regulation
13VAC5-52-220, § 1010.2 · 13VAC5-52-220, § 1010.2 Gates, within the verified official complete Chapter 52
Factual sources
News story
Open questions
Records still needed (3)
Reviewed enforcement history
A publication-ready copy of the related enforcement packet, notices, inspection notes, relevant correspondence and final closure rationale, with private resident information removed.
Likely custodian: City Codes Compliance
The courtesy notice does not supply the complete enforcement history or explain the recorded closure.
Submit this recordPermanent correction and verification
Dated photographs or measurements, work or correction records, follow-up inspection findings and written acceptance of the gate-access remedy.
Likely custodian: City Codes Compliance and the property owner or operator
A passed status does not by itself describe what changed or how access was verified.
Submit this recordRequirements and responsibility
Any public Fire Marshal or access-related review, written requirements applied to this location and documents identifying who was responsible for the correction.
Likely custodian: City Codes Compliance, Fire Marshal and property owner or operator
The case needs the applicable review and assigned responsibilities before drawing a conclusion about compliance.
Submit this record