|
IFR Enroute Charts
at skyvector.com Click on airport for details, drag to scroll around. Zoom using +/- keys. |
|
IFR Enroute Charts
at skyvector.com Click on airport for details, drag to scroll around. Zoom using +/- keys. |
|
FAA NFDC Information Effective 56-day cycle 05/02/2013 - 6/27/2013
| Ops | Comms | Services | Owner | Runways | IFR Procs | Current NOTAMs | Remarks |
| FAA Identifier: | NV62 |
|---|---|
| Lat/Lng: |
36.162875, -115.167736111 36-09-46.3500N, 115-10-03.8500W Estimated by OWNER on 12/01/2008 |
| Elevation: | 2057 feet Estimated by OWNER on 12/01/2008 |
| Magnetic Variation: | [12E (2013)] |
| Sectional: | LAS VEGAS |
| From City: | 1nm NW of Las Vegas |
| Use: | Private |
|---|---|
| Airspace Analysis: |
CONDITIONAL Provided Private Use only; Heliport Operator Must Contact the FAA Las Vegas Airport Traffic Control Tower/Tracon for Operational Requirements for This Facility; All Operations are Conducted in VFR Weather Conditions. |
| Ownership: | Privately owned |
| Activation: | 09/2006 |
| Control Tower: | no |
| ARTCC: | Los Angeles Center (ZLA) |
| FSS: | Reno FSS (RNO) |
| Wind Indicator: | Lighted |
| Landing Fee: | no |
Based Aircraft
|
Annual Operations
|
Ownership
|
| Runways: | H1 |
|---|
| Length: |
60 feet by Owner on 12/01/2008 |
|---|---|
| Width: | 60 feet |
| Surface: | Porland Cement Concrete |
| Runway Lights Edge Intensity: | Perimeter |
This information is current as of the date at the top of the page. These pages are valid for all US airports, based on information from FAA National Flight Data Center. Weather information is provided based on AvnWx Data Sources. NOTAM information is from FAA's NAIMES data portal.
As with most information on this website, this page is generated based on FAA data, with automatic translations done via computer. You can also directly read the A/FD via the green icon link at the top of the page, which is the FAA text, and sometimes provides a different translation of codes. Please email me (using link at top-right of this page) if you see information which is confusing, misleading, or wrong....Or have suggestions for additions/changes.
Comments from the user community are clearly noted as such this page, are for informational purposes only, may be wrong and/or out-of-date, and must not be used as a sole source for critical decision making. See Privacy Policy and Conditions of Use.