WELL · 42-215-33917 · DISTRICT 4

Miller Bob #1

Y

Hidalgo County · Monte Christo (Frio Cons.) field · Producing  · Vertical

Miller Bob #1 (API 42-215-33917) is a well in Hidalgo County operated by Atlas Operating LLC, completed May 19, 2009 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued February 4, 2009, permitted to 11,000 ft.

It was permitted by Chinn Exploration Company and has since transferred to Atlas Operating LLC 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

Atlas Operating LLC

Permitted by Chinn Exploration Company; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Oct 4, 2025 · 78 permits on file · (281) 893-9400

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleAtlas Operating LLC
Production reportsAtlas Operating LLCthrough Mar 2026
Latest permitChinn Exploration CompanyFeb 4, 2009

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

11,000
total depth, ft
1
permits on file
Feb 4, 2009
last permit issued
May 19, 2009
completed
0
cumulative oil, bbl
1.24M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · May 2009 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
May 19, 2009
Shut in
—
Plugged
—

Operator's P-5 on the schedule: H

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
Miller, Bob G-4-249085Monte Christo (Frio Cons.)Atlas Operating LLC101.24MMay 2009 – Jul 2026

Gas, mcf lease total

Last 12 months 18,307 · prior 12 21,278(-14%)

02K4K202420252026

Chain of custody

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

  1. 1Chinn Exploration CompanyNov 2009 → Nov 2015
  2. 2Trivium Operating, LLCDec 2015 → Jul 2016
  3. 3Sue-Ann Operating, L.C.Aug 2016 → Sep 2021
  4. 4Atlas Operating LLCOct 2021 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
677885-99DrillChinn Exploration CompanyJan 27, 2009Feb 4, 2009May 4, 200911,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-249085————

Formation tops

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

FormationMD ftSubsea
Frio7,690-7,523

Perforations

Perforated and open-hole intervals.

FromToType
8,4429,066Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6252,35712.25860 S
4.59,5157.875850 S
4.59,9157.875850 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 2, 2010Dec 21, 2009—
00Aug 13, 2009Jun 26, 2009Yes
00Jul 10, 2009——

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