NC08
Airport
Tusquittee Landing
Hayesville, North Carolina

FAA NFDC Information Effective 56-day cycle 11/13/2014 - 1/8/2015

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:NC08 (November-Charlie-Zero-Eight)
Lat/Lng: 35.0853686111, -83.7362819444
35-05-07.3270N, 083-44-10.6150W
Estimated
Elevation: 2000 feet Estimated
Magnetic Variation: 03W, (1980), [-6W (2014)]
Sectional: CHARLOTTE
From City: 5nm N of Hayesville

Operations

Use: Private
Airspace Analysis: CONDITIONAL
Provided VFR Pvt Use only.
Ownership: Privately owned
Activation: 11/1986
Control Tower: no
ARTCC: Atlanta Center (ZTL)
FSS: Raleigh FSS (RDU)
Wind Indicator: Unlighted
Landing Fee: no

Communications

Services

Based Aircraft

Single Engine GA: 6
Total: 6

Annual Operations

Total: 0

Ownership

Owner: Tusqittee Landing Flyers Assoc Inc
6976 Tusquittee Road
Hayesville, Nc 28904
828-389-0528
Manager: Richard Jones
6976 Tusquittee Road
Hayesville, Nc 28904
828-389-0528

Runways

Runways: 10/28

Runway 10/28

Length: 2700 feet
Width: 50 feet
Surface: Grass / Sod
End 10 End 28
Right Hand Pattern:   Yes
Objects:   Trees
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height:   40' AGL
Object Distance:   600' Along centerline

Procedures

NOTAMs

Additional Remarks


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.