Role & capabilities
- Explosive-hazard detection
- Remote engineering manipulation
- Primary domain
- Land
- System type
- Explosive-ordnance disposal robot
- Developer / manufacturer
- Israel Aerospace Industries — ELTA
- Origin / production countries
- Israel
- Other names
- No additional names recorded
- Variants / configurations
- Not distinguished in reviewed sources
- Operators / programme customers
- Not identified in reviewed sources
Evidence & current status
Reviewed 21 September 2026; named product documented, current fleet quantity not independently established.
RobARC, also called Sahar and designated ELA-6631, is IAI ELTA's robotic route-clearance system. The manufacturer describes an integrated package combining hazard-detection sensors, a manipulator and supporting mission equipment. It belongs in the engineering and explosive-hazard category, separate from logistics carriers and general observation robots.
The current offering advertises active and passive detection equipment and assisted or autonomous functions. The operator remains part of the process described by IAI. A claim of automated detection should not be read as a guarantee that every hazard can be found or that the complete task proceeds without supervision.
IAI had already identified Sahar within its ground-robotics portfolio in its 2016 RoBattle announcement, and the named product remains on the current site. That continuity supports a stable identity, but the reviewed pages do not establish a current customer fleet, acceptance date or configuration-specific dimensions. The catalogue consequently records supplier-reported status. Generic vehicle figures would be misleading because the complete system depends on the selected carrier, sensors and engineering attachments.
Sourced specifications
Figures apply to the named configuration. Maximum values are not guaranteed operating performance.
| Specification | Reported value | Context & source |
|---|---|---|
| Configuration | Robotic route-clearance system | Supplier-published configuration; not an independent acceptance result. Source ↗ |
| Mobility | Not established in the reviewed public sources. | Public evidence gap. No estimate or neighbouring variant value has been substituted. Source ↗ |
| Dimensions | Not established in the reviewed public sources. | Public evidence gap. No estimate or neighbouring variant value has been substituted. Source ↗ |
| Mass | Not established in the reviewed public sources. | Public evidence gap. No estimate or neighbouring variant value has been substituted. Source ↗ |
| Payload | Not established in the reviewed public sources. | Public evidence gap. No estimate or neighbouring variant value has been substituted. Source ↗ |
| Endurance | Not established in the reviewed public sources. | Public evidence gap. No estimate or neighbouring variant value has been substituted. Source ↗ |
| Range | Not established in the reviewed public sources. | Public evidence gap. No estimate or neighbouring variant value has been substituted. Source ↗ |
| Speed | Not established in the reviewed public sources. | Public evidence gap. No estimate or neighbouring variant value has been substituted. Source ↗ |
| Terrain / environment | Not established in the reviewed public sources. | Public evidence gap. No estimate or neighbouring variant value has been substituted. Source ↗ |
| Sensors | Not established in the reviewed public sources. | Public evidence gap. No estimate or neighbouring variant value has been substituted. Source ↗ |
| Communications / control | Remote and autonomous functions described; configuration-specific | Supplier-published configuration; not an independent acceptance result. Source ↗ |
| Launch / deployment | Not established in the reviewed public sources. | Public evidence gap. No estimate or neighbouring variant value has been substituted. Source ↗ |
Publication history
- — Added in the September 2026 global coverage review, with sources, configuration limits and explicit data gaps.
Suggest a correction to this entry →
Follow the evidence
Source types identify who makes the claim. Programme milestones and supplier statements should be read in context.