Pedestrian Detection Feasibility: Was the Technology Available on the Date of the Incident?

Pedestrian detection feasibility is the question at the center of many forklift and heavy equipment injury cases: was a system that could detect people commercially available on the date of the incident, could it have been fitted to the machine involved, and would it have worked in that operation? Answering it takes dated evidence, not today's product catalog.

After a pedestrian is struck, it's easy to look at what's on the market now and assume it was always there. That's hindsight, and it doesn't hold up. The standard of care is measured at a point in time, so the technology question has to be answered at that same point in time.

This article lays out the method I use to answer it. It's written for attorneys and claims professionals reconstructing a decision after the fact, and for EHS managers who want their own decisions to stand up later.

The Four Questions Behind Pedestrian Detection Feasibility

"Was the technology available?" sounds like one question. It's four, and each one needs its own evidence:

1. Did it exist? Had anyone built a system that detects people around this type of vehicle? Research papers, patents and prototypes answer this, but existing is not enough.
2. Was it commercially available? Could a buyer in that market have ordered it, at a known price, with installation and support, on or before the incident date?
3. Was it feasible for this machine? Could it be mounted, powered and configured on the make, model and age of the vehicle involved, in that environment?
4. Was it reasonable to adopt? Given the hazards the employer knew about, the cost, and what comparable operations were doing, would a reasonable employer have evaluated it or put it in place?

Opinions go wrong when they jump from the first question to the fourth. A university prototype from years earlier proves the first question and nothing more. A product launched six months after the incident proves nothing about the date that matters.

"Existing, being for sale and fitting the machine are three different facts. Each one needs its own proof."

Evidence That Proves Availability on a Date

Commercial availability is a historical fact, and it's proven the way other historical facts are: with dated records created at the time. The strongest sources, roughly in order of weight:

• Quotes, purchase orders and invoices. A dated sale of the system to any buyer, especially one in the same industry, is the clearest proof it could be bought.
• Dated price lists and dealer bulletins. These show the product was offered through a sales channel, at a price, before the date in question.
• Archived web pages. The Internet Archive's Wayback Machine stores snapshots of manufacturer and dealer sites. A product page captured before the incident date, with specifications and a contact or buy option, is strong evidence that it was being marketed.
• Press releases, trade press and trade show exhibitor lists. These show launch timing and how widely a product was promoted to the industry.
• Regulatory filings. Wireless tag and radar systems need equipment authorization from the FCC in the United States, and FCC records carry grant dates. A grant shows a device was ready for market, though not that it was sold.
• Installation and deployment records. Evidence the system was running on comparable machines in comparable operations goes to both availability and industry practice.

Patents and academic papers sit at the bottom of the list. They prove the idea existed. They don't prove anyone could buy it.

One more caution. Product names, features and detection ranges change between versions. The evidence has to match the version that was on sale at the time, not the current datasheet.

Pedestrian Detection Feasibility for the Specific Machine

A system sold for warehouse forklifts doesn't automatically fit a 20-year-old rough terrain forklift, a wheel loader or an underground loader. Pedestrian detection feasibility has to be tested against the machine actually involved. The factors I examine:

• Mounting and coverage. Can sensors be placed to cover the zone where the person was struck, given the mast, counterweight, cab and attachments?
• Power. Does the system run on the machine's electrical system and voltage, and does it need ignition switching or a dedicated circuit?
• Environment. Dust, rain, low light, glare, vibration, freezer temperatures and washdown all limit what a given technology can do.
• Technology fit. Tag systems only detect people wearing a working tag, so visitors and contractors matter. Camera AI needs line of sight and enough light. Radar senses objects but generally can't tell a person from a post.
• Retrofit versus factory option. Was the system available as an aftermarket kit, a dealer-installed option, or only on new machines?
• Cost and installation. What did it cost on that date relative to the machine's value and the fleet size, and how long did installation take?

The comparison of technologies is covered in depth in camera AI vs RFID vs radar. For feasibility, the point is narrower: which of them, as sold on that date, could have covered that blind spot on that machine.

Would It Have Worked in That Operation?

A system can be available and fit the machine, yet still not be a workable control in a particular operation. Operational feasibility asks how it would have performed day to day:

• Nuisance alarms. In congested aisles, a system that alarms constantly gets ignored or disconnected. The configuration options available at the time matter.
• Operator acceptance. Was the alert clear and actionable, and would operators on that shift pattern have kept it on?
• Maintenance and support. Was there local service, and what did the system need to stay working?
• Evidence from comparable sites. Pilots and deployments in similar operations show whether the system performed outside a demo.

