WELL · 42-481-34843 · DISTRICT 3

Putnam J. B. #2A

Y

Wharton County · Louise N. (4130) field · Temp Abandoned  · Vertical

Putnam J. B. #2A (API 42-481-34843) is a well in Wharton County operated by Welderxp Ltd., completed May 10, 2006 and listed as temp abandoned on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued April 12, 2006, permitted to 5,000 ft.

It was permitted by Cimarron Engineering Corp. and has since transferred to Welderxp Ltd. on the wellbore schedule.

Completion filings report one formation top, including Frio.

No lease production has been reported under this well’s leases.

Operator of record

Welderxp Ltd.

Permitted by Cimarron Engineering Corp.; the EWA schedule now lists a different operator.

San Antonio, TX · P-5 Y, filed Nov 4, 2025 · 14 permits on file · (210) 601-1249

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleWelderxp Ltd.
Production reportsWelder Exploration & Prod., Inc.through Oct 2013
Latest permitCimarron Engineering Corp.Apr 12, 2006

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

5,000
total depth, ft
2
permits on file
Apr 12, 2006
last permit issued
May 10, 2006
completed
0
cumulative oil, bbl
305K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · May 2006 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
May 10, 2006
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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
Putnam, J. B. G-3-219130Louise, N. (4130)Welderxp Ltd.10305KMay 2006 – 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. 1Cimarron Engineering Corp.May 2006 → May 2011
  2. 2Choice Exploration, Inc.Jun 2011 → Sep 2012
  3. 3Welder Exploration & Prod., Inc.Nov 2012 → Oct 2013

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
617397-98DrillCimarron Engineering Corp.Aug 23, 2006Apr 12, 2006Apr 17, 20065,000
617397-99DrillCimarron Engineering Corp.Apr 11, 2006Apr 12, 2006Apr 17, 20065,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-3-219130————

Formation tops

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

FormationMD ftSubsea
Frio3,850-3,737

Perforations

Perforated and open-hole intervals.

FromToType
4,1324,139Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,05012.25490 S
4.54,3167.875580 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
00Feb 10, 2007Aug 23, 2006Yes
00Sep 19, 2006——

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