WELL · 42-089-31976 · DISTRICT 3
Kainer John #3
Colorado County · Kainer (Frio 4030) field · Vertical
Kainer John #3 (API 42-089-31976) is a plugged well in Colorado County, plugged September 30, 2004, last operated by Geodominion Petroleum.
The RRC has issued one drilling permit, issued May 30, 1996, permitted to 4,500 ft.
Completion filings report 3 formation tops, including Miocene (undifferentiated), Catahoula, Frio.
Operator of record
- Based in
- Corpus Chrsti, TX
- P-5 status
- Inactive (I)
- P-5 last filed
- Jun 30, 2011
- Permits on file
- 125
- Phone
- (325) 388-4249
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Geodominion Petroleum |
| Production reports | Geodominion Petroleumthrough Jun 2002 |
| Latest permit | Geodominion PetroleumMay 30, 1996 |
- 4,500
- total depth, ft
- 1
- permits on file
- May 30, 1996
- last permit issued
- Jun 18, 1996
- completed
- 0
- cumulative oil, bbl
- 115K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jun 1996 THROUGH Sep 2004
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Jun 18, 1996
- Shut in
- —
- Plugged
- Sep 30, 2004
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 |
|---|---|---|---|---|---|---|
| Kainer, John G-3-159534 | Kainer (Frio 4030) | Geodominion Petroleum | 1 | 0 | 115K | Jun 1996 – Sep 2004 |
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.
- 1Geodominion PetroleumJun 1996 → Jun 2002
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 448408-99 | Drill | Geodominion Petroleum | May 22, 1996 | May 30, 1996 | Jun 7, 1996 | 4,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-3-159534 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 142 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Miocene (undifferentiated)MIOCENE | 2,003 | -1,861 |
| Catahoula | 2,705 | -2,563 |
| Frio | 3,217 | -3,075 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 4,064 | 4,067 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 467 | 12.25 | 235 S |
| 2.875 | 4,449 | 7.875 | 820 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 | Sep 16, 1996 | Aug 2, 1996 | Yes |
| 00 | Aug 29, 1996 | — | — |
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-089-31976 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-089-31976 → 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/08931976, documented in the API reference.