WELL · 42-329-30941 · DISTRICT 8

Golladay B. W. #7

Plugged

Midland County · Azalea (San Andres) field  · Vertical

Golladay B. W. #7 (API 42-329-30941) is a plugged well in Midland County, plugged May 27, 2005, last operated by New Height Energy LLC.

The RRC has issued one drilling permit, issued October 10, 1980, permitted to 4,280 ft.

It was permitted by Wood & Locker, Inc. and has since transferred to New Height Energy LLC on the wellbore schedule.

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

Operator of record

New Height Energy LLC

Permitted by Wood & Locker, Inc.; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Nov 4, 2025 · (432) 269-1562

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleNew Height Energy LLC
Production reportsNew Height Energy, LLCthrough Jun 2025
Latest permitWood & Locker, Inc.Oct 10, 1980

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

4,280
total depth, ft
1
permits on file
Oct 10, 1980
last permit issued
Mar 31, 1981
completed
51.6K
cumulative oil, bbl
21
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Mar 31, 1981
Shut in
—
Plugged
May 27, 2005

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 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Golladay,b. W. O-10-26458Azalea (San Andres)New Height Energy, LLC351.6K21Jan 1993 – Jul 2026

Oil, barrels lease total

Last 12 months 373 · prior 12 4,278(-91%)

0200400600202420252026

Chain of custody

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

  1. 1Westar Energy, Inc.Jan 1993 → Dec 2005
  2. 2Rex Energy Operating Corp.Jan 2006 → Feb 2009
  3. 3Adventure Exploration Ptrs, LLCMar 2009 → Aug 2011
  4. 4Bluestem Energy Holdings, LLCSep 2011 → Mar 2015
  5. 5PPC Operating Company LLCApr 2015 → Dec 2017
  6. 6Relentless Permian Operating LLCJan 2018 → Jan 2018
  7. 7New Height Energy, LLCFeb 2023 → Jun 2025

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
95433-99DrillWood & Locker, Inc.Oct 10, 1980Oct 10, 1980Mar 14, 19814,280

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-26458————

Perforations

Perforated and open-hole intervals.

FromToType
4,1244,144Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62529112.25225 S
2.8754,026——
4.54,1647.875500 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
00Jan 12, 1984May 18, 1981—

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