TEXAS · WELLS · MARTIN COUNTY · MABEE Y LEASE · API 42-317-35870 · DISTRICT 7B

Mabee Y #3

Plugged

Martin County · Spraberry (Trend Area) field  · Vertical

Fields on the latest permit · any of 6
Hutex (Dean) · Lacaff (Dean) · Lacaff (Wolfcamp) · Spraberry (Trend Area) · Spraberry (Trend Area CL. Fk.) · Spraberry(trend Area Dean-Wlfcp)
Not one formation; the well must be completed in one of them, and no target formation is stated. The district's wildcat field is also on the permit.

Mabee Y #3 (API 42-317-35870) is a plugged well in Martin County, plugged June 29, 2018, last operated by Diamondback E&P LLC.

The RRC has issued one drilling permit, issued February 19, 2010, permitted to 11,000 ft.

It was permitted by Chesapeake Operating, Inc. and has since transferred to Diamondback E&P LLC on the wellbore schedule.

Completion filings report one formation top, including See Attached.

Its lease has reported 593K barrels of oil and 2.08M mcf of gas since December 2009, last reporting volume in August 2026. The lease carries 10 wells, so these are lease totals, not this well alone.

Operator of record

Diamondback E&P LLC

Permitted by Chesapeake Operating, Inc.; the EWA schedule now lists a different operator.

Based in
Midland, TX
P-5 status
Active (A)
P-5 last filed
May 4, 2026
Permits on file
5,254
Phone
(432) 221-7400

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleDiamondback E&P LLC
Production reportsDiamondback E&P LLCthrough Apr 2026
Latest permitChesapeake Operating, Inc.Feb 19, 2010

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

11,000
total depth, ft
1
permits on file
Feb 19, 2010
last permit issued
Sep 16, 2010
completed
593K
cumulative oil, bbl
2.08M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · DEC 2009 THROUGH AUG 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Sep 16, 2010
Shut in
—
Plugged
Jun 29, 2018

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.

Wells nearby

Every well with a location on file around this well, in any state, nearest first.

Loading the map…

Open the full map →

Texas locations come from drilling permits, so most older Texas wells have none and are not listed.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH AUG 2026

Texas reports oil by lease, not by well. These are the lease this well is completed on; they carry 10 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Mabee Y O-10-39868Spraberry (Trend Area)Diamondback E&P LLC10593K2.08MDec 2009 – Aug 2026

Oil, barrels lease total

Last 12 months 9,476 · prior 12 15,276(-38%)

01K2K202420252026

Gas, mcf lease total

Last 12 months 21,616 · prior 12 46,333(-53%)

05K10K202420252026

Wells named Mabee Y

Diamondback E&P LLC's other wells filed under this lease name in Martin County, newest permit first. The RRC gives a gas well its own lease number, so the name is what joins the wells of a unit.

Loading the lease's wells

Chain of custody

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

  1. 1Chesapeake Operating, Inc.Dec 2009 → Aug 2012
  2. 2Enervest Operating, L.L.C.Sep 2012 → Feb 2014
  3. 3QEP Energy CompanyMar 2014 → Sep 2021
  4. 4Diamondback E&P LLCOct 2021 → Aug 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
691565-99DrillChesapeake Operating, Inc.Feb 18, 2010Feb 19, 2010Jun 11, 201011,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Sep 16, 2010Mabee Y O-10-39868Spraberry (Trend Area)Diamondback E&P LLCPlugged—

Formation tops

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

FormationMD ftSubsea
See Attached——

Perforations

Perforated and open-hole intervals.

FromToType
7,80010,116Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,80011885 S
5.510,3007.8752,340 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Mar 23, 2011Oct 29, 2010Yes
00Mar 14, 2011——

Well logs

2 logs loaded from the RRC's log index, the latest received Aug 19, 2013. Density, Neutron, Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.

Open the RRC's log search for this well ↗
Logas describedFiles Intervalft, as filedDatereceivedSizeMB
NEUTRON/DENSITY POROSITYTIFF200 to 10,299Aug 19, 2013run Jul 3, 20103.64
RESISTIVITYTIFF6,600 to 10,299Aug 19, 2013run Jul 3, 20102.12

Find logs withinmiles of this well:List →Map →

Search the well logs loaded into Petrora →

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.

The logs loaded for this well are under Well logs, with the RRC's log search for it. The University Lands library has no per-well link: then paste it into its 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/31735870, documented in the API reference.