WELL · 42-501-34451 · DISTRICT 8

Luna 336 #1

Y

Yoakum County · Brahaney field · Producing  · Vertical

Luna 336 #1 (API 42-501-34451) is a well in Yoakum County operated by Mcclure Oil Company Inc., completed January 16, 2001 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued August 17, 2000, permitted to 5,400 ft.

It was permitted by Brahaney Drilling CO. and has since transferred to Mcclure Oil Company Inc. on the wellbore schedule.

Completion filings report 3 formation tops, including Anahydrite, Yates, San Andres.

Its lease has reported 72K barrels of oil since January 2001, last reporting in July 2026.

Operator of record

McClure Oil Company Inc.

Permitted by Brahaney Drilling Co.; the EWA schedule now lists a different operator.

Midland, TX · P-5 Y, filed Aug 4, 2025 · 343 permits on file · (432) 683-2787

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleMcClure Oil Company Inc.
Production reportsMcClure Oil Company, Inc.through Apr 2026
Latest permitBrahaney Drilling Co.Aug 17, 2000

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

5,400
total depth, ft
1
permits on file
Aug 17, 2000
last permit issued
Jan 16, 2001
completed
72K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 2001 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jan 16, 2001
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
Luna 336 O-11-68269BrahaneyMcClure Oil Company, Inc.172K0Jan 2001 – Jul 2026

Oil, barrels lease total

Last 12 months 1,679 · prior 12 1,902(-12%)

0100200202420252026

Chain of custody

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

  1. 1Brahaney Drilling Co.Jan 2001 → Feb 2014
  2. 2Brahaney Drilling Company, Ltd.Mar 2014 → Jun 2015
  3. 3McClure Oil Company, Inc.Jul 2015 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
497383-99DrillBrahaney Drilling Co.Jul 19, 2000Aug 17, 2000Nov 22, 20005,400

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-11-68269————

Formation tops

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

FormationMD ftSubsea
Anahydrite1,9601,748
Yates3,270438
San Andres4,633-925

Perforations

Perforated and open-hole intervals.

FromToType
5,2335,309Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6252,40012.251,110 S
5.55,3437.875425 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 30, 2001Feb 13, 2001Yes
00Mar 5, 2001——

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