TEXAS · WELLS · LOVING COUNTY · BOYD 75-8 LEASE · API 42-301-31505 · DISTRICT 7B

Boyd 75-8 #1

Shut in

Loving County · Haley (Lwr. Wolfcamp-Penn Cons.) field · Temp Abandoned  · Vertical

Boyd 75-8 #1 (API 42-301-31505) is a well in Loving County operated by Pdeh LLC, completed February 4, 2010 and listed as temp abandoned on the RRC schedule, shut in April 1, 2022.

The RRC has issued one drilling permit, issued June 25, 2009, permitted to 17,295 ft.

It was permitted by Chesapeake Operating, Inc. and has since transferred to Pdeh LLC on the wellbore schedule.

Completion filings report 8 formation tops, including Delaware, Cherry Canyon, Brushy Canyon, Bone Creek.

Its lease has reported 3.47K barrels of oil and 3.56M mcf of gas since February 2010, last reporting volume in November 2023.

Operator of record

Pdeh 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
Dec 8, 2025
Permits on file
498
Phone
(432) 683-7443

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePdeh LLC
Production reportsPdeh LLCthrough Nov 2023
Latest permitChesapeake Operating, Inc.Jun 25, 2009

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

17,295
total depth, ft
1
permits on file
Jun 25, 2009
last permit issued
Feb 4, 2010
completed
3.47K
cumulative oil, bbl
3.56M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 2010 THROUGH Nov 2023

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Feb 4, 2010
Shut in
Apr 1, 2022
Plugged
—

Operator's P-5 on the schedule: Active (A)

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
Boyd 75-8 G-10-256245Haley (Lwr. Wolfcamp-Penn Cons.)Pdeh LLC13.47K3.56MFeb 2010 – Nov 2023

Gas, mcf lease total

Last 12 months 0 · prior 12 0

01K2K3K202420252026

Chain of custody

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

  1. 1Chesapeake Operating, Inc.Feb 2010 → Sep 2012
  2. 2Shell Western E&POct 2012 → Aug 2021
  3. 3Pdeh LLCSep 2021 → Nov 2023

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
682429-99DrillChesapeake Operating, Inc.Jun 23, 2009Jun 25, 2009Sep 12, 200920,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Feb 4, 2010Boyd 75-8 G-10-256245Haley (Lwr. Wolfcamp-Penn Cons.)Pdeh LLCTemp Abandoned · shut in Apr 1, 202217,295

Formation tops

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

FormationMD ftSubsea
Delaware5,202-2,091
Cherry Canyon6,476-3,365
Brushy Canyon7,570-4,459
Bone Creek9,046-5,935
Wolfcamp12,044-8,933
Strawn13,506-10,395
Atoka15,600-12,489
Morrow16,648-13,537

Perforations

Perforated and open-hole intervals.

FromToType
14,67014,903Perforated
14,67016,760Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3755,26217.52,560 S
9.62512,59112.252,400 S
5.517,2946.75590 S
13.375—17.51,550 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
00Sep 27, 2013Jan 21, 2013—
00Jul 26, 2010Feb 25, 2010Yes
00Jun 21, 2010——

Well logs

4 logs loaded from the RRC's log index, the latest received Dec 19, 2012. Density, Neutron, Resistivity, Sonic. 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
RESISTIVITYSpans Delaware, Cherry Canyon, Brushy Canyon, Bone Creek, WolfcampTIFF5,260 to 12,620Dec 19, 2012run Oct 17, 20091.74
ACOUSTIC POROSITYSpans Delaware, Cherry Canyon, Brushy Canyon, Bone Creek, WolfcampTIFF5,260 to 12,620Dec 18, 2012run Oct 17, 20094.76
NEUTRON/DENSITY POROSITYSpans Delaware, Cherry Canyon, Brushy Canyon, Bone Creek, WolfcampTIFF5,260 to 12,620Dec 18, 2012run Oct 17, 20095.50
RESISTIVITYSpans Delaware, Cherry Canyon, Brushy Canyon, Bone Creek, WolfcampTIFF5,260 to 12,620Dec 18, 2012run Oct 17, 20095.11

"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.

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