geoprimsField-grade geospatial math

RVR and visibility

RVR versus prevailing visibility, the 91.175(h) table that converts one to the other, and the chart legend's longer table.

For pilots · updated 2026-10-20

Planning and education aid. Not for primary navigation. Full disclaimer

An approach chart may give its visibility minimum as RVR 2400. If the runway’s RVR is not being reported, that number becomes 1/2 statute mile. The conversion is a seven-row table in 14 CFR 91.175(h), and it is not interpolated.

The rest of this page explains why there are two measures of visibility at all, and how to read the table without inventing rows it does not have.

Two ways to measure how far you can see

Prevailing visibility is what a weather report gives you. An observer, or an automated sensor, judges how far you can see around the airport. A METAR reports it in statute miles, like 1/2SM. It describes the airport as a whole.

Runway visual range (RVR) is narrower and more precise. The Instrument Procedures Handbook defines it as an instrument-derived value for how far a pilot sees down the runway from the approach end. A transmissometer near the touchdown zone measures how clear the air is, and the system works out how far the runway lights or other targets would be visible. It is reported in hundreds of feet, like R16/2400FT.

Two details in that definition matter:

When a runway has RVR and it is reported, it is the number that counts for that runway’s minimums. The handbook says RVR is used in place of prevailing visibility for a particular runway.

When RVR is not reported

Sometimes the chart’s minimum is an RVR value but nobody is reporting RVR for your runway. The sensor may be out of service, or the runway may not have one.

For that case, 91.175(h)(1) says the RVR minimum is converted to ground visibility using the table in (h)(2), and that visibility becomes the minimum. This applies to takeoff and landing minimums, except Category II and III minimums.

Here is the whole table:

Reading the table honestly

Notice what the table is not. It is not a unit conversion. 2,400 feet is not half a mile; half a mile is 2,640 feet. The rows pair minimums that the FAA treats as comparable, and the gaps between them are uneven: 1,600 to 2,400 ft is a quarter mile, but 4,000 to 4,500 ft is an eighth.

That is why a calculator should not draw a line between rows. An RVR of 2,800 feet does not have a regulation value. If an approach printed an RVR the table lacks, the honest answer is that the table does not cover it, not a number made up halfway between two rows.

The chart legend’s longer table

The FAA’s approach chart books carry a longer version in their legend. It keeps the regulation’s seven rows, marked with a star, and adds eight more, from 1,200 to 5,500 ft. It also adds a rule the regulation lacks: for an RVR between rows, use the next higher listed RVR. The legend’s own example turns 4,800 RVR into 5,000 RVR, which is 1 mile.

The legend is careful about one thing. Its starred rows, the ones copied from 91.175, are the ones to use for takeoff or landing minimums. The extra rows help with other conversions, like adjusting a visibility minimum, and a calculator should say so when it uses one.

A worked example

You are planning an ILS whose chart lists the minimum as RVR 2400. The METAR shows no RVR group for your runway, and the NOTAMs say the touchdown sensor is out.

Now check the METAR’s prevailing visibility against that. If it says 3/4SM, you meet the converted minimum. If it says 1/4SM, you do not.

Two cautions. First, the conversion does not apply to Category II or III minimums; those need RVR. Second, your operator may have rules stricter than Part 91. Commercial operators often do.

The RVR to visibility tool looks up any row of the regulation’s table and refuses values it does not hold; set its table to the legend to use the longer one, with a caution on the rows the regulation lacks. The METAR decoder reads the visibility and any RVR groups out of a report, and the approach category tool finds which column of minimums is yours.

Try it: RVR to ground visibility

The calculator below is the real tool, running its worked example. Change any value; nothing leaves your device.

1/2

Without an RVR report, RVR 2,400 ft is 1/2 statute mile.

Ground visibility (decimal)
RVR row used
When it applies
Rules as of
Provenance
Computed by
aviation.ifr.rvr-visibility 1.1.0, core 0.1.0
Model
Table lookup, 14 CFR 91.175(h)(2): RVR 1,600, 2,400, 3,200, 4,000, 4,500, 5,000, and 6,000 ft are 1/4, 1/2, 5/8, 3/4, 7/8, 1, and 1 1/4 statute miles; no interpolation. Optionally the chart legend's table of 15 rows from 1,200 to 6,000 ft, taking the next higher listed RVR between rows
Accuracy
Exact to the regulation's table; values between rows are not in the rule and are refused
Notes
None
Cites
FAA (eCFR), 14 CFR 91.175(h), Comparable values of RVR and ground visibility; FAA Aeronautical Information Services, Terminal Procedures Publication legend, Comparable Values of RVR and Visibility

Open the full tool, with your values →

Your values

Showing an example. Change anything.
More options 1

Tools for this

Sources

Every number on this page comes from the tools above, which cite their sources on their own pages under "How we got this." Found a mistake? Use "Report a problem" at the bottom of the page.