Modification, Revocation, and Establishment of Area Navigation (RNAV) Routes; Charlotte, NC, 15677-15679 [2014-05894]
Download as PDF
<![CDATA[
Federal Register / Vol. 79, No. 55 / Friday, March 21, 2014 / Rules and Regulations
points listed in the route description.
This action is simply to comply with the
standard format for describing routes.
The existing alignment of the airway is
not affected by this action.
DATES: Effective Dates: 0901 UTC, May
29, 2014. The Director of the Federal
Register approves this incorporation by
reference action under 1 CFR part 51,
subject to the annual revision of FAA
Order 7400.9 and publication of
conforming amendments.
FOR FURTHER INFORMATION CONTACT:
Colby Abbott, Airspace Policy and
Regulations Group, Office of Airspace
Services, Federal Aviation
Administration, 800 Independence
Avenue SW., Washington, DC 20591;
telephone: (202) 267–8783.
SUPPLEMENTARY INFORMATION:
Background
Current format guidelines for airway
and route legal descriptions require that
the order of points in a description be
listed from ‘‘west-to-east’’ or from
‘‘south-to-north,’’ as applicable. The
description for V–626 lists the points
from ‘‘east-to-west.’’ This rule simply
reverses the order of the points to a
‘‘west-to-east’’ format for
standardization.
mstockstill on DSK4VPTVN1PROD with RULES
The Rule
This action amends Title 14 Code of
Federal Regulations (14 CFR) part 71 by
reversing the order of points listed in
the legal description of VOR Federal
airway V–626. This is only an editorial
change to comply with the standard
route description format. The change
does not alter the current alignment of
V–626 and the airway track is correct on
aeronautical charts.
Since this action merely involves an
editorial change in the legal description
of VOR Federal airway V–626 to
standardize the format, and does not
involve a change in the dimensions or
operating requirements of the affected
route, I find that notice and public
procedures under 5 U.S.C. 553(b) are
unnecessary.
The FAA has determined that this
regulation only involves an established
body of technical regulations for which
frequent and routine amendments are
necessary to keep them operationally
current. Therefore, this regulation: (1) Is
not a ‘‘significant regulatory action’’
under Executive Order 12866; (2) is not
a ‘‘significant rule’’ under DOT
Regulatory Policies and Procedures (44
FR 11034; February 26, 1979); and (3)
does not warrant preparation of a
Regulatory Evaluation as the anticipated
impact is so minimal. Since this is a
routine matter that only affects air traffic
VerDate Mar<15>2010
15:59 Mar 20, 2014
Jkt 232001
procedures and air navigation, it is
certified that this rule, when
promulgated, does not have a significant
economic impact on a substantial
number of small entities under the
criteria of the Regulatory Flexibility Act.
The FAA’s authority to issue rules
regarding aviation safety is found in
Title 49 of the United States Code.
Subtitle I, Section 106 describes the
authority of the FAA Administrator.
Subtitle VII, Aviation Programs,
describes in more detail the scope of the
agency’s authority.
This rulemaking is promulgated
under the authority described in
Subtitle VII, Part A, Subpart I, Section
40103. Under that section, the FAA is
charged with prescribing regulations to
assign the use of the airspace necessary
to ensure the safety of aircraft and the
efficient use of airspace. This regulation
is within the scope of that authority as
it is merely an editorial change of the
legal description of V–626 to comply
with existing administrative format
procedures.
Domestic VOR Federal Airways are
published in paragraph 6010(a) of FAA
Order 7400.9X, dated August 7, 2013,
and effective September 15, 2013, which
is incorporated by reference in 14 CFR
71.1. The VOR Federal airway listed in
this document will be published
subsequently in the Order.
Environmental Review
The FAA has determined that this
action qualifies for categorical exclusion
under the National Environmental
Policy Act in accordance with FAA
Order 1050.1E, Environmental Impacts:
Policies and Procedures, paragraph
311a. This airspace action consists of
editorial changes only and is not
expected to cause any potentially
significant environmental impacts, and
no extraordinary circumstances exist
that warrant preparation of an
environmental assessment.
§ 71.1
15677
[Amended]
2. The incorporation by reference in
14 CFR 71.1 of the Federal Aviation
Administration Order 7400.9X, Airspace
Designations and Reporting Points,
dated August 7, 2013, and effective
September 15, 2013, is amended as
follows:
■
Paragraph 6010(a)
airways.
*
*
*
Domestic VOR Federal
*
*
V–626 [Amended]
From INT Fairfield, UT, 126° and Myton,
UT, 264° radials; to Myton.
Issued in Washington, DC, on March 11,
2014.
Gary A. Norek,
Manager, Airspace Policy and Regulations
Group.
[FR Doc. 2014–05896 Filed 3–20–14; 8:45 am]
BILLING CODE 4910–13–P
DEPARTMENT OF TRANSPORTATION
Federal Aviation Administration
14 CFR Part 71
[Docket No. FAA–2013–0915; Airspace
Docket No. 12–ASO–41]
RIN 2120–AA66
Modification, Revocation, and
Establishment of Area Navigation
(RNAV) Routes; Charlotte, NC
Federal Aviation
Administration (FAA), DOT.
ACTION: Final rule.
AGENCY:
■
This action establishes two
RNAV routes; modifies three RNAV
routes; and removes one RNAV route in
the Charlotte, NC, area. These changes,
in combination with existing VOR
Federal airways, provide additional
routing options through and around the
Charlotte, NC area.
DATES: Effective date 0901 UTC, May 29,
2014. The Director of the Federal
Register approves this incorporation by
reference action under 1 CFR part 51,
subject to the annual revision of FAA
Order 7400.9 and publication of
conforming amendments.
FOR FURTHER INFORMATION CONTACT: Paul
Gallant, Airspace Policy and
Regulations Group, Office of Airspace
Services, Federal Aviation
Administration, 800 Independence
Avenue SW., Washington, DC 20591;
telephone: (202) 267–8783.
SUPPLEMENTARY INFORMATION:
Authority: 49 U.S.C. 106(g), 40103, 40113,
40120; E.O. 10854, 24 FR 9565, 3 CFR, 1959–
1963 Comp., p. 389.
History
On December 19, 2013, the FAA
published in the Federal Register a
List of Subjects in 14 CFR Part 71
Airspace, Incorporation by reference,
Navigation (air).
Adoption of the Amendment
In consideration of the foregoing, the
Federal Aviation Administration
amends 14 CFR part 71 as follows:
PART 71—DESIGNATION OF CLASS A,
B, C, D, AND E AIRSPACE AREAS; AIR
TRAFFIC SERVICE ROUTES; AND
REPORTING POINTS
1. The authority citation for 14 CFR
part 71 continues to read as follows:
PO 00000
Frm 00045
Fmt 4700
Sfmt 4700
SUMMARY:
E:\FR\FM\21MRR1.SGM
21MRR1
15678
Federal Register / Vol. 79, No. 55 / Friday, March 21, 2014 / Rules and Regulations
notice of proposed rulemaking (NPRM)
to establish 2 RNAV routes; modify 3
RNAV routes; and remove 1 RNAV
route in the Charlotte, NC, area (78 FR
76784). Interested parties were invited
to participate in this rulemaking effort
by submitting written comments on the
proposal. One comment was received.
The Aircraft Owners and Pilots
Association expressed support for the
proposal.
mstockstill on DSK4VPTVN1PROD with RULES
Differences From the NPRM
The NPRM stated that this action
would support the Charlotte
Optimization of Airspace and
Procedures in a Metroplex (OAPM)
Project. That statement resulted in some
confusion over the status of the T-route
proposal versus the Metroplex project.
To clarify, while these new routes will
enhance airspace efficiency in the
Charlotte Metroplex area, the T-routes
in this rule have independent utility
from the Metroplex project and the
environmental evaluations were
conducted independently.
The Rule
The FAA is amending Title 14, Code
of Federal Regulations (14 CFR) part 71
to establish 2 low-altitude RNAV routes
(T–206 and T–214); modify 3 RNAV
routes (T–201, T–202 and T–203); and
remove 1 RNAV route (T–200), in the
Charlotte, NC, area. The route changes
are described below.
T–200: T–200, extending between the
foothills, GA, VORTAC and the
Florence, SC, VORTAC, is removed in
its entirety. T–200 is seldom used
because it traverses very close to the
‘‘final box’’ for Charlotte/Douglas
International Airport (CLT) when CLT is
landing to the north. The modified T–
202 (see below) provides routing
through the south end of the CLT Class
B airspace area in place of T–200.
T–201: T–201, extending between the
Columbia, SC, VORTAC (CAE) and the
JOTTA, NC, fix, is shortened to extend
between the MEVAE, SC, waypoint
(WP) (near Bethune, SC) at the south
end, and the BORTZ, NC, WP (south of
the JOTTA fix) at the north end. In
addition, the track of the route is shifted
approximately 7 nautical miles (NM) to
the east of its current position. The shift
moves the route to the east of the CLT
Class B airspace area where it passes
through the FEGNO, NC, WP instead of
the LOCAS, NC, fix (on the eastern
boundary of the Class B airspace area).
T–201 segregates low altitude overflight
traffic from CLT departure and arrival
traffic. Waypoints along the route
provide connectivity with RNAV routes
T–202, T–206 and T–214 (described
below).
VerDate Mar<15>2010
15:59 Mar 20, 2014
Jkt 232001
T–202: T–202 is extended at both
ends: northeastward from the GANTS
fix to the ZADEL WP (near Asheboro
Municipal Airport [HBI], NC); and
westward from the RICHE fix to the
GURSH WP (near Union County Airport
[35A], SC). T–202 utilizes airspace
around the south of CLT when CLT is
landing and departing to the south. That
segment from the RICHE WP to the
HUSTN WP segregates T–202 traffic
from CLT departures. Waypoints along
the route provide connectivity to T–201,
T–206 and T–214.
T–203: T–203, extending between the
Columbia, SC, VORTAC and the
Pulaski, VA, VORTAC, is shortened to
the ANDYS, SC, fix (near Winnsboro,
SC) at the south end, and the OREAD,
NC, WP (10 miles north of Hickory, NC)
at the north end. In addition, the track
is shifted slightly to the west of its
current position but still transiting
through the west side of the CLT Class
B airspace area. By routing T–203 via
the ROUTH, NC, WP (near Grover, SC),
transiting aircraft are segregated from
CLT departure airspace. Waypoints
along the route provide connectivity to
T–202, T–206 and T–214.
T–206: T–206 is a new route
extending between the ENADE, NC, WP
(near Cliffside, NC) and the ZADEL, NC,
WP (near Asheboro Regional Airport
[HBI], NC). The route is used to
transition aircraft through the north side
of the CLT Class B airspace area when
CLT is landing and departing to the
north. Waypoints along the route
provide connectivity to T–201, T–202,
T–203 and T–214. Additionally, the
alignment of T–206 through the GOTHS,
NC, WP (northwest of the existing
MOPED, NC, fix) deconflicts transiting
traffic from CLT departures.
T–214: T–214 is a new route
extending between the OREAD WP and
the ORPEE, NC, WP (north of Troy, NC),
allowing aircraft to transition north of
the CLT Class B airspace when CLT is
landing and departing to the north. T–
214 provides a predictable route to
points northwest and west of Charlotte
that are deconflicted from the CLT
arrival flow.
The above routes are segregated from
the heavily used arrival and departure
corridors serving the Charlotte area,
enhancing the efficiency of the National
Airspace System in the Charlotte, NC,
area.
Low altitude RNAV routes are
published in paragraph 6011 of FAA
Order 7400.9X dated August 7, 2013,
and effective September 15, 2013, which
is incorporated by reference in 14 CFR
71.1. The RNAV routes listed in this
document will be published
subsequently in the Order.
PO 00000
Frm 00046
Fmt 4700
Sfmt 4700
The FAA has determined that this
regulation only involves an established
body of technical regulations for which
frequent and routine amendments are
necessary to keep them operationally
current. Therefore, this regulation: (1) Is
not a ‘‘significant regulatory action’’
under Executive Order 12866; (2) is not
a ‘‘significant rule’’ under Department of
Transportation (DOT) Regulatory
Policies and Procedures (44 FR 11034;
February 26, 1979); and (3) does not
warrant preparation of a regulatory
evaluation as the anticipated impact is
so minimal. Since this is a routine
matter that only affects air traffic
procedures and air navigation, it is
certified that this rule, when
promulgated, does not have a significant
economic impact on a substantial
number of small entities under the
criteria of the Regulatory Flexibility Act.
The FAA’s authority to issue rules
regarding aviation safety is found in
Title 49 of the United States Code.
Subtitle I, Section 106 describes the
authority of the FAA Administrator.
Subtitle VII, Aviation Programs,
describes in more detail the scope of the
agency’s authority.
This rulemaking is promulgated
under the authority described in
Subtitle VII, Part A, Subpart I, Section
40103. Under that section, the FAA is
charged with prescribing regulations to
assign the use of the airspace necessary
to ensure the safety of aircraft and the
efficient use of airspace. This regulation
is within the scope of that authority as
it modifies the route structure as
required to enhance the safe and
efficient flow of air traffic in the
Charlotte, NC, area.
Environmental Review
The FAA has determined that this
action qualifies for categorical exclusion
under the National Environmental
Policy Act in accordance with FAA
Order 1050.1E, ‘‘Environmental
Impacts: Policies and Procedures,’’
paragraph 311a. This airspace action is
not expected to cause any potentially
significant environmental impacts, and
no extraordinary circumstances exist
that warrant preparation of an
environmental assessment.
List of Subjects in 14 CFR Part 71
Airspace, Incorporation by reference,
Navigation (air).
Adoption of the Amendment
In consideration of the foregoing, the
Federal Aviation Administration
amends 14 CFR part 71 as follows:
E:\FR\FM\21MRR1.SGM
21MRR1
Federal Register / Vol. 79, No. 55 / Friday, March 21, 2014 / Rules and Regulations
PART 71—DESIGNATION OF CLASS A,
B, C, D, AND E AIRSPACE AREAS; AIR
TRAFFIC SERVICE ROUTES; AND
REPORTING POINTS
Authority: 49 U.S.C. 106(g), 40103, 40113,
40120; E.O. 10854, 24 FR 9565, 3 CFR, 1959–
1963 Comp., p. 389.
1. The authority citation for part 71
continues to read as follows:
■
§ 71.1
[Amended]
T–200
FOOTHILLS, GA to FLORENCE, SC [Removed]
T–201
MEVAE, SC to BORTZ, NC [Amended]
MEVAE, SC
TRUEX, SC
FEGNO, NC
NUROE, NC
BORTZ, NC
T–202
T–203
N.,
N.,
N.,
N.,
N.,
long.
long.
long.
long.
long.
80°22′28″
80°21′18″
80°16′39″
80°31′15″
80°44′56″
W.)
W.)
W.)
W.)
W.)
WP
WP
FIX
FIX
WP
FIX
WP
(lat.
(lat.
(lat.
(lat.
(lat.
(lat.
(lat.
34°42′05″
34°42′00″
34°41′54″
34°53′20″
35°14′49″
35°27′11″
35°33′47″
long.
long.
long.
long.
long.
long.
long.
81°30′32″
81°14′52″
80°59′23″
80°34′20″
80°16′39″
80°06′16″
80°01′47″
W.)
W.)
W.)
W.)
W.)
W.)
W.)
N.,
N.,
N.,
N.,
N.,
long.
long.
long.
long.
long.
81°08′38″
81°14′52″
81°23′59″
81°20′49″
81°16′32″
W.)
W.)
W.)
W.)
W.)
N.,
N.,
N.,
N.,
N.,
long.
long.
long.
long.
long.
81°44′41″
81°20′49″
80°58′25″
80°31′15″
80°01′47″
W.)
W.)
W.)
W.)
W.)
N.,
N.,
N.,
N.,
N.,
long.
long.
long.
long.
long.
81°16′32″
80°44′56″
80°28′57″
80°01′47″
79°52′56″
W.)
W.)
W.)
W.)
W.)
N.,
N.,
N.,
N.,
N.,
N.,
N.,
FIX
WP
WP
WP
WP
(lat.
(lat.
(lat.
(lat.
(lat.
34°22′15″
34°42′00″
35°10′38″
35°28′22″
35°52′03″
WP
WP
WP
WP
WP
(lat.
(lat.
(lat.
(lat.
(lat.
35°12′08″
35°28′22″
35°35′17″
35°34′37″
35°33′47″
OREAD, NC to ORPEE, NC [New]
OREAD, NC
BORTZ, NC
THMSN, NC
ZADEL, NC
ORPEE, NC
Issued in Washington, DC, on March 11,
2014.
Gary A. Norek,
Manager, Airspace Policy and Regulations
Group.
Federal Aviation Administration
14 CFR Part 91
[Docket No. FAA–2011–0246; Amendment
No. 91–321A; SFAR No. 112]
RIN 2120–AJ93
Prohibition Against Certain Flights
Within the Tripoli Flight Information
Region (FIR); Extension of Expiration
Date
Jkt 232001
35°52′03″
35°52′56″
35°53′21″
35°33′47″
35°27′12″
This action extends the
prohibition of flight operations within
the Tripoli Flight Information Region
(FIR) by all U.S. air carriers; U.S.
commercial operators; persons
exercising the privileges of an airman
certificate issued by the FAA, except
when such persons are operating a U.S.registered aircraft for a foreign air
carrier; and operators of U.S.-registered
civil aircraft, except operators of such
aircraft that are foreign air carriers. The
extension of the expiration date is
necessary to prevent a potential hazard
to persons and aircraft engaged in such
flight operations while the FAA
evaluates whether any amendments to
the regulation would be appropriate,
given current conditions in Libya.
SUMMARY:
DEPARTMENT OF TRANSPORTATION
Federal Aviation
Administration (FAA), DOT.
(lat.
(lat.
(lat.
(lat.
(lat.
Final rule; extension of
expiration date.
BILLING CODE 4910–13–P
AGENCY:
WP
WP
WP
WP
WP
ACTION:
[FR Doc. 2014–05894 Filed 3–20–14; 8:45 am]
15:59 Mar 20, 2014
34°25′05″
34°35′55″
35°14′49″
35°34′37″
35°52′56″
ENADE, NC to ZADEL, NC [New]
ENADE, NC
FADOS, NC
GOTHS, NC
NUROE, NC
ZADEL, NC
T–214
(lat.
(lat.
(lat.
(lat.
(lat.
ANDYS, SC to OREAD, NC [Amended]
ANDYS, SC
AWRYT, SC
ROUTH, NC
FADOS, NC
OREAD, NC
T–206
WP
WP
WP
WP
WP
GURSH, SC to ZADEL, NC [Amended]
GURSH, SC.
AWRYT, SC
RICHE, SC
HUSTN, NC
FEGNO, NC
GANTS, NC
ZADEL, NC.
VerDate Mar<15>2010
Airspace Designations and Reporting
Points, dated August 7, 2013, and
effective September 15, 2013, is
amended as follows:
2. The incorporation by reference in
14 CFR 71.1 of FAA Order 7400.9X,
■
mstockstill on DSK4VPTVN1PROD with RULES
15679
In this action, amendment 2 to
§ 91.1603 is effective March 21, 2014.
DATES:
PO 00000
Frm 00047
Fmt 4700
Sfmt 4700
Amendment 3 to § 91.1603 is effective
March 20, 2015.
SFAR 112 (14 CFR 91.1603),
published at 76 FR 16236 (March 23,
2011) and scheduled to expire on March
21, 2014, will remain in effect. The
expiration date is extended until March
20, 2015.
ADDRESSES: You may send comments
identified by docket number FAA–
2011–0246 using any of the following
methods:
• Federal eRulemaking Portal: Go to
https://www.regulations.gov and follow
the online instructions for sending your
comments electronically.
• Mail: Send comments to Docket
Operations, M–30; U.S. Department of
Transportation (DOT), 1200 New Jersey
Avenue SE., Room W12–140, West
Building Ground Floor, Washington, DC
20590–0001.
• Hand Delivery or Courier: Take
comments to Docket Operations in
Room W12–140 of the West Building
E:\FR\FM\21MRR1.SGM
21MRR1
]]>Agencies
[Federal Register Volume 79, Number 55 (Friday, March 21, 2014)]
[Rules and Regulations]
[Pages 15677-15679]
From the Federal Register Online via the Government Printing Office [www.gpo.gov]
[FR Doc No: 2014-05894]
-----------------------------------------------------------------------
DEPARTMENT OF TRANSPORTATION
Federal Aviation Administration
14 CFR Part 71
[Docket No. FAA-2013-0915; Airspace Docket No. 12-ASO-41]
RIN 2120-AA66
Modification, Revocation, and Establishment of Area Navigation
(RNAV) Routes; Charlotte, NC
AGENCY: Federal Aviation Administration (FAA), DOT.
ACTION: Final rule.
-----------------------------------------------------------------------
SUMMARY: This action establishes two RNAV routes; modifies three RNAV
routes; and removes one RNAV route in the Charlotte, NC, area. These
changes, in combination with existing VOR Federal airways, provide
additional routing options through and around the Charlotte, NC area.
DATES: Effective date 0901 UTC, May 29, 2014. The Director of the
Federal Register approves this incorporation by reference action under
1 CFR part 51, subject to the annual revision of FAA Order 7400.9 and
publication of conforming amendments.
FOR FURTHER INFORMATION CONTACT: Paul Gallant, Airspace Policy and
Regulations Group, Office of Airspace Services, Federal Aviation
Administration, 800 Independence Avenue SW., Washington, DC 20591;
telephone: (202) 267-8783.
SUPPLEMENTARY INFORMATION:
History
On December 19, 2013, the FAA published in the Federal Register a
[[Page 15678]]
notice of proposed rulemaking (NPRM) to establish 2 RNAV routes; modify
3 RNAV routes; and remove 1 RNAV route in the Charlotte, NC, area (78
FR 76784). Interested parties were invited to participate in this
rulemaking effort by submitting written comments on the proposal. One
comment was received. The Aircraft Owners and Pilots Association
expressed support for the proposal.
Differences From the NPRM
The NPRM stated that this action would support the Charlotte
Optimization of Airspace and Procedures in a Metroplex (OAPM) Project.
That statement resulted in some confusion over the status of the T-
route proposal versus the Metroplex project. To clarify, while these
new routes will enhance airspace efficiency in the Charlotte Metroplex
area, the T-routes in this rule have independent utility from the
Metroplex project and the environmental evaluations were conducted
independently.
The Rule
The FAA is amending Title 14, Code of Federal Regulations (14 CFR)
part 71 to establish 2 low-altitude RNAV routes (T-206 and T-214);
modify 3 RNAV routes (T-201, T-202 and T-203); and remove 1 RNAV route
(T-200), in the Charlotte, NC, area. The route changes are described
below.
T-200: T-200, extending between the foothills, GA, VORTAC and the
Florence, SC, VORTAC, is removed in its entirety. T-200 is seldom used
because it traverses very close to the ``final box'' for Charlotte/
Douglas International Airport (CLT) when CLT is landing to the north.
The modified T-202 (see below) provides routing through the south end
of the CLT Class B airspace area in place of T-200.
T-201: T-201, extending between the Columbia, SC, VORTAC (CAE) and
the JOTTA, NC, fix, is shortened to extend between the MEVAE, SC,
waypoint (WP) (near Bethune, SC) at the south end, and the BORTZ, NC,
WP (south of the JOTTA fix) at the north end. In addition, the track of
the route is shifted approximately 7 nautical miles (NM) to the east of
its current position. The shift moves the route to the east of the CLT
Class B airspace area where it passes through the FEGNO, NC, WP instead
of the LOCAS, NC, fix (on the eastern boundary of the Class B airspace
area). T-201 segregates low altitude overflight traffic from CLT
departure and arrival traffic. Waypoints along the route provide
connectivity with RNAV routes T-202, T-206 and T-214 (described below).
T-202: T-202 is extended at both ends: northeastward from the GANTS
fix to the ZADEL WP (near Asheboro Municipal Airport [HBI], NC); and
westward from the RICHE fix to the GURSH WP (near Union County Airport
[35A], SC). T-202 utilizes airspace around the south of CLT when CLT is
landing and departing to the south. That segment from the RICHE WP to
the HUSTN WP segregates T-202 traffic from CLT departures. Waypoints
along the route provide connectivity to T-201, T-206 and T-214.
T-203: T-203, extending between the Columbia, SC, VORTAC and the
Pulaski, VA, VORTAC, is shortened to the ANDYS, SC, fix (near
Winnsboro, SC) at the south end, and the OREAD, NC, WP (10 miles north
of Hickory, NC) at the north end. In addition, the track is shifted
slightly to the west of its current position but still transiting
through the west side of the CLT Class B airspace area. By routing T-
203 via the ROUTH, NC, WP (near Grover, SC), transiting aircraft are
segregated from CLT departure airspace. Waypoints along the route
provide connectivity to T-202, T-206 and T-214.
T-206: T-206 is a new route extending between the ENADE, NC, WP
(near Cliffside, NC) and the ZADEL, NC, WP (near Asheboro Regional
Airport [HBI], NC). The route is used to transition aircraft through
the north side of the CLT Class B airspace area when CLT is landing and
departing to the north. Waypoints along the route provide connectivity
to T-201, T-202, T-203 and T-214. Additionally, the alignment of T-206
through the GOTHS, NC, WP (northwest of the existing MOPED, NC, fix)
deconflicts transiting traffic from CLT departures.
T-214: T-214 is a new route extending between the OREAD WP and the
ORPEE, NC, WP (north of Troy, NC), allowing aircraft to transition
north of the CLT Class B airspace when CLT is landing and departing to
the north. T-214 provides a predictable route to points northwest and
west of Charlotte that are deconflicted from the CLT arrival flow.
The above routes are segregated from the heavily used arrival and
departure corridors serving the Charlotte area, enhancing the
efficiency of the National Airspace System in the Charlotte, NC, area.
Low altitude RNAV routes are published in paragraph 6011 of FAA
Order 7400.9X dated August 7, 2013, and effective September 15, 2013,
which is incorporated by reference in 14 CFR 71.1. The RNAV routes
listed in this document will be published subsequently in the Order.
The FAA has determined that this regulation only involves an
established body of technical regulations for which frequent and
routine amendments are necessary to keep them operationally current.
Therefore, this regulation: (1) Is not a ``significant regulatory
action'' under Executive Order 12866; (2) is not a ``significant rule''
under Department of Transportation (DOT) Regulatory Policies and
Procedures (44 FR 11034; February 26, 1979); and (3) does not warrant
preparation of a regulatory evaluation as the anticipated impact is so
minimal. Since this is a routine matter that only affects air traffic
procedures and air navigation, it is certified that this rule, when
promulgated, does not have a significant economic impact on a
substantial number of small entities under the criteria of the
Regulatory Flexibility Act.
The FAA's authority to issue rules regarding aviation safety is
found in Title 49 of the United States Code. Subtitle I, Section 106
describes the authority of the FAA Administrator. Subtitle VII,
Aviation Programs, describes in more detail the scope of the agency's
authority.
This rulemaking is promulgated under the authority described in
Subtitle VII, Part A, Subpart I, Section 40103. Under that section, the
FAA is charged with prescribing regulations to assign the use of the
airspace necessary to ensure the safety of aircraft and the efficient
use of airspace. This regulation is within the scope of that authority
as it modifies the route structure as required to enhance the safe and
efficient flow of air traffic in the Charlotte, NC, area.
Environmental Review
The FAA has determined that this action qualifies for categorical
exclusion under the National Environmental Policy Act in accordance
with FAA Order 1050.1E, ``Environmental Impacts: Policies and
Procedures,'' paragraph 311a. This airspace action is not expected to
cause any potentially significant environmental impacts, and no
extraordinary circumstances exist that warrant preparation of an
environmental assessment.
List of Subjects in 14 CFR Part 71
Airspace, Incorporation by reference, Navigation (air).
Adoption of the Amendment
In consideration of the foregoing, the Federal Aviation
Administration amends 14 CFR part 71 as follows:
[[Page 15679]]
PART 71--DESIGNATION OF CLASS A, B, C, D, AND E AIRSPACE AREAS; AIR
TRAFFIC SERVICE ROUTES; AND REPORTING POINTS
0
1. The authority citation for part 71 continues to read as follows:
Authority: 49 U.S.C. 106(g), 40103, 40113, 40120; E.O. 10854, 24
FR 9565, 3 CFR, 1959-1963 Comp., p. 389.
Sec. 71.1 [Amended]
0
2. The incorporation by reference in 14 CFR 71.1 of FAA Order 7400.9X,
Airspace Designations and Reporting Points, dated August 7, 2013, and
effective September 15, 2013, is amended as follows:
T-200 FOOTHILLS, GA to FLORENCE, SC [Removed]
T-201 MEVAE, SC to BORTZ, NC [Amended]
MEVAE, SC WP (lat. 34[deg]25'05'' N., long. 80[deg]22'28'' W.)
TRUEX, SC WP (lat. 34[deg]35'55'' N., long. 80[deg]21'18'' W.)
FEGNO, NC WP (lat. 35[deg]14'49'' N., long. 80[deg]16'39'' W.)
NUROE, NC WP (lat. 35[deg]34'37'' N., long. 80[deg]31'15'' W.)
BORTZ, NC WP (lat. 35[deg]52'56'' N., long. 80[deg]44'56'' W.)
T-202 GURSH, SC to ZADEL, NC [Amended]
GURSH, SC. WP (lat. 34[deg]42'05'' N., long. 81[deg]30'32'' W.)
AWRYT, SC WP (lat. 34[deg]42'00'' N., long. 81[deg]14'52'' W.)
RICHE, SC FIX (lat. 34[deg]41'54'' N., long. 80[deg]59'23'' W.)
HUSTN, NC FIX (lat. 34[deg]53'20'' N., long. 80[deg]34'20'' W.)
FEGNO, NC WP (lat. 35[deg]14'49'' N., long. 80[deg]16'39'' W.)
GANTS, NC FIX (lat. 35[deg]27'11'' N., long. 80[deg]06'16'' W.)
ZADEL, NC. WP (lat. 35[deg]33'47'' N., long. 80[deg]01'47'' W.)
T-203 ANDYS, SC to OREAD, NC [Amended]
ANDYS, SC FIX (lat. 34[deg]22'15'' N., long. 81[deg]08'38'' W.)
AWRYT, SC WP (lat. 34[deg]42'00'' N., long. 81[deg]14'52'' W.)
ROUTH, NC WP (lat. 35[deg]10'38'' N., long. 81[deg]23'59'' W.)
FADOS, NC WP (lat. 35[deg]28'22'' N., long. 81[deg]20'49'' W.)
OREAD, NC WP (lat. 35[deg]52'03'' N., long. 81[deg]16'32'' W.)
T-206 ENADE, NC to ZADEL, NC [New]
ENADE, NC WP (lat. 35[deg]12'08'' N., long. 81[deg]44'41'' W.)
FADOS, NC WP (lat. 35[deg]28'22'' N., long. 81[deg]20'49'' W.)
GOTHS, NC WP (lat. 35[deg]35'17'' N., long. 80[deg]58'25'' W.)
NUROE, NC WP (lat. 35[deg]34'37'' N., long. 80[deg]31'15'' W.)
ZADEL, NC WP (lat. 35[deg]33'47'' N., long. 80[deg]01'47'' W.)
T-214 OREAD, NC to ORPEE, NC [New]
OREAD, NC WP (lat. 35[deg]52'03'' N., long. 81[deg]16'32'' W.)
BORTZ, NC WP (lat. 35[deg]52'56'' N., long. 80[deg]44'56'' W.)
THMSN, NC WP (lat. 35[deg]53'21'' N., long. 80[deg]28'57'' W.)
ZADEL, NC WP (lat. 35[deg]33'47'' N., long. 80[deg]01'47'' W.)
ORPEE, NC WP (lat. 35[deg]27'12'' N., long. 79[deg]52'56'' W.)
Issued in Washington, DC, on March 11, 2014.
Gary A. Norek,
Manager, Airspace Policy and Regulations Group.
[FR Doc. 2014-05894 Filed 3-20-14; 8:45 am]
BILLING CODE 4910-13-P
