NFIRS Coding : ‘Unable To Locate’ Incident
How do I code an unable to locate (UTL) incident?
Admittedly a call to MVA with precise details (so detailed they have to be witnessing it) that ends up as UTL appears to be in the malicious, mischievous false alarm group, however if it cannot be proven as such, then it should be coded as 622 – No Incident Found.
Even if there is no precise “dispatch address”, e.g. a smoke report in a general area with no reporting party (RP) address not callback, this UTL should be coded as 622 – No Incident Found.
All UTLs are coded as 622 – No Incident Found.
Wrong Location, No Emergency Found Group
These are some of the values in the wrong location / no incident found group:
- 621 – Wrong Location (e.g. maybe wrong fire district.)
- 622 – No Incident Found On Arrival At Dispatch Address
- 600 – Good intent call, other.
Unable To Locate verses Good Intent
Unable to locate is when nothing can be found at or in the area of the incident report. However if something is found, but not an incident (e.g. phone line down not powerline down, legal campfire not illegal or unattended campfire) then report a Good Intent incident type.
Unable To Locate verses Wrong Location
Unable to locate is when nothing can be found at or in the area of the incident report. However if something is found, but UTL incident Wrong location
Last Updated on April 19, 2023