A320
Flight Crew Last 90 Days 225; Flight Crew Total 16000; Flight Crew Type 3000
Situational Awareness
Aircraft Equipment Problem Less Severe
Flight Crew FLC Overrode Automation; Flight Crew Became Reoriented
Aircraft; Procedure
The Airbus FMGC; had it been followed during the HHOOD 2 RNAV arrival into PDX; would have descended the aircraft below the published MEA. The FMGC was checked prior to descent.  With the proper 280 knot descent programmed; the FMGC would have descended the aircraft below the published MEA of 7200 feet between HHOOD and BLRUN.  It is a continuing problem with the programming of the Airbus FMGC; it is trying to set up to handle a 'TOO STEEP PATH' alert after SHAFR; and thinks the aircraft needs to be at 7090 feet at BLRUN in order to meet the later requirements. This has not been a formal ATC issue because PDX approach normally starts vectoring us off the arrival and assigning a Minimum Radar Vector Altitude (which is different than an MEA) prior to reaching BLRUN.  However...if we had descended via the RNAV arrival all the way to SHAFR and beyond; we would have been below the MEA. This is a continuing Airbus problem that needs to be addressed by the fleet and the FAA.  It is a potential violation or accident waiting to happen.
Reporter states that a restriction must be manually entered at BLRUN to prevent the aircraft from descending below the MEA. He believes the MVA at BLRUN is 7000 feet.
A320 First Officer reports that when the HHOOD 2 RNAV arrival to PDX landing Runways 28L and R is entered in the FMGC; the MEA of 7200 feet between HHOOD and BLRUN is not honored. Manual entries to the FMGC are required to keep the aircraft above 7200 feet until after BLRUN.