- When you place/move your burn dot on the map on any form, airshed, elevation, county, (non)attainment, and class 1 areas are automatically calculated
In addition, burns above 6500 feet are now considered to be in the named airshed (for example “9-Uinta Basin” or “3-Virgin River”) in order to consider cumulative effects and nighttime down drainage flows. High elevation airshed 16 (above 6500’) is still valid, it will be considered in the approval process, and can be a way to assess clearing index if using the NWS clearing index by airshed table.
- The system will track the use of HB92 and de minimis (if CI 400-499)
Ordinarily burn approval is conditional on clearing index being 500 +. Quite often burn requests cover multiple days, some of which have clearing index 500+, and others not. Burners can now select more than one avenue,
although additional follow up is still required when burning < 500 CI. Contact the coordinator or see the burn request how-to video for more details.
- The form numbers (2, 3, 4, 5) have gone away.
The
numbers did not have a clear meaning.
Now the progression of forms when doing Rx, in order, is to:
-
Register
a prescribed fire project in the system (One time only, generally once
for each burn plan). This takes the place of “Form 3 pre-burn
information”
-
Request
a burn window (preferred two days before ignition). Formerly “Form 4”
-
Report
emissions post-burn. An abbreviated report is required if you request a
window and don’t burn. This has always been the case, but was
challenging to implement. Formerly “Form 5 accomplishment”
Requesting a window and reporting emissions can be done as many times as
you like for any given burn project.
There is also an annual schedule requirement, this was
formerly known as “Form 2” and was tied up in the “pre burn information /
Form 3” in the old system but now it is a separate table.
One burn boss mentioned to me that since their burn plan specifically
mentions form numbers 3,4, and 5, he felt he may need to do an
amendment
. The new forms comply with the SMP
and state regulation, and capture the same information, so I hope that is
not necessary, and if you need documentation on this I can provide it at
any time
- Burn project codes have gone away.
For example “DIF1202” or “SES1901”.
Names are used to distinguish the burn projects from each other. I know some burn plans mention this number,
you are welcome to keep using the old numbers. If you need documentation of a smoke “number” for a new project, reach out to me and I can get it to you.
- Forms will not have a “DRAFT” status
A registered burn project has no status, either it exists or it doesn’t.
When you submit a burn request it will immediately be “under review”, and it can be shifted to “pending approval”, “approved”, or “denied”.
When you submit an emissions report it will immediately be “under review”, and can be shifted to “approved”.
- If no burning occurs during a burn request window, that information is captured consistently
An abbreviated emissions report is required if you request a burn window and don’t burn. The system will remind users if they forget.
- Too many small changes to list
Hopefully this system will be more intuitive. If you see anything that needs improvement or is confusing, please bring it to the coordinator's attention.