NC72
Airport
Hinton Field
Princeton, 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:NC72
Lat/Lng: 35.45155, -78.1599938889
35-27-05.5800N, 078-09-35.9780W
Estimated
Elevation: 152 feet Estimated
Magnetic Variation: 07W, (1985), [-9W (2014)]
Sectional: CHARLOTTE
From City: 1nm SE of Princeton

Operations

Use: Private
Airspace Analysis: Provided VFR/Pvt Use; and Extreme Caution is Used Because of Numerous Powerlines & Low-Level Military Training Routes in Immediate Vicinity.
Ownership: Privately owned
Activation: 04/1989
Control Tower: no
ARTCC: Washington Center (ZDC)
FSS: Raleigh FSS (RDU)
Wind Indicator: Lighted
Beacon: for Rotating Beacon Call 919-936-2261.
Clear-Green (Lighted Land Airport)
Landing Fee: no

Communications

Services

Based Aircraft

Total: 0

Annual Operations

Total: 0

Ownership

Owner: Jim Hinton
Send All Mail to the Airport Manager.
960 Old Hinton Road
Princeton, Nc 27569-8717
919-936-3501
Manager: Ken Starling
106 Iris Drive
Princeton, Nc 27569
919-936-2261

Runways

Runways: 05/23

Runway 05/23

Length: 2000 feet
Width: 35 feet
Surface: Grass / Sod
End 05 End 23
Objects:   Road
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height:   12' AGL
Object Distance:   20' 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.