CSA
UnknownUSDOT 325773· CARRIER· EIN 74-1649839
⬇ PDF report

FEATHER CREST FARMS INC

14374 E HWY 21, BRYAN, TX, 77808(979) 703-8510david.flora@mpseggs.comBRIAN BARRETT
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%

90-day safety improvement plan

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

No roadside inspections in the last 90 days — nothing to work on right now.

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).

0
Inspections
0
Violations
0
Out-of-service
0
CSA points
2
Crashes
1
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.

Company profile

FMCSA census

PRIVATE PROPERTY

Power units
9
on file (MCS-150)
Drivers
9
7 hold a CDL
Annual mileage
0.4M mi
reported 2019
Recordable crash rate
—
per million miles
How far they run · drivers by operating lane
  • Intrastate · 100+ mi6 drivers
  • Intrastate · <100 mi3 drivers
Company officer
BRIAN BARRETT
Operation
Intrastate (Non-Hazmat)
D-U-N-S
39250766
Registered since
1988-08-24
Last MCS-150 update
2020-04-13
Census status
I

Fleet: 9 trucks · 6 owned tractors · 7 owned trailers.

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 phone numbers or officers with 8 other carriers — review the connections below as part of your vetting.

8
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
7
Strong links
Strong· 7
1
ACES & EIGHTS TRUCKING INC
USDOT 1543200Inactive· CORPUS CHRISTI, TX
Strong
Officer
2
BARRETT TRUCKING COMPANY INC
USDOT 86362Active· BURLINGTON, VT
Strong
Officer
3
BLUE COLLAR BUILDERS
USDOT 2127553Active· MONA, UT
Strong
Officer
4
BSBT LLC
USDOT 1845624Active· CUBA, MO
Strong
Officer
5
DIXIE WRECKER SERVICE INC
USDOT 1416235Active· LINCOLNTON, NC
Strong
Officer
6
SCALES TRANSPORT LLC
USDOT 3244084Inactive· DETROIT, MI
Strong
Officer
7
SOUTHERN STYLE LANDSCAPING
USDOT 1936647Inactive· WOODSTOCK, GA
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. 04/13/2020MCS-150 update filed

    0.4M mi reported (2019)

  2. 08/24/1988Registered with FMCSA

    PRIVATE PROPERTY

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

🚛

Operations

Classification

  • PRIVATE PROPERTY

Area served

  • Intrastate (Non-Hazmat)
★

FMCSA safety rating

Rating
Not rated
Type
—
Rated
—
Last review
—
📄

MCS-150 registration

Form date
2020-04-13
Reported mileage
385,000 mi (2019)
⚡

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