38NC
Airport
Bhh Aviation
Ruffin, North Carolina

FAA NFDC Information Effective 56-day cycle 09/18/2014 - 11/13/2014

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:38NC
Lat/Lng: 36.4760149444, -79.5954322778
36-28-33.6538N, 079-35-43.5562W
Estimated by OWNER on 09/08/2011
Elevation: 608 feet Estimated by OWNER on 09/08/2011
Magnetic Variation: [-9W (2014)]
Sectional: CINCINNATI
From City: 3nm NW of Ruffin

Operations

Use: Private
Airspace Analysis: Provided VFR Operations and Pvt Use only.
Ownership: Privately owned
Activation: 12/2012
Control Tower: no
ARTCC: Washington Center (ZDC)
FSS: Raleigh FSS (RDU)
Wind Indicator: Unlighted
Landing Fee: no

Communications

Services

Based Aircraft

Single Engine GA: 1
Total: 1

Annual Operations

Total: 0

Ownership

Owner: Brent H. Huss
181 Crownover Rd
Ruffin, Nc 27326
336-939-3131
Manager: Brent H. Huss
181 Crownover Rd
Ruffin, Nc 27326
336-939-3131

Runways

Runways: 16/34

Runway 16/34

Length: 1700 feet
by Owner on 09/08/2011
Width: 50 feet
Surface: Grass / Sod, Good Condition
End 16 End 34
Objects: Tree Tree
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height: 30' AGL 50' AGL
Object Distance: 50' Along centerline 300' Along centerline

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.