Takeoff aborted when airspeed differences noted between captain's and first officer's indicators.

Attributes
ACN	200482
Time
Date	199201
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : bli
State Reference	WA
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Dusk
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport
Flight Phase	climbout : takeoff other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 225 flight time total : 9000 flight time type : 2400
ASRS Report	200482
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 100 flight time total : 9100 flight time type : 2600
ASRS Report	200727
Events
Anomaly	aircraft equipment problem : critical other anomaly other other anomaly other
Independent Detector	other flight crewa
Resolutory Action	flight crew : declared emergency flight crew : rejected takeoff
Consequence	Other
Supplementary
Primary Problem	Aircraft

Narrative:

On jan/fri/92 departing from bellingham, wa, first officer was about to fly the leg from bellingham to seattle at xy. All standard and normal company procedure were used as the first officer pushed the tower levers up and asked me to set the power. I called 'airspeed alive, 80 KTS', and as I called 'V1 rotate' (same speed), the first officer said 'no!, there's something wrong.' as the airplane was not rotating I saw no choice but to immediately abort the takeoff and did so instantly. I slammed the thrust levers back, deployed the air brake and lifted spoilers and we both stood on the brakes. We slid off the end of the runway for approximately 150 ft into the grassy muddy overrun area before we stopped. After we had stopped the first officer informed me that his airspeed indicator had lagged about 15 KTS behind my V1 call. We also noted at this point that his altimeter now read 400 ft below sea level (V1 was 106 KTS). Maintenance personnel reported to me the following morning that water had been found in the static system probably from the heavy rains and wind the night before and a test had revealed a discrepancy in airspeed indicator readings between the captain and first officer's sides.

Original NASA ASRS Text

Title: TKOF ABORTED WHEN AIRSPD DIFFERENCES NOTED BTWN CAPT'S AND FO'S INDICATORS.

Narrative: ON JAN/FRI/92 DEPARTING FROM BELLINGHAM, WA, FO WAS ABOUT TO FLY THE LEG FROM BELLINGHAM TO SEATTLE AT XY. ALL STANDARD AND NORMAL COMPANY PROC WERE USED AS THE FO PUSHED THE TWR LEVERS UP AND ASKED ME TO SET THE PWR. I CALLED 'AIRSPD ALIVE, 80 KTS', AND AS I CALLED 'V1 ROTATE' (SAME SPD), THE FO SAID 'NO!, THERE'S SOMETHING WRONG.' AS THE AIRPLANE WAS NOT ROTATING I SAW NO CHOICE BUT TO IMMEDIATELY ABORT THE TKOF AND DID SO INSTANTLY. I SLAMMED THE THRUST LEVERS BACK, DEPLOYED THE AIR BRAKE AND LIFTED SPOILERS AND WE BOTH STOOD ON THE BRAKES. WE SLID OFF THE END OF THE RWY FOR APPROX 150 FT INTO THE GRASSY MUDDY OVERRUN AREA BEFORE WE STOPPED. AFTER WE HAD STOPPED THE FO INFORMED ME THAT HIS AIRSPD INDICATOR HAD LAGGED ABOUT 15 KTS BEHIND MY V1 CALL. WE ALSO NOTED AT THIS POINT THAT HIS ALTIMETER NOW READ 400 FT BELOW SEA LEVEL (V1 WAS 106 KTS). MAINT PERSONNEL RPTED TO ME THE FOLLOWING MORNING THAT WATER HAD BEEN FOUND IN THE STATIC SYS PROBABLY FROM THE HVY RAINS AND WIND THE NIGHT BEFORE AND A TEST HAD REVEALED A DISCREPANCY IN AIRSPD INDICATOR READINGS BTWN THE CAPT AND FO'S SIDES.

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.