WELL · 42-441-34351 · DISTRICT 7

McAnich-Beene Unit #1

Y

Taylor County · Taylor County Regular field · NO Production  · Vertical

Mcanich-Beene Unit #1 (API 42-441-34351) is a well in Taylor County operated by Beasley Well Service Inc., completed January 25, 2012 and listed as no production on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued October 14, 2011, permitted to 2,900 ft.

It was permitted by Winco Oil Inc. and has since transferred to Beasley Well Service Inc. on the wellbore schedule.

Completion filings report one formation top, including Hope Lime.

Its lease has reported 7.14K barrels of oil since January 2012, last reporting in July 2026.

Operator of record

Beasley Well Service Inc.

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

Tuscola, TX · P-5 Y, filed Dec 4, 2025 · (325) 439-1232

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBeasley Well Service Inc.
Production reportsBeasley Well Service Inc.through Jul 2024
Latest permitWinco Oil Inc.Oct 14, 2011

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

2,900
total depth, ft
2
permits on file
Oct 14, 2011
last permit issued
Jan 25, 2012
completed
7.14K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 2012 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jan 25, 2012
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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
McAnich-Beene Unit O-8-31001Taylor County RegularBeasley Well Service Inc.17.14K0Jan 2012 – Jul 2026

Oil, barrels lease total

Last 12 months 0 · prior 12 17(-100%)

02040202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Winco Oil Inc.Jan 2012 → Mar 2021
  2. 2DJM Beasley Well ServiceApr 2021 → Feb 2024
  3. 3Beasley Well Service Inc.Mar 2024 → Jul 2024

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
725907-98DrillWinco Oil Inc.Apr 25, 2012Oct 14, 2011Dec 27, 20112,900
725907-99DrillWinco Oil Inc.Oct 7, 2011Oct 14, 2011—2,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-31001————

Formation tops

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

FormationMD ftSubsea
Hope Lime2,492-657

Perforations

Perforated and open-hole intervals.

FromToType
2,4922,496Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62510112.2580 S
4.52,7917.875195 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
00Sep 14, 2012May 30, 2012Yes

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