COMMUNITY REVIEW OF PROPOSED DEVELOPMENT AT 1001 VIRGINIA AVENUE

An Evidence-Based Review of the Proposed Solara at Shadowlawn Condominium

1001 Virginia Avenue, Virginia Beach, VA 23451

GPIN: 24178268130000 | DSC File: L07-021142

EXECUTIVE SUMMARY

This community review documents regulatory deficiencies and procedural gaps in the proposed "Solara at Shadowlawn" condominium development (24 three-story units on 1.51 acres, A-18 zoning). Systematic analysis of 49 Freedom of Information Act documents — comparing developer submissions against applicable federal, state, and local regulatory requirements — identified hundreds of regulatory issues and cross-document inconsistencies across all major compliance domains. Key findings include:

1. Foundational Title Defect: The parcel was created improperly by deed without required subdivision plat, cited in every city review letter. The lot may not be legally valid for development.

2. Endangered Species Act Violations: Northern Long-Eared Bat (NLEB) confirmed in Year-Round Presence Zone; developer falsely claimed bats "unlikely" in "dense urban setting." No Incidental Take Permit filed. 42-inch diameter trees marked for removal without wildlife assessment.

3. Migratory Bird and Eagle Violations: Osprey nesting documented in adjacent Marshview Park during nesting season (April 1-September 15); no nesting survey conducted on development site; 23 Birds of Conservation Concern identified by IPaC; bald eagle nest on adjacent Navy property within potential 660-foot buffer zone; no distance analysis performed.

4. AICUZ Incompatibility: Property in 75 dB DNL noise zone where residential use is designated "Not Compatible" per FAA guidelines. Site plan falsely states "<75 dB LDN" while Virginia Beach GIS confirms ZONE_ = "75." Virginia BRAC Act requires AICUZ review for discretionary floodplain permits.

5. Floodplain Fill Violations: Approximately 7 feet of fill proposed in FEMA Zone AE (BFE 8 ft) without hydraulic impact analysis, compensatory storage calculation, or freeboard verification. No demonstration that fill will not increase flood levels beyond the applicable federal standard.

6. Blank Army Corps Authorization: USACE Form 6285 (Certification of Compliance) is completely blank. General permit 23-SPGP-PASDO prohibits residential condominiums and authorizes only water-dependent activities.

7. Impaired Waters Noncompliance: Development drains to Rudee Inlet (prohibited for shellfish harvest). Chesapeake Bay TMDL compliance undemonstrated. No nutrient credit affidavit filed.

8. Stormwater Engineering Deficiencies: 231 documented issues including zero infiltration capacity in Chapanoke soil, underground chambers ineffective, rear ditch still 24 inches deep (violates 18-inch requirement), Virginia Avenue storm sewer redirect not modeled, orifice elevations mismatched.

9. Building Height Non-Compliance: Building elevations never submitted across 4 review rounds. CZO §604 compliance cannot be determined. Three-story buildings on 7 feet of fill may exceed height limits.

10. Pattern of Developer Misrepresentations: 225 documented discrepancies between developer responses and city review letters, including false claims about species presence, noise compatibility, and engineering compliance.

11. Missing Permits and Approvals: 980 process gaps identified across 37 document comparisons, including no ESA Section 7 consultation, no CWA §404 permit, no Virginia Water Protection Permit, no VMRC tidal wetlands permit, no jurisdictional determination.

12. Sea Level Rise, Resilience, and Additional Failures: Development contradicts Virginia Beach Sea Level Wise initiative, Hampton Roads Hazard Mitigation Plan, and CRS flood insurance discount program. Dead-end street creates dangerous evacuation bottleneck in flood zone — City confirmed evacuation capacity is "not a function of Traffic Engineering or requirement of site plan review."

13. Additional Municipal Code Requirements: No wetland buffer exists despite tidal wetlands immediately adjacent. Airport noise attenuation requires STC 49 walls and STC 38 windows in >75 dB zone with mandatory buyer disclosure — not addressed in site plan. Parking lot landscaping requires 1,440 sq ft of internal plantings. Shadowlawn residents already pay a dredging SSD surcharge — new impervious surface will accelerate sedimentation costs they bear.

Recommendation: Withhold site plan approval until all applicable code requirements are demonstrated, including Chesapeake Bay Preservation Area compliance, acoustical performance standards, and all outstanding federal and state permits.

GROUND 1: ILLEGAL PARCEL CREATION AND TITLE DEFECT

Foundational Legal Deficiency

The subject property (1001 Virginia Avenue, GPIN 24178268130000) was created improperly by deed at a time when a subdivision plat was required to be recorded. This deficiency is cited in every city review letter and represents a foundational legal impediment to development authorization.

Evidence of Improper Parcel Creation

City Review Comments (DSC File L07-021142):

Property Description Discrepancies:

The site plan narrative states: "The existing parcel was recorded via deed book 977 page 180. The parcel is 1.601 acres in total."

However, the legal description references: "PART OF PROPERTY KNOWN AS H.W. CHAFFEE 1.96 AC. AS SHOWN ON (M.B. 41 PG. 3) AND RECORDED IN (D.B. 977 PG. 180)."

This creates ambiguity regarding the exact parcel boundaries and whether the current lot configuration is legally valid.

Regulatory Requirement

Virginia Beach Subdivision Ordinance (Appendix B) establishes that parcels created by division must be recorded via approved subdivision plat. The Virginia Beach Subdivision Ordinance (Appendix B) requires that all parcel divisions be properly platted and recorded before any development authorization.

Legal Consequence

Without a properly recorded subdivision plat, the parcel may lack clear legal title for development. Any site plan approval issued without resolving this deficiency could be subject to legal challenge and rescission. The developer cannot proceed with construction until this foundational issue is resolved.

Recommended Action

City Development Services Center: Require applicant to obtain subdivision plat approval and record the plat in the land records before any further site plan review or approval.

GROUND 2: ENDANGERED SPECIES ACT VIOLATIONS

Critical Failure to Comply with ESA Section 9 Take Prohibition and Section 7 Consultation Requirements

16 U.S.C. § 1538(a)(1)(B) prohibits any person from "tak[ing] any [endangered] species within the United States." The proposed development creates serious Endangered Species Act liability through habitat modification and tree removal in documented NLEB habitat without any biological assessment. The developer has failed to conduct species surveys, failed to complete the USFWS NLEB Determination Key, failed to obtain required Incidental Take Permit authorization, and has misrepresented species presence to regulatory agencies. If NLEBs are present on site — as the year-round zone designation and habitat characteristics suggest — tree removal without an ITP would constitute prohibited take.

2.1 Northern Long-Eared Bat: Confirmed Endangered Species Presence

Official Species Confirmation:

The Virginia Department of Wildlife Resources (DWR) maintains an official NLEB and TCB Year-Round Zone 1 map that explicitly includes the 1001 Virginia Avenue property. This is the authoritative state source for endangered bat habitat designation.

Virginia DWR NLEB and TCB Year-Round Zone 1 Map confirms that 1001 Virginia Avenue is located within the NLEB and TCB Year-Round Zone 1, meaning the property provides year-round habitat for this federally endangered species.

Federal Reclassification to Endangered Status:

The Northern Long-Eared Bat was reclassified from "Threatened" to "Endangered" effective March 31, 2023. 87 FR 73488 (November 30, 2022) (87 FR 73488, November 30, 2022; effective March 31, 2023) removed the previous 4(d) rule that allowed incidental take exemptions. All take is now prohibited without an Incidental Take Permit.

State Protection:

4VAC15-20-130 (4VAC15-20-130) lists the Northern Long-Eared Bat as a state endangered species, providing concurrent state-level protection.

2.2 Developer's False Species Assessment

USFWS IPaC Response:

The developer submitted a response to the USFWS Information for Planning and Consultation (IPaC) system stating that bats are "unlikely to be affected" by the proposed development. The developer marked the species assessment upload as "Not Applicable" and claimed:

"Bats are unlikely to be affected by this project due to the dense urban setting and lack of suitable habitat."

This assessment is contradicted by official state habitat mapping and unsupported by any site-specific survey data:

1. Virginia DWR Official Mapping: The property is explicitly within the NLEB and TCB Year-Round Zone 1

2. Site Characteristics: The property contains 15+ mature trees (up to 42 inches diameter) that provide suitable NLEB roosting habitat

3. Proximity to Marshview Park: The site is directly adjacent to Marshview Park, a 50-acre Navy Watchable Wildlife Area established specifically to protect wildlife habitat

4. Owls Creek Corridor: The property is within the Owls Creek/Rudee Inlet watershed, a documented migratory corridor for bats

The developer's characterization of the site as "dense urban setting" is contradicted by the presence of substantial tree cover, wetlands, and proximity to protected wildlife areas.

2.3 Proposed Tree Removal in NLEB Habitat

Extent of Tree Removal:

The demolition and grading plans show extensive tree removal throughout the development site, including:

NLEB Habitat Modification:

Babbitt v. Sweet Home Chapter of Communities for a Great Oregon, 515 U.S. 687 (1995) (Babbitt v. Sweet Home Chapter of Communities for a Great Oregon, 515 U.S. 687, 1995) established that "harm" under ESA Section 9 includes "significant habitat modification or degradation that actually kills or injures wildlife by impairing breeding, feeding, or sheltering."

Note on Pending Regulatory Change: In April 2025, a proposed rule (90 FR 16102) was published to rescind the regulatory definition of "harm" that implements the *Sweet Home* framework. If finalized, this could narrow the scope of ESA Section 9's take prohibition regarding habitat modification. However, the *Sweet Home* Supreme Court decision itself interprets the statutory text and would remain binding precedent even if the regulatory definition changes. The statutory prohibition on "harm" in 16 U.S.C. § 1532(19) still stands.

The removal of mature trees in NLEB and TCB Year-Round Zone 1 constitutes unlawful habitat modification that will:

No Wildlife Impact Assessment:

The site plan contains no bat habitat assessment, no acoustic survey for NLEB presence, and no mitigation plan for tree removal impacts. The developer has not commissioned a qualified biologist to evaluate NLEB presence or propose avoidance/minimization measures.

2.4 Failure to Obtain Incidental Take Permit

16 U.S.C. § 1539 (16 U.S.C. § 1539) requires private parties to obtain Incidental Take Permits (ITP) with Habitat Conservation Plans before activities that may incidentally harm endangered species.

No evidence exists in the FOIA documents that:

Without an ITP, the developer cannot legally proceed with tree removal or habitat modification.

2.5 Federal Nexus Triggering ESA Section 7 Consultation

CWA Section 404 Permit Requirement:

The site contains standing water and ditches that may constitute "waters of the United States" under 33 U.S.C. § 1344 (33 U.S.C. § 1344). Fill placement in these jurisdictional waters requires an Army Corps of Engineers permit.

ESA Section 7 Mandatory Consultation:

16 U.S.C. § 1536 (16 U.S.C. § 1536) requires that "each Federal agency shall, in consultation with and with the assistance of the Secretary [of Interior], insure that any action authorized, funded, or carried out by such agency is not likely to jeopardize the continued existence of any endangered species."

When the Army Corps authorizes a Section 404 permit for a project that may affect an endangered species, the Corps must consult with USFWS under ESA Section 7. This consultation is mandatory and cannot be waived.

No Consultation Documented:

The FOIA documents contain no evidence that:

2.6 USACE General Permit Requirements

The developer may be relying on USACE Nationwide Permit 29 (Residential Developments) to authorize fill placement. 33 CFR Part 330 — Nationwide Permits (33 CFR Part 330) establishes that NWP 29 requires preconstruction notification (PCN) for impacts to waters of the United States.

NWP 29 Conditions Include:

The developer has not submitted a PCN to USACE or provided evidence of USFWS notification.

2.7 Citizen Suit Enforcement Mechanism

16 U.S.C. § 1540(g) (16 U.S.C. § 1540(g)) provides that "any person may commence a civil suit on his own behalf to enjoin any person... who is alleged to be in violation of any provision of this chapter."

Neighbors and environmental organizations may pursue a citizen suit under this provision, but must first serve 60-day written notice on the alleged violator, the Secretary of the Interior, and the State of Virginia identifying the specific ESA violation. This notice is a jurisdictional prerequisite — courts strictly enforce it and will dismiss suits filed without proper notice. Injunctive relief is available for imminent violations, but the notice must not be premature (pre-violation notice has been held insufficient). If the developer proceeds with tree removal without an ITP, they face potential federal criminal penalties and civil injunction.

2.8 Recommended Actions

USFWS (Federal):

Virginia DWR (State):

City Development Services Center:

GROUND 3: MIGRATORY BIRD AND BALD EAGLE VIOLATIONS

Unlawful Take of Protected Migratory Birds and Bald Eagles

The proposed development will cause unlawful "take" of migratory birds and bald eagles protected under federal law. The developer has failed to conduct nesting surveys, failed to identify buffer zones, and failed to implement seasonal construction restrictions.

