WELL · 42-131-36957 · DISTRICT 4

Welder -A- #3

Plugged

Duval County · Squire field  · Vertical

Welder -A- #3 (API 42-131-36957) is a plugged well in Duval County, plugged November 3, 1996, last operated by D & B Energy Corporation.

The RRC has issued one drilling permit, issued November 17, 1986, permitted to 4,500 ft.

It was permitted by Price Drilling & Exploration CO. and has since transferred to D & B Energy Corporation on the wellbore schedule.

Completion filings report 4 formation tops, including Catahoula, Frio, Jackson, Yegua.

Its lease has reported 38.5K barrels of oil and 45.2K mcf of gas since January 1993, last reporting in July 2026. The lease carries 3 wells, so these are lease totals, not this well alone.

Operator of record

D & B Energy Corporation

Permitted by Price Drilling & Exploration Co.; the EWA schedule now lists a different operator.

San Antonio, TX · P-5 Y, filed Dec 5, 2008

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleD & B Energy Corporation
Production reportsAlacia Operating Companythrough Aug 2002
Latest permitPrice Drilling & Exploration Co.Nov 17, 1986

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

4,500
total depth, ft
1
permits on file
Nov 17, 1986
last permit issued
Dec 16, 1986
completed
38.5K
cumulative oil, bbl
45.2K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Dec 16, 1986
Shut in
—
Plugged
Nov 3, 1996

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; they carry 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Welder -A- O-4-11121SquireD & B Energy Corporation338.5K45.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. 1South Texas Operating CompanyJan 1993 → Nov 1997
  2. 2Alacia Operating CompanyDec 1997 → Aug 2002

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
323042-99DrillPrice Drilling & Exploration Co.Nov 13, 1986Nov 17, 1986—4,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-4-11121————

Formation tops

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

FormationMD ftSubsea
Catahoula650-130
Frio1,600-1,080
Jackson3,100-2,580
Yegua3,850-3,330

Perforations

Perforated and open-hole intervals.

FromToType
3,7903,795Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62545412.25210 S
5.53,9497.875205 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
00Jan 21, 1987Jan 5, 1987Yes
00Jan 13, 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/13136957, documented in the API reference.