TEXAS · WELLS · PANOLA COUNTY · WALDROP, G.T. GU LEASE · API 42-365-37213 · DISTRICT 06
Waldrop G.T. GU #3
Panola County · Beckville (Cotton Valley) field · Producing · Horizontal
Waldrop G.T. GU #3 (API 42-365-37213) is a horizontal well in Panola County operated by Tgnr East Texas II LLC, completed January 11, 2009 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit (amended once), issued September 2, 2008, permitted to 10,185 ft.
It was permitted by Goodrich Petroleum Company and has since transferred to Tgnr East Texas II LLC on the wellbore schedule.
Completion filings report 3 formation tops, including Travis Peak, Base B Lime, Knowles Lime.
Its lease has reported 3.42K barrels of oil and 1.83M mcf of gas since January 2009, last reporting volume in April 2026.
Operator of record
Permitted by Goodrich Petroleum Company; the EWA schedule now lists a different operator.
- Based in
- Houston, TX
- P-5 status
- Active (A)
- P-5 last filed
- Mar 18, 2026
- Permits on file
- 162
- Phone
- (346) 308-2250
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | TGNR East Texas II LLC |
| Production reports | TGNR East Texas II LLCthrough Apr 2026 |
| Latest permit | Goodrich Petroleum CompanySep 2, 2008 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 10,185
- total depth, ft
- 2
- permits on file
- Sep 2, 2008
- last permit issued
- Jan 11, 2009
- completed
- 3.42K
- cumulative oil, bbl
- 1.83M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 2009 THROUGH Apr 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Jan 11, 2009
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Active (A)
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 →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Waldrop, G.T. GU G-6-249189 | Beckville (Cotton Valley) | TGNR East Texas II LLC | 1 | 3.42K | 1.83M | Jan 2009 – Apr 2026 |
Gas, mcf lease total
Last 12 months 44,407 · prior 12 42,314(+5%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Goodrich Petroleum CompanyJan 2009 → Jun 2014
- 2Samson Lone Star, LLCJul 2014 → Sep 2017
- 3Rockcliff Energy Operating LLCOct 2017 → Nov 2023
- 4TGNR East Texas II LLCDec 2023 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 668782-98 | Drill | Goodrich Petroleum Company | Oct 16, 2008 | Sep 2, 2008 | Oct 20, 2008 | 13,500 |
| 668782-99 | Drill | Goodrich Petroleum Company | Aug 11, 2008 | Sep 2, 2008 | — | 13,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Jan 11, 2009 | Waldrop G.T. GU G-6-249189 | Beckville (Cotton Valley) | TGNR East Texas II LLC | Producing | 10,185 |
Formation tops
As filed on W-2/G-1. Subsea from 352 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Travis Peak | 6,870 | -6,518 |
| Base B Lime | 8,893 | -8,541 |
| Knowles Lime | 9,894 | -9,542 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 10,729 | 13,680 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 974 | 12.25 | 420 S |
| 7 | 10,177 | 8.75 | 776 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 →
| Suffix | RRC record date | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Aug 14, 2009 | May 20, 2009 | Yes |
| 00 | Jul 13, 2009 | — | — |
Well logs
1 log loaded from the RRC's log index, the latest received Jan 6, 2012. Density, Neutron, Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.
Open the RRC's log search for this well ↗| Logas described | Files | Intervalft, as filed | Datereceived | SizeMB |
|---|---|---|---|---|
| COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYSpans Knowles Lime | TIFF | 10,100 to 13,657 | Jan 6, 2012run Dec 20, 2008 | 2.25 |
"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.
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-365-37213 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-365-37213 → scanned completion filings
The logs loaded for this well are under Well logs, with the RRC's log search for it.
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/36537213, documented in the API reference.