WELL · 42-421-31053 · DISTRICT 10

Barrick B #207

Plugged

Sherman County · Hartley Hugoton(krider Dolomite) field  · Vertical

Barrick B #207 (API 42-421-31053) is a plugged well in Sherman County, plugged May 28, 2020, last operated by Lasater & CO Inc..

The RRC has issued one drilling permit (amended once), issued October 23, 2007, permitted to 4,000 ft.

It was permitted by Samson Lone Star, LLC and has since transferred to Lasater & CO Inc. on the wellbore schedule.

Completion filings report 3 formation tops, including Tubb, Brown Dolo, Chase.

Operator of record

Lasater & Co Inc.

Permitted by Samson Lone Star, LLC; the EWA schedule now lists a different operator.

Spearman, TX · P-5 Y, filed Mar 4, 2026 · 13 permits on file · (806) 659-5033

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleLasater & Co Inc.
Production reportsLasater & Co, Inc.through Dec 2014
Latest permitSamson Lone Star, LLCOct 23, 2007

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

4,000
total depth, ft
2
permits on file
Oct 23, 2007
last permit issued
Apr 11, 2008
completed
0
cumulative oil, bbl
50.7K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Nov 2007 THROUGH May 2020

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Apr 11, 2008
Shut in
—
Plugged
May 28, 2020

Surface location

No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Barrick "B" G-14-237103Hartley Hugoton(krider Dolomite)Lasater & Co, Inc.1050.7KApr 2008 – May 2020
Barrick "B" G-14-234758WildcatSamson Lone Star, LLC100Nov 2007 – Apr 2008

No volumes reported on these leases in the last three years.

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Samson Lone Star, LLCApr 2008 → Jan 2014
  2. 2Lasater & Co, Inc.Dec 2014 → Dec 2014

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
648001-98DrillSamson Lone Star, LLCApr 7, 2008Oct 23, 2007Nov 13, 20074,000
648001-99DrillSamson Lone Star, LLCOct 18, 2007Oct 23, 2007Nov 13, 20074,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-14-234758————
—— G-14-237103————

Formation tops

As filed on W-2/G-1. Subsea from 3,788 ft elevation.Download CSV →

FormationMD ftSubsea
Tubb2,2681,520
Brown Dolo3,329459
Chase3,445343

Perforations

Perforated and open-hole intervals.

FromToType
3,3833,465Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62582912.25540 S
4.53,1727.875130 S

Completion filings

W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. About these reports →

SuffixFiledW-2 / G-1 dateLogs referenced
00Sep 24, 2008May 13, 2008—
00Jul 28, 2008——
00Jun 10, 2008Feb 20, 2008Yes
00May 6, 2008——

The source documents

Petrora holds the structured record. The scanned filings live at the RRC; these links open its search already filled in for this API.

Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward). then paste it into their search.

About this data

Permits from the RRC OGA049M master and daily daf420 files; wellbore and operator of record from the EWA schedule, weekly; completions, formation tops, casing, and perforations from the dbf900 wellbore file; production from PDQ lease reports, which lag two to three months; injection from UIC permits, H-10 reports, and TexNet daily volumes; earthquakes from the TexNet catalog.

New to these records? How to read a well page · API numbers · completion reports and tops · why production is by lease

Developers: this page as JSON is GET /v1/data/wells/42131053, documented in the API reference.