Safety-first isn't a marketing position. It's the engineering requirement.
Autonomous equipment on an active airfield must meet a higher standard than anywhere else. Here is how FODBOT is designed to meet it.
Important: FODBOT is not currently FAA certified for autonomous operation on active airfields. All pilot deployments are conducted under coordinated operational protocols with the airport's operations team. FODBOT is pursuing FAA/ICAO-aligned safety certification pathways. This information will be updated as that process advances.
Multiple redundant safety layers in every operation.
ADS-B Traffic Monitoring
FODBOT continuously monitors ADS-B broadcasts to detect aircraft operating in or approaching the airfield exclusion zone. When an aircraft is detected within the configured boundary, FODBOT holds position or initiates a return-to-base sequence.
VHF Airfield Radio Scanning
In addition to ADS-B, FODBOT scans designated airfield communication frequencies to detect approach and departure communications, providing an additional aircraft-awareness layer for aircraft that may not be ADS-B equipped.
Configurable Exclusion Zones
Prior to deployment, FODBOT's operational boundaries are geo-fenced to your runway and taxiway dimensions via RTK-GPS. The system will not operate outside of these boundaries without operator override.
Human Override at All Times
FODBOT operates autonomously but is never beyond human control. A full stop command is available to any operator via the control interface. Automatic emergency hold is triggered on ADS-B detection or communication anomalies.
Operational Window Coordination
FODBOT operational schedules are coordinated with your operations team before deployment. Typical windows are during low-traffic periods or when coordination with tower/CTAF permits safe operation.
Safety Certification Pathway
FODBOT is currently pursuing FAA and ICAO-aligned certification pathways for autonomous airfield ground vehicles. Our engineering documentation and safety case are being developed in accordance with applicable guidance. Certification status will be communicated transparently.
Designed to work alongside crews — not around them.
FODBOT does not replace required human inspections. Regulations require human FOD inspections, and FODBOT is not positioned as a substitute for those obligations.
What FODBOT does is handle the continuous autonomous sweep cycle between required inspections — reducing the frequency of missed debris accumulation, improving the documented record between human inspection events, and freeing crew time for higher-value work.
All FODBOT operational schedules are designed around your crew's existing workflow. No runway closures are required for FODBOT operation. No new safety procedures are needed beyond the coordination protocol established during onboarding.
FODBOT's Safety Commitments
Inspection logs designed for your SMS program.
Every FODBOT inspection run produces a geo-referenced, timestamped log documenting coverage area, detected items, classification results, and removal actions. These logs are structured to support FAA Safety Management System (SMS) documentation requirements and general airfield record-keeping standards. Logs are accessible via the inspection dashboard and exportable for your records system.
Questions about our safety approach?
We are happy to walk through our operational safety protocols, discuss certification status, or answer any technical questions about how FODBOT operates on active airfields.
Talk to the Team