Employer profile — 1982-08-06 to 2015-02-10

IBM CORPORATION

Federal OSHA safety record across 4 records in 4 states.

At a glance

Federal OSHA records for IBM CORPORATION include 1 Severe Injury Report, 0 Form 300/301 injury filings, and 3 OSHA inspections, spanning 4 states, with incidents dated between 1982-08-06 and 2015-02-10. Aggregated from three OSHA data feeds; per-record detail and source citations are linked below.

Compliance History Report IBM CORPORATION's full severe-injury history, benchmarked against its sector and the national average — one portable, citable document.

Get the report →

Ongoing Severe-Injury Monitor A private watch page for IBM CORPORATION, refreshed daily as new federal OSHA severe injuries are published — with full history and benchmark. $99/mo, cancel anytime.

Start monitoring →

By source

SIR1 record Injuries0 records Inspections3 records

Severe Injury Reports — 1

Date range2015-02-10

Most recent 1 of 1 reports for this employer.

HOPEWELL JUNCTION, NEW YORK — 2015-02-10

IBM CORPORATION

EventExposure through intact skin, eyes, or other exposed tissue

Hospitalized

ITA Form 300/301 Injury Reports — 0

No ITA Form 300/301 injury filings recorded for this employer.

OSHA Inspections — 3

Date range1982-08-06 to 1987-02-05

Most recent 3 of 3 inspections for this employer.

ESSEX JUNCTION, VT — 1987-02-05

No OSHA citations recorded for this employer.

Locations on record

BOULDER, CO: 1 record
HOPEWELL JUNCTION, NEW YORK: 1 record
New York -Richmond, NY: 1 record
ESSEX JUNCTION, VT: 1 record

Industries (NAICS codes seen)

NAICS 000000: —
NAICS 334413: —

Sources

This profile aggregates federal OSHA records from three published feeds: OSHA Severe Injury Reports, the ITA Establishment-Specific Injury and Illness Data (Form 300/301), and the U.S. Department of Labor Open Data API (OSHA inspections). Records are matched to this employer by normalized name; small variations in spelling, punctuation, and capitalization collapse to one profile, while materially different legal entities (e.g. parent vs. subsidiary with distinct hyphenated names) remain separate.