WELL · 42-175-33337 · DISTRICT 2
Hamman & Anderson Gas Unit No. 2 #3
Goliad County · Hordes Creek (Kay Sand) field · Vertical
Hamman & Anderson Gas Unit NO. 2 #3 (API 42-175-33337) is a plugged well in Goliad County, plugged February 11, 2004, last operated by Santos USA Corp..
The RRC has issued one drilling permit, issued April 2, 2001, permitted to 14,500 ft.
It was permitted by Esenjay Exploration, Inc and has since transferred to Santos USA Corp. on the wellbore schedule.
Operator of record
Permitted by Esenjay Exploration, Inc; the EWA schedule now lists a different operator.
Houston, TX · P-5 Y, filed Sep 3, 2010 · 67 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Santos USA Corp. |
| Production reports | Esenjay Exploration, Incthrough Mar 2003 |
| Latest permit | Esenjay Exploration, IncApr 2, 2001 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 14,500
- total depth, ft
- 1
- permits on file
- Apr 2, 2001
- last permit issued
- Aug 23, 2001
- completed
- 0
- cumulative oil, bbl
- 7.57K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Aug 2001 THROUGH Feb 2004
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Aug 23, 2001
- Shut in
- —
- Plugged
- Feb 11, 2004
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 |
|---|---|---|---|---|---|---|
| Hamman & Anderson Gas Unit No. 2 G-2-192573 | Hordes Creek (Kay Sand) | Santos USA Corp. | 1 | 0 | 7.57K | Aug 2001 – Feb 2004 |
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.
- 1Esenjay Exploration, IncSep 2002 → Mar 2003
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 507204-99 | Drill | Esenjay Exploration, Inc | Mar 29, 2001 | Apr 2, 2001 | May 18, 2001 | 14,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-2-192573 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 10,842 | 10,870 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 13.375 | 2,200 | 17.5 | 1,465 S |
| 9.625 | 8,940 | 12.25 | 835 S |
| 2.875 | 13,438 | 4.5 | 345 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 | Mar 18, 2003 | Dec 13, 2001 | Yes |
| 00 | Feb 5, 2003 | — | — |
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-175-33337 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-175-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/17533337, documented in the API reference.