For airport operations, safety & procurement teams
Research & buyer’s guide
Automated FOD detection works technically and has been available for two decades, yet the global market remains a fraction of the problem it is sold against. This page gathers the industry’s economics, an engineering checklist for evaluating vendor claims and writing tenders, the regulatory standards that govern equipment, and the primary documents hosted on this site.
1. The economics of FOD: why a $4bn problem bought a $154m market
Read the market analysis →Global runway FOD detection sales were estimated at $153.8m in 2023 (less than one wide-body airliner), against the $4bn direct / $22.7bn total FOD cost quoted in industry sales decks.
In FAA Report TC22-47, Boston Logan’s single-runway system cost ~$1.71m and logged 155 detections in 17 months — roughly one item every three days, most of it harmless.
ACI-NA data shows 55% of FOD is found on stands and aprons (accounting for ~10% of FOD costs), while almost every first-generation sensor watched the runway.
Twenty years of voluntary Western guidance produced two US civil installations. China built a market via ≥95% Pd certification (AC-137-CA-2024-01) and manual-sweep credits.
Anyone preparing a business case for an automated FOD detection system has to confront a simple question: if the technology works and FOD costs aviation $4 billion a year, why have only two American airports and a handful of European hubs ever bought a system? Three structural reasons explain almost the entire gap.
1. Most of the $4 billion is not on the runway. The headline cost figure sums tool control, hangar maintenance, ramp handling and engine ingestion across the entire airfield. When a maintainer leaves a torch inside an F-35 engine at Luke AFB ($4 million in damage) or a loose cargo container is ingested on a taxiway at Chicago O’Hare or Delhi, no runway sensor could have prevented it. A runway detector only addresses the subset of debris that lies on the runway surface between inspections — such as the thrust reverser liner shed on departure at San Francisco or the steady toll of burst aircraft tyres.
2. The split-incentive problem (who pays vs. who saves). At a civil airport, the airport operator pays the capital and maintenance bill for the sensor, cannot reduce its scheduled manual runway checks under FAA AC 150/5210-24A, and bears the capacity loss of closing a runway to retrieve objects. The financial saving — avoided engine blade replacements and tyre bursts — lands on the airlines and engine lessors. Unless an airport recovers the cost through per-flight charges (as Vietnam proposed in 2016), specifies the sensors into a multi-billion-dollar greenfield construction budget (as at Beijing Daxing), or bundles FOD into turnaround and pavement-maintenance budgets (AiPRON, Moog ROMDAS), the civil spreadsheet rarely closes. By contrast, a military operator (USMC at Yuma, Israeli Air Force, Indian Navy) owns the runway, the airframe and the engine bill in one budget.
3. Nobody states the probability of detection — and “FOD” is overused as a shield. Because no vendor publishes a verified probability of detection across weather and object types, buyers cannot calculate the risk reduction they are purchasing. Worse, “foreign object damage” is routinely reached for by airlines after engine failures to deflect scrutiny from maintenance onto the airfield — as seen when metallurgy proved Ryanair flight FR1879 failed from dovetail root fatigue, leading to fleet-wide CFM56-7B fan-blade inspection directives rather than airfield changes.
2. RFP & buyer’s evaluation checklist: 6 questions vendors avoid
Run the numbers in the calculator →Every detection system — radar, electro-optical, laser or AI camera — is governed by the same fundamental trade-off between sensitivity, detection time and false alarm rate. If you are drafting a Request for Proposals (RFP) or evaluating vendor responses, insist on written answers to these six items.
Probability of detection (Pd) vs. scan speed and “AI”
Vendors lead with scan times (“full runway in 60 seconds”) and machine-learning object lists because both are easy to state. Neither governs risk. Under six-hourly manual checks, every missed item stays on the runway for an average of 180 minutes. As the Risk Calculator demonstrates, a slow system that detects 99% of debris beats a fast system that detects 90% by a wide margin.
Read: “AI” is the new “detection time” →
False alarm rate (FAR) on wet asphalt, snow and heat haze
Any sensor can be made more sensitive by lowering its detection threshold, and the price is always paid in false alarms. Standing water puddles (170+ rain days a year at Singapore Changi), snow banks and thermal shimmer trigger nuisance alerts. An operator flooded with false alarms stops trusting the display and clears alerts without an inspection — driving effective Pd to zero.
Read: How Changi cut iFerret false alarms more than tenfold →
FAA AC 150/5300-13 obstacle clearance and tower blind spots
Tower-mounted radars and cameras require clear line-of-sight to the far runway edge without penetrating the Primary Surface (1,000 ft wide), the 7:1 Transitional Surface, or the Taxiway Object Free Area (386 ft for Group VI aircraft). Double parallel taxiways can push towers beyond 1,000 ft from the centreline, while ground that slopes away outside the taxiway forces taller towers or creates coverage gaps.
Read: Site design & deployment geometry at Atlanta (ATL) →
Airside trenching, power, fibre and runway closures
Sensor hardware is frequently less than half the installed cost. Edge-light systems avoid tower siting rules but require power, high-bandwidth data links and optical alignment at dozens of runway-edge light cans. Tower systems require deep foundations, frangibility engineering and cable trenching across active movement areas.
Read: The cost of a FOD system — an infographic →
Retrieval time (tr), runway capacity and inspection rules
A sensor only reports coordinates; the debris stays on the runway until a vehicle drives out and picks it up (td + tr). Furthermore, FAA Advisory Circular 150/5210-24A explicitly states that automated FOD detection supplements airport personnel — it does not allow an airport to cancel its scheduled manual runway inspections.
Read: The FAA rewrites its FOD management guidance →
Supplier longevity and 20-year software ownership
A runway detection system is a twenty-year infrastructure asset sold by a small industry. Stratech won the largest contract in the history of the field (HK$280m at Hong Kong) and was ordered into compulsory liquidation five months after commissioning. Changi only preserved its installation by rebuilding the detection software in-house with NCS.
Read: The end of iFerret — Stratech wound up in 2018 →
3. Standards, regulations & mandate tracker
All FAA coverage →The regulatory documents, federal evaluations and national mandates that define what counts as an approved FOD detection system, where it can be sited on an airfield, and how it fits into a Part 139 or ICAO Annex 14 safety management programme.
| Document / Mandate | Date | Title | Scope & engineering significance |
|---|---|---|---|
| FAA AC 150/5220-24 | Sept 2009 | Airport Foreign Object Debris (FOD) Detection Equipment | The primary technical performance standard for equipment procured under the US Airport Improvement Program (AIP). Defines four system categories (Stationary Radar, Stationary Electro-Optical, Stationary Hybrid, Mobile Radar), target sizes, false-alarm limits (≤1/day) and weather envelopes. Has not yet been updated for radio-over-fibre, ML classification or autonomous vehicles. |
| FAA AC 150/5210-24A & CertAlert 24-03 | Feb 2024 | Airport Foreign Object Debris (FOD) Management | Revises airport FOD programme guidance to recognise continuous detection on “runways and other aircraft movement areas” (taxiways and aprons) alongside mobile detection devices, while restating that automated equipment supplements rather than replaces scheduled manual inspections. |
| FAA Report DOT/FAA/TC-22/47 | May 2023 | Cost-Benefit Analysis of FOD Detection Systems (Hilburn & Pesmen) | First federal economic analysis built on live US operational logs: 48 months at Seattle-Tacoma (2016–2019) and 17 months at Boston Logan (155 detections, averaging 9.1/month, against a ~$1.71m single-runway installation cost). Notes high radar capital cost as the primary barrier to civil adoption. |
| Public Law 115-254 § 142 Report | Oct 2018 / Nov 2021 | FAA Report to Congress on Foreign-Developed Runway Safety Technologies | Congressionally mandated survey of international FOD detection deployments at US airports. Confirmed only two US full-runway civil installations (Boston Logan and Seattle-Tacoma) after a decade of eligibility, and formally recorded that Stratech was no longer in business. |
| FAA Tech Center Assessments | 2011–2012 | Performance Assessments of the Original Four Systems | Field evaluations conducted by the FAA Airport Technology R&D Team at Providence (Tarsier, Feb 2011), O’Hare/Honolulu/Palomar (FOD Finder, Sept 2011), Changi/US test sites (iFerret, Mar 2012) and Boston Logan (FODetect, June 2012), establishing AC 150/5220-24 compliance. |
| FAA Buy American & FCC Waivers | 2010–2015 | AIP Procurement Eligibility & 78–81 GHz Spectrum Waivers | Because Tarsier (UK), iFerret (SG), FODetect (IL) and DEB-RA (IT/DE) were developed outside the US, nationwide Buy American waivers were required for airports to use federal AIP grants. Trex’s mobile FOD Finder separately secured an FCC restricted-frequency waiver in July 2013. |
| FAA AC 150/5300-13 | Ongoing | Airport Design (Primary, Transitional & Taxiway Object Free Surfaces) | Sets the obstacle-free geometry around runways and taxiways (1,000 ft Primary Surface, 7:1 Transitional Surface slope, 386 ft Group VI Taxiway OFA) that governs where fixed FOD sensor towers can be built. |
| CAAC AC-137-CA-2024-01 & CCAR-140 | 2022–2026 | CAAC FOD Detection Equipment Technical Requirements & Inspection-Reduction Rules | Brings FOD detectors under mandatory specialized-equipment certification (AC-137-CA-2024-01, June 2024; ICAO A42-WP/598, Sept 2025): ≥95% Pd on a 10-item real-object test set in 30×30 m, ≤1 false alarm/day over 90 days, wake-turbulence frangibility/tethering, and rectify-or-suspend enforcement. Under AP-140-CA-2022-05 (Art. 16) and CCAR-140 (Art. 47), 1 year of verified operation allows airports to reduce intermediate manual runway sweeps. |
| ICAO Annex 14 / Doc 9137 & EASA ADR.OPS | Ongoing | Aerodrome Design, Surface Inspections & Frangibility Standards | Establishes international scheduled physical runway inspection baselines and strict frangibility requirements for any equipment sited in runway strips or Runway End Safety Areas (RESAs) — underscored by the December 2024 Muan localiser berm accident. |
4. Primary documents & downloads library
Browse full archive →Regulatory circulars, FAA Technical Center evaluation reports, procurement RFIs, patent filings and the original Risk Calculator workbook hosted directly on this site.
-
FOD Risk Calculator Original Workbook (FOD-risk-v2.xls)
The original unrestricted spreadsheet model introducing “FOD minutes” and comparing three detection systems side by side to prove why probability of detection dominates detection time. (Context: How important is detection time?)
-
FAA Advisory Circular 150/5220-24 (Draft): Airport FOD Detection Equipment
The foundational FAA specification defining the four approved classes of FOD detection equipment (stationary radar, stationary EO, stationary hybrid and mobile radar) and their target detection requirements. (Context: FAA draft FOD circular issued)
-
FAA Performance Assessment: Mobile Radar-Based FOD Detection System (FOD Finder)
Full FAA Airport Technology R&D Team evaluation report covering field tests of Trex Enterprises’ vehicle-mounted millimetre-wave radar at Chicago O’Hare, Honolulu and McClellan-Palomar. (Context: FAA report on FOD Finder)
-
FOD Detection as Part of NextGen Surface Surveillance
Technical briefing on how automated runway debris detection fits into the FAA’s NextGen surface surveillance and A-SMGCS architecture. (Context: FOD detection as a part of NextGen)
-
The Cost of a FOD System — Industry Cost & Payback Infographic
Visual breakdown comparing direct aircraft FOD damage costs ($4bn/yr), indirect airline delay and fuel-efficiency losses, and the capital cost of runway detection hardware. (Context: The cost of a FOD system – an infographic)
-
Military Airfield FOD Detection Request for Information (RFI)
Example defence procurement solicitation illustrating how military airfield operators specify automated FOD detection requirements. (Context: Request for information – Department of Air Defense)
-
Changi iFerret US$8.4m Contract Profile (The Edge Singapore)
Detailed contemporary reporting on Stratech’s landmark Changi International Airport contract and commercial projections during the industry’s first wave. (Context: iFerret sale to Changi International worth $8.4 million)
-
Stratech iFerret US Patent Approval Filing
SGX corporate announcement detailing US patent protection granted for Stratech’s vision-based airfield FOD detection and tracking system. (Context: Stratech’s iFerret Patent Approved)
-
Thales & Aéroports de Paris Release: Paris CDG FODspot Trial
Joint announcement by Thales, Xsight Systems and Aéroports de Paris on installing a single FODspot unit at a Charles de Gaulle taxiway intersection eleven years after the Concorde crash. (Context: It took more than 11 years, and it wasn’t worth the wait)
-
Academic Paper: Still-Image-Based FOD Detection System (Aftab & Minhas)
Research paper evaluating optical contrast, minimum detectable object size (0.6 × 0.6 inch) and environmental limitations in camera-only FOD detection. (Context: Still image based Foreign Object Debris detection system)