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)
- [[zoning-flood-zone-findings]] is GIS-confirmed as of 2026-06-10: zoning RS-75, folio 120668.0000, Culbreath Bayou Unit No 4, 8,653 sf lot (0.20 ac), 68 ft platted frontage x ~130 ft deep, existing 1962 two-story with a ~38 ft x 34 ft (about 1,292 sf) footprint. FEMA Zone AE, Base Flood Elevation (BFE) 11.0 ft above the North American Vertical Datum of 1988 (NAVD88), Flood Insurance Rate Map (FIRM) panel 12057C0342J effective 2021-10-07.
- Same note: the 68 ft frontage is below RS-75's 75 ft minimum, so the lot is legally nonconforming on width. Written confirmation that a rebuild is still permitted is a Zoning Verification Letter item, not a desk item.
- Same note: the buildable envelope after 25 ft front / 7 ft side / 20 ft rear setbacks is given as 85 ft x 54 ft = 4,590 sf of footprint. That figure assumes a 68 x 130 rectangle, which would be 8,840 sf and does not reconcile with the recorded 8,653 sf. See the parcel-geometry bullet below, which resolves it.
- Same note, flag #4, verbatim: FAR, impervious and lot coverage are "not in 27-156's principal table" and were logged as "a gap to close before schematic design." Flag #5, verbatim: "Worth asking Planning if any Sunset Park overlay is pending." Those two flags are what this brief addresses.
- [[2026-06-11-comp-3-streets-over]] records neighbors building closer to property lines than the marked easements, read at the time as variances or Planned Development rezonings, i.e. "Sunset Park precedent for relief exists."
- The Zoning Verification Letter is still an open gate in [[home-rebuild-2027/milestones]]; the teardown (rather than renovate) path is already the working assumption in [[2026-08-04-flood-zone-ae-construction-loan-requirements]] and [[2026-08-20-save-our-homes-teardown-rebuild-reassessment]].
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.
- Tampa has exactly eight adopted overlay districts and none is Sunset Park. The City of Tampa OpenData "Overlay Districts" GIS layer, queried 2026-10-11, returns 8 polygons: South Howard Commercial (Sec. 27-236), New Tampa Commercial (27-237), Westshore (27-238), East Tampa (27-240), West Tampa (27-241), Parkland Estates (27-242), Kennedy Boulevard Corridor (27-243), Tampa Heights (27-244). Chapter 27 Article IV Division 2 read directly on Municode (2026-10-11) returns the identical eight with 27-239 and 27-245 marked Reserved, and the City's Land Development Code (LDC) Assessment Public Draft of February 2025 independently states "There are 53 base zoning districts and eight overlay districts in the City's current development regulations." The tampa.gov "Special Districts and Overlay Districts" page, stamped "Updated: 05/29/2026," lists the same set plus four special districts and names no proposed or pending overlay.
- Parkland Estates, the only residential overlay of the eight, is plat-limited and is a different subdivision. Sec. 27-242 applies expressly to "the Revised Plat of Parkland Estates... Plat Book 1, Page 156." It covers roughly 122 acres in South Tampa near Palma Ceia, not Sunset Park, Beach Park or Culbreath Bayou.
- Point-in-polygon at the actual parcel returns no overlay. Querying the parcel's geocoded location (Tampa's ParcelFolioLocator resolves folio 120668.0000 to 1212 S Suffolk Dr at Florida State Plane West x=164,941.9, y=1,310,776.8, EPSG:2881) against the City's planning layers on 2026-10-11: Overlay Districts - no intersect; Zoning District - RS-75, "Residential Single-Family"; Historic District Local - no intersect; Historic Districts National - no intersect; Bonus FAR Areas - no intersect; Accessory Dwelling Unit (ADU) allowable areas - "ADU Not Permitted"; Planning District - South Tampa; City Council District - District 6, Charlie Miranda (layer updated 2026-09-25).
- No area-wide land-use case is pending anywhere near the parcel. City of Tampa "Active Entitlement Locations" layer, queried 2026-10-11, returns zero records within 2,000 ft of the parcel. The layer held 274 active records citywide at that moment, so it is populated and the zero is a real absence of filings rather than an empty layer. Nine open cases carry a Sunset Park or Beach Park neighborhood tag, and eight are parcel-level Variance Review Board, Design Exception or Formal Decision items (4705 W Leona St, 5108 W Platt St, 4631 W Longfellow Ave, 4821 W San Jose St, 401 S Royal Poinciana Dr, 4801 W Longfellow Ave, 35 W Spanish Main St, 4630 W Bay To Bay Blvd). The ninth is a single-site rezoning at 5600 Mariner St, Beach Park. Not one is an area-wide instrument, and individual variances loosen standards parcel by parcel, which is the opposite of what an overlay does.
- Council record search, 2025-07-17 through 2026-10-08, finds nothing. All 99 meeting pages in that window (City of Tampa structured agendas and official closed-caption transcripts, accessed through the unofficial tampamonitor.com archive) were downloaded and full-text searched: "neighborhood conservation" 0 files, "conservation overlay" 0, "residential overlay" 0, "interim development control" 0, "lot coverage" 0, "scrape and build" 0, "mansionization" 0. "Culbreath" returns 7 files, all of them sidewalk in-lieu-fee or tree items. The 28 files mentioning "overlay district" all concern East Tampa, West Tampa, Tampa Heights, Seminole Heights or the Hyde Park Architectural Review Commission. The three "McMansion" mentions are all comprehensive-plan public comment arguing for density. The three "Sunset Park" hits are a platted right-of-way vacation (Nov 6 and Dec 4 2025) and a Bay-to-Bay detour. "Beach Park" was not run as a separate term against the corpus.
- No neighborhood association has petitioned for one, either. The Sunset Park Area Homeowners Association (SPAHA) public site at spaha.org, all 9 pages crawled 2026-10-11, carries zero zoning, teardown, tree or stormwater content; its published "Legal Docs" are bylaws (2020-11-10), articles of incorporation (1993) and an Internal Revenue Service determination letter, with no newsletters, minutes or deed restrictions. SPAHA does not appear in the member directory of the Tampa Homeowners Association of Neighborhoods (THAN). Twenty-six sets of THAN minutes dated January 2022 to April 2025 were read: zero occurrences of "teardown," "scrape-and-build," "mansionization," "lot coverage," "impervious surface" or "floor area ratio." THAN's stated vehicles are the citywide code rewrite, "design exceptions," and tree canopy. The Beach Park homeowners association was found to have no public surface beyond a private Facebook group and so could not be checked. The Culbreath Bayou Homeowners Association, which is the association that actually covers this parcel, was not searched.
- What relief in this neighborhood actually looks like: setback variances and grand-tree removals. Official City of Tampa Variance Review Board minutes for 2026-04-14: VRB-26-33, 5023 W Dante Ave, RS-75, Sec. 27-156, applicant Adobe Homes Inc. / Innovative Pools, rear setback 20 ft to 9 ft and east side 7 ft to 4 ft - withdrawn; VRB-26-28, 4510 S Ferncroft Cir, RS-75, Sec. 27-156, rear setback 20 ft to 5 ft - continued to 2026-05-12 by 6-0; VRB-26-55, 4003 W Kensington Ave, RS-60, Sec. 27-284.2.5, grand-oak removal to build a larger replacement home - continued by 6-0. Both the Sunset Park and Culbreath Bayou associations appear on those cases only as recipients of the City's Good Neighbor notice, which is not evidence either took a position, and no organized group appears as a party in the minutes read.
On what the local pushback actually produced instead
- A sidewalk in-lieu-fee directive that names Culbreath Bayou by name. City agenda-packet text, via the unofficial tampamonitor.com archive, states verbatim that "on March 26, 2026, the City Council of the City of Tampa approved a motion directing City staff to formulate language to amend the City Code of Ordinances to create a new impracticability criteria where applicants residing in certain qualifying neighborhoods, like Culbreath Bayou, could apply to pay the sidewalk in-lieu fee instead of constructing a sidewalk." The language appears in the 2026-05-07 and 2026-06-04 agenda packets, and the transcript motivation is oak-tree loss on new-home builds, not house size. This is a council directive to draft; no filed ordinance number was located. It is nonetheless the only city action in the record that names this neighborhood in connection with new construction.
- Beach Park's organized opposition is anti-density, not anti-teardown. preservebeachpark.org opposed rezoning REZ-26-0000062 at 5600 Mariner St (OP-1, an office-professional district, to Planned Development, an 11-story 262-unit proposal) and claims Council denied it on 2026-09-10. The site mentions no overlay, no neighborhood conservation district, no moratorium and no LDC amendment. The City's own Active Entitlement layer still showed that case "In Process" with a tentative 2026-08-20 hearing when queried on 2026-10-11. That conflict is unresolved: the denial was not verified against the 2026-09-10 council record even though that date falls inside the swept window.
On the FAR and lot-coverage question - the standard does not exist, in the current code or in the published rewrite installments
- Current code: RS-75 has no FAR and no lot-coverage standard. The City's own training deck "ABCs of Zoning," Module One, January 11 2023, reproduces Sec. 27-156 Table 4-2, "Schedule of Area, Height, Bulk and Placement Regulations." For RS-75 it gives minimum area 7,500 sf; minimum lot width 75 ft; minimum land area per dwelling unit 7,500 sf; front yard 25 ft; side 7 ft; rear 20 ft interior / 12 ft corner; corner 15 ft; Maximum FAR "—"; Maximum Height 35 ft. The FAR column reads "—" for every RS and RM district, and Table 4-2 has no lot-coverage and no impervious column at all. The omission is structural, not an oversight: the same code uses explicit FAR and coverage columns in Table 4-3 for the Municipal Airport districts. The same RS-75 figures with the same absent coverage and FAR rows appear in Table II-3, "Key Standards," of the City's February 2025 LDC Assessment, and the setback figures are confirmed again by Variance Review Board minutes citing Sec. 27-156. Note the lot conforms on area: 8,653 sf against a 7,500 sf minimum. Only width is nonconforming.
- Parcel geometry, which resolves the vault's 68 x 130 figure. The City's TaxParcel layer, queried 2026-10-11, returns for folio 120668.0000 (legal description "Culbreath Bayou Unit No 4, S 68 Ft Of Lot 34 Block 9"): recorded area 8,653.42 sf, acreage 0.20, perimeter 393.01 ft. The polygon is five-sided, not rectangular, with side lengths of 66.78, 129.77, 66.65, 30.17 and 99.73 ft - that is, roughly 66.7 ft of frontage by about 129.8 ft deep (66.7 x 129.8 = 8,657 sf, which reconciles). A true 68 x 130 rectangle would be 8,840 sf with a 396 ft perimeter. So the mapped frontage is about 66.7 ft rather than the 68 ft platted figure, which makes the width nonconformity marginally worse, and the setback envelope is about 4,470 sf (52.7 ft x 84.8 ft) rather than the 4,590 sf in the vault note. Both numbers are below the 75 ft width minimum and above the impervious threshold discussed below, so no conclusion turns on which is used, but the 2019 Exacta boundary survey is the authority and should settle it.
- Pending rewrite: RS-75 would be folded into "RSS," and RSS still has no FAR and no lot coverage. Tampa is mid-rewrite of its entire LDC under the project name "Tampa Forward" (reported as launched April 2024 with completion targeted in the second half of 2026; no current project page URL was located, see Blocked below). Installment 1 Public Draft is dated February 17 2026 (Articles 3, 4 and 9) and Installment 2 October 1 2026 (Article 2, Administration). Installment 1 consolidates RS-150/100/75/60/50 into four residential districts, and RS-75 and RS-100 would merge into RSS: Residential Single-Family Suburban (Sec. 3.2.4). Table 3.2.4-A, RSS Intensity and Dimensional Standards, reads in full: density "In accordance with comprehensive plan"; Lot size, min = n/a; Lot width, min = 75 ft; Height, max = 35 ft; setbacks front 25, side 7, corner 15, rear 20 interior / 12 corner. There is no FAR row, no lot-coverage row and no impervious row. The draft's own footnote explains that RSS "eliminates minimum lot size requirements to reduce nonconformities and increase development flexibility, but maintains minimum lot width and maximum height standards to maintain the desired district character." This is a text-level district consolidation; no zoning-map conversion for this parcel is cited in the draft.
- The rewrite also does not add single-family design standards to RSS. Installment 1 adds "form and design standards" (building orientation, wall offsets) only to RSU, the urban district replacing RS-50 and RS-60, where duplexes, triplexes, fourplexes and cottage courts would become permitted by right. RSS gets no such subsection. The February 2025 Assessment does carry a "Theme 6: Protect the Character of the City's Residential Neighborhoods from Incompatible Development," and its answer is a planned Sec. 5.9, "Neighborhood Compatibility Standards." But Installment 1 scopes that section to standards "intended to mitigate the impacts of retail or other nonresidential development that is adjacent to single-family homes," plus multifamily next to single-family. It is not a bulk cap on houses, house-for-house teardowns are unaddressed in both installments, and Article 5 has not been published yet.
- One forward-looking wrinkle: the rewrite newly defines "lot coverage" to include driveways. Draft Sec. 9.2.6 defines it as "The portion of a lot that is covered by principal and accessory buildings or structures, and by surfaces that prevent the passage or absorption of stormwater such as paving and driveways," footnoted "New definition for a term used in the current LDC but not defined." The drafters also note they chose lot coverage over FAR as the regulating tool in the mixed-use districts - MU-N, Mixed-Use Neighborhood, is set at 40 | 80 percent of gross lot area. So the machinery for a residential coverage cap now exists in Tampa's drafting language even though no number is applied to RSS.
- Full-text scans of both rewrite drafts find no trace of this neighborhood or of the teardown framing. Installment 1 (February 17 2026, 19,196 extracted lines, verified independently for this brief): "Sunset Park" 0, "Culbreath" 0, "neighborhood conservation" 0, "mansioniz*" 0, "teardown" 0, "scrape" 0; the single "Beach Park" hit is an unrelated legacy alcohol-standards cleanup. Installment 2 (October 1 2026): "Sunset Park" 0, "Beach Park" 0, "Culbreath" 0, "mansioniz*" 0, "neighborhood conservation" 0. The February 2025 Assessment is the same on all of those terms, and its only two "lot coverage" references propose increasing coverage as an affordable-housing incentive. Both drafts carry the same eight overlays forward and create no new residential overlay.
- The pathway an overlay would have to run is Sec. 27-232, "Residential overlay districts." Read on Municode 2026-10-11: any resident, property owner or organization may petition City Council; the Barrio Latino / historic body recommends; the Planning Commission reports within 60 days; Council holds a hearing within 90 days. No such petition for this area appears anywhere in the record searched.
On whether the teardown pressure is real
- City of Tampa "Single Family Permits" GIS layer, queried 2026-10-11, application type "Residential New Construction and Additions (1 and 2 Family)": Sunset Park 1 (2022), 7 (2024), 30 (2025), 35 (2026 year-to-date); Beach Park 1 / 6 / 20 / 16; Culbreath Bayou 1 (2025), 4 (2026 YTD). The five Culbreath Bayou permits are 4518 W Watrous Ave (2025) and 4510 W Watrous Ave, 4510 W Brookwood Dr, 4525 S Ferncroft Cir and 1122 S Dunbar Ave (2026), all within a few blocks of the subject parcel. Caveat: the City bundles new construction and additions into one application type, so this is not a pure teardown count.
On the number that actually binds
- City of Tampa Stormwater Technical Standards Manual (originally adopted 1996-12-05, revised June 2022), Sec. II.A: "One (1) Detached Single Family Dwelling - General Development Requirements only"; and "One Single Family with impervious surfaces (not including the water surface of pools) greater than 50% of entire site - General Development Requirements and Minimum Retention/Detention Standards." Sec. IV.B.1 exempts one detached single-family residence from City stormwater treatment and attenuation "except as stipulated in IV.B.2." Sec. IV.B.2: residential projects over 50% impervious "exceed the design capacity of the City stormwater management system. To reduce this excess flow, the project must retain the first 1/2" of rainfall onsite. Subsequent additions to a site will not be approved unless the site is brought into compliance with this standard."
- The parcel is not actually in Sunset Park. The City's Neighborhoods layer assigns 1212 S Suffolk Dr to Culbreath Bayou Homeowners Association, Inc. (bounds W Watrous Ave north, W Neptune St south, S Manhattan Ave east, S Westshore Blvd west), which the City's own description places "between Beach Park and Sunset Park." Even a successful Sunset Park overlay would need its boundary checked against this parcel before it bound anything here.
Convergences and contradictions
- Convergence, and an upgrade in confidence. The vault's 2026-04-18 read that Sec. 27-156 contains no FAR and no lot-coverage standard for RS-75 is now confirmed from a City of Tampa document rather than inferred from a third-party code mirror. Flag #4 moves from "gap to close before schematic design" to settled in the current code, and absent from the two published draft installments, with Article 5 of the rewrite still pending.
- Clean negative on flag #5, from non-overlapping record types. The City's overlay GIS layer, Chapter 27 itself on Municode, the tampa.gov overlay page as of 2026-05-29, the active-entitlement case layer, 99 council meeting records from 2025-07-17 to 2026-10-08, all three LDC-rewrite documents (February 2025, February 2026, October 2026), SPAHA's own public site and 26 sets of THAN minutes all agree: no Sunset Park overlay exists, none is proposed, and no area-wide instrument is pending.
- One third-party source is simply wrong and should be ignored. propertyzoned.com lists "maximum lot coverage 35%" for Tampa RS-75, last verified 2026-04-05. The City's own reproduction of Table 4-2 has no lot-coverage column at all. If that figure has already reached any builder or architect conversation, correct it.
- Contradiction in emphasis, not in fact. The vault treated the missing FAR and coverage numbers as the open risk. Tampa's zoning code sets no limit on hardscape or impervious area for a single-family lot at all - setbacks cap the building footprint, but driveways, walks and patios are permitted within the setback yards, so Chapter 27 never constrained total impervious coverage. The only published number that does is the 50% impervious trigger in the Stormwater Technical Standards Manual, which the vault note never names.
- And the real pushback took a different shape than the question assumed. The scrape-and-build friction in this neighborhood did reach City Council, on 2026-03-26, but it arrived as an oak-tree-and-sidewalk problem and the remedy being drafted is a sidewalk in-lieu-fee impracticability criterion. Nobody in the record is proposing to cap house size here.
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
- Is "3,000 sf" the footprint or the heated area? The impervious allowance swings from 1,326 sf to about 2,800 sf on that one definition. Founder question, not a research question.
- When Article 5 of the Tampa LDC rewrite reaches public draft, does Sec. 5.7 (Form and Design Standards) or Sec. 5.9 (Neighborhood Compatibility Standards) apply anything to RSS single-family detached development, and does any lot-coverage maximum get attached to RSS using the new Sec. 9.2.6 definition that counts driveways?
- Did the 2026-03-26 Council sidewalk in-lieu-fee directive ever become a filed ordinance, and does Culbreath Bayou end up on the qualifying-neighborhood list?
- What is the baseline tree-retention percentage in Tampa Code Sec. 27-284, and does it bind this lot? Variance Review Board case VRB-26-45 records an applicant asking to "reduce tree retention from 50 percent to 3 percent," but the 50% baseline was not verified against the code text, because the adopting ordinance PDF on tampa.gov returns HTML rather than a PDF. Given the retained live oak, this is the highest-value remaining desk question.
- Does the Tampa Comprehensive Plan's Future Land Use category for this parcel impose any density or intensity standard beyond RS-75? No Future Land Use GIS layer was found on either the City of Tampa or Hillsborough County ArcGIS servers, and a comprehensive-plan amendment cycle (reported in a search snippet as "TA/CPA 25-06", a Text Amendment / Comprehensive Plan Amendment case number; the source page was unreachable and the case number is unverified) appears to be in progress. Both drafts tie RSS density to "accordance with comprehensive plan," so the comprehensive plan is now the live document for density.
- Has any Tampa neighborhood association ever successfully petitioned under Sec. 27-232 for a residential overlay, and how long did it take? Parkland Estates is the only residential overlay on the books, so its adoption history is the one available precedent for pace and feasibility.
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:
- Whether the 1/2 inch retention volume is computed over the total site area or over the impervious area only. Stormwater Technical Standards Manual Sec. IV.B.2 does not say.
- The parcel's authoritative dimensions. The City's mapped polygon gives about 66.7 ft of frontage, the plat and the vault note give 68 ft; the 2019 Exacta boundary survey is the authority and should be re-read to settle frontage and depth before any envelope number is used in design.
- Written confirmation that a single-family rebuild is permitted on the substandard-width nonconforming lot, and whether the pending rewrite's carried-forward 75 ft minimum changes that answer.
- Whether a new build triggers a sidewalk construction requirement at this address, and whether a fee-in-lieu is currently available.
- Whether Development Services applies any administrative impervious or hardscape standard not published in Chapter 27 or the Stormwater manual.
- The Architectural Review Commission review path for demolishing the 1962 structure.
- Whether any private deed restriction or Culbreath Bayou Unit No 4 plat covenant imposes a coverage, size or architectural-review limit. Private covenants appear in no city or county GIS layer and cannot be desk-confirmed.
- Whether City staff are working on anything not yet on a public agenda. Only a phone call reaches that.
Limits of the negative, stated plainly. The negative above is strong but bounded, and these are its edges:
- 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.
- 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.
- 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.
- The 26 sets of THAN minutes span 40 months and are therefore not a complete monthly run.
- "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
- [[zoning-flood-zone-findings]]
- [[home-rebuild-2027/milestones]]
- [[2026-06-11-comp-3-streets-over]]
- [[2026-07-22-ae-zone-elevation-cost-premium-tampa]]
- [[2026-08-04-flood-zone-ae-construction-loan-requirements]]
- [[2026-08-20-save-our-homes-teardown-rebuild-reassessment]]
- [[2026-08-14-construction-to-permanent-loans-florida]]
Sources
Vault:
~/rdco-vault/01-projects/home-rebuild-2027/zoning-flood-zone-findings.md~/rdco-vault/01-projects/home-rebuild-2027/milestones.md~/rdco-vault/01-projects/home-rebuild-2027/2026-06-11-comp-3-streets-over.md~/rdco-vault/06-reference/research/2026-07-22-ae-zone-elevation-cost-premium-tampa.md~/rdco-vault/06-reference/research/2026-08-04-flood-zone-ae-construction-loan-requirements.md~/rdco-vault/06-reference/research/2026-08-20-save-our-homes-teardown-rebuild-reassessment.md~/rdco-vault/06-reference/research/2026-08-14-construction-to-permanent-loans-florida.md
Primary, City of Tampa documents:
- City of Tampa, "ABCs of Zoning," Module One, 2023-01-11, reproducing Sec. 27-156 Tables 4-1 and 4-2: https://www.tampa.gov/sites/default/files/document/2023/abcs-of-zoning-module-one.pdf (current accessible copy, same Table 4-2 content: https://www.tampa.gov/sites/default/files/document/2026/abcs-of-zoning-module-one_ada.pdf)
- City of Tampa Stormwater Technical Standards Manual, adopted 1996-12-05, revised June 2022, Sec. II.A and Sec. IV.B.1-2: https://www.tampa.gov/sites/default/files/document/2022/stormwatertechnicalstandardsmanualfinal_0.pdf
- City of Tampa, Land Development Code Assessment, Public Draft, February 2025 (Theme 6; Table II-3): https://www.tampa.gov/sites/default/files/document/2025/tampa-ldc-assessment-public-draft-feb-2025.pdf
- City of Tampa, Updated Land Development Code, Public Draft Installment 1, 2026-02-17 (Sec. 3.2.4 RSS and Table 3.2.4-A; Sec. 3.2.5 RSU; Table 3.6.3-A MU-N; Sec. 9.2.6 Lot Coverage): https://www.tampa.gov/sites/default/files/document/2026/tampa-updated-ldc-inst-1-public-draft-feb-17-2026-1.pdf
- City of Tampa, Updated Land Development Code, Public Draft Installment 2, 2026-10-01: https://www.tampa.gov/sites/default/files/document/2026/tampa_updated_ldc-inst_2_public_draft_oct_1_2026_remediated-v6.pdf
- City of Tampa Planning Division, "Special Districts and Overlay Districts," page stamped Updated 2026-05-29: https://www.tampa.gov/planning-division/info/design-overlay-districts
- City of Tampa Variance Review Board minutes, 2026-04-14 (cases VRB-26-28, VRB-26-33, VRB-26-55): https://www.tampa.gov/sites/default/files/document/2026/april-14-2026-vrb-minutes-ada_remediated.pdf
- Tampa Code of Ordinances Chapter 27, Article IV (Overlay Districts), Division 1 Sec. 27-232 and Division 2 Secs. 27-236 to 27-245, read 2026-10-11: https://library.municode.com/fl/tampa/codes/code_of_ordinances?nodeId=COOR_CH27ZOLADE_ARTIVOVDI
Primary, City of Tampa GIS, all queried 2026-10-11:
- Overlay Districts, Zoning District, Historic District Local and National, Bonus FAR Areas, ADU allowable areas, Planning Districts: https://arcgis.tampagov.net/arcgis/rest/services/OpenData/Planning/MapServer (layers 3, 28, 1, 2, 6, 37, 19)
- TaxParcel, for folio 120668.0000 area, perimeter, legal description and polygon geometry: https://arcgis.tampagov.net/arcgis/rest/services/Parcels/TaxParcel/MapServer/0
- Active Entitlement Locations: https://arcgis.tampagov.net/arcgis/rest/services/Planning/ActiveEntitlementLocations/MapServer/0
- Single Family Permits: https://arcgis.tampagov.net/arcgis/rest/services/Planning/SingleFamilyPermits/MapServer/0
- Neighborhoods, for association assignment and boundary description: https://arcgis.tampagov.net/arcgis/rest/services/Neighborhoods/Neighborhoods/MapServer/0
- City Council District: https://arcgis.tampagov.net/arcgis/rest/services/OpenData/Boundary/MapServer/0
- Parcel folio geocode, folio 120668.0000 to 1212 S Suffolk Dr: https://arcgis.tampagov.net/arcgis/rest/services/Locators/ParcelFolioLocator/GeocodeServer
Secondary, labelled:
- tampamonitor.com, an unofficial archive of City of Tampa structured agendas and official closed-caption transcripts. Used for the 2025-07-17 to 2026-10-08 full-text council sweep and for the verbatim 2026-03-26 sidewalk in-lieu-fee directive language, which appears in the 2026-05-07 and 2026-06-04 agenda packets: https://meetings.tampamonitor.com/meetings/2824/ and https://meetings.tampamonitor.com/meetings/2833/ (Sunset Park right-of-way items: /2653/ and /2713/)
- preservebeachpark.org, a neighborhood advocacy site, for the REZ-26-0000062 opposition and its unverified claim that Council denied the case on 2026-09-10: https://www.preservebeachpark.org/
- Sunset Park Area Homeowners Association public site, all 9 pages crawled 2026-10-11, used only to support the negative: https://www.spaha.org
- Tampa Homeowners Association of Neighborhoods published minutes, 26 sets dated January 2022 to April 2025, read 2026-10-11, used only to support the negative. No stable document URL was captured for the individual minutes sets; re-running this check requires re-crawling the THAN site.
- The finding that the Beach Park homeowners association has no public surface beyond a private Facebook group (facebook.com/groups/beachparkcommunity, not publicly readable) rests on that crawl, not on a citable page.
Secondary, contradicted and not used as a finding:
- propertyzoned.com lists "maximum lot coverage 35%" for Tampa RS-75, last verified 2026-04-05. Contradicted by the City's own reproduction of Table 4-2, which has no lot-coverage column. Treat as a third-party error: https://www.propertyzoned.com/city/florida/tampa/zones/rs-75
Blocked or unreachable, with exact failures:
library.municode.comreturns only the string "Municode Library" to WebFetch; the site is JavaScript-rendered. Chapter 27 Article IV was ultimately read via Playwright (about 234 KB of extracted text). The api.municode.com REST routes exist (/Clients/stateAbbr?stateAbbr=FLreturns Tampa as ClientID 4583) but no product-listing route was found for that client, soCodesContentcould not be called directly.tampa.legistar.com/Calendar.aspxand/Legislation.aspx: HTTP 200 with a 19-byte body reading "Invalid parameters!"webapi.legistar.com/v1/tampa/matters: HTTP 500, "LegistarConnectionString setting is not set up in InSite for client: tampa." Tampa is not on Legistar, which is why the council sweep ran through the tampamonitor.com archive instead.https://www.tampa.gov/search?...: HTTP 403, body "Enable JavaScript and cookies to continue" (Cloudflare managed challenge). Failed via curl, WebFetch and Playwright in both headless and headed Chrome. Static tampa.gov pages and PDFs fetch fine; only the/searchpath is blocked. This is why no "Tampa Forward" project page URL could be located, and why its launch date and completion target are reported without a citable page.https://planhillsborough.org/?s=Sunset+Parkand the City of Tampa plan-amendments interactive map: HTTP 403 Cloudflare challenge. Plan Hillsborough PDFs under/wp-content/uploads/are reachable. This blocks the Planning Commission record, a required step under Sec. 27-232.https://apps.tampagov.net/cttv_cc_webapp/(official City Council closed-caption transcript search, which has a real keyword search): the search fieldset isdisplay:noneuntiltranscript-search.jsreveals it; Playwrightfilltimed out on the hidden locator and a hand-built ASP.NET__VIEWSTATEPOST returned a byte-identical unfiltered result grid. This is the failure that leaves the 2023-01-01 to 2025-07-16 council window un-swept.wtsp.comarticle containing a Virginia Park resident's quote blaming street flooding on "people overbuilding": HTTP 403, body "Access Denied ... Reference #18.53743217.1791695555.413d9f29" via curl with a browser User-Agent, and 403 again through a text-extraction proxy. That quote is search-snippet level only and is not relied on above.tampa.gov/.../final_adopted_-_tree-ls_related_codes_-_ord_2019-54...pdf(the adopting ordinance for Tampa's tree and landscape code): returns HTML rather than a PDF, "Syntax Warning: May not be a PDF file." This is why the Sec. 27-284 tree-retention baseline is unconfirmed.vpna.communitysite.com(Virginia Park Neighborhood Association): fetched but returned empty, JavaScript-rendered content.http://tampa-fl.elaws.us(the code mirror cited in the April 2026 vault note): curl requests with a browser User-Agent all timed out with 0 bytes received. The mirror appears to be down as of 2026-10-11.- No Future Land Use layer exists on
arcgis.tampagov.net, nor in theTampaDatafolder onmaps.hillsboroughcounty.org(checked 2026-10-11).