WELL · 42-263-31862 · DISTRICT 8
Polar 38 #1
Kent County · Vertical
Polar 38 #1 (API 42-263-31862) is a permitted well in Kent County filed by Sharp Image Energy, Inc.; no completion report is on file yet.
The RRC has issued 2 drilling permits between 2009 and 2021, permitted to 8,000 ft.
Completion filings report 3 formation tops, including Strawn, Mississippian, Ellenburger.
Its lease has reported 33.3K barrels of oil since May 2009, last reporting in May 2022.
Operator of record
Big Spring, TX · P-5 Y, filed May 4, 2026 · 665 permits on file · (432) 238-6478
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | Sharp Image Energy, Inc.through Jun 2019 |
| Latest permit | Sharp Image Energy, Inc.Feb 16, 2021 |
- 8,000
- total depth, ft
- 2
- permits on file
- Feb 16, 2021
- last permit issued
- —
- completed
- 33.3K
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · May 2009 THROUGH May 2022
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- —
Surface location
33.008559, -100.998415
OpenStreetMap → · Google Maps →
Permit surface location from the RRC GIS record, in Kent 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; this well is the only one on it.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Polar 38 O-11-69401 | Polar (Penn.) | Sharp Image Energy, Inc. | 1 | 33.3K | 0 | May 2009 – May 2022 |
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.
- 1Sharp Image Energy, Inc.May 2009 → Jun 2019
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 867714-99 | Recompletion | Sharp Image Energy, Inc. | Feb 11, 2021 | Feb 16, 2021 | — | 7,927 |
| 679529-99 | Drill | Sharp Image Energy, Inc. | Mar 16, 2009 | Mar 17, 2009 | Apr 23, 2009 | 8,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-11-69401 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 2,401 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| StrawnUPPER STRAWN | 7,145 | -4,744 |
| StrawnSTRAWN C | 7,355 | -4,954 |
| Mississippian | 7,595 | -5,194 |
| Ellenburger | 7,765 | -5,364 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 7,532 | 7,536 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 1,707 | 11 | 525 S |
| 5.5 | 5,520 | 7.875 | 500 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 | Sep 10, 2009 | Jun 5, 2009 | Yes |
| 00 | Aug 7, 2009 | — | — |
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-263-31862 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-263-31862 → 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.
Carol Sue Reed '59'42-263-32064
3.4 KM · Tong Petrotech Inc. · Section with this well →
| Missipian | 7,708 | -5,424 |
| Pollan (Ellenburger) | 7,746 | -5,462 |
| Silurian (undifferentiated) | — |
Carol Sue Reed '66-SE'42-169-34132
3.9 KM · Tong Petrotech Inc. · Section with this well →
| Strawn | 7,236 | -4,913 |
| Strawn | 7,536 | -5,213 |
| Mississippian | 7,614 | -5,291 |
| Ellenburger | 7,752 | -5,429 |
Cooper Creek 11 B42-263-31784
9.9 KM · Sharp Image Energy, Inc. · Section with this well →
| Yates | 700 | 1,508 |
| San Andres | 1,100 | 1,108 |
| Clear Fork | 2,100 | 108 |
| Coleman Junction | 2,500 | -292 |
| Wichita-Albany | 3,000 | -792 |
| Noodle Creek | 4,140 | -1,932 |
| Fuller | 4,900 | -2,692 |
| Wolfcamp | 5,300 | -3,092 |
12 TOPS · FIRST 8
Cooper Creek #142-263-31775
11.2 KM · Sharp Image Energy, Inc. · Section with this well →
| Clear Fork | 2,178 | -45 |
| Wolfcamp | 4,170 | -2,037 |
| Noodle Creek | 4,607 | -2,474 |
| Wolfcamp | 5,096 | -2,963 |
Cogdell Canyon Reef Unit42-415-03933
11.4 KM · Occidental Permian Ltd. · Section with this well →
| Yates | 1,330 | 1,129 |
| Clear Fork | 3,350 | -891 |
| Canyon | 6,700 | -4,241 |
Cogdell Canyon Reef Unit42-415-35465
11.4 KM · Occidental Permian Ltd. · Section with this well →
| Yates | 708 | 1,745 |
| San Andres | 1,626 | 827 |
| Clear Fork | 2,513 | -60 |
| Wolfcamp | 4,420 | -1,967 |
| Wichita-Albany | 4,504 | -2,051 |
| Fuller Sand | 5,242 | -2,789 |
| Wichita-Albany | — | |
| Glorieta | — |
10 TOPS · FIRST 8
P.L. Fuller NCT-142-415-04165
11.7 KM · Occidental Permian Ltd. · Section with this well →
| Fuller | 5,289 | -2,766 |
| Canyon | 6,918 | -4,395 |
| Strawn | 7,359 | -4,836 |
Fuller42-415-03914
11.7 KM · Occidental Permian Ltd. · Section with this well →
| Canyon | 6,760 | -4,263 |
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/26331862, documented in the API reference.