TEXAS · WELLS · HARDIN COUNTY · API 42-199-31653 · DISTRICT 03

T. T. Co. Fee #752

Plugged

Hardin County · Sour Lake field  · Vertical

T. T. CO. Fee #752 (API 42-199-31653) is a plugged well in Hardin County, plugged May 26, 1988, last operated by Radco Operations L.P..

The RRC has issued one drilling permit, issued October 2, 1981, permitted to 2,100 ft.

It was permitted by Texaco Inc. and has since transferred to Radco Operations L.P. on the wellbore schedule.

Operator of record

Radco Operations L.P.

Permitted by Texaco Inc.; the EWA schedule now lists a different operator.

Based in
Sourlake, TX
P-5 status
Active (A)
P-5 last filed
Dec 22, 2025
Permits on file
50
Phone
(409) 287-1277

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleRadco Operations L.P.
Production reportsnone
Latest permitTexaco Inc.Oct 2, 1981

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

2,100
total depth, ft
1
permits on file
Oct 2, 1981
last permit issued
Feb 16, 1982
completed
—
cumulative oil, bbl
—
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS

On this pageInjection volumes

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Feb 16, 1982
Shut in
—
Plugged
May 26, 1988

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.

Wells nearby

Every well with a location on file around this well, in any state, nearest first.

Loading the map…

Open the full map →

Texas locations come from drilling permits, so most older Texas wells have none and are not listed.

Wells named T. T. Co. Fee

Radco Operations L.P.'s other wells filed under this lease name in Hardin County, newest permit first. The RRC gives a gas well its own lease number, so the name is what joins the wells of a unit.

Loading the lease's wells

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
135317-99DrillTexaco Inc.Oct 2, 1981Oct 2, 1981—2,100

Completions

CompletedLeaseFieldOperatorStatusDepth
Feb 16, 1982T. T. Co. Fee O-3-3929Sour LakeRadco Operations L.P.Plugged—

Perforations

Perforated and open-hole intervals.

FromToType
1,0651,090Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.7517415175 S
3.5992——
71,0609.875311 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, 1984Mar 11, 1982—

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 →

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

17.5K
bbl, last 12 reported months
138K
bbl, all reported
Jan 1985
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000045305H-1 InjectionPlugged Jul 8, 1988533523400–1,095

MONTHLY INJECTED, BBL · H-10 · LAST 16 REPORTED MONTHS

Last 12 months 17,502 · prior 12 120,693(-85%)

010K20K30K19841985

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