TEXAS · WELLS · SHACKELFORD COUNTY · CALDWELL LEASE · API 42-417-37497 · DISTRICT 6E

Caldwell #6

Y

Shackelford County · Shackelford County Regular field · Producing  · Vertical

Caldwell #6 (API 42-417-37497) is a well in Shackelford County operated by Oaktree Oil Company, completed April 7, 1992 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued April 5, 1991, permitted to 1,009 ft.

Completion filings report one formation top, including Cook Sand.

Its lease has reported 48.2K barrels of oil and 257 mcf of gas since January 1993, last reporting volume in April 2026. The lease carries 10 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 CompanyApr 5, 1991
1,009
total depth, ft
1
permits on file
Apr 5, 1991
last permit issued
Apr 7, 1992
completed
48.2K
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
Apr 7, 1992
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 10 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Caldwell O-8-20518Shackelford County RegularOaktree Oil Company1048.2K257Jan 1993 – Apr 2026

Oil, barrels lease total

Last 12 months 1,234 · prior 12 644(+92%)

0100200202420252026

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
386258-99DrillOaktree Oil CompanyApr 1, 1991Apr 5, 1991Apr 23, 19911,200

Completions

CompletedLeaseFieldOperatorStatusDepth
Apr 7, 1992Caldwell O-8-20518Shackelford County RegularOaktree Oil CompanyProducing1,009

Formation tops

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

FormationMD ftSubsea
Cook Sand958535

Perforations

Perforated and open-hole intervals.

FromToType
958962Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
4.59906.75150 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
00Jun 12, 1992May 7, 1992—
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/41737497, documented in the API reference.