Georgia Airport / Military Installation Federal Overlay Conflict Check (GA)

Tracked preemption from the Georgia overlay bundle.

Overview

Effective
1958-01-01
Sunset
Authority
state
Scope
state:GA

Trigger predicate

When this evaluates true for a parcel, the law's preempted fields take precedence over base zoning.

OR
  • city.airport_influence_zones attribute is present
  • city.military_installation_influence attribute is present

Preempted fields

2 fields on the base district schema are rewritten when the trigger fires.

FieldOpValueNote
base_districts[*].max_height_ftcap_atfederal_part_77_or_aicuz_surfaceHartsfield-Jackson Atlanta (ATL) Part 77 surfaces; Fort Benning/Moore, Fort Stewart, Robins AFB AICUZ height/use restrictions
base_districts[*].allowed_usesremovenoise_sensitive_uses_in_aicuz_high_noise_zones

Citation

Authority source
FAA Part 77 (14 CFR Part 77); DoD AICUZ program (DoDI 4165.57)
§ FAA Part 77; AICUZ for Fort Moore (Benning), Fort Stewart, Robins AFB, plus Part 77 for ATL
https://www.ecfr.gov/current/title-14/chapter-I/subchapter-E/part-77

Research notes

Federal-overlay conflict check is enabled because GA hosts multiple federal airspace overlays: Hartsfield-Jackson Atlanta International (ATL) Part 77; Fort Moore (formerly Fort Benning) AICUZ near Columbus; Fort Stewart AICUZ near Hinesville/Savannah; Robins AFB AICUZ near Warner Robins. Any state-overlay preemption that would raise allowed height or introduce noise-sensitive uses in these zones must be flagged for federal conflict resolution. State-level overlay set has no direct height-floor preemptions today, but this overlay exists to ensure the evaluator surfaces conflicts when city-level overlays touch base_districts[*].max_height_ft or allowed_uses.