WELL · 42-331-34088 · DISTRICT 1
Wayne Brinkley #1
Milam County · Cherokee (Navarro) field · Shut IN · Vertical
Wayne Brinkley #1 (API 42-331-34088) is a well in Milam County operated by Cxl Energy LLC, completed February 16, 2012 and listed as shut in on the RRC schedule.
The RRC has issued one drilling permit, issued December 21, 2011, permitted to 4,000 ft.
It was permitted by Exploration Techniques Inc. and has since transferred to Cxl Energy LLC on the wellbore schedule.
Completion filings report 2 formation tops, including Poth, Navarro.
No lease production has been reported under this well’s leases.
Operator of record
Permitted by Exploration Techniques Inc.; the EWA schedule now lists a different operator.
Canada · P-5 Y, filed Nov 4, 2025 · (512) 595-6469
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | CXL Energy LLC |
| Production reports | none |
| Latest permit | Exploration Techniques Inc.Dec 21, 2011 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 4,000
- total depth, ft
- 1
- permits on file
- Dec 21, 2011
- last permit issued
- Feb 16, 2012
- completed
- 0
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jul 2012 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Feb 16, 2012
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Delinquent
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 |
|---|---|---|---|---|---|---|
| Wayne Brinkley O-1-17676 | Cherokee (Navarro) | CXL Energy LLC | 1 | 0 | 0 | Jul 2012 – Jul 2026 |
No volumes reported on these leases in the last three years.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 730213-99 | Drill | Exploration Techniques Inc. | Dec 16, 2011 | Dec 21, 2011 | Jan 18, 2012 | 4,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-1-17676 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 455 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Poth | 2,350 | -1,895 |
| Navarro | 2,965 | -2,510 |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 462 | 12.25 | 190 S |
| 5.5 | 3,400 | 7.875 | 627 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 | Jul 31, 2014 | Aug 17, 2012 | — |
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-331-34088 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-331-34088 → 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/33134088, documented in the API reference.