Not AuthorizedUSDOT 1266790· MC496016· CARRIER· EIN 35-2233840

METRO TOWING LLC

5719 LEESBURG PIKE, FALLS CHURCH, IN, 46375(703) 906-6093SATINDER SINGH

Vetting snapshot

Authority

Inactive

operating authority

Insurance

No active filing

$750K required — verify

Vehicle OOS

—

no inspections

Driver OOS

—

no inspections

Crashes 24mo

clean

Red flags

1 flag

see details below

/ 100

Risk factors

High riskVioCodes score

Operating authority is not activeNo active liability (BIPD) insurance filing on file

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

MC496016

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

No active liability (BIPD) insurance filing on file

Common

None

Contract

None

Broker

None

Authorized for: Property

Liability (BIPD)

No active filing

$750K required

Cargo

Not on file

not required

Bond / surety

Not on file

not required

Authority history (1) ▾

09/01/2004MOTOR PROPERTY COMMON CARRIERDISMISSED

Insurance history1 insurer on record

Filing timeline (1) ▾

INTERSTATE INDEMNITY COMPANY$750KCancelled
BIPD/Primary · eff 07/08/2004 → 06/01/2005

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%

CSA performance breakdown

FMCSA · August 28, 2026

0 inspections · 0 violations (0 OOS) · —% of inspections had an OOS finding.

Inspections

Violations

OOS violations

Distinct codes

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.

Company profile

FMCSA census

AUTHORIZED FOR HIRE

Power units

on file (MCS-150)

Drivers

1 hold a CDL

Annual mileage

0.2M mi

reported 2003

Recordable crash rate

—

per million miles

How far they run · drivers by operating lane

Interstate · 100+ mi5 drivers
Interstate · <100 mi7 drivers

Company officer: SATINDER SINGH
Operation: Interstate
Registered since: 2004-07-14
Last MCS-150 update: 2006-02-27
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.

Connections

carrier graph

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

Connected carriers

Fleet-transfer links

Activity history

4 events

02/27/2006MCS-150 update filed
0.2M mi reported (2003)
06/01/2005Insurance cancelled — INTERSTATE INDEMNITY COMPANY
BIPD/Primary · policy TP 6120463
09/01/2004MOTOR PROPERTY COMMON CARRIER — DISMISSED
07/14/2004Registered with FMCSA
AUTHORIZED FOR HIRE

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

🚛

Operations

Classification

AUTHORIZED FOR HIRE

Area served

Interstate

★

FMCSA safety rating

Rating: Not rated
Type: —
Rated: —
Last review: —

📄

MCS-150 registration

Form date: 2006-02-27
Reported mileage: 173,800 mi (2003)

⚡

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