WELL · 42-347-31663 · DISTRICT 6

Blount, L. F. #A 2

Plugged

Nacogdoches County  · Vertical

Blount, L. F. #A 2 (API 42-347-31663) is a plugged well in Nacogdoches County, plugged May 14, 1997, last operated by Brg Petroleum Corporation.

The RRC has issued 2 drilling permits in 1999, permitted to 9,300 ft.

Completion filings report 7 formation tops, including Massive Anhydrite (marker), Rodessa, James Lime, Pettit.

Operator of record

BRG Petroleum Corporation

Tulsa, OK · P-5 Y, filed May 8, 2009 · 92 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsWeatherly Oil & Gas, LLCthrough Sep 2019
Latest permitBRG Petroleum CorporationFeb 22, 1999
9,300
total depth, ft
2
permits on file
Feb 22, 1999
last permit issued
—
completed
0
cumulative oil, bbl
440K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · May 1999 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
May 14, 1997

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
Blount, Lois Foster Gas Unit A G-6-173359Appleby, N. (Travis Peak)Weatherly Oil & Gas, LLC10440KMay 1999 – Jul 2026
Blount, Lois Foster Gas Unit A G-6-173361Appleby, N (Pettit)Chesapeake Operating, Inc.100May 1999 – Apr 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. 1BRG Petroleum CorporationMay 1999 → Feb 2005
  2. 2Chesapeake Operating, Inc.Mar 2005 → Oct 2014
  3. 3Chesapeake Operating, L.L.C.Nov 2014 → Dec 2014
  4. 4SND Operating, L.L.C.Jan 2015 → Sep 2017
  5. 5Weatherly Oil & Gas, LLCOct 2017 → Sep 2019

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
482684-99DrillBRG Petroleum CorporationFeb 12, 1999Feb 22, 1999May 8, 19974,203
482603-99ReenterBRG Petroleum CorporationFeb 9, 1999Feb 9, 1999Feb 15, 19999,300

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-6-173359————
—— G-6-173361————

Formation tops

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

FormationMD ftSubsea
Massive Anhydrite (marker)BASE MASSIVE ANHYDRITE6,634-6,138
Rodessa6,664-6,168
James LimeJAMES7,130-6,634
Pettit7,378-6,882
Transition Zone7,808-7,312
Transitionzone7,808-7,312
Travis Peak7,934-7,438

Perforations

Perforated and open-hole intervals.

FromToType
7,6747,775Perforated
7,9777,992Perforated
8,2688,385Perforated
8,4578,677Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,52311360 S
4.58,9507.8751,100 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
00Jul 20, 1999Jun 14, 1999Yes
00Jul 8, 1999——

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