🪰85,269 violations tracked across 67 Florida counties
Back to Blog

Central Florida Restaurant Closures: What August Callback Records Reveal

Ten August closure records from Orlando, Bunnell, St. Petersburg, and Tampa show why callback inspections matter more than a single viral headline.

InspectFL Team · Aug 16, 2026 · Updated Aug 16, 2026
Health inspection clipboard in a commercial pizzeria kitchen
Snapshot from August 16, 2026. Health Scores update weekly (Sunday night) and may have shifted since this article was published. Inspection data itself updates daily; the headline score reflects a weekly weighted recompute. The official DBPR record at myfloridalicense.com is the authoritative source for any specific restaurant.

One Central Florida closure story got attention because of a memorable inspection note. But the more useful question is what the callback record showed after the headline moved on.

InspectFL reviewed 10 Florida DBPR closure sequences from August 3 through August 9, 2026, including restaurants in Orlando, Bunnell, St. Petersburg, and Tampa. The pattern is more interesting than a single viral detail: some locations cleared callback quickly, several still carry weak InspectFL Health Scores, and one Orlando pizzeria shows why a current grade should never be read without the inspection timeline.

The Orlando restaurant was Castello’s Pizza at 8947 Conroy Windermere Road. Florida DBPR records in InspectFL show an August 4, 2026 emergency order recommendation, an August 5 callback marked not complied, and an August 6 emergency-order callback marked complied.

That sequence is the important part. The closure headline tells you something serious happened. The callback tells you whether the immediate issue was cleared. The broader inspection history tells you whether the restaurant looks like a one-off problem or part of a deeper pattern.

In this case, the broader list matters even more than the single pizzeria.

Important context: The inspection events below are historical DBPR records from August 3 through August 9, 2026. A closure order means inspectors found an immediate condition that required the restaurant to stop operating temporarily. InspectFL Health Scores are separate, current site scores based on broader recent inspection history.

The Orlando Callback Sequence

Castello’s Pizza had three inspection records in the August 4-6 sequence:

  • August 4: emergency order recommended, with 3 recorded findings.
  • August 5: emergency order callback not complied, with 2 recorded findings.
  • August 6: emergency order callback complied, with 0 recorded findings.

The August 4 record documented live roach activity around the three-compartment sink, prep area, pizza oven area, pizza station, and kitchen wall areas. The August 5 callback record included the detail that spread widely: approximately 300 dead roaches in glue traps throughout the establishment, along with additional live roach activity.

InspectFL timeline showing the August 4 emergency order, August 5 not-complied callback, and August 6 complied callback
InspectFL timeline based on public Florida DBPR records for Castello's Pizza in Orlando.

That is bad. It is also exactly why the callback record matters. By August 6, the emergency-order callback was marked complied.

What may surprise people is the current InspectFL score: A 98.3 as of this snapshot. That does not make the August findings harmless. It means InspectFL’s longer scoring model sees this location differently than restaurants with repeated unresolved problems, many more findings, or weaker recent histories.

The Bigger Closure List

WKMG/ClickOrlando reported 10 Central Florida and Tampa Bay eateries forced to shut down at least temporarily during the week of August 3 through August 9, 2026. InspectFL matched those locations to public DBPR records and current InspectFL restaurant pages.

Restaurant City Closure sequence InspectFL score
Taqueria La Calentana DosBunnellAug. 3 emergency order; Aug. 6 callback compliedF 31.8
Castello's PizzaOrlandoAug. 4 emergency order; Aug. 6 callback compliedA 98.3
HootersOrlandoAug. 5 emergency order; Aug. 6 time extensionF 69.4
Jersey Mike's SubsOrlandoAug. 7 emergency order; Aug. 8 callback compliedA 98.8
Subway Sandwiches & Salads #213OrlandoAug. 4 emergency order; same-day callback compliedB 92
The Juicy CrabOrlandoAug. 7 emergency order; Aug. 8 extension pendingF 40.6
White Wolf Cafe & BarOrlandoAug. 3 emergency order; Aug. 4 callback compliedF 55
Buffet CitySt. PetersburgAug. 3 emergency order; Aug. 6 callback compliedF 34.2
Devito's Italian SpecialtiesTampaAug. 4 emergency order; Aug. 5 time extensionC 83.6
The Fryer HouseTampaAug. 3 emergency order; Aug. 4 callback not complied/time extensionF 36.4

The Pattern Is Not Just Roaches

Pest activity drove much of the week. Castello’s Pizza, Jersey Mike’s, The Juicy Crab, Buffet City, Devito’s, and The Fryer House had roach-related records in the sequence. White Wolf Cafe & Bar had a rodent-dropping record. Subway and Taqueria La Calentana Dos had flying-insect activity documented.

But the bigger risk pattern was not one pest note. It was the combination of emergency orders, repeat callbacks, and broader scores.

Three restaurants stand out most clearly:

  • Taqueria La Calentana Dos had an emergency order on August 3, callback records across August 4 and August 5, and a complied emergency-order callback on August 6. Current score: F 31.8.
  • Buffet City had an August 3 emergency order, emergency-order callbacks marked not complied on August 4 and August 5, and a complied callback on August 6. Current score: F 34.2.
  • The Fryer House had an August 3 emergency order, then August 4 callback records marked not complied and time extension. Current score: F 36.4.

Those are the examples where the closure headline and the longer score point in the same direction.

Why Castello’s Still Matters

Castello’s Pizza is the eye-catching example because the inspection note is so vivid. Approximately 300 dead roaches in traps is not the kind of detail anyone forgets.

But the current score shows why diners should not use one number alone.

If you only look at the current grade, an A can make the August 4-5 sequence look less serious than it was. If you only look at the headline, you may miss the August 6 complied callback and the broader history. The useful answer is in the timeline.

That is the central point: a temporary closure is an event, not the whole record.

How To Read A Closure Story

When a restaurant appears in a closure roundup, check three things before making a decision:

  • Was the emergency-order callback eventually marked complied?
  • Were there multiple not-complied callbacks or time extensions?
  • Does the current InspectFL Health Score support the same concern, or does the longer record look stronger?

The answer is not always “never eat there again.” Sometimes the record says a restaurant had a serious inspection event and corrected the immediate issue. Other times, the record says the problem was not finished when the headline moved on.

For the August 3-9 list, both things were true.

Source Note

This article was inspired by an August 14, 2026 WKMG/ClickOrlando report on Central Florida restaurant closures. InspectFL matched the restaurants to public Florida DBPR inspection records, added current InspectFL Health Scores, linked the restaurant pages, and reviewed the callback sequences.

Related reading:

Want to check a restaurant?

Search any Florida restaurant's inspection history and grade.

Search Restaurants

Join the discussion

Seen this place in person? Share what stood out — cleanliness, food handling, service, or whether the inspection record matches the real experience.

Add your take in under a minute

Sign in once, then comment, reply, and save restaurants to your watchlist.

or comment with email

Loading comments…