WELL · 42-479-36857 · DISTRICT 4

Bruni A. M. #18

Y

Webb County · Presa de Oro (Lobo No. 6) field · Producing  · Vertical

Bruni A. M. #18 (API 42-479-36857) is a well in Webb County operated by Faulconer Energy LLC, completed March 5, 1998 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued January 15, 1998, permitted to 9,700 ft.

It was permitted by Petro-Hunt Corporation and has since transferred to Faulconer Energy LLC on the wellbore schedule.

Completion filings report 2 formation tops, including Wilcox, Lobo 6.

No lease production has been reported under this well’s leases.

Operator of record

Faulconer Energy LLC

Permitted by Petro-Hunt Corporation; the EWA schedule now lists a different operator.

Tyler, TX · P-5 Y, filed Sep 4, 2025 · 46 permits on file · (337) 332-1726

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleFaulconer Energy LLC
Production reportsFaulconer Energy, LLCthrough Aug 2022
Latest permitPetro-Hunt CorporationJan 15, 1998

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

9,700
total depth, ft
1
permits on file
Jan 15, 1998
last permit issued
Mar 5, 1998
completed
0
cumulative oil, bbl
2.88M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 1998 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Mar 5, 1998
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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 lease this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Bruni, A. M. G-4-167326Presa de Oro (Lobo No. 6)Faulconer Energy, LLC102.88MMar 1998 – 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. 1Petro-Hunt CorporationMar 1998 → Oct 1998
  2. 2Petro-Hunt, L.L.C.Nov 1998 → Apr 2003
  3. 3Faulconer, Vernon E., Inc.May 2003 → Dec 2021
  4. 4Faulconer Energy, LLCJan 2022 → Aug 2022

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
472281-99DrillPetro-Hunt CorporationJan 15, 1998Jan 15, 1998Jan 31, 19989,700

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-167326————

Formation tops

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

FormationMD ftSubsea
WilcoxTOP OF WILCOX5,150-4,590
Lobo 68,650-8,090

Perforations

Perforated and open-hole intervals.

FromToType
8,6568,668Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,65512.25570 S
77,5938.75470 S
4.59,0006.25160 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
00May 6, 1998Mar 19, 1998Yes
00Apr 6, 1998——

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