CSA
UnknownUSDOT 1490103· CARRIER
⬇ PDF report

JAMES E CHURCH

8 RUSSELL STREET, FLEMINGBURG, KY, 41041(606) 849-2970KPTAX@FUSE.NETJAMES E CHURCH
Vetting snapshot
Authority
Unknown
per SAFER
Insurance
No active filing
not required
Vehicle OOS
—
no inspections
Driver OOS
—
no inspections
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.

Vehicle0 inspections · 0% OOS · National 22%
Driver0 inspections · 0% OOS · National 6.7%

Company profile

FMCSA census
Power units
0
on file (MCS-150)
Drivers
—
Annual mileage
—
Recordable crash rate
—
per million miles
Company officer
JAMES E CHURCH
Registered since
2006-04-19
Last MCS-150 update
2006-04-27
Census status
I

Fleet: 0 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.

Data change history

Every FMCSA record change we’ve detected — address, fleet size, contacts, MCS-150 — newest first.

Connections

carrier graph

This carrier shares officers or emails with 22 other carriers — review the connections below as part of your vetting.

22
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
22
Strong links
Strong· 22
1
ARTHUR L DE JONG
USDOT 1328411Inactive· SOUTH HOLLAND, IL
Strong
Email
2
BETH TRUCKING LLC
USDOT 1227384Inactive· MASON, OH
Strong
Email
3
BRIAN THIGPEN
USDOT 1445026Inactive· FAIRBORN, OH
Strong
Email
4
CARL A LOCKE JR
USDOT 2158728Inactive· LEWISPORT, KY
Strong
Email
5
CONDL TRUCK LINES INC
USDOT 1333213Inactive· ARLINGTON HEIGHTS, IL
Strong
Email
6
CRYSTAL G ROWLAND
USDOT 2035465Inactive· FLORENCE, KY
Strong
Email
7
DAKOTA STROUP
USDOT 2158651Inactive· OWENSBORO, KY
Strong
Email
8
DARYL J BLASY
USDOT 1333183Inactive· MCHENRY, IL
Strong
Email
9
DAVID RON MCDONNELL
USDOT 1860480Inactive· GERMANTOWN, OH
Strong
Email
10
DONALD CLARK
USDOT 1466704Inactive· BEAVERCREEK, OH
Strong
Email
11
GARNIK MARGARYAN
USDOT 1363739Inactive· CINCINNATI, OH
Strong
Email
12
J D E TRUCKING LLC
USDOT 1750220Inactive· WOOSTER, OH
Strong
Email
13
JAMES E CHURCH
USDOT 2469022Inactive· SPRINGFIELD, MO
Strong
Officer
14
JOHN T BRANSTON
USDOT 1333187Inactive· MARENGO, IL
Strong
Email
15
JOSEPH S MARINKAS
USDOT 1333285Inactive· AURORA, IL
Strong
Email
16
LASZLO BANYASZ
USDOT 2063672Inactive· VALENCIA, CA
Strong
Email
17
MARK KIELBUS
USDOT 1333230Inactive· ALGONQUIN, IL
Strong
Email
18
PHILLIPS TRUCKING
USDOT 1211597Inactive· CINCINNATI, OH
Strong
Email
19
RICHARD A BUCAR
USDOT 1333297Inactive· LAKE IN THE HILLS, IL
Strong
Email
20
ROBERT E MILLER
USDOT 1452239Inactive· LIMA, OH
Strong
Email
21
RONALD L GRANT
USDOT 1333221Inactive· HANOVER PARK, IL
Strong
Email
22
TIMOTHY R CUNNINGHAM
USDOT 1248816Inactive· FELICITY, OH
Strong
Email

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. 04/27/2006MCS-150 update filed
  2. 04/19/2006Registered with FMCSA

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

★

FMCSA safety rating

Rating
Not rated
Type
—
Rated
—
Last review
—
📄

MCS-150 registration

Form date
2006-04-27
Reported mileage
—
⚡

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 28, 2026, 5:42 AM. VioCodes is not affiliated with FMCSA. To dispute incorrect data, file a DataQs Request for Data Review.