WELL · 42-479-37004 · DISTRICT 4

Prevost #6

Y

Webb County · Clark Ranch (Lobo) field · Producing  · Vertical

Prevost #6 (API 42-479-37004) is a well in Webb County operated by Columbus Energy LLC, completed September 27, 1998 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued June 12, 1998, permitted to 7,800 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 Queen City, Reklaw, Carrizo, Wilcox.

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 12, 1998

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
Jun 12, 1998
last permit issued
Sep 27, 1998
completed
0
cumulative oil, bbl
1.2M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 1998 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Sep 27, 1998
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
Prevost G-4-170467Clark Ranch (Lobo)Columbus Energy, LLC101.2MSep 1998 – Jul 2026

Gas, mcf lease total

Last 12 months 5,328 · prior 12 4,985(+7%)

05001K202420252026

Chain of custody

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

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

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
476987-99DrillColumbus Energy Corp.Jun 9, 1998Jun 12, 1998Aug 28, 19987,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-170467————

Formation tops

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

FormationMD ftSubsea
Queen CityQUEEN CITY M5V1,615-1,202
Reklaw2,604-2,191
Carrizo2,878-2,465
Wilcox3,916-3,503

Perforations

Perforated and open-hole intervals.

FromToType
7,6677,676Perforated
7,6907,700Perforated
7,7097,712Perforated
7,7227,730Perforated
7,7447,748Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62584812.25300 S
75,7508.75350 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
00Nov 10, 1998Oct 27, 1998Yes
00Oct 30, 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/47937004, documented in the API reference.