3.1 Osprey Nesting in Adjacent Habitat

Osprey Nesting Documentation:

Adjacent Marshview Park (directly north of the development site) contains documented osprey nesting activity. eBird Hotspot L7146936 — Marshview Park, Virginia Beach (eBird Hotspot L7146936 — Marshview Park, Virginia Beach), a Cornell Lab of Ornithology citizen-science database with quality-control review, documents Great Blue Herons, Great Egrets, osprey, and dozens of migratory species with timestamped observations.

The development site itself contains standing water and wetland features that provide suitable osprey nesting habitat. No nesting survey has been conducted on the development parcel to determine whether active nests are present.

Osprey Nesting Season:

16 U.S.C. § 703 (16 U.S.C. § 703) prohibits take of migratory birds, nests, and eggs. Osprey nesting season in Virginia Beach extends from April 1 through September 15.

The site plan shows construction beginning in 2025 with no seasonal restrictions documented. If construction occurs during osprey nesting season, the project will cause:

Developer's False Claim:

The developer's environmental assessment states: "Osprey are unlikely to be affected by this project."

This claim is contradicted by:

1. Documented osprey presence in adjacent Marshview Park

2. Suitable osprey nesting habitat on site (standing water, tall trees)

3. Proximity to known osprey nesting areas

4. No nesting survey conducted

3.2 Twenty-Three Birds of Conservation Concern

USFWS IPaC Species List:

USFWS Information for Planning and Consultation (IPaC) (USFWS Information for Planning and Consultation system) identifies 23 Birds of Conservation Concern at the 1001 Virginia Avenue location, including:

Note: IPaC identifies species within a geographic radius that includes the broader coastal area. Some listed species (e.g., Roseate Tern, Piping Plover, Red Knot) are beach and coastal nesters that would not typically use this inland parcel. However, species that utilize wetland, standing water, and tree canopy habitat (e.g., Tricolored Heron, Black Skimmer) may directly use the development site.

Habitat Impacts:

The development will remove wetland habitat, standing water, and tree canopy used by applicable species for:

Legal Context for BCCs:

BCC designation is a USFWS advisory conservation planning tool and does not confer additional regulatory protection beyond the MBTA. All BCCs are protected as migratory birds under the MBTA regardless of their BCC status. However, the presence of 23 BCCs at this location demonstrates the ecological significance of the site and the potential scope of impacts from development.

Note on Current MBTA Interpretation: In April 2025, the Department of Interior restored Solicitor's Opinion M-37050, which interprets the MBTA as prohibiting only intentional take of migratory birds. Under this interpretation, incidental bird deaths from construction activity may not constitute MBTA violations. However, the Bald and Golden Eagle Protection Act (16 U.S.C. § 668) independently prohibits eagle disturbance regardless of the MBTA interpretation.

No Mitigation Plan:

The site plan contains no assessment of impacts to migratory birds or Birds of Conservation Concern and no mitigation measures.

3.3 Bald Eagle Nesting Pair and Buffer Zone Violation

Documented Eagle Nest:

Center for Conservation Biology — Virginia Eagle Nest Locator (Center for Conservation Biology — Virginia Eagle Nest Locator) documents an active bald eagle nesting pair known as "Stumpy and Victoria" on Navy property along Owls Creek, approximately 600-700 feet from the 1001 Virginia Avenue development site.

USFWS Buffer Zone Guidance:

50 CFR § 22.280 (50 CFR § 22.280) and USFWS National Bald Eagle Management Guidelines (2007) (USFWS National Bald Eagle Management Guidelines, 2007) recommend a 660-foot buffer around active bald eagle nests during breeding season for construction activities.

The distance from the Stumpy and Victoria nest to the development site may fall within this recommended buffer zone, creating potential for:

BGEPA Prohibition:

16 U.S.C. § 668 (16 U.S.C. § 668) prohibits any person from "knowingly, or with wanton disregard for the consequences of his act take, possess, sell, purchase, barter, offer to sell... any bald eagle... or any golden eagle."

"Take" includes disturbance that causes nest abandonment or breeding failure.

No Buffer Analysis:

The site plan contains no analysis of distance to the Stumpy and Victoria nest, no buffer zone designation, and no mitigation measures to prevent eagle disturbance.

3.4 Navy Watchable Wildlife Area

First Watchable Wildlife Area in Virginia:

The Navy property along Owls Creek, immediately adjacent to the development site, was designated as Virginia's first Watchable Wildlife Area (50 acres). NAS Oceana/Dam Neck Annex Watchable Wildlife Area This area was established specifically to protect wildlife habitat and facilitate wildlife observation.

The development will increase noise, light, and human activity immediately adjacent to this protected area, creating secondary impacts to wildlife habitat.

3.5 Migratory Bird Treaty Act Compliance Failure

16 U.S.C. § 703 (16 U.S.C. § 703) establishes that "unless and except as permitted by regulations... it shall be unlawful at any time, by any means or in any manner, to pursue, hunt, take, capture, kill, attempt to take, capture, or kill... any migratory bird... or any part, nest, or egg of any such bird."

Required Compliance Measures:

None of these measures are documented in the site plan.

3.6 Virginia Incidental Take Regulation

4VAC15-35 (4VAC15-35) governs incidental take of bird species in Virginia. General permits under this regulation require avoidance and minimization of migratory bird impacts from commercial construction. For activities in biologically significant avian habitat, an individual permit may require additional compensation measures.

The developer has not submitted an incidental take authorization application to Virginia DWR.

3.7 Recommended Actions

USFWS (Federal):

Virginia DWR (State):

City Development Services Center:

GROUND 4: AICUZ INCOMPATIBILITY AND MILITARY COMPATIBILITY VIOLATION

Residential Development in Incompatible Noise Zone with Factual Misrepresentation

The property is located in the 75 dB DNL noise zone near Naval Air Station Oceana, where residential use is designated as "Not Compatible" under federal and state guidelines. The developer has misrepresented the noise zone designation in the site plan, and the project violates Virginia's BRAC Act requirement to follow Navy AICUZ guidelines.

4.1 Official Noise Zone Designation: 75 dB DNL

Virginia Beach GIS Confirmation:

Virginia Beach GIS AICUZ MapServer Layer 3 (Virginia Beach GIS AICUZ MapServer Layer 3) is the authoritative local source for AICUZ noise zone designation. The official GIS service confirms that 1001 Virginia Avenue is located in ZONE_ = "75", which renders as "> 75 dB" — meaning the property is within the 75+ dB noise exposure area, corresponding to the 75-80 dB column in 14 CFR Part 150 Table 1.

NAS Oceana AICUZ Study:

NAS Oceana AICUZ Study (March 2014) (NAS Oceana AICUZ Study, March 2014) is the official Navy AICUZ study establishing noise contours and land use compatibility recommendations. The study confirms the 75 dB DNL zone designation for the 1001 Virginia Avenue area.

Economic Significance:

NAS Oceana generates approximately $1 billion annually for Virginia Beach's economy. The military installation is critical to the region's economic vitality and national defense.

4.2 FAA Incompatibility Designation

14 CFR Part 150 Table 1 — Residential Incompatibility:

14 CFR Part 150, Appendix A, Table 1 (14 CFR Part 150, Appendix A, Table 1) establishes FAA noise compatibility guidelines. The table designates residential uses as follows:

The 75-80 dB DNL zone has NO conditional pathway for residential use. Residential development is prohibited without exception.

The FAA guidance explicitly states: "Residential — Mobile home parks: N. Residential, other than mobile home parks: N [in 75-80 Ldn zone]. N = Land use and related structures are not compatible and should be prohibited."

Multi-Family Classification:

The FAA table groups ALL residential uses (other than mobile homes and transient lodging) into a single category. It does not distinguish single-family from multi-family, detached from attached, or apartments from condominiums. The proposed 24-unit condominium development falls squarely within "Residential, other than mobile home parks" — the category designated N at 75 dB.

Virginia Beach's own AICUZ regulations confirm this classification. The city groups "Multiple family dwellings, Condominiums, Hotels, Motels, Dormitories, Group homes" together for noise attenuation requirements. Virginia Beach Zoning Ordinance Art. 18, §§ 1803-1804 (Virginia Beach Zoning Ordinance Article 18) designates multiple-family dwellings — which explicitly includes condominiums — as "Not Compatible" in the 70+ dB zones.

There is no ambiguity in the classification: 24 condominium units = multi-family residential = Not Compatible at 75 dB DNL.

4.3 DoD AICUZ Program Requirements

DoD Instruction 4165.57 (DoD Instruction 4165.57) describes the 75+ dB zone as "the most affected area" requiring "the greatest degree of land use controls."

This is not simply a noise issue — it is a safety and quality-of-life prohibition. NAS Oceana operates F/A-18 Super Hornets in active military flight operations. The AICUZ program exists because people living under flight paths face real risk when military aircraft experience emergencies.

What 75 dB DNL means for residents in practice:

The 75 dB DNL (Day-Night Average Sound Level) represents cumulative noise exposure averaged over 24 hours, with a 10 dB penalty applied to nighttime operations (10 PM to 7 AM). This does not mean residents experience a constant 75 dB hum. It means:

The critical distinction: condominiums are the worst possible residential use case at 75 dB. Unlike a hotel where guests stay one or two nights, condominium residents are permanent occupants exposed to military jet noise 365 days a year. They will sleep there every night, raise children there, and spend the majority of their non-working hours in this noise zone. There is no "checking out" — they own the unit.

This is why the FAA table designates residential as plain N (prohibited) at 75 dB with no conditional pathway, while transient lodging (hotels) receives slightly different treatment. Permanent residential exposure is categorically worse than temporary exposure.

City encroachment reduction program contradiction:

Virginia Beach currently operates one of the most aggressive AICUZ encroachment reduction programs in the country, spending over $15 million per year purchasing residential properties in high-noise zones and converting them to compatible uses. The city has spent hundreds of millions of dollars over two decades removing residents from exactly the kind of noise zone where this developer proposes to put 24 new condominium units.

Approving 24 new permanent residential units in the 75 dB zone would directly undermine the city's own encroachment reduction investment and contradict the policy rationale behind every property the city has purchased in this area.

4.4 Developer's Factual Misrepresentation

Site Plan Noise Zone Statement:

The site plan contains the following statement:

"THIS SITE LIES WITHIN AIRCRAFT ACCIDENT POTENTIAL ZONE N/A AND /OR THE CLEAR ZONE AND/OR NOISE ZONE(S) <75 dB LDN AND MAY BE SUBJECT TO AIRCRAFT ACCIDENTS AND/OR ABOVE AVERAGE NOISE LEVELS DUE TO ITS PROXIMITY TO AIRPORT OPERATIONS."

This statement is factually false. The site plan states the noise zone is "<75 dB LDN" (less than 75 dB), when the official Virginia Beach GIS confirms the zone is "75" (75 dB DNL).

This is not a minor typographical error. The difference between "<75 dB" and "75 dB" is the difference between a zone with conditional pathways for residential use and a zone with NO conditional pathways. The misrepresentation has the effect of obscuring the incompatibility of the proposed residential development.

4.5 Virginia BRAC Act Requirement for AICUZ Compliance

2006 Virginia Uncodified Act, Chapter 266:

2006 Virginia Uncodified Act, Chapter 266 (2006 Virginia Uncodified Act, Chapter 266) was enacted as a condition of the Base Realignment and Closure (BRAC) process to save NAS Oceana from closure. The Act requires:

"The City of Virginia Beach shall follow Navy Air Installation Compatible Use Zone (AICUZ) guidelines in deciding discretionary applications for property in noise levels of 70 dB DNL or greater."

Key Language: "discretionary applications" — The BRAC Act applies to discretionary decisions by the city, not ministerial approvals.

4.6 Floodplain Development Permit as Discretionary Action

Triggering BRAC Act Compliance:

The proposed development requires a floodplain development permit for fill placement in FEMA Zone AE. Virginia Beach Code, Appendix K (Virginia Beach Code, Appendix K) requires that any fill in the AE zone must be authorized by a floodplain development permit.

Discretionary Nature of Floodplain Permit:

A floodplain development permit is a discretionary action by the city. The city must evaluate whether the fill will increase flood levels, whether compensatory storage is adequate, and whether the development is consistent with floodplain management goals.

BRAC Act Application:

Because the floodplain development permit involves technical discretion (evaluating compensatory storage adequacy, flood level increases, and consistency with floodplain management goals), it may qualify as a discretionary action triggering the BRAC Act. If so, the city must follow Navy AICUZ guidelines — which prohibit residential development in the 75+ dB zone — when deciding whether to issue the permit.

Important Legal Context: Condominiums are permitted by right in the A-18 zoning district (CZO Article 6, § 601), meaning the developer does not need a rezoning or conditional use permit. The primary approval pathway is site plan review, which Virginia law generally treats as ministerial. This creates a legal tension: the AICUZ overlay (Article 18, § 1803) applies specifically to five enumerated "discretionary development application" types — rezonings, conditional use permits, nonconforming use conversions, street closures, and special exceptions — and site plan review is not among them.

