TEXAS · WELLS · SHACKELFORD COUNTY · DE LAFOSSE LEASE · API 42-417-37493 · DISTRICT 6E

De Lafosse #11

Y

Shackelford County · Shackelford County Regular field · Producing  · Vertical

De Lafosse #11 (API 42-417-37493) is a well in Shackelford County operated by Oaktree Oil Company, completed February 4, 1994 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued March 26, 1991, permitted to 820 ft.

Completion filings report one formation top, including Hope Sand.

Its lease has reported 8.28K barrels of oil and 257 mcf of gas since January 1993, last reporting volume in April 2026. The lease carries 8 wells, so these are lease totals, not this well alone.

Operator of record

Oaktree Oil Company

Based in
Albany, TX
P-5 status
Active (A)
P-5 last filed
Mar 2, 2026
Permits on file
62
Phone
(325) 762-5386

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleOaktree Oil Company
Production reportsOaktree Oil Companythrough Apr 2026
Latest permitOaktree Oil CompanyMar 26, 1991
820
total depth, ft
1
permits on file
Mar 26, 1991
last permit issued
Feb 4, 1994
completed
8.28K
cumulative oil, bbl
257
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Feb 4, 1994
Shut in
—
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; they carry 8 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
De Lafosse O-8-12070Shackelford County RegularOaktree Oil Company88.28K257Jan 1993 – Apr 2026

Oil, barrels lease total

Last 12 months 291 · prior 12 300(-3%)

02040202420252026

Chain of custody

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

  1. 1Oaktree Oil CompanyJan 1993 → Apr 2026
  2. 2Petree Operating, Inc.Jan 1995 → Feb 1996

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
385971-99DrillOaktree Oil CompanyMar 21, 1991Mar 26, 1991Apr 8, 19911,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Feb 4, 1994De Lafosse O-8-12070Shackelford County RegularOaktree Oil CompanyProducing820

Formation tops

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

FormationMD ftSubsea
Hope Sand380824

Perforations

Perforated and open-hole intervals.

FromToType
380384Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
4.54316.7565 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
00May 17, 1994Mar 31, 1994—
00May 8, 1992Mar 18, 1992Yes
00Apr 1, 1992——

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