Narrative:

On takeoff from vps, the first officer and pilot at the controls announced that he had an airspeed flag in his airspeed indicator. I glanced at his indicator and verified the airspeed flag in view and his airspeed indicator needle appeared to be frozen at 100 KIAS. The captain's airspeed indicator appeared normal with airspeed accelerating through 120 KIAS. In an effort to avoid a high speed abort, I considered taking control of the airplane and executing the takeoff. I determined that a change of controls would not be the safe choice to make. Additionally, I wasn't sure of the cause of the failure of the first officer's indicator and whether or not the captain's indicator might be affected. As the airspeed approached V1 with the aircraft nearing mid field, I called for the abort and took control of the aircraft. A reading of the digital fdr later indicated that the abort was initiated at 141 KIAS. Our computed V1 was 136 KIAS. Additionally it has been brought to my attention by the first officer that he believes now that we may have used the incorrect V1 speed from the weight and data form. He believes the correct V1 speed should have been 133 KIAS. Supplemental information from acn 636485: during takeoff at approximately 80 KTS, first officer noticed momentary airspeed indicator flag. At approximately 100 KTS airspeed, flag returned and airspeed indicator froze. First officer never heard a V1 call and did not have an airspeed indicator. First officer supported captain confirming reversers and spoilers. Made passenger PA and called tower to roll fire trucks. Jumpseater pilot noted he saw maximum speed during sequence of 140 KTS. After rejected takeoff, aircraft came to a stop approximately 1000 ft from runway 1 north end.

Related reports:

Google
 

Original NASA ASRS Text

Title: AFTER LOSING THE FO'S AIRSPD INDICATOR, THE PIC OF AN MD88 PERFORMS A HIGH SPD ABORT NEAR 140 KTS AT VPS.

Narrative: ON TKOF FROM VPS, THE FO AND PLT AT THE CTLS ANNOUNCED THAT HE HAD AN AIRSPD FLAG IN HIS AIRSPD INDICATOR. I GLANCED AT HIS INDICATOR AND VERIFIED THE AIRSPD FLAG IN VIEW AND HIS AIRSPD INDICATOR NEEDLE APPEARED TO BE FROZEN AT 100 KIAS. THE CAPT'S AIRSPD INDICATOR APPEARED NORMAL WITH AIRSPD ACCELERATING THROUGH 120 KIAS. IN AN EFFORT TO AVOID A HIGH SPD ABORT, I CONSIDERED TAKING CTL OF THE AIRPLANE AND EXECUTING THE TKOF. I DETERMINED THAT A CHANGE OF CTLS WOULD NOT BE THE SAFE CHOICE TO MAKE. ADDITIONALLY, I WASN'T SURE OF THE CAUSE OF THE FAILURE OF THE FO'S INDICATOR AND WHETHER OR NOT THE CAPT'S INDICATOR MIGHT BE AFFECTED. AS THE AIRSPD APCHED V1 WITH THE ACFT NEARING MID FIELD, I CALLED FOR THE ABORT AND TOOK CTL OF THE ACFT. A READING OF THE DIGITAL FDR LATER INDICATED THAT THE ABORT WAS INITIATED AT 141 KIAS. OUR COMPUTED V1 WAS 136 KIAS. ADDITIONALLY IT HAS BEEN BROUGHT TO MY ATTN BY THE FO THAT HE BELIEVES NOW THAT WE MAY HAVE USED THE INCORRECT V1 SPD FROM THE WT AND DATA FORM. HE BELIEVES THE CORRECT V1 SPD SHOULD HAVE BEEN 133 KIAS. SUPPLEMENTAL INFO FROM ACN 636485: DURING TKOF AT APPROX 80 KTS, FO NOTICED MOMENTARY AIRSPD INDICATOR FLAG. AT APPROX 100 KTS AIRSPD, FLAG RETURNED AND AIRSPD INDICATOR FROZE. FO NEVER HEARD A V1 CALL AND DID NOT HAVE AN AIRSPD INDICATOR. FO SUPPORTED CAPT CONFIRMING REVERSERS AND SPOILERS. MADE PAX PA AND CALLED TWR TO ROLL FIRE TRUCKS. JUMPSEATER PLT NOTED HE SAW MAX SPD DURING SEQUENCE OF 140 KTS. AFTER REJECTED TKOF, ACFT CAME TO A STOP APPROX 1000 FT FROM RWY 1 N END.

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.