WELL · 42-083-31965 · DISTRICT 7
Richmond W.J. #3
Coleman County · Coleman County Regular (Gas) field · Vertical
Richmond W.J. #3 (API 42-083-31965) is a plugged well in Coleman County, plugged April 14, 2021, last operated by Ringo Rig LLC.
The RRC has issued one drilling permit, issued January 17, 1980, permitted to 2,990 ft.
It was permitted by Dominy, Chas. F. and has since transferred to Ringo Rig LLC on the wellbore schedule.
Operator of record
Permitted by Dominy, Chas. F.; the EWA schedule now lists a different operator.
Coleman, TX · P-5 Y, filed Apr 4, 2026 · 10 permits on file · (682) 333-4655
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Ringo Rig LLC |
| Production reports | Dominy Oil Co., Inc.through Mar 1993 |
| Latest permit | Dominy, Chas. F.Jan 17, 1980 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 2,990
- total depth, ft
- 1
- permits on file
- Jan 17, 1980
- last permit issued
- Jul 16, 1980
- completed
- 0
- cumulative oil, bbl
- 682
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Apr 2021
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Jul 16, 1980
- Shut in
- —
- Plugged
- Apr 14, 2021
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 |
|---|---|---|---|---|---|---|
| Richmond, W.J. G-8-114547 | Coleman County Regular (Gas) | Ringo Rig LLC | 1 | 0 | 682 | Jan 1993 – Apr 2021 |
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.
- 1Dominy Oil Co., Inc.Jan 1993 → Mar 1993
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 70061-99 | Drill | Dominy, Chas. F. | Jan 17, 1980 | Jan 17, 1980 | Mar 19, 1980 | 2,990 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-8-114547 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 2,268 | 2,284 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 300 | 11 | 200 S |
| 2.375 | 2,404 | — | — |
| 4.5 | 2,413 | 7.875 | 200 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 | Feb 13, 1985 | Jan 18, 1985 | — |
| 00 | Feb 12, 1985 | Dec 28, 1984 | — |
| 00 | Jan 12, 1984 | Aug 4, 1980 | — |
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-083-31965 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-083-31965 → 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/08331965, documented in the API reference.