WELL · 42-187-31737 · DISTRICT 1
Kerschner Harrison #2
Guadalupe County · LA Vernia field · Vertical
Kerschner Harrison #2 (API 42-187-31737) is a plugged well in Guadalupe County, plugged December 5, 1995, last operated by Rampage Exploration Inc..
The RRC has issued one drilling permit, issued July 27, 1981, permitted to 1,000 ft.
It was permitted by Lang Exploration CO. and has since transferred to Rampage Exploration Inc. on the wellbore schedule.
Its lease has reported 14 barrels of oil and 17 mcf of gas since January 1993, last reporting in August 2003.
Operator of record
Permitted by Lang Exploration Co.; the EWA schedule now lists a different operator.
Austin, TX · P-5 Inactive, filed Apr 16, 2003 · (830) 755-9087
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Rampage Exploration Inc. |
| Production reports | Rampage Exploration, Inc.through May 1995 |
| Latest permit | Lang Exploration Co.Jul 27, 1981 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 1,000
- total depth, ft
- 1
- permits on file
- Jul 27, 1981
- last permit issued
- Sep 28, 1981
- completed
- 14
- cumulative oil, bbl
- 17
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Aug 2003
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Sep 28, 1981
- Shut in
- —
- Plugged
- Dec 5, 1995
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 |
|---|---|---|---|---|---|---|
| Kerschner, Harrison O-1-7456 | LA Vernia | Rampage Exploration, Inc. | 1 | 14 | 17 | Jan 1993 – Aug 2003 |
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.
- 1Rampage Exploration, Inc.Jan 1993 → Dec 1993
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 127238-99 | Drill | Lang Exploration Co. | Jul 27, 1981 | Jul 27, 1981 | — | 1,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-1-7456 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 636 | 652 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 2.375 | 610 | — | — |
| 4.5 | 711 | 6.75 | 110 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 13, 1981 | — |
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-187-31737 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-187-31737 → 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/18731737, documented in the API reference.