WELL · 42-391-32174 · DISTRICT 2
Gant-Stone #2R
Refugio County · McFaddin (2600) field · Vertical
Gant-Stone #2R (API 42-391-32174) is a plugged well in Refugio County, plugged June 14, 2002, last operated by Anderson Oil Ltd..
The RRC has issued 2 drilling permits between 1997 and 1999, permitted to 3,500 ft.
Operator of record
Houston, TX · P-5 Y, filed Dec 4, 2025 · 114 permits on file · (713) 881-8600
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Anderson Oil Ltd. |
| Production reports | Anderson Oil Ltd.through May 2001 |
| Latest permit | Anderson Oil LtdNov 23, 1999 |
- 3,500
- total depth, ft
- 2
- permits on file
- Nov 23, 1999
- last permit issued
- Nov 24, 1999
- completed
- 0
- cumulative oil, bbl
- 534K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Mar 1997 THROUGH Jun 2002
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Nov 24, 1999
- Shut in
- —
- Plugged
- Jun 14, 2002
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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Gant-Stone G-2-176013 | McFaddin (2600) | Anderson Oil Ltd. | 1 | 0 | 182K | Nov 1999 – Jun 2002 |
| Gant-Stone G-2-162809 | Fagan (Matt 2150) | Anderson Oil Corporation | 1 | 0 | 352K | Mar 1997 – Nov 1999 |
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.
- 1Anderson Oil CorporationMar 1997 → Nov 1999
- 2Anderson Oil Ltd.Nov 1999 → May 2001
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 489756-99 | Recompletion | Anderson Oil Ltd | Nov 23, 1999 | Nov 23, 1999 | Nov 23, 1999 | 3,400 |
| 459009-99 | Drill | Anderson Oil Corporation | Feb 21, 1997 | Feb 21, 1997 | Feb 22, 1997 | 3,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-2-162809 | — | — | — | — |
| — | — G-2-176013 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 2,148 | 2,156 | Perforated |
| 2,663 | 2,669 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 1,402 | 12.25 | 485 S |
| 4.5 | 3,200 | 7.875 | 615 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 | May 1, 2000 | Dec 20, 1999 | Yes |
| 00 | Mar 10, 2000 | — | — |
| 00 | Jun 27, 1997 | Mar 27, 1997 | Yes |
| 00 | May 15, 1997 | — | — |
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-391-32174 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-391-32174 → 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/39132174, documented in the API reference.