NC48
Airport
Safe Field
Wallace, North Carolina

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:NC48
Lat/Lng:34.7501083333, -78.0615194444
34-45-00.3900N, 078-03-41.4700W
Estimated
Elevation:50 feet Estimated
Magnetic Variation:07W,(1985), [-10W (2024)]
Sectional:CHARLOTTE
From City:3nm NW of Wallace

Operations

Use:Private
Airspace Analysis:CONDITIONAL
VFR/Pvt Use only; Traffic Patterns Remain West of Runway.
Ownership:Privately owned
Activation:11/1989
Control Tower:no
ARTCC:Washington(ZDC)Washington Center
FSS:Raleigh FSS(RDU)
Wind Indicator:None
Landing Fee:no

Communications

Services

Based Aircraft

Total:0

Annual Operations

Total:0

Ownership

Owner:Carolyn M. Colwell
6990 S Nc 41
Wallace, Nc 28466
910-285-5679
910-289-5148 Cell
Manager:Carolyn M. Colwell
6990 S Nc 41
Wallace, Nc 28466
910-285-5679
910-289-5148 Cell

Runways

Runways:10/28

Runway 10/28

Length:3000 feet
Width:70 feet
Surface:Grass / Sod
Surface Treatment:NONE
End 10 End 28
Objects: Powerline
Objects affecting Navigable Airspace (CFR part 77):Utility runway with a visual approachUtility runway with a visual approach
Object Height: 30' AGL
Object Distance: 200' Along centerline

Procedures

NOTAMs

Additional Remarks

for Cd Contact Washington ARTCC at 703-771-3587.

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.