MY44
Heliport
Rice Memorial Hospital
Willmar, Minnesota

FAA NFDC Information Effective 56-day cycle 09/18/2014 - 11/13/2014

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:MY44
Lat/Lng: 45.1200833333, -95.0465833333
45-07-12.3000N, 095-02-47.7000W
Estimated by OWNER on 03/25/2005
Elevation: 1179 feet Estimated by OWNER on 03/25/2005
Magnetic Variation: [2E (2014)]
Sectional: TWIN CITIES
From City: in Willmar

Operations

Use: Private
Airspace Analysis: CONDITIONAL
Provided Approach/Departure Fr 350 to 360 Deg & 170 T0 180 Deg; Area is Marked; Hel Stay Below Ill Airport's TPA; All Operations Must Coordinate with Ill Airport Authority.
Ownership: Privately owned
Activation: 05/2006
Control Tower: no
ARTCC: Minneapolis Center (ZMP)
FSS: Princeton FSS (PNM)
Wind Indicator: Lighted
Lights: for Rotating Beacon and Perimeter Lights Call 320-235-4543.
Beacon: Clear-Green-Yellow (Heliport)
Landing Fee: no

Communications

Services

Based Aircraft

Total: 0

Annual Operations

Total: 0

Ownership

Owner: Rice Memorial Hospital
301 Becker Ave SW
Willmar, Mn 56201
320-235-4543
Manager: Jon Hilleren
301 Becker Ave SW
Willmar, Mn 56201
320-231-4723

Runways

Runways: H1

Runway H1

Length: 45 feet
by Owner on 03/25/2005
Width: 45 feet
Surface: Aluminum
Runway Lights Edge Intensity: Perimeter
Flood Lights.

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.