New Precision On The Ramp?

  • warning: mysqli_real_connect() [function.mysqli-real-connect]: (28000/1045): Access denied for user 'cbnewtor_chris'@'localhost' (using password: YES) in /home1/cbnewtor/public_html/corpuscurio/gallery2/lib/adodb/drivers/adodb-mysqli.inc.php on line 108.
  • warning: mysqli_real_connect() [function.mysqli-real-connect]: (28000/1045): Access denied for user 'cbnewtor_chris'@'localhost' (using password: YES) in /home1/cbnewtor/public_html/corpuscurio/gallery2/lib/adodb/drivers/adodb-mysqli.inc.php on line 108.

Today I flew my 182 on a familiar trip from Torrance to Chino - this time to have one of my radios scrutinized at Advantage Avionics. I've flown this trip more times than I can count, but something was different today - a subtle difference I didn't really notice until later. Thinking back on it, my first clue was the taxi instructions I got from my hangar to runway 29R. This is at most 75 yards and the controller has always just cleared me "to 29R". Today, he specifically said, "29R via the ramp and Juliet". At the time, I didn't think much of it, simply repeated it back and continued to the runway.

Upon landing at Chino, I again noticed specific, step-by-step instructions where before there was simply a clearance to my destination on the field. By the time I returned to Torrance and, once again, received specific taxi instructions back to my hangar, I'd grown accustomed to it. But then this evening I read in the weekly AOPA ePilot email that the FAA has officially directed ground controllers to use this new, detailed method for all taxi instructions. It's part of their ongoing efforts to improve safety on the ground.

While it adds a bit to the dialog, I for one think it's a great idea. In effect, we now get "progressive taxi" instructions all the time. Sure it may seem a hassle at our familiar airports, but what about the pilots sharing those fields with us who are unfamiliar? I'd prefer not have them crossing in front of me as I'm starting my takeoff roll. Good idea, FAA.

To read more, go to the AOPA article.