WELL · 42-175-31376 · DISTRICT 2
Bluntzer Heirs Unit #2
Goliad County · Poehler (Seg. N. 5100 Gas) field · Vertical
Bluntzer Heirs Unit #2 (API 42-175-31376) is a plugged well in Goliad County, plugged May 3, 2012, last operated by Overly Operating CO..
The RRC has issued one drilling permit, issued September 2, 1980, permitted to 5,500 ft.
Completion filings report 3 formation tops, including Vicksburg, Pettus, Yegua.
Its 2 leases have reported 9.52K barrels of oil and 434 mcf of gas since January 1993, last reporting in July 2012.
Operator of record
San Antonio, TX · P-5 Y, filed May 2, 2014 · 71 permits on file · (210) 826-3822
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Overly Operating Co. |
| Production reports | Overly Operating Co.through Jun 2011 |
| Latest permit | Overly Operating Co.Sep 2, 1980 |
- 5,500
- total depth, ft
- 1
- permits on file
- Sep 2, 1980
- last permit issued
- Oct 15, 1980
- completed
- 9.52K
- cumulative oil, bbl
- 434
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2012
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Oct 15, 1980
- Shut in
- —
- Plugged
- May 3, 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 2 leases this well is completed on; this well is the only one on it.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Bluntzer Heirs Unit O-2-7803 | Poehler (Seg. N. 5100 Gas) | Overly Operating Co. | 1 | 9.52K | 434 | Jan 1993 – Jul 2012 |
| — G-2-91201 | — | — | 0 | 0 | 0 | — |
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.
- 1Overly Operating Co.Jan 1993 → Jun 2011
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 93192-99 | Drill | Overly Operating Co. | Sep 2, 1980 | Sep 2, 1980 | — | 5,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-2-91201 | — | — | — | — |
| — | — O-2-7803 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 326 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 5,148 | 5,154 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 348 | 12.25 | 225 S |
| 2.375 | 5,096 | — | — |
| 4.5 | 5,405 | 7.875 | 1,200 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 19, 1992 | Jun 25, 1992 | — |
| 00 | Jul 13, 1992 | — | — |
| 00 | Jan 12, 1984 | Oct 24, 1980 | — |
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-175-31376 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-175-31376 → 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/17531376, documented in the API reference.