UT35
Heliport
Mountain View Hospital
Payson, Utah

FAA NFDC Information Effective 56-day cycle 04/18/2024 - 6/13/2024

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:UT35
Lat/Lng:40.0442916667, -111.715397222
40-02-39.4500N, 111-42-55.4300W
Estimated by Faa-Est Imagery on 07/08/2016
Elevation:4597 feet Estimated
Magnetic Variation:14E,(1990), [11E (2024)]
Sectional:SALT LAKE CITY
From City:2nm E of Payson

Operations

Use:Private
Medical.
Airspace Analysis:CONDITIONAL
Provided Approach/Departure Routes are only from Threshold North, West, and Southwest.
Ownership:Privately owned
Activation:01/1992
Control Tower:no
ARTCC:Salt Lake City(ZLC)Salt Lake City Center
FSS:Cedar City FSS(CDC)
Wind Indicator:Unlighted
Lights:for Perimeter Lights Call 801-465-7000.
Landing Fee:no

Communications

Services

Based Aircraft

Total:0

Annual Operations

Total:0

Ownership

Owner:Mountain View Hospital, Inc.
1000 East Hwy 6
Payson, Ut 84651
801-465-7104
Manager:Richard Brunson
Additional Contact: ASHLEY.SHEPHERD@MOUNTAINSTARHEALTH.COM
1000 East Hwy 6
Payson, Ut 84651
801-485-7104

Runways

Runways:H1

Runway H1

Length:60 feet
Width:60 feet
Surface:Porland Cement Concrete
Surface Treatment:NONE
Runway Lights Edge Intensity:Perimeter

Procedures

NOTAMs

Additional Remarks

for Cd Contact Salt Lake City Approach at 801-325-9670.

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.