Don Desfosse

Well, today's the day, folks! It's official, it's now Line Up and Wait. (Ugh..., he said in distaste....)

The Boston ARTCC (vZBW) is currently seeking a Webmaster / Data Services Manager who will provide compelling capability and effective management of the vZBW web and data services function. The Webmaster will also be responsible for the creation, delivery, management, quality and governance of the vZBW website. Key Accountabilities: * Reports to the Boston Air Traffic Manager * Manages and oversees the ARTCC's data services including web content and delivery, web services, email systems, data storage systems, etc. * Must respond quickly to web site and data systems needs * Develops and implements policies and procedures for operation and maintenance of the ARTCC web and data systems * Functions as an ARTCC staff member and attends periodic meetings as necessary Required Skills: * Must be an active member of the network in good standing with a clean history and no previous incidence of misuse of technology (hacking, cracking, etc.) * Must be proficient with modern web programming languages and techniques, including PHP Object Oriented Programming, HTML, PHP/MySQL, CSS * Must be able to succeed in a team environment * Must have excellent written and oral communication skills Desired Skills: * Demonstrated custom web programming with PHP/MySQL in a production environment, Commercial/Enterprise class experience a bonus * AJAX/Javascript * RSS/XML and DOM * Familiarity with APIs for other applications (Google, Twitter, Facebook, etc.) Applicant must provide letter of application, including resume to include examples of previous work. Letter of application should summarize the applicant's reasons for wanting to join the Boston team, compelling evidence to show how the position requirements are met, and how the function will thrive under the applicant's leadership. Applications should be submitted to Don Desfosse, ZBW Air Traffic Manager, at atm -at- bostonartcc.net. Application deadline is 30 September 2010.

