WELL · 42-239-33556 · DISTRICT 2
Leach #1
Jackson County · Vertical
Leach #1 (API 42-239-33556) is a permitted well in Jackson County filed by Everest Resource Company; no completion report is on file yet.
The RRC has issued 2 drilling permits (amended once) between 2010 and 2016, permitted to 16,000 ft.
Completion filings report 3 formation tops, including Frio, Jackson, Yegua.
Operator of record
Corpus Chrsti, TX · P-5 Y, filed Dec 4, 2025 · 113 permits on file · (361) 688-1025
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | Everest Resource Companythrough Feb 2016 |
| Latest permit | Everest Resource CompanyApr 22, 2016 |
- 16,000
- total depth, ft
- 3
- permits on file
- Apr 22, 2016
- last permit issued
- —
- completed
- 0
- cumulative oil, bbl
- 36K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Mar 2011 THROUGH Jul 2026
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; this well is the only one on it.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Leach G-2-264530 | Big 12 (Yegua AY-3) | Everest Resource Company | 1 | 0 | 36K | Mar 2011 – Jul 2026 |
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.
- 1Alta Mesa Services, LPMar 2011 → Dec 2012
- 2Everest Resource CompanyJan 2013 → Feb 2016
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 815097-99 | Recompletion | Everest Resource Company | Apr 18, 2016 | Apr 22, 2016 | — | 5,700 |
| 704412-98 | Drill | Alta Mesa Services, LP | Jan 10, 2011 | Oct 29, 2010 | Dec 17, 2010 | 16,000 |
| 704412-99 | Drill | Alta Mesa Services, LP | Oct 27, 2010 | Oct 29, 2010 | Dec 17, 2010 | 14,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-2-264530 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 50 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 12,764 | 12,772 | Perforated |
| 12,783 | 12,787 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 13.375 | 2,600 | 17.5 | 2,070 S |
| 9.625 | 7,640 | 12.25 | 885 S |
| 4.5 | 13,970 | 6.75 | 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 | Aug 30, 2012 | Apr 13, 2011 | Yes |
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-239-33556 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-239-33556 → 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/23933556, documented in the API reference.