TEXAS · WELLS · HEMPHILL COUNTY · DILLMAN LEASE · API 42-211-34266 · DISTRICT 08

Dillman #3

Shut in

Hemphill County · Red Deer Creek (Granite Wash) field · Temp Abandoned  · Directional

Fields on the latest permit · any of 4
Mendota, NW. (Granite Wash) · Mendota, NW. (Granite Wash, SW.) · Red Deer Creek (Cherokee) · Red Deer Creek (Granite Wash)
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.

Dillman #3 (API 42-211-34266) is a well in Hemphill County operated by Presidio Petroleum LLC, completed May 1, 2009 and listed as temp abandoned on the RRC schedule, shut in October 1, 2018.

The RRC has issued one drilling permit (amended once), issued June 3, 2008, permitted to 11,344 ft.

It was permitted by Unit Petroleum Company and has since transferred to Presidio Petroleum LLC on the wellbore schedule.

Completion filings report 5 formation tops, including Brown Dolomite, Douglas, Kansas City, Granite Wash.

Its lease has reported 8.51K barrels of oil and 559K mcf of gas since May 2009, with no volume in the three years through April 2026.

Operator of record

Presidio Petroleum LLC

Permitted by Unit Petroleum Company; the EWA schedule now lists a different operator.

Based in
Canadian, TX
P-5 status
Active (A)
P-5 last filed
May 1, 2026
Permits on file
13
Phone
(806) 217-4483

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePresidio Petroleum LLC
Production reportsPresidio Petroleum LLCthrough Sep 2018
Latest permitUnit Petroleum CompanyOct 31, 2008

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

11,344
total depth, ft
2
permits on file
Oct 31, 2008
last permit issued
May 1, 2009
completed
8.51K
cumulative oil, bbl
559K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · May 2009 THROUGH Sep 2018

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
May 1, 2009
Shut in
Oct 1, 2018
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
Dillman G-14-252281Red Deer Creek (Granite Wash)Presidio Petroleum LLC18.51K559KMay 2009 – Sep 2018

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. 1Unit Petroleum CompanyMay 2009 → Sep 2018

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
661963-98DrillUnit Petroleum CompanyOct 28, 2008Oct 31, 2008Dec 30, 200811,350
661963-99DrillUnit Petroleum CompanyMay 14, 2008Jun 3, 2008Dec 30, 200811,350

Completions

CompletedLeaseFieldOperatorStatusDepth
May 1, 2009Dillman G-14-252281Red Deer Creek (Granite Wash)Presidio Petroleum LLCTemp Abandoned · shut in Oct 1, 201811,344

Formation tops

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

FormationMD ftSubsea
Brown Dolomite4,052-1,469
Douglas7,143-4,560
Kansas City8,290-5,707
Granite Wash9,745-7,162
13 Finger11,460-8,877

Perforations

Perforated and open-hole intervals.

FromToType
9,95410,162Perforated
10,38710,558Perforated
10,66410,762Perforated
10,85410,934Perforated
11,01811,108Perforated
11,19011,260Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6253,22312.251,209 S
5.511,5948.75515 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
00Dec 16, 2009Aug 11, 2009Yes
00Nov 3, 2009——

Well logs

2 logs loaded from the RRC's log index, the latest received May 6, 2010. 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 POROSITYSpans Brown Dolomite, Douglas, Kansas City, Granite Wash, 13 FingerTIFF4,000 to 11,594May 6, 2010run Jan 29, 200912.8
RESISTIVITYSpans Brown Dolomite, Douglas, Kansas City, Granite Wash, 13 FingerTIFF3,222 to 11,594May 6, 2010run Jan 29, 200912.3

"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.

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