Narrative:

A330 departed out of iad over wooly direct bross.J42./. Overseas through the swann sector (17) at washington center; took an airbus turn at bross that commenced nearly 15 miles prior to the fix. The turn did not get close to bross and encroached upon the dupont sector (18) in transition to the woodstown sector (19). The sector 17 controller had to point the aircraft out to the sector 18 controller; which created unnecessary added workload during a busy departure push out of the washington metro area. This situation is becoming all too common for international departures eastbound out of iad through sector 17 and highlights the need for corrective action. There were two air traffic bulletins released by the FAA on this issue in 2000 and 2003 respectively. The 2000 bulletin (00-1) addressed high altitude turn anticipation? In response to reports of certain aircraft beginning to turn a significant distance from a fix? The bulletin addressed a known issue of airbus aircraft; specifically; the A319/320/321; making turns greater than 70 degrees above FL180.? The A330 was identified with this issue as well. It was found that these aircraft have been designed; for reasons of passenger comfort and aerodynamics; to make what we would consider shallow turns at altitude? This particular turn; from a direct course; wooly to bross onto J42; is not a 70 degree or greater turn. The 2003 bulletin (03-5 special) went further in depth by explaining aircraft behavior while performing advanced RNAV procedures. One of the benefits of RNAV described to the air traffic workforce was increased flight path predictability and repeatability? This came with the caveat; however; that RNAV databases and equipment are not fully standardized; and there is no firm guidance on how the information is processed by aircraft systems. Further; these track differences should not be significant enough to appear as deviations from the published procedure. This guidance is open to too much interpretation for application within the rigid east coast airspace structure of the united states. I can say; unequivocally; these flight paths are not predictable; and the track differences are significant enough to be considered as deviations from published procedures as in this case. System errors have occurred due to this issue; and will continue to occur if it is not addressed. In the ten years since the FAA issued its first air traffic bulletin covering this topic; these procedures are still not covered in FAA order 7110.65T; air traffic control for controllers throughout the NAS).

Related reports:

Google
 

Original NASA ASRS Text

Title: ZDC Controller described near airspace entry event; the reporter claiming the turns used by Airbus aircraft are extremely shallow and take up too much space in the cramped Eastern airspace; noting procedure expectations are not adequately covered in FAA directives.

Narrative: A330 departed out of IAD over WOOLY direct BROSS.J42./. Overseas through the SWANN Sector (17) at Washington Center; took an Airbus turn at BROSS that commenced nearly 15 miles prior to the fix. The turn did not get close to BROSS and encroached upon the DuPont Sector (18) in transition to the Woodstown Sector (19). The Sector 17 Controller had to point the aircraft out to the Sector 18 Controller; which created unnecessary added workload during a busy departure push out of the Washington Metro area. This situation is becoming all too common for international departures eastbound out of IAD through Sector 17 and highlights the need for corrective action. There were two Air Traffic Bulletins released by the FAA on this issue in 2000 and 2003 respectively. The 2000 bulletin (00-1) addressed High Altitude Turn Anticipation? In response to reports of certain aircraft beginning to turn a significant distance from a fix? The bulletin addressed a known issue of Airbus aircraft; specifically; the A319/320/321; making turns greater than 70 degrees above FL180.? The A330 was identified with this issue as well. It was found that these aircraft have been designed; for reasons of passenger comfort and aerodynamics; to make what we would consider shallow turns at altitude? This particular turn; from a direct course; WOOLY to BROSS onto J42; is not a 70 degree or greater turn. The 2003 bulletin (03-5 SPECIAL) went further in depth by explaining aircraft behavior while performing advanced RNAV procedures. One of the benefits of RNAV described to the air traffic workforce was increased flight path predictability and repeatability? This came with the caveat; however; that RNAV databases and equipment are not fully standardized; and there is no firm guidance on how the information is processed by aircraft systems. Further; these track differences should not be significant enough to appear as deviations from the published procedure. This guidance is open to too much interpretation for application within the rigid East Coast airspace structure of the United States. I can say; unequivocally; these flight paths are not predictable; and the track differences are significant enough to be considered as deviations from published procedures as in this case. System errors have occurred due to this issue; and will continue to occur if it is not addressed. In the ten years since the FAA issued its first Air Traffic Bulletin covering this topic; these procedures are still not covered in FAA Order 7110.65T; AIR TRAFFIC CONTROL for controllers throughout the NAS).

Data retrieved from NASA's ASRS site as of April 2012 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.