TEXAS · WELLS · HOWARD COUNTY · GASKINS 43 LEASE · API 42-227-37519 · DISTRICT 7B

Gaskins 43 #1

Plugged

Howard County · Spraberry (Trend Area) field  · Vertical

Gaskins 43 #1 (API 42-227-37519) is a plugged well in Howard County, plugged July 11, 2013, last operated by Diamondback E&P LLC.

The RRC has issued one drilling permit, issued June 24, 2013, permitted to 11,500 ft.

It was permitted by Energen Resources Corporation and has since transferred to Diamondback E&P LLC on the wellbore schedule.

Its lease has reported 18.8K barrels of oil and 18.1K mcf of gas since July 2013, with no volume in the three years through April 2026. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

Diamondback E&P LLC

Permitted by Energen Resources Corporation; the EWA schedule now lists a different operator.

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

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleDiamondback E&P LLC
Production reportsDiamondback E&P LLCthrough Jul 2019
Latest permitEnergen Resources CorporationJun 24, 2013

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

11,500
total depth, ft
1
permits on file
Jun 24, 2013
last permit issued
Jul 11, 2013
completed
18.8K
cumulative oil, bbl
18.1K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Nov 2013 THROUGH Jul 2019

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jul 11, 2013
Shut in
—
Plugged
Jul 11, 2013

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Gaskins 43 O-10-44231Spraberry (Trend Area)Diamondback E&P LLC218.8K18.1KJul 2013 – Jul 2019

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. 1Energen Resources CorporationNov 2013 → Jan 2019
  2. 2Diamondback E&P LLCFeb 2019 → Feb 2019

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
765052-99DrillEnergen Resources CorporationJun 19, 2013Jun 24, 2013Jun 30, 201311,500

Completions

CompletedLeaseFieldOperatorStatusDepth
Jul 11, 2013Gaskins 43 O-10-44231Spraberry (Trend Area)Diamondback E&P LLCPlugged—

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37543817.5500 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 14, 2014Sep 16, 2013Yes

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 filed since 2004 open from the RRC's log search for this well; none are loaded here for it.

Find logs withinmiles of this well:List →Map →

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