A lighthouse can be visible from a ship, yet the tower may be difficult to identify on a radar display among land returns, harbor structures and other targets. A RACON—short for radar beacon—answers a ship’s radar pulse with a coded response. On the display, that response appears as a recognizable line or mark associated with the beacon’s echo. It is an electronic aid to identification, not a replacement for the radar picture or the chart.
From radar pulse to coded response
The U.S. Coast Guard’s Navigation Center describes a RACON as a receiver/transmitter transponder. It receives a radar pulse and transmits an identifiable response back to the radar set. The response is encoded as a Morse character, with the identifying mark beginning with a dash. Because the RACON responds after the structure’s own echo, its coded trace appears behind that echo on the display.
This arrangement links a radar return to a known feature. A ship’s radar may show the coastline, a buoy or a tower as an echo; the coded response gives the operator a way to recognize which marked aid or landmark is being detected. The Coast Guard lists uses including identifying buoys, land-based aids such as lighthouses, landfall positions on inconspicuous coasts, navigable bridge spans, offshore platforms and some environmentally sensitive areas. The exact use depends on the authority and the location.
What a RACON can tell the operator
A RACON can help positively identify the radar echo from the structure on which it is mounted. It can also provide a recognizable reference when a coast has few distinctive visual features. In some places, a beacon’s coded character is shown in chart or navigational publications so that the expected response can be compared with the observed one.
It does not independently provide a safe route or prove that a vessel is at a particular position. The response is related to the beacon’s location and the ship’s radar geometry, but users still need to compare it with the chart, other radar targets and their overall position fixing. Nor does a RACON eliminate uncertainty from poor propagation, clutter or equipment settings. The Coast Guard specifically warns that rain or sea clutter controls and other suppression circuitry may mask or degrade a return.
These limits matter because an electronic mark can look authoritative. The Coast Guard advises that reliance should be placed on a RACON flash only when it is consistent with the expected appearance and the ship is believed to be within the beacon’s quoted range. Unusual propagation can produce spurious flashes at unexpected ranges or positions along a bearing. A single unexplained display mark is therefore not enough to establish identity.
Frequency bands and practical range
A RACON may also have a duty cycle rather than transmitting continuously. The Coast Guard says its U.S. buoy installations are normally active for twenty seconds and then off for twenty seconds, while shore-based RACONs are commonly programmed active for a larger share of the cycle. The stated reason is to conserve battery power on buoys and avoid masking important radar targets. Operating details vary by installation and should be checked in the current relevant publication.
RACON, RAMARK and other radar marks
The Coast Guard distinguishes a RACON from a RAMARK. A RACON responds when interrogated by a ship’s radar; a RAMARK transmits independently without waiting for that radar pulse. A RAMARK return does not provide the same distance indication and appears differently on the display. The distinction is useful because the term “radar beacon” can refer to more than one system.
Modern marine navigation can present many kinds of electronic information, but a RACON is not an AIS message. It is detected through the ship’s radar. An AIS AtoN, by contrast, transmits navigation information over AIS and appears on a compatible electronic display. These technologies can complement one another, but they use different equipment and transmission methods. Confusing the two obscures what the mariner is actually seeing.
How the coded line is interpreted
Display presentation varies by radar model, settings and chart integration. Anti-clutter controls can suppress a weak response, and a radar that is off-tuned may have a reduced detection range. If a return seems absent or malformed, a user should consider those factors alongside the charted information and the equipment manual rather than assuming the physical beacon has failed.
Read a coded trace without measuring its length as distance
Imagine a simplified radar picture with an ordinary echo and a coded extension behind it. The extension is the beacon's response; its drawn length is not the physical size of the lighthouse or the distance from the vessel to a second object. Label the echo, response direction and code separately.
If the code appears on one sweep but not another, several explanations remain possible. The beacon may be in an inactive part of its duty cycle, the radar settings may affect presentation or the received response may be weak. The absence of a recognizable code on one observation is not, by itself, proof that the supporting structure has disappeared.
Compare this with AIS: the RACON reply is triggered by radar, whereas AIS carries a structured message received through different equipment. The same lighthouse may be associated with several kinds of information without making those channels interchangeable. A labeled teaching display helps preserve that distinction; it does not certify current beacon operation.
