CSA
Not AuthorizedUSDOT 1083108· MC449527· CARRIER· EIN 43730023
⬇ PDF report

POWER LOGISTICS CORPORATION

1282 LEWISBURG PIKE, FRANKLIN, TN, 37064(615) 550-5000tawatson@bellsouth.netLISA WATSON
Vetting snapshot
Authority
Inactive
operating authority
Insurance
No active filing
not required
Vehicle OOS
—
no inspections
Driver OOS
—
no inspections
Crashes 24mo
0
clean
Red flags
None
nothing flagged
45
/ 100

Risk factors

High riskVioCodes score
Operating authority is not active

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.

Authority & insurance

MC449527

Operating authority and insurance on file — from FMCSA Licensing & Insurance (L&I).

Common
None
Contract
None
Broker
None
Authorized for: Property
Liability (BIPD)
No active filing
not required
Cargo
Not on file
not required
Bond / surety
Not on file
required
Authority history (1) ▾
02/06/2003PROPERTY BROKERDISMISSED

Source: FMCSA Licensing & Insurance (L&I), public data. This shows the carrier’s federal insurance filings (BMC-91X liability, BMC-34 cargo) — the federally-required minimums on file for operating authority — not the carrier’s full commercial policy (its actual auto combined-single-limit, general liability, cargo, or workers’ comp, which appear on the carrier’s ACORD certificate of insurance). Always confirm current coverage with a COI from the carrier’s agent before making a vetting decision.

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
1
on file (MCS-150)
Drivers
1
0 hold a CDL
Annual mileage
—
reported 0
Recordable crash rate
—
per million miles
How far they run · drivers by operating lane
  • Interstate · <100 mi1 drivers
Company officer
LISA WATSON
Operation
Interstate
Registered since
2002-12-26
Last MCS-150 update
2004-08-18
Census status
I

Fleet: 1 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 addresses, phone numbers or officers with 5 other carriers — review the connections below as part of your vetting.

5
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
3
Strong links
Strong· 3
1
AMERICAS BEST MOVING SYSTEM CHARLOTTE
USDOT 1351662Inactive· MIDLAND, NC
Strong
Officer
2
CLINTON WATSON
USDOT 3122506Active· CASTLEBERRY, AL
Strong
Officer
3
LAS WATER METERING SERVICES LLC
USDOT 4075822Inactive· TRINITY, TX
Strong
Officer
Medium· 2
THOMAS WATSON
USDOT 1230759Inactive· FRANKLIN, TN
Medium
MailingPhoneAddress
TLW LLC
USDOT 1466042Inactive· FRANKLIN, TN
Medium
MailingPhoneAddress

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

3 events
  1. 08/18/2004MCS-150 update filed
  2. 02/06/2003PROPERTY BROKER — DISMISSED
  3. 12/26/2002Registered with FMCSA

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

🚛

Operations

Area served

  • Interstate
★

FMCSA safety rating

Rating
Not rated
Type
—
Rated
—
Last review
—
📄

MCS-150 registration

Form date
2004-08-18
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 27, 2026, 5:49 PM. VioCodes is not affiliated with FMCSA. To dispute incorrect data, file a DataQs Request for Data Review.