TEXAS · WELLS · HARRISON COUNTY · API 42-203-32160 · DISTRICT 06
Smith T.P. Estate C #2
Harrison County · Waskom (Travis Peak Upper) field · Producing · Vertical
Smith T.P. Estate C #2 (API 42-203-32160) is a well in Harrison County operated by Brookston Energy Inc., completed January 26, 2005 and listed as producing on the RRC schedule, shut in May 1, 2026.
The RRC has issued 2 drilling permits between 1992 and 1993, permitted to 9,650 ft.
It was permitted by Sonat Exploration Company -Tyler and has since transferred to Brookston Energy Inc. on the wellbore schedule.
Completion filings report 4 formation tops, including Travis Peak, Cotton Valley, Cv Lime, Cv Taylor.
No lease production has been reported under this well’s leases.
Operator of record
Permitted by Sonat Exploration Company -Tyler; the EWA schedule now lists a different operator.
- Based in
- Tyler, TX
- P-5 status
- Active (A)
- P-5 last filed
- Sep 5, 2025
- Permits on file
- 46
- Phone
- (903) 405-1901
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Brookston Energy Inc. |
| Production reports | Brookston Energy, Inc.through Apr 2026 |
| Latest permit | Sonat Exploration Company -TylerMar 24, 1993 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 9,650
- total depth, ft
- 2
- permits on file
- Mar 24, 1993
- last permit issued
- Jan 26, 2005
- completed
- 0
- cumulative oil, bbl
- 1.65M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Jan 26, 2005
- Shut in
- May 1, 2026
- Plugged
- —
Operator's P-5 on the schedule: Active – Extension (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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Smith, T.P. Estate 'C' G-6-144272 | Waskom (Cotton Valley) | Brookston Energy, Inc. | 1 | 0 | 1.17M | Jan 1993 – Jul 2026 |
| Smith, T.P. Estate 'C' G-6-145222 | Waskom, (Travis Peak, Upper) | Brookston Energy, Inc. | 1 | 0 | 480K | Mar 1993 – Jul 2026 |
Gas, mcf lease total
Last 12 months 22,510 · prior 12 31,365(-28%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Sonat Exploration Company -TylerJan 1993 → Jul 1995
- 2Comstock Oil & Gas, Inc.Aug 1995 → Oct 2004
- 3Comstock Oil & Gas, LPNov 2004 → Aug 2019
- 4Comstock Oil & Gas, LLCSep 2019 → Aug 2025
- 5Brookston Energy, Inc.Sep 2025 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 410148-99 | Other | Sonat Exploration Company -Tyler | Mar 24, 1993 | Mar 24, 1993 | Jan 19, 1993 | 9,800 |
| 403802-99 | Drill | Sonat Exploration Company -Tyler | Sep 23, 1992 | Sep 23, 1992 | Oct 18, 1992 | 9,800 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Jan 26, 2005 | Smith T.P. Estate C G-6-145222 | Waskom (Travis Peak Upper) | Brookston Energy Inc. | Producing · shut in May 1, 2006 | 9,650 |
| Jan 8, 1993 | Smith T.P. Estate C G-6-144272 | Waskom (Cotton Valley) | Brookston Energy Inc. | Producing · shut in May 1, 2026 | 9,650 |
Formation tops
As filed on W-2/G-1. Subsea from 333 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Travis Peak | 5,920 | -5,587 |
| Cotton Valley | 7,950 | -7,617 |
| Cotton ValleyCOTTON VALLEY LIME | 7,950 | -7,617 |
| Cotton ValleyCOTTON VALLEY LM | 7,950 | -7,617 |
| CV Lime | 7,950 | -7,617 |
| Cotton ValleyCOTTON VALLEY TAYLOR | 9,200 | -8,867 |
| CV Taylor | 9,200 | -8,867 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 5,952 | 5,960 | Perforated |
| 5,963 | 5,967 | Perforated |
| 6,051 | 6,056 | Perforated |
| 6,131 | 6,137 | Perforated |
| 6,290 | 6,296 | Perforated |
| 6,316 | 6,325 | Perforated |
| 6,369 | 6,379 | Perforated |
| 8,177 | 8,188 | Perforated |
| 9,287 | 9,492 | Perforated |
| 9,287 | 9,492 | Open hole |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 10.75 | 1,052 | 14.75 | 620 S |
| 2.875 | 6,502 | 9.875 | 1,580 S |
| 4.5 | 9,650 | 7.875 | 1,200 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 →
| Suffix | Filed | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Jun 28, 2005 | Apr 14, 2005 | — |
| 00 | Feb 3, 2005 | Nov 19, 2002 | — |
| 00 | Mar 29, 1994 | Jan 26, 1994 | — |
| 00 | Jul 16, 1993 | Apr 19, 1993 | Yes |
| 00 | May 27, 1993 | — | — |
| 00 | Mar 26, 1993 | Feb 11, 1993 | Yes |
| 00 | Mar 12, 1993 | — | — |
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.
- Wellbore filings for 42-203-32160 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-203-32160 → scanned completion filings
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/20332160, documented in the API reference.