No - Ord. No. 2026-49 Leaves the Sec. 27-43 Height Definition and the RS-75 Height Cell Untouched, So the 35-ft-From-Finished-Floor Verdict Stands
The question
"Does Tampa Ord. No. 2026-49 (adopted 2026-06-04) alter the Sec. 27-43 Height definition or the Sec. 27-156 RS-75 height cell?"
Context: [[2026-10-21-tampa-rs75-height-limit-datum]] concluded that the 35-ft RS-75 cap runs from the required finished floor (a flood-derived datum), giving the ~33 ft Sterling ridge roughly 4.5-5.5 ft of slack instead of 2.0 ft. That verdict rests entirely on the Sec. 27-43 "Height" definition as currently codified, and Municode badges both Sec. 27-43 and Sec. 27-156 as amended by an ordinance whose body it does not expose. This brief reads the ordinance body.
What we already know (from the vault)
- The parent verdict hangs on one clause of Sec. 27-43: "Height: The vertical distance between the required finished floor to the highest point of the structure. Required finished floor shall be determined by utilizing all applicable regulations of the city, county, state and federal government." Remove "required finished floor" and substitute grade, and the slack collapses from ~4.5-5.5 ft to ~2.0 ft ([[2026-10-21-tampa-rs75-height-limit-datum]]).
- The 35 ft itself sits in Sec. 27-156 Table 4-2, "Schedule of Area, Height, Bulk and Placement Regulations," RS-75 row, "Maximum Height (ft.)" column, with only an aviation-carve-out footnote attached ([[2026-10-21-tampa-rs75-height-limit-datum]], [[2026-10-11-tampa-sunset-park-zoning-overlay-far-lot-coverage]]).
- The parent brief could read only Municode's caption for the amending ordinance, which named certified recovery residences, parking and setbacks - nothing about height - and explicitly flagged the unread body as the one open point that could move the verdict ([[2026-10-21-tampa-rs75-height-limit-datum]]).
- Dedupe confirmed: [[2026-10-11-tampa-sunset-park-zoning-overlay-far-lot-coverage]] contains no reference to Ord. No. 2026-49, no reference to Sec. 27-43, and no height-datum analysis at all - it carries Table 4-2's 35 ft only as a table value. No overlap.
- Lot context for the arithmetic: 1212 S Suffolk Dr, RS-75, FEMA Zone AE, BFE 11.0 ft NAVD88, average existing grade ~8.5 ft ([[zoning-flood-zone-findings]]).
What the web says
- The ordinance body was retrieved. The adopted text is the substitute ordinance attached to City Attorney memorandum of April 22, 2026 (Dana Crosby Collier, Sr. Assistant City Attorney), File No. E2026-8 CH 27, "July 2025 Land Development Code cycle, substitute ordinance," heard and passed at the June 4, 2026 regular City Council session (OnBase item 24180; recorded vote line "Hurtak no, Carlson absent"). The body runs 14 sections (substitute ordinance PDF).
- Section 1 touches Sec. 27-43 by addition only. Verbatim: "Section 1. That 'Sec. 27-43. Definitions.' is hereby amended by adding the underlined language as follows:" followed by a single underlined definition - "'Certified recovery residence' means a recovery residence that holds a valid certificate of compliance and is actively managed by a certified recovery residence administrator as further defined in section 397.311, Florida Statutes." The clause authorizes adding underlined language and nothing else; there is no strikethrough anywhere in Section 1, and the "Height" definition is neither reproduced nor altered. The leading and trailing ellipses mark omitted unchanged text.
- Section 2 touches the wrong table. Verbatim: "Section 2. That 'Sec. 27-156. Official schedule of district regulations.' is hereby amended by adding the underlined language as follows:" and the table reproduced beneath it is Table 4-1, "Schedule of Permitted, Accessory, and Special Uses by District" - the use schedule. The amendment adds one use row ("Certified recovery residences", footnote 32) with an underlined "X" across RS-150, RS-100, RS-75, RS-60, RS-50, RM-12 through RM-75, RO, RO-1, OP and OP-1. Table 4-2, the Schedule of Area, Height, Bulk and Placement Regulations, is not reproduced, not referenced, and not amended by this ordinance.
- The one maximum-height change in the ordinance is Channel District only. Section 7 amends Sec. 27-199, Table 19-2, whose only columns are CD-1 and CD-2: the "Maximum Height (ft.)" row strikes "175" (and its footnote reference) and adds "FAA/HCAA" in both columns, with old footnote 3 struck in full and replaced by "(Reserved)". RS-75 appears nowhere in Table 19-2; no single-family district does.
- Municode's own index agrees. The Ordinance No. 2026-49 record lists 9 amended sections: Sec. 27-43, Sec. 27-156, Sec. 27-160, Sec. 27-177, Sec. 27-198, Sec. 27-211.8, Sec. 27-212.4, Division 2 Regulations for Specified Uses, and Sec. 27-283.12. Table 4-2 and the RS-75 dimensional standards appear nowhere in it (Municode Ord. 2026-49, read 2026-10-24).
- The codified Height definition re-read live today is unchanged, word for word, from the parent brief's quotation, and the Definitions page carries no 2026 amendment badge other than 2026-49 (Municode Sec. 27-43, version May 27, 2026, read 2026-10-24). The Sec. 27-156 page likewise shows Ordinance No. 2026-49 as its only 2026 badge, and still describes Table 4-2 as the "Schedule of Area, Height, Bulk and Placement Regulations."
- Effective date. Section 14: "That this ordinance shall take effect thirty days after adoption thereof." Adopted 2026-06-04, so effective on or about 2026-07-04 - already in force, and still not reflected in the published code version dated May 27, 2026.
Convergences and contradictions
- Four surfaces converge on "no height change": the ordinance's own Section 1 amendment clause (addition only), its Section 2 table identification (Table 4-1, not 4-2), Municode's 9-section amended-sections index, and the live codified text of both sections. The Municode caption the parent brief relied on was, in this instance, accurate - but it was accurate by luck of summary, and reading the body is what converts a plausible inference into a verified fact.
- One scare that resolved cleanly. The codified Sec. 27-43 page also carries an "Ordinance No. 2026-50" badge, which the parent brief did not record. That badge belongs to Sec. 27-6, not Sec. 27-43: Municode renders Article I as one page, and Ord. No. 2026-50 is the companion Subdivision Regulations ordinance (33 amended sections, Sec. 27-6 plus Article II Division 8, same File No. E2026-8 CH 27, split off as its own substitute "limited solely to the Subdivision Regulations"). Its 52-page body contains zero occurrences of "27-43" and zero occurrences of "height".
- A minor index discrepancy, immaterial (U). The ordinance caption and body both amend Sec. 27-184 and Sec. 27-199, but Municode's 9-section list for 2026-49 omits both. Most likely a Municode indexing artifact rather than a severance, since the body plainly contains Sections 5 and 7 enacting them. It cannot affect this question either way: the Sec. 27-199 change is confined to CD-1/CD-2.
- Identification caveat (U). The substitute ordinance PDF is captioned "ORDINANCE NO. 2026-______" with the number blank, because Tampa assigns the number at adoption. Binding this body to the number "2026-49" rests on convergence rather than on a single document bearing both: all 9 of Municode's listed 2026-49 amended sections appear in this body's caption, the adoption date matches, and the subject matter (certified recovery residences, parking, setbacks) matches. No document was found showing the number and the body text together.
Synthesis for RDCO
Direct answer: no. Ord. No. 2026-49 did not alter the Sec. 27-43 "Height" definition and did not alter the Sec. 27-156 RS-75 maximum-height cell. Its Sec. 27-43 amendment is additive by its own operative words ("amended by adding the underlined language"), and the single thing it adds is a definition of "certified recovery residence." Its Sec. 27-156 amendment operates on Table 4-1, the use schedule, while the 35 ft lives in Table 4-2, the area/height/bulk/placement schedule - two different tables inside the same code section, which is precisely the ambiguity that made the Municode caption alone insufficient. The ordinance does change a maximum height, which is why this question deserved an answer rather than an assumption, but that change is in Sec. 27-199 Table 19-2 and reaches only Channel District CD-1 and CD-2.
The parent brief's verdict survives unchanged, and no recomputation is needed. The 35 ft still runs from the required finished floor; the ~33 ft Sterling ridge still clears with roughly 4.5-5.5 ft of slack under the correct datum and 2.0 ft under the incorrect grade reading; height still is not a design constraint on this plan. The one substantive upgrade is to the verdict's confidence rather than its content: the parent brief carried an explicit conditional ("the amended text itself could not be read"), and that condition is now discharged against the ordinance body rather than its caption. The downstream recommendation is unaffected - still no redesign, still add the datum question to the Zoning Verification Letter list.
Two side effects of this ordinance do matter to the home build, neither of them about height. First, and worth the founder knowing because it changes what can be built next door rather than what he can build: Table 4-1 as amended makes certified recovery residences a permitted principal use (X) in RS-75 - by right, not by special use, subject to the new reasonable-accommodation procedure in Sec. 27-282.31, which includes a sixty-day deemed-approval default if the zoning administrator does not issue a written determination. That is a neighborhood-character fact about Sunset Park, not a constraint on 1212 S Suffolk, and it is the kind of thing that surfaces later as a surprise if nobody files it now. Second, Section 3 repeals Sec. 27-160, Special Street Setbacks, in its entirety - the whole street-by-street setback-from-centerline table is struck. A repeal can only relax a setback, never tighten one, so it cannot hurt the build; whether it helps depends on whether any street bounding the parcel was on that list, which is worth a glance when the survey is in hand. A third change, the striking of the Sec. 27-283.12(l) "EV Capable" parking requirement, applies only to developments over 50 parking spaces and is irrelevant to a single-family house.
The method lesson is the transferable part. The parent brief did the right thing by flagging the caption as insufficient instead of treating it as dispositive, and the flag was worth about forty minutes of retrieval to clear. The retrieval route that worked is worth recording: Municode 403s both WebFetch and curl and exposes ordinance captions only, but the Tampa City Council meeting record mirrors the full attachment set - agenda item, Planning Commission resolution, per-section Technical Coordinating Committee packets with underline/strikethrough, and the City Attorney's substitute-ordinance memo carrying the operative body. The amendment clauses in that body ("amended by adding the underlined language," "amended by adding underlined language and deleting the stricken language," "repealed in its entirety," "created to read as follows") are the evidence, because they state the operation performed on each section. Several of those pages were image scans with no text layer, so the sequence that worked was: download, pdftotext to map which pages carry text, render the scanned remainder to PNG, and read the images - with the bulk page-reading delegated to a sub-agent so that ten pages of scanned legal text never entered the parent context.
Why this is in the vault
This discharges the second open follow-up in [[2026-10-21-tampa-rs75-height-limit-datum]] and converts that brief's height verdict from conditional to verified, which removes the last reason the Sunset Park architect brief would need to budget for a height redesign. It also puts two previously unrecorded facts about RS-75 into the home-build file: certified recovery residences are now a by-right principal use in the district, and the Sec. 27-160 special street setbacks are repealed.
Open follow-ups
- Does the Tampa Forward rewrite's Article 9 draft definition of "Height" keep the required-finished-floor datum, or revert to grade? Installment 1 (2026-02-17) contains Article 9, and its height definition has still never been read - it is the only route by which this datum could change for a 2027 permit.
- Was any street bounding 1212 S Suffolk Dr on the repealed Sec. 27-160 special-street-setback table? The repeal can only relax, but the pre-repeal baseline is what the 2019 survey was drawn against.
- Does the Sec. 27-282.31 sixty-day deemed-approval default mean a certified recovery residence can establish in RS-75 without any public notice to adjacent owners? The section as enacted describes no notice step.
- What is the required finished-floor elevation Tampa will actually certify for a Zone AE lot at BFE 11.0? Still the open freeboard item from [[2026-07-22-ae-zone-elevation-cost-premium-tampa]]; it sets the datum's elevation, which this brief does not touch.
Related
- [[2026-10-21-tampa-rs75-height-limit-datum]] - the parent brief whose conditional verdict this discharges; its Sec. 27-43 quotation and Sterling slack math are inherited unchanged
- [[2026-10-11-tampa-sunset-park-zoning-overlay-far-lot-coverage]] - RS-75 Table 4-2 standards and Tampa Forward rewrite status; dedupe-checked, no overlap with this ordinance
- [[2026-10-17-sterling-plan-fit-and-cost]] - the ~33 ft ridge estimate the surviving verdict applies to
- [[zoning-flood-zone-findings]] - parcel zoning and flood facts, and the Zoning Verification Letter question queue this feeds
- [[2026-07-22-ae-zone-elevation-cost-premium-tampa]] - the still-open freeboard item that sets the datum's elevation
- [[2026-10-17-adu-pool-house-rules]] - carried the Sec. 27-43 "required finished floor" citation for accessory structures
Sources
- City of Tampa substitute ordinance, File No. E2026-8 CH 27, "July 2025 Land Development Code cycle," City Attorney memorandum dated April 22, 2026, 14 sections, captioned "ORDINANCE NO. 2026-______" (number blank pending adoption) - https://docs.meetings.tampamonitor.com/2026-06-04/meeting-2833/24180/memo-july-2025-land-development-code-cycle-substitute-ordinance-evening-session-may-14-2026-file-no.-e2026-8-ch27.pdf (read 2026-10-24; pages 2-13 are image scans read as rendered PNGs)
- City of Tampa Technical Coordinating Committee packet, "LDC Sec. 27-43, Sec. 27-156 Table 4-1, Sec. 27-282," including Exhibit E proposed language and the Planning Commission resolution of April 13, 2026 - https://docs.meetings.tampamonitor.com/2026-06-04/meeting-2833/24180/ldc-sec.-27-43-sec.-27-156-table-401-sec.-27-282-tcc-packet.pdf
- City of Tampa TCC packet, LDC Sec. 27-199 (Channel District maximum building height) - https://docs.meetings.tampamonitor.com/2026-06-04/meeting-2833/24180/ldc-sec.-27-199-tcc-packet.pdf
- City of Tampa TCC packets, LDC Sec. 27-160 and Sec. 27-283.12 - https://docs.meetings.tampamonitor.com/2026-06-04/meeting-2833/24180/ldc-sec.-27-160-tcc-packet.pdf and https://docs.meetings.tampamonitor.com/2026-06-04/meeting-2833/24180/ldc-sec.-27-283.12-tcc-packet.pdf
- Tampa City Council agenda, June 4, 2026 regular meeting (meeting-2833), item 24180 caption and vote line - https://tampamonitor.com/tampa-city-council/agendas/6-4-26-regular-meeting/ (third-party mirror of the city meeting record; the attached PDFs are the city's own documents)
- City of Tampa companion substitute ordinance, Subdivision Regulations (item 24435), later Ord. No. 2026-50 - https://docs.meetings.tampamonitor.com/2026-06-04/meeting-2833/24435/memo-and-ordinance-for-revised-title-division-8-subdivision-procedures.pdf
- Municode, Ordinance No. 2026-49 record and its 9-item Amended Sections list - https://library.municode.com/fl/tampa/ordinances/code_of_ordinances?nodeId=1432230 (read 2026-10-24 via Playwright; curl and WebFetch both 403)
- Municode, Ordinance No. 2026-50 record and its 33-item Amended Sections list - https://library.municode.com/fl/tampa/ordinances/code_of_ordinances?nodeId=1432231
- City of Tampa Code of Ordinances Sec. 27-43, Definitions ("Height"), version May 27, 2026 - https://library.municode.com/fl/tampa/codes/code_of_ordinances?nodeId=COOR_CH27ZOLADE_ARTIGEPR_DIV4DE_S27-43DE (re-read 2026-10-24; text unchanged from the 2026-10-21 reading)
- City of Tampa Code of Ordinances Sec. 27-156, Official schedule of district regulations - https://library.municode.com/fl/tampa/codes/code_of_ordinances?nodeId=COOR_CH27ZOLADE_ARTIIIESZODIDIRE_DIV1GEZODI_S27-156OFSCDIRE (re-read 2026-10-24; only 2026 badge is Ord. No. 2026-49)
- Vault: ~/rdco-vault/06-reference/research/2026-10-21-tampa-rs75-height-limit-datum.md
- Vault: ~/rdco-vault/06-reference/research/2026-10-11-tampa-sunset-park-zoning-overlay-far-lot-coverage.md
- Vault: ~/rdco-vault/01-projects/life/home-build/2026-10-17-sterling-plan-fit-and-cost.md
- Vault: ~/rdco-vault/01-projects/life/home-build/2026-10-17-adu-pool-house-rules.md
- Vault: ~/rdco-vault/06-reference/research/2026-07-22-ae-zone-elevation-cost-premium-tampa.md
- Vault: ~/rdco-vault/01-projects/home-rebuild-2027/zoning-flood-zone-findings.md