WELL · 42-105-40498 · DISTRICT 7

Adams 166 #5

Y

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

Adams 166 #5 (API 42-105-40498) is a well in Crockett County operated by Hubbard Operating, completed March 24, 2008 and listed as temp abandoned on the RRC schedule.

The RRC has issued one drilling permit, issued December 8, 2007, permitted to 5,500 ft.

It was permitted by Remuda Operating Company and has since transferred to Hubbard Operating on the wellbore schedule.

Completion filings report 4 formation tops, including Clear Fork, U Wolfcamp, L Wolfcamp, Canyon.

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

Operator of record

Hubbard Operating

Permitted by Remuda Operating Company; 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 permitRemuda Operating CompanyDec 8, 2007

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
Dec 8, 2007
last permit issued
Mar 24, 2008
completed
0
cumulative oil, bbl
46.2K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 2008 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Mar 24, 2008
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 166 G-9-241474Adams-Baggett Ranch (Canyon Sd.)Hubbard Operating1046.2KMar 2008 – Jul 2026

Gas, mcf lease total

Last 12 months 0 · prior 12 1,154(-100%)

0100200300202420252026

Chain of custody

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

  1. 1Remuda Operating CompanyApr 2008 → Jan 2021
  2. 2Hubbard OperatingFeb 2021 → Apr 2025

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
650503-99DrillRemuda Operating CompanyNov 30, 2007Dec 8, 2007Feb 8, 20085,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-9-241474————

Formation tops

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

FormationMD ftSubsea
Clear ForkCLEARFORK1,748324
U Wolfcamp2,449-377
L Wolfcamp4,072-2,000
CanyonCANYON SAND4,991-2,919

Perforations

Perforated and open-hole intervals.

FromToType
4,9815,189Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
71,0239.875350 S
4.55,2156.125380 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
00Dec 4, 2008Aug 27, 2008Yes
00Oct 31, 2008——

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