WELL · 42-161-33452 · DISTRICT 5

Melvin Waldrip Gas Unit II #3

N

Freestone County  · Vertical

Melvin Waldrip Gas Unit II #3 (API 42-161-33452) is a permitted well in Freestone County filed by Xto Energy Inc.; no completion report is on file yet.

The RRC has issued 3 drilling permits between 2006 and 2012, permitted to 14,800 ft.

Completion filings report 5 formation tops, including BMA, Pettit, Travis Peak, Cotton Valley.

Operator of record

XTO Energy Inc.

Spring, TX · P-5 Y, filed Feb 4, 2026 · 16,156 permits on file · (832) 625-1100

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsHilcorp Energy Companythrough Apr 2026
Latest permitXTO Energy Inc.Aug 22, 2012
14,800
total depth, ft
3
permits on file
Aug 22, 2012
last permit issued
—
completed
0
cumulative oil, bbl
2.78M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 2006 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 3 leases this well is completed on; they carry 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Waldrip, Melvin Gas Unit II G-5-222975Bear Grass (Cotton Valley Cons)Hilcorp Energy Company102.78MSep 2006 – Jul 2026
Waldrip, Melvin Gas Unit II G-5-266308Bear Grass (Travis Peak)Hilcorp Energy Company100Aug 2012 – Jul 2026
Waldrip, Melvin Gas Unit II G-5-266318Bear Grass (Pettit)Hilcorp Energy Company100Aug 2012 – Jul 2026

Gas, mcf lease total

Last 12 months 63,549 · prior 12 68,067(-7%)

05K10K202420252026

Chain of custody

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

  1. 1XTO Energy Inc.Sep 2006 → Dec 2023
  2. 2Hilcorp Energy CompanyJan 2024 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
745043-99RecompletionXTO Energy Inc.Jul 20, 2012Aug 22, 2012Jun 20, 201214,211
690440-99RecompletionXTO Energy Inc.Jan 28, 2010Feb 3, 2010—14,211
611837-99DrillXTO Energy Inc.Jan 3, 2006Jan 9, 2006Jul 5, 200614,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-5-222975————
—— G-5-266308————
—— G-5-266318————

Formation tops

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

FormationMD ftSubsea
BMA7,900-7,441
Pettit8,634-8,175
Travis Peak8,893-8,434
Cotton ValleyCOTTON VALLEY CONS.11,544-11,085
Cotton ValleyCOTTON VALLEY LIME13,825-13,366
CVL13,825-13,366

Perforations

Perforated and open-hole intervals.

FromToType
8,6658,790Perforated
9,0099,976Perforated
11,55814,048Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,41612.25475 S
712,4608.751,138 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
00Feb 27, 2013Aug 29, 2012—
00Apr 14, 2007Nov 16, 2006Yes
00Dec 8, 2006——

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