WELL · 42-039-30583 · DISTRICT 3

Belcher W. T. -A- #42

Plugged

Brazoria County · Manvel (FB-III Oligocene Seg A) field  · Vertical

Belcher W. T. -A- #42 (API 42-039-30583) is a plugged well in Brazoria County, plugged September 7, 1999, last operated by Denbury Onshore LLC.

The RRC has issued one drilling permit, issued December 31, 1986, permitted to 6,200 ft.

It was permitted by Texaco Inc. and has since transferred to Denbury Onshore LLC on the wellbore schedule.

Its lease has reported 153K barrels of oil and 299K mcf of gas since January 1993, last reporting in July 2026. The lease carries 7 wells, so these are lease totals, not this well alone.

Operator of record

Denbury Onshore LLC

Permitted by Texaco Inc.; the EWA schedule now lists a different operator.

Based in
Spring, TX
P-5 status
Active (A)
P-5 last filed
Dec 30, 2025
Permits on file
789
Phone
(866) 831-3235

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleDenbury Onshore LLC
Production reportsDenbury Onshore, LLCthrough Oct 2021
Latest permitTexaco Inc.Dec 31, 1986

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

6,200
total depth, ft
1
permits on file
Dec 31, 1986
last permit issued
Mar 10, 1987
completed
153K
cumulative oil, bbl
299K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Mar 10, 1987
Shut in
—
Plugged
Sep 7, 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 lease this well is completed on; they carry 7 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Belcher, W. T. -A- O-3-10796Manvel (FB-III, Oligocene Seg A)Denbury Onshore, LLC7153K299KJan 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. 1Texaco E & P Inc.Jan 1993 → Nov 1994
  2. 2North Central Oil Corp.Dec 1994 → Dec 2005
  3. 3Pogo Producing CompanyJan 2006 → Mar 2007
  4. 4Texcal Energy (GP) LLCApr 2007 → Apr 2010
  5. 5Energyquest II, LLCMay 2010 → Sep 2012
  6. 6Argent Energy (US) Holdings Inc.Oct 2012 → Apr 2015
  7. 7Denbury Onshore, LLCMay 2015 → Oct 2021

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
324811-99RecompletionTexaco Inc.Dec 29, 1986Dec 31, 1986—6,200

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-10796————

Perforations

Perforated and open-hole intervals.

FromToType
5,3065,318Perforated
—5,401Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.7576115425 S
2.8755,303——
76,1959.875425 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
00Apr 13, 1987Mar 26, 1987Yes
00Jan 12, 1984Apr 25, 1975—

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