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

Newark, NJ —

OSHA Injury Report: Flying food Group

Injury · Job transfer or restriction

At a glance

On , an injury at Flying food Group in 640 Frelinghuysen Ave, Newark, NJ 07108 resulted in job transfer or restriction. Employee was driver in banquet halls with catering staff.

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

Where did this happen?

Establishment
Flying food Group
Parent company
Flying Food Group
Street
640 Frelinghuysen Ave
City
Newark
State
NJ
ZIP
07108
On-site location
Loading dock inside dishroom

What was the outcome?

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

Before the incident

On loading the truck carrying the airline trolleys

What happened

While closing the truck rear door employee put his left hand between the door getting his fingers caught

Injury or illness

Caught in object

Object or substance involved

Truck Rear door

Summary line

Laceration of the left ring finger without foreign body with damage to nail

Employee and industry

Job description
Driver
SOC code
9999 — Uncoded
NAICS code
722320 — Banquet halls with catering staff
NAICS vintage
2022
Avg employees
569
Total hours worked
1007267
EIN
364331472
Establishment ID
1251407
Employer case #
2440392262

When (timing detail)

Date of incident
Shift started
13:30:00.000
Time of incident
15:00:00.000
Filing year
2023
Submitted
03DEC24:22:28:00

More injuries at Flying food Group

View Flying food Group's full OSHA safety record →

More injuries in this industry (NAICS 722320)

More injuries in NJ

SECAUCUS, NJ—

WM 3520

RIVERDALE, NJ—

WM 3443

Source

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