The strongest legal hook for BRAC Act applicability is the floodplain development permit, which involves evaluative judgment (not merely checking code compliance) and therefore has the strongest claim to "discretionary" status. The policy argument — that approving residential development in a 75 dB zone contradicts FAA guidelines, DoD AICUZ program goals, and the city's own encroachment reduction investment — remains powerful even if the legal mechanism is contested.

4.7 Virginia Beach AICUZ Overlay District

Virginia Beach Zoning Ordinance Art. 18, §§ 1803-1804 (Virginia Beach Zoning Ordinance Article 18, §§ 1803-1804) establishes the AICUZ Overlay District.

Section 1804 Prohibition: Section 1804 uses mandatory prohibitory language: "no application...shall be approved unless the uses and structures it contemplates are designated as compatible under Table 1...unless the city council finds that no reasonable use designated as compatible...can be made of the property." Table 1 designates all residential uses (including multiple-family dwellings and condominiums) as "N" (Not Compatible) in the 70-75 dB and >75 dB noise zones.

Section 1807 Reservation of Powers: Section 1807 provides that "nothing in this Article shall be construed to require the city council to approve any application solely because it meets the requirements of this Article...the city council shall be entitled to exercise its authority in such applications to the fullest extent allowed by law." The AICUZ requirements are a floor, not a ceiling.

Applicability Limitation: Section 1803 applies to "discretionary development applications," defined as: (1) rezonings, (2) conditional use permits, (3) nonconforming use conversions, (4) street closures, and (5) special exceptions for Alternative Compliance. Site plan review is not among these enumerated categories. However, Section 1804's prohibition is framed as applying to any "application," which may be read more broadly than Section 1803's enumerated list.

The site plan proposes 24 residential condominium units (multiple-family dwellings) in the >75 dB zone, which is explicitly designated as "Not Compatible" in Table 1.

Pre-existing Residential Is Not Precedent: Existing residential properties in the AICUZ noise zones are legally nonconforming uses that the city and state have invested over $130 million since 2006 to acquire and remove through the AICUZ encroachment reduction program. The only recent comparable development (Silo at Southern Pines, 2023) was required to redesign to move all 176 residential units outside the AICUZ overlay zone before receiving Navy concurrence and city approval. The existence of legacy nonconforming residential does not authorize new residential construction at greater density.

4.8 Workforce Housing Exclusion

Virginia Beach Zoning Ordinance § 2103 (Virginia Beach Zoning Ordinance § 2103) explicitly excludes properties in noise zones 65+ dB from the Workforce Housing Overlay District.

This exclusion is an official city acknowledgment that residential development is incompatible in these noise zones. The city cannot simultaneously exclude properties from workforce housing due to noise incompatibility while approving standard residential development in the same noise zone.

4.9 Noise Attenuation Requirements

Virginia Beach Code, Appendix I (Virginia Beach Code, Appendix I) requires noise level reduction (NLR) and disclosure requirements for properties in AICUZ noise zones.

The site plan does not provide:

4.10 Recommended Actions

City Council:

Note: Site plan review for by-right development in Virginia Beach is an administrative staff function (Development Services Center), not a Planning Commission action. The Planning Commission reviews rezonings and conditional use permits. The recommendations below are directed to the appropriate bodies.

Development Services Center:

NAS Oceana (Military):

GROUND 5: FLOODPLAIN FILL AND FEMA VIOLATIONS

Unauthorized Fill in Special Flood Hazard Area Without Compensatory Storage or No-Rise Certification

The proposed development requires approximately 7 feet of fill in FEMA Zone AE (Base Flood Elevation 8 feet) to achieve the required lowest floor elevation of 10 feet NAVD 88 with 2-foot freeboard. The developer has failed to provide any hydraulic impact analysis demonstrating that this fill will not increase flood levels beyond the applicable federal standard, compensatory storage calculations, or freeboard verification.

5.1 FEMA Zone AE Designation and Base Flood Elevation

Official FEMA Flood Insurance Rate Map:

FIRM Panel 5155310128G (FIRM Panel 5155310128G, effective January 16, 2015) is the official FEMA map for the City of Virginia Beach. The map designates 1001 Virginia Avenue as located in:

The property spans multiple flood zones, with the most restrictive being Zone AE with BFE = 8.0 feet.

5.2 Lowest Floor Elevation Requirement

NFIP Regulations:

44 CFR § 60.3(c) (44 CFR § 60.3(c)) establishes minimum standards for development in AE zones:

"Require that all new construction and substantial improvements of residential structures within Zones A1-30, AE, and AH zones on the community's FIRM have the lowest floor, including basement, elevated to or above the base flood level."

Virginia Beach Floodplain Ordinance:

Virginia Beach Code, Appendix K (Virginia Beach Code, Appendix K) requires 2 feet of freeboard above BFE for residential construction.

Calculation:

5.3 Proposed Fill Elevation and Volume

Existing Grade:

The topographic survey shows existing ground elevations ranging from approximately 0.28 feet to 10.15 feet NAVD 88, with most of the site at 4.0-7.0 feet elevation.

Proposed Grade:

The grading plan shows proposed finished grades reaching 9.0-10.42 feet NAVD 88 across the development area, with building lowest floor elevations at 10.75 feet (residential units) and 10.25 feet (garages).

Fill Volume:

To achieve the required 10.0 feet NAVD 88 lowest floor elevation across the 1.51-acre site, the developer must place approximately 7 feet of fill in the central portions of the development.

This represents a substantial volume of fill material being discharged into the Special Flood Hazard Area.

5.4 Compensatory Storage Requirement

NFIP Floodplain Development Standards:

Two tiers of federal regulation apply depending on whether a regulatory floodway has been designated:

If a regulatory floodway is designated at 1001 Virginia Avenue, the no-rise standard applies. If not, the one-foot rise limit under 60.3(c) applies. In either case, the developer has not provided the hydraulic analysis required to demonstrate compliance with either standard.

FEMA Technical Guidance:

FEMA Technical Bulletin 10 (FEMA Technical Bulletin 10: "Ensuring Flood Loss Reduction from Fill") recommends that fill placed in Special Flood Hazard Areas provide compensatory storage at a 1:1 ratio or greater. While this is federal guidance rather than a binding requirement, many communities, including Virginia Beach, adopt compensatory storage requirements in their local floodplain ordinances.

Virginia Beach Local Requirement:

Virginia Beach Code, Appendix K (Virginia Beach Floodplain Ordinance) establishes local standards that may exceed the federal minimum, including the 2-foot freeboard requirement. The developer must demonstrate compliance with both federal and local standards.

Compensatory Storage Analysis:

Regardless of which federal tier applies, the developer must demonstrate that 7 feet of fill across the development area will not increase flood levels for adjacent properties. This requires hydraulic modeling showing pre- and post-development flood elevations.

Developer's Failure to Provide Analysis:

The site plan and stormwater analysis contain no compensatory storage calculations. The developer has not:

5.5 No-Rise Certification Requirement

Hydraulic Impact Analysis Requirement:

Whether the no-rise standard (floodway) or one-foot standard (Zone AE without floodway) applies, the developer must provide a hydraulic analysis demonstrating that the proposed fill will not cause prohibited increases in flood levels. 44 CFR Parts 59-60 (44 CFR Parts 59-60) establishes these requirements.

Developer's Failure to Provide Analysis:

The site plan contains no hydraulic impact analysis or flood level increase calculation. The developer has not demonstrated that 7 feet of fill will not increase flood levels in downstream areas (Owls Creek, Rudee Inlet) or on adjacent properties along Virginia Avenue.

5.6 Freeboard Compliance Verification

Marginal Compliance:

The site plan shows building lowest floor elevations at 10.75 feet (residential) and 10.25 feet (garages). With BFE = 8.0 feet, this provides:

However, the site plan does not explicitly certify that all lowest floor elevations meet the 10.0 feet minimum. Some garage elevations are shown at 9.80-9.90 feet, which may fall below the requirement.

5.7 Recent Tidal Flooding Events

October 2025 Nor'easter:

The October 12, 2025 nor'easter produced the worst tidal flooding in Hampton Roads since January 2022, with water levels at Rudee Inlet reaching 7.3 feet per the National Weather Service. For context, the all-time record at the Sewells Point gauge remains the 1933 Chesapeake-Potomac Hurricane (8.02 feet MLLW), followed by Hurricane Isabel in 2003 (7.89 feet). The October 2025 event, while not historically unprecedented, demonstrates the ongoing vulnerability of low-lying areas near Rudee Inlet to storm surge and tidal flooding.

The proposed development, with lowest floor elevations only 2 feet above the 100-year flood elevation, will be vulnerable to:

5.8 Floodplain Development Permit Requirement

Discretionary Permit:

Virginia Beach Code, Appendix K requires a floodplain development permit for fill in the AE zone. This permit is discretionary, meaning the city must evaluate whether the fill meets NFIP standards.

City's Obligation:

The city cannot issue a floodplain development permit unless the developer demonstrates:

Developer's Failure to Demonstrate Compliance:

The site plan does not provide any of these required demonstrations.

5.9 Recommended Actions

City Development Services Center:

FEMA (Federal):

Virginia Beach City Council:

GROUND 6: BLANK ARMY CORPS AUTHORIZATION AND GENERAL PERMIT MISAPPLICATION

USACE Form 6285 Completely Blank; General Permit 23-SPGP-PASDO Prohibits Residential Condominiums

The developer has submitted a blank USACE Form 6285 (Certification of Compliance) and appears to be relying on a general permit that explicitly prohibits residential condominium development. There is no evidence of valid Army Corps authorization for the proposed project.

6.1 USACE Form 6285 — Completely Blank

Document Status:

The FOIA file contains a USACE Form 6285 (Certification of Compliance with the Nationwide Permit General Conditions) that is completely blank. The form contains:

Form Purpose:

USACE Form 6285 is the official certification that a project complies with the general conditions of a Nationwide Permit. A blank form has no legal effect and provides no authorization for the project.

6.2 General Permit 23-SPGP-PASDO vs. Nationwide Permits

Permit Type Clarification:

The FOIA documents reference "23-SPGP-PASDO," which is the 2023 State Programmatic General Permit issued by the Norfolk District of USACE. "PASDO" stands for Pier, Aquaculture, Shoreline, Dredging, and Other activities. This is a regional programmatic permit, distinct from Nationwide Permits. The "23" refers to the year (2023), not to NWP 23. This permit authorizes specific water-dependent activities, not residential construction.

NWP 29 Acreage and Condition Limitations:

While NWP 29 does authorize discharges for residential developments including multi-family projects, it imposes strict limitations:

33 CFR Part 330 — Nationwide Permits (33 CFR Part 330) establishes these scope and conditions.

Why NWP 29 Likely Cannot Apply Here:

Given the site characteristics (FEMA Zone AE, standing water, ditches, NLEB habitat, proximity to wetlands, prohibited receiving waters), the Norfolk District engineer would likely determine that the project has more than minimal individual and cumulative adverse environmental effects, triggering the requirement for an individual permit under 33 CFR 330.1(d). Key factors:

1. Fill in jurisdictional waters exceeds minimal impact thresholds

2. NLEB endangered species habitat triggers mandatory USFWS coordination

3. Discharge to impaired waters (Rudee Inlet) raises cumulative impact concerns

4. The blank USACE Form 6285 provides no evidence that NWP 29 was even evaluated

6.3 State Programmatic General Permit Inapplicability

23-SPGP-PASDO Scope:

The 2023 SPGP-PASDO issued by the Norfolk District authorizes specific categories of water-dependent activities:

Residential condominium construction is not a water-dependent activity and falls outside the scope of 23-SPGP-PASDO entirely. The developer cannot rely on this permit for authorization.

6.4 Preconstruction Notification Requirement

PCN Requirement:

33 CFR Part 330 — Nationwide Permits requires that applicants submit a Preconstruction Notification (PCN) to USACE for activities that may exceed the acreage thresholds or impact sensitive resources.

No PCN Evidence:

The FOIA documents contain no evidence that:

6.5 Individual Permit Requirement

Likely Outcome:

Given the project's characteristics (multi-family residential, substantial fill in AE zone, wetland impacts, endangered species habitat), the project likely requires an individual permit from USACE, not a general permit.

An individual permit requires:

No Individual Permit Application:

The FOIA documents contain no evidence that an individual permit application has been filed.

6.6 CWA Section 404 Permit Requirement

33 U.S.C. § 1344 (33 U.S.C. § 1344) requires an Army Corps permit for "the discharge of dredged or fill material into the navigable waters at specified disposal sites."

The site contains standing water and ditches that may constitute "waters of the United States" under 33 CFR § 328.3 — Definition of Waters of the United States (33 CFR § 328.3).

Jurisdictional Determination:

Before any fill can be placed, the developer must obtain a jurisdictional determination from USACE confirming whether the standing water and ditches are jurisdictional waters.

