WELL · 42-127-32929 · DISTRICT 1

Barker Bruce et AL #1

Plugged

Dimmit County · Pearsall (Austin Chalk) field  · Horizontal

Barker Bruce ET AL #1 (API 42-127-32929) is a plugged horizontal well in Dimmit County, plugged April 6, 2011, last operated by Dimmit Partners LLC.

The RRC has issued one drilling permit (amended once), issued September 6, 1990, permitted to 10,143 ft.

It was permitted by Tex-Hex Corp. and has since transferred to Dimmit Partners LLC on the wellbore schedule.

Completion filings report 4 formation tops, including Escondido, Olmos, Anacacho, Austin Chalk.

Its lease has reported 4.66K barrels of oil and 21 mcf of gas since January 1993, last reporting in July 2011.

Operator of record

Dimmit Partners LLC

Permitted by Tex-Hex Corp.; the EWA schedule now lists a different operator.

Abilene, TX · P-5 Y, filed Jul 8, 2011

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleDimmit Partners LLC
Production reportsDimmit Partners, LLCthrough Dec 2010
Latest permitTex-Hex Corp.Sep 6, 1990

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

10,143
total depth, ft
2
permits on file
Sep 6, 1990
last permit issued
Oct 30, 1990
completed
4.66K
cumulative oil, bbl
21
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2011

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Oct 30, 1990
Shut in
—
Plugged
Apr 6, 2011

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 lease this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Barker, Bruce et AL O-1-13157Pearsall (Austin Chalk)Dimmit Partners, LLC14.66K21Jan 1993 – Jul 2011

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. 1Southwest Oil & Land, Inc.Jan 1993 → Jan 1994
  2. 2McDay Energy Corp.Feb 1994 → Oct 2010
  3. 3Dimmit Partners, LLCNov 2010 → Dec 2010

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
377575-98DrillTex-Hex Corp.Sep 25, 1990Sep 6, 1990—10,143
377575-99DrillTex-Hex Corp.Sep 6, 1990Sep 6, 1990Sep 8, 199010,093

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-1-13157————

Formation tops

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

FormationMD ftSubsea
Escondido1,808-1,198
Olmos2,802-2,192
Anacacho4,775-4,165
Austin Chalk5,105-4,495

Perforations

Perforated and open-hole intervals.

FromToType
5,31010,143Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.751,56314.75915 S
75,3109.875600 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
00Aug 7, 1991Jun 3, 1991Yes
00Aug 6, 1991——

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/12732929, documented in the API reference.