WELL · 42-465-30692 · DISTRICT 1

Bunger 30 #5

Y

Val Verde County · Pandale (Canyon Sand) field · Producing  · Vertical

Bunger 30 #5 (API 42-465-30692) is a well in Val Verde County operated by Dawson Energy LLC, completed June 22, 2003 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued April 16, 2003, permitted to 7,000 ft.

It was permitted by Concho Oil & Gas Corp. and has since transferred to Dawson Energy LLC on the wellbore schedule.

No lease production has been reported under this well’s leases.

Operator of record

Dawson Energy LLC

Permitted by Concho Oil & Gas Corp.; the EWA schedule now lists a different operator.

Midland, TX · P-5 Y, filed Dec 19, 2025 · (817) 456-2491

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleDawson Energy LLC
Production reportsDawson Energy, LLCthrough Apr 2026
Latest permitConcho Oil & Gas Corp.Apr 16, 2003

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

7,000
total depth, ft
1
permits on file
Apr 16, 2003
last permit issued
Jun 22, 2003
completed
0
cumulative oil, bbl
313K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 2003 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jun 22, 2003
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
Bunger "30" G-1-196012Pandale (Canyon Sand)Dawson Energy, LLC10313KJun 2003 – Jul 2026

Gas, mcf lease total

Last 12 months 1,197 · prior 12 1,702(-30%)

05001K202420252026

Chain of custody

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

  1. 1Concho Resources Inc.Jun 2003 → Mar 2004
  2. 2Chesapeake Operating, Inc.Apr 2004 → Mar 2010
  3. 3Three Rivers Operating Co LLCApr 2010 → Jul 2012
  4. 4COG Operating LLCAug 2012 → Dec 2012
  5. 5Legacy Reserves Operating LPMar 2013 → Nov 2018
  6. 6Bonfire Operating LLCDec 2018 → Oct 2024
  7. 7Wolfcamp Energy, LLCNov 2024 → Nov 2025
  8. 8Dawson Energy, LLCDec 2025 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
530533-99DrillConcho Oil & Gas Corp.Apr 10, 2003Apr 16, 2003May 30, 20037,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-1-196012————

Perforations

Perforated and open-hole intervals.

FromToType
4,0124,022Perforated
4,1024,112Perforated
4,1784,188Perforated
4,2844,298Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,53511360 S
4.54,7507.875530 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
00Aug 22, 2003Aug 5, 2003Yes
00Aug 14, 2003——

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