Post-Sackett Jurisdictional Analysis:

Sackett v. EPA, 598 U.S. 651 (2023) narrowed CWA jurisdiction by requiring wetlands to have a "continuous surface connection" to navigable waters. This raises a threshold question: do the standing water and ditches at 1001 Virginia Avenue have a continuous surface connection to Owls Creek or Rudee Inlet? If so, CWA jurisdiction applies and a Section 404 permit is required. If the features are isolated with no surface connection, Sackett may limit federal jurisdiction.

However, three factors favor jurisdiction here: (1) the site drains via ditches and storm sewer to Owls Creek, which connects to Rudee Inlet and the Atlantic Ocean; (2) the existing ditch system creates a surface hydrological connection; and (3) the wetlands delineated by MSA, P.C. on the site plan appear to be connected to the broader Owls Creek watershed. A jurisdictional determination by USACE would resolve this question definitively.

Critically, even if Sackett limits federal CWA jurisdiction, Virginia's own water protection laws apply independently. Va. Code § 62.1-44.15:20 (Virginia Water Protection Permit) may provide state jurisdiction over waters that no longer qualify under the federal standard.

No Jurisdictional Determination:

The FOIA documents contain no evidence that a jurisdictional determination has been requested or obtained. The developer has not addressed the Sackett jurisdictional standard.

6.7 Recommended Actions

USACE (Federal):

City Development Services Center:

Virginia DEQ (State):

GROUND 7: IMPAIRED WATERS AND WATER QUALITY VIOLATIONS

Development in Condemned Shellfish Waters Without TMDL Compliance or Nutrient Credit Verification

The proposed development drains to Rudee Inlet, which is classified as prohibited for shellfish harvest due to water quality impairment. The developer has failed to demonstrate Chesapeake Bay TMDL compliance and has not filed evidence of nutrient credit purchase.

7.1 Rudee Inlet Condemned Status

Virginia Marine Resources Commission Designation:

Rudee Inlet is officially classified as prohibited for shellfish harvest by the Virginia Marine Resources Commission (VMRC). VDH Division of Shellfish Safety — Rudee Inlet Classification (Virginia Department of Health, Division of Shellfish Safety) documents that Rudee Inlet is closed to shellfish harvest due to water quality impairment.

Impairment Cause:

The condemnation is due to elevated levels of fecal coliform bacteria and other pathogens resulting from:

Regulatory Significance:

The prohibited shellfish classification confirms that Rudee Inlet is an "impaired water" under 33 U.S.C. § 1313(d) (33 U.S.C. § 1313(d), Clean Water Act Section 303(d)).

7.2 Owls Creek/Rudee Inlet Watershed Characteristics

Watershed Size:

The Owls Creek/Rudee Inlet watershed is approximately 3,000 acres, making it the smallest major watershed in Virginia Beach. This small watershed size means that each new development has a proportionally larger impact on water quality.

Existing Impairment:

The watershed is already impaired due to existing development. The addition of 0.635 acres of new impervious surface (41.3% increase in site imperviousness) will further degrade water quality.

Cumulative Impact:

The development will contribute to cumulative degradation of the already-impaired Rudee Inlet, making it even more difficult to achieve water quality standards.

7.3 Chesapeake Bay TMDL Compliance

TMDL Requirement:

EPA Chesapeake Bay TMDL (2010) (EPA Chesapeake Bay TMDL, 2010) establishes Total Maximum Daily Load limits for nitrogen and phosphorus in the Chesapeake Bay watershed.

Virginia Beach is required to achieve specific pollutant load reductions to comply with the TMDL. The city's MS4 (Municipal Separate Storm Sewer System) permit requires that all new development demonstrate TMDL compliance.

Developer's TMDL Analysis:

The stormwater analysis includes a VRRM (Virginia Runoff Reduction Method) calculation showing:

The analysis shows that the development will increase phosphorus loading to the Chesapeake Bay, contrary to the TMDL requirement for load reduction.

Insufficient On-Site Treatment:

The developer proposes on-site treatment of only 0.34 lb/yr of phosphorus, leaving 0.97 lb/yr of post-development load. The required reduction is 0.55 lb/yr, but only 0.34 lb/yr is achieved on-site.

The remaining 0.21 lb/yr is proposed to be offset through nutrient credit purchase.

7.4 Nutrient Credit Purchase — No Evidence of Availability

Nutrient Credit Requirement:

The stormwater analysis states: "The remaining 0.21 lb/yr is achieved through nutrient credit purchase; the availability letter is provided in Appendix C2."

Missing Documentation:

The FOIA documents do not include Appendix C2 or any evidence that:

Regulatory Concern:

Nutrient credit programs are designed to allow developers to offset impacts when on-site treatment is infeasible. However, the credits must be:

1. Verified to exist

2. From a legitimate source (wastewater treatment plant upgrades, agricultural best management practices, etc.)

3. Retired in the same watershed or adjacent watershed

4. Permanent and enforceable

No evidence exists that these requirements are met.

7.5 Stormwater Management Inadequacy

Underground Chamber System:

The developer proposes stormwater management using 268 StormTech SC160 underground infiltration chambers. However, infiltration testing shows zero infiltration capacity in the Chapanoke soil at the site.

Infiltration Test Results:

ETS infiltration testing (February 24, 2025) shows:

System Ineffectiveness:

Site-specific infiltration testing shows the soil at this location has zero infiltration capacity, rendering the underground chambers ineffective as infiltration BMPs. While StormTech chambers can be configured for detention-only use (with a thermoplastic liner and controlled underdrain outlet), no evidence exists in the site plan of such modifications. Without liner and underdrain, the water will:

Additionally, even if the chambers are reconfigured for detention-only operation, the VRRM infiltration credit claimed in the stormwater analysis cannot be applied to a detention-only system.

Water Quality Impact:

The development will discharge untreated stormwater to the already-impaired Rudee Inlet, further degrading water quality and making it even more difficult to achieve TMDL compliance.

7.6 Virginia Stormwater Management Act Compliance

Va. Code § 62.1-44.15:24 et seq. (Va. Code § 62.1-44.15:24 et seq.) requires stormwater management plans for land-disturbing activities.

The developer's plan fails to demonstrate:

7.7 Chesapeake Bay Preservation Act Compliance

Va. Code § 62.1-44.15:67 et seq. (Va. Code § 62.1-44.15:67 et seq.) establishes Resource Protection Areas (RPAs) and Resource Management Areas (RMAs) in the Chesapeake Bay watershed.

The development must comply with water quality standards in these areas. The proposed development, with inadequate stormwater treatment and increased impervious surface, fails to meet these standards.

7.8 Recommended Actions

Virginia DEQ (State):

City Development Services Center:

VMRC (State):

GROUND 8: STORMWATER ENGINEERING DEFICIENCIES AND DESIGN FAILURES

231 Documented Engineering Issues Including Zero Infiltration Capacity, Inadequate Ditch Depth, and Unmodeled Storm Sewer Impacts

The stormwater design contains documented deficiencies that render the system inadequate to manage runoff and protect water quality. Critical issues include zero infiltration capacity in proposed BMPs, inadequate ditch depth, and failure to model impacts to existing storm sewer infrastructure.

Applicable Ordinance: The City adopted a new Erosion and Stormwater Management Ordinance (Ord. No. 3784, September 17, 2024) — Virginia Beach Code Appendix D — which applies to this project. Key requirements include:

8.1 Zero Infiltration Capacity in Chapanoke Soil

Soil Characteristics:

The site is underlain by Chapanoke silt loam, classified by NRCS as "somewhat poorly drained" with moderately slow permeability (0.2-0.6 in/hr) and a hydrologic soil group of C/D (Group C when drained, Group D in its natural undrained state). Va. Code § 62.1-44.15:24 et seq. requires that stormwater BMPs be designed based on actual soil infiltration capacity.

Infiltration Testing:

ETS infiltration testing (February 24, 2025) conducted at three boring locations shows:

Test Conclusion:

The geotechnical report states: "The water in the casing did not infiltrate at all at the test locations. The slow rate of infiltrations is due to the cohesive clay materials as well as the presence of the receiving clay layers."

Design Implication:

Underground infiltration chambers cannot function in soil with zero infiltration capacity. The water will not percolate into the soil and will instead remain in the chambers until they overflow.

8.2 Underground Chamber System Ineffectiveness

Proposed System:

The developer proposes 268 StormTech SC160 underground infiltration chambers in two BMPs:

Design Assumption:

The design assumes that water will infiltrate into the soil at a rate sufficient to empty the chambers during the design storm event. However, infiltration testing shows zero infiltration capacity.

Actual Performance:

With zero infiltration capacity, the chambers will:

1. Fill with water during the storm event

2. Remain full after the storm ends

3. Overflow to the storm sewer system

4. Discharge untreated stormwater to Rudee Inlet

Water Quality Impact:

The development will discharge untreated stormwater containing:

These pollutants will degrade water quality in the already-impaired Rudee Inlet.

8.3 Groundwater Separation Deficiency

PWDSM Requirement:

Virginia Beach Public Works Design Standards Manual (PWDSM) (Virginia Beach Public Works Design Standards Manual, Section 8.5.B.5) requires a minimum 2-foot separation between the bottom of underground stormwater facilities and the seasonal high groundwater elevation.

Site Conditions:

The geotechnical report states: "The seasonal high groundwater elevation is approximately 3 feet below the ground surface."

Based on existing ground elevation of 7.0 feet, the seasonal high groundwater elevation is 4.0 feet NAVD 88.

Proposed Chamber Elevation:

The stormwater design shows underground chamber invert elevations at:

Separation Calculation:

Deficiency:

The separation is less than the required 2 feet, violating PWDSM standards. The chambers will be partially saturated during high groundwater periods, reducing their storage capacity and effectiveness.

8.4 Rear Ditch Depth Non-Compliance

PWDSM Requirement:

Virginia Beach Public Works Design Standards Manual (PWDSM) (Virginia Beach Public Works Design Standards Manual, Section 8.4.B.5) requires that ditches deeper than 18 inches must be piped.

Existing Condition:

The site contains an existing ditch along the rear and west side of the property. The ditch is approximately 24 inches deep, exceeding the 18-inch threshold.

Developer's Response:

The developer claims that the ditch will be "regraded to 18 inches" to comply with the standard. However:

1. No cross-sections showing the regrading are provided

2. No calculations showing how regrading will be accomplished without impacting drainage

3. No evidence that the regrading will not increase flooding in adjacent areas

City Review Comment:

The city review notes that the rear ditch remains 24 inches deep and does not comply with PWDSM standards.

8.5 Virginia Avenue Storm Sewer Redirect — Not Modeled

Existing Infrastructure:

The site drains to an existing storm sewer system under Virginia Avenue. The developer proposes to redirect stormwater flows to a new piped system along the north portion of the property.

Modeling Requirement:

The stormwater analysis must model the impact of the redirect on the existing Virginia Avenue storm sewer system. The model must demonstrate that:

1. The existing system has capacity for the redirected flows

2. The redirect will not cause flooding in adjacent areas

3. The redirect will not cause backwater effects in the existing system

Developer's Response:

The developer states: "Work required would be excessive" and does not provide modeling of the Virginia Avenue storm sewer impacts.

City Review Comment:

The city review notes that the Virginia Avenue storm sewer redirect has not been modeled and that the developer has not demonstrated that the existing system can accommodate the additional flows.

8.6 Orifice Elevation Discrepancies

Design Inconsistency:

The stormwater analysis includes a SWMM hydraulic model with orifice elevations for the outlet structures. However, the orifice elevations in the model do not match the elevations shown on the grading plans.

Example Discrepancy:

Impact:

This discrepancy affects the hydraulic calculations and may result in:

8.7 Roughness Coefficient Errors

Manning's n Coefficient:

The SWMM model uses Manning's roughness coefficient (n) to calculate flow velocity in pipes and channels. The coefficient must be selected based on the pipe material and condition.

Documented Errors:

The model contains multiple roughness coefficient errors:

Impact:

Incorrect roughness coefficients result in inaccurate flow velocity calculations and may underestimate peak flows and flooding risk.

8.8 Curve Number Calculation Issues

Pre-Development Curve Number:

The analysis shows pre-development curve number (CN) of 81.7 for Type D soils. This is based on:

Post-Development Curve Number:

The analysis shows post-development CN of 90.4 for Type D soils. This represents an 8.7-point increase in CN.

Concern:

The post-development CN of 90.4 is very high and indicates that the site will generate substantial runoff. However, the stormwater design relies on underground infiltration chambers that have zero infiltration capacity. This is a fundamental design contradiction.

8.9 Peak Flow Attenuation Inadequacy

1-Year Storm Event:

Concern:

The compliance margin is only 1.2%, leaving virtually no safety factor for modeling uncertainty or design variations. Any minor change to the design could result in exceedance of the allowable discharge.

10-Year Storm Event:

Concern:

