3IN5
Airport
Pippenger
Albion, 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:3IN5 (Three-India-November-Five)
Lat/Lng: 41.3169444444, -85.3713888889
41-19-01.0000N, 085-22-17.0000W
Estimated by OWNER on 09/11/2002
Elevation: 980 feet Estimated by OWNER on 09/11/2002
Magnetic Variation: 04W, (2000), [-6W (2014)]
Sectional: CHICAGO
From City: 5nm SE of Albion

Operations

Use: Private
Airspace Analysis: CONDITIONAL
Provided Clear 20:1 Approach and Clear Obstacle Free Zone.
Ownership: Privately owned
Activation: 11/2002
Control Tower: no
ARTCC: Chicago Center (ZAU)
FSS: Terre Haute FSS (HUF)
Wind Indicator: Lighted
Landing Fee: no

Communications

Services

Based Aircraft

Single Engine GA: 1
Total: 1

Annual Operations

Total: 0

Ownership

Owner: Jason Pippenger
2689 S 300 E
Albion, in 46701
260-693-3145
Manager: Jason Pippenger
2689 S 300 E
Albion, in 46701
260-693-3145

Runways

Runways: 16/34

Runway 16/34

Length: 1300 feet
by Owner on 09/11/2002
Width: 75 feet
Surface: Grass / Sod
End 16 End 34
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach

Procedures

NOTAMs

Additional Remarks

Tower 2.5 NM West of Airport.

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.