TEXAS · WELLS · NOLAN COUNTY · API 42-353-33693 · DISTRICT 6E
Sims #4
Nolan County · Hardrock (King Sand) field · Vertical
Sims #4 (API 42-353-33693) is a plugged well in Nolan County, plugged September 10, 2019, last operated by Scout Energy Management LLC.
The RRC has issued one drilling permit, issued July 24, 2019, permitted to 4,500 ft.
It was permitted by Scout Energy Management LLC and has since transferred to Scout Energy Management LLC on the wellbore schedule.
Operator of record
Scout Energy Management LLC
Permitted by Scout Energy Management LLC; the EWA schedule now lists a different operator.
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | none |
| Latest permit | Scout Energy Management LLCJul 24, 2019 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 4,500
- total depth, ft
- 1
- permits on file
- Jul 24, 2019
- last permit issued
- —
- completed
- —
- cumulative oil, bbl
- —
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- Sep 10, 2019
Surface location
32.377293, -100.280171 NAD27, as filed
32.377416, -100.280549 WGS84
Permit surface location from the RRC GIS record, referenced to NAD27 as the RRC files it; the WGS84 pair is the same point through NOAA's NADCON grid, and the map link uses it, in Nolan County.
Wells nearby
Every well with a location on file around this well, in any state, nearest first.
Texas locations come from drilling permits, so most older Texas wells have none and are not listed.
Only the permit record exists for this well so far, here and in the RRC's wellbore query. Completion reports, formation tops, lease production, and the scanned filings appear once the operator files a completion report, typically months after drilling. Petrora refreshes the wellbore file weekly, so a filing from the last few days may reach the RRC before it shows here. How long each source takes →
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 855398-99 | Drill | Scout Energy Management LLC | Jul 22, 2019 | Jul 24, 2019 | Sep 4, 2019 | 4,500 |
Well logs
1 log loaded from the RRC's log index, the latest received Aug 31, 2020. Density, Neutron, Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.
Open the RRC's log search for this well ↗| Logas described | Files | Intervalft, as filed | Datereceived | SizeMB |
|---|---|---|---|---|
| COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITY | TIFF | 2,500 to 4,228 | Aug 31, 2020run Sep 9, 2019 | 11.9 |
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-353-33693 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-353-33693 → scanned completion filings
The logs loaded for this well are under Well logs, with the RRC's log search for it.
Nearby wells and their tops
NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM
Draw a cross-section
This well has no tops filed, so it cannot anchor a section; its neighbors can.
Section of the neighbors →Sims42-353-33654
0.3 KM · Mid-Con Energy Operating, LLC · Section with this well →
| Coleman Junction | 3,030 | -821 |
| T/Noodle Creek | 3,266 | -1,057 |
| T/Cisco Lime | 3,794 | -1,585 |
| B/Breckenridge | 4,049 | -1,840 |
| T/King Sand | 4,059 | -1,850 |
| Wichita-Albany | — | |
| Tannehill | — | |
| Wolfcamp | — |
10 TOPS · FIRST 8
Joe Young42-353-33616
0.7 KM · Mid-Con Energy Operating, LLC · Section with this well →
| Coleman Junction | 3,339 | -1,087 |
| T/Noodle Creek Lime | 3,500 | -1,248 |
| B/Breckenridge Lime | 4,071 | -1,819 |
| T/King Sand | 4,096 | -1,844 |
| B/Black Shale | 5,499 | -3,247 |
| B/Black Shale Marker | 5,499 | -3,247 |
| T/Strawn Lime | 5,620 | -3,368 |
| T/Strawn SD | 5,670 | -3,418 |
28 TOPS · FIRST 8
Boyd42-353-33638
2.3 KM · Mid-Con Energy Operating, LLC · Section with this well →
| Coleman Junction | 3,012 | -717 |
| Wolfcamp | — | |
| Cisco | — | |
| Elm Creek - Disposal | — | |
| Flippen Sand - Disposal | — | |
| King Sand - Disposal | — | |
| Noodle Creek - Disposal | — | |
| Serratt Sand - Disposal | — |
10 TOPS · FIRST 8
Boyd42-353-33646
2.3 KM · Mid-Con Energy Operating, LLC · Section with this well →
| Coleman Junction | 3,096 | -701 |
| T/Noodle Creek Lime | 3,475 | -1,080 |
| T/Noodle Zone | 3,502 | -1,107 |
| B/Breckenridge Lime | 4,232 | -1,837 |
| T/King Sand | 4,241 | -1,846 |
| Wolfcamp | — | |
| Elm Creek - Disposal | — | |
| Noodle Creek - Disposal | — |
10 TOPS · FIRST 8
Brooks42-353-33660
2.6 KM · Mid-Con Energy Operating, LLC · Section with this well →
| Coleman Junction | 2,866 | -548 |
| Noodle Creek - Disposal | 3,292 | -974 |
| T/Saddle Creek | 3,672 | -1,354 |
| B/Breckenridge | 4,149 | -1,831 |
| T/King Sand | 4,160 | -1,842 |
| Wolfcamp | — | |
| Wichita-Albany | — | |
| Tannehill | — |
10 TOPS · FIRST 8
Boyd, (Caddo Conglomerate) Unit42-353-32574
5.3 KM · Clear Fork, Incorporated · Section with this well →
| Canyon | 4,920 | -2,467 |
| Caddo | 6,512 | -4,059 |
| Caddo | 6,512 | -4,059 |
Boyd, C.E. 59 LCS42-353-32596
5.6 KM · Clear Fork, Incorporated · Section with this well →
| Coleman Junction | 2,892 | -378 |
| Coleman Junction | 2,892 | -378 |
| Base Noodle Creek | 3,582 | -1,068 |
| Noodle Creek | 3,582 | -1,068 |
| Palo Pinto | 5,652 | -3,138 |
| Palo Pinto | 5,652 | -3,138 |
C. E. Boyd '59'42-353-32997
5.8 KM · Clear Fork, Incorporated · Section with this well →
| Palo Pinto | 5,686 | -3,169 |
| Palo Pinto | 5,686 | -3,169 |
| Caddo | 6,468 | -3,951 |
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/35333693, documented in the API reference.