WELL · 42-423-32256 · DISTRICT 6
Goldston Fee #1
Smith County · Hitts Lake North (Paluxy) field · Directional
Goldston Fee #1 (API 42-423-32256) is a plugged well in Smith County, plugged November 13, 2012, last operated by Goldston Oil Corporation.
The RRC has issued one drilling permit (amended once), issued May 24, 2010, permitted to 7,600 ft.
Completion filings report 5 formation tops, including Buda, Goodland, Mainstreet Lime, Paluxy.
Its lease has reported 2.42K barrels of oil since November 2010, last reporting in May 2013.
Operator of record
Houston, TX · P-5 Y, filed Feb 4, 2026 · 265 permits on file · (800) 268-2661
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Goldston Oil Corporation |
| Production reports | Goldston Oil Corporationthrough Apr 2012 |
| Latest permit | Goldston Oil CorporationMay 24, 2010 |
- 7,600
- total depth, ft
- 2
- permits on file
- May 24, 2010
- last permit issued
- Nov 25, 2010
- completed
- 2.42K
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Nov 2010 THROUGH May 2013
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Nov 25, 2010
- Shut in
- —
- Plugged
- Nov 13, 2012
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 |
|---|---|---|---|---|---|---|
| Goldston Fee O-6-15006 | Hitts Lake, North (Paluxy) | Goldston Oil Corporation | 1 | 2.42K | 0 | Nov 2010 – May 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.
- 1Goldston Oil CorporationDec 2010 → Apr 2012
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 679907-98 | Drill | Goldston Oil Corporation | Dec 3, 2010 | May 24, 2010 | May 22, 2010 | 7,600 |
| 679907-99 | Drill | Goldston Oil Corporation | Mar 27, 2009 | May 24, 2010 | May 22, 2010 | 7,600 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-6-15006 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 553 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 7,280 | 7,306 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 1,690 | 12.25 | 368 S |
| 5.5 | 7,447 | 8.75 | 360 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 | Apr 8, 2011 | Dec 29, 2010 | Yes |
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-423-32256 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-423-32256 → 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/42332256, documented in the API reference.