WELL · 42-479-34819 · DISTRICT 4

Dinn Mineral Trusts The #1A

N

Webb County · Guerra (4200) field  · Vertical

Dinn Mineral Trusts The #1A (API 42-479-34819) is a well in Webb County operated by Lobo Resources Ltd., completed July 14, 1989.

The RRC has issued 2 drilling permits between 1989 and 1991, permitted to 4,500 ft.

Completion filings report 4 formation tops, including Frio, Cole, Mirando, Cook Mountain.

Its 3 leases have reported 12.3K barrels of oil and 17 mcf of gas since January 1993, last reporting in July 2026.

Operator of record

Lobo Resources Ltd.

Houston, TX · P-5 Y, filed Sep 5, 2008 · 133 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleLobo Resources Ltd.
Production reportsPrime Operating Companythrough Oct 1996
Latest permitLobo Resources, Ltd.Sep 16, 1991

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

4,500
total depth, ft
2
permits on file
Sep 16, 1991
last permit issued
Jul 14, 1989
completed
12.3K
cumulative oil, bbl
17
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jul 14, 1989
Shut in
—
Plugged
—

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.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the 3 leases this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Dinn Mineral Trusts, The O-4-12055Guerra (3800)Hilcorp Energy Company112.3K17Jan 1993 – Jul 2026
— G-4-131963——000—
— G-4-139573——000—

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. 1Lobo Resources, Ltd.Jan 1993 → Mar 1994
  2. 2Lobo Energy, Inc.Apr 1994 → Jun 1994
  3. 3Lobo Operating, Inc.Jul 1994 → Feb 1996
  4. 4Prime Operating CompanyMay 1996 → Oct 1996

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
391957-99RecompletionLobo Resources, Ltd.Sep 16, 1991Sep 16, 1991Sep 17, 19914,500
355837-99DrillLobo Resources, Ltd.Feb 7, 1989Feb 7, 1989—4,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-131963————
—— G-4-139573————
—— O-4-12055————

Formation tops

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

FormationMD ftSubsea
Frio1,180-381
Cole2,080-1,281
Mirando2,640-1,841
Cook Mountain4,210-3,411

Perforations

Perforated and open-hole intervals.

FromToType
3,7963,806Perforated
4,2104,298Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,05612.25420 S
4.54,5107.875360 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 16, 1992Apr 22, 1992—
00Jun 15, 1992——
00Dec 2, 1991Oct 11, 1991Yes
00Oct 23, 1991——
00Oct 12, 1989Aug 1, 1989Yes
00Oct 5, 1989——

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.

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