39TN
Airport
Big Sandy Airpark
Big Sandy, Tennessee

FAA NFDC Information Effective 56-day cycle 07/24/2014 - 9/18/2014

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:39TN
Lat/Lng: 36.2797222222, -88.0436111111
36-16-47.0000N, 088-02-37.0000W
Estimated by OWNER on 10/17/2006
Elevation: 632 feet Estimated by OWNER on 10/17/2006
Magnetic Variation: [-3W (2014)]
Sectional: ST LOUIS
From City: 5nm NE of Big Sandy

Operations

Use: Private
Airspace Analysis: CONDITIONAL
Provided VFR Operations, Pvt Use, and You are Aware That Airport is Within or Near a Military Training Rte or Military Training Area.
Ownership: Privately owned
Activation: 08/2005
Control Tower: no
ARTCC: Memphis Center (ZME)
FSS: Jackson FSS (MKL)
Wind Indicator: Unlighted
Landing Fee: no

Communications

Services

Based Aircraft

Single Engine GA: 3
Total: 3

Annual Operations

Total: 0

Ownership

Owner: Mike Chase
26 Forked Oak Lane
Humbodt, Tn 38343
731-618-1706
Manager: Mike Chase
26 Forked Oak Lane
Humbodt, Tn 38343
731-618-1706

Runways

Runways: 03/21

Runway 03/21

Length: 3000 feet
Width: 50 feet
Surface: Grass / Sod
End 03 End 21
Objects: Trees Trees
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height: 50' AGL 50' AGL

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.