WELL · 42-083-32796 · DISTRICT 7
Jacobs #1
Coleman County · Wildcat field · Vertical
Jacobs #1 (API 42-083-32796) is a plugged well in Coleman County, plugged December 13, 1990, last operated by Mciver Terry L..
The RRC has issued one drilling permit, issued December 21, 1981, permitted to 2,500 ft.
It was permitted by Santana Exploration, Inc. and has since transferred to Mciver Terry L. on the wellbore schedule.
Completion filings report 5 formation tops, including Tannehill, Home Creek, Crosscut, Jennings.
Operator of record
Permitted by Santana Exploration, Inc.; the EWA schedule now lists a different operator.
Santa Anna, TX · P-5 Y, filed Sep 14, 2001 · 29 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | McIver Terry L. |
| Production reports | none |
| Latest permit | Santana Exploration, Inc.Dec 21, 1981 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 2,500
- total depth, ft
- 1
- permits on file
- Dec 21, 1981
- last permit issued
- Jan 1, 1982
- completed
- 0
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Jan 1, 1982
- Shut in
- —
- Plugged
- Dec 13, 1990
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 |
|---|---|---|---|---|---|---|
| — O-8-25045 | — | — | 0 | 0 | 0 | — |
No volumes reported on these leases in the last three years.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 145472-99 | Drill | Santana Exploration, Inc. | Dec 21, 1981 | Dec 21, 1981 | — | 2,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-8-25045 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 1,728 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Tannehill | 470 | 1,258 |
| Home Creek | 1,008 | 720 |
| Crosscut | 1,824 | -96 |
| Jennings | 1,854 | -126 |
| Fry | 2,108 | -380 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 2,108 | 2,118 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 107 | 11 | 70 S |
| 5.5 | 2,249 | 7.875 | 350 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 13, 1988 | Apr 13, 1988 | Yes |
| 00 | Sep 2, 1988 | — | — |
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-083-32796 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-083-32796 → 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/08332796, documented in the API reference.