WELL · 42-237-32436 · DISTRICT 9
Kendrick Mercer #1
Jack County · Jack County Regular (Gas) field · Vertical
Kendrick Mercer #1 (API 42-237-32436) is a plugged well in Jack County, plugged January 7, 2012, last operated by Peba Oil & Gas Inc..
The RRC has issued one drilling permit, issued November 8, 1978, permitted to 5,500 ft.
It was permitted by Corpening Enterprises and has since transferred to Peba Oil & Gas Inc. on the wellbore schedule.
Operator of record
Permitted by Corpening Enterprises; the EWA schedule now lists a different operator.
- Based in
- Nocona, TX
- P-5 status
- Active – Extension (X)
- P-5 last filed
- Mar 5, 2026
- Permits on file
- 19
- Phone
- (940) 825-4825
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Peba Oil & Gas Inc. |
| Production reports | Bivins, Orville J. Jr.through Apr 1997 |
| Latest permit | Corpening EnterprisesNov 8, 1978 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 5,500
- total depth, ft
- 1
- permits on file
- Nov 8, 1978
- last permit issued
- Aug 15, 1979
- completed
- 0
- cumulative oil, bbl
- 5.58K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jan 2012
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Aug 15, 1979
- Shut in
- —
- Plugged
- Jan 7, 2012
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 |
|---|---|---|---|---|---|---|
| Kendrick, Mercer G-13-84363 | Jack County Regular (Gas) | Peba Oil & Gas, Inc. | 1 | 0 | 5.58K | Jan 1993 – Jan 2012 |
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.
- 1Bivins, Orville J. Jr.Jan 1993 → Apr 1997
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 36464-99 | Drill | Corpening Enterprises | Nov 8, 1978 | Nov 8, 1978 | Dec 6, 1978 | 5,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-13-84363 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 5,280 | 5,285 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 322 | 12.25 | 250 S |
| 2.875 | 5,340 | 7.625 | 300 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 | Jan 12, 1984 | Oct 9, 1979 | — |
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-237-32436 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-237-32436 → 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/23732436, documented in the API reference.