WELL · 42-395-32044 · DISTRICT 5

Valero Hearne #1

N

Robertson County  · Vertical

Valero Hearne #1 (API 42-395-32044) is a permitted well in Robertson County filed by Valero Terminaling & Distrib. CO; no completion report is on file yet.

The RRC has issued one drilling permit, issued May 28, 2019, permitted to 265 ft.

Operator of record

Valero Terminaling & Distrib. Co

San Antonio, TX · P-5 Y, filed Jul 4, 2026 · 1 permits on file · (866) 423-0898

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitValero Terminaling & Distrib. CoMay 28, 2019
265
total depth, ft
1
permits on file
May 28, 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

30.859040, -96.574773

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Robertson 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

PermitTypeOperatorReceivedIssuedSpudDepth
853346-99DrillValero Terminaling & Distrib. CoMay 21, 2019May 28, 2019—265

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.

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.

Section of the neighbours →

Kudu Unit42-395-32025

1.8 KM · Treadstone Energy Prtnr OP, LLC · Section with this well →

Pecan Gap4,712-4,419
Austin Chalk5,853-5,560
Travis Peak—
Paluxy—
Buda—
Georgetown—
Edwards—
Cotton Valley—

10 TOPS · FIRST 8

Midnight Special 242-395-32047

2.8 KM · BBL Operating Company LLC · Section with this well →

Nacatoch2,200-1,941
Pecan Gap4,461-4,202
Austin Chalk5,647-5,388
Eagle Ford5,825-5,566
Edwards—
Georgetown—
Travis Peak—
Paluxy—

10 TOPS · FIRST 8

Big Bad John42-395-32023

2.9 KM · BBL Operating Company LLC · Section with this well →

Nacatoch4,468-4,209
Austin Chalk5,654-5,395
Travis Peak—
Buda—
Cotton Valley—
Edwards—
Georgetown—
Paluxy—

9 TOPS · FIRST 8

Midnight Special42-395-32033

2.9 KM · BBL Operating Company LLC · Section with this well →

Nacatoch2,200-1,941
Austin Chalk5,692-5,433
Eagle Ford5,818-5,559
Woodbine5,818-5,559
Georgetown—
Paluxy—
Travis Peak—
Buda—

10 TOPS · FIRST 8

Pale Rider42-395-32089

4.2 KM · LRR Pecos Valley, LLC · Section with this well →

Navarro3,003-2,739
Tylru3,533-3,269
Pecan Gap4,375-4,111
Wolf City Sand4,572-4,308
Sprinkle4,779-4,515
Austin Chalk5,593-5,329
Woodbine—
Nacatoch—

9 TOPS · FIRST 8

Pabst Unit42-395-32034

5.9 KM · Treadstone Energy Prtnr OP, LLC · Section with this well →

Pecan Gap4,389-4,121
Austin Chalk5,591-5,323
Travis Peak—
Woodbine—
Paluxy—
Nacatoch—
Georgetown—
Edwards—

10 TOPS · FIRST 8

Pabst Unit42-395-32038

5.9 KM · Treadstone Energy Prtnr OP, LLC · Section with this well →

Pecan Gap4,445-4,177
Austin Chalk5,639-5,371
Woodbine5,855-5,587
Giddings (Eagleford)5,979-5,711
Edwards—
Nacatoch—
Georgetown—
Buda—

10 TOPS · FIRST 8

Aragorn A42-395-32113

6.2 KM · Wildfire Energy Operating LLC · Section with this well →

Pecan Gap4,473-4,208
Gober5,611-5,346
Austin Chalk5,678-5,413
Woodbine—
Buda—
Cotton Valley—
Edwards—
Georgetown—

11 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/39532044, documented in the API reference.