## 43181 Federal Register / Vol. 77, No. 142 / Tuesday, July 24, 2012 / Proposed Rules

Instructions of Boeing Alert Service Bulletin MD90–57A026, Revision 1, dated February
23, 2011.

(B) Within 13,500 flight cycles after doing the doubler repair required by paragraph (i)(2)(i)(A) of this AD, do an ETHF inspection for any cracking in the repaired area of the rear spar upper cap, in accordance with the Accomplishment Instructions of Boeing Alert Service Bulletin MD90–57A026, Revision 1, dated February 23, 2011. Repeat the inspection thereafter at intervals not to exceed 8,500 flight cycles. If any cracking is found during any inspection required by this paragraph, before further flight, repair in accordance with a method approved in accordance with the procedures specified in paragraph (l) of this AD.

(C) Within 20,000 flight cycles after doing the splice repair required by paragraph (i)(2)(i)(A) of this AD, do an ETLF inspection and a UT inspection for cracking in the repaired area of the rear spar lower cap, in accordance with the Accomplishment Instructions of Boeing Alert Service Bulletin MD90–57A026, Revision 1, dated February 23, 2011. Repeat the inspections thereafter at intervals not to exceed 3,000 flight cycles. If any cracking is found during any inspection required by this paragraph, before further flight, repair in accordance with a method approved in accordance with the procedures specified in paragraph (l) of this AD.

(ii) Option 2: Before further flight, do a splice repair of the rear spar upper and lower caps, in accordance with the Accomplishment Instructions of Boeing Alert Service Bulletin MD90–57A026, Revision 1, dated February 23, 2011. Within 20,000 flight cycles after doing the splice repair, do an ETLF inspection and a UT inspection for cracking in the repaired area of the rear spar lower cap, in accordance with the Accomplishment Instructions of Boeing Alert Service Bulletin MD90–57A026, Revision 1, dated February 23, 2011. Repeat the inspections thereafter at intervals not to exceed 3,000 flight cycles. If any cracking is found during any inspection required by this paragraph, before further flight, repair in accordance with a method approved in accordance with the procedures specified in paragraph (l) of this AD.

(3) If any crack that is greater than two inches is found in the rear spar upper cap, before further flight, do a splice repair of the rear spar upper and lower caps, in accordance with the Accomplishment Instructions of Boeing Alert Service Bulletin MD90–57A026, Revision 1, dated February 23, 2011. Within 20,000 flight cycles after doing the splice repair, do an ETLF inspection and a UT inspection for cracking in the repaired area of the rear spar lower cap, in accordance with the Accomplishment Instructions of Boeing Alert Service Bulletin MD90–57A026, Revision 1, dated February 23, 2011. Repeat the inspections thereafter at intervals not to exceed 3,000 flight cycles. If any cracking is found during any inspection required by this paragraph, before further flight, repair in accordance with a method approved in accordance with the procedures specified in paragraph (l) of this AD. (j) Repeat ETHF Inspection For airplanes on which any splice repair was required by this AD: Within 30,000 flight cycles after the splice repair, repeat the inspection required by paragraph (g) of this AD for the repaired wing. If no cracking is found on the on the rear spar lower cap of the repaired wing, repeat the inspection on the affected wing rear spar lower cap thereafter at intervals not to exceed 2,550 flight cycles. If any cracking is found during any inspection required by this paragraph, before further flight, repair in accordance with a method approved in accordance with the procedures specified in paragraph (l) of this AD.

(k) Credit for Previous Actions

This paragraph provides credit for the actions required by paragraphs (g), (h), and (i) of this AD, if those actions were performed before the effective date of this AD using Boeing Alert Service Bulletin MD90–57A026, dated February 11, 2010.

(l) Alternative Methods of Compliance (AMOCs)

(1) The Manager, Los Angeles Aircraft Certification Office (ACO), FAA, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. In accordance with 14 CFR 39.19, send your request to your principal inspector or local Flight Standards District Office, as appropriate. If sending information directly to the manager of the ACO, send it to the attention of the person identified in the Related Information section of this AD.

(2) Before using any approved AMOC, notify your appropriate principal inspector, or lacking a principal inspector, the manager of the local flight standards district office/ certificate holding district office.

(3) An AMOC that provides an acceptable level of safety may be used for any repair required by this AD if it is approved by the Boeing Commercial Airplanes Organization Designation Authorization (ODA) that has been authorized by the Manager, Los Angeles ACO, to make those findings. For a repair method to be approved, the repair must meet the certification basis of the airplane and 14 CFR 25.571, Amendment 45, and the approval must specifically refer to this AD.

(m) Related Information

(1) For more information about this AD, contact Roger Durbin, Airframe Branch, ANM–120L, FAA, Los Angeles ACO, 3960 Paramount Boulevard, Lakewood, California 90712–4137; phone: (562) 627–5233; fax: (562) 627–5210; email: roger.durbin@faa.gov.

