WELL · 42-479-31860 · DISTRICT 4

Bruni Mineral Trust A #2

N

Webb County · Laredo (Lobo) field  · Vertical

Bruni Mineral Trust A #2 (API 42-479-31860) is a permitted well in Webb County filed by Chevron U. S. A. Inc.; no completion report is on file yet.

The RRC has issued 2 drilling permits between 1977 and 1994, permitted to 10,690 ft.

It was permitted by Chevron U. S. A. Inc. and has since transferred to Gulf Oil Corp. on the wellbore schedule.

Operator of record

Gulf Oil Corp.

Permitted by Chevron U. S. A. Inc.; the EWA schedule now lists a different operator.

Based in
Houston, TX
P-5 status
Inactive (I)
P-5 last filed
Apr 4, 1985
Permits on file
4,382
Phone
(713) 754-9729

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleGulf Oil Corp.
Production reportsHilcorp Energy Companythrough Jan 2023
Latest permitChevron U. S. A. Inc.Aug 25, 1994

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

10,690
total depth, ft
2
permits on file
Aug 25, 1994
last permit issued
—
completed
0
cumulative oil, bbl
146K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Bruni Mineral Trust 'A' G-4-153633Juanita (7100)Hilcorp Energy Company1092.1KAug 1994 – Jul 2026
Bruni Mineral Trust "A" G-4-80717Juanita (Lobo)Chevron U. S. A. Inc.1054KJan 1993 – Sep 1996

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. 1Chevron U. S. A. Inc.Mar 1993 → Sep 2003
  2. 2Laredo EnergyMar 2004 → Mar 2005
  3. 3Chesapeake Operating, Inc.Apr 2005 → Dec 2008
  4. 4Hilcorp Energy CompanyOct 2014 → Jan 2023

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
427385-99RecompletionChevron U. S. A. Inc.Aug 25, 1994Aug 25, 1994Jul 15, 19949,550
10567-99DrillGulf Oil Corp.Oct 25, 1977Oct 25, 1977—10,690

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-80717————
—— G-4-153633————

Perforations

Perforated and open-hole intervals.

FromToType
7,1407,150Perforated
7,3087,321Perforated
7,3547,360Perforated
9,9469,987Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.751,02013.25500 S
10.751,02013.5500 S
10.751,020——
7.6257,8749.875710 S
7.6257,874——
2.3759,870——
510,3366.5550 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 12, 1995Oct 14, 1994Yes
00Apr 12, 1995——
00Jan 12, 1984Mar 3, 1978—
00Jan 12, 1984Jan 25, 1978—

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