WELL · 42-485-34381 · DISTRICT 9
Kempner #2
Wichita County · Wichita County Regular field · Vertical
Kempner #2 (API 42-485-34381) is a plugged well in Wichita County, plugged May 16, 2003, last operated by Dutton Bill.
The RRC has issued one drilling permit, issued July 11, 1977, permitted to 100 ft.
It was permitted by Potter, W. R. JR. and has since transferred to Dutton Bill on the wellbore schedule.
Its lease has reported 836 barrels of oil and 25 mcf of gas since January 1993, last reporting in July 2026. The lease carries 7 wells, so these are lease totals, not this well alone.
Operator of record
Permitted by Potter, W. R. Jr.; the EWA schedule now lists a different operator.
Iowa Park, TX · P-5 Y, filed Aug 4, 2006
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Dutton Bill |
| Production reports | SQ Oilthrough Sep 1999 |
| Latest permit | Potter, W. R. Jr.Jul 11, 1977 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 100
- total depth, ft
- 1
- permits on file
- Jul 11, 1977
- last permit issued
- Jul 12, 1977
- completed
- 836
- cumulative oil, bbl
- 25
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Jul 12, 1977
- Shut in
- —
- Plugged
- May 16, 2003
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 7 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Kempner O-13-18555 | Wichita County Regular | Dutton, Bill | 7 | 836 | 25 | Jan 1993 – 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.
- 1DS OilJan 1993 → Jan 1997
- 2Menasco, J.Jul 1994 → Aug 1994
- 3SQ OilSep 1999 → Sep 1999
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 2645-99 | Drill | Potter, W. R. Jr. | Jul 11, 1977 | Jul 11, 1977 | — | 100 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-13-18555 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| — | 80 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 4.5 | 100 | 6.75 | 20 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 | Sep 29, 1977 | — |
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-485-34381 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-485-34381 → 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/48534381, documented in the API reference.