The taxiway layout at Boston Logan airport (KBOS) has changed. Affected and new taxiways include: Alpha, Alpha-1, Alpha-2, Bravo, Delta, Echo, Echo-1, Echo-2, Golf, Kilo, & Mike. We realize that use of the current layout will differ from default scenery found in FS2004, FSX and XPlane. However, it has been over 2.5 years since many of the configuration changes took effect, and a majority of pilots are now using add-on scenery and/or current charts, so it was causing more confusion to provide guidance using the old, default configuration.

As there are now a number of commercial, VA and freeware scenery updates available to pilots, we will now provide ground control service consistent with the NEW (current) taxiway configuration, unless a pilot specifically advises the controller he/she has default scenery and is not able to accept a taxi route via the new taxiway configuration.

As of now, we are aware that the following software vendors have payware KBOS scenery available:

• FlyTampa KBOS v3.1 (includes all current changes, except the taxiway Delta extension mistakenly connects with Echo instead of Papa (developers notified of the error on 28 May 2010; no estimate for a correction yet) www.flytampa.org
• Blueprint Simulations KBOS v1.2.x (includes all changes except taxiway Delta extension; Blueprint has agreed to incorporate that change and offer it as a free update (based on conversation with them on 16 Apr 2010) www.blueprintsimulations.com

There are a few freeware versions available by searching the internet, with varying quality. If you know of any that you feel are very good quality, please email that information to atm -at- bostonartcc.net. If possible, also include a screenshot of overhead the airport, so we may evaluate taxiway layout accuracy (any other screenshots welcome also).

We certainly appreciate your patience as we transition to the new taxiway configuration.

The FAA has issued FAA Notice 7110.532, effective 30 Jun 2010, that affects significantly the taxi procedures used when crossing runways.

Summary of Changes:
1. The phraseology "Taxi to _____" will no longer be used.
2. Aircraft are no longer automatically permitted to cross runways along their taxi route. An explicit runway crossing clearance must be issued for each runway (active/inactive or closed) crossing and requires an aircraft/vehicle to have crossed the previous runway before another runway crossing clearance may be issued.

An example using the new terminology:
Note: In the following example, KBOS is using the 27/27 configuration, Local and Ground control are combined.

Old clearance to Runway 27 for departure, using the new taxi diagram, would sound like:
AAL123, taxi to runway 27 via Bravo, Charlie, Delta.

New clearance to Runway 27 for departure, using the new taxi diagram, would sound like:
AAL123, Runway 27, taxi via Bravo, Charlie, Delta.

even though no hold short was issued for Runway 4L, AAL123 cannot cross 4L without a clearance.

as AAL123 approaches Runway 4L:
AAL123, cross Runway 4L.

as AAL123 approaches Runway 4R:
AAL123, cross Runway 4R.

as AAL123 approaches Runway 33L:
AAL123, cross Runway 33L.

Now, all that said, due to the VATSIM top-down control methodology, there may be instances where a controller above (Approach or Center) is providing local and/or ground service at an airport. These new procedures will be followed to the best of the controller's ability, on a workload permitting basis. Pilots should be patient (RW and VATSIM!) as these new procedures are deployed, and expect some delays as this new rule in some cases will significantly affect controllers' workloads. A controller's primary responsibility is separation of aircraft in the air; in the event of combined positions, priority will always go to that function before crossing clearances. Once we all come down the learning curve, it will get better and more efficient.