Narrative:

On final approach with flaps 2 degrees; we received an overspd warning. Looking at my airspeed indicator; I saw that we were on speed and at the correct airspeed. The first officer's airspeed indicator was showing 20 KTS faster and thus the overspd warning. Crosschecked the standby airspeed indicator and it was closer to the first officer's airspeed. I clicked off the autoplt and autothrottles to maintain airspeed between minimum and maximum; which wasn't that large a margin since we were already configuring. We continued with the approach; because although in rain and IMC to about 600 ft; I felt that was a safer course of action than trying to go missed approach in heavy rain IMC when we were more on a stabilized approach at that point. The rest of the approach was uneventful with no additional overspd/underspd warnings and landed approximately 2000 ft down runway xxr in ZZZ. Debriefed maintenance once we arrived at the gate of the problem. Supplemental information from acn 795835: I believe there was a human factors issue of pressing on. In other words of trying to complete the mission that we were on instead of breaking off the approach when the discrepancy was first noticed. I think the approach should have been discontinued and some time taken in a less task saturated phase of flight to properly ascertain the airspeed discrepancy and then flying the approach with the first officer as the PF instead of the captain trying to xchk the airspeed constantly. Also; I believe the approach speed was flown 5-9 KTS fast as he was fighting the tendency not to get too slow even though his airpsd indicator read erroneously slow.

Related reports:

Google
 

Original NASA ASRS Text

Title: AN A320 CAPT CONTINUED AN IMC ILS APCH WITH A 20 KT AIRSPEED DIFFERENCE BETWEEN THE CAPT'S; FO'S AND STBY AIRSPEED INDICATORS.

Narrative: ON FINAL APCH WITH FLAPS 2 DEGS; WE RECEIVED AN OVERSPD WARNING. LOOKING AT MY AIRSPD INDICATOR; I SAW THAT WE WERE ON SPD AND AT THE CORRECT AIRSPD. THE FO'S AIRSPD INDICATOR WAS SHOWING 20 KTS FASTER AND THUS THE OVERSPD WARNING. XCHKED THE STANDBY AIRSPD INDICATOR AND IT WAS CLOSER TO THE FO'S AIRSPD. I CLICKED OFF THE AUTOPLT AND AUTOTHROTTLES TO MAINTAIN AIRSPD BTWN MINIMUM AND MAX; WHICH WASN'T THAT LARGE A MARGIN SINCE WE WERE ALREADY CONFIGURING. WE CONTINUED WITH THE APCH; BECAUSE ALTHOUGH IN RAIN AND IMC TO ABOUT 600 FT; I FELT THAT WAS A SAFER COURSE OF ACTION THAN TRYING TO GO MISSED APCH IN HVY RAIN IMC WHEN WE WERE MORE ON A STABILIZED APCH AT THAT POINT. THE REST OF THE APCH WAS UNEVENTFUL WITH NO ADDITIONAL OVERSPD/UNDERSPD WARNINGS AND LANDED APPROX 2000 FT DOWN RWY XXR IN ZZZ. DEBRIEFED MAINT ONCE WE ARRIVED AT THE GATE OF THE PROB. SUPPLEMENTAL INFO FROM ACN 795835: I BELIEVE THERE WAS A HUMAN FACTORS ISSUE OF PRESSING ON. IN OTHER WORDS OF TRYING TO COMPLETE THE MISSION THAT WE WERE ON INSTEAD OF BREAKING OFF THE APCH WHEN THE DISCREPANCY WAS FIRST NOTICED. I THINK THE APCH SHOULD HAVE BEEN DISCONTINUED AND SOME TIME TAKEN IN A LESS TASK SATURATED PHASE OF FLT TO PROPERLY ASCERTAIN THE AIRSPD DISCREPANCY AND THEN FLYING THE APCH WITH THE FO AS THE PF INSTEAD OF THE CAPT TRYING TO XCHK THE AIRSPD CONSTANTLY. ALSO; I BELIEVE THE APCH SPD WAS FLOWN 5-9 KTS FAST AS HE WAS FIGHTING THE TENDENCY NOT TO GET TOO SLOW EVEN THOUGH HIS AIRPSD INDICATOR READ ERRONEOUSLY SLOW.

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