2IN9
Airport
Berry Field
New Whiteland, Indiana

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:2IN9 (Two-India-November-Nine)
Lat/Lng: 39.5666666667, -86.1180555556
39-34-00.0000N, 086-07-05.0000W
Estimated
Elevation: 795 feet Estimated
Magnetic Variation: 03W, (1995), [-5W (2014)]
Sectional: ST LOUIS
From City: 1nm W of New Whiteland

Operations

Use: Private
Airspace Analysis: CONDITIONAL
Provided Clear 125 Ft Either Side of Runway Centerline; Obstns Removed/Lowered to Provide 20:1 Clearance; Area Around Runway Cleared & Graded.
Ownership: Privately owned
Activation: 02/1998
Control Tower: no
ARTCC: Indianapolis Center (ZID)
FSS: Terre Haute FSS (HUF)
Wind Indicator: Unlighted
Landing Fee: no

Communications

Services

Based Aircraft

Single Engine GA: 1
Total: 1

Annual Operations

Total: 0

Ownership

Owner: Mark H. Berry
6208 N. 75 W.
Whiteland, in 46184
317-345-6261
Manager: Mark H. Berry
6208 N. 75 W.
Whiteland, in 46184
317-345-6261

Runways

Runways: 10/28

Runway 10/28

Length: 1300 feet
Width: 50 feet
Surface: Grass / Sod
End 10 End 28
Right Hand Pattern:   Yes
Objects: Trees Bldg
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height: 50' AGL 25' AGL
Object Distance: 600' Along centerline 1700' 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.