Understanding Flame Detection Methods: Flame Rods vs UV Scanners vs IR Scanners
By Profire TeamMay 11, 2026
A “Pilot Flame Not Proven” trip doesn’t always mean the pilot failed to light. In many cases, the pilot flame is present, but the burner management system can’t confirm it with enough signal strength or stability to pass the proving window. That is why the flame detection method matters. A flame rod, UV scanner, and IR scanner don’t prove flame the same way, and they don’t fail the same way in the field.
Different flame detectors look for different proof. A flame rod depends on rectification current and a clean return path. A UV scanner depends on optical access to the pilot flame root. An IR scanner depends on seeing the right flicker signature and rejecting background IR energy. When crews start with the detector type instead of jumping straight to parts replacement, troubleshooting usually gets faster and the likely causes narrow quickly.
What is a “Pilot Flame Not Proven” alarm?
A “Pilot Flame Not Proven” alarm means the burner management system didn’t receive an acceptable pilot flame signal during PTFI, or Pilot Trial for Ignition, and the pilot proving period, sometimes called PFEP, or Pilot Flame Establishing/Proving Period. If the signal doesn’t rise high enough, or if it doesn’t remain stable long enough to satisfy the flame safeguard logic, the system shuts fuel and recycles or locks out. Depending on the equipment class, that lightoff and flame supervision framework is addressed in applicable regulatory standards, such as NFPA 85 for large boilers and combustion systems hazards, NFPA 86 for ovens and furnaces, and NFPA 87 for fluid heaters.
That usually puts the event into one of three categories:
the pilot never ignited
the pilot ignited, but the flame detection system couldn’t confirm it with enough signal margin
the pilot lit, but the flame signal wouldn’t stay acceptable long enough to pass
Those distinctions matter because they point the investigation in different directions. A no-light condition pushes the check toward ignition energy, pilot fuel delivery, restrictions, and pilot ignition timing. A proving failure with visible flame pushes it toward a flame detector, flame sensor position, sighting, grounding, contamination, flame stability, or interference issue.
Once the installed flame sensor is identified, the troubleshooting path gets much shorter.
What Should You Check Before You Replace Flame Detection Hardware?
Before replacing hardware, answer a few basic questions:
Did the pilot actually light, or was there only an ignition attempt?
Which flame detection system is installed: flame rod, UV scanner, or IR scanner?
Was the flame signal weak, unstable, or absent during the proving window?
What changed since the unit last ran well: draft conditions, pilot pressure, weather, fouling, or recent maintenance?
Is the failure cold-only, hot-only, or inconsistent from startup to startup?
Asking these questions is more useful than replacing a detector on the first trip. A “Pilot Flame Not Proven” event can be caused by no ignition, weak proof, unstable proof, or a flame failure immediately after lightoff. Those are different problems, even though the alarm text looks the same.
Flame Rod / Flame Rectification
How does a flame rod/rectification prove flame?
A flame rod proves flame through Flame Rectification. The controller applies a sensing voltage, and the flame becomes part of the electrical path through the ionization principle. In practical terms, the control is looking for a stable micro-amp DC current that confirms flame is present at the rod. For that signal to hold, the flame sensing rod needs stable flame contact, the return path to ground needs to stay intact, and the wiring back to the controller needs to remain clean.
Visible flame alone is not enough. The pilot can be present, but if the flame rectification signal is weak or unstable, the burner management system may still register a “Pilot Flame Not Proven” condition. That is why a flame rectification system can look healthy to the eye and still fail to prove.
What does flame rod/rectification failure look like?
Rectification problems usually show up as margin problems, rather than complete signal loss. The pilot may light, the system may prove once or twice, and then fail on the next startup with no obvious mechanical change.
Common patterns include:
a flame signal that is low, drifting, or unstable
nuisance trips after maintenance changed rod position, grounding, or wiring
proving that drops out when draft conditions or flame shape shift
weather-related trips that expose weak signal margin
a pilot that looks acceptable to the eye, but doesn’t stay in solid contact with the flame rod
Poor pilot pressure, weak flame contact, poor pilot sensor position, gas quality issues, and cable loading can all produce this type of failure signature.
What to check first when troubleshooting flame rod/rectification problem?
Start with the return path. Weak grounding, poor bonding, or cable-related signal loss can make a healthy flame rod look bad. Then inspect the flame sensing rod itself for contamination, carbon tracking, cracked ceramic, erosion, or poor placement in the pilot flame root.
Next, inspect the lead and routing. Damaged insulation, loose terminations, excess cable loading, and weak ground reference can all reduce flame rectification signal quality.
Then go back to the pilot flame. If pilot pressure is off, mixing is poor, or draft is pulling the flame off the rod, the problem can look electrical even though it started as a flame-contact issue.
If the controller displays live flame signal, trend it during startup. Weak margin usually shows up as unstable proof before it becomes a hard “Pilot Flame Not Proven” lockout.
What are Integrated Ignition / Rectification Assemblies?
Some systems combine the igniter and flame rod into one assembly. When these trip on “Pilot Flame Not Proven”, crews often assume the entire problem is on the ignition side.
Sometimes that is true. No spark at all, or arcing inside the porcelain instead of a clean spark at the tip, can prevent successful lightoff. But a healthy spark still doesn’t guarantee successful proving. Once the pilot lights, the Flame Rectification side still has to deliver a stable signal the controller will accept.
Treat those as two separate checks:
First confirm spark and pilot fuel delivery.
Then confirm flame contact, return path, and signal margin.
If the spark is healthy, but the flame sensor still can’t hold proof, the trip is still a “Pilot Flame Not Proven” problem, not simply an ignition problem.
UV Flame Scanners
How does a UV scanner prove flame?
A UV scanner, or Ultraviolet Scanner, proves flame by viewing ultraviolet energy from the pilot flame. In practice, it needs a clean sight path and the right target. The scanner should be looking at the pilot flame root near the pilot nozzle, not just any visible portion of the flame.
That makes UV one of the most line-of-sight-dependent flame detection methods. If the lens is dirty, the sight pipe is restricted, or the aim is off, the scanner may not deliver a signal with enough margin to pass the proving window. On many burners, the UV scanner is the primary flame sensor for pilot proof, so small changes in sighting matter more than crews expect.
What does UV scanner failure look like?
A UV scanner usually fails in ways that look like optics or sighting problems. The pilot lights, the scanner sees it briefly, and then the signal drops away. In other cases, the unit works after cleaning and then starts tripping again as deposits return.
Common patterns include:
dropout shortly after lightoff
better performance right after cleaning
failures tied to moisture, dust, snow, condensate, or dirty service
trips after small alignment shifts or vibration
cold starts that work better than hot restarts
If the UV scanner isn’t aimed at the stable flame root near the pilot nozzle tip, it may not hold a signal through the proving window. That kind of mis-aimed ultraviolet detector can create a repeat “Pilot Flame Not Proven” nuisance trip even when the pilot looks normal.
What to check first when troubleshooting UV scanner problems?
Start with the lens and sight pipe. Check for dust, sand, soot, moisture, condensate, ice, and physical blockage. It doesn’t take much fouling to create an intermittent “Pilot Flame Not Proven” trip on a UV scanner.
Then verify the aim. Confirm the scanner is actually looking at the pilot flame root, not a flame shape that shifts during warm-up or changes with draft conditions.
If the installation uses purge air, confirm it’s flowing continuously, clean and dry, and that the purge path isn’t restricted. In dirty or wet service—environments with dust, sand, snow, and moisture that can quickly foul the lens—purge air often makes the difference between reliable proving and repeat nuisance trips.
After that, inspect the surrounding hardware. Vibration, heat soak, water ingress, and connector issues can all reduce consistency even when the pilot still looks normal.
IR Flame Scanners
How does an IR flame scanner prove flame?
An IR scanner, or Infrared Scanner, proves flame by reading IR energy and flame flicker characteristics. Its biggest challenge is seeing the right energy from the right target.
That makes IR more sensitive to discrimination problems than many crews expect. If hot refractory, glowing metal, reflections, or adjacent flames enter the field of view, the scanner can struggle to separate the pilot from the background. This is where UV/IR detectors are often talked about together, but the failure signatures aren’t identical. A UV scanner usually loses optical proof. An IR scanner can continue to see energy and still fail because the signal no longer represents the pilot.
What does IR flame scanner failure look like?
An IR scanner often looks inconsistent until someone checks the sightline. The pilot may be lit, but the flame signal becomes unstable as the heater throat, refractory, or nearby surfaces heat up.
Common patterns include:
proving that gets worse as the unit heats up
intermittent validation with visible pilot flame present
instability tied to adjacent burners or reflections
startups that fail hot even though cold lightoff looked acceptable
flame-shape changes that affect proving more than ignition itself
If the detector is seeing anything other than the pilot flame, stable proof becomes much harder. That’s one reason IR flame detectors can produce a “Pilot Flame Not Proven” alarm on a healthy pilot when the real issue is background interference.
What to check first when troubleshooting IR flame scanner problems?
Start with sighting. Confirm the IR scanner is aimed at the pilot flame’s flicker zone, and that the field of view excludes refractory, glowing surfaces, reflections, and nearby flame sources.
Then inspect the optics and mounting. Like a UV scanner, an IR device can suffer from dirty sight paths and small alignment changes. The difference is that it may continue to see energy while still seeing the wrong target.
Next, check what changes occur during heat-up. If the problem appears only after the heater gets hot, background IR interference should move near the top of the list.
Finally, verify the pilot itself. A weak or poorly anchored pilot flame can alter flicker frequency and flame stability enough to reduce acceptance even when operators can still see flame.
Where Does Flame Detection Troubleshooting Usually Go Sideways?
The most common mistake is replacing the detector before confirming what actually failed.
If the pilot never lights, start with ignition energy, pilot pressure, restrictions, and pilot ignition timing. If the pilot lights, but doesn’t prove, move toward signal strength, flame sensor position, sighting, grounding, contamination, and interference. If the pilot proves briefly and then drops out, look harder at pilot stability, draft conditions (especially in natural draft systems), air settings, and detector placement.
A few field realities are worth keeping in mind:
proving issues show up most often during startup
long pilot piping can delay ignition enough to miss the proving window
excessive draft or poor pilot-to-main positioning can pull the pilot away from the detector
inspection and cleaning every three to six months can catch fouling, poor drafting, and ignition wear before they turn into repeat lockouts
NOTE: bypassing interlocks should only happen under site procedure and senior authorization, not as a casual troubleshooting shortcut
Many nuisance trips start as small margin problems that only become obvious during startup. That is why flame failure analysis has to begin with the proving method, not just the alarm text.
What Should You Track After a Successful Startup?
After a successful startup, record a few baseline values:
time-to-prove
flame signal or scanner strength, if available
pilot pressure during lightoff
sighting photos for rods and scanners
whether performance changes hot versus cold
That information shortens the next troubleshooting cycle and gives the team something more useful than a list of replaced parts. It also helps separate a true flame failure from a weak flame detection system that is only barely proving on a good day.
Match the Detector Type Before You Change Parts
A “Pilot Flame Not Proven” alarm tells you the system didn’t accept the pilot flame signal. It doesn’t tell you why.
A flame rod points the investigation toward return path integrity, rod placement, lead condition, and stable flame contact. A UV scanner points it toward sighting, lens condition, and purge effectiveness. An IR scanner points it toward sightline discipline, hot background interference, and flame discrimination.
When the detector type matches the failure signature, troubleshooting gets shorter, unnecessary part changes drop off, and startup performance usually becomes more predictable.
Post-Trip Workflow for “Pilot Not Proven” Shutdowns: First-Out, Signal Margin, and Prevention (Coming Soon)
Frequently Asked Questions About Flame Detection Methods
What are the different flame detection methods?
There are three primary flame detection methods: flame rod/flame rectification, UV flame scanners, and IR flame scanners. All three methods differ in how they detect and prove flame, and how they fail in the field.
What does “Pilot Flame Not Proven” mean?
“Pilot Flame Not Proven” means the burner management system did not receive an acceptable pilot flame signal during the proving window. That can happen because the pilot never lit, because the flame was present but the detector couldn’t confirm it with enough signal strength, or because the signal dropped out before the sequence could continue.
What is PTFI in a burner management system?
PTFI stands for Pilot Trial for Ignition. It is the part of the startup sequence when the system allows ignition energy and pilot fuel, then looks for proof of pilot flame within a defined time. If the flame detection system does not prove the pilot during that period, the system shuts fuel and recycles or locks out.
Why would a pilot flame be lit but not proven?
A pilot can be visibly lit and still fail proving if the flame signal is weak or unstable. Common causes include poor flame rod contact, weak grounding or bonding, dirty scanner optics, bad scanner sighting, unstable pilot flame, or interference from hot backgrounds or reflections.
How do I troubleshoot a weak flame rod signal?
Start with the return path. Check grounding, bonding, rod condition, rod placement, and lead wire integrity. Then verify that the pilot flame stays in reliable contact with the rod throughout the entire proving window. If the controller displays flame signal, trend it during startup. Weak margin usually shows up as a low or unstable signal rather than a clean on-off dropout.
Why do UV scanners fail after they worked yesterday?
Because the sight path can change quickly in real service. Dust, soot, moisture, condensate, ice, and small aim shifts can turn an acceptable UV signal into an intermittent one. If cleaning restores operation, that usually points to a fouling, purge-air, or sighting problem that will come back unless the underlying cause is fixed.
Why does an IR scanner fail after the unit heats up?
As the heater warms up, surrounding surfaces emit more infrared energy. If the scanner’s field of view includes hot refractory, reflective metal, or adjacent flames, that background IR can compete with the actual pilot signal and reduce reliable discrimination. In practice, that means the pilot may still be lit while the detector struggles to prove it.
When should I stop replacing parts and start gathering data?
If repeated hardware changes have not corrected the issue, stop swapping components and start measuring. Confirm pilot fuel delivery at lightoff, review flame signal margin during proving, check draft stability, inspect sighting and alignment, and document whether the failure happens cold, hot, or only under certain operating conditions. That information is more useful than a list of replaced parts.
What standards apply to pilot flame proving?
The exact standard depends on the equipment class, but light-touch references that fit this article include NFPA 85 for large boilers and combustion systems hazards, NFPA 86 for ovens and furnaces, and NFPA 87 for fluid heaters. In this article, the standards mention should stay contextual rather than turn into a code interpretation section.
