2,042,423Injury reports 130,778Establishments Most recent incident 2025-12-31
Safety Incidents OSHA Severe Injury Reports · 2015–2025

Newton, MS —

OSHA Injury Report: La-Z-Boy South, Newton MS

Injury · Job transfer or restriction

At a glance

On , an injury at La-Z-Boy South, Newton MS in 133 Scanlan Street, Newton, MS 39345 resulted in job transfer or restriction. Employee was router Operator in furniture, household-type, upholstered on frames of any material, manufacturing.

Where did this happen?

Establishment
La-Z-Boy South, Newton MS
Parent company
La-Z-Boy, Newton MS
Street
133 Scanlan Street
City
Newton
State
MS
ZIP
39345
On-site location
Router Operating Parts Table

What was the outcome?

Outcome
Job transfer or restriction (code 3)
Type
Injury (code 1)
Days restricted or transferred
5

Before the incident

Removing cut parts from router table.

What happened

Employee was removing cut parts from the router table placing them on inspection table and strained lower back.

Injury or illness

Strain to lower back.

Object or substance involved

Employee repetitive motion.

Summary line

Employee removing cut parts from router table turned and strained lower back.

Employee and industry

Job description
Router Operator
SOC code
51-7042 — Woodworking Machine Setters, Operators, and Tenders, Except Sawing
NAICS code
337121 — Furniture, household-type, upholstered on frames of any material, manufacturing
NAICS vintage
2022
Avg employees
257
Total hours worked
343233
EIN
331098685
Establishment ID
984921
Employer case #
2

When (timing detail)

Date of incident
Shift started
14:15:00.000
Time of incident
15:00:00.000
Submitted
18JAN24:16:46:00

More injuries at La-Z-Boy South, Newton MS

View La-Z-Boy South, Newton MS's full OSHA safety record →

More injuries in this industry (NAICS 337121)

More injuries in MS

TUPELO, MS—

WM 391

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.