TEXAS · WELLS · BURLESON COUNTY · COOKS POINT LEASE · API 42-051-32493 · DISTRICT 03

Cooks Point #1

Plugged

Burleson County · Giddings (Austin Chalk-3) field  · Vertical

Cooks Point #1 (API 42-051-32493) is a plugged well in Burleson County, plugged April 16, 2015, last operated by Sheridan Production Company LLC.

The RRC has issued one drilling permit, issued July 13, 1983, permitted to 7,920 ft.

It was permitted by Sage Energy Company and has since transferred to Sheridan Production Company LLC on the wellbore schedule.

Its lease has reported 207 barrels of oil and 221 mcf of gas since January 1993, with no volume in the three years through April 2026.

Operator of record

Sheridan Production Company LLC

Permitted by Sage Energy Company; the EWA schedule now lists a different operator.

Based in
Houston, TX
P-5 status
Inactive (I)
P-5 last filed
Oct 23, 2020
Permits on file
1,009
Phone
(713) 548-1000

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSheridan Production Company LLC
Production reportsSheridan Production Company, LLCthrough Jan 1993
Latest permitSage Energy CompanyJul 13, 1983

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

7,920
total depth, ft
1
permits on file
Jul 13, 1983
last permit issued
Aug 25, 1983
completed
207
cumulative oil, bbl
221
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jan 1993

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Aug 25, 1983
Shut in
—
Plugged
Apr 16, 2015

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
Cooks Point O-3-16842Giddings (Austin Chalk-3)Sheridan Production Company, LLC1207221Jan 1993 – Jan 1993

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. 1Sage Energy CompanyJan 1993 → Jan 1993

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
201315-99DrillSage Energy CompanyJul 13, 1983Jul 13, 1983—7,920

Completions

CompletedLeaseFieldOperatorStatusDepth
Aug 25, 1983Cooks Point O-3-16842Giddings (Austin Chalk-3)Sheridan Production Company LLCPlugged—

Perforations

Perforated and open-hole intervals.

FromToType
7,1467,238Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6253,51012.251,300 S
2.3757,083——
5.57,3137.875400 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
00Jan 12, 1984Sep 1, 1983—

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