WELL · 42-165-38795 · DISTRICT 8

Laredo A #3H

Y

Gaines County · Carter-New Mexico (San Andres) field · Producing  · Horizontal

Laredo A #3H (API 42-165-38795) is a horizontal well in Gaines County operated by Joint Resources Company, completed February 3, 2020 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued September 24, 2019, permitted to 5,900 ft.

Completion filings report 10 formation tops, including Yates, Seven Rivers, Queen, San Andres.

Its lease has reported 83.3K barrels of oil and 778K mcf of gas since February 2020, last reporting in July 2026.

Operator of record

Joint Resources Company

Fort Worth, TX · P-5 Y, filed Dec 4, 2025 · 241 permits on file · (817) 946-1158

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleJoint Resources Company
Production reportsJoint Resources Companythrough Apr 2026
Latest permitJoint Resources CompanySep 24, 2019
5,900
total depth, ft
2
permits on file
Sep 24, 2019
last permit issued
Feb 3, 2020
completed
83.3K
cumulative oil, bbl
778K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 2020 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Feb 3, 2020
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

Surface location

32.792558, -103.022035

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Gaines 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
Laredo A O-11-71013Carter-New Mexico (San Andres)Joint Resources Company183.3K778KFeb 2020 – Jul 2026

Gas, mcf lease total

Last 12 months 86,736 · prior 12 152,326(-43%)

010K20K30K202420252026

Oil, barrels lease total

Last 12 months 6,585 · prior 12 9,681(-32%)

01K2K202420252026

Chain of custody

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

  1. 1Joint Resources CompanyFeb 2020 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
857247-98DrillJoint Resources CompanyOct 2, 2019Sep 24, 2019Oct 4, 20195,900
857247-99DrillJoint Resources CompanySep 19, 2019Sep 24, 2019Oct 5, 20195,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-11-71013————

Formation tops

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

FormationMD ftSubsea
YatesYATES - OVERPRESSURE, INERT GAS3,456143
Seven Rivers3,731-132
Queen4,335-736
San AndresSAN ANDRES - ACTIVE CO2 FLOOD5,176-1,577
Clear ForkCLEARFORK——
Glorieta——
Leonard——
San Angelo——
Spraberry——
Wichita-AlbanyWICHITA ALBANY——

Perforations

Perforated and open-hole intervals.

FromToType
6,14413,071Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6252,27412.25915 S
5.513,1317.8752,917 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
00Jun 9, 2020Apr 28, 2020Yes

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) and the University Lands library. 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 →

Laredo42-165-38747

0.0 KM · Joint Resources Company · Section with this well →

Yates3,455144
Seven Rivers3,696-97
Queen4,331-732
San Andres5,205-1,606
Clear Fork—
Spraberry—
San Angelo—
Leonard—

10 TOPS · FIRST 8

Scrambler-Alc42-165-38882

1.1 KM · Joint Resources Company · Section with this well →

Yates3,369238
Seven Rivers3,717-110
Queen4,325-718
San Andres5,096-1,489
Wichita-Albany—
Spraberry—
San Angelo—
Leonard—

10 TOPS · FIRST 8

Scrambler42-165-38713

1.2 KM · Joint Resources Company · Section with this well →

Yates3,406209
Seven Rivers4,038-423
Queen4,444-829
San Andres5,176-1,561
Glorieta—
Wichita-Albany—
Spraberry—
San Angelo—

10 TOPS · FIRST 8

Scrambler A42-165-38777

2.5 KM · Joint Resources Company · Section with this well →

Yates3,353275
Seven Rivers3,59929
Queen4,202-574
San Andres5,100-1,472
Leonard—
Wichita-Albany—
Spraberry—
San Angelo—

10 TOPS · FIRST 8

Granberry42-165-33205

2.6 KM · O'Neill Properties, Ltd. · Section with this well →

Yates3,352258
San Andres5,072-1,462
Glorieta6,289-2,679
Clear Fork6,720-3,110
Wichita-Albany8,239-4,629
Queen—
San Angelo—
Seven Rivers—

10 TOPS · FIRST 8

Renegade42-165-38779

3.0 KM · Joint Resources Company · Section with this well →

Yates3,389252
Seven Rivers3,645-4
Queen4,247-606
San Andres5,137-1,496
Glorieta—
Clear Fork—
Leonard—
San Angelo—

10 TOPS · FIRST 8

Renegade42-165-38591

3.6 KM · Joint Resources Company · Section with this well →

Yates3,350246
Seven Rivers3,950-354
Queen4,331-735
San Andres4,957-1,361
San Angelo—
Spraberry—
Wichita-Albany—
Clear Fork—

10 TOPS · FIRST 8

Renegade42-165-38694

3.7 KM · Joint Resources Company · Section with this well →

Yates3,352283
Seven Rivers3,986-351
Queen4,382-747
San Andres5,183-1,548
Clear Fork—
Spraberry—
Wichita-Albany—
Glorieta—

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