Federal Aviation Administration December 20, 2006 – Federal Register Recent Federal Regulation Documents
Results 1 - 7 of 7
Establishment of Restricted Area 5601F; Fort Sill, OK
This action establishes Restricted Area 5601F (R-5601F) over Fort Sill, OK. The United States (U.S.) Army requested that the FAA take action to establish R-5601F to provide additional airspace needed to support new high angle air-to-ground training requirements for Air Force, Navy, and Marine aircraft operating over the Falcon Bombing Range and to enhance Fort Sill's ability to host joint training.
Production and Airworthiness Approvals; Extension of Comment Period
This action extends by 30 days the comment period for an NPRM that was published on October 5, 2006. In that document, the FAA proposed changes to its certification procedures and identification requirements for aeronautical products and parts. This extension is a result of requests from the Aeronautical Repair Station Association, the Aerospace Industries Association, and the General Aviation Manufacturers Association.
Aviation Rulemaking Advisory Committee; Transport Airplane and Engine Issue Area-New Task
Notice is given of a new task assignment for the Aviation Rulemaking Advisory Committee (ARAC). This notice is to inform the public of this ARAC activity and solicit membership to a new Propeller Harmonization Working Group to support ARAC in developing advice and recommendations on this new task.
Noise-Exposure Map Notice: Receipt of Noise-Compatibility Program and Request for Review for Portland International Airport, Portland, OR
The Federal Aviation Administration (FAA) announces its determination that the noise-exposure maps (NEM) submitted by the Director of Aviation for Portland International Airport under the provisions of 49 U.S.C. 47501 et seq. (Aviation Safety and Noise Abatement Act) and 14 CFR part 150 are in compliance with applicable requirements. The FAA also announces that it is reviewing a proposed noise-compatibility program that was submitted for Portland International Airport under Part 150, in conjunction with the noise- exposure map, and that this program will be approved or disapproved on or before June 15, 2007.
Revision of the Cancellation of Preparation of Environmental Impact Statement (EIS) for Ontario International Airport, Ontario, San Bernardino County, CA
On December 1, 2006, the FAA terminated preparation of the EIS at Ontario International Airport (ONT) since there are no proposed projects ripe for review. Los Angeles World Airports, the airport owner, will continue to prepare a master plan for ONT.
Military Airport Program (MAP) Application; Extension of Application Deadline
The Federal Aviation Administration (FAA) is extending to January 19, 2007, the date to submit an application for the MAP. The original notice, Notice of Opportunity to Participate, criteria requirements and application procedure for participation in the MAP appeared in the Federal Register on October 16, 2006 (71 FR 60791). In that Notice of Opportunity to Participate, FAA requested applications be received on or before November 27, 2006. The agency is taking this action in response to requests for an application deadline extension to allow interested persons additional time to submit applications.
Notice of a Proposed Change in Monitor Status of Air Navigational Aids
The Federal Aviation Administration is requesting public comment on a proposal to change the monitor status of select air navigational aids (NAVAIDS) at airports in the United States. The FAA is proposing that certain Instrument Landing Systems (ILS), Localizer Type Directional Aids (LDA), Microwave Landing Systems (MLS), and Non- Directional Beacons (NDB) become unmonitored. The ILS NAVAIDS at the following airports are proposed to become unmonitored during the times that the control tower is closed. The associated ILS approaches for these airports are either not authorized for alternate airport filing purposes when the control tower is closed or the airport activity is low when the control tower is closed: (1) Florence, South Carolina (FLO), ILS, Runway 9. (2) Joplin, Missouri (JLN), ILS, Runways 13 and 18. (3) Macon, Georgia (MCN), ILS, Runway 5. (4) Manhattan, Kansas (MHK), ILS, Runway 3. (5) Mobile, Alabama (MOB), ILS, Runways 14 and 32. (6) Missoula, Montana (MSO), ILS, Runway 11. (7) North Myrtle Beach, South Carolina (CRE), ILS, Runway 23. (8) Savannah, Georgia (SAV), ILS, Runways 9 and 36. (9) Tallahassee, Florida (TLH), ILS, Runway 36. (Tallahassee ILS, Runway 27 will not be affected because of its ILS Category II status.) (10) Walla Walla, Washington (ALW), ILS, Runway 20. The following ILS NAVAIDS are proposed to become unmonitored due to low annual activity at the associated airport: 1) Bemidji, Minnesota (BJI) ILS, Runway 31. (2) Huron, South Dakota (HON), ILS, Runway 12. (3) Hoquiam, Washington (HQM), ILS, Runway 24. (4) International Falls, Minnesota (INL), ILS, Runway 31. (5) Liberal, Kansas (LBL), ILS, Runway 35. (6) Muscle Shoals, Alabama (MSL), ILS, Runway 29. (7) Norfolk, Nebraska (OFK), ILS, Runway 1. The following NAVAIDS associated with non-precision approaches are proposed to become unmonitored: (1) Charles City, Iowa (CCY), ILS Localizer, Runway 12. (2) Conrad, Montana (SO1), Conrad (CRD) NDB. (3) Elkins, West Virginia (EKN), LDA/ DME. (4) Elko, Nevada (EKO), LDA/DME, Runway 23. (5) Miles City, Montana (MLS), Horton (HTN) NDB. (6) Mountain Home Municipal, Idaho (U76), Sturgeon (STI) NDB. (7) Ontario, Oregon (ONO), Ontario (ONO) NDB. (8) Pullman/Moscow ID, Washington (PUW), MLS. (9) Rawlins, Wyoming (RWL), Sinclair (SIR) NDB. (10) Wenatchee, Washington (EAT), MLS.
This site is protected by reCAPTCHA and the Google
Privacy Policy and
Terms of Service apply.
