Employer profile · to
NC-KANNA01
Federal OSHA safety record across 101 records in North Carolina.
How these records are matched, and what they cover. Records are grouped by normalized employer name. Nothing in OSHA's published files ties them to a legal entity. Unrelated companies that happen to share a name are combined onto one profile, and there is no EIN, address, or parent-company check to separate them; conversely, one company filing under several spellings can appear as several profiles. Severe-injury data covers establishments under federal OSHA jurisdiction only: about 22 states run their own OSHA-approved state plans, and severe-injury reports from those states are not in OSHA's published federal file. Verify against the linked OSHA source records before drawing any conclusion about a specific company.
At a glance
Federal OSHA records for NC-KANNA01 include 0 Severe Injury Reports, 101 Form 300/301 injury filings, and 0 OSHA inspections, spanning North Carolina, with records dated between and . Aggregated from three OSHA data feeds; per-record detail and source citations are linked below.
Most recent 25 of 101 Form 300/301 filings · Jan 17, 2023 – Nov 26, 2025.
Showing 25 of 101. full Form 300/301 record in the $149 report →
The complete federal record
OSHA is one federal index of many. Standard Record compiles this employer's file across federal agencies (labor, environmental, and transportation enforcement) into a single company record.
See NC-KANNA01's Standard Record on standardrecord.com →
Company facts
- Name as filed with OSHA
- NC-KANNA01
- States with records
- NC
Addresses on OSHA filings
- 52 records
- 6200 GORDON FOOD SERVICE DR, CONCORD, NC 48027
- 49 records
- 6200 GORDON FOOD SERVICE DR, CONCORD, NC 28027
Locations on record
Industries (NAICS codes on file)
Verified name family
A federal filing by the company itself — the same EIN on its OSHA, benefits, SEC, or IRS filings, or a trade name the carrier declared to FMCSA — ties 425 spellings to this one legal entity, holding 2,423 records combined. These are stated facts, not name resemblance.
- MA-TAUNT01
- 170 records · same EIN on federal filings
- TX-HOUST01
- 166 records · same EIN on federal filings
- GA-LITHI02
- 146 records · same EIN on federal filings
- KY-SHEPH01
- 141 records · same EIN on federal filings
- MI-BRIGH01
- 139 records · same EIN on federal filings
- OH-SPRIN01
- 121 records · same EIN on federal filings
- FL-PLANT01
- 92 records · same EIN on federal filings
- MI-WYOMI03
- 92 records · same EIN on federal filings
- PA-IMPER01
- 86 records · same EIN on federal filings
- MD-ABERD01
- 82 records · same EIN on federal filings
- WI-KENOS01
- 62 records · same EIN on federal filings
- TX-COPPE01
- 45 records · same EIN on federal filings
- +412 more filed names
- 980 records not listed here
Explore the full OSHA index
This is one employer's record. Look up OSHA accident reports by company across every employer in the index, or browse severe injury reports by year, state, and company.
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 only. That has two consequences worth stating plainly. Small variations in spelling, punctuation, and capitalization collapse to one profile, but so do unrelated companies that happen to share a name, because the published records carry no EIN, parent-company, or address key we can use to tell them apart. And a single company filing under materially different legal names (parent vs. subsidiary, or a distinct hyphenated spelling) will appear here as more than one profile, each showing only part of its record. Coverage is federal only: severe-injury data covers establishments under federal OSHA jurisdiction, and about 22 states run their own OSHA-approved state plans whose severe-injury reports are not in OSHA's published federal file. Verify every record against the OSHA source linked from its detail page.