Understanding reporting rules helps companies avoid penalties and enforcement actions.
Proper reporting demonstrates proactive compliance and safety accountability.
The DOT doesn’t leave incident reporting to guesswork—there are clear rules on when and how to report hazardous materials incidents. Found in 49 CFR Part 171, Subpart B, these regulations define which events require immediate reporting, which need follow-up documentation, and who’s responsible for filing the report.
§171.15 – Immediate Reporting for Serious Incidents
Some incidents require a call to the National Response Center as soon as possible, including when:
Someone is killed.
Someone is hospitalized.
The public is evacuated for one hour or more.
A major transportation route or facility is closed for an hour or more.
These high-severity events almost always trigger a DOT inspection. If the incident involves air transport—such as a lithium battery thermal event—you can expect the FAA to get involved quickly.
§171.16 – Detailed Written Reports
For incidents not covered under §171.15, companies must still submit a written incident report within the timelines specified in the regulation. This ensures PHMSA has complete records of hazardous materials events, even if they’re less severe.
Special Permits and Air Transport
If a shipment is moving under a special permit, the permit holder must contact PHMSA for any incident. Air transport incidents carry heightened scrutiny because of their potential safety risks.
Why Understanding the Rules Matters
Knowing these reporting requirements:
Helps you stay compliant and avoid fines.
Ensures you respond appropriately to any incident.
Positions your company as proactive and safety-focused when regulators arrive.
Questions about your specific situation? Book a call with our expert today!
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
SourceBuster is used by WooCommerce for order attribution based on user source.
Name
Description
Duration
sbjs_session
The number of page views in this session and the current page path
30 minutes
sbjs_udata
Information about the visitor’s user agent, such as IP, the browser, and the device type
session
sbjs_first
Traffic origin information for the visitor’s first visit to your store (only applicable if the visitor returns before the session expires)
session
sbjs_current
Traffic origin information for the visitor’s current visit to your store
session
sbjs_first_add
Timestamp, referring URL, and entry page for your visitor’s first visit to your store (only applicable if the visitor returns before the session expires)
session
sbjs_current_add
Timestamp, referring URL, and entry page for your visitor’s current visit to your store
session
sbjs_migrations
Technical data to help with migrations between different versions of the tracking feature