NFIRS Coding - Smoke
NFIRS - NFIRS Codes - NFIRS Examples
Need to replace your Fire RMS?
Responserack provides innovative middle-of-the-night firefighter-simple volunteer fire department software and NFIRS incident reporting software. Learn how Responserack helps your volunteer fire department.Smoke Report / Smoke Chase Incident Coding
How do I code a smoke report?
It might have been calling in as a smoke report, but when it isn’t a wildland fire (or some other fire) we code NFIRS “as is, not as toned”. The incident could end up as Unable to Locate (UTL) however it could also be 652 - Steam, Vapor, Fog or Dust Thought To Be Smoke.
Smoke Report / Smoke Chase - Smoke
Here are some of those choices…
Unable to Locate (UTL)
If no smoke was found and no cause of something appearing like smoke was determined, code as unable to locate (UTL).
Clouds, Water Dogs & More …
Use 652 - Steam, Vapor, Fog or Dust Thought To Be Smoke for incidents that was from some form of steam or vapor or fog or dust that was mistaken for smoke. It is a wide description of many types of reasons that the incident was mistakenly identified as smoke when called in.
Diesel exhaust (typically from heavy equipment, and especially when starting up cold) that is mistaken for smoke, or low lying clouds (sometimes presenting as “water dogs”) which are a form of water vapour, or dust from a drilling rig or railway track grinder … all these fit into 652 - Steam, Vapor, Fog or Dust Thought To Be Smoke.
Water Dogs - Vapor Clouds
Something else?
If you have a cause that appeared like smoke, but was not fire, then 652 - Steam, Vapor, Fog or Dust Thought To Be Smoke is the likely coding. If this is not a fit, check alternative incident types.
Do not confuse with ‘Smoke Scare’
Do not confuse 651 - Smoke Scare, Odor Of Smoke with a smoke report/smoke chase. A smoke scare or oder of smoke incident type code is identifying those incidents that have smoke, or had smoke upon arriving at scene.
Need other NFIRS coding help?
See more NFIRS coding examples for quick “how to” coding snippets:
For more information see the NFIRS / eNFIRS training and contact Responserack if you would like more help with NFIRS or eNFIRS.