![\"\"](\"https:\/\/midradar.com\/wp-content\/uploads\/2026\/09\/border-surveillance-radar-1.webp\")
Border Surveillance Radar: How It Protects 1,000+ km Lines<\/p><\/div>\n
What “Border Surveillance Radar” Actually Covers<\/h2>\n
The term gets used loosely. In practice it spans two distinct radar classes doing different jobs along the same line:<\/p>\n
- \n
- Ground\/surface surveillance radar: tracks personnel, vehicles, and vessels moving along or across the line, typically out to tens of kilometers.<\/li>\n
- S\u00e9curit\u00e9 de l'espace a\u00e9rien \u00e0 basse altitude radar de surveillance<\/a>: tracks aircraft, UAVs, and other airborne threats crossing the line at altitude, layered on top of the ground picture.<\/li>\n<\/ul>\n
A border project rarely deploys just one. A river crossing needs vessel detection; a mountain pass needs vehicle and personnel detection; an airspace corridor above either needs UAV detection. The radar mix follows the terrain, not the other way around.<\/p>\n
Why Long, Remote Border Lines Are a Different Engineering Problem<\/h2>\n
A 5 km perimeter around a facility and a 500 km desert border segment are not the same design problem, even though both use “surveillance radar.” Three things change at border scale:<\/p>\n
Power and connectivity thin out. Sites are often off-grid or on limited solar\/generator budgets, which is why radar power draw (measured in watts, not just detection range) becomes a real selection criterion rather than a footnote.<\/p>\n
Terrain and climate swing wider. A single border line can cross desert heat, coastal humidity, and winter cold in the same deployment plan, which is why environmental ratings (operating temperature and ingress protection) matter as much as range figures.<\/p>\n
Target mix is unpredictable. The same stretch of line may need to flag a person on foot, a smuggling vehicle, a small boat, and a UAV overflight, each with a different radar cross-section (RCS) and therefore a different real-world detection range even from the same unit.<\/p>\n
Midradar’s own deployment base covers 1,000+ km of border and coastline across installed projects, which is the practical reference point for this article: the specification approach below reflects what that scale of deployment actually requires, not a theoretical range figure from a datasheet.<\/p>\n
The Two Radar Layers: MR-RDG (Ground\/Surface) vs. MR-RDA (Low-Altitude)<\/h2>\n
Both series are X-band or Ku-band AESA\/DBF radar, but they’re specified against different target sets. The table below uses only the ranges published for each model; where a range is tied to a specific radar cross-section (RCS) assumption, that’s noted rather than smoothed over.<\/p>\n
\n\n
\n Mod\u00e8le<\/td>\n Radar type<\/td>\n Personnel range<\/td>\n Vehicle \/ small boat range<\/td>\n Large vessel \/ aircraft range<\/td>\n Azimuth coverage<\/td>\n Alimentation<\/td>\n Environmental rating<\/td>\n<\/tr>\n \n MR-RDG50K<\/td>\n 1-D X-band AESA<\/td>\n \u226515 km<\/td>\n \u226525 km<\/td>\n \u226550 km<\/td>\n 90\u00b0<\/td>\n \u2264200 W<\/td>\n IP67, -40\u00b0C to +55\u00b0C<\/td>\n<\/tr>\n \n MR-RDG20K<\/td>\n 1-D X-band AESA<\/td>\n \u226510 km<\/td>\n \u226515 km<\/td>\n \u226525 km<\/td>\n 95\u00b0<\/td>\n \u2264140 W<\/td>\n IP67<\/td>\n<\/tr>\n \n MR-RDG07K<\/td>\n X-band AESA (9.55\u20139.75 GHz)<\/td>\n \u226510 km @ RCS 0.5 m\u00b2<\/td>\n \u226515 km @ RCS 5 m\u00b2<\/td>\n \u226525 km @ RCS 10 m\u00b2<\/td>\n 90\u00b0<\/td>\n 20 W transmit, \u2264140 W total<\/td>\n IP67<\/td>\n<\/tr>\n \n MR-RDG06K<\/td>\n Compact 1-D X-band AESA<\/td>\n \u22655 km<\/td>\n \u22658 km<\/td>\n \u226516 km<\/td>\n \u2014<\/td>\n \u226475 W<\/td>\n IP67, \u22645 kg<\/td>\n<\/tr>\n \n MR-RDG03K<\/td>\n Compact 1-D DBF Ku-band<\/td>\n \u22653 km<\/td>\n \u22656 km<\/td>\n \u226510 km<\/td>\n \u2014<\/td>\n \u226485 W<\/td>\n IP67<\/td>\n<\/tr>\n \n MR-RDG03-4R<\/td>\n Four-sided 1-D DBF Ku-band<\/td>\n \u22653 km<\/td>\n \u22656 km<\/td>\n \u226510 km<\/td>\n 90\u00b0\/face (see note below)<\/td>\n \u2014<\/td>\n IP67<\/td>\n<\/tr>\n \n MR-RDA15K-4R<\/a><\/td>\n Four-array 2-D AESA 3D<\/td>\n \u2014<\/td>\n \u22658 km (vehicle\/helicopter)<\/td>\n Small UAV \u22655 km, altitude to 1,500 m<\/td>\n 360\u00b0, elevation -2\u00b0 to 45\u00b0<\/td>\n \u22641.6 kW total<\/td>\n IP66 system \/ IP67 host<\/td>\n<\/tr>\n \n MR-RDA10K-4R<\/a><\/td>\n X-band 2-D phased array, monopulse<\/td>\n \u226512 km<\/td>\n \u226515 km (vehicles\/ships)<\/td>\n Small UAV (RCS 0.01 m\u00b2) \u226510 km clear weather<\/td>\n 90\u00b0\/face, 360\u00b0 four-face<\/td>\n \u2014<\/td>\n \u2014<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n The MR-RDG line covers everything from a compact 5 kg unit for short gaps to a 50 km-class unit for open coastline; the MR-RDA line adds the airborne layer that ground\/surface radar doesn’t see.<\/p>\n
![\"\"](\"https:\/\/midradar.com\/wp-content\/uploads\/2026\/09\/border-surveillance-radar-2.webp\")
Border Surveillance Radar: How It Protects 1,000+ km Lines<\/p><\/div>\n
How Range Actually Changes With Target Type, and Why That Matters for Procurement<\/h2>\n
The MR-RDG07K datasheet is the clearest illustration of why a single “detection range” number is misleading: the same radar reaches 25 km against a 10 m\u00b2 target (a large vehicle or boat), 15 km against a 5 m\u00b2 target, and 10 km against a 0.5 m\u00b2 target (a person). Radar cross-section, not the radar alone, sets the effective range. A procurement spec that asks only “what’s the detection range” without naming the target RCS will get a technically true but operationally useless number.<\/p>\n
This is also why the MR-RDA10K-4R’s small-UAV figure (\u226510 km against a 0.01 m\u00b2 target) is qualified as “clear weather” rather than stated as an unconditional maximum. Small UAVs are the lowest-RCS target class most border projects need to detect, so their range figure is the most weather-sensitive one on a spec sheet, and worth confirming against the actual regional climate at quote stage.<\/p>\n
Multi-Sensor Integration for Border Command Centers<\/h2>\n
Radar alone gives a track; it doesn’t give visual confirmation. Border deployments pair radar with electro-optical\/thermal cameras in a radar-vision fusion arrangement, where the radar track cues the camera to slew to the target automatically rather than requiring an operator to manually steer toward every alert. For integration into an existing command platform, VMS, or C2 system, the relevant open standards are GB\/T 28181, ONVIF, and RTSP, alongside RESTful APIs and SDKs for deeper platform-level integration. These are the protocols to confirm compatibility against before specifying a system, rather than assuming proprietary lock-in.<\/p>\n
Compared to single-sensor approaches still common on older or lower-budget border segments (seismic\/PIR ground sensors, or camera-only towers with no radar cueing), a radar-cued, multi-sensor layer reduces the operator workload of manually scanning wide, low-activity stretches of line for the handful of genuine crossings per shift.<\/p>\n
Two Deployment Edge Cases Worth Asking About Before You Order<\/h2>\n
MR-RDG03-4R azimuth coverage.\u00a0The published spec page lists 90\u00b0 per face for this four-sided unit but doesn’t explicitly confirm whether the intended full-azimuth (360\u00b0) coverage is achieved by the four faces working as one assembled system or needs to be verified per installation. For a project relying on this unit for gapless perimeter coverage, confirm the assembled-system azimuth figure directly with a current datasheet rather than assuming 4 \u00d7 90\u00b0 automatically equals 360\u00b0 with no overlap or blind arc.<\/p>\n
MR-RDA10K-4R conflicting spec pages.\u00a0This model has two published product pages listing materially different specifications under the same model name. Until that’s resolved on the manufacturer side, treat any MR-RDA10K-4R figure as provisional and request a signed, current datasheet before it goes into a bid or design document \u2014 this is exactly the kind of discrepancy that causes rework late in a procurement cycle if it’s caught after equipment has shipped rather than before the quote is finalized.<\/p>\n
A Framework for Specifying Border Radar Coverage<\/h2>\n
- \n
- Segment the line by terrain and target mix.Desert, coastline, river crossing, and mountain pass each imply a different radar class and range requirement; map this before selecting models, not after.<\/li>\n
- Set the range requirement against the smallest relevant RCS, not the largest. If personnel detection matters, size the radar to the personnel range figure, not the large-vessel figure on the same datasheet.<\/li>\n
- Check power and connectivity against the actual site.A 1.6 kW system needs grid or substantial generator capacity; a sub-100 W unit is viable on solar in most climates.<\/li>\n
- Confirm environmental rating against the harshest point on the segment, not the average. A line that touches both desert heat and coastal salt air needs the rating validated for both.<\/li>\n
- Decide the airborne layer separately from the ground layer.If UAV or low-altitude aircraft threats are in scope, MR-RDA-series coverage is a separate line item, not something the ground\/surface radar picture already includes.<\/li>\n
- Request the current signed datasheet for any model with a known spec discrepancy(see edge cases above) before finalizing a bid.<\/li>\n<\/ol>\n
![\"\"](\"https:\/\/midradar.com\/wp-content\/uploads\/2026\/09\/border-surveillance-radar-3.webp\")
Border Surveillance Radar: How It Protects 1,000+ km Lines<\/p><\/div>\n
What This Costs<\/h2>\n
Midradar does not publish list pricing for the MR-RDG or MR-RDA series. Border radar pricing depends on range class, quantity, mounting infrastructure, and whether radar-vision fusion or platform integration is included in the scope, so a quote is required to get an accurate number for a specific segment plan.<\/p>\n
Trade-offs Worth Weighing<\/h2>\n
Radar-centered detection covers distances and weather conditions that camera-only systems can’t match, and it reduces the false-alarm load that plagues seismic\/PIR-only systems on vegetated or windy terrain. The trade-off is that radar alone doesn’t identify a target \u2014 it hands off to a camera or an operator for visual confirmation, which means the fusion and platform layer isn’t optional if the goal is an actionable alert rather than just a track on a screen. The MR-RDA15K-4R’s 1.6 kW power draw is a genuine constraint for solar-only or off-grid airborne-layer sites, and it’s worth checking against the site’s actual power budget before it’s specified, not after installation.<\/p>","protected":false},"excerpt":{"rendered":"
How border surveillance radar covers 1,000+ km of remote, harsh-terrain border and coastline, including radar types, detection ranges by target class, integration standards, and a procurement framework for RDG\/RDA-series deployments.<\/p>","protected":false},"featured_media":3417,"comment_status":"closed","ping_status":"closed","template":"","class_list":["post-3416","news","type-news","status-publish","has-post-thumbnail","hentry","news_category-blog"],"acf":[],"_links":{"self":[{"href":"https:\/\/midradar.com\/fr\/wp-json\/wp\/v2\/news\/3416","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/midradar.com\/fr\/wp-json\/wp\/v2\/news"}],"about":[{"href":"https:\/\/midradar.com\/fr\/wp-json\/wp\/v2\/types\/news"}],"replies":[{"embeddable":true,"href":"https:\/\/midradar.com\/fr\/wp-json\/wp\/v2\/comments?post=3416"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/midradar.com\/fr\/wp-json\/wp\/v2\/media\/3417"}],"wp:attachment":[{"href":"https:\/\/midradar.com\/fr\/wp-json\/wp\/v2\/media?parent=3416"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}