32AR
Heliport
Stuttgart Meml Hospital
Stuttgart, Arkansas

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:32AR
Lat/Lng:34.5177777778, -91.5597222222
34-31-04.0000N, 091-33-35.0000W
Estimated by Owner on 10/19/2007
Elevation:193 feet Estimated by Owner on 10/19/2007
Magnetic Variation:03E,(1985), [-1W (2024)]
Sectional:MEMPHIS
From City: in Stuttgart

Operations

Use:Private
Medical.
Airspace Analysis:CONDITIONAL
Provided Ingress/Egress Routes are from/to the West only and Procedure Established to Restrict Pedestrian Access to Landing Area During Helicopter Operations.
Ownership:Privately owned
Activation:05/1989
Control Tower:no
ARTCC:Memphis(ZME)Memphis Center
FSS:Jonesboro FSS(JBR)
Wind Indicator:Lighted
Lights:for Perimeter Lights Call 870-673-3511.
Landing Fee:no

Communications

Services

Based Aircraft

Total:0

Annual Operations

Total:0

Ownership

Owner:Stuttgart Meml Hosp Assn. Inc
1703 North Buerklo Rd
Stuttgart, Ar 72160
(870) 673-3511
Manager:Kevin Storey
1703 North Buerklo Rd
Stuttgart, Ar 72160
870-673-3511

Runways

Runways:H1

Runway H1

Length:40 feet
by Faa-Est Imagery on 10/14/2015
Width:40 feet
Surface:Porland Cement Concrete
Surface Treatment:NONE
Runway Lights Edge Intensity:Perimeter

Procedures

NOTAMs

Additional Remarks

for Cd Contact Little Rock Approach 501-379-2908 or Little Rock Air Traffic Control Tower 501-379-2911.

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.