WELL · 42-373-31181 · DISTRICT 3

Mills Bennett #2

Plugged

Polk County · Padgett (Yegua Y-3) field  · Vertical

Mills Bennett #2 (API 42-373-31181) is a plugged well in Polk County, plugged September 7, 2024, last operated by Davis Southern Operating CO LLC.

The RRC has issued one drilling permit (amended once), issued November 2, 2010, permitted to 6,000 ft.

Completion filings report one formation top, including Yegua.

Its lease has reported 16.3K barrels of oil and 15.4K mcf of gas since January 2011, last reporting in January 2025.

Operator of record

Davis Southern Operating Co LLC

Houston, TX · P-5 Y, filed Jan 4, 2026 · 127 permits on file · (713) 299-0787

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleDavis Southern Operating Co LLC
Production reportsDavis Southern Operating Co LLCthrough Sep 2015
Latest permitDavis Southern Operating Co LLCNov 2, 2010
6,000
total depth, ft
2
permits on file
Nov 2, 2010
last permit issued
Apr 30, 2019
completed
16.3K
cumulative oil, bbl
15.4K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 2011 THROUGH Jan 2025

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Apr 30, 2019
Shut in
—
Plugged
Sep 7, 2024

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
Mills Bennett O-3-25816Padgett (Yegua Y-3)Davis Southern Operating Co LLC116.3K15.4KJan 2011 – Jan 2025

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. 1Davis Southern Operating Co LLCApr 2011 → Sep 2015

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
704234-98DrillDavis Southern Operating Co LLCNov 18, 2010Nov 2, 2010Dec 11, 20106,000
704234-99DrillDavis Southern Operating Co LLCOct 25, 2010Nov 2, 2010Dec 10, 20106,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-25816————

Formation tops

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

FormationMD ftSubsea
YeguaYEGUA Y-35,079-4,896

Perforations

Perforated and open-hole intervals.

FromToType
5,0795,083Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,85011734 S
5.55,4667.875900 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 25, 2020Jan 23, 2020—
00Jun 28, 2012Apr 26, 2011Yes

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.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

0
bbl, last 12 reported months
0
bbl, all reported
Feb 2025
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000117685H-1 InjectionPlugged Jan 13, 20252,0002,5005,000–5,100

MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS

Last 12 months 0 · prior 12 0

0120242025

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