Safety Incidents OSHA Severe Injury Reports · 2015–2025
5,189,992Inspections Most recent open 2026-07-18 Last loaded 2026-07-22

OSHA Inspection: BALTIMORE CITY FIRE DEPARTMENT

Accident-driven inspection · Safety discipline

On , OSHA opened an accident-driven safety inspection of BALTIMORE CITY FIRE DEPARTMENT in 143 SOUTH CALVERTON ROAD, BALTIMORE, MD 21223 (NAICS 922160). OSHA activity number 308984350.

What this inspection record means

OSHA opens inspections for many reasons — routine scheduling under a national or local emphasis program, an employee complaint or referral, or a follow-up after a reported injury. Opening or conducting an inspection is not itself an allegation or a finding that this employer broke any rule; any findings appear as the citations listed below, and citations can be contested, reduced, or withdrawn.

Watch Baltimore City Fire Department — free Get an email when a new federal OSHA severe-injury report for Baltimore City Fire Department is published. One employer, no account, unsubscribe in one click.
Site address
143 SOUTH CALVERTON ROAD
City
BALTIMORE
State
MD
ZIP
21223
Mailing
CALVERTON & FREDERICK ROAD, BALTIMORE, MD 21223
Inspection type
Accident-driven (A)
Scope
Partial (B)
Discipline
Safety
Advance notice
No
Union status
Y
Opened
Closing conference
Case closed
Last modified
Data loaded
NAICS code
922160
SIC code (legacy)
9224
Employees
1300
Ownership type
A

33 citations on file for this inspection.

50104 A

Willful 1 instance 50 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

50104 A

Willful 1 instance 50 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

50104 A

Willful 1 instance 50 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

50104 A

Willful 1 instance 50 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

50104 A

Willful 1 instance 50 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

50104 A

Willful 1 instance 50 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

50104 A

Willful 1 instance 50 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

50104 A

Willful 1 instance 50 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

50104 A

Willful 1 instance 50 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

50104 A

Willful 1 instance 10 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

50104 A

Willful 1 instance 50 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

50104 A

Willful 1 instance 50 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

50104 A

Willful 1 instance 50 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

50104 A

Willful 1 instance 50 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

50104 A

Willful 1 instance 50 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

50104 A

Willful 1 instance 50 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

50104 A

Serious 1 instance 50 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

50104 A

Serious 1 instance 50 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

50104 A

Serious 1 instance 50 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

50104 A

Serious 1 instance 50 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

50104 A

Serious 1 instance 50 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

50104 A

Serious 1 instance 50 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

50104 A

Serious 1 instance 50 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

50104 A

Serious 1 instance 50 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

50104 A

Serious 1 instance 50 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

50104 A

Serious 1 instance 50 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

50104 A

Serious 1 instance 50 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

50104 A

Serious 1 instance 50 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

50104 A

Serious 1 instance 50 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

50104 A

Serious 1 instance 50 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

50104 A

Serious 1 instance 50 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

50104 A

Serious 1 instance 50 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

50104 A

Serious 1 instance 50 exposed
Issued
Jun 26, 2007
Abate by
Jul 2, 2007

View Baltimore City Fire Department's full OSHA safety record →

This record is reproduced from the U.S. Department of Labor Open Data API (OSHA inspection dataset). The original IMIS detail view is available at OSHA's Establishment Search for activity number 308984350.

Look up any company's OSHA accident reports by company, or browse severe injury reports by year, state, and company.