WELL · 42-215-32354 · DISTRICT 4

Val Verde #1

Plugged

Hidalgo County · Texan Gardens (5900) field  · Vertical

Val Verde #1 (API 42-215-32354) is a plugged well in Hidalgo County, plugged July 1, 1999, last operated by Coastal Oil & Gas Corporation.

The RRC has issued one drilling permit, issued October 14, 1996, permitted to 9,000 ft.

It was permitted by Bnp Petroleum Corporation and has since transferred to Coastal Oil & Gas Corporation on the wellbore schedule.

Completion filings report one formation top, including Frio.

Operator of record

Coastal Oil & Gas Corporation

Permitted by BNP Petroleum Corporation; the EWA schedule now lists a different operator.

Based in
Houston, TX
P-5 status
Inactive (I)
P-5 last filed
Mar 2, 2001
Permits on file
1,543
Phone
(713) 420-6346

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCoastal Oil & Gas Corporation
Production reportsCoastal Oil & Gas Corporationthrough Sep 1998
Latest permitBNP Petroleum CorporationOct 14, 1996

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
Oct 14, 1996
last permit issued
Nov 4, 1996
completed
0
cumulative oil, bbl
380K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Nov 1996 THROUGH Jun 1999

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Nov 4, 1996
Shut in
—
Plugged
Jul 1, 1999

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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Val Verde G-4-161501Texan Gardens (5900)Coastal Oil & Gas Corporation10183KNov 1996 – Jun 1999
Val Verde G-4-161657Texan Gardens (5700)Coastal Oil & Gas Corporation10197KNov 1996 – Jun 1999

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. 1BNP Petroleum CorporationNov 1996 → Dec 1997
  2. 2Coastal Oil & Gas CorporationJan 1998 → Sep 1998

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
453797-99DrillBNP Petroleum CorporationOct 14, 1996Oct 14, 1996Oct 20, 19969,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-161501————
—— G-4-161657————

Formation tops

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

FormationMD ftSubsea
Frio5,050-4,808

Perforations

Perforated and open-hole intervals.

FromToType
5,7305,736Perforated
5,9165,923Perforated
5,9345,944Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62561812.2585 S
4.56,1157.875376 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
00Mar 10, 1997Jan 21, 1997Yes
00Feb 27, 1997——
00Feb 12, 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 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/21532354, documented in the API reference.