NC83
Heliport
Cape Fear Valley Medical Center
Fayetteville, North Carolina

FAA NFDC Information Effective 56-day cycle 04/03/2014 - 5/29/2014

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:NC83
Lat/Lng: 35.0334969444, -78.9372494444
35-02-00.5890N, 078-56-14.0980W
Estimated
Elevation: 213 feet Estimated
Magnetic Variation: 07W, (1985), [-9W (2014)]
Sectional: CHARLOTTE
From City: 3nm SW of Fayetteville

Operations

Use: Private
Medical.
Airspace Analysis: CONDITIONAL
Operations Limited to VFR Wx Conditions; Landing Area Limited to Private Use; Use of Heliport Coordinated with General Aviation District Office Raleigh Nc.
Ownership: Privately owned
Activation: 02/1979
Control Tower: no
ARTCC: Washington Center (ZDC)
FSS: Raleigh FSS (RDU)
Wind Indicator: Unlighted
Beacon: Sunset-Sunrise (local time)
Clear (Unlighted Land Airport)
Landing Fee: no

Communications

UNICOM: Multicom 122.05 Available.

Services

Based Aircraft

Total: 0

Annual Operations

Total: 0

Ownership

Owner: Cape Fear Valley Medical Center
Po Box 2000
Fayetteville, Nc 28302
910-323-6151
Manager: Kevin Jackson
1638 Owen Drive
Fayetteville, Nc 28304
910-609-6700

Runways

Runways: H1

Runway H1

Length: 90 feet
Width: 90 feet
Surface: Porland Cement Concrete
Runway Lights Edge Intensity: Perimeter 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.