An A320 was released under MEL 34-61 after maintenance stated the navigation database was out of dat...

Narrative:

I believe that an incorrect mel was issued by ZZZ maintenance. Mel 34-61-01 was issued. Preflight was difficult because there was no way to load the route or other entries into the mcdu; but at the time we believed that this was the issue that was covered by the MEL. Later in flight the flight crew became aware that the condition was much worse and was possibly issued the wrong mel. Both fmgcs were found to be inoperative. Associated systems that were affected beyond just the navigation data being out of date included autopilot inoperative; autothrust inoperative; GPWS degraded; pressurization degraded; along with a total loss of all automation afforded from the mcdu. ACARS was accessible. The aircraft was operated without incident; and a safe landing was performed at the intended destination.I believe that the discrepancy should have involved both failed FMGC's and under mel 22-83-01 this does not afford the airplane to be dispatched with both FMGC inoperative. I believe that the maintenance department withheld information from the flight crew and instead of grounding the aircraft affixed a placard that allowed dispatch.

Original NASA ASRS Text

Title: An A320 was released under MEL 34-61 after maintenance stated the NAV DATABASE was out of date. However; incompatible FMGC system software was loaded following the NAV DATABASE OUT OF DATE alert which rendered the FMGC's inoperative for flight.

Narrative: I believe that an incorrect Mel was issued by ZZZ maintenance. Mel 34-61-01 was issued. Preflight was difficult because there was no way to load the route or other entries into the MCDU; but at the time we believed that this was the issue that was covered by the MEL. Later in flight the flight crew became aware that the condition was much worse and was possibly issued the wrong Mel. Both FMGCs were found to be inoperative. Associated systems that were affected beyond just the NAV DATA being out of date included autopilot inoperative; Autothrust inoperative; GPWS degraded; pressurization degraded; along with a total loss of all automation afforded from the MCDU. ACARS was accessible. The aircraft was operated without incident; and a safe landing was performed at the intended destination.I believe that the discrepancy should have involved both failed FMGC's and under Mel 22-83-01 this does not afford the airplane to be dispatched with both FMGC inoperative. I believe that the maintenance department withheld information from the flight crew and instead of grounding the aircraft affixed a placard that allowed dispatch.

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.

Attributes
ACN	957388
Time
Date	201106
Local Time Of Day	0601-1200
Place
Locale Reference	ZZZ.Airport
State Reference	US
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	A320
Operating Under FAR Part	Part 121
Flight Phase	Parked
Flight Plan	IFR
Component
Aircraft Component	FMS/FMC
Person 1
Function	Captain Pilot Not Flying
Qualification	Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 275 Flight Crew Total 23000 Flight Crew Type 10000
Events
Anomaly	Aircraft Equipment Problem Critical Deviation - Procedural MEL Deviation - Procedural Published Material / Policy

An A320 was released under MEL 34-61 after maintenance stated the navigation database was out of date. However; incompatible FMGC system software was loaded following the navigation database out of date alert which rendered the FMGC's inoperative for flight.