66IN
Airport
Oakes Field
Charlottesville, Indiana

FAA NFDC Information Effective 56-day cycle 03/21/2024 - 5/16/2024

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:66IN (Six-Six-India-November)
Lat/Lng:39.7875, -85.6369444444
39-47-15.0000N, 085-38-13.0000W
Estimated
Elevation:935 feet Estimated
Magnetic Variation:03W,(1995), [-6W (2024)]
Sectional:ST LOUIS
From City:1nm W of Charlottesville

Operations

Use:Private
Airspace Analysis:CONDITIONAL
Provided 20:1 Approach Slope; Clear Area 125 ft Both Sides of Centerline & 240 ft Off Both Runway Ends.
Ownership:Privately owned
Activation:02/1998
Attended:Continuous
Control Tower:no
ARTCC:Indianapolis(ZID)Indianapolis Center
FSS:Terre Haute FSS(HUF)
Wind Indicator:Lighted
Landing Fee:no

Communications

Services

Based Aircraft

Total:0

Annual Operations

Total:0

Ownership

Owner:David W. Oakes
8933 East Highway 40
Greenfield, in 46140
(317) 498-4296
Manager:David W. Oakes
8933 East Highway 40
Greenfield, in 46140
317-936-5500

Runways

Runways:18/36

Runway 18/36

Length:1025 feet
Width:75 feet
Surface:Grass / Sod, Good Condition
Surface Treatment:NONE
End 18 End 36
Objects affecting Navigable Airspace (CFR part 77):Utility runway with a visual approachUtility runway with a visual approach

Procedures

NOTAMs

Additional Remarks

for Cd Contact Indianapolis Approach at 317-227-5743.

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.