06-reference/research

tampa sunset park zoning overlay far lot coverage

2026-10-11·research-brief·source: deep-research·by Ray Data Co (deep-research synthesis)·! medium
tampa-zoninghome-rebuild-2027land-development-codestormwater-imperviousoverlay-districts

No Sunset Park Overlay Exists or Is Pending, and Neither Tampa's Current Code Nor the Published Installments of Its Draft Rewrite Cap Floor Area Ratio or Lot Coverage on RS-75

The question

"Is there a pending or recently-proposed zoning overlay in Tampa's Sunset Park neighborhood addressing 'scrape-and-build' teardown pushback, and what would it change for FAR/lot-coverage on a 3,000sf new-build footprint?"

Context: this is the desk-researchable slice of flags #4 and #5 in [[zoning-flood-zone-findings]], sitting ahead of the founder's formal Zoning Verification Letter request for 1212 S Suffolk Dr (folio 120668.0000), the teardown-and-rebuild candidate in the ~$2M-build-versus-paid-off-house decision. "FAR" is Floor Area Ratio, the ratio of total building floor area to lot area.

What we already know (from the vault)

What the web says

On the overlay question - a clean negative, from seven separate record surfaces. Several of them restate the same adopted code, so they are separate records rather than fully independent evidence.

On what the local pushback actually produced instead

On the FAR and lot-coverage question - the standard does not exist, in the current code or in the published rewrite installments

On whether the teardown pressure is real

On the number that actually binds

Convergences and contradictions

Synthesis for RDCO

