WELL · 42-237-40514 · DISTRICT 9
Sahota Red House #3
Jack County · Jack County Regular field · Shut IN · Vertical
Sahota Red House #3 (API 42-237-40514) is a well in Jack County operated by Arcooil Corp, completed April 24, 2019 and listed as shut in on the RRC schedule.
The RRC has issued one drilling permit, issued October 5, 2018, permitted to 3,500 ft.
Completion filings report 10 formation tops, including Palo Pinto, Butram, Atoka, Bryson.
Its lease has reported 14 barrels of oil since April 2019, last reporting in July 2026. The lease carries 2 wells, so these are lease totals, not this well alone.
Operator of record
San Antonio, TX · P-5 Y, filed Aug 4, 2025 · 6 permits on file · (918) 740-7661
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Arcooil Corp |
| Production reports | Arcooil Corpthrough Nov 2019 |
| Latest permit | Arcooil CorpOct 5, 2018 |
- 3,500
- total depth, ft
- 1
- permits on file
- Oct 5, 2018
- last permit issued
- Apr 24, 2019
- completed
- 14
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Apr 2019 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Apr 24, 2019
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Delinquent
Surface location
33.184107, -98.253151
OpenStreetMap → · Google Maps →
Permit surface location from the RRC GIS record, in Jack County.
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; they carry 2 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Sahota Red House O-13-33878 | Jack County Regular | Arcooil Corp | 2 | 14 | 0 | Apr 2019 – Jul 2026 |
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.
- 1Arcooil CorpApr 2019 → Nov 2019
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 845082-99 | Drill | Arcooil Corp | Sep 26, 2018 | Oct 5, 2018 | — | 3,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-13-33878 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 1,150 ft elevation.Download CSV →
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 349 | 12.25 | 230 S |
| 4.5 | 3,500 | 7.875 | 390 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 6, 2019 | May 6, 2019 | 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-237-40514 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-237-40514 → 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.
Nearby wells and their tops
NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM
Draw a cross-section
This well's tops beside its 5 nearest neighbours, subsea-aligned so they line up regardless of surface terrain.
Sahota Red House42-237-40508
0.3 KM · Arcooil Corp · Section with this well →
| Palo Pinto | 1,510 | -356 |
| Butram | 2,200 | -1,046 |
| Bryson | — | |
| Canyon | — | |
| Atoka | — | |
| Weir | — | |
| Village Bend | — | |
| Strawn | — |
10 TOPS · FIRST 8
Carney42-237-39855
1.0 KM · White Knight Production LLC · Section with this well →
| Bend | 4,868 | -3,670 |
| Conglomerate | 4,868 | -3,670 |
| Marble Falls | 5,066 | -3,868 |
| Barnett | 5,469 | -4,271 |
| Barnett | 5,469 | -4,271 |
Simpson42-237-39636
1.5 KM · Oakridge Oil and Gas, LP · Section with this well →
| Conglomerate | 4,893 | -3,667 |
| Marble Falls | 4,997 | -3,771 |
| Barnett | 5,379 | -4,153 |
| Barnett | 5,380 | -4,154 |
| Ellenburger | 5,594 | -4,368 |
Kemp-Derrick Unit42-237-38670
2.2 KM · Western Chief Oil & Gas Company · Section with this well →
| Palo Pinto | 1,077 | 158 |
| Capps Lime | 1,749 | -514 |
| Bryson | 2,898 | -1,663 |
| Bryson | 2,930 | -1,695 |
| Brannon Bridge | 3,204 | -1,969 |
| Caddo | 4,467 | -3,232 |
| Marble Falls | 4,938 | -3,703 |
| Mississippian | 5,346 | -4,111 |
June Easter42-237-40302
2.3 KM · Petrobal Omega 1, LLC · Section with this well →
| Palo Pinto | 1,103 | 39 |
| Village Bend | 1,781 | -639 |
| Weir | 1,980 | -838 |
| Butram | 2,225 | -1,083 |
| Bryson | 2,788 | -1,646 |
| Caddo | 4,479 | -3,337 |
| Atoka | 4,788 | -3,646 |
| Gunsight | — |
10 TOPS · FIRST 8
Bloodworth42-237-39576
2.4 KM · Oakridge Oil and Gas, LP · Section with this well →
| Butram | 2,190 | -958 |
| Caddo | 4,550 | -3,318 |
| Marble Falls | 5,100 | -3,868 |
| Barnett | 5,520 | -4,288 |
| Barnett | 5,520 | -4,288 |
Simpson42-237-40544
2.5 KM · Atoka Operating, Inc. · Section with this well →
| Bryson | 3,082 | -1,720 |
| Strawn | 4,178 | -2,816 |
| Caddo | 4,526 | -3,164 |
| Weir | — | |
| Atoka | — | |
| Butram | — | |
| Gunsight | — | |
| Palo Pinto | — |
10 TOPS · FIRST 8
Peavy 'F'42-237-39706
2.7 KM · Veritas Energy, LLC · Section with this well →
| Caddo | 4,586 | -3,403 |
| Bend | 4,910 | -3,727 |
| Marble Falls | 5,032 | -3,849 |
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/23740514, documented in the API reference.