WELL · 42-163-33975 · DISTRICT 1

R. L. Minor #1H

Y

Frio County · Pearsall (Buda S.) field · NO Production  · Horizontal

R. L. Minor #1H (API 42-163-33975) is a horizontal well in Frio County operated by Texas International Resource LLC, completed January 22, 2016 and listed as no production on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued October 23, 2015, permitted to 7,540 ft.

Completion filings report 10 formation tops, including Olmos, Anacacho, Austin Chalk, Eagle Ford.

Its lease has reported 5.74K barrels of oil since January 2016, last reporting in July 2026.

Operator of record

Texas International Resource LLC

Allen, TX · P-5 Y, filed Jan 5, 2026 · 12 permits on file · (214) 914-3313

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleTexas International Resource LLC
Production reportsTexas International Resource LLCthrough Jan 2020
Latest permitTexas International Resource LLCOct 23, 2015
7,540
total depth, ft
2
permits on file
Oct 23, 2015
last permit issued
Jan 22, 2016
completed
5.74K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 2016 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jan 22, 2016
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Delinquent

Surface location

28.645003, -99.277469

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Frio County.

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 →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
R. L. Minor O-1-19000Pearsall (Buda, S.)Texas International Resource LLC15.74K0Jan 2016 – Jul 2026

No volumes reported on these leases in the last three years.

Chain of custody

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

  1. 1Texas International Resource LLCJan 2016 → Jan 2020

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
811381-98DrillTexas International Resource LLCJun 16, 2017Oct 23, 2015Nov 4, 20157,540
811381-99DrillTexas International Resource LLCOct 20, 2015Oct 23, 2015Nov 4, 20157,400

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-1-19000————

Formation tops

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

FormationMD ftSubsea
Olmos5,189-4,659
Anacacho6,380-5,850
Austin ChalkAUSTIN CHALK - H2S6,800-6,270
Eagle FordEAGLE FORD - H2S7,339-6,809
BudaBUDA - H2S7,540-7,010
Escondido——
GeorgetownGEORGETOWN - H2S——
Navarro——
Pearsall——
Queen City——

Perforations

Perforated and open-hole intervals.

FromToType
8,02011,137Open hole

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.753,57713.51,120 S
7.6257,6509.8751,060 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 →

SuffixFiledW-2 / G-1 dateLogs referenced
00Jul 10, 2017Feb 15, 2017Yes

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's tops beside its 5 nearest neighbours, subsea-aligned so they line up regardless of surface terrain.

Open the cross-section →

Copps Rme B242-283-37733

4.3 KM · Ridgemar Energy Operating, LLC · Section with this well →

Anacacho6,698-6,199
Austin Chalk7,068-6,569
Eagle Ford7,553-7,054
Eagle Ford7,615-7,116
Olmos—
Queen City—
Sparta—
Yegua—

12 TOPS · FIRST 8

Copps Rme B142-283-37732

4.3 KM · Ridgemar Energy Operating, LLC · Section with this well →

Anacacho6,592-6,093
Austin Chalk6,740-6,241
Eagle Ford7,587-7,088
Eagle Ford7,641-7,142
Olmos—
Escondido—
Yegua—
Wilcox—

10 TOPS · FIRST 8

Copps Rme B3 AC42-283-37734

4.3 KM · Ridgemar Energy Operating, LLC · Section with this well →

Midway3,652-3,153
Escondido4,252-3,753
Olmos5,318-4,819
Anacacho6,490-5,991
Austin Chalk6,737-6,238
Wilcox—
Eagle Ford—
Queen City—

10 TOPS · FIRST 8

Heiser Unit42-163-33460

4.3 KM · Blackbrush O & G, LLC · Section with this well →

Austin Chalk6,568-5,993
Austin Chalk6,637-6,062
Austin Chalk6,824-6,249
Eagle Ford7,032-6,457
Buda7,225-6,650

Copps Rme A242-283-37730

4.7 KM · Ridgemar Energy Operating, LLC · Section with this well →

Anacacho6,526-6,011
Austin Chalk6,781-6,266
Eagle Ford7,608-7,093
Eagle Ford7,674-7,159
Olmos—
Queen City—
Escondido—
Wilcox—

12 TOPS · FIRST 8

Copps Rme A142-283-37729

4.7 KM · Ridgemar Energy Operating, LLC · Section with this well →

Anacacho6,765-6,250
Austin Chalk7,158-6,643
Eagle Ford7,621-7,106
Eagle Ford7,689-7,174
Sparta—
Yegua—
Wilcox—
Queen City—

12 TOPS · FIRST 8

Falsette Ranch HC1 B42-283-37132

4.9 KM · Chesapeake Operating, L.L.C. · Section with this well →

Queen City900-383
Yegua1,100-583
Sparta1,400-883
Wilcox1,800-1,283
Escondido4,274-3,757
Olmos5,328-4,811
San Miguel6,204-5,687
Anacacho6,960-6,443

10 TOPS · FIRST 8

Falsette Ranch HC2 B42-283-37133

4.9 KM · Chesapeake Operating, L.L.C. · Section with this well →

Queen City900-405
Yegua1,100-605
Sparta1,400-905
Wilcox1,800-1,305
Escondido3,655-3,160
Olmos5,328-4,833
San Miguel6,198-5,703
Anacacho6,953-6,458

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