WELL · 42-301-31873 · DISTRICT 8
JO Sledge #1
Loving County · Wheat (Cherry Canyon) field · Producing · Vertical
JO Sledge #1 (API 42-301-31873) is a well in Loving County operated by QP Inc., completed July 16, 2020 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit, issued October 16, 2012, permitted to 7,000 ft.
Completion filings report 13 formation tops, including Ramsey, Olds, Cherry Canyon, Rustler.
Its lease has reported 27.6K barrels of oil since March 2013, last reporting in July 2026.
Operator of record
Midland, TX · P-5 Y, filed Jan 5, 2026 · 4 permits on file · (432) 634-4455
SOURCE · RRC EWA WELLBORE SCHEDULE
- 7,000
- total depth, ft
- 1
- permits on file
- Oct 16, 2012
- last permit issued
- Jul 16, 2020
- completed
- 27.6K
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Mar 2013 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Jul 16, 2020
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Active
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 |
|---|---|---|---|---|---|---|
| JO Sledge O-10-43921 | Wheat (Cherry Canyon) | QP, Inc. | 1 | 27.6K | 0 | Mar 2013 – Jul 2026 |
Oil, barrels lease total
Last 12 months 298 · prior 12 817(-64%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1QP, Inc.Apr 2013 → Nov 2025
Permits
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-10-43921 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 2,788 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Ramsey | 4,766 | -1,978 |
| Olds | 4,831 | -2,043 |
| Cherry Canyon | 6,021 | -3,233 |
| Rustler | 6,072 | -3,284 |
| AtokaATOKA - HIGH PRESSURE | — | — |
| Bell Canyon | — | — |
| Bone Spring | — | — |
| Brushy Canyon | — | — |
| Delaware | — | — |
| Pennsylvanian | — | — |
| Red Bluff | — | — |
| Strawn | — | — |
| Wolfcamp | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 6,021 | 6,026 | Perforated |
| 6,072 | 6,081 | Perforated |
| 6,084 | 6,088 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 887 | 11 | 500 S |
| 5.5 | 6,243 | 7.875 | 550 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 7, 2020 | Jul 22, 2020 | — |
| 00 | Feb 10, 2014 | May 9, 2013 | 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-301-31873 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-301-31873 → scanned completion filings
Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward) and the University Lands library. 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/30131873, documented in the API reference.