A319 flight crew experiences FMGC failures while being vectored for approach when no STAR is selecte...

Narrative:

Turning base leg for ILS parallel approaches in progress 2;000 foot ceiling; captain (an airbus lca) asked me to 'clean up box.' I selected no STAR and extended one of the fixes. While on base leg; cabin pr ldg elev fault ECAM annunciated; (usually a sign of FMGC 1 having a problem in my experience). While starting to sort this out; we were given a turn to intercept localizer (northeast hdg) and a speed to maintain until the marker. During the next 20-30 seconds; things got a little confusing. Things I'm pretty sure happened were the uncommanded autopilot disengagement and associated sound; my ILS symbology disappearing; 2fd2 FMA on my side; followed by 1fd2 and the cabin pr ECAM sounding again; captain losing his map display as we had different ranges selected; a few mcdu messages on my side opp FMGC/independent operation; etc; and me finally selecting ls (raw) on my nav display. At that point; I saw what I thought was localizer south of us and told captain we need to come right. Within a few moments of that; ATC advised us we were 'capturing the wrong localizer and to turn right to 180 degrees and maintain 3;000 ft.' captain gave me the aircraft and started a dialog with ATC describing our situation and requested a vector to visual conditions (again 2;000 foot ceiling). Once that was sorted out; we were vectored for an IMC descent to a visual. What was troubling from this point was both of us ultimately ended up in stby navigation with the proper ILS frequency/course tuned; and I had selected the correct ILS on MCDU2/FMGC2 (mine); yet the identifier remained steady on [the original runway] for both of us the entire time with what appeared to be erroneous glideslope indications. The identifier for the original planned runway; I presume was stored in FMGC 1. Not sure if this is an anomaly or just how the system works? Fortunately it was VFR below the cloud deck! Uneventful landing /taxi back. Mcdu still locked/not responding to any button pushing even after shutdown. Wrote up maintenance item FMGC 1 fail.

Original NASA ASRS Text

Title: A319 flight crew experiences FMGC failures while being vectored for approach when No STAR is selected in the FMGC to clean up the map display. ATC is advised and vectors for a visual approach are provided.

Narrative: Turning base leg for ILS parallel approaches in progress 2;000 foot ceiling; Captain (an airbus LCA) asked me to 'Clean up box.' I selected NO STAR and extended one of the fixes. While on base leg; Cabin PR LDG ELEV Fault ECAM annunciated; (usually a sign of FMGC 1 having a problem in my experience). While starting to sort this out; we were given a turn to intercept Localizer (northeast hdg) and a speed to maintain until the marker. During the next 20-30 seconds; things got a little confusing. Things I'm pretty sure happened were the uncommanded autopilot disengagement and associated sound; my ILS symbology disappearing; 2FD2 FMA on my side; followed by 1FD2 and the Cabin Pr ECAM sounding again; Captain losing his map display as we had different ranges selected; a few MCDU messages on my side OPP FMGC/Independent Operation; etc; and me finally selecting LS (RAW) on my Nav display. At that point; I saw what I thought was LOC south of us and told Captain we need to come right. Within a few moments of that; ATC advised us we were 'capturing the wrong Localizer and to turn right to 180 degrees and maintain 3;000 FT.' Captain gave me the aircraft and started a dialog with ATC describing our situation and requested a vector to visual conditions (again 2;000 foot ceiling). Once that was sorted out; we were vectored for an IMC descent to a visual. What was troubling from this point was both of us ultimately ended up in STBY NAV with the proper ILS frequency/course tuned; and I had selected the correct ILS on MCDU2/FMGC2 (mine); yet the identifier remained steady on [the original runway] for both of us the entire time with what appeared to be erroneous glideslope indications. The identifier for the original planned runway; I presume was stored in FMGC 1. Not sure if this is an anomaly or just how the system works? Fortunately it was VFR below the cloud deck! Uneventful landing /taxi back. MCDU still locked/not responding to any button pushing even after shutdown. Wrote up Maintenance item FMGC 1 Fail.

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

Attributes
ACN	1145867
Time
Date	201401
Local Time Of Day	0601-1200
Place
Locale Reference	ZZZ.TRACON
State Reference	US
Environment
Flight Conditions	IMC
Aircraft 1
Make Model Name	A319
Operating Under FAR Part	Part 121
Flight Phase	Final Approach
Flight Plan	IFR
Component
Aircraft Component	FMS/FMC
Person 1
Function	First Officer Pilot Not Flying
Experience	Flight Crew Last 90 Days 200 Flight Crew Total 10000 Flight Crew Type 2900
Person 2
Function	Pilot Flying Captain
Qualification	Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 180 Flight Crew Total 13000 Flight Crew Type 9000
Events
Anomaly	Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Deviation - Track / Heading All Types

A319 flight crew experiences FMGC failures while being vectored for approach when no STAR is selected in the FMGC to clean up the map display. ATC is advised and vectors for a visual approach are provided.