Official Federal Forms > Federal Aviation Administration (FAA)
Notice Of Landing Area Proposal FAA 7480-1 - Official Federal Forms
| Notice Of Landing Area Proposal Form. This is a national form and can be used in Federal Aviation Administration (FAA) . |
|
||||||
 Get this form for FREE as a print-only pdf |
|||||||
|
Form approved OMB No. 2120-0036 02/28/2007 U.S. Department of Transportation Federal Aviation Administration NOTICE OF LANDING AREA PROPOSAL Address of Proponent, Individual , or Organization (No., Street, City, State, Zip Code) Name of Proponent, Individual , or Organization Check if the property owner's name and address are different than above, and list property owner's name and address on the reverse. Establishment or Activation Alteration A. Location of Landing Area 1. Associated City/State 4. Name of Landing Area B. Purpose Type Use Public Private Private Use of Public Land/Waters Deactivation or abandonment Change of Status } OF Airport Heliport Ultraflight Flightpark Seaplane Base Vertiport Other (Specify) 3. Distance and Direction From Associated City or Town 2. County/State (Physical Location of Airport) 5. Latitude ° 6. Longitude ° 7. Elevation " Miles Direction ' " ' If Change of Status or Alteration, Describe Change Establishment or change to traffic pattern (Describe on reverse) Construction Dates To Begin/Began Est. Completion Ref. A5 above Direction Distance From Landing Area C. Other Landing Areas From Landing Area D. Landing Area Data 1. Airport, Seaplane Base, or Flightpark Magnetic Bearing of Runway (s) or Sealane Length of Runway (s) or Sealane (s) in Feet Width of Runway (s) or Sealane (s) in Feet Type of Runway Surface (Concrete, Asphalt, Turf, Etc.) 2. Heliport Dimensions of Final Approach and Take off Area (FATO) in Feet Dimensions of Touchdown and Lift-Off Area (TLOF) in Feet Magnetic Direction of Ingress/Egress Existing (if any) Rwy #1 Rwy #2 Rwy #3 Rwy Proposed Rwy Rwy E. Obstructions Type Height Above Landing. Area Direction From Landing Area Distance From Landing Area Routes Type of Surface (Turf, concrete, rooftop, etc.) 3. All Landing Areas Description of Lighting (If any) Direction of Prevailing Wind F. Operational Data 1. Estimated or Actual Number Based Aircraft Airport, Flightpark, Seaplane base Multi-engine Single-engine Glider Present (If est. indicate by letter "E") Anticipated 5 Years Hence Heliport Present (If est. indicate by letter "E") Anticipated 5 Years Hence Under 3500 lbs. MGW Over 3500 lbs. MGW G. Other Considerations Identification Direction From Landing Area Distance From Landing Area 2. Average Number Monthly Landings Present (If est. indicate by letter "E") Jet Turboprop Prop Anticipated 5 Years Hence Helicopter Ultralight Glider Present (If est. indicate by letter "E") Anticipated 5 Years Hence 3. Are IFR Procedures For The Airport Anticipated No Yes Within Years H. Application for Airport Licensing Has Been Made Not Required Will Be Made State Type Navaid: County Municipal Authority I. CERTIFICATION: I hereby certify that all of the above statements made by me are true and complete to the best of my knowledge. Signature (in ink) Name, title (and address if different than above) of person filing this notice -- type or print Date of Signature Telephone No. (Precede with area code) FAA Form 7480-1 (1-93) Supersedes Previous Edition Central Region Electronic Revision per ACE-625 (March, 2000) American LegalNet, Inc. www.FormsWorkflow.com Paperwork Reduction Act Statement: The information collected on this form is necessary because it is the description of the physical and operational characteristics of the airport that will be on file with the FAA. The information on all airports will be maintained in FAA computers for record keeping purposes and used in airspace studies. Some of the information on public use airports is safety-critical and will be published in flight information handbooks and charts for pilot use. The burden associated with completing this form is estimated to be 30 minutes. Providing this information is mandatory if the proponent wishes to have the airport on file with the FAA and entered into the National Airspace System No assurances of confidentiality are given. An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB control number. The OMB control number associated with this collection is 2120-0036. Comments concerning the accuracy of this burden and suggestions for reducing the burden should be directed to the FAA at: 800 Independence Ave SW, Washington, DC 20591, Attn: Information Collection Clearance Officer, ABA-20. INSTRUCTIONS NOTICE OF LANDING AREA PROPOSAL As Used Herein, The Term ''Airport'' Means Any Landing or Takeoff Area such as Airport, Heliport, Helistop, Vertiport, Gliderport, Seaplane Base, Ultralight Flightpark, or Balloonport Federal Aviation Regulations Part 157 requires all persons to notify the FAA at least 90 days before any construction, alteration, activation, deactivation, or change to the status or use of a civil or joint-use (civil/military) airport. Notice is not required for the establishment of a temporary airport at which operations will be conducted under visual flight rules (VFR) and will be used for less than 30 days with no more than 10 operations per day. Notice also is not required for the intermittent use of a site that is not an established airport, which is used for less than one year and at which flight operations will be conducted only under VFR. Intermittent use means the use of the site for no more than 3 days in any one week and for no more than 10 operations per day. Required notice shall be submitted on this form from each person who intends to do any of the following: 1. Construct or otherwise establish a new airport or activate an airport. 2. Construct, realign, alter, or activate any runway, or other aircraft landing or takeoff area of an airport. 3. Construct realign, alter, or activate a taxiway associated with a landing or takeoff area on a public-use airport. 4. Deactivate, discontinue using, or abandon an airport or any landing or takeoff area of an airport for a period of one year or more. 5. Deactivate, abandon, or discontinue using a taxiway associated with a landing or takeoff area on a public-use airport. 6. Change the status of an airport from private use (use by the owner or use by the owner and other persons authorized by the owner) to an airport open to the public or from public-use to another status. 7. Change status from IFR to VFR or VFR to IFR. 8. Establish or change any traffic pattern or traffic pattern altitude or direction. The notice required shall be made by submitting this form to the nearest Federal Aviation Administration Regional Off
|
|||||||
