TEXAS · WELLS · CROCKETT COUNTY · UNIVERSITY LAND 30-30A LEASE · API 42-105-36760 · DISTRICT 6E

University Land 30-30A #41

Plugged

Crockett County · Howards Creek (Canyon) field  · Vertical

University Land 30-30a #41 (API 42-105-36760) is a plugged well in Crockett County, plugged June 2, 2022, last operated by Djh Oil & Gas LLC.

The RRC has issued one drilling permit, issued January 5, 1995, permitted to 6,850 ft.

It was permitted by Harrison Interests, Ltd. and has since transferred to Djh Oil & Gas LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Spraberry, Cpx Marker, Canyon.

Operator of record

DJH Oil & Gas LLC

Permitted by Harrison Interests, Ltd.; the EWA schedule now lists a different operator.

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Aug 7, 2025
Permits on file
1
Phone
(713) 632-1300

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleDJH Oil & Gas LLC
Production reportsDJH Oil & Gas LLCthrough Oct 2021
Latest permitHarrison Interests, Ltd.Jan 5, 1995

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

6,850
total depth, ft
1
permits on file
Jan 5, 1995
last permit issued
Feb 15, 1995
completed
0
cumulative oil, bbl
271K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 1995 THROUGH Jun 2022

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Feb 15, 1995
Shut in
—
Plugged
Jun 2, 2022

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
University Land 30-30A G-9-153364Howards Creek (Canyon)DJH Oil & Gas LLC10271KFeb 1995 – Jun 2022

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. 1Harrison Interests, Ltd.Feb 1995 → Oct 2017
  2. 2DJH Oil & Gas LLCNov 2017 → Oct 2021

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
431337-99DrillHarrison Interests, Ltd.Dec 27, 1994Jan 5, 1995Jan 18, 19956,850

Completions

CompletedLeaseFieldOperatorStatusDepth
Feb 15, 1995University Land 30-30A G-9-153364Howards Creek (Canyon)DJH Oil & Gas LLCPlugged—

Formation tops

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

FormationMD ftSubsea
Spraberry4,113-1,744
CPX Marker5,982-3,613
CanyonUPPER CANYON6,273-3,904

Perforations

Perforated and open-hole intervals.

FromToType
6,4346,504Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,94011700 S
4.56,6667.875460 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 28, 1995Mar 13, 1995Yes

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.

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