Narrative:

Upon pushback from the gate; we were informed by ground that runway 30 RVR was 300; inop; inop. I asked how runway 28's visibility was and they replied 1;800 RVR for runway 28R and no RVR for runway 28L. I asked for the prevailing visibility which was 1/4 mile. According to the 10-9A page; 1/4 NM prevailing visibility was approved. The controller specifically said no RVR on runway 28L not 'inoperative RVR' and he made a point to state mid and rollout RVR inoperative on runway 30. We requested taxi for runway 28L and continued to get updates for the RVR for the other runways. Two separate ground controllers stated RVR for runway 30 and 28R and that there was no RVR on 28L and the prevailing visibility was 1/4 mile. As we approached runway 28R for takeoff; the tower said 28R visibility was 4;000 RVR; no RVR for runway 28L and prevailing visibility was still 1/4 mile. We elected to takeoff on 28L due to the longer runway and our calculated takeoff data was complete. After we were airborne; I studied the 10-9A page and noticed that 28L shows RVR on the chart. The terminology used by all controllers was the same stating no RVR applicable for runway 28L and they did state explicitly if RVR was available and/or inop on all other runways. NOTAMS did not show RVR decommissioned on 28L. So now the confusion is if the charts are wrong about the RVR being controlling for runway 28L or if the controller's terminology was wrong in saying no RVR on runway 28L which led me to believe that prevailing visibility applied. I should have been more proactive in reviewing the 10-9A page where I would have caught the RVR notation. Then I would have queried the controller more thoroughly about RVR applicability to runway 28L and determined if 'no RVR' really meant the equipment is installed and not on or has been removed from that runway.

Related reports:

Google
 

Original NASA ASRS Text

Title: Air carrier departing OAK experienced confusion regarding ATC's terminology regarding RVR readings and status.

Narrative: Upon pushback from the gate; we were informed by Ground that Runway 30 RVR was 300; inop; inop. I asked how Runway 28's visibility was and they replied 1;800 RVR for Runway 28R and no RVR for Runway 28L. I asked for the prevailing visibility which was 1/4 mile. According to the 10-9A page; 1/4 NM prevailing visibility was approved. The Controller specifically said no RVR on Runway 28L not 'inoperative RVR' and he made a point to state mid and rollout RVR inoperative on Runway 30. We requested taxi for Runway 28L and continued to get updates for the RVR for the other runways. Two separate Ground Controllers stated RVR for Runway 30 and 28R and that there was no RVR on 28L and the prevailing visibility was 1/4 mile. As we approached Runway 28R for takeoff; the Tower said 28R visibility was 4;000 RVR; no RVR for Runway 28L and prevailing visibility was still 1/4 mile. We elected to takeoff on 28L due to the longer runway and our calculated takeoff data was complete. After we were airborne; I studied the 10-9A page and noticed that 28L shows RVR on the chart. The terminology used by all Controllers was the same stating no RVR applicable for Runway 28L and they did state explicitly if RVR was available and/or inop on all other runways. NOTAMS did not show RVR decommissioned on 28L. So now the confusion is if the charts are wrong about the RVR being controlling for Runway 28L or if the Controller's terminology was wrong in saying no RVR on Runway 28L which led me to believe that prevailing visibility applied. I should have been more proactive in reviewing the 10-9A page where I would have caught the RVR notation. Then I would have queried the Controller more thoroughly about RVR applicability to Runway 28L and determined if 'no RVR' really meant the equipment is installed and not on or has been removed from that runway.

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.