A321
Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Confusion; Situational Awareness; Training / Qualification
Deviation / Discrepancy - Procedural Published Material / Policy
General None Reported / Taken
Equipment / Tooling; Software and Automation
During pre-flight programming of the MCDU; Takeoff Performance page; I noticed the loaded EOAA (Engine out Acceleration Altitude) was too low by 520 feet. The EOAA that was downloaded vis ACARS was 3;180; but the EOAA for Runway XXR was 3;700 feet for Flaps 1; which we were using. Most of the time the ACARS-loaded EOAA value is normally within 30 feet; but this one was 520 feet too low! I have also noticed in a past flight from ZZZ1 Runway XY; that the EOAA was over 700 feet too low with reference to company data.In accordance with the Ops Manual; crews are to verify the accuracy of the EOAA when programming the MCDU for flight. However; if this is missed; the potential for a near mishap is significant.  I lack the technical knowledge in this matter to make a specific recommendation.  The requirement here is to ensure the EOAA value found in performance data is the same as the EOAA value that gets downloaded via ACARS in the MCDU.
A321 pilot reported the ACARS generated Eng Out Acceleration Altitude (EOAA) was not the same as the pilot company data recommended EOAA for this aircraft configuration and runway in use.