An A320 flight crew experienced a track deviation on the barin 1 RNAV arrival to iad when the FMGC e...

Attributes
ACN	822000
Time
Date	200902
Local Time Of Day	1201-1800
Place
Locale Reference	IAD.Airport
State Reference	DC
Aircraft 1
Make Model Name	A320
Operating Under FAR Part	Part 121
Route In Use	STAR BARIN ONE
Flight Plan	IFR
Component
Aircraft Component	FMS/FMC
Person 1
Function	First Officer Pilot Not Flying
Experience	Flight Crew Last 90 Days 270 Flight Crew Total 5000 Flight Crew Type 2000
Person 2
Function	Pilot Flying Captain
Experience	Flight Crew Last 90 Days 240 Flight Crew Total 25000 Flight Crew Type 6500
Events
Anomaly	Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types

Narrative:

On the barin arrival with runway 1R in the computer; the waypoint from brv to barin and beyond seem to be erased by the computer. Potomac questioned why we made a left turn after brv; instead of going direct to barin. The computer erased barin and all the points after that; and directed us to go from brv direct to deces; then onto the runway 1R approach course. Deces is an IAF for runway 1R approach. We were given a heading and told to intercept runway 1R localizer. The approach controller mentioned we were the 2nd aircraft today to fly the same ground track on the arrival. I think there may be an issue with the airbus computer erasing points on the barin arrival when runway 1R is loaded as well.callback conversation with reporter revealed the following information: reporter advised the A320 FMGC requires the runway to be selected first and then the associated arrivals. When this sequence is followed the resulting route is brv direct to deces.

Original NASA ASRS Text

Title: An A320 flight crew experienced a track deviation on the BARIN 1 RNAV arrival to IAD when the FMGC entered the DECES transition to the ILS Runway 1R vice flying to BARIN and thence radar vectors per the procedure.

Narrative: On the BARIN arrival with Runway 1R in the computer; the waypoint from BRV to BARIN and beyond seem to be erased by the computer. Potomac questioned why we made a left turn after BRV; instead of going direct to BARIN. The computer erased BARIN and all the points after that; and directed us to go from BRV direct to DECES; then onto the Runway 1R approach course. DECES is an IAF for Runway 1R approach. We were given a heading and told to intercept Runway 1R localizer. The Approach Controller mentioned we were the 2nd aircraft today to fly the same ground track on the arrival. I think there may be an issue with the Airbus computer erasing points on the BARIN arrival when Runway 1R is loaded as well.Callback conversation with reporter revealed the following information: Reporter advised the A320 FMGC requires the runway to be selected first and then the associated arrivals. When this sequence is followed the resulting route is BRV direct to DECES.

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.

An A320 flight crew experienced a track deviation on the barin 1 RNAV arrival to iad when the FMGC entered the deces transition to the ILS runway 1R vice flying to barin and thence radar vectors per the procedure.