Loudon, TN —
OSHA Injury Report: Purdy Brothers Trucking Loudon, TN
Injury · Days away from work
At a glance
On , an injury at Purdy Brothers Trucking Loudon, TN in Loudon, TN 37774 resulted in days away from work. Employee was over the Road Truck Driver in general freight trucking, long-distance, truckload (TL).
Where did this happen?
- Establishment
- Purdy Brothers Trucking Loudon, TN
- Parent company
- Purdy Brothers Trucking, LLC
- Street
- 199 Commercial Park Drive
- City
- Loudon
- State
- TN
- ZIP
- 37774
- On-site location
- I-40 West Rest Area - Jackson TN
What was the outcome?
- Outcome
- Days away from work (code 2)
- Type
- Injury (code 1)
- Days away from work
- 40
Before the incident
Driver was going to a rest area on [REDACTED] to walk her dog. As she was approaching the rest area she saw a glow near a trailer tire out of her passenger side mirror. She stopped at the rest area and grabbed her fire extinguisher. She went to the rear of the trailer and deployed her fire extinguisher.
What happened
As the fire was being extinguished the heat from the fire caused the brake chamber to blow and caused her to fall.
Injury or illness
Head contusion fractured patella to R knee.
Object or substance involved
Brake chamber
Summary line
R knee injury after brake chamber blew on the rear of trailer from fire causing the driver to fall at ground level.
Employee and industry
- Job description
- Over the Road Truck Driver
- SOC code
- 53-3032 — Heavy and Tractor-Trailer Truck Drivers
- NAICS code
- 484121 — General freight trucking, long-distance, truckload (TL)
- NAICS vintage
- 2022
- Avg employees
- 193
- Total hours worked
- 472152
- EIN
- 471655633
- Establishment ID
- 616138
- Employer case #
- 202300205
When (timing detail)
- Date of incident
- Shift started
- 1:00:00.000
- Time of incident
- 4:30:00.000
- Submitted
- 28FEB24:15:39:00
Source
Data from OSHA ITA Form 300/301 electronic submissions, filing year unspecified. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.