WELL · 42-295-31543 · DISTRICT 10

Miller Reba N. #3

Plugged

Lipscomb County · Lipscomb (Cleveland) field  · Vertical

Miller Reba N. #3 (API 42-295-31543) is a plugged well in Lipscomb County, plugged August 19, 2019, last operated by Xto Energy Inc..

The RRC has issued one drilling permit, issued July 24, 1984, permitted to 10,300 ft.

It was permitted by Exxon Corp. and has since transferred to Xto Energy Inc. on the wellbore schedule.

Completion filings report 7 formation tops, including Douglas, Tonkawa, Tonkowa, Cleveland.

Its lease has reported 5.2K barrels of oil and 34.4K mcf of gas since January 1993, last reporting in April 2020.

Operator of record

XTO Energy Inc.

Permitted by Exxon Corp.; the EWA schedule now lists a different operator.

Based in
Spring, TX
P-5 status
Active – Extension (X)
P-5 last filed
Apr 8, 2026
Permits on file
16,156
Phone
(346) 502-1572

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleXTO Energy Inc.
Production reportsExxon Mobil Corporationthrough Jan 2007
Latest permitExxon Corp.Jul 24, 1984

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

10,300
total depth, ft
1
permits on file
Jul 24, 1984
last permit issued
Mar 12, 1985
completed
5.2K
cumulative oil, bbl
34.4K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Apr 2020

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Mar 12, 1985
Shut in
—
Plugged
Aug 19, 2019

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, Reba N. O-14-6082Lipscomb (Cleveland)XTO Energy Inc.15.2K34.4KJan 1993 – Apr 2020

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. 1Exxon Corp.Jan 1993 → Mar 2000
  2. 2Exxon Mobil CorporationApr 2000 → Apr 2006

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
245915-99DrillExxon Corp.Jul 16, 1984Jul 24, 1984Dec 31, 198410,300

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-14-6082————

Formation tops

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

FormationMD ftSubsea
Douglas6,272-3,773
Tonkawa6,726-4,227
Tonkowa6,726-4,227
Cleveland7,796-5,297
Des Moines8,076-5,577
Atoka8,937-6,438
Chester10,148-7,649

Perforations

Perforated and open-hole intervals.

FromToType
7,8067,824Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6252,02412.251,010 S
5.510,2157.8751,000 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
00May 29, 1985May 13, 1985—
00May 28, 1985May 13, 1985—
00May 25, 1985——

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