TN02
Airport
Paradise Airpark
Lewisburg, Tennessee

FAA NFDC Information Effective 56-day cycle 05/02/2013 - 6/27/2013

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:TN02 (Tango-November-Zero-Two)
Lat/Lng: 35.5188888889, -86.8525
35-31-08.0000N, 086-51-09.0000W
Estimated by OWNER on 11/04/2010
Elevation: 670 feet Estimated by OWNER on 11/04/2010
Magnetic Variation: [-3W (2013)]
Sectional: ATLANTA
From City: 5nm NW of Lewisburg

Operations

Use: Private
Airspace Analysis: CONDITIONAL
Provided VFR Operations and Pvt Use only; Adhere to Signed Loa Between Ellington Airport and Paradise Airpark.
Ownership: Privately owned
Activation: 01/2011
Control Tower: no
ARTCC: Memphis (ZME) Memphis Center (ZME)
FSS: Jackson FSS (MKL)
Wind Indicator: Unlighted
Landing Fee: no

Communications

Services

Based Aircraft

Ultralights: 1
Total: 1

Annual Operations

For year ending: 09/01/2010
Total: 0

Ownership

Owner: Dale & Adrienne Slechta
2222 Paradise Dr
Lewisburg, Tn 37091
520-247-4032
Manager: Dale Slechta
2222 Paradise Dr
Lewisburg, Tn 37091
520-247-4032

Runways

Runways: 09/27

Runway 09/27

Length: 970 feet
by Owner on 11/04/2010
Width: 50 feet
Surface: Grass / Sod, Good Condition
End 09 End 27
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:   100' AGL
Object Distance:   50' 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.