<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>RF Coverage on Counter UAV Radar — Low-Altitude Surveillance Radar</title>
    <link>https://www.counteruavradar.com/en/tags/rf-coverage/</link>
    <description>Recent content in RF Coverage on Counter UAV Radar — Low-Altitude Surveillance Radar</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Sun, 11 Oct 2026 00:00:00 +0800</lastBuildDate>
    <atom:link href="https://www.counteruavradar.com/en/tags/rf-coverage/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Remote ID Reception Range: What Actually Changes It?</title>
      <link>https://www.counteruavradar.com/en/knowledge-base/remote-id-reception-range-what-actually-changes-it/</link>
      <pubDate>Tue, 13 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://www.counteruavradar.com/en/knowledge-base/remote-id-reception-range-what-actually-changes-it/</guid>
      <description>&lt;p&gt;Remote ID reception range is often discussed as if it were a single performance number. In practice, it is not. It is the result of a radio link, and radio links are shaped by transmitter behavior, receiver design, antenna characteristics, path loss, and the environment between the aircraft and the receiving system.&lt;/p&gt;&#xA;&lt;p&gt;That distinction matters because buyers and operators regularly mix together three different questions. One is a compliance question: does the aircraft broadcast Remote ID information? Another is a consumer-receiver question: can a nearby phone or handheld app hear it? The third is a system-design question: can a site reliably receive and use those messages in the sectors and distances that matter operationally? Those are related questions, but they are not the same.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
