Date: 201302
Location: PHX.Airport, AZ
Flight conditions: VMC
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Aircraft component: Altimeter
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Human factors: Human-Machine Interface; Confusion
Second reporter function: Pilot Not Flying; Captain
Anomaly: Aircraft Equipment Problem Critical; Deviation - Altitude Crossing Restriction Not Met; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem; Flight Crew Returned To Clearance
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: We were nearing the top of descent on our filed and cleared route that included the KOOLY RNAV STAR to PHX. We expected and briefed the arrival for Runway 25L. We then received a clearance to fly direct to SQUEZ and descend via the KOOLY4 for landing Runway 25L. We set the MCP [altitude alert] to 4;000 FT for a managed descent. In the descent I realized that it was time for a new ATIS so I requested one through ACARS. Upon passing FL180 we set the altimeters to the just received ATIS altimeter setting (30.37). I am not certain of the exact sequence of the following events; but we received a clearance to delete the speeds on the arrival and change to Runway 25R. This runway does not have an ILS; so we needed to spend some time determining what approach page matches the identifier in the FMGC; in this case I believe it was RNAV Y 25R. About this time we were crossing SQUEZ and the Controller informed us ATIS was now Tango and the new altimeter setting. We reset our altimeters; and I requested the new ATIS since we had Sierra. After resetting to the new setting (30.03) we realized that this was a large difference. Soon the Captain discovered that I had requested; received; and told him the altimeter for PDX and not PHX. At this point we realized that we had likely crossed SQUEZ low.The rest of the flight was normal. The approach planning and briefing was conducted in a non hurried manner which included review of the NOTAMs and runway performance. The Captain is conscientious and disciplined; and he creates an atmosphere in which I should be able to perform my best. In the future I will read the ATIS line by line to try to avoid making the same mistake.


Second narrative: It is certainly possible the Controller issued the altimeter setting during the descent; but we either misheard or were possibly distracted with a route change shortly before SQUEZ.I will certainly give extra scrutiny to ATIS requests; particularly where airport identifiers could be easily entered as a similar airport; such as PDX and PHX or SNA and SAN.


Synopsis: When the First Officer aboard the A320 inadvertently picked up the ATIS for PDX vice their destination; PHX; the altimeter thus obtained may have caused the flight to cross their active waypoint; SQUEZ below the required 15;000/12;000 FT window before they discovered their error.