WELL · 42-227-40467 · DISTRICT 10
Carter 22-15 #1H
Howard County · Horizontal
Carter 22-15 #1H (API 42-227-40467) is a permitted horizontal well in Howard County filed by Paladin Petroleum Iii, L.L.C.; no completion report is on file yet.
The RRC has issued one drilling permit, issued November 26, 2019, permitted to 10,000 ft.
Operator of record
Austin, TX · P-5 Y, filed Apr 4, 2026 · 42 permits on file · (512) 656-8477
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | none |
| Latest permit | Paladin Petroleum III, L.L.C.Nov 26, 2019 |
- 10,000
- total depth, ft
- 1
- permits on file
- Nov 26, 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
- —
Surface location
32.352047, -101.249306
OpenStreetMap → · Google Maps →
Permit surface location from the RRC GIS record, in Howard County.
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 |
|---|---|---|---|---|---|---|
| 859438-99 | Drill | Paladin Petroleum III, L.L.C. | Nov 26, 2019 | Nov 26, 2019 | — | 10,000 |
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-227-40467 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-227-40467 → 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 has no tops filed, so it cannot anchor a section; its neighbours can.
B-Side 21-1642-227-41158
0.8 KM · Bayswater Operating Company LLC · Section with this well →
| Rustler | 993 | 1,400 |
| Yates | 1,163 | 1,230 |
| Seven Rivers | 1,313 | 1,080 |
| San Andres | 2,313 | 80 |
| Glorieta | 2,370 | 23 |
| Clear Fork | 2,555 | -162 |
| Spraberry | 4,425 | -2,032 |
| Dean | 5,854 | -3,461 |
10 TOPS · FIRST 8
Side Hustle 27-22-1542-227-41749
1.3 KM · Bayswater Operating Company LLC · Section with this well →
| Rustler | 988 | 1,427 |
| Yates | 1,160 | 1,255 |
| Seven Rivers | 1,342 | 1,073 |
| San Andres | 2,293 | 122 |
| Glorieta | 2,376 | 39 |
| Clear Fork | 2,453 | -38 |
| Spraberry | 4,578 | -2,163 |
| Dean | 5,702 | -3,287 |
10 TOPS · FIRST 8
Sidekick 27-22-1542-227-41774
1.3 KM · Bayswater Operating Company LLC · Section with this well →
| Rustler | 1,012 | 1,403 |
| Yates | 1,190 | 1,225 |
| Seven Rivers | 1,342 | 1,073 |
| San Andres | 2,304 | 111 |
| Glorieta | 2,380 | 35 |
| Clear Fork | 2,509 | -94 |
| Spraberry | 4,567 | -2,152 |
| Dean | 5,738 | -3,323 |
10 TOPS · FIRST 8
Forever 21-16-9A42-227-40912
2.0 KM · Bayswater Operating Company LLC · Section with this well →
| Rustler | 964 | 1,377 |
| Yates | 1,108 | 1,233 |
| Seven Rivers | 1,261 | 1,080 |
| San Andres | 2,253 | 88 |
| Glorieta | 2,369 | -28 |
| Clear Fork | 2,549 | -208 |
| Spraberry | 4,489 | -2,148 |
| Dean | 5,913 | -3,572 |
10 TOPS · FIRST 8
Forty Caliber 20-1742-227-40911
2.0 KM · Bayswater Operating Company LLC · Section with this well →
| Rustler | 944 | 1,397 |
| Yates | 1,095 | 1,246 |
| Seven Rivers | 1,252 | 1,089 |
| San Andres | 2,248 | 93 |
| Glorieta | 2,361 | -20 |
| Clear Fork | 2,523 | -182 |
| Spraberry | 4,527 | -2,186 |
| Dean | 5,937 | -3,596 |
10 TOPS · FIRST 8
Read 3442-227-39460
2.3 KM · Paladin Petroleum III, L.L.C. · Section with this well →
| San Andres | 2,170 | 230 |
| Glorieta | 3,073 | -673 |
| Clear Fork | 3,233 | -833 |
| Spraberry | 3,695 | -1,295 |
| Dean | 5,583 | -3,183 |
| Wolfcamp | 5,936 | -3,536 |
| Leonard | — | |
| Coleman Junction | — |
10 TOPS · FIRST 8
Read 3342-227-39425
2.5 KM · Paladin Petroleum III, L.L.C. · Section with this well →
| San Andres | 2,253 | 158 |
| Clear Fork | 3,020 | -609 |
| Spraberry | 5,000 | -2,589 |
| Coleman Junction | — | |
| Yates | — | |
| Wolfcamp | — | |
| Seven Rivers | — | |
| Leonard | — |
10 TOPS · FIRST 8
Read 33 SWD42-227-39525
3.0 KM · Paladin Petroleum III, L.L.C. · Section with this well →
| San Andres | 2,253 | 198 |
| Clear Fork | 3,020 | -569 |
| Wolfcamp | — | |
| Spraberry | — | |
| Seven Rivers | — | |
| Dean | — | |
| Glorieta | — | |
| Leonard | — |
10 TOPS · FIRST 8
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/22740467, documented in the API reference.