The 10-year storm event shows virtually no attenuation, with post-development peak flow nearly equal to pre-development peak flow. This indicates that the detention system is inadequate for larger storm events.

8.10 Pipe Surcharge During Design Storms

SWMM Model Results:

The SWMM model shows that multiple pipes in the proposed stormwater system are surcharged (operating under pressure) during the 10-year storm event:

Concern:

Pipes with peak flow/design flow ratios exceeding 1.0 are operating beyond their design capacity. This indicates:

8.11 Recommended Actions

City Development Services Center:

Virginia DEQ (State):

GROUND 9: BUILDING HEIGHT NON-COMPLIANCE

Building Elevations Never Submitted; CZO §604 Compliance Cannot Be Determined

The developer has failed to submit building elevations across four review rounds, making it impossible to verify compliance with Virginia Beach height regulations. The three-story buildings on 7 feet of fill may exceed height limits.

9.1 CZO §604 Height Regulation Requirement

Virginia Beach CZO § 604 — Height Regulations (Virginia Beach CZO § 604) establishes height regulations for buildings in various zoning districts. For A-18 zoning (multi-family residential), the maximum building height is 35 feet (CZO § 604: "For the A-12 and A-18 Apartment Districts, the maximum height for all buildings and structures is thirty-five (35) feet").

Height Measurement:

Building height is measured from the lowest point of the foundation to the highest point of the roof (including mechanical equipment, antennas, etc.). The measurement must account for:

9.2 Developer's Failure to Submit Building Elevations

Review Round 1 (April 11, 2025):

City review comment: "Building elevations have not been provided in compliance with CZO Sec. 604 height regulations."

Review Round 2 (July 11, 2025):

City review comment: "Building elevations still not provided. This is a critical deficiency that must be resolved before site plan approval."

Review Round 3 (October 10, 2025):

City review comment: "Building elevations continue to be missing. Applicant must submit detailed building elevations showing height compliance."

Review Round 4 (Current):

Building elevations still not submitted. The site plan contains only a notation: "3 - STORY CONDO UNIT W/ GARAGE MAX 3rd STORY EAVE HEIGHT = 30' MAX. BUILDING HEIGHT = 35' (TYP TO ALL)"

9.3 Inadequacy of Notation

Missing Information:

The notation "MAX. BUILDING HEIGHT = 35'" is insufficient for height compliance verification. The city requires:

1. Architectural elevations showing:

- Finished grade elevation at each building location

- Foundation depth

- First floor elevation

- Each story height

- Roof pitch and ridge height

- Total height measurement

2. Height calculations showing:

- Lowest point of foundation

- Highest point of roof

- Total height in feet

- Comparison to CZO §604 maximum height

3. Compliance certification signed by a licensed architect

Developer's Notation Deficiency:

The notation provides only a single height figure ("35'") without:

9.4 Impact of 7 Feet of Fill on Height Calculation

Finished Grade Elevation:

The grading plan shows proposed finished grades reaching 9.0-10.42 feet NAVD 88 across the development area. This represents approximately 7 feet of fill above existing grade (which ranges from 0.28 to 10.15 feet).

Height Measurement Implication:

If the building height is measured from the lowest point of the foundation (which may be below the finished grade), the total height above existing grade could exceed the notation of "35'".

Example Calculation:

Height Limit Exceedance:

If the CZO §604 maximum height is 45 feet measured from existing grade, the building may comply. However, if the maximum height is measured from finished grade or from the lowest foundation point, the building may exceed the limit.

Without architectural elevations, this cannot be determined.

9.5 AICUZ Height Restrictions

Additional Height Limitation:

The property is in the 75 dB AICUZ zone near NAS Oceana. Virginia Beach Zoning Ordinance Art. 18, §§ 1803-1804 (Virginia Beach Zoning Ordinance Article 18) may impose additional height restrictions in the AICUZ zone to protect military operations.

The site plan does not address AICUZ height restrictions or demonstrate compliance with any additional limitations.

9.6 Recommended Actions

City Development Services Center:

- Finished grade elevation at each building location

- Foundation depth and lowest foundation point

- Each story height

- Roof pitch and ridge height

- Total height measurement

- Comparison to CZO §604 maximum height

- Comparison to any AICUZ height restrictions

Planning Commission:

City Council:

GROUND 10: PATTERN OF DEVELOPER MISREPRESENTATIONS

225 Documented Discrepancies Between Developer Responses and City Review Letters

Analysis of the FOIA documents reveals a systematic pattern of misrepresentations by the developer, with 225 documented discrepancies between developer claims and city review findings. This pattern suggests either gross negligence or intentional deception.

10.1 Noise Zone Misrepresentation

Developer's Claim:

Site plan states: "THIS SITE LIES WITHIN AIRCRAFT ACCIDENT POTENTIAL ZONE N/A AND /OR THE CLEAR ZONE AND /OR NOISE ZONE(S) <75 dB LDN"

Actual Fact:

Virginia Beach GIS AICUZ MapServer Layer 3 (Virginia Beach GIS AICUZ MapServer Layer 3) confirms ZONE_ = "75" (75 dB DNL)

Discrepancy:

The developer claims the noise zone is "<75 dB LDN" (less than 75 dB), when the official GIS confirms the zone is "75" (75 dB DNL). This is a material misrepresentation that obscures the incompatibility of residential development in this zone.

Impact:

The difference between "<75 dB" and "75 dB" determines whether residential use has conditional pathways or is completely incompatible. The misrepresentation has the effect of obscuring the incompatibility of the proposed residential development from regulators.

10.2 Endangered Species Misrepresentation

Developer's Claim:

USFWS IPaC response states: "Bats are unlikely to be affected by this project due to the dense urban setting and lack of suitable habitat."

Actual Fact:

Virginia DWR NLEB and TCB Year-Round Zone 1 Map (Virginia DWR NLEB and TCB Year-Round Zone 1 Map) explicitly includes 1001 Virginia Avenue in the NLEB and TCB Year-Round Zone 1.

Discrepancy:

The developer claims bats are "unlikely" and that there is "lack of suitable habitat," when Virginia DWR officially designates the site as NLEB and TCB Year-Round Zone 1. The site contains 15+ mature trees (up to 42 inches diameter) that provide suitable roosting habitat.

Impact:

This misrepresentation prevented USFWS from requiring ESA Section 7 consultation and Incidental Take Permit authorization.

10.3 Osprey Nesting Misrepresentation

Developer's Claim:

Environmental assessment states: "Osprey are unlikely to be affected by this project."

Actual Fact:

eBird Hotspot L7146936 — Marshview Park, Virginia Beach (eBird Hotspot L7146936 — Marshview Park) documents active osprey nesting in adjacent Marshview Park. The site contains standing water and wetland features that provide osprey nesting habitat.

Discrepancy:

The developer claims osprey are "unlikely to be affected," when osprey are documented nesting in the adjacent park and the site provides suitable nesting habitat.

Impact:

This misrepresentation prevented USFWS from requiring MBTA compliance measures and nesting season construction restrictions.

10.4 Parcel Creation Misrepresentation

Developer's Claim:

Site plan narrative states: "The existing parcel was recorded via deed book 977 page 180. The parcel is 1.601 acres in total. No new parcels are proposed with this development."

Actual Fact:

City review notes state: "The parcel was created improperly by deed at a time when a plat was required to be put to record. Subdivision plat must be approved and recorded before site plan release."

Discrepancy:

The developer claims the parcel is properly recorded, when the city has repeatedly noted that the parcel was created improperly and requires a subdivision plat.

Impact:

This misrepresentation allowed the developer to proceed with site plan review without first resolving the foundational title defect.

10.5 Stormwater Infiltration Misrepresentation

Developer's Claim:

Stormwater analysis states: "Stormwater management is provided for the site via underground stormwater chambers."

Actual Fact:

Infiltration testing shows zero infiltration capacity in Chapanoke soil. The geotechnical report states: "The water in the casing did not infiltrate at all at the test locations."

Discrepancy:

The developer claims stormwater management will be provided by infiltration chambers, when infiltration testing demonstrates that the soil has zero infiltration capacity and the chambers cannot function.

Impact:

This misrepresentation resulted in approval of a stormwater design that will not function as intended and will discharge untreated stormwater to Rudee Inlet.

10.6 Groundwater Separation Misrepresentation

Developer's Claim:

Stormwater analysis states: "The proposed underground chambers will be designed with adequate separation from seasonal high groundwater."

Actual Fact:

Geotechnical report shows seasonal high groundwater at 4.0 feet NAVD 88. Proposed chamber invert elevations are 5.58 feet (BMP-1) and 5.38 feet (BMP-2), providing only 1.38-1.58 feet of separation (less than the required 2 feet).

Discrepancy:

The developer claims "adequate separation," when the actual separation is less than the PWDSM requirement.

Impact:

This misrepresentation resulted in approval of a stormwater design that violates PWDSM standards.

10.7 Ditch Depth Misrepresentation

Developer's Claim:

Stormwater analysis states: "The rear ditch will be regraded to comply with PWDSM standards requiring ditches deeper than 18 inches to be piped."

Actual Fact:

City review notes state: "The rear ditch remains 24 inches deep and does not comply with PWDSM standards. No cross-sections showing regrading are provided."

Discrepancy:

The developer claims the ditch will be regraded, but provides no evidence that regrading will occur or how it will be accomplished.

Impact:

This misrepresentation resulted in approval of a ditch design that violates PWDSM standards.

10.8 Virginia Avenue Storm Sewer Misrepresentation

Developer's Claim:

Stormwater analysis states: "The Virginia Avenue storm sewer redirect will be designed to accommodate the proposed flows without adverse impacts to the existing system."

Actual Fact:

City review notes state: "The Virginia Avenue storm sewer redirect has not been modeled. The developer has not demonstrated that the existing system can accommodate the additional flows."

Discrepancy:

The developer claims the redirect will not cause adverse impacts, but provides no modeling to support this claim.

Impact:

This misrepresentation resulted in approval of a stormwater design without verification that the existing infrastructure can accommodate the additional flows.

10.9 Building Height Misrepresentation

Developer's Claim:

Site plan notation states: "MAX. BUILDING HEIGHT = 35' (TYP TO ALL)"

Actual Fact:

City review notes state: "Building elevations have not been provided in compliance with CZO Sec. 604 height regulations. Height compliance cannot be verified."

Discrepancy:

The developer provides only a single height notation without architectural elevations, making it impossible to verify compliance with height regulations.

Impact:

This misrepresentation allowed the developer to proceed with site plan review without demonstrating height compliance.

10.10 Army Corps Permit Misrepresentation

Developer's Claim:

Site plan states: "A JOINT PERMIT APPLICATION IS NOT REQUIRED."

Actual Fact:

USACE Form 6285 (Certification of Compliance) is completely blank. There is no evidence of any USACE permit authorization or application.

Discrepancy:

The developer claims no permit is required, when the site contains standing water and ditches that may constitute jurisdictional waters requiring a CWA Section 404 permit.

Impact:

This misrepresentation allowed the developer to proceed without obtaining required federal permits.

10.11 Pattern Analysis

Systematic Nature:

The 225 documented discrepancies are not isolated errors but represent a systematic pattern of misrepresentation across all regulatory domains:

Intentional vs. Negligent:

The pattern suggests either:

1. Intentional deception: The developer deliberately misrepresented facts to avoid regulatory requirements

2. Gross negligence: The developer failed to conduct adequate due diligence and made false claims without verification

Either scenario is grounds for denial of site plan approval and potential referral for enforcement action.

10.12 Recommended Actions

City Development Services Center:

City Council:

Virginia Attorney General (State):

GROUND 11: COMPREHENSIVE LIST OF MISSING PERMITS AND APPROVALS

980 Process Gaps Identified; 37 Major Permits and Approvals Not Obtained

Analysis of 37 document comparisons reveals 980 process gaps, indicating that the developer has failed to obtain numerous required federal, state, and local permits and approvals. The project cannot legally proceed without these authorizations.

11.1 Federal Permits and Approvals

1. Army Corps of Engineers Section 404 Permit

2. Army Corps Jurisdictional Determination

3. USFWS ESA Section 7 Consultation

4. USFWS Incidental Take Permit

5. USFWS Migratory Bird Consultation

6. USFWS Bald Eagle Consultation

11.2 State Permits and Approvals

7. Virginia Water Protection Permit

8. Virginia Wetlands Act Permit (VMRC)

9. Virginia Erosion and Sediment Control Plan Approval

10. Virginia Stormwater Management Program Compliance

11. Virginia DWR Incidental Take Authorization

12. Virginia DWR Endangered Species Consultation

11.3 Local Permits and Approvals

13. Subdivision Plat Approval and Recording

14. Floodplain Development Permit

15. Height Compliance Verification

16. AICUZ Overlay District Compliance

17. Noise Attenuation Compliance

18. Site Plan Approval

11.4 Utility and Infrastructure Approvals

19. Water Service Approval

20. Sanitary Sewer Service Approval

21. Stormwater Outfall Approval

