Hannah Rhea Field
Walterboro, South Carolina

FAA NFDC Information Effective 56-day cycle 08/17/2017 - 10/12/2017

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks


FAA Identifier:29SC
Lat/Lng: 32.9006416667, -80.8521194444
32-54-02.3100N, 080-51-07.6300W
Estimated by OWNER on 04/15/2003
Elevation: 89 feet Estimated by OWNER on 04/15/2003
Magnetic Variation: [-7W (2017)]
Sectional: CHARLOTTE
From City: 9nm W of Walterboro


Use: Private
Airspace Analysis: CONDITIONAL
Pvdd VFR, Pvt.
Ownership: Privately owned
Activation: 09/2003
Control Tower: no
ARTCC: Jacksonville (ZJX) Atlanta Center (ZTL)
FSS: Anderson FSS (AND)
Wind Indicator: Lighted
Landing Fee: no



Based Aircraft

Single Engine GA: 1
Total: 1

Annual Operations

For year ending: 04/01/2003
Total: 0


Owner: Benjamin Lee Givens
2953 Cane Branch Road
Walterboro, Sc 29488
Manager: Benjamin Lee Givens
2953 Cane Branch Road
Walterboro, Sc 29488


Runways: 18/36

Runway 18/36

Length: 1800 feet
by Owner on 04/15/2003
Width: 70 feet
Surface: Grass / Sod
End 18 End 36
Displaced Threshold Distance: 300'
Displaced Threshold Runway 18 Marked with Orange Cones.
Objects: Road  
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height: 15' AGL  
Object Distance: 50' Along centerline  



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.