WELL · 42-363-31087 · DISTRICT 7

Bailey-Miller #1

Y

Palo Pinto County · Meeker (Congl. 5100) field · Producing  · Vertical

Bailey-Miller #1 (API 42-363-31087) is a well in Palo Pinto County operated by Upham Oil & Gas Company, completed October 17, 2011 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued September 8, 2011, permitted to 6,000 ft.

Completion filings report 2 formation tops, including Marble Falls, Barnett.

Its 2 leases have reported 1.98K barrels of oil and 140K mcf of gas since January 1993, last reporting in July 2026. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Upham Oil & Gas Company

Mineral Wells, TX · P-5 Y, filed Sep 4, 2025 · 141 permits on file · (940) 325-4491

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleUpham Oil & Gas Company
Production reportsUpham Oil & Gas Companythrough Dec 2025
Latest permitUpham Oil & Gas CompanySep 8, 2011
6,000
total depth, ft
1
permits on file
Sep 8, 2011
last permit issued
Oct 17, 2011
completed
1.98K
cumulative oil, bbl
140K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Oct 17, 2011
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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Bailey-Miller Unit G-8-69000Meeker (Conglomerate 4000)Upham Oil & Gas Company10117KJan 1993 – Jul 2026
Bailey-Miller O-8-30895Meeker (Congl. 5100)Upham Oil & Gas Company11.98K23.2KOct 2011 – Jul 2026

Gas, mcf lease total

Last 12 months 228 · prior 12 411(-45%)

050100150202420252026

Oil, barrels lease total

Last 12 months 42 · prior 12 62(-32%)

051015202420252026

Chain of custody

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

  1. 1Upham Oil & Gas CompanyJan 1993 → Dec 2025

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
723771-99RecompletionUpham Oil & Gas CompanySep 7, 2011Sep 8, 2011Sep 9, 20116,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-8-69000————
—— O-8-30895————

Formation tops

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

FormationMD ftSubsea
Marble Falls5,010-3,843
BarnettBARNETT SHALE5,400-4,233

Perforations

Perforated and open-hole intervals.

FromToType
5,3105,316Perforated
5,3285,346Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62556212.25525 S
4.54,3387.875250 S
2.8755,5853.875258 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
00Apr 10, 2013Mar 22, 2012—
00Mar 23, 2012Oct 24, 2011Yes
00Jan 12, 1984Nov 24, 1976—

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