53NR
Airport
Barker Private Stol
Asheville, North Carolina

FAA NFDC Information 28-day cycle

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:53NR
Lat/Lng:35.647490499999996, -82.66896
35-38-50.9658N, 082-40-08.2560W
Estimated by Ado on 11/20/2024
Elevation:2150 feet Estimated by Ado on 11/20/2024
Magnetic Variation: [-7W (2025)]
Sectional:ATLANTA
From City:7nm NW of Asheville

Operations

Use:Private
Airspace Analysis:CONDITIONAL
Ownership:Privately owned
Activation:06/2024
Control Tower:no
ARTCC:Atlanta(ZTL)Atlanta Center
FSS:Raleigh FSS(RDU)
Wind Indicator:Lighted
Beacon:None
Landing Fee:no

Communications

CTAF:122.900

Services

Ownership

Owner:Kevin Barker
1155 Old Leicester Hwy
Asheville, Nc 28806
919-610-8811
Manager:Kevin Barker
1155 Old Leicester Hwy
Asheville, Nc 28806
919-610-8811

Runways

Runways:17/35

Runway 17/35

Length:602 feet
by Ado on 11/20/2024
Width:75 feet
Surface:Grass / Sod, Fair Condition
Surface Treatment:NONE
Runway Lights Edge Intensity:Non-standard Lighting System
End 17 End 35
Right Hand Pattern:YesYes
Runway Markings:NoneNone
Elevation at End:2150.0' MSL2150.0' MSL
Objects affecting Navigable Airspace (CFR part 77):Utility runway with a visual approachUtility runway with a visual approach

Procedures

NOTAMs

Additional Remarks

VFR Operations.

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 Chart Supplment (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.

rgrep