WELL · 42-479-37438 · DISTRICT 4

Rancho Blanco #10

Y

Webb County · Rancho Blanco (Lobo) field · Producing  · Vertical

Rancho Blanco #10 (API 42-479-37438) is a well in Webb County operated by Columbus Energy LLC, completed April 30, 2000 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued February 16, 2000, permitted to 7,800 ft.

It was permitted by Zachry Exploration, Inc. and has since transferred to Columbus Energy LLC on the wellbore schedule.

Completion filings report one formation top, including Lobo.

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

Operator of record

Columbus Energy LLC

Permitted by Zachry Exploration, Inc.; 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 permitZachry Exploration, Inc.Feb 16, 2000

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

7,800
total depth, ft
1
permits on file
Feb 16, 2000
last permit issued
Apr 30, 2000
completed
0
cumulative oil, bbl
4.32M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2000 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 30, 2000
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
Rancho Blanco G-4-177063Rancho Blanco (Lobo)Columbus Energy, LLC104.32MApr 2000 – Jul 2026

Gas, mcf lease total

Last 12 months 3,631 · prior 12 5,177(-30%)

05001K202420252026

Chain of custody

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

  1. 1Zachry Exploration, Inc.Apr 2000 → Nov 2009
  2. 2Zachry Exploration, Ltd.May 2002 → Jan 2009
  3. 3Zachry Exploration, LLCDec 2009 → Jul 2010
  4. 4Columbus Energy, LLCAug 2010 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
492190-99DrillZachry Exploration, Inc.Feb 16, 2000Feb 16, 2000Feb 21, 20007,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-177063————

Formation tops

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

FormationMD ftSubsea
Lobo6,850-6,411

Perforations

Perforated and open-hole intervals.

FromToType
6,9257,060Perforated
7,2177,279Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62593412.25305 S
76,0698.75300 S
4.57,6686.25290 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 25, 2000May 12, 2000Yes
00Jun 5, 2000——

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