KIND - Indianapolis International Airport Ariman's Information Publication
Airman's Information Publication (AIP): Indianapolis International (KIND)
In the northwestern corner of Indianapolis ARTCC's (ZID's) airspace, lies Indianapolis International (KIND). KIND is currently the second-busiest airport in the ARTCC (behind KCVG), both in the real world and in the virtual world (vZID). Not only is KIND a common arrival and departure airport for those going to anywhere inside Indiana, KIND is also one of the lower-cost alternatives within driving distance of Cincinnati and its major airport, Cincinnati/Northern Kentucky International (KCVG). Beyond the normal commercial passenger traffic, KIND is a hub location for Federal Express (FedEx), as well as a major location for Hawker Beechcraft, servicing the general aviation (GA) world.
Although not a class-B airport, KIND has enough going on to warrant a fair number of routes, notes, and procedures. This AIP provides one location for all of the general information that a pilot will need when deciding to fly in to, or out from, KIND. This AIP, combined with the KIND page on AirNav, and the sectional and enroute charts from SkyVector, will give you all of the inforamtion required to complete a safe and successful flight!
This document begins by discussing some common scenery problems, so you see the same thing as everyone else. Next up is a description of the various parking locations available, so you can start (or end) your flight in the same place as the real-world pilots. At this point, you should have enough information to find a good starting point on the ground, so the next section covers the list of ATC positions commonly staffed at this airport. Some quick notes about the airspace are provided for VFR pilots, followed by a list of common runway configurations. This AIP ends with a list of nearby airports, and the preferred routes, for both directions, between those airports and KIND.
KIND, with its extreme proximity to the City of Indianapolis, Indianapolis Motor Speedway ("the Brickyard"), the NCAA Hall of Champions, and easy access to nearby universities (many of which have small airports), untold miles of countryside, and (if absolutely necessary) Chicago, can make for a nice flying experience, as long as you have a good scenery package. If your scenery does not match what the controller (and other pilots) are using, you may be causing them untold amounts of pain; what you think is a parking spot may be, in reality, an active runway (and with Indianapolis, this may easily be true!). Although there are small differences between sceneries, and controllers have come to expect and compensate for this, you should avoid sceneries that deviate extensively from other scenery packages and the contoller's sector file (which controls what they see on their radar screen).
At this time, there is least one problematic scenery package, although it is not known exactly which scenery package has problems. Pilots with this problematic scenery report being parked at a gate at the terminal, when they are actually sitting either on runway 14/32, or on taxiway MIKE. In the former case, this makes runway 14/32 unavailable for active use; in the latter case, aircraft may be able to enter/leave certain parts of the terminal. In the case of heavy traffic, or during an event, if use are using this problematic scenery, you may be asked to disconnect shortly after reaching your parking place, to allow other pilots to proceed.
The following issues have been reported so far:
- One issue affects many pilots of Level D planes flying the DAWNN SID: During the radar-vector section, while attempting to intercept the VOR radial specified in the SID, when LNAV mode is activated the plane may begin to execute unexpected turns. The workaround is to either hand-fly the plane to a point where the FMS can properly pick up the flight plan, or to request direct routing to the SID transition point. This issue may also affect the ROCKY SID, which also involves radar vectors.
- The Level D STAR issue described above also applies to pilots of PMDG aircraft, but in their case there is a solution: Replace the default SID/STAR data with a third-party version, maintained by Dan Downs. When this paragraph was written, the latest release was available to download on AVSIM for AIRAC cycle 0811. Later releases may be found in the Flight Simulator 2004 - Flight Plans section of the AVSIM Library.
KIND New Terminal Notes
On 12 November, 2008, KIND completed the opening of their new terminal. All commercial aircraft was moved from the old terminal, now known as the northeast ramp, to the new terminal. On 8 November 2008, as part of an event celebrating the occasion, vZID initiated control of operations at the new terminal, and associated taxiways.
At this time, although there is pilot scenery released for the new terminal, vZID controllers have only partial diagrams for the following areas:
- The entire new terminal, and associated ramp.
- Taxiway BRAVO south of B-2 (taxiways B-1, B-2, PAPA, and the part of BRAVO that connects to them is OK)
- Taxiways B-5, B-7, B-11, and B-12.
- Taxiways TANGO, SIERRA, ECHO, KILO, and UNIFORM.
- Taxiway ROMEO between taxiways HOTEL and CHARLIE (the section of ROMEO from HOTEL to runway 5L/23R is OK)
Although vZID controllers currently have incomplete information, they will continue to provide services to pilots looking to taxi in the areas listed above, and pilots should not hesitate to request taxi to the new terminal.
Real-world KIND has facilities for all aircraft, and on VATSIM vZID maintains this. Since KIND accepts all types of aircraft, there is a real-world parking location for everyone; it would be helpful if you used them!
All commercial passenger air carriers park at the new terminal building. The new terminal building, located between taxiways BRAVO, ROMEO, and CHARLIE, has two concourses (A and B). Concourse A is located on the south side of the new terminal building (closest to runway 5R/23L), and Concourse B is located on the north side (closest to runway 5L/23R). Concourse A is used almost exclusively by Continental, Delta, and Northwest. Concourse B is shared by Air Canada, AirTran, American, Frontier, Midwest, Southwest, United, and US Airways. All incoming international flights, regardless of airline, park at gates A3 through A5, located closest to taxiway UNIFORM.
All commercial passenger air carriers who do not have scenery for the new terminal should park at the old terminal building, now known as the northeast ramp. The northeast ramp, located between taxiways HOTEL, MIKE, and M-2, had four Concourses (A through D), with Concourse A to the north, and Concourse D to the east. Northwest Airlines parked at Concourse A exclusively. Concourse B, the circular building south of Concourse A, was shared by American Airlines and Delta Airlines. Moving south-east, Concourse C was shared by AirTran, Cape Air, Continental, Frontier, Midwest, and Southwest. Finally, to the east, Concourse D was shared by Air Canada and US Airways. Parking for incoming international flights is described later in this section.
For cargo carriers, east of runway 5R/23L and south of runway 14/32, probably the biggest building on the field is the Federal Express (FedEx) building. This is the primary parking place for all FedEx flights. There is also a smaller cargo area off of taxiway GOLF, between the US Customs area and the Hawker Beechcraft area.
General aviation flights have four areas from which to choose. Hawker Beechcraft maintains a large presence on the field, with a number of buildings off of taxiway GOLF, west of the terminal building. Signature also has a presence on the field, off of taxiway MIKE, between taxiways M-2 and DELTA. General aviation can also park at the buildings located off of taxiway MIKE east of taxiway DELTA. Finally, there is a flight school and private hangars off of taxiway ALPHA, between A-1 and A-4.
For incoming international flights, if the pilot does not have scenery for the new terminal, flights should park by the US Customs building, located off of taxiway MIKE between taxiways ALPHA and M-1. For incoming international flights whose pilots have scenery for the new terminal, customs is located in the terminal building through gates A3, A4, and A5.
Finally, there are a few areas of the field that deserve special note. West of taxiway ALPHA, between A-5 and A-7, is an AAR maintenance, repair, and overhaul (MRO) building, providing services for large commercial passenger aircraft. FedEx has a dedicated maintenance hangar, located off of taxiway ALPHA just south of taxiway NOVEMBER. Finally, off of taxiway ALPHA between A-4 and A-5, there is a large building, with several smaller buildings. These used to form United States Postal Service hub; the building and associated ramp space now sits unused.
RAMP NOTE: Ground control does not normally include ramp control. After your clearance, you will typically be advised "PUSH AND START AT YOUR DISCRETION, CONTACT ME WHEN READY TO TAXI". However, in cases of heavy traffic, ground control will take over certain aspects of ramp control to prevent airplanes pushing out into each other.
GATE NOTE: Although the controllers know the location of the individual buildings, controllers do not know the location of specific gates. The controller will most likely ignore the gate portion of the request, instead providing instructions that will get you close enough to your destination to allow you to continue on your own.
TAXI NOTE: As required by FAA Notice N7110.482, if you are receiving taxi instructions from IND_APP, IND_TWR, or IND_GND, instead of receiving basic taxi instructions ("DELTA 123 TAXI TO THE GATE"), your taxi instructions will include the specific route to take ("DELTA 123 TAXI TO THE GATE VIA ALPHA MIKE HOTEL"). Please follow the instructions given by the controller. If you are unable, please say so, along with a request explaining why ("DELTA 123 UNABLE, NO AIRPORT DIAGRAM, REQUEST PROGRESSIVE TAXI").
The following positions serve KIND and are regularly-staffed:
The following positions serve KIND, but are not normally staffed:
TIME NOTE: When you are deciding to fly into or out of KIND, and you are checking to see who is online, be aware: As per vZID policy, any controller who signs on to a position must man said position for at least 1 hour, and must announce closing at least 10 minutes in advance.
KIND is a class-C field, whose airspace covers up to 4,800 feet MSL. The outermost ring of the airspace extends down to 2,100 feet. No SVFR flights are allowed at KIND.
Being a class-C field, you must establish communications with IND_APP (or IND_CTR if IND_APP is not online) before entry. If departing from KIND, you must establish communications with IND_TWR, or IND_APP if IND_TWR is offline, or (at least resort) IND_CTR.
The airspace covered by IND_APP bumps up against the approach airspace for Cincinnati (KCVG). If all of the approaches were staffed, and your crusing altitude was low enough, you could fly from Indianapolis to Cincinnati, and from there to Lousiville (KSDF) or Dayton (KDAY), entirely within approach control.
The airspace around KIND includes a number of areas that should be avoided by all pilots. Pilots are advised to fly safe by remaining on published VFR (V- and T-) and IFR (J- and Q-) routes. If you are on a published route, then you will always be kept clear of prohibited and restricted areas, and will be kept clear of most MOAs. Although restrictions on these areas may not be enforced by vZID, it is advised that you remain clear of the restricted airspace anyway. vZID ATC know where the restricted airsapce is located, and will be happy to vector you away from and around it.
MOA NOTE: Although it is not forbidden for civilian pilots to fly through MOAs, extreme caution must be taken when traversing them. Even if you are an IFR flight, or a VFR flight receiving flight following services, with or without TCAS, those services may still not be enough to keep you clear of all military traffic. The military use aircraft which are capable of rapid changes in speed, heading, and altitude, such that a controller-issued traffic alert or TCAS notification may come too late to be of any use. Pilots flying VFR through the area are advised to obtain flight following services, at least as long as you are in the MOA, to ensure you have some controller attention. It is also advised that you obtain the current usage status of the MOA from ATC well before entry, so that any reroutes may be planned and executed well before MOA entry.
To the south lie R-3401A and R-3401B, and MOAs, the RACER A, B, C, and D MOAs. R-3401A and R-3401B are bounded by V53 on the west, V221 on the north-west, and V128 on the north-east (there is no nearby route or other landmark for the southern boundary). At its extremes, the restricted area is in continuous use, covering surface to 40,000 feet.
The RACER C and D MOAs extended to the west and south of the restricted areas, but remain within the same route boundaries, and covering 500 ft AGL up to (but not including) FL180. The RACER A and B MOAs, however, extend far enough to the south and west as to overlap V53, but their extreme altitude boundaries are 500 ft AGL to 8000. These MOAs are active from 0700 (local time) to 2200 (again, at the extremes).
KIND determines the runways in use according to a Standard Operating Procedure (SOP) that accounts for both the winds and the time of day.
During the day, if winds permit, arrivals and departures take place on runways 23L and 23R. If the winds are strong enough, the runway most aligned with the winds will be used.
Noise Abatement / Contraflow Advisory
KIND sits on one of the corners of Indianapolis, with heavily-populated areas from the north to the east. This can be best seen using Google Maps . From this view, it seems like the only way to placate the masses is to have flights fly north-east into the airport, and south-west out of it. Can this be done? Like **** it can!
Between 2200 and 0700 local time, wind-permitting, all flights into KIND will land on runway 5R, while at the same time all flights out of KIND will depart runway 23R. This procedure is known as contraflow. When contraflow is active, and there is opposite-direction traffic, you will be advised by the tower controller ("DELTA ONE TWO THREE, COMPANY TRAFFIC ARRIVING, OPPOSITE DIRECTION ON PARALLEL RUNWAY"). If you end up in a situation where contraflow is active, and there is opposite-direction traffic, use excessive caution. Do not move into the path of the opposite-direction aircraft, either by turning into it, or by failing to correct for crosswind. Inbound aircraft will either be using the localizer, or will be on a visual approach, and will have a firm ground reference. As a departing aircraft, you will likely have no such reference. Remember to aviate, navigate, and then communicate!
Although, in driving times, KIND is at least an hour away from any other major airport, in flying times, KIND is located close to many major airports located just one ARTCC away. The best examples of this are Chicago and Atlanta, major airports located in neighboring ARTCCs. KIND is also located close to vZID's only class-B airport, KCVG. To maintain an orderly flow of traffic between these fields, vZID has negotiated agreements between the neighboring Centers, which include lists of preferred routings between KIND and airports in neighboring Centers.
Listed below are major airports, and the preferred routes to file when you are flying (in either direction) between KIND and the major airport. These routes will allow your flight to adhere to all applicable Letters of Agreement, as well as avoiding restricted areas. If your departure/arrival airport is not listed below, check the FAA Air Traffic Control System Command Center (ARCSCC) National Flight Data Center's (NFDC) Preferred Routes Database before creating a route of your own. You can get the current airport diagram; as well as the latest departure, arrival, and approach plates; for all U.S. airports from AirNav by clicking on the airport name. If an airport has a vZID AIP, or other source of consolidated information, a link will be provided.
- KATL - Atlanta Hartsfield :
To KATL: File the INDY2 departure to PXV, then fly direct BWG for the the ROME3 or ERLIN5 (RNAV) arrival.
To KIND: RNAV flights, file the SUMMT5 departure to VXV.
Non-RNAV flights, file the ATLANTA5 departure to NOTWO, joining J43/J91 to VXV.
From VXV take J99 to IIU for the DECEE arrival.
- KBNA - Nashville :
To KBNA: File the DAWNN3 departure to MYS, then direct CCT for the HEHAW5 arrival.
To KIND: File the TITAN1 to IIU for the DECEE3 arrival.
- KCMH - Port Columbus :
To KCMH: File the INDY2 departure to ROD for the GUNNE1 arrival.
To KIND: Request radar vectors to ROD for the CLANG5 arrival.
There are no SIDs available for KCMH.
- KCLE - Cleveland :
To KCLE: File the INDY2 departure to DQN for the ZABER1 arrival.
Specify a cruising altitude at or below FL250.
To KIND: File the OBRLN1 departure to ROD for the CLANG5 arrival.
- KCLT - Charlotte :
To KCLT: File the INDY2 departure to CVG, then direct FLM for the SHINE5 or JOHNS1 (RNAV) arrival.
To KIND: File the BOBCAT2 or HARAY4 (RNAV) departure to VXV, then via J99 to IIU for the DECEE3 arrival.
- KCVG - Cincinnati / Northern Kentucky International :
— KCVG has an AIP available from vZID.
To KCVG: Request radar vectors to SHB, for the SHELBYVILLE2 or CEGRM1 (RNAV) arrival.
To KIND: Request radar vectors to join V128, from CVG to VHP.
The initial approach fix for runway 32, OZMOE, is the last fix on V128 before VHP.
- KDAY - James M Cox Dayton International :
To KDAY: Request radar vectors to SHB, then take V12 to DQN.
To KIND: Request radar vectors to RID, then take V12 to SHB.
The initial approach fix for runway 32, OZMOE, can be reached by continuing to take V12 past SHB.
- KDCA - Reagan National :
To KDCA: File the DAWNN3 departure to IIU, then via J526 to BKW for the ELDEE4 (RNAV) arrival.
NOTE: The current LoA also makes the non-RNAV FINKS STAR available, but the FINKS STAR no longer exists. Non-RNAV pilots are advised to use the WZRRD2 STAR.
To KIND: There are no SIDs available for KDCA. Request radar vectors to BRV, then via J137 to GVE, then via J42 to BKW, then via J526 to IIU for the DECEE3 arrival.
- KDTW - Detroit Metro :
To KDTW: File the INDY2 departure to OKK, then direct FWA for the MIZAR3 arrival.
Specify a cruising altitude that is at or below FL250.
To KIND: File the ROSEWOOD2 departure to ROD for the CLANG5 arrival.
- KIAD - Washington Dulles :
To KIAD: File the DAWNN3 departure to IIU, then via J8/J78 to HVQ.
NOTE: The current LoA requires that pilots fly the JANSEN arrival, which no longer exists. Pilots are advised to use either the ROYIL2 or the SHNON2 (RNAV) STAR.
To KIND: File the CAPITAL7 departure to GVE, then via J42 to BKW, then via J526 to IIU for the DECEE3 arrival.
- KMCI - Kansas City :
To KMCI: File the INDY2 departure to VHP, then via J80 to SPI for the BRAYMER arrival.
NOTE: Although the current LoA mentioned BRAYMER3 by number, it is out-of-date (BRAYMER4 is current); pilots are advised to fly the BRAYMER4 arrival.
To KIND: File the LAKES5 departure to SPI, then take J80 to VHP.
- KMDW - Chicago Midway :
To KMDW: RNAV flights, file the INDY2 departure to OKK for the FISSK1 arrival.
Non-RNAV flights, file the INDY2 departure to BVT for the BOILER2 arrival.
To KIND: File the MIDWAY7 or CICERO4 departure to EON, then take V24/V399 to KENLA, then take V24/V128 to VHP.
- KMEM - Memphis :
To KMEM: File the INDY2 departure to PXV for the WLDER5 or LTOWN4 (RNAV) arrival.
To KIND: File the MEMPHIS7 departure to BNA, then take J39 to IIU for the DECEE3 arrival.
- KORD - Chicago O'Hare :
To KORD: RNAV flights, file the INDY2 departure to MZZ for the ROYKO3 arrival.
Non-RNAV flights, file the INDY2 departure to VHP, then direct OXI for the KNOX4 arrival.
NOTE: The ROYKO3 and the KNOX4 STARs differ greatly from their previous version. If you file one of the new STARs, be sure it is using the correct route.
NOTE: There is a new STAR for KORD, the WATSN1. The MZZ transition is assigned by ATC only, and may not be filed or requested by the pilot.
To KIND: RNAV flights, file the O'HARE3 departure to EARND, then via ELANR, EMMLY, and JAKKS to VHP.
Non-RNAV flights, file the O'HARE3 departure to EON, then take V24/V399 to KENLA, then take V24/V128 to VHP.
- KPIT - Pittsburgh :
To KPIT: File the INDY2 departure to DQN, then proceed direct EMPTY, joining J80 to AIR for the WISKE3 arrival.
To KIND: File the PITTSBURGH9 departure to AIR, then via J80 to EMPTY for the CLANG5 arrival.
- KRDU - Raleigh-Durham:
To KRDU: File the DAWNN3 departure to IIU, then via J526 to BKW, then direct ROA for the SOUTH BOSTON4 arrival.
To KIND: File the RALEIGH7 departure to FAK, then direct BKW, then via J526 to IIU for the DECEE3 arrival.
- KRIC - Richmond :
To KRIC: File the INDY2 departure to CVG, then direct to FLM, then via J24 to MOL. At this time, there are no STARs for KRIC.
To KIND: File the YEAST1 departure to MOL, then via J42 to BKW, then via J526 to IIU for the DECEE3 arrival.
- KSDF - Louisville International / Standiford Field :
To KSDF: Request radar vectors to SHB, then via V51 to IIU.
To KIND: Request radar vectors to ABB, then via V51 to DECEE3 for the DECEE arrival.
- KSTL - St. Louis :
To KSTL: File the INDY2 departure to VHP for the VANDALA arrival.
NOTE: Although the current LoA mentions VANDALIA5 by number, it is out-of-date (VANDALIA6 is current), so pilots are advised to fly the VANDALIA6 arrival.
To KIND: File the GATEWAY4 departure to VHP. If weather dictates, file the CARDS7 departure to SPI, then take J80 to VHP.
The maintainer of this document would like to thank the following people and sites for their contribution to this AIP:
- Ben Bain, a vZID controller (current as of October 2008), VATSIM CID 943570, who provided descriptions of all of the buildings located at Indianapolis International airport. His information made it possible to know exactly who needs to go where.
- The offices of the Federal Aviation Administration, part of the Department of Transportation. They maintain and publish the vast amount of charts and other documents pertaining to flight and navigation within the United States of America. It is difficult, yes, but definitely worth it.
- SkyVector, for making available virtually all published FAA charts for easy online viewing. SkyVector serves as a perfect integration between Web 2.0 and navigation.
- AirNav, LLC, for taking the large amount of information available on airports, navaids, and airspace fixes, and making said information easy to access and easy to view. AirNav shows that it is possible to make aviation information easy to get, and easy to see.
- The Indianapolis Airport Authority, for making information available, via their Indianapolis International airport website, on exactly which commercial passenger airlines park at each terminal concourse.
- Banjamin Van Eps, a VATSIM pilot, VATSIM CID 987241, for creating a VATSIM forums thread alerting VATSIM pilots to the problem with the KIND SIDs, as implemented by PMDG and Level 3 planes.
- Dan Downs, for maintaining accurate freeware PMDG SID/STAR information.
- Dave Paige, a VATSIM pilot, VATSIM CID 925700, for the posting to the VATSIM forums pointing users to Dan Downs' procedure files.
Disclaimer & Copyright
Although much of this material is taken from sources suitable for real-world navigation, this document is not intended for such use. This document is intended for use by flight simulator pilots on the VATSIM network.
Most of the information in this document is obtained from the governments of the United States, the State of Indiana, the County of Marion, the City of Indianapolis, and the Indianapolis Airport Authority, and is therefore public domain. Those portions of this document which are not public domain are Copyright © 2008 by those who are referred to by the Acknowledgements section above, and by A. Karl Kornel (vZID controller as of October 2008, VATSIM CID 964857), the current maintainer of this document. This work is licensed under the Creative Commons Attribution-Share Alike 3.0 United States License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/3.0/us/ or send a letter to Creative Commons, 171 Second Street, Suite 300, San Francisco, California, 94105, USA.
Since creation as a draft document, this AIP has gone through the following changes:
- 27 January 2009:: Updated routings to KDCA and KCLT.
- 14 December 2008: Replaced SID/STAR names with their full names. Added major revision numbers for SIDs/STARs. Updated routings to/from KDCA, KMCI, KORD, and KSTL.
- 16 November 2008: Modified the Scenery Notes section to reflect that the new areas are in use; modified the Ground Notes section to describe the airline concourse assignments, and the location of the international gates. Also modified the Scenery Notes section to mention a problem with PMDG and Level 3 planes with KIND SIDs that involve vectors. Added two entries to the Acknowledgements.
- 30 October 2008: Publication. No changes were made since the previous revision.
- 19 October 2008: Draft released to vZID controllers for comment.