WELL · 42-435-33337 · DISTRICT 7
Ward Rip #1093
Sutton County · Sawyer (Canyon) field · Vertical
Ward Rip #1093 (API 42-435-33337) is a plugged well in Sutton County, plugged June 7, 2011, last operated by Ozark Exploration Inc..
The RRC has issued one drilling permit (amended once), issued June 26, 1987, permitted to 6,530 ft.
Completion filings report one formation top, including Canyon.
Operator of record
- Based in
- Dallas, TX
- P-5 status
- Active (A)
- P-5 last filed
- Mar 6, 2026
- Permits on file
- 99
- Phone
- (214) 526-6270
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Ozark Exploration Inc. |
| Production reports | Ozark Exploration, Inc.through Feb 2007 |
| Latest permit | Ozark Exploration, Inc.Jun 26, 1987 |
- 6,530
- total depth, ft
- 2
- permits on file
- Jun 26, 1987
- last permit issued
- Nov 23, 1992
- completed
- 0
- cumulative oil, bbl
- 281K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Dec 2011
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Nov 23, 1992
- Shut in
- —
- Plugged
- Jun 7, 2011
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 |
|---|---|---|---|---|---|---|
| Ward, Rip G-9-125151 | Sawyer (Canyon) | Ozark Exploration, Inc. | 1 | 0 | 281K | Jan 1993 – Dec 2011 |
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.
- 1Ozark Exploration, Inc.Jan 1993 → Feb 2007
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 332063-98 | Drill | Ozark Exploration, Inc. | Sep 16, 1987 | Jun 26, 1987 | — | 6,530 |
| 332063-99 | Drill | Ozark Exploration, Inc. | Jun 24, 1987 | Jun 26, 1987 | — | 6,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-9-125151 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 2,253 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 5,334 | 5,467 | Perforated |
| 5,589 | 5,686 | Perforated |
| 5,887 | 6,226 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 1,321 | 12.25 | 500 S |
| 4.5 | 6,509 | 7.875 | 500 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 | Feb 16, 1993 | Dec 21, 1992 | — |
| 00 | Oct 9, 1987 | Sep 16, 1987 | Yes |
| 00 | Oct 1, 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-435-33337 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-435-33337 → 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/43533337, documented in the API reference.