WELL · 42-285-32352 · DISTRICT 2
Schilhab #1
Lavaca County · Seclusion (Cockfield 6100) field · Vertical
Schilhab #1 (API 42-285-32352) is a plugged well in Lavaca County, plugged December 21, 2006, last operated by Camoil Inc..
The RRC has issued one drilling permit, issued December 19, 1995, permitted to 6,500 ft.
It was permitted by Zachry Exploration, Inc. and has since transferred to Camoil Inc. on the wellbore schedule.
Operator of record
Permitted by Zachry Exploration, Inc.; the EWA schedule now lists a different operator.
Columbus, TX · P-5 Y, filed Oct 4, 2025 · 20 permits on file · (979) 733-6678
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Camoil Inc. |
| Production reports | Camoil, Inc.through Jul 2004 |
| Latest permit | Zachry Exploration, Inc.Dec 19, 1995 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 6,500
- total depth, ft
- 1
- permits on file
- Dec 19, 1995
- last permit issued
- Jan 24, 1996
- completed
- 0
- cumulative oil, bbl
- 832K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1996 THROUGH Oct 2008
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Jan 24, 1996
- Shut in
- —
- Plugged
- Dec 21, 2006
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 |
|---|---|---|---|---|---|---|
| Schilhab G-2-157510 | Seclusion (Cockfield 6100) | Camoil, Inc. | 1 | 0 | 832K | Jan 1996 – Oct 2008 |
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.
- 1Zachry Exploration, Inc.Jan 1996 → Apr 2001
- 2Wagner Oil CompanyMay 2001 → Aug 2002
- 3Camoil, Inc.Sep 2002 → Jul 2004
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 443013-99 | Drill | Zachry Exploration, Inc. | Dec 19, 1995 | Dec 19, 1995 | Jan 2, 1996 | 6,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-2-157510 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 6,242 | 6,250 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 1,257 | 12.25 | 325 S |
| 4.5 | 6,483 | 7.875 | 400 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 | May 3, 1996 | Feb 16, 1996 | Yes |
| 00 | Apr 3, 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-285-32352 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-285-32352 → 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/28532352, documented in the API reference.