CSA
UnknownUSDOT 10301· CARRIER· EIN 54-0331860
⬇ PDF report

PAXTON COMPANY

1111 INGLESIDE RD, NORFOLK, VA, 23502(757) 853-6781billj@paxtonco.comJAMES BEALE
Vetting snapshot
Authority
Unknown
per SAFER
Insurance
No active filing
not required
Vehicle OOS
2.9%
below 22% national avg
Driver OOS
5.7%
below 6.7% national avg
Crashes 24mo
0
clean
Red flags
None
nothing flagged
100
/ 100

Risk factors

Low riskVioCodes score
No red flags in the public FMCSA record

A weighted read of the public FMCSA signals below — authority, insurance, out-of-service, crashes, roadside OOS rates, and carrier connections. A starting point for vetting, not a guarantee.

Roadside inspection performance

Out-of-service rate vs national average. Lower is better.

Vehicle34 inspections · 2.9% OOS · National 22%
Driver35 inspections · 5.7% OOS · National 6.7%

CSA performance breakdown

FMCSA · Sep 2026

35 inspections · 12 violations (3 OOS) · 10% of inspections had an OOS finding.

35
Inspections
12
Violations
3
OOS violations
8
Distinct codes

Violations by BASIC

click to filter codes

12
total

Most inspected in · top 3 states

  • MD19
  • NC10
  • DE1

Latest FMCSA SMS snapshot. Codes link to the lookup — severity weighting, contest angles, and the DataQs Drafter for each. Click a BASIC to filter the codes.

Recommendations

What’s driving each score, what to do about it, and where it could go.

A high share of violations are occurring in Wicomico County, MD

Medium impact

6 of 6 violations in the last 12 months (100%) came from inspections in Wicomico County, MD. That can mean tougher enforcement there or simply more of your miles run through it — either way it's worth a look.

What to do
  • Review the inspections from Wicomico County, MD to spot recurring issues
  • Brief drivers running that lane; consider rerouting around the toughest enforcement corridors where practical

Following / lane / reckless violations are the leading contributor to Unsafe Driving

Low impact

Estimated Unsafe Driving percentile of 15% is under the 60% line. In decent shape, but here's what's driving it.

What’s contributing5 violations (24 mo)
Following / lane / reckless3 viol59%
  • 392.2-SLLTCDState/Local Laws - Failed to obey a traffic control device - Permanent or Temporary - e.g., safety official, signal, sign, light, lane marking, other3× · 59%
Speeding1 viol24%
  • 392.2-SLLS3State/Local Laws - Speeding 11-14 miles per hour over the speed limit1× · 24%
Phone / texting1 viol17%
  • 392.2-SLLCPState/Local Laws - Operate a CMV while using a cellular phone1× · 17%
What to do
  • Defensive-driving refresher on following distance and lane discipline
Projected estimatecould improve up to 9 pts in ~12 mo
nowin 12 months
Current trend 50% followed 100% followed 60% line

Hours-of-Service Compliance needs attention

Low impact

Estimated Hours-of-Service Compliance percentile of 0% is under the 60% line. In decent shape, but here's what's driving it.

What to do
  • Review recent inspections with violations in this BASIC and take remedial action with drivers/equipment

Controlled Substances/Alcohol needs attention

Low impact

Estimated Controlled Substances/Alcohol percentile of 0% is under the 75% line. In decent shape, but here's what's driving it.

What to do
  • Review recent inspections with violations in this BASIC and take remedial action with drivers/equipment

Recommendations are generated from the carrier’s public FMCSA roadside-inspection record. Percentiles and projections are VioCodes estimates, not official FMCSA figures. Informational, not legal advice.

90-day safety improvement plan

What this carrier has struggled with most in the last 90 days — where to focus now.

Holding steady
2
Inspections
1
Violations
0
Out-of-service
1
Clean
Where the violations are
Unsafe Driving 100%
Focus here first
1Unsafe Driving
1 violation · 100% of recent
  • 392.2-SLLTCDState/Local Laws - Failed to obey a traffic control device - Permanent or Temporary - e.g., safety official, signal, sign, light, lane marking, other
Do this
  • Walk the lights every pre-trip and carry spare bulbs/fuses
  • Clean lenses and check the trailer plug for corrosion
🎓
Turn these into driver coaching — and prove it
FleetTrained (my companion project) makes branded, multilingual training videos for these exact violations — your driver watches and gets a completion certificate for the file.

Based on roadside inspections in the last 90 days, ranked by what recurs most. Informational, not legal advice.