(2) For service information identified in this AD, contact Boeing Commercial Airplanes, Attention: Data & Services Management, 3855 Lakewood Boulevard, MC D800–0019, Long Beach, California 90846– 0001; telephone 206–544–5000, extension 2; fax 206–766–5683; Internet https:// www.myboeingfleet.com. You may review copies of the referenced service information at the FAA, Transport Airplane Directorate, 1601 Lind Avenue SW., Renton, Washington. For information on the availability of this material at the FAA, call 425–227–1221. Issued in Renton, Washington, on July 13,

2012. Michael Kaszycki, Acting Manager, Transport Airplane Directorate, Aircraft Certification Service.

[FR Doc. 2012–17968 Filed 7–23–12; 8:45 am]

**BILLING CODE 4910–13–P**



### DEPARTMENT OF TRANSPORTATION

**Federal Aviation Administration**

**14 CFR Part 71**

**Docket No. FAA–2012–0705; Airspace Docket No. 12–AWP–4** 



### Proposed Establishment of Class E **Airspace; Coaldale, NV**

**AGENCY** 

### : Federal Aviation Administration (FAA), DOT.

**ACTION** 

### : Notice of proposed rulemaking (NPRM).

**SUMMARY** 

### : This action proposes to establish Class E airspace at Coaldale VHF Omni-Directional Radio Range Tactical Air Navigational Aid (VORTAC), Coaldale, NV to facilitate vectoring of Instrument Flight Rules (IFR) aircraft under control of Oakland Air Route Traffic Control Center (ARTCC). The FAA is proposing this action to enhance the safety and management of aircraft operations within the National Airspace System.

**DATES** 

### : Comments must be received on or before September 7, 2012.

**ADDRESSES** 

### : Send comments on this proposal to the U.S. Department of Transportation, Docket Operations, M– 30, West Building Ground Floor, Room W12–140, 1200 New Jersey Avenue SE., Washington, DC 20590; telephone (202) 366–9826. You must identify FAA Docket No. FAA–2012–0705; Airspace Docket No. 12–AWP–4, at the beginning of your comments. You may also submit comments through the Internet at http://www.regulations.gov.

**FOR FURTHER INFORMATION CONTACT** 

### : Eldon Taylor, Federal Aviation Administration, Operations Support Group, Western Service Center, 1601 Lind Avenue SW., Renton, WA 98057; telephone (425) 203–4537.

**SUPPLEMENTARY INFORMATION** 

### :

Comments Invited

Interested parties are invited to participate in this proposed rulemaking by submitting such written data, views, or arguments, as they may desire. Comments that provide the factual basis supporting the views and suggestions presented are particularly helpful in developing reasoned regulatory


## 43182 Federal Register / Vol. 77, No. 142 / Tuesday, July 24, 2012 / Proposed Rules

decisions on the proposal. Comments are specifically invited on the overall regulatory, aeronautical, economic, environmental, and energy-related aspects of the proposal.

