Liley Field
Fall Branch, Tennessee

FAA NFDC Information Effective 56-day cycle 08/17/2017 - 10/12/2017

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks


FAA Identifier:20TN (Two-Zero-Tango-November)
Lat/Lng: 36.3636666667, -82.5906666667
36-21-49.2000N, 082-35-26.4000W
Estimated by OWNER on 02/10/2010
Elevation: 1850 feet Estimated by OWNER on 02/10/2010
Magnetic Variation: [-7W (2017)]
From City: 4nm SE of Fall Branch


Use: Private
Airspace Analysis: CONDITIONAL
Provided VFR Operations and Pvt Use only; Operations in and out of Liley Field are Coordinated with Tri-Cities Regional ATC.
Ownership: Privately owned
Activation: 03/2010
Control Tower: no
ARTCC: Atlanta (ZTL) Atlanta Center (ZTL)
FSS: Nashville FSS (BNA)
Wind Indicator: Unlighted
Landing Fee: no



Based Aircraft

Single Engine GA: 2
Total: 2

Annual Operations

For year ending: 02/10/2010
Total: 0


Owner: Brian Liley
204 Rosecliff Dr
Fall Branch, Tn 37656
Manager: Brian Liley
204 Rosecliff Dr
Fall Branch, Tn 37656


Runways: 13/31

Runway 13/31

Length: 1100 feet
by Owner on 02/10/2010
Width: 50 feet
Surface: Grass / Sod, Good Condition
End 13 End 31
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach



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.