66GA
Airport
Sawyer Farm
Blakely, Georgia

FAA NFDC Information Effective 56-day cycle 07/24/2014 - 9/18/2014

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:66GA
Lat/Lng: 31.4747222222, -85.0027777778
31-28-29.0000N, 085-00-10.0000W
Estimated by OWNER on 10/08/2008
Elevation: 350 feet Estimated by OWNER on 10/08/2008
Magnetic Variation: [-4W (2014)]
Sectional: NEW ORLEANS
From City: 7nm NW of Blakely

Operations

Use: Private
Airspace Analysis: CONDITIONAL
Provided VFR Operations and Pvt Use only.
Ownership: Privately owned
Activation: 07/2009
Control Tower: no
ARTCC: Jacksonville (ZJX) Jacksonville Center (ZJX)
FSS: Macon FSS (MCN)
Wind Indicator: Unlighted
Landing Fee: no

Communications

Services

Based Aircraft

Single Engine GA: 1
Total: 1

Annual Operations

For year ending: 07/02/2008
Total: 0

Ownership

Owner: Fred Sawyer
61 Sawyer Rd
Blakely, Ga 39823
229-723-3813
Manager: Fred Sawyer
61 Sawyer Rd
Blakely, Ga 39823
229-723-3813

Runways

Runways: 09/27

Runway 09/27

Length: 1700 feet
by Owner on 10/08/2008
Width: 60 feet
Surface: Grass / Sod
End 09 End 27
Objects:   Trees
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height:   40' 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.