WELL · 42-105-33865 · DISTRICT 7

Adams #19

Y

Crockett County · Adams-Baggett Ranch (Canyon Sd.) field · Producing  · Vertical

Adams #19 (API 42-105-33865) is a well in Crockett County operated by Hubbard Operating, completed September 9, 1982 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued January 27, 1982, permitted to 5,500 ft.

It was permitted by Blue Ridge Oil & Gas Exp., Inc. and has since transferred to Hubbard Operating on the wellbore schedule.

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

Operator of record

Hubbard Operating

Permitted by Blue Ridge Oil & Gas Exp., Inc.; the EWA schedule now lists a different operator.

Ozona, TX · P-5 Y, filed Jun 4, 2026 · (325) 277-9721

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHubbard Operating
Production reportsHubbard Operatingthrough Apr 2025
Latest permitBlue Ridge Oil & Gas Exp., Inc.Jan 27, 1982

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
Jan 27, 1982
last permit issued
Sep 9, 1982
completed
0
cumulative oil, bbl
23K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Sep 9, 1982
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
Adams G-9-102300Adams-Baggett Ranch (Canyon Sd.)Hubbard Operating1023KJan 1993 – Jul 2026

Gas, mcf lease total

Last 12 months 0 · prior 12 352(-100%)

050100202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Blue Ridge Oil & Gas Exp., Inc.Mar 1993 → Jul 1994
  2. 2E R Operating CompanyAug 1994 → Nov 1994
  3. 3Gulf Coast E. & P., Inc.Jan 1995 → Oct 1995
  4. 4Araxas Exploration, Inc.Nov 1995 → Nov 1997
  5. 5Xplor Energy Operating Co.Dec 1997 → Jun 2001
  6. 6Patina Oil & Gas CorporationJul 2001 → Feb 2002
  7. 7Remuda Operating CompanyMar 2002 → Sep 2019
  8. 8Hubbard OperatingOct 2019 → Apr 2025

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
148714-99DrillBlue Ridge Oil & Gas Exp., Inc.Jan 27, 1982Jan 27, 1982Feb 1, 19825,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-9-102300————

Perforations

Perforated and open-hole intervals.

FromToType
4,5494,613Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,40711450 S
4.54,8447.875950 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 12, 1984Oct 28, 1982—

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) and the University Lands library. 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/10533865, documented in the API reference.