TN31
Heliport
Cookeville Regional Medical Center
Cookeville, 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:TN31 (Tango-November-Three-One)
Lat/Lng: 36.1694277778, -85.5074833333
36-10-09.9400N, 085-30-26.9400W
Estimated by FAA-EST IMAGERY on 04/01/2011
Elevation: 1126 feet Estimated by OWNER on 04/01/2011
Magnetic Variation: 01W, (1985), [-4W (2014)]
Sectional: MEMPHIS
From City: in Cookeville

Operations

Use: Private
Medical Use.
Airspace Analysis: CONDITIONAL
VFR Pvt Use; App/Departure Routes be on the 80 Deg Rad; Area is Marked; Wind Indic is Maintained; No Night Operations.
Ownership: Privately owned
Activation: 11/1989
Attended: Continuous
Control Tower: no
ARTCC: Memphis Center (ZME)
FSS: Nashville FSS (BNA)
NOTAMs and Weather: FDC
Wind Indicator: Unlighted
Landing Fee: no

Communications

Services

Based Aircraft

Total: 0

Annual Operations

Total: 0

Ownership

Owner: Cookeville Regional Medical Center
1 Medical Center Blvd.
Cookeville, Tn 38501
931-528-2541
Manager: Joe Iwanyszyn
1 Medical Center Blvd.
Cookeville, Tn 38501
931-528-2541
Ext 2588

Runways

Runways: H1

Runway H1

Length: 40 feet
Width: 40 feet
Surface: Porland Cement Concrete
Runway Lights Edge Intensity: Perimeter

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.