Inspection & crash map

live · FMCSA MCMIS

Every inspection and crash on record — hover a point for the summary, click for full detail (codes, severity, CSA points).

47
Inspections
18
Violations
3
Out-of-service
94
CSA points
12
Crashes
4
States
cleanviolOOS

CSA points = violation severity weight × FMCSA time weight (3× in the last 6 months, 2× at 6–12, 1× at 12–24). Points are spread within each state — FMCSA records the inspection state, not an exact location. Source: FMCSA MCMIS.

Equipment

VINs via NHTSA

12 distinct vehicles seen in this carrier’s roadside inspections.

12 incomplete vehicle
2023 ISUZU NRRseen 9×
JALE5W166P7301174· UB18774 VA
2024 ISUZU NRRseen 7×
JALE5W166R7310847· UC26057 VA
2024 ISUZU NRRseen 7×
JALE5W166R7309472· UA63764 VA
2023 ISUZU NPR-HDseen 6×
54DC4W1D4PS201660· 1FD6163 MD
2022 ISUZU NRRseen 5×
JALE5W165N7303589· UC33099 VA
2023 ISUZU NRRseen 2×
JALE5W161P7303849· UA85490 VA
2019 HINO XJC740 / XFC740seen 2×
JHHSDM2H9KK010196· UA31455 VA
2023 ISUZU NRRseen 2×
JALE5W166P7301806· UB57673 VA
2023 ISUZU NRRseen 2×
JALE5W160P7303163· UA85466 VA
2018 HINO XJC740 / XFC740seen 2×
JHHSDM2HXJK007757· TX315617 VA
2020 HINO XJC740 / XFC740seen 2×
JHHSDM2H1LK012798· UA20294 VA
2025 ISUZU NRR
JALE5W164S7P00593· UC33100 VA

Equipment is inferred from VINs recorded on roadside inspections (FMCSA MCMIS), decoded via the NHTSA vPIC API — it reflects vehicles inspected, not a current fleet roster.

Company profile

FMCSA census

PRIVATE PROPERTY

Power units
29
on file (MCS-150)
Drivers
29
20 hold a CDL
Annual mileage
1.4M mi
reported 2025
Recordable crash rate
per million miles
How far they run · drivers by operating lane
  • Interstate · 100+ mi23 drivers
  • Intrastate · <100 mi6 drivers
Company officer
JAMES BEALE
Operation
Interstate · Hazmat
D-U-N-S
3179074
Registered since
1974-06-01
Last MCS-150 update
2026-01-06
Census status
Active

Fleet: 29 trucks.

Source: FMCSA Company Census File (data.transportation.gov). Fleet and driver counts are self-reported on the carrier’s most recent MCS-150 filing.

Connections

carrier graph

This carrier shares officers with 1 other carrier — review the connections below as part of your vetting.

1
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
1
Strong links
Strong· 1
1
JAMES BEALE TRUCKING INC
USDOT 1045858Active· GARDNERVILLE, NV
Strong
Officer

Shared VINs come from FMCSA roadside-inspection records — a vehicle inspected under more than one carrier, often a fleet transfer or trailer interchange. Other links come from the FMCSA census. Shared identifiers are common and often legitimate — treat these as leads to investigate, not proof of wrongdoing.

Activity history

2 events
  1. 01/06/2026MCS-150 update filed

    1.4M mi reported (2025)

  2. 06/01/1974Registered with FMCSA

    PRIVATE PROPERTY

Merged from FMCSA authority, insurance, out-of-service, and census records.

🚛

Operations

Classification

  • PRIVATE PROPERTY

Area served

  • Interstate

FMCSA safety rating

Rating
Not rated
Type
Rated
Last review
2009-09-01
📄

MCS-150 registration

Form date
2026-01-06
Reported mileage
1,400,000 mi (2025)
📜

Changes on file

FMCSA census history
  1. November, 2022

    • Moved to NORFOLK, VA
  2. January, 2021

    First on-record entry — PAXTON COMPANY, ,

Got a violation you want to contest?

Use the free AI-powered DataQs Drafter to generate a polished challenge letter — quotes the relevant 49 CFR, predicts your grant chance.

Open the Drafter →
Data sourced from public FMCSA records via safer.fmcsa.dot.gov · Latest FMCSA update: Sep 2026 · Page refreshed: Sep 20, 2026, 11:33 PM. VioCodes is not affiliated with FMCSA. To dispute incorrect data, file a DataQs Request for Data Review.