Narrative:

On initial climb out of ZZZ lost both captain and first officer's primary altimeters and airspeed indicators. Emergency declared, returned to ZZZ. Using standby airspeed and altimeter. Potential conflict with another aircraft on approach. We overshot runway 18R traffic on runway 18L. No breakout required. Not sure of actual distance between aircraft. Landed uneventfully. Emergency was declared to ensure altitude protection for standby operations. Could have been much worse if IMC conditions. Conditions were set to broken at 4000 ft. Callback conversation with reporter revealed the following information: the reporter stated the #2 air data computer system had a long and chronic maintenance history of malfunctions. The reporter said the system was worked on again overnight, but either did not complete the work or was not fixed. The reporter stated maintenance reported the #1 system air data computer was used for troubleshooting the #2 system and was not connected into the #1 system after troubleshooting. The reporter said there were not inoperative flags showing on the #1 system. Callback from acn 593167: the reporter stated the dual failure was caused by the #1 air data computer not being connected and the complete failure of #2 air data computer system. The reporter said maintenance had worked the #2 air data computer system, but not fixed the problem.

Google
 

Original NASA ASRS Text

Title: A B737-200 ON CLB OUT AT 1000 FT DECLARED AN EMER AND DIVERTED DUE TO LOSS OF PRIMARY ALTIMETERS AND AIRSPEED INDICATORS. STANDBY INDICATORS OK.

Narrative: ON INITIAL CLB OUT OF ZZZ LOST BOTH CAPT AND FO'S PRIMARY ALTIMETERS AND AIRSPEED INDICATORS. EMER DECLARED, RETURNED TO ZZZ. USING STANDBY AIRSPEED AND ALTIMETER. POTENTIAL CONFLICT WITH ANOTHER ACFT ON APCH. WE OVERSHOT RWY 18R TFC ON RWY 18L. NO BREAKOUT REQUIRED. NOT SURE OF ACTUAL DISTANCE BTWN ACFT. LANDED UNEVENTFULLY. EMER WAS DECLARED TO ENSURE ALT PROTECTION FOR STANDBY OPS. COULD HAVE BEEN MUCH WORSE IF IMC CONDITIONS. CONDITIONS WERE SET TO BKN AT 4000 FT. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR STATED THE #2 AIR DATA COMPUTER SYSTEM HAD A LONG AND CHRONIC MAINT HISTORY OF MALFUNCTIONS. THE RPTR SAID THE SYSTEM WAS WORKED ON AGAIN OVERNIGHT, BUT EITHER DID NOT COMPLETE THE WORK OR WAS NOT FIXED. THE RPTR STATED MAINT RPTED THE #1 SYSTEM AIR DATA COMPUTER WAS USED FOR TROUBLESHOOTING THE #2 SYSTEM AND WAS NOT CONNECTED INTO THE #1 SYSTEM AFTER TROUBLESHOOTING. THE RPTR SAID THERE WERE NOT INOP FLAGS SHOWING ON THE #1 SYSTEM. CALLBACK FROM ACN 593167: THE RPTR STATED THE DUAL FAILURE WAS CAUSED BY THE #1 AIR DATA COMPUTER NOT BEING CONNECTED AND THE COMPLETE FAILURE OF #2 AIR DATA COMPUTER SYSTEM. THE RPTR SAID MAINT HAD WORKED THE #2 AIR DATA COMPUTER SYSTEM, BUT NOT FIXED THE PROB.

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