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

Baytown, TX —

OSHA Injury Report: Jindal Pipe USA Inc.

Injury · Other recordable case

At a glance

On , an injury at Jindal Pipe USA Inc. in 1411 FM 565, Baytown, TX 77523 resulted in other recordable case. Employee was general labor in pipe (e.g., heavy riveted, lock joint, seamless, welded) made from purchased iron or steel.

Where did this happen?

Establishment
Jindal Pipe USA Inc.
Parent company
Jindal PIPE USA LLC
Street
1411 FM 565
City
Baytown
State
TX
ZIP
77523
On-site location
Hydro

What was the outcome?

Outcome
Other recordable case (code 4)
Type
Injury (code 1)

Before the incident

Employee [REDACTED] was grinding a pipe and had to walk outside to push a pipe at table #4.

What happened

When pushing the pipe down the table the pipe hit another pipe and rolled back pinching [REDACTED] 's finger in between the two.

Injury or illness

Laceration to left pinky finger.

Object or substance involved

Pipe

Summary line

Laceration to left pinky finger.

Employee and industry

Job description
General labor
SOC code
53-7062 — Laborers and Freight, Stock, and Material Movers, Hand
NAICS code
331210 — Pipe (e.g., heavy riveted, lock joint, seamless, welded) made from purchased iron or steel
NAICS vintage
2012
Avg employees
213
Total hours worked
582194
Establishment ID
1036303
Employer case #
13

When (timing detail)

Date of incident
Shift started
6:47
Time of incident
22:25
Filing year
2024
Submitted
31JUL2025:19:05:00

More injuries at Jindal Pipe USA Inc.

View Jindal Pipe USA Inc.'s full OSHA safety record →

More injuries in this industry (NAICS 331210)

More injuries in TX

AMARILLO, TX—

WM 4464

VICTORIA, TX—

WM 4194

FORT WORTH, TX—

WM 3005

ARLINGTON, TX—

WM 2977

SAN ANTONIO, TX—

WM 1803

Source

Data from OSHA ITA Form 300/301 electronic submissions, filing year 2024. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.