Narrative:

Nearing the end of a 7 hour flight from phl to lgw, united kingdom, the gatwick/london director ATC area, we were advised to enter holding at the holly/willo arrival circuit due to traffic congestion. The holly/willo arrival is hard programmed into our software. Upon the second circuit (second left turn in holding pattern) after just passing willo intersection, we were given an approximately heading of 044 degrees to head us toward mayfield (may) intersection on the RNAV runway 26L arrival. Upon pulling and dragging the heading track selector knob to the left, the aircraft was virtually non responsive. The controller, thinking that we had missed his instruction, asked us if we were in a left turn, at which time we were slowly turning. The controller then asked us to turn to the right over 180 degrees toward mayfield (on assigned heading not direct). The plane again was virtually unresponsive (very slow to turn). It should be pointed out that we had a check airman who was in the cockpit to certify the RNAV capabilities of the airbus 330 overseas at gatwick. Over the 14 yrs that I've been flying to gatwick with this carrier, this (willo/holly) arrival has always been a problem area of understanding. The london controllers are excellent and have always been in this area. At the present time we are experiencing navigation/heading problems in sequencing over the north atlantic. Apparently software upgrades/changes are being made. London controllers should be advised of this problem and should avoid giving us 180 degree turns immediately (a turn with 45 degrees should be initially given to get aircraft turning in correct direction and then followed by final desired turn). This was captain's second trip to europe on this aircraft. 4 highly qualified pilots in cockpit (91 yrs of experience). Callback conversation with reporter revealed the following information: the first officer stated that this problem with the slow turn rate was probably associated with the design of the software within the FMS/IRS system of the A330-300. This software problem was also involved in at least 2 known 'failures to sequence the nat' (when over 1 waypoint the FMS failed to shift to the next waypoint). Nat track deviations experienced by 2 separate other airline check airmen on this equipment. It was alleged that these 2 track deviations were associated with software interface malfunctions and that the manufacturer of the software did not coordination with reporter's airline. Reporter stated that 'a major software change is forthcoming to correct this problem.' in this event, during one of many required RNAV equipment certification flts, the flying first officer did not disengage the autoplt to make a manual heading change. He admits that he should have. He cited an old inbred training issue of not disconnecting the automated system. He also said to 'forget all the old xyz aircraft stuff.' first officer feels that the autoplt/FMS thought the aircraft was still in the holding pattern during the attempted turn. The first officer (termed a 'whiz on the computers') and the check airman were jump seating and could not make out why the aircraft was not responding as it should have. Everyone is 'new' to this aircraft, the captain having about 60 hours total in type. So far as the reporter knows, the only feedback to aircraft manufacturer on these events is the methodology used in selecting the new heading. Aircraft manufacturer says to 'select heading first, then pull the heading/track selector knob.' the company is monitoring the situation but is 'hampered by the fact that an all new airline safety board is in place.' a copy of this report was also sent to the union safety office.

Google
 

Original NASA ASRS Text

Title: AN A330-300 FO RPT ON THE INABILITY OF THE CREW TO TURN THEIR ACFT IN ACCORDANCE WITH RADAR VECTORS IN THE LONDON AREA OF GATWICK, EGKK, FO.

