| IN65
Airport
|
Wolfe Field
|
|
Shipshewana, Indiana
|
|
|
|
FAA NFDC Information Effective 56-day cycle 05/02/2013 - 6/27/2013
| FAA Identifier: | IN65 (India-November-Six-Five) |
| Lat/Lng: |
41.6914391667, -85.5955416667
41-41-29.1810N, 085-35-43.9500W
Estimated
|
| Elevation: |
896 feet
Surveyed
|
| Magnetic Variation: |
03W,
(1985),
[-5W (2013)]
|
| Sectional: |
CHICAGO
|
| From City: |
1nm
NW of Shipshewana
|
| Use: |
Private
|
| Ownership: |
Privately owned
|
| Activation: |
11/1960
|
| Attended: |
Ireg Ireg IRREG (local)
|
| Control Tower: |
no
|
| ARTCC: |
Chicago Center
(ZAU)
|
| FSS: |
Terre Haute FSS
(HUF)
|
| Wind Indicator: |
Unlighted
|
| Landing Fee: |
no
|
| Airframe Repair: |
None
|
| Powerplant Repair: |
None
|
| Bottled Oxygen: |
None
|
| Bulk Oxygen: |
None
|
| Transient Storage: |
Hanger
|
| Single Engine GA: |
5
|
| Total: |
5
|
|
| Local GA (< 20 miles): |
1500
|
| Non-local GA: |
50
|
| Total: |
1550
|
|
| Owner: |
Shipshewana Air Assoc
Shipshewana, in 46565
|
| Manager: |
Ralph Lutes
8845W 350N
Shipshewana, in 46565
260-768-4058
|
|
Runway 09/27
| Length: |
2600 feet
|
| Width: |
200 feet
|
| Surface: |
Grass / Sod
|
|
End 09 |
End 27 |
| Objects: |
Road
|
Road
|
| Object Clearance Slope: |
0:1
|
0:1
|
| Object Distance: |
0' Along centerline
|
0' Along centerline
|
| • | Heavy Agricultureal Aircraft Activity may Through October. |
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.