It's changing common US phraseology to common international (ICAO) phraseology, to help "everyone else" understand the instruction better. Conformance to the ICAO standard. No comment on whether I think it's smart or necessary or not... ;) (The FAA didn't ask me....)

The long-anticipated change from Taxi into Position and Hold (TIPH) to Line Up And Wait (LUAW) is now official, with an implementation effectivity of 30 Sep 2010. The FAA just issued FAA Notice 7110.536, effective 30 Sep 2010, that changes our terminology from "Position and Hold" to "Line Up and Wait". This further drives our alignment to ICAO procedures. Summary of Changes: 1. The phraseology "Position and Hold" will be replaced with "Line Up and Wait".

And this is precisely what we'll do, and we'll reassess after a few weeks. Where positions are combined, workload permitting, we'll follow the new regulation (i.e. "Runway 22R, taxi via Bravo, November, Cross runway 15R.") If workload does not permit, multiple crossing clearances will be utilized (i.e. the example above, or "Runway 22R, taxi via Bravo, November, Cross runways 15R and 15L." or "Runway 22R, taxi via Bravo, November, cross all runways.")

CN, you're not missing anything. I'm struggling with the best way to implement this, yet also realizing that oftentimes we have a lone CTR controller working everything in ZBW, sometimes with more traffic than one could be expected to handle all their traffic and ground crossings at our 31 towered fields.... I want to maintain realism as best as possible, yet the alternative, if the lone CTR controller (for example) is truly too busy to hold everyone's hand across every runway, is to treat most/all subordinate fields as uncontrolled. I'd really like to avoid doing the uncontrolled thing. I thought this approach, taking into account the comments/suggestions published here as well as on the VATSIM and VATUSA forums, was a reasonable compromise. I should have stated that I'd like to try this approach out for a few weeks, then solicit input as to whether or not it's working, and determining if a course correction is warranted. Fair?

Well, that's a great question.... Technically, yes we are, though we all know that it's not been published very well (in my opinion) to pilots. Neither FAR Part 91 nor the AIM have been revised to incorporate this change. Not that everyday pilots read FAA Notices regarding JO 7110.65, but the FAA maintains that the change has been published via the earlier FAA Notice 7110.528, and the more recent FAA Notice 7110.532. It has also been published on FAASafety.gov (including via email to everyone who is registered on www.faasafety.gov on 28 June), and has appeared in several of the aviation media (AOPA, AvWeb, etc.). So I don't really expect all pilots (RW and VATSIM) to be up to speed on this. Like lots of things, this will become an added part of our education mission -- we'll teach the new procedure to our pilots.

Yep, that's legal.

Well, folks, it's here. Remember that a specific hold short need not be issued for every runway along the taxi route. So in the example above, using 27/27, no hold shorts are needed, but a specific crossing clearance will be. In the case of the 33/27 configuration, the only specific hold short would have to be for 33L. So here's an example for that: Note: In the following example, KBOS is using the 33/27 configuration, Local and Ground control are combined. Old clearance to Runway 27 for departure, using the new taxi diagram, would sound like: AAL123, Runway 27, taxi via Bravo, Charlie Delta, hold short Runway 33L. New clearance to Runway 27 for departure, using the new taxi diagram, would sound like: AAL123, Runway 27, taxi via Bravo, Charlie Delta, hold short Runway 33L. (see, this is actually the same. But that's where the similarity ends....) 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, since Ground and Local are combined, once it is safe to cross: AAL123, cross Runway 33L. Note that if Ground and Local were not combined, Ground would pass AAL123 off to Local as it approached 33L, same as before. 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 are to 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.

As I enjoy my 2 kids today, and prepare to have a major gathering of family, including many fathers (and a soon-father-to-be), I wanted to share my hope that all fathers out there can share in the enjoyment and celebration of being a Dad today. Happy Fathers' Day!

And a touch late for Memorial Day yesterday, but I just received this and thought it worth sharing.

Team, please join me in welcoming Carl Klinker (KK) as our newest Facility Engineer! Carl currently serves as a mentor, and has a good amount of experience in the technical side of the house. He's now learned to create sector files, and is doing a good job with that. We look forward to more contributions soon! Congratulations!

Let's take a moment to remember why this is a holiday weekend coming up (in the USA). Three years after the Civil War ended, on May 5, 1868, the head of an organization of Union veterans -- the Grand Army of the Republic (GAR) -- established Decoration Day as a time for the nation to decorate the graves of the war dead with flowers. Maj. Gen. John A. Logan declared that Decoration Day should be observed on May 30. It is believed that date was chosen because flowers would be in bloom all over the country. The first large observance was held that year at Arlington National Cemetery, across the Potomac River from Washington, D.C. The ceremonies centered around the mourning-draped veranda of the Arlington mansion, once the home of Gen. Robert E. Lee. Various Washington officials, including Gen. and Mrs. Ulysses S. Grant, presided over the ceremonies. After speeches, children from the Soldiers' and Sailors' Orphan Home and members of the GAR made their way through the cemetery, strewing flowers on both Union and Confederate graves, reciting prayers and singing hymns. The crowd attending the first Memorial Day ceremony at Arlington National Cemetery was approximately 5,000 people. Then, as now, small American flags were placed on each grave -- a tradition followed at many national cemeteries today. In recent years, the custom has grown in many families to decorate the graves of all departed loved ones. The origins of special services to honor those who die in war can be found in antiquity. The Athenian leader Pericles offered a tribute to the fallen heroes of the Peloponnesian War over 24 centuries ago that could be applied today to the 1.1 million Americans who have died in the nation's wars: "Not only are they commemorated by columns and inscriptions, but there dwells also an unwritten memorial of them, graven not on stone but in the hearts of men." To ensure the sacrifices of America's fallen heroes are never forgotten, in December 2000, the U.S. Congress passed and the president signed into law "The National Moment of Remembrance Act," P.L. 106-579, creating the White House Commission on the National Moment of Remembrance. The commission's charter is to "encourage the people of the United States to give something back to their country, which provides them so much freedom and opportunity" by encouraging and coordinating commemorations in the United States of Memorial Day and the National Moment of Remembrance. The National Moment of Remembrance encourages all Americans to pause wherever they are at 3 p.m. local time on Memorial Day for a minute of silence to remember and honor those who have died in service to the nation. As Moment of Remembrance founder Carmella LaSpada states: "It's a way we can all help put the memorial back in Memorial Day." May you all enjoy a safe and happy holiday weekend, and give the appropriate thought, remembrance, and consideration to those who went before us, fighting to protect the freedome we enjoy.

Awesome, appreciate that! We can use the help!

Note: This posting is still open! I'd appreciate it if anyone on our team knows anyone that's qualified, or even has the interest in learning, to let them know about this opening! We have several projects lining up in queue!

I don't know if it's me or if there's something in the water around here.... But I can't seem to hold onto my staff.... Last week my Webmaster gets promoted to become Houston's ATM, and this week my Facility Engineer gets promoted to VATUSA Division Director :) Anyway, without further ado: The Boston ARTCC (vZBW) is currently seeking a Facility Engineer who will provide compelling capability and effective management of the vZBW facilities infrastructure function. The Facility Engineer will also be responsible for the creation, delivery, management, quality and governance of the vZBW facilities infrastructure. Key Accountabilities: * Reports to the Boston Air Traffic Manager * Develops, maintains and manages the ARTCC's facilities infrastructure, including sector files, alias files, position files, VRC/ASRC files, TowerTrainer and ACSIM facilities files, etc. * Must respond quickly to facilities issues and needs * Employs the use of and manages other ARTCC members' efforts to increase bandwidth * Functions as an ARTCC staff member and attends periodic meetings as necessary Required Skills: * Must be an active member of the network in good standing with a clean history and no previous incidence of intentional disciplinary issues * Familiar with sector file design methodologies and utilities * Familiar with tools such as VRC, ASRC, Gndmaker, alias files, etc. * Must be able to succeed in a team environment * Must have excellent written and oral communication skills Desired Skills: * Demonstrated experience developing and/or maintaining facilities/sector files * Familiar with TowerTrainer and/or ACSIM * Familiar with ZBW airspace and procedures Applicant must provide letter of application, including resume to include examples of previous work. Letter of application should summarize the applicant's reasons for wanting to join the Boston team, compelling evidence to show how the position requirements are met, and how the function will thrive under the applicant's leadership. Applications should be submitted to Don Desfosse, ZBW Air Traffic Manager, at atm -at- bostonartcc.net. Additionally, we are looking for 2-3 interested team members who are willing to work specific sector file development projects as assigned by the Facility Engineer. Contact DO if you are interested in further supporting the team.

I spoke with some of the folks at AOPA. I think they're starting to realize that they need to advertise this on behalf of the pilot community. I complained that not enough advertising regarding who what when why how and how come was being done.... No commitment, but reply back from the person I was talking to is that they'll look into it......

Haven't we done this once before? Our deepest and heartiest congratulations go out to our very own Gary Millsaps (MS), who is (once again) wandering across the fence to take over the reins as Director of the VATUSA Division. Many of you will recall that Gary has already served as VATUSA1, holding arguably one of the most successful runs at the job since VATSIM came into existence. It is with full trust and confidence that I say that we're once again on the path to excellence with Gary at the reins. Best wishes for luck and success, Gary! Here is the announcement from Bryan Wollenberg, the VATUSA North American Region Director:

I think the problem there is with the proviso in the new 3-7-2© (effective 30 Jun 2010), which states: The other thing I was hoping to capitalize on was but our parallels are 1500 feet apart. The only place I see an opportunity to use that is for aircraft exiting 33L/15R onto either Quebec or Mike, Quebec, whereby Local could issue them, "(Welcome to Boston), left turn onto Quebec, cross runway 4L, taxi to.... (or contact Ground on the other side)." or "(Welcome to Boston), right turn onto Quebec, cross runway 4L, taxi to.... (or contact Ground on the other side)." or "(Welcome to Boston), right turn onto Mike, right turn onto Quebec, cross runway 4L, taxi to.... (or contact Ground on the other side)." To capitalize on the above at other towered airports, the proviso will need to be included in the airport SOP. Anyone willing to look at the airport diagrams for our towered airports and give me a list of situations where we could capitalize on a runway crossing clearance where the taxi route between runway centerlines is less than 1,000 feet apart? This blows. I hope someone comes to their senses and fixes this before 30 Jun 2010....

Yes, that remains unchanged.

Team, The FAA just issued FAA Notice 7110.528, 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. Yes, so on a busy day (read event), can you see the issue with this....? Methinks the lawyers won, ATC and the pilots lost.....

The Boston ARTCC (vZBW) is currently seeking a Webmaster who will provide compelling capability and effective management of the vZBW web and services function. The Webmaster will also be responsible for the creation, delivery, management, quality and governance of the vZBW website. Key Accountabilities: * Reports to the Boston Air Traffic Manager * Manages and oversees the ARTCC's data services including web content and delivery, web services, email systems, data storage systems, etc. * Must respond quickly to web site and data systems needs * Develops and implements policies and procedures for operation and maintenance of the ARTCC web and data systems * Functions as an ARTCC staff member and attends periodic meetings as necessary Required Skills: * Must be an active member of the network in good standing with a clean history and no previous incidence of misuse of technology (hacking, cracking, etc.) * Must be proficient with modern web programming languages and techniques, including PHP Object Oriented Programming, HTML, PHP/MySQL, CSS * Must be able to succeed in a team environment * Must have excellent written and oral communication skills Desired Skills: * Demonstrated custom web programming with PHP/MySQL in a production environment, Commercial/Enterprise class experience a bonus * AJAX/Javascript * RSS/XML and DOM * Familiarity with APIs for other applications (Google, Twitter, Facebook, etc.) Applicant must provide letter of application, including resume to include examples of previous work. Letter of application should summarize the applicant's reasons for wanting to join the Boston team, compelling evidence to show how the position requirements are met, and how the function will thrive under the applicant's leadership. Applications should be submitted to Don Desfosse, ZBW Air Traffic Manager, at atm -at- bostonartcc.net. Application deadline is 30 April 2010.

Also known as, "Redefining Obesity" ;D The FAA has released a notice addressing the reclassification of the heavy category of aircraft to become aligned with the International Civil Aviation Organization's (ICAO) heavy classification. To be considered heavy under the new policy, aircraft must have a maximum certificated takeoff weight (MTOW) of at least 300,000 lbs. The old rule to be classified as a heavy was an MTOW of at least 255,000 lbs. Boeing 757s, both -200 and -300 models, are therefore all classified under the large category, and heavy will no longer be part of any 757 aircraft callsigns. Radar controllers: For the purposes of wake turbulence separation, the 757 (again, both the -200 and -300 series) is a large aircraft when it is trailing behind another aircraft. When it is ahead of another aircraft, it is separated as a 757 (not a large nor heavy; the 757 has its own classification). If you don't know what that means, then you probably need to check out 7110.65T Chapter 5-5-4. So, in essence, this should actually make our lives easier, as we no longer have to worry about whether a B757 is heavy or not; they are all large. 5-5-4 remains unchanged, so B757s are now all B757s, not either B757s or heavies depending on the model....

It's with a heavy heart that, due to real world obligations that need to take the preponderance of his time and focus, I announce the resignation of Jeffrey Marques (AA) as my Ass Chief. Jeff continues to have my utmost respect as an excellent, seasoned controller and instructor, and has been of great help and counsel to me as I took over the reins as Chief of the ARTCC last summer. Jeff, you have been and continue to be a great friend. I and the whole ARTCC have appreciated your dedication and steadfastness, and look forward to your contributions again as you have more time to contribute. That said, I am thrilled to announce that Rich Bonneau (BU) has accepted my invitation to join this wild and crazy ride as my new Ass Chief. Rich is an excellent manager, is dedicated and loyal to ZBW, and knows just how much Jim Beam goes in my Coke to make it perfect. Obviously a perfect fit for the job! ;D Seriously, Rich is a steady force of excellence here at ZBW, and I (and we) are looking forward to your leadership in the number 2 slot (for now....!). Finally, to ensure we maintain our excellence in staffing for events, Matt Spencer (SP) has accepted the role of Events Coordinator. Between ensuring we keep up with ZBW's historical set of good events and dreaming up exciting new ones, I (and we) look forward to kicking it up a notch or two and getting to practice our fun more often. Please join me in congratulating Jeff on a job well done and a well earned retirement (we look forward to bringing you out of retirement in a few months!) and congratulating Rich and Matt in their new roles. Give 'em a week to get settled into their new offices and learn how to spell their new titles, then give 'em hell! Don Desfosse Air Traffic Manager Boston ARTCC

Thanks, Mike, your post brought me back to remember great memories of when I was appointed. This has been just a super 4 months at the helm of the best ARTCC on the planet! Helping each other succeed is what this team is all about. Thanks again, and best wishes for super holidays!