Arlington Municipal Airport Development Plan Arlington Airport Development Plan | Page 166
Another option to meeting RPZ standards on Runway 34 would be to modify the existing runway envi‐
ronment so as to move the approach RPZ off the incompatible land uses. This can be done in two
ways. The first would be to simply reduce the runway length. This option would then shift the RPZ in
relation to the amount of runway reduced. As previously noted, the Airport and its users would like to
achieve greater runway length, not less. Reducing the runway pavement would impact both landings
in one direction and takeoffs in the other. As a result, this option is not preferred and should be avoid‐
ed if possible. A second option is to allow the runway pavement to remain intact but instead limit op‐
erational runway length through the displacement of the landing threshold. The following alternatives
further detail these options.
Runway 34 Approach RPZ – Alternative 1
Alternative 1 on Exhibit 4D shifts the Runway 34 approach RPZ to the north in order to be fully situated
on airport property and clear of Southeast Green Oaks Boulevard. Since the RPZ begins 200 feet prior
to the landing threshold, this alternative would require displacing the Runway 34 threshold by 1,936
feet. In doing so, only 4,144 feet of runway length would be available for aircraft landing on Runway
34.
Other significant airfield impacts associated with Alternative 1 would include the relocation of the
MALSR. Approximately 1,800 feet of the MALSR would need to be located in the pavement, so as not
to be an obstruction to aircraft movements. The remaining portion of the approach lighting system
can be constructed aboveground.
The glide slope antenna associated with the ILS approach to Runway 34 would also have to be relocat‐
ed to account for the displaced threshold. According to the FAA, glide slope antennas can be sited be‐
tween 750 feet and 1,250 feet from a runway threshold. As such, the relocation of the glide slope an‐
tenna and its associated critical area would make the southern portion of partial parallel Taxiway G
unusable for aircraft movements. While Alternative 1 would shift the approach RPZ onto airport prop‐
erty, it would also introduce new incompatibilities on the east side of the Airport to include two air‐
craft storage hangars and a portion of the south aircraft parking apron.
Runway 34 Approach RPZ – Alternative 2
Exhibit 4D also presents Alternative 2 in dealing with the Runway 34 approach RPZ. The goal of this
alternative would be to relocate the RPZ off the residential land uses. As depicted, the RPZ would need
to be shifted a minimum of 200 feet north so as to remain clear of the residences farther south. In do‐
ing so, the Runway 34 threshold would be displaced 200 feet, providing for a landing distance of 5,880
feet on Runway 34.
The southeast portion of the approach RPZ would encompass approximately 0.89 acres of uncontrolled
property, to include a portion of South Collins Street. At a minimum, the Airport sponsor would need
Chapter Four - 20