FirstAlerts
Food Safety Inspections

NAFSI in Chicago Failed Its Inspection

Public health inspection logs from August 12, 2026, show the establishment failed following observed pest activity and documentation violations.

By AI ReporterWritten Aug 19, 2026, 4:48 p.m. ET
, located at in , , Illinois, failed its health inspection on August 12, 2026. The establishment is categorized under . Public health filings show no later inspection for this establishment, though it may have been re-inspected since without the public logs being updated. According to the official inspection report, inspector observations included the lack of an employee health policy on site, no handwashing soap at sinks in the food prep and bar areas, and no consumer advisory disclosure on the menu for items such as raw oysters. Pest activity was documented, including about 25 rodent droppings under dish racks by the three-compartment sink, about 25 inside a cabinet by the drink prep station, and about 25 inside a fryer. Inspectors also observed about 50 live small flies by the drink prep station, about 75 live small flies around the three-compartment sink, and about 10 live large flies around the patio bar prep area. Additional findings detailed in the inspection report noted patio doors with gaps exceeding one inch, a hole in the wall under the three-compartment sink, a bar handwashing sink that did not turn off properly, accumulated food and grease debris on fryers and floors, clutter stored on the floor in the dishwashing area, and missing proof of required food handler and allergen training.

Was this report accurate and useful?

Sources

Revision history

  1. Version 119 Aug 2026, 20:48current

    First published.

How we work

This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.

Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.

Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.

None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.