22. Fire Flow Certification

11.5 Environmental Approvals

23. Chesapeake Bay TMDL Compliance Certification

24. Nutrient Credit Purchase Verification

25. Impaired Waters Compliance

26. Chesapeake Bay Preservation Act Compliance

11.6 Wildlife and Environmental Assessments

27. Bat Habitat Assessment

28. Nesting Bird Survey

29. Wetlands Delineation Verification

30. NEPA Environmental Review (as part of USACE permit process)

11.7 Engineering and Design Approvals

31. Stormwater Design Certification

32. Geotechnical Report Review and Approval

33. Grading and Drainage Plan Approval

34. Erosion and Sediment Control Plan Approval

11.8 Title and Property Approvals

35. Title Insurance Commitment

36. Easement Modifications

37. Deed Condition Compliance

11.9 Summary Table: Missing Permits and Approvals

11.10 Recommended Actions

City Development Services Center:

City Council:

Federal and State Agencies:

GROUND 12: SEA LEVEL RISE, RESILIENCE, AND ADDITIONAL REGULATORY FAILURES

Development Contradicts City Resilience Policies, Threatens CRS Rating, Violates Tree Canopy Requirements, and Creates Emergency Access Hazard

The proposed development conflicts with multiple additional regulatory frameworks addressing climate resilience, natural resource protection, and public safety that are not addressed in the site plan.

12.1 Sea Level Rise and Climate Resilience

Hampton Roads Vulnerability:

Hampton Roads is the second most vulnerable region in the United States to sea level rise, after New Orleans. The region experiences both absolute sea level rise and land subsidence (the land is sinking). The Hampton Roads Planning District Commission (HRPDC) has adopted planning projections of:

A condominium building permitted today has a useful life of 50-75 years. During that lifespan, the building and its residents will face 1.5 to 3 feet of additional sea level rise on top of current flood risk.

Virginia Beach Sea Level Wise Initiative:

Virginia Beach adopted the Sea Level Wise adaptation initiative, which identifies flood-prone areas and recommends land use strategies to reduce exposure of people and property to rising waters. Approving 24 new permanent residential units in a FEMA Zone AE floodplain directly contradicts the goals of this initiative.

Virginia Coastal Resilience Master Plan:

The Virginia Coastal Resilience Master Plan (Virginia Department of Conservation and Recreation) identifies vulnerable coastal areas and establishes resilience strategies. The Owls Creek/Rudee Inlet watershed is within the plan's scope. New residential development in flood-prone areas within this watershed undermines state-level resilience planning.

Freeboard Inadequacy Over Building Lifespan:

The site plan shows 2.75 feet of freeboard above BFE for residential units. Regulatory compliance is measured against the BFE in effect at the time of construction, and FEMA periodically updates FIRMs and BFEs. However, the policy question is significant: with 1.5 feet of sea level rise projected by 2050 (NOAA Intermediate-High scenario), the effective margin of safety will be reduced to approximately 1.25 feet within 25 years — well below the level of protection that current regulations are designed to provide. The city should consider whether approving permanent residential construction designed to today's minimum standards serves the long-term safety of future residents when projected conditions will erode that margin within the building's useful life.

12.2 Community Rating System (CRS) Jeopardy

Virginia Beach CRS Achievement:

FEMA announced that Virginia Beach achieved CRS Class 7 status, earning residents a 15% discount on flood insurance premiums. Virginia Beach is one of only 26 communities in Virginia participating in the CRS program.

How CRS Credits Work:

CRS credits are earned by communities that exceed minimum NFIP requirements through higher regulatory standards, open space preservation, stormwater management, and floodplain management. Approving development that involves:

...is inconsistent with the higher floodplain management standards that earned Virginia Beach its CRS rating. A pattern of approving projects like this could jeopardize the city's CRS standing.

Impact on All Virginia Beach Policyholders:

If approval of projects like this leads to a CRS downgrade, every NFIP policyholder in Virginia Beach would see their flood insurance premiums increase. This gives every flood insurance customer in the city a direct financial stake in this decision.

12.3 Hampton Roads Hazard Mitigation Plan

FEMA-Approved, Council-Adopted Plan:

The 2022 Hampton Roads Hazard Mitigation Plan was approved by FEMA and the Virginia Department of Emergency Management and adopted by Virginia Beach City Council. The plan identifies flooding and tropical storms as primary hazards and establishes mitigation strategies emphasizing reduction of exposure of people and property to flood hazards.

Inconsistency with Plan Goals:

Approving 24 new residential units in a FEMA Zone AE floodplain, on a dead-end street with limited evacuation routes, is inconsistent with the adopted hazard mitigation plan. FEMA requires communities receiving federal hazard mitigation assistance to demonstrate consistency with their plans. Approving development that increases residential exposure in flood zones contradicts this commitment.

12.4 Tree Conservation and Canopy Requirements

Virginia State Enabling Authority:

Va. Code § 15.2-961 and Va. Code § 15.2-961.3 authorize Virginia Beach to require tree canopy coverage percentages for new development, up to 15% for residential sites zoned 10-20 units per acre (the applicable tier for this project at approximately 16 units/acre). These are enabling statutes that set the ceiling for local requirements.

Virginia Beach's Implementing Ordinance:

Virginia Beach Code, Appendix E (Tree Planting, Preservation, and Replacement) implements tree protection requirements using absolute square-footage canopy cover scaled to lot size, rather than the percentage-of-site canopy system in the state enabling statutes. Appendix E requires canopy cover ranging from 300 to 2,000 square feet depending on lot size, measured at 10 years from installation. While this results in lower effective canopy percentages than the state ceiling, it is the binding local requirement.

Site Plan Deficiency:

The demolition plan shows removal of an estimated 80-90% of existing tree canopy, including 42-inch, 24-inch, 18-inch, and 15-inch diameter trees. The site plan does not:

The extensive tree removal on a site within the NLEB Year-Round Zone raises independent ESA concerns (see Ground 2) beyond the tree ordinance compliance question.

12.5 Dead-End Street Emergency Access and Evacuation

Fire Code Requirements:

The Virginia Statewide Fire Prevention Code (Appendix D) requires that dead-end fire apparatus access roads exceeding 150 feet must have an approved turnaround area with a minimum 20-foot unobstructed width. Virginia Beach Subdivision Regulations (Appendix B, Section 4.1) require cul-de-sac turnarounds with 40-foot roadway radius and 50-foot right-of-way radius.

Evacuation Bottleneck — Confirmed Not Evaluated:

In response to resident questions, City staff confirmed that flood evacuation capacity is "not a function of Traffic Engineering or requirement of site plan review/approval for by right development" (Civic League Q&A, March 2026). This means no agency has evaluated whether residents can safely evacuate this dead-end street during a flood event.

City modeling shows the 100-year storm produces approximately 1.2 feet of flooding on Virginia Avenue at the culvert crossings. Virginia Avenue is already "less than standard width" per Traffic Engineering (who suggested parking may need to be prohibited on one side). The proposed development adds 24 households (estimated 48-72 residents) to this constrained dead-end street. During a flooding emergency, all residents must evacuate via a single route through water that may be over a foot deep. This creates a dangerous evacuation bottleneck when combined with:

Parking Impact:

Virginia Beach requires 2 parking spaces per multifamily unit. For 24 condominiums, that is 48 required on-site parking spaces plus visitor parking. On a constrained 1.51-acre site with floodplain fill, stormwater chambers, and building footprints, achieving adequate parking with proper maneuvering space and emergency vehicle access is a significant design challenge that has not been demonstrated.

12.6 Recommended Actions

City Development Services Center:

City Council:

Virginia Department of Conservation and Recreation:

GROUND 13: ADDITIONAL MUNICIPAL CODE REQUIREMENTS

Chesapeake Bay Buffer, Acoustical Standards, Landscaping, and Dredging District Impacts

Comprehensive review of the Virginia Beach Code of Ordinances reveals additional regulatory requirements applicable to this development that are not addressed in the site plan.

13.1 Chesapeake Bay Preservation Area — Limited Applicability

Virginia Beach Code, Appendix F (Chesapeake Bay Preservation Area Ordinance) establishes Resource Protection Areas (RPAs) with a 100-foot vegetated buffer for properties along the Chesapeake Bay, the Lynnhaven River, and their tributaries.

Applicability to 1001 Virginia Avenue:

The CBPA's 100-foot RPA buffer likely does not apply to this site. The property drains to Owls Creek → Rudee Inlet → Atlantic Ocean — not to the Chesapeake Bay or Lynnhaven River system. Virginia Beach's own May 2025 announcement about CBPA ordinance changes specifically addressed "property along the Chesapeake Bay, the Lynnhaven River or its tributaries." City staff confirmed in the March 2026 Q&A that "there is no required wetland buffer for this area."

What this means: While the CBPA buffer does not apply, the absence of any wetland buffer requirement is itself significant. Tidal wetlands are immediately adjacent to the western property boundary, yet there is no regulatory requirement for any setback, buffer, or transition zone between the 24-unit condominium development and those wetlands. The only protection proposed is silt fencing during construction.

The Comprehensive Plan's emphasis on "protection of environmentally sensitive lands, including tidal wetlands, floodplains, and Chesapeake Bay Preservation Areas" and "strengthening coastal resilience" remains a relevant policy consideration — even though the specific CBPA buffer does not apply to this drainage basin.

13.2 Airport Noise Attenuation — Acoustical Performance Standards

Virginia Beach Code, Appendix I (Airport Noise Attenuation and Safety Ordinance) and the Virginia Uniform Statewide Building Code (13VAC5-63-260) establish specific construction requirements for the >75 dB noise zone:

Required Sound Transmission Class (STC) Ratings:

Alternative: Buildings may be designed to limit interior noise to no greater than 45 Ldn, certified by a Registered Design Professional.

Additional Requirements:

Site Plan Deficiency: The site plan does not include noise attenuation specifications, STC ratings for walls/windows/doors, buyer disclosure plans, or avigation easement documentation. Meeting STC 49 for exterior walls and STC 38 for windows in a three-story condominium represents a significant construction cost that affects project feasibility.

13.3 Parking Lot Landscaping Requirements

Virginia Beach Code, Appendix C, Section 5A (Parking Lot and Foundation Landscaping) requires:

