WELL · 42-199-33451 · DISTRICT 3

Choate Fee #69

Y

Hardin County · Batson New field · Producing  · Vertical

Choate Fee #69 (API 42-199-33451) is a well in Hardin County operated by Tandem Energy Corporation, completed April 21, 2014 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued September 27, 2013, permitted to 2,800 ft.

Completion filings report 8 formation tops, including Caprock, Fleming-Catahoula - Disposal, Frio, Jackson.

Its lease has reported 960K barrels of oil and 41.8K mcf of gas since January 1993, last reporting in July 2026. The lease carries 57 wells, so these are lease totals, not this well alone.

Operator of record

Tandem Energy Corporation

Houston, TX · P-5 Y, filed May 4, 2026 · 138 permits on file · (281) 351-5840

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleTandem Energy Corporation
Production reportsTandem Energy Corporationthrough Apr 2026
Latest permitTandem Energy CorporationSep 27, 2013
2,800
total depth, ft
1
permits on file
Sep 27, 2013
last permit issued
Apr 21, 2014
completed
960K
cumulative oil, bbl
41.8K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 21, 2014
Shut in
—
Plugged
—

Operator's P-5 on the schedule: X

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Choate Fee O-3-224Batson NewTandem Energy Corporation57960K41.8KJan 1993 – Jul 2026

Oil, barrels lease total

Last 12 months 17,017 · prior 12 23,326(-27%)

02K4K202420252026

Chain of custody

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

  1. 1Porter, James W.Jan 1993 → Sep 1993
  2. 2Porter, James W. SpecialOct 1993 → Jan 2001
  3. 3Arrowhead Operating Inc.Feb 2001 → Apr 2005
  4. 4Tandem Energy CorporationMay 2005 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
770166-99DrillTandem Energy CorporationSep 17, 2013Sep 27, 2013Apr 8, 20142,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-224————

Formation tops

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

FormationMD ftSubsea
CaprockCAPROCK - DISPOSAL——
Fleming-Catahoula - Disposal——
FrioFRIO - DISPOSAL——
JacksonJACKSON - DISPOSAL——
Miocene (undifferentiated)MIOCENE - DISPOSAL——
Oligocene - Disposal——
VicksburgVICKSBURG - DISPOSAL——
YeguaYEGUA - DISPOSAL——

Perforations

Perforated and open-hole intervals.

FromToType
2,2262,234Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62529212.25235 S
5.52,3488.75283 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. About these reports →

SuffixFiledW-2 / G-1 dateLogs referenced
00Nov 4, 2014May 8, 2014Yes

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 are in archives with no per-well link: the RRC's Neubus archive (2004 onward). then paste it into their search.

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