PELICAN HAULING AND TRANSPORT LLC

Louisburg, NC · Interstate · 3 power units · Not rated · USDOT since May 15, 2020 (6 years)

No risk signals found

How risk signals work

Nothing in the FMCSA record matched our risk signals. That is not a guarantee, and it does not confirm who you are talking to; follow the checks below.

Confirm on Motus ↗ Call (330) 416-1503 Safety: SAFER ↗
Operating authority
Active
MC1110349: Motor carrier active
FMCSA Motus · Oct 19, 2026
Liability insurance (BI&PD)
$1,000,000
Required minimum: $1,000,000
No cargo cover filed with FMCSA
FMCSA Motus · Oct 19, 2026
Vehicle out-of-service rate
Not enough data
No vehicle inspections in this period
FMCSA inspections · Oct 19, 2024 – Oct 19, 2026

Green means the FMCSA record shows it. It does not confirm who you are talking to, or that a policy covers your specific load.

Confirm on Motus ↗Call

Operating authority

MC1110349 FMCSA Motus · Oct 19, 2026

Motor carrier
Motor Carrier of Property (Except Household Goods)
Active
Liability insurance on file$1,000,000 (required: $1,000,000)

Confirm current authority: Motus record for USDOT 3428808 ↗

Insurance on file

Liability (BI&PD) pays for injury and damage to other people and property; it does not cover the freight. Cargo insurance covers the freight. FMCSA only requires cargo filings from household goods carriers and freight forwarders, so most carriers file none: ask for a cargo certificate that fits your load. No cargo cover filed with FMCSA.

TypeDocketLayerInsurerCoverageEffectiveStatus
Liability (BI&PD)MC1110349—Stonewood Insurance Company
Policy JST1007021 · BMC-91X
$1,000,000Jul 24, 2026Active

Source: FMCSA Motus · Oct 19, 2026. Identical filings repeated in the FMCSA data are shown once; a filing listed under two dockets is one policy, not extra coverage. Coverage is the maximum amount filed with FMCSA, not the full policy.

Confirm current filings: Motus record ↗ and ask the insurer for a certificate naming you as holder.

Roadside inspections Oct 19, 2024 – Oct 19, 2026

4inspections
—vehicle out-of-service
0 of 0 · North Carolina avg 21.9%
0.0%driver out-of-service
0 of 4 · North Carolina avg 5.9%
6violations written on inspection reports
4 most recent inspections
DateStateLevelViolationsOut of service
Aug 26, 2026NE31No
Jul 18, 2026AR31No
May 22, 2026GA32No
Feb 11, 2025PA32No
How these rates are calculated

Period: Oct 19, 2024 – Oct 19, 2026. Vehicle rate = vehicle inspections with a vehicle out-of-service order ÷ vehicle inspections (levels 1, 2, 5 and 6). Driver rate uses levels 1, 2, 3 and 6. The North Carolina average covers 60,599 vehicle and 118,016 driver inspections of all North Carolina-based carriers in this period. It mixes every type of operation, so compare with care; rates based on a handful of inspections say little. FMCSA's own SMS measures are weighted differently: SMS profile ↗ · SAFER snapshot ↗

Violations in FMCSA's SMS last 24 months

1 violation counted in FMCSA's Safety Measurement System (SMS), 0 of them serious enough to put the driver or vehicle out of service.

Why is this different from the 6 violations above?

The inspections section's number counts every violation written on the inspection reports in our Oct 19, 2024 – Oct 19, 2026 window. The SMS count comes from FMCSA's own monthly SMS snapshot, which uses its own 24-month window and only the violations it scores. Both are FMCSA figures; they measure different things.

Category (FMCSA BASIC)ViolationsOut of serviceShareNorth Carolina share
Hours-of-Service Compliance10100.0%15.9%
1 most frequent violations
ViolationTimesOut of service
HOS (ELD) Driver failing to have instruction sheet describing the data transfer mechanisms supported by the ELD and step-by-step instructions for the driver to pr
EOBR Related · Hours-of-Service Compliance · code 39522H2ELDNISDT
10

Source: FMCSA SMS violation file, inspections in the last 24 months, published Oct 19, 2026. "Share" is this company's mix of violations; the North Carolina column is the mix across all North Carolina-based carriers, so you can see which kinds of problems stand out. A high count partly reflects fleet size and how often trucks are inspected.

Crashes Oct 19, 2024 – Oct 19, 2026

1crashes
0fatal
1injury
0tow-away
Crash details
DateLocationFatalitiesInjuries
Jun 18, 2025High Point, NC02

Reportable crashes do not imply the carrier was at fault.

Company details FMCSA census · Oct 19, 2026

USDOT number3428808
MC / docketMC1110349
Legal namePELICAN HAULING AND TRANSPORT LLC
OperationInterstate
Business type—
Power units3
Drivers4
Annual mileage127,000 (2025)
HazmatYes
Safety ratingNot rated (no compliance review on record)
USDOT number addedMay 15, 2020 · 6 years ago
Last MCS-150 updateJan 21, 2026

Cargo carried

General FreightDrive/Tow AwayBuilding MaterialsMachinery, Large ObjectsConstruction

Change history

No changes to name, contact details, authority or insurance since we started tracking on Oct 18, 2026. We compare every company's FMCSA record each day.

to see it on your watchlist when something changes.

Questions about PELICAN HAULING AND TRANSPORT LLC

What does PELICAN HAULING AND TRANSPORT LLC's operating authority allow?

MC1110349: Motor carrier (may haul regulated property for hire).

Which information about PELICAN HAULING AND TRANSPORT LLC is old or missing?

There are too few vehicle inspections in the last 24 months to judge the out-of-service rate. FMCSA has not issued a safety rating, which means no compliance review is on record, not that the carrier is unsafe.

What should I verify before booking PELICAN HAULING AND TRANSPORT LLC?

Confirm the authority and insurance on the Motus record for USDOT 3428808. Call the company back on the phone number on file, (330) 416-1503, not a number from an email or load board message. Check that the MC number the dispatcher gave you matches MC1110349, and ask the insurer for a certificate of insurance naming you as holder, with cargo coverage that fits your load.

Company details from the FMCSA Company Census File (Oct 19, 2026). Inspections and crashes from FMCSA MCMIS files. About our data · Report an error on this page (how corrections work).

Page generated 2026-10-20 02:14 UTC.