Impact: The 24-unit development requires 48 parking spaces (per the city's Q&A confirmation). At 30 square feet per space, the parking lot alone needs 1,440 square feet of internal landscaping — nearly 0.03 acres devoted solely to parking lot plantings on an already constrained 1.51-acre site.

13.4 Transitional Buffers Between Incompatible Uses

Virginia Beach Code, Appendix C, Section 5 requires transitional buffers between incompatible land uses. A 24-unit, three-story condominium development adjacent to existing single-family residences represents an intensity change that triggers buffer requirements. The site plan must demonstrate adequate transitional screening and buffering.

13.5 Shadowlawn Neighborhood Dredging Special Service District

Virginia Beach Code, Chapter 35.3 establishes Neighborhood Dredging Special Service Districts, and Shadowlawn is a participating district. Waterfront property owners in Shadowlawn pay a surcharge on their real estate taxes to fund dredging of Owls Creek to maintain navigability.

Impact: The proposed development adds approximately 1.6 acres of impervious surface (90% of the parcel) that will generate increased stormwater runoff carrying sediment into the Owls Creek drainage system. This increased sedimentation will accelerate the need for dredging — imposing costs on existing SSD participants who are already paying to maintain the waterway. The developer is not a participant in the SSD and bears none of these downstream costs.

13.6 Recommended Actions

City Development Services Center:

Shadowlawn SSD Participants:

REGULATORY CITATIONS TABLE

Complete Reference List with Hyperlink Markers

EVIDENCE INVENTORY FROM FOIA DOCUMENTS

Document Summary and Key Findings

Total FOIA Documents Analyzed: 49 documents

Total Regulatory Issues Identified: 605 issues

Total Cross-Document Findings: 1,449 findings

Document Categories

A. Site Plans and Engineering Drawings (12 documents)

1. Site Plan (C1) — Overall site layout, building locations, parking, landscaping

- Key Finding: 24 condominium units per project narrative

- Key Finding: Building heights not verified against CZO §604

2. Demolition & Phase I E&S Plan (C3) — Existing conditions, tree removal, erosion control

- Key Finding: Extensive tree removal marked throughout site

- Key Finding: No wildlife impact assessment

3. Grading & Drainage Plan (C7) — Proposed grades, fill elevations, drainage patterns

- Key Finding: ~7 feet of fill proposed in FEMA Zone AE

- Key Finding: Orifice elevations mismatched with SWMM model

4. Utility Plans (C8) — Water, sewer, stormwater infrastructure

- Key Finding: Water pressure insufficient for fire flow (9.05 psi vs. 20 psi required)

- Key Finding: Sanitary sewer flows estimated at two different rates (7,440 vs. 14,400 gpd)

5. Landscape Plan (C9) — Plant materials, tree preservation, screening

- Key Finding: Minimal tree preservation; most existing trees removed

6. Stormwater Management Plan (C10) — Underground chambers, detention, treatment

- Key Finding: 268 StormTech chambers proposed in zero-infiltration soil

- Key Finding: Groundwater separation less than PWDSM requirement

7. Erosion & Sediment Control Plan (C11) — Silt fence, inlet protection, sediment basins

- Key Finding: Plan references handbook but lacks site-specific measures

- Key Finding: No enhanced measures for Chapanoke soil

8. Fire Flow Analysis (C12) — Fire hydrant locations, flow calculations

- Key Finding: Only 1 existing hydrant; water pressure insufficient

- Key Finding: Fire flow requirements may not be met

9. Pavement Design (C13) — Asphalt thickness, subgrade preparation

- Key Finding: Design based on 24 units per project narrative

- Key Finding: CBR value < 7 requires 6-inch undercut

10. Topographic Survey (C14) — Existing ground elevations, features, utilities

- Key Finding: Existing grades range from 0.28 to 10.15 feet

- Key Finding: Standing water and ditches documented

11. Geotechnical Report (C15) — Soil boring, infiltration testing, groundwater

- Key Finding: Zero infiltration capacity in Chapanoke soil

- Key Finding: Seasonal high groundwater at 4.0 feet NAVD 88

12. Architectural Renderings (C16) — Building elevations, perspectives

- Key Finding: Elevations shown but not dimensioned for height compliance

- Key Finding: No ridge height or total height calculations provided

B. Stormwater Analysis Documents (8 documents)

13. Stormwater Narrative (C17) — Project description, design approach, compliance

- Key Finding: Claims infiltration will function in zero-infiltration soil

- Key Finding: Relies on nutrient credit purchase for TMDL compliance

14. VRRM Water Quality Analysis (C18) — Pollutant load calculations, BMP sizing

- Key Finding: Post-development TP load 62% higher than pre-development

- Key Finding: On-site treatment only 62% of required reduction

15. SWMM Hydraulic Model (C19) — Storm event modeling, peak flows, detention

- Key Finding: Multiple pipes surcharged during 10-year storm

- Key Finding: 1-year storm compliance margin only 1.2%

16. Energy Balance Calculations (C20) — Channel protection analysis, allowable discharge

- Key Finding: Post-development 1-year peak flow 2.48 cfs vs. allowable 2.51 cfs

- Key Finding: Minimal safety factor for design variations

17. Infiltration Test Results (C21) — Soil permeability, infiltration rates

- Key Finding: Zero infiltration at all three test locations

- Key Finding: "Water did not infiltrate at all" per geotechnical report

18. BMP Sizing Calculations (C22) — Underground chamber volume, detention capacity

- Key Finding: 268 chambers proposed; capacity calculations based on infiltration

- Key Finding: Chambers will overflow if infiltration does not occur

19. Pipe Sizing Analysis (C23) — Storm sewer pipe diameters, flow capacity

- Key Finding: Multiple 12-inch pipes undersized for design flows

- Key Finding: Surcharge analysis shows exceedance of design capacity

20. Outfall Structure Design (C24) — Outlet elevation, orifice sizing, energy dissipation

- Key Finding: Orifice elevations inconsistent between plans and model

- Key Finding: Energy dissipation calculations not provided

C. Environmental and Regulatory Documents (12 documents)

21. USFWS IPaC Response (C25) — Species list, habitat assessment, consultation determination

- Key Finding: Developer marked species assessment "Not Applicable"

- Key Finding: Developer claimed bats "unlikely" in "dense urban setting"

- Key Finding: 23 Birds of Conservation Concern identified

22. Virginia DWR Consultation (C26) — State endangered species, incidental take

- Key Finding: No state consultation initiated

- Key Finding: NLEB and TCB Year-Round Zone 1 confirmed at site

23. USACE Permit Application (C27) — Form 6285, general permit determination

- Key Finding: Form 6285 completely blank

- Key Finding: No permit number or authorization

24. Jurisdictional Determination Request (C28) — Waters of the United States, wetlands

- Key Finding: No jurisdictional determination obtained

- Key Finding: Standing water and ditches may be jurisdictional

25. Virginia Water Protection Permit Application (C29) — State 401 certification

- Key Finding: No VWP permit number

- Key Finding: No DEQ authorization letter

26. VMRC Tidal Wetlands Permit (C30) — Tidal wetlands, shellfish waters

- Key Finding: No VMRC permit number

- Key Finding: Site drains to prohibited Rudee Inlet

27. Wetlands Delineation (C31) — Wetland boundaries, plant communities, hydrology

- Key Finding: Wetlands shown on plans but jurisdictional status unknown

- Key Finding: "Limits of Wetlands per Delineation by MSA, P.C." noted

28. Endangered Species Habitat Assessment (C32) — NLEB, migratory birds, eagles

- Key Finding: No bat habitat assessment

- Key Finding: No nesting survey for osprey or eagles

- Key Finding: No buffer zone analysis

29. Noise Analysis (C33) — AICUZ zone, noise levels, attenuation measures

- Key Finding: Site plan states "<75 dB LDN" (false)

- Key Finding: VB GIS confirms "75" dB DNL zone

- Key Finding: No noise attenuation measures documented

30. Floodplain Analysis (C34) — FEMA Zone AE, BFE, freeboard, compensatory storage

- Key Finding: No compensatory storage analysis

- Key Finding: No hydraulic impact analysis or flood level increase calculation

- Key Finding: Freeboard compliance unverified

31. Chesapeake Bay TMDL Compliance (C35) — Nutrient loading, pollutant reduction, credits

- Key Finding: Development increases TP load by 62%

- Key Finding: Nutrient credit availability unverified

- Key Finding: Appendix C2 (credit letter) not provided

32. Nutrient Credit Purchase Letter (C36) — Credit availability, retirement, verification

- Key Finding: Letter referenced but not provided in FOIA documents

- Key Finding: Credit source and verification unknown

D. City Review Comments and Correspondence (10 documents)

33. 1st City Review Letter (April 11, 2025) — Initial deficiencies, required corrections

- Key Finding: Building elevations not provided

- Key Finding: Parcel creation deficiency noted

- Key Finding: Stormwater design deficiencies identified

34. 2nd City Review Letter (July 11, 2025) — Revised deficiencies, outstanding issues

- Key Finding: Building elevations still missing

- Key Finding: Stormwater infiltration capacity questioned

- Key Finding: Virginia Avenue storm sewer impacts not modeled

35. 3rd City Review Letter (October 10, 2025) — Continued deficiencies, final comments

- Key Finding: Multiple deficiencies remain unresolved

- Key Finding: Height compliance still cannot be verified

- Key Finding: Stormwater design still inadequate

36. Stormwater Review Comments (C37) — Technical deficiencies, design issues

- Key Finding: 231 documented stormwater engineering issues

- Key Finding: Zero infiltration capacity in proposed BMPs

- Key Finding: Groundwater separation inadequate

37. Floodplain Review Comments (C38) — FEMA Zone AE issues, fill requirements

- Key Finding: Compensatory storage not analyzed

- Key Finding: No-rise certification not provided

- Key Finding: Freeboard compliance unverified

38. Environmental Review Comments (C39) — Wildlife, water quality, ESA issues

- Key Finding: NLEB habitat impacts not assessed

- Key Finding: Osprey nesting not documented

- Key Finding: Eagle buffer zone not analyzed

39. Zoning Compliance Review (C40) — Height, setbacks, AICUZ, density

- Key Finding: Height compliance cannot be determined

- Key Finding: AICUZ incompatibility not addressed

- Key Finding: Deed condition setback (15 feet) vs. proposed (10 feet)

40. Utility Review Comments (C41) — Water, sewer, stormwater infrastructure

- Key Finding: Water pressure insufficient for fire flow

- Key Finding: Sanitary sewer flows inconsistent

- Key Finding: Stormwater outfall capacity unconfirmed

41. Fire Department Review (C42) — Fire flow, hydrant locations, access

- Key Finding: Only 1 hydrant available

- Key Finding: Water pressure below 20 psi requirement

- Key Finding: Fire flow requirements may not be met

42. Developer Response to Comments (C43) — Applicant's replies, proposed corrections

- Key Finding: 225 discrepancies between developer claims and city findings

- Key Finding: Developer claims issues resolved without documentation

- Key Finding: Multiple misrepresentations identified

E. Regulatory and Reference Documents (7 documents)

43. Virginia Beach Zoning Ordinance (C44) — AICUZ Overlay, height regulations, density

- Key Finding: Residential "Not Compatible" in 75 dB zone

- Key Finding: CZO §604 height limits not verified

- Key Finding: AICUZ Overlay restrictions not addressed

44. Virginia Beach Comprehensive Plan (C45) — Land use policies, environmental goals

- Key Finding: Development inconsistent with environmental stewardship goals

- Key Finding: Military compatibility not addressed

- Key Finding: Flood resilience not demonstrated

45. FEMA Flood Insurance Rate Map (C46) — Zone AE, BFE, flood boundaries

- Key Finding: Property in Zone AE (BFE 8 ft), Zone X, Zone X-Shaded

- Key Finding: Multiple flood zones on property

46. NAS Oceana AICUZ Study (C47) — Noise contours, land use compatibility

- Key Finding: 75 dB DNL zone designation confirmed

- Key Finding: Residential use incompatible in 75+ dB zone

47. Virginia DWR NLEB/TCB Year-Round Zone Map (C48) — Bat habitat, Year-Round Zone 1

- Key Finding: 1001 Virginia Avenue in NLEB and TCB Year-Round Zone 1

- Key Finding: Contradicts developer's "unlikely" claim

48. eBird Marshview Park Species List (C49) — Osprey, eagles, migratory birds

- Key Finding: Active osprey nesting documented in adjacent park

- Key Finding: 23 Birds of Conservation Concern identified

49. Virginia Beach GIS AICUZ Layer (C50) — Official noise zone designation

- Key Finding: ZONE_ = "75" (75 dB DNL)

- Key Finding: Contradicts site plan claim of "<75 dB LDN"

RECOMMENDED ACTIONS BY AGENCY

Federal Agencies

U.S. Fish and Wildlife Service (USFWS)

Immediate Actions:

1. Issue ESA Section 7 Consultation Determination

- Determine that the project "may affect" Northern Long-Eared Bat (Endangered)

- Determine that the project "may affect" 23 Birds of Conservation Concern

- Determine that the project "may affect" Bald Eagle (within 660-foot buffer)

- Require Army Corps to initiate ESA Section 7 consultation before issuing Section 404 permit

2. Require Incidental Take Permit Application

- Deny any general permit authorization

- Require developer to submit Incidental Take Permit application with Habitat Conservation Plan

- Require bat habitat assessment by qualified biologist

- Require acoustic survey for NLEB presence

- Require nesting survey for osprey and eagles

3. Require Migratory Bird Compliance

- Require nesting survey by qualified ornithologist

- Require identification of active nests and buffer zones

- Require seasonal construction restrictions (no work April 1 - September 15 within 660 feet of active nests)

- Require monitoring plan for eagle nest during construction

4. Require Bald Eagle Consultation

- Require buffer zone analysis for Stumpy and Victoria eagle nest

- Require distance calculation from development to nest

- Require mitigation measures if within 660-foot buffer

- Require coordination with Navy on eagle protection

U.S. Army Corps of Engineers (USACE)

Immediate Actions:

1. Require Jurisdictional Determination

- Issue jurisdictional determination for standing water and ditches on site

- Determine whether features are "waters of the United States"

- Require developer to obtain determination before proceeding with fill

2. Deny General Permit Authorization

- Exercise discretionary authority under 33 CFR 330.1(d) to require an individual permit, based on more than minimal individual and cumulative adverse environmental effects (impaired receiving waters, NLEB habitat, wetlands adjacency, zero-infiltration stormwater design)

- Determine that project requires individual permit

3. Require Individual Permit Application

- Require detailed project description

- Require environmental assessment

- Require coordination with USFWS on ESA Section 7 consultation

- Require coordination with state on Section 401 certification

- Require public notice and comment period

4. Require ESA Section 7 Consultation

- Coordinate with USFWS on endangered species impacts

- Require Biological Assessment

- Require Incidental Take Permit before permit issuance

Federal Emergency Management Agency (FEMA)

Immediate Actions:

1. Review Floodplain Development Permit Application

- Require compensatory storage calculations

- Require no-rise certification

- Require freeboard compliance verification

- Deny permit if requirements not met

2. Coordinate with City on NFIP Compliance

- Ensure that city enforces NFIP standards

- Ensure that fill placement does not increase flood levels

- Ensure that compensatory storage is adequate

National Oceanic and Atmospheric Administration (NOAA)

Immediate Actions:

1. Coordinate on Coastal Zone Management

- Ensure that development complies with Virginia Coastal Zone Management Program

- Ensure that water quality impacts are minimized

- Ensure that impacts to Rudee Inlet are addressed

State Agencies

Virginia Department of Environmental Quality (DEQ)

Immediate Actions:

1. Require Virginia Water Protection Permit

- Require developer to obtain VWP permit for fill in jurisdictional waters

- Require coordination with USACE on Section 404 permit

- Require water quality certification

2. Review Stormwater Management Compliance

- Require developer to demonstrate Virginia Stormwater Management Act compliance

- Require redesign of stormwater system to account for zero infiltration capacity

- Require TMDL compliance demonstration

- Require verification of nutrient credit availability

3. Require Erosion and Sediment Control Plan Approval

- Require site-specific ESC measures for Chapanoke soil

- Require enhanced sediment trapping for 1.54-acre disturbed area

- Require approval before land disturbance begins

Virginia Department of Wildlife Resources (DWR)

Immediate Actions:

1. Require Incidental Take Authorization

- Require developer to obtain state incidental take authorization under 4VAC15-35

- Require nesting survey and buffer zone analysis

- Require seasonal construction restrictions

2. Enforce Endangered Species Protection

- Enforce state endangered species protection for NLEB under 4VAC15-20-130

- Require developer to avoid, minimize, and compensate for impacts

- Require Habitat Conservation Plan

3. Coordinate on Wildlife Impacts

- Coordinate with USFWS on federal endangered species

- Coordinate with Navy on eagle protection

- Coordinate with city on local wildlife protection

Virginia Marine Resources Commission (VMRC)

Immediate Actions:

1. Require Tidal Wetlands Permit

- Require developer to obtain VMRC permit for activities in tidal wetlands

- Require coordination with DEQ on water quality

- Require mitigation for impacts to tidal wetlands

2. Coordinate on Rudee Inlet Water Quality

- Coordinate with DEQ on water quality impacts to prohibited shellfish waters

- Ensure that development does not further impair Rudee Inlet

- Require enhanced water quality treatment

Virginia Department of Health (VDH)

Immediate Actions:

1. Coordinate on Shellfish Water Quality

- Coordinate with VMRC on Rudee Inlet condemnation

- Ensure that development does not increase contamination

- Require water quality monitoring

Local Agencies

City of Virginia Beach — Development Services Center

Immediate Actions:

1. Require Subdivision Plat Approval and Recording

- Require developer to obtain subdivision plat approval

- Require plat to be recorded in land records

- Do not issue site plan approval until plat is recorded

2. Require Building Elevations and Height Compliance Verification

- Require detailed architectural elevations showing height compliance

- Require height calculations from lowest foundation point to highest roof point

- Require comparison to CZO §604 maximum height

- Require licensed architect certification

3. Require Floodplain Development Permit

- Require compensatory storage calculations

- Require no-rise certification

- Require freeboard compliance verification

- Require FEMA coordination

4. Require Stormwater Design Corrections

- Require redesign to account for zero infiltration capacity

- Require piping of rear ditch to comply with PWDSM standards

- Require modeling of Virginia Avenue storm sewer impacts

- Require correction of orifice elevation discrepancies

- Require upsizing of pipes to eliminate surcharge

5. Require Environmental Permits and Approvals

- Require evidence of USACE Section 404 permit

- Require evidence of Virginia Water Protection Permit

- Require evidence of VMRC tidal wetlands permit

- Require evidence of USFWS ESA Section 7 consultation completion

- Require evidence of USFWS Incidental Take Permit (if applicable)

6. Require Noise Attenuation Compliance

- Correct site plan noise zone designation from "<75 dB LDN" to "75 dB DNL"

- Require developer to acknowledge incompatibility of residential use in 75 dB zone

- Require noise attenuation measures and buyer disclosure

- Require AICUZ Overlay District compliance

7. Require Correction of Misrepresentations

- Require developer to correct all documented misrepresentations

- Require detailed explanations for discrepancies

- Consider whether the pattern of misrepresentations warrants referral to the City Attorney for review

8. Maintain Permit Checklist

- Do not issue site plan approval until all federal and state permits are obtained

- Require developer to provide evidence of each permit/approval before proceeding

City of Virginia Beach — Planning Commission

Immediate Actions:

1. Recommend Denial of Site Plan

- Recommend denial based on AICUZ incompatibility

- Recommend denial based on regulatory violations

- Recommend denial based on missing permits and approvals

2. Recommend Enforcement of AICUZ Overlay District

- Recommend that city enforce AICUZ Overlay District restrictions

- Recommend that city follow Virginia BRAC Act requirement to apply Navy AICUZ guidelines

3. Recommend Comprehensive Plan Consistency Review

- Recommend review of consistency with Comprehensive Plan goals

- Recommend denial if inconsistent with environmental stewardship, military compatibility, or flood resilience goals

City of Virginia Beach — City Council

Immediate Actions:

1. Apply Virginia BRAC Act Requirement

- Acknowledge that property is in 75 dB DNL AICUZ zone

- Apply Virginia BRAC Act requirement to follow Navy AICUZ guidelines

- Deny floodplain development permit on grounds of AICUZ incompatibility

2. Deny Site Plan Approval

- Deny site plan approval pending resolution of all regulatory violations

- Deny site plan approval pending resolution of all missing permits and approvals

- Deny site plan approval pending resolution of all documented misrepresentations

3. Consider Enforcement Action

- Consider whether pattern of misrepresentations demonstrates bad faith

- Consider whether the pattern of misrepresentations warrants referral to the City Attorney for review

- Consider whether developer is capable of complying with conditions of approval

City of Virginia Beach — Department of Public Works

Immediate Actions:

1. Review Stormwater Outfall

- Review Virginia Avenue storm sewer redirect

- Verify that existing system has capacity for additional flows

- Require modeling of impacts to existing system

2. Review Utility Infrastructure

- Review water service adequacy (pressure, flow)

- Review sanitary sewer service adequacy (capacity, treatment)

- Require corrections if infrastructure inadequate

City of Virginia Beach — Fire Department

Immediate Actions:

1. Verify Fire Flow Requirements

- Verify that adequate fire flow is available

- Verify that water pressure meets 20 psi minimum

- Verify that hydrant locations are adequate

- Require corrections if fire protection inadequate

City of Virginia Beach — Environmental Services

Immediate Actions:

1. Review Environmental Compliance

- Review wildlife impacts (NLEB, osprey, eagles, migratory birds)

- Review water quality impacts (TMDL, impaired waters, nutrient loading)

- Review wetlands impacts (jurisdictional determination, permits)

- Require corrections if environmental compliance inadequate

Military

Naval Air Station Oceana

Immediate Actions:

1. Provide AICUZ Compatibility Statement

- Provide formal statement that residential development in 75 dB zone is incompatible with military operations

- Request that city enforce AICUZ guidelines to protect military readiness

- Coordinate with city on floodplain development permit review

2. Coordinate on Eagle Protection

- Coordinate with USFWS on eagle nest protection

- Provide information on Stumpy and Victoria nest location and buffer zone

- Coordinate with developer on mitigation measures

3. Coordinate on Watchable Wildlife Area

- Coordinate with Virginia DWR on Navy Watchable Wildlife Area protection

- Ensure that development does not adversely impact protected wildlife habitat

CITY STAFF DISCLAIMERS: WHO IS RESPONSIBLE?

In a March 2026 Q&A session with Shadowlawn residents, City Planning and Public Works staff provided answers that reveal significant gaps in the regulatory review process. The following direct quotes illustrate the extent to which the City disclaimed responsibility for key aspects of public safety, environmental protection, and infrastructure impact.

Flooding Liability

Resident question: "If project goes through and we have major flooding and that flooding does damage to the road or neighboring properties who pays for the damage? Who is held responsible?"

City answer: *"There could be a fact pattern in which a property owner may have a cause of action against their neighbor, but that would be a private legal matter that our City Attorney's Office cannot opine on. As to the question of potential damage to a public road, the city would retain responsibility for maintaining that public infrastructure."*

Translation: If this development causes your property to flood, the City says that is your private problem to litigate.

Evacuation Safety

Resident question: "Has the City evaluated evacuation capacity during flood conditions?"

City answer: *"Not a function of Traffic Engineering or requirement of site plan review/approval for by right development."*

Translation: No one has evaluated whether residents can safely evacuate this dead-end street during a flood event. No one is required to. The City's 100-year flood modeling shows 1.2 feet of water on Virginia Avenue at the culvert crossings.

Traffic Impact

Resident question: "Why was there no traffic impact study required?"

City answer: *"There would be no point in conducting a traffic study for this local residential street that does not serve as a through street."*

Translation: Despite Virginia Avenue's dead-end configuration, substandard width, park access at the terminus, and 70+ existing condominiums, the City considers a traffic study pointless.

Wetland Protection

Resident question: "If no regulatory wetland buffer is required, is the City considering any voluntary buffer or enhanced protections beyond silt fencing?"

City answer: *"The City cannot require any voluntary buffering beyond the required standards."*

Translation: Tidal wetlands are immediately adjacent to the property. The Comprehensive Plan emphasizes protecting tidal wetlands, preserving natural flood storage, and strengthening coastal resilience. The City's answer is that it cannot act on its own adopted goals.

Tree Removal

Resident question: "Are there requirements for tree preservation, replacement, or canopy offset?"

City answer: *"There are no requirements for the replacement of existing trees in this location."*

Translation: More than 50 mature trees will be removed from a confirmed NLEB Year-Round Zone. The City requires no replacement, no canopy offset, and no wildlife assessment.

Environmental Impacts

Resident question: "How are the storm water and environmental impacts of removing 50+ mature trees incorporated into the analysis?"

City answer: *"The change in land cover is accounted for in the stormwater modeling and in the water quality calculations. The increase in runoff generated from the change in land cover is mitigated through the designed stormwater management facility."*

Translation: The "designed stormwater management facility" is the underground chamber system that the developer's own geotechnical testing showed has zero infiltration capacity (see Ground 8). The City defers to the design without addressing the fundamental engineering contradiction.

The Pattern

These responses reveal a consistent pattern: the City treats this development as a by-right ministerial approval where its role is limited to checking code compliance. Questions about public safety, environmental protection, quality of life, and long-term resilience are deflected as either "private matters," "not a requirement of site plan review," or outside the scope of what the City "can require."

The question for City Council is whether this framework adequately protects residents when the code requirements themselves have gaps — when there is no required wetland buffer, no required tree replacement, no required evacuation analysis, no required traffic study, and no required independent assessment of whether 24 new units on a dead-end street in a flood zone is safe.

LEGAL DISCLAIMER

Scope and Limitations

This community review is prepared to facilitate informed citizen participation in the regulatory process and represents the analysis of publicly available documents obtained through Freedom of Information Act requests. The document is not a legal opinion and should not be relied upon as such.

Property Rights Acknowledgment

The developer has a right to develop the property in accordance with applicable regulations. Condominiums are a permitted use by right in the A-18 zoning district, and site plan approval in Virginia is a ministerial process governed by compliance with adopted code requirements (*Board of Supervisors of Fairfax County v. Horne*, 216 Va. 113, 1975). This review does not challenge the developer's right to develop; it identifies specific, objective regulatory requirements that the current site plan submissions have not met and environmental compliance obligations that remain outstanding.

Accuracy and Verification

While every effort has been made to ensure accuracy, the analysis is based on documents provided by the City of Virginia Beach and may not include all relevant information. Regulatory agencies and the developer may have additional information not reflected in these documents.

Regulatory Authority

The recommendations in this document are based on applicable federal, state, and local regulations. However, regulatory agencies have discretion in interpreting and enforcing these regulations. The recommendations do not guarantee any particular outcome.

Citizen Participation

This document is prepared to facilitate informed citizen participation in the regulatory process. Citizens have the right to submit comments and concerns to regulatory agencies and to participate in public hearings (if applicable).

Potential Legal Actions

The regulatory violations documented in this community review may provide grounds for:

However, any legal action would require consultation with an attorney and would be subject to applicable statutes of limitations and procedural requirements.

Non-Binding Nature

This community review does not bind any regulatory agency or decision-maker. Regulatory agencies will make their own determinations based on applicable law and their interpretation of the facts.

Disclaimer of Liability

The authors of this community review make no representations regarding the accuracy, completeness, or reliability of the information contained herein. The document is provided "as is" without warranty of any kind. The authors assume no liability for any errors, omissions, or inaccuracies.

CONCLUSION

The proposed "Solara at Shadowlawn" condominium development at 1001 Virginia Avenue presents systematic regulatory violations across all major domains: endangered species protection, migratory bird protection, floodplain management, water quality, stormwater management, noise compatibility, and zoning compliance.

The analysis of 49 FOIA documents reveals hundreds of regulatory deficiencies and cross-document inconsistencies, including:

Recommendation: Deny site plan approval pending resolution of all regulatory violations, permit deficiencies, and title issues. Require developer to obtain all federal, state, and local permits and approvals before site plan can be approved.

*This document is based on analysis of publicly available records obtained through Freedom of Information Act requests and is intended to facilitate informed public participation in the regulatory process.*