WELL · 42-077-34449 · DISTRICT 9

Browning #2

Plugged

Clay County · Vera (Strawn) field  · Vertical

Browning #2 (API 42-077-34449) is a plugged well in Clay County, plugged March 4, 2009, last operated by Wolsey Well Service L.P..

The RRC has issued one drilling permit, issued October 3, 1991, permitted to 4,000 ft.

It was permitted by Corpening, Joe F. and has since transferred to Wolsey Well Service L.P. on the wellbore schedule.

Completion filings report 2 formation tops, including Palo Pinto, Strawn.

Its lease has reported 11.2K barrels of oil and 21 mcf of gas since January 1993, last reporting in July 2009. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

Wolsey Well Service L.P.

Permitted by Corpening, Joe F.; the EWA schedule now lists a different operator.

Bowie, TX · P-5 Y, filed Feb 6, 2015 · 1 permits on file · (940) 872-4007

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleWolsey Well Service L.P.
Production reportsWolsey Well Service, L.P.through Nov 2008
Latest permitCorpening, Joe F.Oct 3, 1991

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

4,000
total depth, ft
1
permits on file
Oct 3, 1991
last permit issued
Oct 15, 1991
completed
11.2K
cumulative oil, bbl
21
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2009

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Oct 15, 1991
Shut in
—
Plugged
Mar 4, 2009

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 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Browning O-13-27775Vera (Strawn)Wolsey Well Service, L.P.211.2K21Jan 1993 – Jul 2009

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. 1Corpening, Joe F.Jan 1993 → Jun 1993
  2. 2Continental Export CorporationJul 1993 → Aug 2002
  3. 3Wolsey Well Service, Inc.Sep 2002 → Jul 2006
  4. 4Wolsey Well Service, L.P.Aug 2006 → Nov 2008

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
392434-99DrillCorpening, Joe F.Oct 2, 1991Oct 3, 1991Oct 9, 19914,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-27775————

Formation tops

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

FormationMD ftSubsea
Palo Pinto1964
Strawn2,000-1,035

Perforations

Perforated and open-hole intervals.

FromToType
3,6723,676Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62525111—
5.53,69829778 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 27, 1991Nov 18, 1991Yes
00Nov 22, 1991——

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