WELL · 42-247-32247 · DISTRICT 4
Austin #3
Jim Hogg County · Jaron (Queen City) field · Vertical
Austin #3 (API 42-247-32247) is a plugged well in Jim Hogg County, plugged February 27, 2013, last operated by Hamman Oil & Refining Company.
The RRC has issued one drilling permit, issued May 8, 2002, permitted to 10,000 ft.
Completion filings report one formation top, including Queen City.
Operator of record
- Based in
- Houston, TX
- P-5 status
- Active (A)
- P-5 last filed
- Jun 1, 2026
- Permits on file
- 359
- Phone
- (713) 526-7417
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Hamman Oil & Refining Company |
| Production reports | Hamman Oil & Refining Companythrough Nov 2011 |
| Latest permit | Hamman Oil & Refg. Co.May 8, 2002 |
- 10,000
- total depth, ft
- 1
- permits on file
- May 8, 2002
- last permit issued
- Jun 12, 2002
- completed
- 0
- cumulative oil, bbl
- 476K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jun 2002 THROUGH Aug 2013
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Jun 12, 2002
- Shut in
- —
- Plugged
- Feb 27, 2013
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 |
|---|---|---|---|---|---|---|
| Austin G-4-189306 | Jaron (Queen City) | Hamman Oil & Refining Company | 1 | 0 | 476K | Jun 2002 – Aug 2013 |
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.
- 1Hamman Oil & Refining CompanyJun 2002 → Nov 2011
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 519833-99 | Drill | Hamman Oil & Refg. Co. | May 8, 2002 | May 8, 2002 | May 12, 2002 | 10,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-4-189306 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 515 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Queen CityQUEEN CITY A | 9,454 | -8,939 |
| Queen CityQUEEN CITY B | 9,490 | -8,975 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 9,490 | 9,510 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 2,360 | 12.25 | 680 S |
| 7 | 6,615 | 8.75 | 285 S |
| 4.5 | 9,740 | 6.125 | 230 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 | Aug 7, 2002 | Jun 24, 2002 | Yes |
| 00 | Jul 15, 2002 | — | — |
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-247-32247 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-247-32247 → 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/24732247, documented in the API reference.