10GA
Airport
Beaverbrook Aerodrome
Griffin, Georgia

FAA NFDC Information Effective 56-day cycle 11/13/2014 - 1/8/2015

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:10GA (One-Zero-Golf-Alpha)
Lat/Lng: 33.3251138889, -84.2982566667
33-19-30.4100N, 084-17-53.7240W
Estimated
Elevation: 910 feet Estimated
Magnetic Variation: 02W, (1985), [-5W (2014)]
Sectional: ATLANTA
From City: 5nm N of Griffin

Operations

Use: Private
Airspace Analysis: CONDITIONAL
All Operations Conducted in VFR. Landing Area is Limited to Pvt Use. All Traffic Pats are Estabd on the NE Side of the Runway.
Ownership: Privately owned
Activation: 01/1978
Attended: All year Mon-Sat 0800-DUSK (local)
Control Tower: no
ARTCC: Atlanta Center (ZTL)
FSS: Macon FSS (MCN)
Wind Indicator: Unlighted
Landing Fee: no

Communications

Services

Based Aircraft

Single Engine GA: 7
Total: 7

Annual Operations

Total: 0

Ownership

Owner: Gerald N. Bailey
262 Mobley Road
Griffin, Ga 30223
404-229-4461
Manager: Gerald N. Bailey
262 Mobley Road
Griffin, Ga 30223
404-229-4461

Runways

Runways: 15/33

Runway 15/33

Length: 2100 feet
Width: 150 feet
Surface: Grass / Sod, Good Condition
End 15 End 33
Right Hand Pattern:   Yes
Objects:   Powerline
Object Height:   20' AGL
Object Distance:   500' Along centerline

Procedures

NOTAMs

Additional Remarks

(A52) Pole

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.