TEXAS · WELLS · BORDEN COUNTY · API 42-033-32436 · DISTRICT 08
Zant, H.N. SWD #14R
Borden County · Vertical
Zant, H.N. Swd #14R (API 42-033-32436) is a former disposal or injection well in Borden County, last operated by Sabalo Operating, LLC; its UIC permit is no longer active.
The RRC has issued one drilling permit (amended once), issued September 22, 2017, permitted to 11,500 ft.
Operator of record
- Based in
- Corpus Chrsti, TX
- P-5 status
- Inactive (I)
- P-5 last filed
- Sep 3, 2021
- Permits on file
- 180
- Phone
- (361) 888-7708
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | none |
| Latest permit | Sabalo Operating, LLCSep 22, 2017 |
- 11,500
- total depth, ft
- 2
- permits on file
- Sep 22, 2017
- 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.526237, -101.523268 NAD27, as filed
32.526349, -101.523677 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 Borden County.
Wells nearby
Every well with a location on file around this one, in any state, nearest first.
Texas locations come from drilling permits, so most older Texas wells have none and are not listed.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 831049-98 | Drill | Sabalo Operating, LLC | Nov 13, 2018 | Sep 22, 2017 | — | 11,500 |
| 831049-99 | Drill | Sabalo Operating, LLC | Sep 18, 2017 | Sep 22, 2017 | — | 8,290 |
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-033-32436 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-033-32436 → scanned completion filings
Log images filed since 2004 open from the RRC's log search for this well; none are loaded here 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.
Erlking Unit B 21-0942-033-32619
0.8 KM · Surge Operating, LLC · Section with this well →
| Rustler | 1,323 | 1,262 |
| Yates | 1,834 | 751 |
| San Andres | 3,225 | -640 |
| Clear Fork | 5,434 | -2,849 |
| Spraberry | 5,993 | -3,408 |
| Dean | 7,220 | -4,635 |
| Wolfcamp | 7,358 | -4,773 |
| Leonard | — |
10 TOPS · FIRST 8
Erlking Unit a 21-0942-033-32618
0.8 KM · Surge Operating, LLC · Section with this well →
| Rustler | 1,333 | 1,252 |
| Yates | 1,844 | 741 |
| San Andres | 3,235 | -650 |
| Clear Fork | 5,444 | -2,859 |
| Spraberry | 6,030 | -3,445 |
| Dean | 7,230 | -4,645 |
| Wolfcamp | 7,368 | -4,783 |
| Leonard | — |
10 TOPS · FIRST 8
Erlking Unit B 21-0942-033-32565
0.9 KM · Surge Operating, LLC · Section with this well →
| Rustler | 1,263 | 1,276 |
| Yates | 1,800 | 739 |
| San Andres | 3,081 | -542 |
| Clear Fork | 5,337 | -2,798 |
| Spraberry | 5,873 | -3,334 |
| Dean | 7,090 | -4,551 |
| Wolfcamp | 7,286 | -4,747 |
| Wichita-Albany | — |
10 TOPS · FIRST 8
Erlking Unit B 21-0942-033-32564
0.9 KM · Surge Operating, LLC · Section with this well →
| Rustler | 1,254 | 1,285 |
| Yates | 1,791 | 748 |
| San Andres | 3,167 | -628 |
| Clear Fork | 5,345 | -2,806 |
| Spraberry | 5,884 | -3,345 |
| Dean | 7,094 | -4,555 |
| Wolfcamp | 7,180 | -4,641 |
| Wichita-Albany | — |
10 TOPS · FIRST 8
Erlking Unit a 21-0942-033-32537
1.2 KM · Surge Operating, LLC · Section with this well →
| Rustler | 1,303 | 1,297 |
| Yates | 1,776 | 824 |
| San Andres | 3,410 | -810 |
| Clear Fork | 5,457 | -2,857 |
| Spraberry | 6,011 | -3,411 |
| Dean | 7,212 | -4,612 |
| Wolfcamp | 7,301 | -4,701 |
| Wichita-Albany | — |
10 TOPS · FIRST 8
Erlking Unit a 21-0942-033-32541
1.2 KM · Surge Operating, LLC · Section with this well →
| Rustler | 1,297 | 1,303 |
| Yates | 1,772 | 828 |
| San Andres | 3,398 | -798 |
| Glorieta | 4,560 | -1,960 |
| Clear Fork | 5,428 | -2,828 |
| Spraberry | 5,978 | -3,378 |
| Dean | 7,160 | -4,560 |
| Leonard | — |
10 TOPS · FIRST 8
Dodger 33-2842-227-42032
1.6 KM · Laredo Petroleum, Inc. · Section with this well →
| Salado | 1,290 | 1,299 |
| Yates | 1,803 | 786 |
| Seven Rivers | 1,909 | 680 |
| Queen | 2,268 | 321 |
| Grayburg | 2,818 | -229 |
| San Andres | 3,198 | -609 |
| Glorieta | 4,117 | -1,528 |
| Clear Fork | 4,779 | -2,190 |
10 TOPS · FIRST 8
Dodger 33-2842-227-39465
1.7 KM · Sabalo Operating, LLC · Section with this well →
| Yates | 1,817 | 742 |
| Seven Rivers | 1,912 | 647 |
| San Andres | 3,269 | -710 |
| Glorieta | 4,131 | -1,572 |
| Clear Fork | 4,177 | -1,618 |
| Spraberry | 5,961 | -3,402 |
| Leonard | 6,474 | -3,915 |
| Dean | 7,187 | -4,628 |
12 TOPS · FIRST 8
Beyond the permit record
RRC UIC permits · H-10 reported volumes
Injection
- 0
- bbl, last 12 reported months
- 0
- bbl, all reported
- Dec 2022
- reported through
| UIC | Kind | Status | Permitted bbl/d | Max psi | Zone ft |
|---|---|---|---|---|---|
| 000115587 | H-1 Injection | Canceled Jul 21, 2023 | 40,000 | 4,080 | 8,160–11,500 |
MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS
Last 12 months 0 · prior 12 0
USGS catalog, Texas
Seismicity near this well
- 0
- M2+ events within 10 km, last 2 years
- —
- largest
A proximity count, not an attribution. How to read it →
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/03332436, documented in the API reference.