Narrative: NEARING THE END OF A 7 HR FLT FROM PHL TO LGW, UNITED KINGDOM, THE GATWICK/LONDON DIRECTOR ATC AREA, WE WERE ADVISED TO ENTER HOLDING AT THE HOLLY/WILLO ARR CIRCUIT DUE TO TFC CONGESTION. THE HOLLY/WILLO ARR IS HARD PROGRAMMED INTO OUR SOFTWARE. UPON THE SECOND CIRCUIT (SECOND L TURN IN HOLDING PATTERN) AFTER JUST PASSING WILLO INTXN, WE WERE GIVEN AN APPROX HDG OF 044 DEGS TO HEAD US TOWARD MAYFIELD (MAY) INTXN ON THE RNAV RWY 26L ARR. UPON PULLING AND DRAGGING THE HDG TRACK SELECTOR KNOB TO THE L, THE ACFT WAS VIRTUALLY NON RESPONSIVE. THE CTLR, THINKING THAT WE HAD MISSED HIS INSTRUCTION, ASKED US IF WE WERE IN A L TURN, AT WHICH TIME WE WERE SLOWLY TURNING. THE CTLR THEN ASKED US TO TURN TO THE R OVER 180 DEGS TOWARD MAYFIELD (ON ASSIGNED HDG NOT DIRECT). THE PLANE AGAIN WAS VIRTUALLY UNRESPONSIVE (VERY SLOW TO TURN). IT SHOULD BE POINTED OUT THAT WE HAD A CHK AIRMAN WHO WAS IN THE COCKPIT TO CERTIFY THE RNAV CAPABILITIES OF THE AIRBUS 330 OVERSEAS AT GATWICK. OVER THE 14 YRS THAT I'VE BEEN FLYING TO GATWICK WITH THIS CARRIER, THIS (WILLO/HOLLY) ARR HAS ALWAYS BEEN A PROB AREA OF UNDERSTANDING. THE LONDON CTLRS ARE EXCELLENT AND HAVE ALWAYS BEEN IN THIS AREA. AT THE PRESENT TIME WE ARE EXPERIENCING NAV/HDG PROBS IN SEQUENCING OVER THE NORTH ATLANTIC. APPARENTLY SOFTWARE UPGRADES/CHANGES ARE BEING MADE. LONDON CTLRS SHOULD BE ADVISED OF THIS PROB AND SHOULD AVOID GIVING US 180 DEG TURNS IMMEDIATELY (A TURN WITH 45 DEGS SHOULD BE INITIALLY GIVEN TO GET ACFT TURNING IN CORRECT DIRECTION AND THEN FOLLOWED BY FINAL DESIRED TURN). THIS WAS CAPT'S SECOND TRIP TO EUROPE ON THIS ACFT. 4 HIGHLY QUALIFIED PLTS IN COCKPIT (91 YRS OF EXPERIENCE). CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE FO STATED THAT THIS PROB WITH THE SLOW TURN RATE WAS PROBABLY ASSOCIATED WITH THE DESIGN OF THE SOFTWARE WITHIN THE FMS/IRS SYS OF THE A330-300. THIS SOFTWARE PROB WAS ALSO INVOLVED IN AT LEAST 2 KNOWN 'FAILURES TO SEQUENCE THE NAT' (WHEN OVER 1 WAYPOINT THE FMS FAILED TO SHIFT TO THE NEXT WAYPOINT). NAT TRACK DEVS EXPERIENCED BY 2 SEPARATE OTHER AIRLINE CHK AIRMEN ON THIS EQUIP. IT WAS ALLEGED THAT THESE 2 TRACK DEVS WERE ASSOCIATED WITH SOFTWARE INTERFACE MALFUNCTIONS AND THAT THE MANUFACTURER OF THE SOFTWARE DID NOT COORD WITH RPTR'S AIRLINE. RPTR STATED THAT 'A MAJOR SOFTWARE CHANGE IS FORTHCOMING TO CORRECT THIS PROB.' IN THIS EVENT, DURING ONE OF MANY REQUIRED RNAV EQUIP CERTIFICATION FLTS, THE FLYING FO DID NOT DISENGAGE THE AUTOPLT TO MAKE A MANUAL HDG CHANGE. HE ADMITS THAT HE SHOULD HAVE. HE CITED AN OLD INBRED TRAINING ISSUE OF NOT DISCONNECTING THE AUTOMATED SYS. HE ALSO SAID TO 'FORGET ALL THE OLD XYZ ACFT STUFF.' FO FEELS THAT THE AUTOPLT/FMS THOUGHT THE ACFT WAS STILL IN THE HOLDING PATTERN DURING THE ATTEMPTED TURN. THE FO (TERMED A 'WHIZ ON THE COMPUTERS') AND THE CHK AIRMAN WERE JUMP SEATING AND COULD NOT MAKE OUT WHY THE ACFT WAS NOT RESPONDING AS IT SHOULD HAVE. EVERYONE IS 'NEW' TO THIS ACFT, THE CAPT HAVING ABOUT 60 HRS TOTAL IN TYPE. SO FAR AS THE RPTR KNOWS, THE ONLY FEEDBACK TO ACFT MANUFACTURER ON THESE EVENTS IS THE METHODOLOGY USED IN SELECTING THE NEW HDG. ACFT MANUFACTURER SAYS TO 'SELECT HDG FIRST, THEN PULL THE HDG/TRACK SELECTOR KNOB.' THE COMPANY IS MONITORING THE SIT BUT IS 'HAMPERED BY THE FACT THAT AN ALL NEW AIRLINE SAFETY BOARD IS IN PLACE.' A COPY OF THIS RPT WAS ALSO SENT TO THE UNION SAFETY OFFICE.

Data retrieved from NASA's ASRS site as of July 2007 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.