The honest answer to the question as asked is no, and the premise behind the second half of it does not hold either. No Sunset Park overlay exists, none is pending, and seven separate record surfaces say so. One framing correction comes first, though: the parcel is not in Sunset Park. The City's own neighborhoods layer assigns 1212 S Suffolk Dr to the Culbreath Bayou Homeowners Association, which the City describes as sitting "between Beach Park and Sunset Park," so even a successful Sunset Park petition would have to be boundary-checked before it bound this lot. More importantly, an overlay could not "change FAR or lot coverage" for this build because Tampa does not regulate single-family bulk by FAR or by lot coverage in RS districts at all - the Table 4-2 FAR column is dashed for every RS and RM district and there is no coverage column. Chapter 27 Table 4-2 applies four dimensional numbers to a house on RS-75: 25 ft front, 7 ft sides, 20 ft rear, under a 35 ft height cap. On this lot that yields a footprint envelope of roughly 4,470 sf using the City's mapped parcel geometry (4,590 sf using the vault note's 68 x 130 assumption), so a 3,000 sf footprint sits inside it with roughly 1,470 to 1,590 sf to spare. Two scope caveats on that negative, stated up front rather than buried: the council-record sweep covers 2025-07-17 onward only, and the Hillsborough City-County Planning Commission record - a required step under Sec. 27-232 - was unreachable.

The number that actually bites is 50% impervious. On an 8,653 sf site, half is 4,326 sf. Note what this means: zoning imposes no hardscape limit whatsoever, because driveways, walks and patios may occupy the setback yards, so the Stormwater Technical Standards Manual's 50% trigger is the only published number covering total impervious area on this lot - and a house built out to the full setback envelope would already sit above it before any paving. If "3,000 sf footprint" is taken literally, the house consumes 34.7% of the lot and leaves 1,326 sf for driveway, walks, patio, pool deck and equipment pads before the trigger fires. A single north-side driveway at 12 ft by 60 ft is 720 sf, which is 54% of that remaining allowance. That is tight. If instead 3,000 sf means heated area over two stories - roughly a 1,500 to 1,600 sf footprint, close to the existing house's ~1,292 sf - impervious starts at 17.3 to 18.5% and there is 2,726 to 2,826 sf of allowance. The two readings of "3,000 sf" are the difference between a constrained site plan and an unconstrained one, so pin that down before anything else goes to an architect.

Crossing 50% is not a prohibition, it is a retention requirement: the first half-inch of rainfall held onsite. Over the whole 8,653 sf site that is 361 cubic feet (about 2,697 gallons); if the governing denominator is the impervious area only, at 4,326 sf it is 180 cubic feet (about 1,348 gallons). Ray's read, not a sourced cost, is that this is an exfiltration trench or dry well rather than a design-altering intervention - it has not been priced and should be, but at that volume it is far below the elevation line item. Which denominator applies is not desk-resolvable and it is the single most useful new question to add to the Planning conversation. Two details are worth handing to the designer alongside it: the manual explicitly excludes "the water surface of pools" from the impervious calculation, which for a 15 x 30 pool is 450 sf of relief, and it warns that "subsequent additions to a site will not be approved unless the site is brought into compliance," meaning a site planned to land at 49% leaves no headroom for a future addition.

Three things change in how we hold this project. First, drop the FAR and lot-coverage contingency for the published City code. Flag #4 is closed as to Chapter 27 and the two published rewrite installments. A coverage or size limit could still arrive from a private deed covenant, from administrative practice not published in the code, or from the unpublished Article 5 of the rewrite, so those stay open and route to the Zoning Verification Letter and a title and plat pull. Flag #5 is closed on desk evidence within the stated search window. Second, the risk register loses an item and gains a smaller, well-bounded one: the elevation-to-BFE cost already priced in [[2026-07-22-ae-zone-elevation-cost-premium-tampa]] remains the dominant variable, with a stormwater retention line added only if hardscape crosses 50%. Third, the overlay question becomes a watch item with a known trigger rather than an unknown risk, and the thing to watch is not an overlay. Tampa's live vehicle is the citywide LDC rewrite, whose February 2026 draft would fold RS-75 into a new RSS district with identical setbacks and height, no FAR, no coverage, no impervious standard, and minimum lot size deleted. Two second-order notes from that draft do matter: the 75 ft minimum lot width is carried forward, so the frontage stays nonconforming under the proposed code - and the City's mapped geometry puts that frontage at about 66.7 ft rather than the platted 68 ft, which is worth reconciling against the survey before the Zoning Verification Letter goes in. The draft also newly defines "lot coverage" to include "paving and driveways," which means the machinery for a residential coverage cap now exists in Tampa's drafting language even though no number is applied to RSS. Article 5 of the rewrite, which carries the form, design and compatibility standards, has not been published; that is the one document that could still introduce something, and it is worth a single check when it drops.

Finally, the one live local item worth the founder's attention is not about house size at all. On 2026-03-26 Council directed staff to draft an impracticability criterion letting applicants in "certain qualifying neighborhoods, like Culbreath Bayou" pay the sidewalk in-lieu fee instead of constructing a sidewalk, driven by oak-tree loss on new-home builds. A new build at 1212 S Suffolk Dr plausibly triggers a sidewalk construction requirement, the lot has one retained live oak at the southwest corner per [[zoning-flood-zone-findings]], and whether the fee-in-lieu path is available by permit time is a real line item. That belongs in the Planning conversation, and it is the concrete form the scrape-and-build pushback actually took in this neighborhood.

Why this is in the vault

This closes flag #5 and closes flag #4 as to the published City code in [[zoning-flood-zone-findings]], using primary City sources plus an unofficial archive of City council records. That lets the founder's pending Zoning Verification Letter drop two of its questions and keep what needs the city: written confirmation that a rebuild is permitted on the substandard-width lot, the Architectural Review Commission path for the 1962 structure, the denominator for the half-inch retention calculation, and the sidewalk requirement or in-lieu-fee availability. It also gives the architect a numeric impervious ceiling (4,326 sf, above which onsite retention is triggered) to design against at schematic instead of an unknown, and it kills a wrong third-party number (35% lot coverage) before it reaches a builder.

Open follow-ups

NOT desk-researchable - belongs in the Zoning Verification Letter or a call to Tampa Planning (813-274-3100), and must not be mistaken for a finding above:

Limits of the negative, stated plainly. The negative above is strong but bounded, and these are its edges:

  1. The primary-source council-record sweep covers 2025-07-17 through 2026-10-08. The window 2023-01-01 through 2025-07-16 was not swept at the agenda-and-transcript level, because the City's own closed-caption transcript search application could not be driven (see Blocked below). That window is covered indirectly by 26 sets of THAN minutes running January 2022 to April 2025 and by the rewrite documents, but not directly.
  2. The Hillsborough City-County Planning Commission and Plan Hillsborough record was unreachable (HTTP 403). Under Sec. 27-232 the Planning Commission is a required step for any residential overlay, so this is the most consequential blocked source.
  3. The council corpus was accessed through an unofficial archive, and its claim of completeness ("all 99 meeting pages") was not cross-checked against the City's own meeting calendar.
  4. The 26 sets of THAN minutes span 40 months and are therefore not a complete monthly run.
  5. "Beach Park" was not run as a separate search term against the council corpus, and the Culbreath Bayou Homeowners Association's own public surface was not searched.

Related

Sources

Vault:

Primary, City of Tampa documents:

Primary, City of Tampa GIS, all queried 2026-10-11:

Secondary, labelled:

Secondary, contradicted and not used as a finding:

Blocked or unreachable, with exact failures: