WELL · 42-493-31838 · DISTRICT 1
Casares Unit #1
Wilson County · Marcelina Creek (Buda) field · Vertical
Casares Unit #1 (API 42-493-31838) is a plugged well in Wilson County, plugged February 17, 2003, last operated by Pontiac Oil Inc..
The RRC has issued one drilling permit, issued November 13, 1985, permitted to 8,000 ft.
It was permitted by Rgr Production and has since transferred to Pontiac Oil Inc. on the wellbore schedule.
Completion filings report 3 formation tops, including Austin Chalk, Eagle Ford, Buda.
Operator of record
Permitted by RGR Production; the EWA schedule now lists a different operator.
Graham, TX · P-5 Y, filed Dec 4, 2025
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Pontiac Oil Inc. |
| Production reports | none |
| Latest permit | RGR ProductionNov 13, 1985 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 8,000
- total depth, ft
- 1
- permits on file
- Nov 13, 1985
- last permit issued
- Feb 16, 1986
- completed
- 0
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Feb 16, 1986
- Shut in
- —
- Plugged
- Feb 17, 2003
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 |
|---|---|---|---|---|---|---|
| Casares Unit O-1-11417 | Marcelina Creek (Buda) | Pontiac Oil, Inc. | 1 | 0 | 0 | Jan 1993 – Jul 2026 |
No volumes reported on these leases in the last three years.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 290521-99 | Drill | RGR Production | Nov 13, 1985 | Nov 13, 1985 | Dec 4, 1985 | 8,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-1-11417 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 341 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Austin ChalkAUSTIN | 7,255 | -6,914 |
| Eagle FordEAGLEFORD | 7,537 | -7,196 |
| Buda | 7,617 | -7,276 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 7,617 | 7,693 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 1,720 | 12.25 | 700 S |
| 4.5 | 7,713 | 7.875 | 1,250 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 | Apr 1, 1986 | Mar 11, 1986 | Yes |
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-493-31838 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-493-31838 → 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/49331838, documented in the API reference.