TEXAS · WELLS · WEBB COUNTY · B.M.T. LEASE · API 42-479-36598 · DISTRICT 04

B.M.T. #8

Y

Webb County · Laredo (Lobo) field · Producing  · Vertical

B.M.T. #8 (API 42-479-36598) is a well in Webb County operated by Columbus Energy LLC, completed March 7, 1997 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued December 11, 1996, permitted to 7,650 ft.

It was permitted by Columbus Energy Corp. and has since transferred to Columbus Energy LLC on the wellbore schedule.

Its lease has reported 3.45K barrels of oil and 1.1M mcf of gas since March 1997, last reporting volume in April 2026.

Operator of record

Columbus Energy LLC

Permitted by Columbus Energy Corp.; the EWA schedule now lists a different operator.

Based in
Houston, TX
P-5 status
Active – Extension (X)
P-5 last filed
Jun 2, 2026
Permits on file
51
Phone
(832) 432-8540

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleColumbus Energy LLC
Production reportsColumbus Energy, LLCthrough Apr 2026
Latest permitColumbus Energy Corp.Dec 11, 1996

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

7,650
total depth, ft
1
permits on file
Dec 11, 1996
last permit issued
Mar 7, 1997
completed
3.45K
cumulative oil, bbl
1.1M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 1997 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Mar 7, 1997
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active – Extension (X)

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
B.M.T. G-4-162560Laredo (Lobo)Columbus Energy, LLC13.45K1.1MMar 1997 – Apr 2026

Gas, mcf lease total

Last 12 months 5,898 · prior 12 5,367(+10%)

05001K202420252026

Chain of custody

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

  1. 1Columbus Energy Corp.Apr 1997 → Jun 2007
  2. 2Columbus Energy, LLCJul 2007 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
456077-99DrillColumbus Energy Corp.Dec 9, 1996Dec 11, 1996Feb 10, 19977,800

Completions

CompletedLeaseFieldOperatorStatusDepth
Mar 7, 1997B.M.T. G-4-162560Laredo (Lobo)Columbus Energy LLCProducing7,650

Perforations

Perforated and open-hole intervals.

FromToType
7,4487,493Perforated
7,5687,578Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62584812.25310 S
75,4888.75345 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00May 8, 1997Apr 21, 1997Yes
00Apr 29, 1997——

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 filed since 2004 open from the RRC's log search for this well; none are loaded here for it.

Find logs withinmiles of this well:List →Map →

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