Narrative:

During taxi out for takeoff at sfo we were given a runway change from 1R to 28L. The first officer took responsibility of changing the FMC to the new runway while the relief pilot and I took the responsibility of taxiing the aircraft to the new runway. Upon crossing the runways 1L and 1R the relief pilot assisted the first officer in reprogramming the FMC for the new runway; new noise abatement departure procedure 1 (NADP1) departure and the new SID for 28L. I asked the international relief officer to confirm that the runway analysis for 28L was included in the paperwork in case the performance calculations for [runway] 28L did not show up in time for departure. The relief pilot confirmed that we were good for a runway 28L departure and even confirmed; with the back of the briefing card; that we were ok to use the onboard performance calculations for a runway change. Upon reaching runway 28L we all confirmed that we were able and ready to accept a departure. Runway 28L was verified to be correct during the initiation of the first officer's takeoff roll. Upon setting thrust and after checking the engine instruments I referenced the airspeed indicator to make my '100 KTS' call. No green lines for the v-speeds were present and after glancing at the FMC takeoff page I noticed no numerical values in the v-speed locations; only dashes. I elected to reject the takeoff because the aircraft was still below 100 KTS (around 90) and there was around 10;000 ft of dry runway left to stop the aircraft. We exited the runway at taxiway foxtrot; completed the rejected takeoff checklist; and referenced the brake cooling chart. The decision was made to use a conservative number of 23 minutes of brake cooling (110 KT column) and dispatch was notified of the situation and expected fob for the subsequent takeoff. None of the 3 cockpit crew members can recall seeing amber 'no v-speed' warning on the airspeed indicator none of us could make a conclusion on why there were no v-speeds during the takeoff roll.

Related reports:

Google
 

Original NASA ASRS Text

Title: A B737 flight crew rejected their takeoff when the Captain noted no V-speed settings were displayed.

Narrative: During taxi out for takeoff at SFO we were given a runway change from 1R to 28L. The First Officer took responsibility of changing the FMC to the new runway while the Relief Pilot and I took the responsibility of taxiing the aircraft to the new runway. Upon crossing the runways 1L and 1R the Relief Pilot assisted the First Officer in reprogramming the FMC for the new runway; new Noise Abatement Departure Procedure 1 (NADP1) departure and the new SID for 28L. I asked the IRO to confirm that the runway analysis for 28L was included in the paperwork in case the performance calculations for [Runway] 28L did not show up in time for departure. The Relief Pilot confirmed that we were good for a Runway 28L departure and even confirmed; with the back of the briefing card; that we were ok to use the onboard performance calculations for a runway change. Upon reaching Runway 28L we all confirmed that we were able and ready to accept a departure. Runway 28L was verified to be correct during the initiation of the First Officer's takeoff roll. Upon setting thrust and after checking the engine instruments I referenced the airspeed indicator to make my '100 KTS' call. No green lines for the V-speeds were present and after glancing at the FMC takeoff page I noticed no numerical values in the V-speed locations; only dashes. I elected to reject the takeoff because the aircraft was still below 100 KTS (around 90) and there was around 10;000 FT of dry runway left to stop the aircraft. We exited the runway at Taxiway Foxtrot; completed the RTO Checklist; and referenced the brake cooling chart. The decision was made to use a conservative number of 23 minutes of brake cooling (110 KT column) and Dispatch was notified of the situation and expected FOB for the subsequent takeoff. None of the 3 cockpit crew members can recall seeing amber 'no V-speed' warning on the airspeed indicator none of us could make a conclusion on why there were no V-speeds during the takeoff roll.

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