WELL · 42-135-06036 · DISTRICT 8
TXL B #5
Ector County · Vertical
Txl B #5 (API 42-135-06036) is a permitted well in Ector County filed by Chesapeake Operating, Inc.; no completion report is on file yet.
The RRC has issued one drilling permit, issued August 6, 2009, permitted to 8,000 ft.
Its lease has reported 71K barrels of oil and 325K mcf of gas since January 1993, last reporting in April 2018. The lease carries 9 wells, so these are lease totals, not this well alone.
Operator of record
Oklahoma City, OK · P-5 Y, filed Jul 4, 2026 · 13,061 permits on file · (405) 935-7500
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | Three Rivers Operating Co LLCthrough Apr 2010 |
| Latest permit | Chesapeake Operating, Inc.Aug 6, 2009 |
- 8,000
- total depth, ft
- 1
- permits on file
- Aug 6, 2009
- last permit issued
- —
- completed
- 71K
- cumulative oil, bbl
- 325K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Apr 2018
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- —
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 9 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| TXL -B- O-10-11858 | Slator (San Andres) | Aghorn Operating, Inc. | 9 | 71K | 325K | Jan 1993 – Apr 2018 |
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.
- 1Cross Timbers Operating CompanyJan 1993 → Nov 1999
- 2St. Johns Operating #1 L.P.Dec 1999 → Jul 2002
- 3Permian Resources, Inc.Aug 2002 → Apr 2004
- 4Chesapeake Operating, Inc.May 2004 → Mar 2010
- 5Three Rivers Operating Co LLCApr 2010 → Apr 2010
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 683818-99 | Recompletion | Chesapeake Operating, Inc. | Aug 4, 2009 | Aug 6, 2009 | — | 8,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-10-11858 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| — | 4,299 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 1,469 | 11 | 500 S |
| 8.625 | 1,469 | — | — |
| 4.5 | 4,342 | — | — |
| 4.5 | 4,375 | 7.875 | 150 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 | Feb 14, 2007 | Sep 15, 2006 | — |
| 00 | Jan 12, 1984 | Jan 8, 1960 | — |
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-135-06036 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-135-06036 → scanned completion filings
Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward) and the University Lands library. 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/13506036, documented in the API reference.