IFR Enroute Charts
at skyvector.com Click on airport for details, drag to scroll around. Zoom using +/- keys. |
|
FAA NFDC Information 28-day cycle
Ops | Comms | Services | Owner | Runways | IFR Procs | Current NOTAMs | Remarks |
FAA Identifier: | IN43 (India-November-Four-Three) |
---|---|
Lat/Lng: | 38.47506083333334, -85.997195 38-28-30.2190N, 085-59-49.9020W Estimated |
Elevation: | 830 feet Estimated |
Magnetic Variation: | 02W,(1985), [-5W (2025)] |
Sectional: | ST LOUIS |
From City: | 2nm SE of Pekin |
Use: | Private |
---|---|
Airspace Analysis: | CONDITIONAL Provided Any Obstruction in Runway Approach Slope Removed/Lowered or Threshold Displaced to Provide 20:1 Approach Clearance Over Obstruction. |
Ownership: | Privately owned |
Activation: | 11/1990 |
Control Tower: | no |
ARTCC: | Indianapolis(ZID)Indianapolis Center |
FSS: | Terre Haute FSS(HUF) |
Wind Indicator: | None |
Beacon: | None |
Landing Fee: | no |
Owner: | Ann G. Neel 8556 South Voyles Rd. Pekin, in 47165 502-396-3033 |
---|---|
Manager: | Ron & Lori Russell 8950 South Voyels Rd. Pekin, in 47165 (309) 967 4624 |
Runways: | 01/19 |
---|
Length: | 1000 feet |
---|---|
Width: | 60 feet |
Surface: | Grass / Sod |
Surface Treatment: | NONE |
End 01 | End 19 | |
---|---|---|
Objects: | 60' Trees on the 19 Approach on Property to North. | Fence |
Object Height: | 5' AGL | |
Object Distance: | 300' Along centerline |
• | for Cd Contact Louisville Approach at 502-375-7499 |
---|
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 Chart Supplment (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.
rgrep