UT95
Heliport
St. Mark's Hospital
Millcreek, Utah

FAA NFDC Information 28-day cycle

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:UT95
Lat/Lng:40.68630833333333, -111.85659444444444
40-41-10.7100N, 111-51-23.7400W
Estimated by Ado on 01/23/2024
Elevation:4498 feet Estimated by Ado on 01/23/2024
Magnetic Variation: [11E (2025)]
Sectional:SALT LAKE CITY
From City:1nm E of Millcreek

Operations

Use:Private
Airspace Analysis:for Design and Operation of This Facility, Refer to Asn: 2022-Anm-4158-Nra and Reference FAA Advisory Circular (Ac) 150/5390-2, Heliport Design (Current Version) and the Recommendations in Flight Standards' Evaluation for This Heliport.
Ownership:Privately owned
Activation:01/2024
Control Tower:no
ARTCC:Salt Lake City(ZLC)Salt Lake City Center
FSS:Cedar City FSS(CDC)
Wind Indicator:Lighted
Lights:Sunset-Sunrise
Beacon:None
Landing Fee:no

Communications

Services

Ownership

Owner:St. Mark's Hospital
1200 E 3900 S
Millcreek, Ut 84124
801-268-7111
Manager:St. Mark's Hospital
1200 E 3900 S
Millcreek, Ut 84124
801-268-7111

Runways

Runways:H1

Runway H1

Length:50 feet
by Ado on 01/23/2024
Width:50 feet
Surface:Pierced Steel Planking / Landing Mats / Membranes, Fair Condition
Surface Treatment:NONE
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 Chart Supplment (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.

rgrep