WELL · 42-317-33441 · DISTRICT 8
Schenecker -24- #1
Martin County · Spraberry (Trend Area) field · Vertical
Schenecker -24- #1 (API 42-317-33441) is a plugged well in Martin County, plugged March 16, 1993, last operated by Midland Oil And Gas Inc..
The RRC has issued 2 drilling permits between 1987 and 1988, permitted to 10,800 ft.
Completion filings report 3 formation tops, including Spraberry, Dean, Strawn.
Operator of record
Midland, TX · P-5 Y, filed Jun 4, 2026 · 229 permits on file · (432) 661-1580
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Midland Oil and Gas Inc. |
| Production reports | Midland Oil and Gas, Inc.through Jan 1993 |
| Latest permit | Midland Oil and Gas, Inc.Oct 24, 1988 |
- 10,800
- total depth, ft
- 2
- permits on file
- Oct 24, 1988
- last permit issued
- Oct 24, 1988
- completed
- 0
- cumulative oil, bbl
- 431
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 1993
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Oct 24, 1988
- Shut in
- —
- Plugged
- Mar 16, 1993
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 |
|---|---|---|---|---|---|---|
| Schenecker -24- O-10-31434 | Spraberry (Trend Area) | Midland Oil and Gas, Inc. | 1 | 0 | 431 | Jan 1993 – Jul 1993 |
No volumes reported on these leases in the last three years.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 352453-99 | Recompletion | Midland Oil and Gas, Inc. | Oct 19, 1988 | Oct 24, 1988 | — | 10,730 |
| 332773-99 | Drill | Midland Oil and Gas, Inc. | Jul 13, 1987 | Jul 16, 1987 | — | 10,800 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-10-31434 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 2,793 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 7,670 | 8,021 | Perforated |
| 8,191 | 8,594 | Perforated |
| 8,971 | 9,337 | Perforated |
| 10,263 | 10,493 | Perforated |
| 10,457 | 10,493 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 13.375 | 318 | 17.5 | 350 S |
| 8.625 | 4,240 | 11 | 300 S |
| 4.5 | 10,730 | 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 | Apr 4, 1989 | Feb 28, 1989 | — |
| 00 | Oct 30, 1987 | Sep 25, 1987 | Yes |
| 00 | Oct 20, 1987 | — | — |
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-317-33441 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-317-33441 → scanned completion filings
Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward) and the University Lands library. 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/31733441, documented in the API reference.