WELL · 42-021-31042 · DISTRICT 3

Wilkinson B #3

Plugged

Bastrop County · Serbin (Taylor Sand) field  · Vertical

Wilkinson B #3 (API 42-021-31042) is a plugged well in Bastrop County, plugged April 9, 1998, last operated by Cap Operating Inc..

The RRC has issued one drilling permit, issued May 28, 1987, permitted to 5,500 ft.

It was permitted by Mid-Western Oil & Gas, Inc. and has since transferred to Cap Operating Inc. on the wellbore schedule.

Completion filings report 2 formation tops, including Wilcox, Navarro.

Its lease has reported 1.11K barrels of oil and 23.2K mcf of gas since January 1993, last reporting in July 2026.

Operator of record

Cap Operating Inc.

Permitted by Mid-Western Oil & Gas, Inc.; the EWA schedule now lists a different operator.

Borger, TX · P-5 Y, filed Jul 6, 2014

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCap Operating Inc.
Production reportsCap Operating Inc.through May 1997
Latest permitMid-Western Oil & Gas, Inc.May 28, 1987

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

5,500
total depth, ft
1
permits on file
May 28, 1987
last permit issued
Jun 28, 1987
completed
1.11K
cumulative oil, bbl
23.2K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jun 28, 1987
Shut in
—
Plugged
Apr 9, 1998

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
Wilkinson "B" O-3-19808Serbin (Taylor Sand)Cap Operating Inc.11.11K23.2KJan 1993 – Jul 2026

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. 1B.T.E. Oil Operator, Inc.Feb 1993 → Feb 1993
  2. 2TDK Energy CorporationMar 1993 → Feb 1994
  3. 3Penrod Oil Company of Texas, IncMar 1994 → Nov 1995
  4. 4Mobile Production Systems, Inc.Oct 1994 → Oct 1994
  5. 5Cap Operating Inc.Jan 1996 → May 1997

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
330796-99DrillMid-Western Oil & Gas, Inc.May 27, 1987May 28, 1987—5,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-19808————

Formation tops

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

FormationMD ftSubsea
Wilcox3,800-3,400
Navarro4,600-4,200

Perforations

Perforated and open-hole intervals.

FromToType
5,0665,072Perforated
5,0785,094Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62562012.25260 S
4.55,1867.875940 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
00Oct 14, 1987Sep 28, 1987Yes
00Oct 8, 1987——

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