TEXAS · WELLS · LOVING COUNTY · API 42-301-32312 · DISTRICT 7B

Voyager W #1H

Shut in

Loving County · Sandbar (Bone Spring) field · Temp Abandoned  · Horizontal

Voyager W #1H (API 42-301-32312) is a horizontal well in Loving County operated by Eog Resources Inc., completed August 4, 2016 and listed as temp abandoned on the RRC schedule, shut in December 1, 2023.

The RRC has issued one drilling permit (amended once), issued September 22, 2014, permitted to 8,939 ft.

Completion filings report 10 formation tops, including Bell Canyon, Delaware, Cherry Canyon, Brushy Canyon.

Its 2 leases have reported 313K barrels of oil and 3.46M mcf of gas since February 2015, last reporting volume in November 2023. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

EOG Resources Inc.

Based in
Midland, TX
P-5 status
Active – Extension (X)
P-5 last filed
Aug 12, 2026
Permits on file
16,354
Phone
(713) 651-7000

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleEOG Resources Inc.
Production reportsEOG Resources, Inc.through Jan 2024
Latest permitEOG Resources, Inc.Sep 22, 2014
8,939
total depth, ft
2
permits on file
Sep 22, 2014
last permit issued
Aug 4, 2016
completed
313K
cumulative oil, bbl
3.46M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · AUG 2016 THROUGH JAN 2024

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Aug 4, 2016
Shut in
Dec 1, 2023
Plugged
—

Operator's P-5 on the schedule: Active – Extension (X)

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.

Wells nearby

Every well with a location on file around this well, in any state, nearest first.

Loading the map…

Open the full map →

Texas locations come from drilling permits, so most older Texas wells have none and are not listed.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH AUG 2026

Texas reports oil by lease, not by well. These are the 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Voyager W G-10-283671Sandbar (Bone Spring)EOG Resources, Inc.1313K3.46MAug 2016 – Jan 2024
Voyager W O-10-47372Sandbar (Bone Spring)EOG Resources, Inc.100Feb 2015 – —

Gas, mcf lease total

Last 12 months 0 · prior 12 0

010K20K30K202420252026

Wells named Voyager W

EOG Resources Inc.'s other wells filed under this lease name in Loving County, newest permit first. The RRC gives a gas well its own lease number, so the name is what joins the wells of a unit.

Loading the lease's wells

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1EOG Resources, Inc.Aug 2016 → Nov 2023

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
793389-98DrillEOG Resources, Inc.Sep 23, 2014Sep 22, 2014Jan 7, 201511,000
793389-99DrillEOG Resources, Inc.Aug 5, 2014Sep 22, 2014Jan 29, 201511,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Aug 4, 2016Voyager W G-10-283671Sandbar (Bone Spring)EOG Resources Inc.Temp Abandoned · shut in Dec 1, 20238,939
Aug 4, 2016Voyager W O-10-47372Sandbar (Bone Spring)EOG Resources Inc.Not on Schedule—

Formation tops

As filed on W-2/G-1. Subsea from 3,094 ft elevation.Download CSV →

FormationMD ftSubsea
Bell Canyon4,532-1,438
Delaware4,532-1,438
Cherry Canyon5,495-2,401
Brushy Canyon7,043-3,949
Bone SpringBONE SPRINGS8,638-5,544
AtokaATOKA - HIGH PRESSURE——
Pennsylvanian——
Red Bluff——
Strawn——
Wolfcamp——

Perforations

Perforated and open-hole intervals.

FromToType
9,21013,869Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62579812.25310 S
5.513,9608.751,760 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Apr 10, 2018Feb 27, 2018—
00Mar 28, 2017Dec 22, 2016Yes
00Mar 21, 2016Mar 8, 2016Yes

Well logs

1 log loaded from the RRC's log index, the latest received Feb 12, 2018. 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 describedFiles Intervalft, as filedDatereceivedSizeMB
RESISTIVITYSpans Bell Canyon, Delaware, Cherry Canyon, Brushy Canyon, Bone SpringTIFF0 to 8,935Feb 12, 2018run Feb 16, 20159.69

"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.

Find logs withinmiles of this well:List →Map →

Search the well logs loaded into Petrora →

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.

The logs loaded for this well are under Well logs, with the RRC's log search for it. The University Lands library has no per-well link: then paste it into its 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/30132312, documented in the API reference.