WELL · 42-029-34904 · DISTRICT 1

Sumerlin Jesse B. Jr. -B- #2

Plugged

Bexar County · Somerset field  · Vertical

Sumerlin Jesse B. JR. -B- #2 (API 42-029-34904) is a plugged well in Bexar County, plugged August 2, 2013, last operated by Seeker Oil Company II Inc..

The RRC has issued one drilling permit, issued January 17, 1984, permitted to 1,700 ft.

It was permitted by Seeker Oil Company, Incorporated and has since transferred to Seeker Oil Company II Inc. on the wellbore schedule.

Completion filings report one formation top, including Olmos.

Its lease has reported 1.4K barrels of oil and 7 mcf of gas since January 1993, last reporting in April 2015. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

Seeker Oil Company II Inc.

Permitted by Seeker Oil Company, Incorporated; the EWA schedule now lists a different operator.

San Antonio, TX · P-5 Y, filed Jun 3, 2016 · (210) 913-1014

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSeeker Oil Company II Inc.
Production reportsPaisano Production, Inc.through Jan 2011
Latest permitSeeker Oil Company, IncorporatedJan 17, 1984

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

1,700
total depth, ft
1
permits on file
Jan 17, 1984
last permit issued
May 18, 1984
completed
1.4K
cumulative oil, bbl
7
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Apr 2015

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
May 18, 1984
Shut in
—
Plugged
Aug 2, 2013

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 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Sumerlin, Jesse B. Jr. -B- O-1-10848SomersetSeeker Oil Company II, Inc.21.4K7Jan 1993 – Apr 2015

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. 1Seeker Oil Company, IncorporatedJan 1993 → Dec 2001
  2. 2Paisano Production, Inc.Jun 2004 → Jan 2011

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
226996-99DrillSeeker Oil Company, IncorporatedJan 11, 1984Jan 17, 1984—1,700

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-1-10848————

Formation tops

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

FormationMD ftSubsea
Olmos1,546-882

Perforations

Perforated and open-hole intervals.

FromToType
1,5461,566Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
4.51,6336.75215 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
00Mar 12, 1986May 25, 1984—
00Jan 25, 1986——
00Jun 12, 1984May 25, 1984—
00Jun 9, 1984May 25, 1984—

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