Nighttime Visibility Observations: MOR, Lights and Observer Reports

Quick Answer

Nighttime visibility observations need a clear distinction between a visible light and meteorological optical range, or MOR. The distance at which a person can detect a lamp depends on the lamp, the background and the viewing conditions as well as the atmosphere. A forward-scattering sensor estimates MOR from a local optical measurement. The two observations can differ without either being a simple calibration error.

Seeing a distant lamp does not directly establish MOR

A port operator may see a bright light while a nearby sensor reports a much shorter MOR. A road observer may lose sight of a dim object before losing a brighter one at the same distance. Those comparisons involve different visual targets. Treating the farthest visible light as a direct reference for the instrument can produce a misleading fault report.

The American Meteorological Society explanation of Allard's law relates the night visual range of a light to atmospheric extinction, the source and the observer's detection threshold. This is why an arbitrary lamp is not an interchangeable reference target. Brightness, beam direction and background conditions matter.

For an instrument enquiry, first state the required quantity: MOR, a specified visual-observation report, or a separate operational quantity such as runway visual range. Do not ask a supplier to guarantee that a MOR reading always equals the distance to a particular streetlight. The light may not have a stable known intensity, and the line of sight may pass through air that differs from the sensor location.

What the instrument is measuring after dark

MOR is an atmospheric optical quantity rather than a measurement of human eyesight. The Met Office description of visibility measurement defines it using the path length over which luminous flux is reduced to 5% of its initial value. That definition is different from asking whether a person can still see an illuminated sign.

The NiuBoL NBL-W-VS uses forward scattering. Its transmitter illuminates a small atmospheric sampling zone, the receiver detects scattered light, and the processing converts that optical signal into an estimate of MOR. It does not aim at a harbour light or measure the complete road ahead of a driver.

The scattering schematic below represents a localized sampling volume. It is not an observer-to-light sightline. For a fuller comparison of instrument methods, see the forward-scattering visibility sensor guide. A method comparison and a nighttime visual comparison should not be treated as the same test.

Check the selected NBL-W-VS configuration

The atmospheric NBL-W-VS configuration measures 5 m-10 km. At the upper limit, establish how the logger labels capped or out-of-range results rather than presenting the limit as an exact observation of indefinitely clear conditions. A sensor at its reporting ceiling cannot quantify how far actual visibility extends beyond that ceiling.

A manufacturer's range and laboratory specification do not establish agreement with every observer report. Define the reference method and required comparison conditions in the project acceptance plan. For aviation, MOR and runway visual range are distinct quantities; assess the required equipment and operational requirements separately.

Investigate a nighttime disagreement in a useful order

1. Identify exactly what each number represents. Record whether the comparison is MOR, a visual estimate or another reported quantity.
2. Align the observation times. A later observer report and an earlier sensor record may describe different conditions.
3. Record target distance, viewing direction and light conditions. Note whether the light is flashing, partly obscured or directed away from the observer.
4. Compare the observation path with the sensor's surroundings. Local fog, spray, dust or an obstruction can make the two exposures different.
5. Inspect the optical windows, sampling zone, supply and communications. Keep a suspected instrument fault separate from a valid spatial difference.
6. Use a suitable instrument-reference procedure when calibration or accuracy is in question. An uncharacterized light is not that procedure.

Make visual checks from a safe, approved location. A roadside comparison should not require a person to stand in traffic or move into an operationally restricted area. Observation records can support an investigation, but they are not permission to bypass the site's safety arrangements.

Do not calibrate away a difference in meaning

If the sensor reports 600 m MOR and an observer can see a lamp at 1 km, the statement that the sensor is 400 m low is not justified by those two facts alone. The example illustrates unlike quantities; it is not a measured result from a NiuBoL installation. Check the visual target and observation method before changing instrument settings.

Equally, do not dismiss every disagreement as an observer issue. Repeated discrepancies under comparable conditions warrant a review of contamination, siting, the receiving system and instrument performance. Store the original readings while investigating so a software correction does not conceal the evidence needed to find the cause.

Specify a nighttime visibility channel that can be used correctly

Tell NiuBoL the application, required quantity and range, mounting environment, receiving PLC or RTU, reporting interval and intended reference procedure. If the system combines MOR with visual reports, use different field names and retain their observation times. An RS485 Modbus RTU connection can transfer the sensor value; it cannot make unlike observations equivalent.

For ports, roads and industrial sites, the operational response should be defined by the responsible authority or site procedure. Avoid deriving universal stopping distances, closure thresholds or navigation permissions from a single instrument specification. The useful output is a correctly labelled observation delivered to a system that understands its scope.

Project Decision FAQ

Q1. Why can a light remain visible beyond the reported MOR?

A light's visual range depends on its output and direction, the background and the observer's detection conditions as well as the atmosphere. MOR is a separate optical quantity. Visibility of an arbitrary light does not directly validate or invalidate the MOR value.

Q2. Does a forward-scattering sensor need daylight?

No. It uses its own optical transmitter and receiver. Day and night comparisons still need to distinguish instrument MOR from human visual observations and account for representative siting and instrument condition.

Q3. What does a 10 km reading mean on this configuration?

It reaches the upper end of the specified 5 m-10 km range. Check the device status and reporting convention. Do not interpret a capped value as an exact measurement of visibility beyond the sensor's range.

Q4. Is MOR the same as runway visual range?

No. They are distinct quantities. A project requiring runway visual range needs a separate assessment of the measurement system and operational requirements; a MOR register must not simply be renamed RVR.

Q5. What should be recorded before reporting a nighttime fault?

Retain the sensor value and status, observation time, target distance and direction, lighting conditions, local weather and optical-window condition. Establish whether the comparison uses the same quantity before requesting calibration changes.

Summary

Nighttime visibility observations become useful when the reported quantity is clear. Keep MOR separate from the visual range of a lamp, compare observations at the same time and investigate site and instrument conditions before adjusting calibration. This gives operators an interpretable record without claiming that one sensor describes every viewing condition.

Sensor documents

NBL-W-VS visibility sensor instruction manual.