WELL · 42-203-31321 · DISTRICT 6

Weathersby-Black #1

N

Harrison County · Brad Bowles (Page Sand) field  · Vertical

Weathersby-Black #1 (API 42-203-31321) is a well in Harrison County operated by Bowles Properties Inc., completed December 5, 1985.

The RRC has issued one drilling permit, issued October 4, 1985, permitted to 6,800 ft.

Completion filings report 6 formation tops, including Base M.A., Base Ma, Massive Anhydrite (marker), Pettit.

Its lease has reported 34.6K barrels of oil and 375K mcf of gas since January 1993, last reporting in July 2026.

Operator of record

Bowles Properties Inc.

Longview, TX · P-5 Y, filed Jun 4, 1999 · 33 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBowles Properties Inc.
Production reportsBowles Energy, Inc.through Jul 2022
Latest permitBowles Properties, Inc.Oct 4, 1985

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

6,800
total depth, ft
1
permits on file
Oct 4, 1985
last permit issued
Dec 5, 1985
completed
34.6K
cumulative oil, bbl
375K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Dec 5, 1985
Shut in
—
Plugged
—

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
Weathersby-Black Heirs O-6-12187Brad Bowles (Page Sand)Bowles Energy, Inc.134.6K375KJan 1993 – Jul 2026

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. 1Bowles Properties, Inc.Jan 1993 → Dec 1998
  2. 2Bowles Energy, Inc.Jan 1999 → Jul 2022

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
286496-99DrillBowles Properties, Inc.Sep 20, 1985Oct 4, 1985Nov 11, 19856,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-6-12187————

Formation tops

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

FormationMD ftSubsea
Base M.A.5,081-4,719
Base MA5,081-4,719
Massive Anhydrite (marker)MASSIVE ANHYDRITE5,081-4,719
Pettit5,898-5,536
PettitTOP PETTIT5,898-5,536
Page Sand6,151-5,789
Travis PeakTOP TRAVIS PEAK6,236-5,874
Travis Peak6,236-5,874

Perforations

Perforated and open-hole intervals.

FromToType
6,1516,155Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62540412.75125 S
4.56,7097.875640 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 24, 2013Aug 2, 2013—
00Jul 17, 1987May 27, 1987—
00Jul 6, 1987——
00Apr 23, 1986Jan 17, 1986—
00Apr 22, 1986Feb 13, 1986Yes
00Apr 19, 1986——
00Mar 27, 1986Feb 13, 1986Yes
00Mar 26, 1986——

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