WELL · 42-177-31583 · DISTRICT 1
Sasha #1
Gonzales County · Vertical
Sasha #1 (API 42-177-31583) is a permitted well in Gonzales County filed by H.D.C. Ventures, Inc.; no completion report is on file yet.
The RRC has issued 3 drilling permits between 1984 and 1985, permitted to 8,000 ft.
Completion filings report 5 formation tops, including Austin Chalk, Eagle Ford, Buda, Del Rio.
Operator of record
Gonzales, TX · P-5 Y, filed Aug 15, 1990 · 34 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | none |
| Latest permit | H.D.C. Ventures, Inc.Oct 21, 1985 |
- 8,000
- total depth, ft
- 3
- permits on file
- Oct 21, 1985
- last permit issued
- —
- completed
- 0
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Aug 2003
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- —
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 |
|---|---|---|---|---|---|---|
| Sasha O-1-10633 | Peach Creek (Austin Chalk) | McRae Energy Corp. | 1 | 0 | 0 | Jan 1993 – Aug 2003 |
No volumes reported on these leases in the last three years.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 288017-99 | Recompletion | H.D.C. Ventures, Inc. | Aug 5, 1985 | Oct 21, 1985 | — | 7,600 |
| 259231-99 | Drill | H.D.C. Ventures, Inc. | Oct 25, 1984 | Nov 27, 1984 | Jul 12, 1984 | 7,600 |
| 245484-99 | Drill | H.D.C. Ventures, Inc. | Jun 29, 1984 | Jun 29, 1984 | — | 8,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-1-10633 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 285 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Austin Chalk | 7,068 | -6,783 |
| Eagle FordEAGLEFORD | 7,462 | -7,177 |
| Buda | 7,530 | -7,245 |
| Del Rio | 7,622 | -7,337 |
| Georgetown | 7,640 | -7,355 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 7,247 | 7,452 | Perforated |
| 7,524 | 7,540 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 2,214 | 12.25 | 805 sx |
| 5.5 | 7,658 | 7.875 | 275 sx |
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 | Nov 12, 1985 | Oct 24, 1985 | Yes |
| 00 | Nov 6, 1985 | — | — |
| 00 | Aug 16, 1984 | Aug 6, 1984 | — |
| 00 | Aug 15, 1984 | Aug 6, 1984 | — |
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-177-31583 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-177-31583 → 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/17731583, documented in the API reference.