Arlington Municipal Airport Development Plan Arlington Airport Development Plan | Page 170
Alternative 2 helps to decrease incompatibilities within the approach RPZ by removing it from the resi‐
dential land uses to the south. This would require a 200‐foot displacement on Runway 34 and decreas‐
ing the landing length to less than 6,000 feet. The major airfield improvement needed to accommo‐
date this alternative involves modifying the MALSR, which would include installing a new in‐pavement
light‐lane at the existing end of runway pavement. It should be noted that since this alternative calls
for a change to the runway environment (i.e., displaced threshold as a result of the relocated approach
RPZ), the Airport would need to coordinate this modification with the FAA’s proper lines of business
(including APP‐400) to get an official approval on the relocation of the RPZ as proposed.
Alternative 3 aims to satisfy the FAA‐recommended approach of securing positive control of the RPZ
through fee simple acquisition of the property currently encompassing residential land uses. As a re‐
sult, the homes can be removed and/or relocated from within the RPZ. A portion of South Collins
Street would still remain in the outer portion of the RPZ, but the FAA may allow this roadway since it is
considered an existing condition. The same would apply to Southeast Green Oaks Boulevard farther
north.
Implementation of any of the alternatives would result in similar environmental impacts associated
with potential land acquisition and the relocation of navigational approach aids on and adjacent to the
Airport.
RUNWAY 16‐34 EXTENSION ANALYSIS
As previously discussed, the 2008 Master Plan and 2009 ALD propose a 700‐foot extension on Runway
16‐34. Runway extensions greater than 700 feet were also analyzed; however, given the existing con‐
straints to the north and south of the Airport, namely U.S. Interstate 20 and Southeast Green Oaks
Boulevard, and the investment necessary to construct such an extension, this study considers it not
practicable to do so. Furthermore, updated FAA design standards will make it difficult for the Airport
to justify any runway extension scenario, not to mention one in excess of what is depicted on the exist‐
ing ALD. As a result, no runway extension options beyond the existing ALD approved 700‐foot exten‐
sion will be evaluated.
The exhibits to follow analyze two separate alternatives dealing with the 700‐foot extension. The first
alternative depicts the extension as called for in the previous Master Plan and on the existing ALD. The
second alternative applies updated FAA guidance to properly meet safety design standards associated
with the proposed extension. Both alternatives include options for improving taxiway geometry.
Runway 16‐34 Extension – Alternative 1
Alternative 1, depicted on Exhibit 4E, considers the 700‐foot northerly extension on Runway 16‐34,
achieving an overall usable pavement length of 6,780 feet. The proposed RSA and ROFA would extend
beyond the north property boundary, necessitating the need to acquire land. As proposed, approxi‐
Chapter Four - 24