WELL · 42-187-32342 · DISTRICT 1
Sommer John #5
Guadalupe County · LA Vernia field · Vertical
Sommer John #5 (API 42-187-32342) is a well in Guadalupe County operated by Eagle Petroleum, completed March 1, 1983.
The RRC has issued one drilling permit, issued December 14, 1982, permitted to 1,000 ft.
Its lease has reported 4.23K barrels of oil and 21 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
San Marcos, TX · P-5 Y, filed Jan 15, 1986 · 10 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Eagle Petroleum |
| Production reports | Three J Energy, Inc.through May 2025 |
| Latest permit | Eagle PetroleumDec 14, 1982 |
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
- Dec 14, 1982
- last permit issued
- Mar 1, 1983
- completed
- 4.23K
- cumulative oil, bbl
- 21
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Mar 1, 1983
- 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; they carry 7 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Schnitz, Harley D. O-1-2176 | LA Vernia | Three J Energy, Inc. | 7 | 4.23K | 21 | Jan 1993 – Jul 2026 |
Oil, barrels lease total
Last 12 months 6 · prior 12 50(-88%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Zaf OilJan 1993 → Aug 2002
- 2Three J Energy IncSep 2002 → Jun 2004
- 3New BeginningJul 2004 → Jun 2016
- 4Three J Energy, Inc.Jul 2016 → May 2025
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 180467-99 | Drill | Eagle Petroleum | Dec 14, 1982 | Dec 14, 1982 | — | 1,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-1-2176 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 628 | 642 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 1 | 700 | — | — |
| 4.5 | 788 | 6.75 | 125 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 17, 1987 | Jun 6, 1983 | — |
| 00 | Aug 1, 1987 | — | — |
| 00 | Jan 12, 1984 | Jun 6, 1983 | — |
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-32342 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-187-32342 → 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/18732342, documented in the API reference.