- What is Business Aviation?
- Flight Department Administration
- Aircraft Operations
- Professional Development
- News & Publications
- Products & Services
This page lists regional airspace issues for Minneapolis Center, ZMP; Chicago Center, ZAU; Kansas City Center, ZKC; and Denver Center, ZDV. Notices, restrictions, and advisories may change at any time and without notice. Do not attempt any operation in the National Airspace System without first obtaining and understanding a thorough pre-flight briefing.
- New RNAV STARs at Denver Satellite Airports
- November 26, 2012
On November 15th, 2012, a new system of RNAV STARs was implemented in the Denver terminal area allowing for more efficient arrivals and fewer ground and air delays at the major hub and satellite airports. The new system applies to turbojet aircraft only and includes a set of 16 STARs – 8 dedicated to a south landing flow at DEN and 8 for a north flow. The STARs utilize altitude windows and airspeed constraints to accommodate optimized descents. Between Nov 15th and Dec 3rd these STARs are 'ATC Assigned Only'. Then, beginning Dec 3rd, the full system will be active and aircraft will be expected to file the appropriate STAR. It is critical that flightcrews familiarize themselves with these new procedures and strictly adhere to all altitude and airspeed requirements. A detailed video description of the operational characteristics of the new system can be found here. For questions and more information please contact Ted Goodlin at firstname.lastname@example.org.
- Runway Safety Alert Issued for Chicago Midway (MDW)
- September 17, 2012
The FAA is calling on pilots to exercise greater vigilance in maintaining situational awareness during ground operations at Chicago-Midway Airport (MDW). Officials note that many runway incursions are caused by transient traffic and GA pilots in particular have been responsible for the recent string of incursions at MDW. Often dubbed the “World’s busiest square mile”, MDW is designed with complex runways and associated taxiway configurations which creates uncommon Runway Hold Positions. In many cases the taxiways do not intersect the runways at right angles which can lead to confusion. View the safety alert and associated taxi illustrations.
- Jeppesen Charts to Feature CABAA Visual Departure at PWK
- April 30, 2012
The Chicago Area Business Aviation Association (CABAA) received approval to have the CABAA Visual Departure at Chicago Executive Airport (PWK) published in Jeppesen charts. The procedure, which was developed in 2011 to minimize takeoff delays with the opening of Runway 27R at Chicago O’Hare (ORD), has until now been published only in the Airport/Facility Directory. The new Jeppesen chart will be issued on May 12 under Revision 11. The departure is to be used in conjunction with an IFR clearance when departing Runway 16 at PWK. Pilots are responsible for aircraft separation and avoidance of the Class B airspace until IFR control is provided by TRACON. Learn More.
- New Chicago Class B Airspace Effective October 29 Not Reflected in Jeppesen Database
- October 28, 2010
The redesign of Chicago’s Class B airspace goes in to effect on October 29, 2010. However, the latest Jeppesen Database did not include the changes and flight crews need to pay special attention to the airspace changes. View the Jeppesen NavData Alert.
- Slot Reservation Requirement at Chicago O'Hare International Airport (ORD) Ends October 31
- October 25, 2010
The requirement to obtain slots for non-scheduled aircraft arriving at ORD, which has been in place since 2005, expires on October 31, 2010. The requirement was originally issued through SFAR No. 105 and was put into place to help manage the volume of non-scheduled arrivals flying into ORD. The SFAR specified an expiration date of October 31, 2010, anticipating that sufficient airspace and airport improvements would be made to allow for the program’s cancellation. View the SFAR.
- Chicago Class B Redesign Highlights Importance of Local Industry Involvement
- September 14, 2010
The newly redesigned Chicago Class B airspace, expected to debut later this year, can be viewed as a success, and a model for airspace re-design elsewhere, in part because of involvement from local business aviation stakeholders. Chicago is one of the first Class B area redesigns scheduled for this year and next. Other redesigns in process include those for Cleveland, Detroit, New York, Philadelphia and Seattle. Redesigns for Class B areas around Cincinnati, Las Vegas, Miami, Minneapolis, Salt Lake City and Washington/Baltimore are pending.
Learn more about the Chicago Class B Redesign.
- Ramp and Taxiway Safety Emphasized at Aspen/Pitken County Airport (ASE)
- December 22, 2009
Due to a number of recent ground incidents at Aspen/Pitken County Airport (ASE), the Federal Aviation Administration (FAA) is asking pilots to be vigilant while on the ground at this airport. Several incidents have occurred where pedestrians and vehicles have wandered onto active taxiways without clearance. Also, passengers, either deplaning or getting ready to board, have crossed hold lines in order to take pictures of the surrounding scenery. Download the ASE “hot spot brochure” (481KB, PDF)
- MKC Prohibits Category C and D Operations on Runways 3, 21
- April 6, 2009
Runways 3 and 21 at Kansas City Charles B. Wheeler/Downtown Airport (MKC) in Missouri recently were reclassified to the B-II airplane design group to meet runway safety area requirements. Takeoffs and landings by category C and D airplanes are now prohibited on these runways at all times. Category C and D airplanes must use Runway 1 or 19 for takeoff and landing, as appropriate for the weather conditions. As a reminder, an airplane’s approach category is fixed and based on landing threshold speed at the maximum certified landing weight and may never be reduced to a lower approach category based on the actual weight at the time of takeoff or landing. For more information, refer to the FAA Airport/Facility Directory entry for the MKC airport or contact NBAA’s Bob Quinn at email@example.com.
- FAA Releases Western Service Area Letter to Airmen 08-03
- July 2, 2008
VFR aircraft executing practice instrument approaches at the locations listed in the letter will be provided IFR separation, to the extent possible, as described in the Aeronautical Information Manual, paragraph 4-3-21. Controller responsibility for separation begins at the point where the approach clearance becomes effective.
- FAA Asks Pilots to Note Configuration of Pueblo Runways, Avoid Incursions
- June 23, 2008
The FAA’s Runway Safety Office has notified NBAA about the alarming number of runway incursions at Pueblo Memorial Airport (PUB) in Pueblo, CO. This airport has an unusual configuration: Runway 8R/26L runs along the north edge of the ramp with no physical divider separating the ramp from the runway. Only a 4,000-foot-long hold line marks the boundary of the runway. The most common incursion is for a pilot to be instructed and correctly read back “hold short Runway 8R/26L” and then cross the runway hold line not realizing that the runway is there. It is critical that pilots calling for taxi from the ramp to (1) identify the hold line for the ramp runway prior to taxi, and (2) follow the painted yellow taxiway centerlines when taxiing on the ramp. NBAA encourages Members to become familiar with the airport configuration prior to arrival and again before taxi.
- FAA to Implement New Chicago Area Southbound Departure Routes
- March 13, 2008
Effective April 10, 2008, the FAA will implement new Chicago South Departures utilizing RNAV routes. These new routes will affect both Chicago International Airport (ORD) and all satellite airports in the Chicago area. This includes routes, airspace, sectorization and procedures. FAA has provided a PowerPoint presentation designed to assist the pilots in understanding differences and the associated reasons.View the presentation. Questions should be directed to Mike O’Brien, ZAU, at (630) 906-8445 or Michael.O'Brien@faa.gov or Bill Smar, Front Line Manger, ZAU Operations, (630) 906-8239 or firstname.lastname@example.org.