Narrative:

Given direct bsv by pit departure control; and then turned over to cle center. While changing to 29.92 I noticed the airspeed did not appear to be responding properly; yet the pitch and directional bars showed proper indications. About that time cle asked us if we were given a heading; we told him no. My nd; which had been showing on course; now showed off course; the captain's showed right of course. I corrected back to course. There were no ECAM's or scratch pad messages at this time. We were then turned over to another controller. At about the same time; we got an ECAM; cabin attendant pr ldg elev fault. Capt handled the ECAM and I flew. While handling the ECAM we were comparing the nd's. Captain's nd showed us off course; to the right (again) and mine showed us on course. We queried ATC and he said we were off course. We switched autopilots to AP1; which seemed to be working fine and the AC returned to course. We then received a scratch pad message; independent operation. Since everything now seemed to be operating normally we determined we could safely navigate to destination. We used FMGC 1; a dr log; high altitude charts and ATC to verify our position with every controller change. No further course issues noted. Maintenance and dispatch were notified. Nd 2 had lost all route data. Captain's all seemed fine. We were unable to access mcdu 2 and pages would display randomly. We did notice a difference in time; distance; and fuel between the mcdu's periodically. The aircraft was not off course during the rest of the flight till short final. On final all speed tape information was lost and nothing could be manually set. The FD didn't indicate a turn to the runway as all approach data was lost on short final. However; as noted; we were already on final so elected to continue using visual references and typical approach speed of about 140 KTS for this airplane and weight. No further incident.

Related reports:

Google
 

Original NASA ASRS Text

Title: A319 flight crew experiences navigational difficulties and eventual FMGC failure during climb. During approach the second FMGC fails removing all FMGC calculated speeds from the airspeed tape. The crew takes over manually and using a typical approach speed of 140 KTS; lands safely.

Narrative: Given direct BSV by PIT Departure Control; and then turned over to CLE Center. While changing to 29.92 I noticed the airspeed did not appear to be responding properly; yet the pitch and directional bars showed proper indications. About that time CLE asked us if we were given a heading; we told him no. My ND; which had been showing on course; now showed off course; the Captain's showed right of course. I corrected back to course. There were no ECAM's or scratch pad messages at this time. We were then turned over to another controller. At about the same time; we got an ECAM; CAB PR LDG ELEV FAULT. Capt handled the ECAM and I flew. While handling the ECAM we were comparing the ND's. Captain's ND showed us off course; to the right (again) and mine showed us on course. We queried ATC and he said we were off course. We switched autopilots to AP1; which seemed to be working fine and the AC returned to course. We then received a scratch pad message; Independent Operation. Since everything now seemed to be operating normally we determined we could safely navigate to destination. We used FMGC 1; a DR log; High Altitude charts and ATC to verify our position with every controller change. No further course issues noted. Maintenance and Dispatch were notified. ND 2 had lost all route data. Captain's all seemed fine. We were unable to access MCDU 2 and pages would display randomly. We did notice a difference in time; distance; and fuel between the MCDU's periodically. The aircraft was not off course during the rest of the flight till short final. On final all speed tape information was lost and nothing could be manually set. The FD didn't indicate a turn to the runway as all approach data was lost on short final. However; as noted; we were already on final so elected to continue using visual references and typical approach speed of about 140 KTS for this airplane and weight. No further incident.

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