WELL · 42-089-00310 · DISTRICT 3
Columbus Field Unit #1703
Colorado County · Columbus (Consolidated) field · Temp Abandoned · Vertical
Columbus Field Unit #1703 (API 42-089-00310) is a well in Colorado County operated by Rusk Energy Operating LLC, completed May 20, 2022 and listed as temp abandoned on the RRC schedule, shut in June 1, 2017.
The RRC has issued one drilling permit, issued July 7, 1998, permitted to 9,814 ft.
It was permitted by Mitchell Energy Corporation and has since transferred to Rusk Energy Operating LLC on the wellbore schedule.
Completion filings report one formation top, including Wilcox.
Its 4 leases have reported 921K barrels of oil and 1.36M mcf of gas since January 1993, last reporting in July 2026. The leases carry 45 wells, so these are lease totals, not this well alone.
Operator of record
Permitted by Mitchell Energy Corporation; the EWA schedule now lists a different operator.
- Based in
- Houston, TX
- P-5 status
- Active – Extension (X)
- P-5 last filed
- Feb 12, 2026
- Permits on file
- 16
- Phone
- (713) 252-6566
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Devon Energy Operating Co. L.P. |
| Production reports | Sydri Operating, LLCthrough Apr 2019 |
| Latest permit | Mitchell Energy CorporationJul 7, 1998 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 9,814
- total depth, ft
- 1
- permits on file
- Jul 7, 1998
- last permit issued
- May 20, 2022
- completed
- 921K
- cumulative oil, bbl
- 1.36M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- May 20, 2022
- Shut in
- Jun 1, 2017
- Plugged
- —
Operator's P-5 on the schedule: Active (A)
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 4 leases this well is completed on; they carry 45 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Columbus Field Unit G-3-170584 | Columbus (Consolidated) | Rusk Energy Operating LLC | 1 | 0 | 57.1K | Aug 1998 – Jul 2026 |
| Columbus Field Unit O-3-785 | Columbus (11-A) | Devon Energy Operating Co., L.P. | 10 | 351K | 474K | Jan 1993 – Jul 2002 |
| Columbus Field Unit O-3-784 | Columbus | Devon Energy Operating Co., L.P. | 33 | 571K | 834K | Jan 1993 – May 2002 |
| Columbus Field Unit G-3-170586 | Columbus ( 7-E) | Mitchell Energy Company L.P. | 1 | 0 | 0 | Aug 1998 – Aug 2001 |
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.
- 1OXY USA Inc.Jan 1993 → Apr 1998
- 2Mitchell Energy CorporationMay 1998 → Dec 2000
- 3Mitchell Energy Company L.P.Jan 2001 → Aug 2001
- 4Linn Operating, Inc.Nov 2016 → Apr 2017
- 5Linn Operating, LLCMay 2017 → May 2017
- 6Sydri Operating, LLCSep 2018 → Apr 2019
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 477740-99 | Recompletion | Mitchell Energy Corporation | Jul 7, 1998 | Jul 7, 1998 | Aug 4, 1998 | 8,680 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| May 20, 2022 | Columbus Field Unit G-3-170584 | Columbus (Consolidated) | Rusk Energy Operating LLC | Temp Abandoned · shut in Jun 1, 2017 | 9,814 |
| Aug 26, 1998 | Columbus Field Unit G-3-170586 | Columbus ( 7-E) | Mitchell Energy Company L.P. | Not on Schedule | — |
| Dec 2, 1957 | Columbus Field Unit O-3-784 | Columbus | Devon Energy Operating Co. L.P. | Not on Schedule | — |
| — | Columbus Field Unit O-3-785 | Columbus (11-A) | Devon Energy Operating Co. L.P. | Not on Schedule | — |
Formation tops
As filed on W-2/G-1. Subsea from 234 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 8,162 | 8,166 | Perforated |
| 8,297 | 8,312 | Perforated |
| 8,338 | 8,342 | Perforated |
| 8,410 | 8,430 | Perforated |
| 8,450 | 8,465 | Perforated |
| — | 9,276 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 10.75 | 1,612 | 15 | 900 S |
| 7 | 9,814 | 9.875 | 800 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 31, 2022 | Jun 17, 2022 | — |
| 00 | Feb 5, 2019 | Nov 15, 2018 | — |
| 00 | Aug 14, 2012 | Apr 3, 2012 | — |
| 00 | Nov 21, 2001 | Oct 18, 2001 | — |
| 00 | Dec 11, 1998 | Oct 29, 1998 | — |
| 00 | Nov 19, 1998 | Oct 15, 1998 | — |
| 00 | Nov 5, 1998 | — | Yes |
| 00 | Jan 12, 1984 | Oct 21, 1963 | — |
| 00 | Jan 12, 1984 | — | — |
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-089-00310 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-089-00310 → 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/08900310, documented in the API reference.