WELL · 42-479-37839 · DISTRICT 4

Martinez D. S. #7

Y

Webb County · Blancas Creek (Lobo 6) field · Producing  · Vertical

Martinez D. S. #7 (API 42-479-37839) is a well in Webb County operated by Columbus Energy LLC, completed August 7, 2001 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued June 4, 2001, permitted to 9,000 ft.

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

Completion filings report 4 formation tops, including Lobo Unconformity, Lobo 1, Lobo 3, Lobo 6.

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

Operator of record

Columbus Energy LLC

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

Houston, TX · P-5 Y, filed Apr 4, 2026 · 51 permits on file · (956) 722-5238

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleColumbus Energy LLC
Production reportsColumbus Energy, LLCthrough Apr 2026
Latest permitColumbus Energy Corp.Jun 4, 2001

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

9,000
total depth, ft
1
permits on file
Jun 4, 2001
last permit issued
Aug 7, 2001
completed
0
cumulative oil, bbl
474K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Aug 2001 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Aug 7, 2001
Shut in
—
Plugged
—

Operator's P-5 on the schedule: 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
Martinez, D. S. G-4-186229Blancas Creek (Lobo 6)Columbus Energy, LLC10474KAug 2001 – Jul 2026

Gas, mcf lease total

Last 12 months 5,722 · prior 12 4,815(+19%)

05001K202420252026

Chain of custody

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

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

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
509806-99DrillColumbus Energy Corp.Jun 4, 2001Jun 4, 2001Jun 19, 20019,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-186229————

Formation tops

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

FormationMD ftSubsea
Lobo Unconformity6,622-6,197
Lobo 17,121-6,696
Lobo 37,378-6,953
Lobo 67,592-7,167

Perforations

Perforated and open-hole intervals.

FromToType
7,2287,240Perforated
7,3787,390Perforated
7,5987,614Perforated
7,6247,630Perforated
7,6677,670Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62583012.25306 S
75,6988.75340 S
4.57,8336.25386 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
00Jan 28, 2002Dec 3, 2001Yes
00Jan 7, 2002——

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