WELL · 42-457-30601 · DISTRICT 3

Black Stone Minerals Co #1

Plugged

Tyler County · Wildcat field  · Directional

Black Stone Minerals CO #1 (API 42-457-30601) is a plugged well in Tyler County, plugged January 8, 2017, last operated by Vision Operating Company L.L.C..

The RRC has issued one drilling permit (amended twice), issued July 12, 2005, permitted to 15,825 ft.

It was permitted by Brammer Engineering, Inc. and has since transferred to Vision Operating Company L.L.C. on the wellbore schedule.

Completion filings report 5 formation tops, including Wilcox, Midway, Navarro, Austin Chalk.

Operator of record

Vision Operating Company L.L.C.

Permitted by Brammer Engineering, Inc.; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Aug 4, 2025 · 16 permits on file · (239) 405-1429

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleVision Operating Company L.L.C.
Production reportsnone
Latest permitBrammer Engineering, Inc.Jul 12, 2005

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

15,825
total depth, ft
3
permits on file
Jul 12, 2005
last permit issued
Feb 9, 2006
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 2006 THROUGH Jan 2017

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Feb 9, 2006
Shut in
—
Plugged
Jan 8, 2017

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
Black Stone Minerals Co G-3-216266WildcatVision Operating Company, L.L.C.100Feb 2006 – Jan 2017

No volumes reported on these leases in the last three years.

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
603338-97DrillBrammer Engineering, Inc.Feb 14, 2006Jul 12, 2005Jul 19, 200515,825
603338-98DrillBrammer Engineering, Inc.Aug 10, 2005Jul 12, 2005Jul 19, 200515,000
603338-99DrillBrammer Engineering, Inc.Jul 12, 2005Jul 12, 2005Jul 19, 200515,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-3-216266————

Formation tops

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

FormationMD ftSubsea
WilcoxTOP WILCOX6,730-6,437
MidwayTOP MIDWAY10,888-10,595
NavarroTOP NAVARRO12,770-12,477
NavarroBASE NAVARRO13,295-13,002
Austin ChalkTOP AUSTIN CHALK13,928-13,635
WoodbineTOP WOODBINE14,375-14,082

Perforations

Perforated and open-hole intervals.

FromToType
15,48515,539Perforated
15,60115,623Perforated
15,71915,725Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3753,53917.51,313 S
9.62513,05012.251,120 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
00Oct 3, 2006Apr 13, 2006Yes
00Jun 9, 2006——

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