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

Brenham, TX —

OSHA Injury Report: Kruse Village

Injury · Job transfer or restriction

At a glance

On , an injury at Kruse Village in 1700 East Stone St, Brenham, TX 77833 resulted in job transfer or restriction. Employee was culinary in continuing care retirement communities.

Watch Kruse Village — free Get an email when a new federal OSHA severe-injury report for Kruse Village is published. One employer, no account, unsubscribe in one click.

Where did this happen?

Establishment
Kruse Village
Parent company
Kruse Village
Street
1700 East Stone St
City
Brenham
State
TX
ZIP
77833
On-site location
Kitchen Area

What was the outcome?

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

Before the incident

Sharpening a knife

What happened

EE states she was sharpening a knife when the knife slipped and lacerated her left ring finger and pinky finger. EE is right hand dominant and supervisor was notified.

Injury or illness

Laceration to left hand

Object or substance involved

Knife

Summary line

Laceration to left hand

Employee and industry

Job description
Culinary
SOC code
9999 — Uncoded
NAICS code
623311 — Continuing care retirement communities
NAICS vintage
2022
Avg employees
91
Total hours worked
158002
EIN
300741595
Establishment ID
1250558
Employer case #
2

When (timing detail)

Date of incident
Shift started
10:00
Time of incident
11:00
Filing year
2024
Submitted
31JAN2025:17:32:00

More injuries at Kruse Village

View Kruse Village's full OSHA safety record →

More injuries in this industry (NAICS 623311)

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.