37VA
Heliport
St Mary's Hospital
Richmond, Virginia

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:37VA
Lat/Lng:37.5824, -77.5136
37-34-56.6400N, 077-30-48.9600W
Estimated by Faa-Est Imagery on 04/05/2016
Elevation:263 feet Estimated by Owner on 02/01/2008
Magnetic Variation: [-10W (2024)]
Sectional:WASHINGTON
From City:17nm W of Richmond

Operations

Use:Private
Airspace Analysis:CONDITIONAL
Provided Pvt Use & VFR Operations only; Takeoff/Landing Area Marked; Wind Indicator Maintained; Per FSS Office, Remove Two Light Poles, Trees, and Bushes; Place Large Balls on Wires Bordering Chase St.
Ownership:Privately owned
Activation:05/2009
Attended:Continuous
Control Tower:no
ARTCC:Washington(ZDC)Washington Center
FSS:Leesburg FSS(DCA)
Wind Indicator:Unlighted
Landing Fee:no

Communications

Services

Based Aircraft

Total:0

Annual Operations

For year ending:03/01/2008
Total:0

Ownership

Owner:Bon Secours Richmond Health System
5801 Bremo Rd
Richmond, Va 23226
804-287-7833
Manager:Michael Ortega
5801 Bremo Rd
Richmond, Va 23226
(804) 281-8594

Runways

Runways:H1

Runway H1

Length:40 feet
by Owner on 02/01/2008
Width:40 feet
Surface:Asphalt / Bituminous Concrete
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 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.