TN66
Airport
Austin Field
Pikeville, Tennessee

FAA NFDC Information Effective 56-day cycle 09/18/2014 - 11/13/2014

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:TN66
Lat/Lng: 35.7445127778, -85.0471772222
35-44-40.2460N, 085-02-49.8380W
Estimated
Elevation: 1000 feet Estimated
Magnetic Variation: 02W, (1990), [-5W (2014)]
Sectional: ATLANTA
From City: 11nm NE of Pikeville

Operations

Use: Private
Airspace Analysis: CONDITIONAL
Provided All Operations are Conducted in VFR Wx Conds and the Landing Area is Limited to Pvt Use.
Ownership: Privately owned
Activation: 05/1992
Control Tower: no
ARTCC: Atlanta Center (ZTL)
FSS: Nashville FSS (BNA)
Wind Indicator: Unlighted
Landing Fee: no

Communications

UNICOM: 122.725

Services

Based Aircraft

Single Engine GA: 2
Total: 2

Annual Operations

Total: 0

Ownership

Owner: John L. Austin
210 Turkey Trot Ln
Pikeville, Tn 37367
423-533-2279
Manager: John L. Austin
210 Turkey Trot Ln
Memphis, Tn 38119
423-533-2279

Runways

Runways: 06/24

Runway 06/24

Length: 2100 feet
Width: 100 feet
Surface: Grass / Sod, Good Condition
End 06 End 24
Objects: Hill  
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height: 100' AGL  
Object Distance: 3000' 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.