Feasibility cuts both ways. For a plaintiff, it shows that a workable system existed for that operation. For a defendant, it can show that the available systems were poorly suited to the conditions and that other controls were a reasonable choice. The method is the same either way.

Availability Is Not Causation

Proving a system was available and feasible doesn't prove it would have prevented the incident. That's a separate question, and it turns on detection timing:

1. Would the system have detected the person, given where they were, how they moved and the conditions?
2. When would it have detected them, given its detection range and the vehicle's speed?
3. Was there enough time for the operator to react, or for an automatic slowdown to act, and for the machine to stop short of the person?

Those answers come from the incident evidence: video, scene measurements, vehicle speed and stopping distance, sight lines and lighting. Sometimes they show a detection system would very likely have changed the outcome. Sometimes they show it would not. Both findings are useful, and an opinion that can't reach either one isn't grounded in the facts.

Common Mistakes in Pedestrian Detection Feasibility Opinions

These are the errors I see most often, on both sides of a case:

• Hindsight. Using a current product, current price or current performance claim to describe a past date.
• Brochure reliance. Taking a marketing claim for detection range or accuracy as proof of real-world performance.
• Wrong machine. Showing a system worked on warehouse forklifts and assuming it fit a loader or a rough terrain truck.
• Prototype as product. Treating a research project, patent or trade show concept as something a buyer could order.
• Ignoring the environment. Skipping the dust, lighting, cold or traffic density that decides whether the technology works.
• Ignoring compliance with the system. For tag systems, overlooking whether everyone on site would actually have worn a working tag.

Records to Request When Pedestrian Detection Feasibility Is at Issue

For attorneys building or testing a feasibility opinion, these records usually decide it:

• Make, model, year, hours and attachments of the vehicle involved
• Equipment purchase, lease and rental records, including options offered
• Any vendor proposals, demos or quotes for detection systems the employer received
• Safety meeting minutes, hazard assessments and near-miss reports mentioning pedestrian risk
• Insurance loss-control recommendations and audit findings
• Traffic management plans and site layouts at the time of the incident
• Video, scene photos and measurements needed for a detection timing analysis
• Records of detection systems in use at the employer's other sites or at comparable operations

Frequently Asked Questions

What does "feasible" mean for pedestrian detection technology?

It means a system was commercially available on the relevant date, could be fitted to the specific vehicle, and could work reliably in that operating environment. All three have to be shown with evidence from that time.

How do you prove a product was available on a past date?

With records created at the time: quotes, invoices, dated price lists, archived web pages, press releases, trade show listings and regulatory filings such as FCC equipment authorizations for wireless systems.

Does a patent prove a technology was available?

No. A patent shows an idea was described and claimed. It doesn't show a product was for sale, supported or suitable for the machine involved.

If a system was available, does that mean the employer was required to install it?

Not by itself. Availability and feasibility are inputs to the standard of care, which also weighs the known hazards, cost, industry practice and other controls in place. I cover that in the forklift pedestrian safety standard of care.

Can a feasibility analysis help a defendant?

Yes. The same analysis can show that available systems were poorly suited to the machine or conditions, or that detection would not have changed the outcome in time.

From the Field

I've sold, installed and supported AI pedestrian detection systems on forklifts and heavy equipment, and worked with equipment dealers on fleet deployments. That's where I learned that "the system was available" and "the system would have worked here" are different statements. Mounting positions, wiring, lighting and operator habits decide the second one.

When I review a matter, I start with the date and work outward: what could a buyer in that industry actually order, what would it have taken to put it on that machine, and what does the incident evidence say about detection timing.

The framework behind this approach is set out in my book Evaluating Pedestrian Detection: An Expert Framework for Industrial-Vehicle Safety Technology, Risk, and Reasonable Decision-Making.

For attorneys evaluating a struck-by matter, I offer expert witness services on availability, feasibility, standard of care and detection timing, for plaintiffs or defendants.

Start With the Date

Pedestrian detection feasibility is answered one fact at a time: what existed, what could be bought, what fit the machine, and what would have worked in that operation, all on the date of the incident. Opinions built that way hold up. Opinions built on today's catalog usually don't.

"The right question is never what's possible today. It's what was possible then."

Want to talk through a matter? Book a 30-minute call.

This article is general information about safety technology and expert analysis, not legal advice.