TEXAS · WELLS · POLK COUNTY · GRANBURY, C. B. LEASE · API 42-373-00275 · DISTRICT 03

Granbury C. B. #16

Plugged

Polk County · Livingston field  · Vertical

Permitted field
Livingston (McElroy -a-, North)
The district's wildcat field is also on the permit.

Granbury C. B. #16 (API 42-373-00275) is a plugged well in Polk County, plugged August 24, 1993, last operated by HD Operating CO LLC.

The RRC has issued one drilling permit, issued April 22, 1982, permitted to 4,207 ft.

It was permitted by Exxon Corp. and has since transferred to HD Operating CO LLC on the wellbore schedule.

Its lease has reported 2.22K barrels of oil and 6.94K mcf of gas since January 1993, with no volume in the three years through April 2026. The lease carries 15 wells, so these are lease totals, not this well alone.

Operator of record

HD Operating Co LLC

Permitted by Exxon Corp.; the EWA schedule now lists a different operator.

Based in
Kilgore, TX
P-5 status
Active (A)
P-5 last filed
Nov 4, 2025
Phone
(903) 984-3443

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHD Operating Co LLC
Production reportsHD Operating Co, LLCthrough Oct 1994
Latest permitExxon Corp.Apr 22, 1982

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

4,207
total depth, ft
1
permits on file
Apr 22, 1982
last permit issued
Dec 29, 1982
completed
2.22K
cumulative oil, bbl
6.94K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Oct 1994

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Dec 29, 1982
Shut in
—
Plugged
Aug 24, 1993

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 15 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Granbury, C. B. O-3-2751LivingstonHD Operating Co, LLC152.22K6.94KJan 1993 – Oct 1994

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. 1Exxon Corp.Jan 1993 → Oct 1994

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
155776-99RecompletionExxon Corp.Apr 22, 1982Apr 22, 1982—4,207

Completions

CompletedLeaseFieldOperatorStatusDepth
Dec 29, 1982Granbury C. B. O-3-2751LivingstonHD Operating Co LLCPlugged—

Perforations

Perforated and open-hole intervals.

FromToType
3,6243,630Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
2.8753,498——

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, 1984Jan 18, 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/37300275, documented in the API reference.