WELL · 42-169-33542 · DISTRICT 8

John B #1

Plugged

Garza County · Happy (Spraberry Lime) field  · Vertical

John B #1 (API 42-169-33542) is a plugged well in Garza County, plugged October 15, 2010, last operated by Cml Exploration LLC.

The RRC has issued one drilling permit, issued July 21, 1999, permitted to 5,100 ft.

It was permitted by Patterson Petroleum, Inc. and has since transferred to Cml Exploration LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Yates, San Andres, Spraberry.

Its lease has reported 39.8K barrels of oil and 13.9K mcf of gas since August 1999, last reporting in December 2010.

Operator of record

CML Exploration LLC

Permitted by Patterson Petroleum, Inc.; the EWA schedule now lists a different operator.

Austin, TX · P-5 Y, filed Jul 4, 2026 · 514 permits on file · (800) 460-6313

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCML Exploration LLC
Production reportsCML Exploration, LLCthrough Dec 2009
Latest permitPatterson Petroleum, Inc.Jul 21, 1999

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

5,100
total depth, ft
1
permits on file
Jul 21, 1999
last permit issued
Aug 6, 1999
completed
39.8K
cumulative oil, bbl
13.9K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Aug 1999 THROUGH Dec 2010

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Aug 6, 1999
Shut in
—
Plugged
Oct 15, 2010

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
John "B" O-11-68114Happy (Spraberry Lime)CML Exploration, LLC139.8K13.9KAug 1999 – Dec 2010

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. 1Patterson Petroleum, Inc.Aug 1999 → Feb 2000
  2. 2Patterson Petroleum LPMar 2000 → Jul 2007
  3. 3Patterson Petroleum LLCAug 2007 → Oct 2007
  4. 4CML Exploration, LLCNov 2007 → Dec 2009

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
485780-99DrillPatterson Petroleum, Inc.Jul 12, 1999Jul 21, 1999Jul 15, 19995,100

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-11-68114————

Formation tops

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

FormationMD ftSubsea
Yates1,2401,150
San Andres2,30882
Spraberry4,932-2,542

Perforations

Perforated and open-hole intervals.

FromToType
4,9324,942Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
12.7521917.5225 S
8.6253,61311800 S
5.55,1247.875400 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
00Sep 17, 1999Aug 13, 1999Yes
00Aug 20, 1999——

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