| MN16
Heliport
|
Virginia Regional Hospital
|
|
Virginia, Minnesota
|
|
|
|
FAA NFDC Information Effective 56-day cycle 05/02/2013 - 6/27/2013
| FAA Identifier: | MN16 (Mike-November-One-Six) |
| Lat/Lng: |
47.5313888889, -92.5480555556
47-31-53.0000N, 092-32-53.0000W
Estimated by OWNER on 12/09/2007
|
| Elevation: |
1550 feet
Estimated
by OWNER
on 12/09/2007
|
| Magnetic Variation: |
[-1W (2013)]
|
| Sectional: |
GREEN BAY
|
| From City: |
in Virginia
|
| Use: |
Private
|
| Airspace Analysis: |
CONDITIONAL
All Approach Helicopter Operations in An Area from 306Deg Clockwise to 242 Deg Using the Touchdown Pad As the Center of the Compass Rose; Landing Area Marked; & Hospitalsecurity Procedures During Helicopter Operations are Written & Trained As to Restrain Unauthorised Persons from Access to the Takeoff/Landing Area.
|
| Ownership: |
Privately owned
|
| Activation: |
09/2007
|
| Control Tower: |
no
|
| ARTCC: |
Minneapolis
(ZMP)
Minneapolis Center
(ZMP)
|
| FSS: |
Princeton FSS
(PNM)
|
| Wind Indicator: |
Lighted
|
| Landing Fee: |
no
|
|
|
|
| Owner: |
Virginia Regional Hospital
901 N 9Th St
Virginia, Mn 55792
218-741-3340
|
| Manager: |
Rich Weiss
901 N 9Th St
Virginia, Mn 55792
218-749-9493
|
|
Runway H1
| Length: |
50 feet
|
| Width: |
50 feet
|
| Surface: |
Pierced Steel Planking / Landing Mats / Membranes
|
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.