WELL · 42-317-43978 · DISTRICT 8

Vineyard 23-8 B #1LS

Y

Martin County · Spraberry (Trend Area) field · Producing  · Horizontal

Vineyard 23-8 B #1LS (API 42-317-43978) is a horizontal well in Martin County operated by Diamondback E&P LLC, completed July 24, 2022 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued November 23, 2021, permitted to 9,440 ft.

Completion filings report 10 formation tops, including Yates, Queen, Grayburg, San Andres.

Its lease has reported 200K barrels of oil and 228K mcf of gas since July 2022, last reporting in July 2026.

Operator of record

Diamondback E&P LLC

Midland, TX · P-5 Y, filed Mar 4, 2026 · 5,237 permits on file · (855) 247-5920

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleDiamondback E&P LLC
Production reportsDiamondback E&P LLCthrough Apr 2026
Latest permitDiamondback E&P LLCNov 23, 2021
9,440
total depth, ft
1
permits on file
Nov 23, 2021
last permit issued
Jul 24, 2022
completed
200K
cumulative oil, bbl
228K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 2022 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 24, 2022
Shut in
—
Plugged
—

Operator's P-5 on the schedule: X

Surface location

32.487489, -102.155603

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Martin County.

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
Vineyard 23-8 B O-10-58572Spraberry (Trend Area)Diamondback E&P LLC1200K228KJul 2022 – Jul 2026

Oil, barrels lease total

Last 12 months 28,324 · prior 12 32,705(-13%)

02K4K6K202420252026

Gas, mcf lease total

Last 12 months 54,745 · prior 12 27,322(+100%)

05K10K202420252026

Chain of custody

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

  1. 1Diamondback E&P LLCJul 2022 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
874723-99DrillDiamondback E&P LLCNov 22, 2021Nov 23, 2021Mar 12, 20229,440

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-58572————

Formation tops

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

FormationMD ftSubsea
Yates2,86019
Queen3,457-578
Grayburg3,892-1,013
San AndresSAN ANDRES - ACTIVE CO2 FLOOD; H4,311-1,432
Clear ForkCLEARFORK6,250-3,371
Spraberry8,135-5,256
Cisco——
Dean——
Santa Rosa——
Wolfcamp——

Perforations

Perforated and open-hole intervals.

FromToType
10,50821,496Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
11.751,51814.75960 S
8.6256,423111,450 S
5.521,5647.8752,295 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 21, 2023Jan 10, 2023Yes

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) and the University Lands library. then paste it into their search.

Nearby wells and their tops

NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM

Draw a cross-section

This well's tops beside its 5 nearest neighbours, subsea-aligned so they line up regardless of surface terrain.

Open the cross-section →

Vineyard 23-8 A42-317-43974

0.0 KM · Diamondback E&P LLC · Section with this well →

Yates2,85722
Queen3,462-583
Grayburg3,899-1,020
San Andres4,311-1,432
Clear Fork6,244-3,365
Spraberry8,131-5,252
Dean—
Santa Rosa—

10 TOPS · FIRST 8

Vineyard 23-8 C42-317-43979

0.0 KM · Diamondback E&P LLC · Section with this well →

Yates2,86217
Queen3,462-583
Grayburg3,879-1,000
San Andres4,314-1,435
Spraberry8,134-5,255
Dean9,332-6,453
Wolfcamp9,550-6,671
Cisco—

10 TOPS · FIRST 8

Vineyard 23-8 E42-317-43982

0.0 KM · Diamondback E&P LLC · Section with this well →

Yates2,85425
Queen3,454-575
Grayburg3,900-1,021
San Andres4,306-1,427
Spraberry8,129-5,250
Pennsylvanian—
Wolfcamp—
Santa Rosa—

10 TOPS · FIRST 8

Vineyard 23-8 F42-317-43983

0.0 KM · Diamondback E&P LLC · Section with this well →

Yates2,85029
Queen3,452-573
Grayburg3,884-1,005
San Andres4,310-1,431
Spraberry8,113-5,234
Dean9,358-6,479
Wolfcamp9,530-6,651
Santa Rosa—

16 TOPS · FIRST 8

Vineyard 23-8 D42-317-43980

0.0 KM · Diamondback E&P LLC · Section with this well →

Yates2,85524
Queen3,451-572
Grayburg3,880-1,001
San Andres4,301-1,422
Clear Fork6,231-3,352
Spraberry8,114-5,235
Santa Rosa—
Wolfcamp—

10 TOPS · FIRST 8

Vineyard 24-7 B42-317-45379

0.2 KM · Diamondback E&P LLC · Section with this well →

Santa Rosa1,2021,678
Yates2,86515
Queen3,467-587
Grayburg3,917-1,037
San Andres4,339-1,459
Spraberry8,126-5,246
Dean9,380-6,500
Wolfcamp9,546-6,666

10 TOPS · FIRST 8

Vineyard 24-7 A42-317-45378

0.2 KM · Diamondback E&P LLC · Section with this well →

Santa Rosa1,2021,678
Yates2,86515
Queen3,467-587
Grayburg3,917-1,037
San Andres4,339-1,459
Spraberry8,153-5,273
Wolfcamp—
Pennsylvanian—

10 TOPS · FIRST 8

Vineyard 24-7 C42-317-45380

0.2 KM · Diamondback E&P LLC · Section with this well →

Santa Rosa1,2021,678
Yates2,86515
Queen3,467-587
Grayburg3,917-1,037
San Andres4,339-1,459
Clear Fork6,292-3,412
Spraberry8,150-5,270
Dean9,410-6,530

10 TOPS · FIRST 8

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