TEXAS · WELLS · AUSTIN COUNTY · SCHAFFNER LEASE · API 42-015-30864 · DISTRICT 03
Schaffner #1
Austin County · El Pleasant (Wilcox LO) field · Vertical
Schaffner #1 (API 42-015-30864) is a plugged well in Austin County, plugged June 30, 2009, last operated by Jamex Inc..
The RRC has issued one drilling permit (amended once), issued May 21, 2004, permitted to 13,500 ft.
Completion filings report 4 formation tops, including Frio, Yegua, Wilcox, L. Wilcox.
Operator of record
- Based in
- Lewisville, TX
- P-5 status
- Active (A)
- P-5 last filed
- Jun 22, 2026
- Permits on file
- 332
- Phone
- (214) 265-7141
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Jamex Inc. |
| Production reports | Jamex, Inc.through Feb 2008 |
| Latest permit | Jamex, Inc.May 21, 2004 |
- 13,500
- total depth, ft
- 2
- permits on file
- May 21, 2004
- last permit issued
- Jan 7, 2005
- completed
- 0
- cumulative oil, bbl
- 38.7K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 2005 THROUGH Jun 2009
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Jan 7, 2005
- Shut in
- —
- Plugged
- Jun 30, 2009
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 |
|---|---|---|---|---|---|---|
| Schaffner G-3-209751 | El Pleasant (Wilcox, LO) | Jamex, Inc. | 1 | 0 | 38.7K | Jan 2005 – Jun 2009 |
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.
- 1Jamex, Inc.Jan 2005 → Feb 2008
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 545797-98 | Drill | Jamex, Inc. | May 10, 2005 | May 21, 2004 | Aug 19, 2004 | 13,500 |
| 545797-99 | Drill | Jamex, Inc. | May 17, 2004 | May 21, 2004 | Aug 19, 2004 | 13,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Jan 7, 2005 | Schaffner G-3-209751 | El Pleasant (Wilcox LO) | Jamex Inc. | Plugged | — |
Formation tops
As filed on W-2/G-1. Subsea from 153 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 11,918 | 11,940 | Perforated |
| 11,969 | 11,980 | Perforated |
| 12,137 | 12,160 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 5.5 | 12,630 | 8.75 | 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 | Sep 28, 2005 | Mar 7, 2005 | Yes |
| 00 | Aug 2, 2005 | — | — |
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-015-30864 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-015-30864 → 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/01530864, documented in the API reference.