Communications should identify both docket numbers (FAA Docket No. FAA 2012–0705 and Airspace Docket No. 12– AWP–4) and be submitted in triplicate to the Docket Management System (see

**ADDRESSES** 

### section for address and phone number). You may also submit comments through the Internet at http://www.regulations.gov.

Commenters wishing the FAA to acknowledge receipt of their comments on this action must submit with those comments a self-addressed stamped postcard on which the following statement is made: ‘‘Comments to FAA Docket No. FAA–2012–0705 and Airspace Docket No. 12–AWP–4.’’ The postcard will be date/time stamped and returned to the commenter.

All communications received on or before the specified closing date for comments will be considered before taking action on the proposed rule. The proposal contained in this action may be changed in light of comments received. All comments submitted will be available for examination in the public docket both before and after the closing date for comments. A report summarizing each substantive public contact with FAA personnel concerned with this rulemaking will be filed in the docket.
Availability of NPRMs

An electronic copy of this document may be downloaded through the
Internet at http://www.regulations.gov. Recently published rulemaking documents can also be accessed through the FAA’s Web page at http:// www.faa.gov/airports

_airtraffic/
air

_ traffic/publications/ airspace

_amendments/.

You may review the public docket containing the proposal, any comments received, and any final disposition in person in the Dockets Office (see the

**ADDRESSES** 

### section for the address and phone number) between 9:00 a.m. and 5:00 p.m., Monday through Friday, except federal holidays. An informal docket may also be examined during normal business hours at the Northwest Mountain Regional Office of the Federal Aviation Administration, Air Traffic Organization, Western Service Center, Operations Support Group, 1601 Lind Avenue SW., Renton, WA 98057.

Persons interested in being placed on a mailing list for future NPRMs should contact the FAA’s Office of Rulemaking, (202) 267–9677, for a copy of Advisory Circular No. 11–2A, Notice of Proposed Rulemaking Distribution System, which describes the application procedure.
The Proposal

The FAA is proposing an amendment to Title 14 Code of Federal Regulations (14 CFR) Part 71 by establishing Class E en route domestic airspace extending upward from 1,200 feet above the surface at Coaldale VORTAC, Coaldale, NV. This action would contain aircraft while in IFR conditions under control of the Oakland ARTCC by vectoring aircraft from en route airspace to terminal areas.

Class E airspace designations are published in paragraph 6006, of FAA Order 7400.9V, dated August 9, 2011, and effective September 15, 2011, which is incorporated by reference in 14 CFR 71.1. The Class E airspace designation listed in this document will be published subsequently in this Order.

The FAA has determined this proposed regulation only involves an established body of technical regulations for which frequent and routine amendments are necessary to keep them operationally current. Therefore, this proposed 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 will only affect air traffic procedures and air navigation, it is certified this proposed rule, when promulgated, would 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 U.S. Code. Subtitle 1, Section 106, describes the authority for 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 would establish controlled airspace at the Coaldale VORTAC, Coaldale, NV.

This proposal will be subject to an environmental analysis in accordance with FAA Order 1050.1E, ‘‘Environmental Impacts: Policies and Procedures’’ prior to any FAA final regulatory action.
List of Subjects in 14 CFR Part 71

Airspace, Incorporation by reference, Navigation (air).
The Proposed Amendment

Accordingly, pursuant to the authority delegated to me, the Federal Aviation Administration proposes to amend 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:

Authority: 49 U.S.C. 106(g), 40103, 40113, 40120; E.O. 10854, 24 FR 9565, 3 CFR, 1959– 1963 Comp., p. 389.

**§ 71.1 [Amended]**



### 2. The incorporation by reference in 14 CFR 71.1 of the Federal Aviation Administration Order 7400.9V, Airspace Designations and Reporting Points, dated August 9, 2011, and effective September 15, 2011 is amended as follows:

Paragraph 6006 En Route Domestic Airspace Areas



### * * * * *

AWP NV E6 Coaldale, NV [New]

Coaldale VORTAC

(Lat. 38 ° 00 ′ 12 ′′ N., long. 117 ° 46 ′ 14 ′′ W.) That airspace extending upward from 1,200 feet above the surface bounded by a line beginning at lat. 38 ° 55 ′ 20′′ N., long.

119 ° 22 ′42 ′′ W.; to lat. 38 ° 57 ′46 ′′ N., long.

119 ° 14 ′44 ′′ W.; to lat. 38 ° 41 ′ 13 ′′ N., long.

118 ° 53 ′ 31 ′′ W.; to lat. 38 ° 44 ′ 27 ′′ N., long.

118 ° 48 ′ 52 ′′ W.; to lat. 38 ° 37 ′03 ′′ N., long.

118 ° 40 ′45 ′′ W.; to lat. 38 ° 23 ′ 17 ′′ N., long.

118 ° 20 ′ 35 ′′ W.; to lat. 38 ° 16 ′ 55 ′′ N., long.

118 ° 13 ′ 39 ′′ W.; to lat. 38 ° 02 ′ 23 ′′ N., long.

117 ° 56 ′00′′ W.; to lat. 37 ° 45 ′08 ′′ N., long.

117 ° 41 ′ 19 ′′ W.; to lat. 37 ° 45 ′ 58 ′′ N., long.

117 ° 39 ′ 55 ′′ W.; to lat. 37 ° 29 ′ 37 ′′ N., long.

117 ° 25 ′ 57 ′′ W.; to lat. 37 ° 15 ′ 12 ′′ N., long.

117 ° 13 ′46 ′′ W.; to lat. 37 ° 12 ′00′′ N., long.

117 ° 20 ′00′′ W.; to lat. 37 ° 12 ′02 ′′ N., long.

117 ° 38 ′40′′ W.; to lat. 37 ° 19 ′09 ′′ N., long.

117 ° 58 ′ 15 ′′ W.; to lat. 37 ° 28 ′ 23 ′′ N., long.

117 ° 54 ′ 28 ′′ W.; to lat. 37 ° 55 ′00′′ N., long.

118 ° 10 ′ 30′′ W.; to lat. 38 ° 04 ′06 ′′ N., long.

119 ° 15 ′00′′ W.; thence to the point of origin.

Issued in Seattle, Washington, on July 16,

2012. Robert Henry, Acting Manager, Operations Support Group,
Western Service Center.

[FR Doc. 2012–18072 Filed 7–23–12; 8:45 am]

**BILLING CODE 4910–13–P**