WELL · 42-495-05450 · DISTRICT 8

Wheeler, R. A. #2

N

Winkler County  · Vertical

Wheeler, R. A. #2 (API 42-495-05450) is a permitted well in Winkler County filed by M & J Energy, Inc.; no completion report is on file yet.

The RRC has issued 3 drilling permits between 1979 and 1999, permitted to 10,652 ft.

Completion filings report 4 formation tops, including Devonian, Silurain, McKee, Waddell.

Its lease has reported 13.5K barrels of oil and 50.1K mcf of gas since January 1993, last reporting in July 2026. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

M & J Energy, Inc.

Breckenridge, CO · P-5 Y, filed May 3, 2013 · 17 permits on file · (970) 409-7913

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsBeach Oil & Gas, Inc.through Nov 2015
Latest permitM & J Energy, Inc.Aug 9, 1999
10,652
total depth, ft
3
permits on file
Aug 9, 1999
last permit issued
—
completed
13.5K
cumulative oil, bbl
50.1K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
—

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; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Wheeler, R. A. O-10-28204Wheeler (Wolfcamp)Apv McCamey LLC213.5K50.1KJan 1993 – Jul 2026

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. 1M & J Energy, Inc.Feb 1996 → Apr 2008
  2. 2Beach Oil & Gas, Inc.May 2008 → Nov 2015

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
485644-99RecompletionM & J Energy, Inc.Jul 2, 1999Aug 9, 1999—10,652
192597-99RecompletionSuperior Oil Company, TheApr 12, 1983Apr 12, 1983—10,562
54378-99RecompletionSuperior Oil Company, TheJul 25, 1979Jul 25, 1979—10,652

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-28204————

Formation tops

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

FormationMD ftSubsea
Devonian8,390-5,269
Silurain9,260-6,139
McKee10,085-6,964
Waddell10,395-7,274

Perforations

Perforated and open-hole intervals.

FromToType
7,7407,830Perforated
7,7408,555Perforated
8,3868,600Perforated
8,5008,555Perforated
9,2649,324Perforated
9,2909,300Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.375259——
9.6253,69912.253,500 S
9.6253,699——
2.8758,564——
2.8758,603——
710,642—200 S
710,6428.75425 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 14, 2000Nov 10, 1999—
00Jan 12, 1984Jun 24, 1983—
00Jan 12, 1984Sep 21, 1979—
00Jan 12, 1984Jun 29, 1961—

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