WELL · 42-211-34795 · DISTRICT 10

Washita River 39 #2

Y

Hemphill County · Begert (10 200) field · Producing  · Vertical

Washita River 39 #2 (API 42-211-34795) is a well in Hemphill County operated by Bce-Mach II LLC, completed January 26, 2011 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued October 20, 2010, permitted to 13,840 ft.

It was permitted by Laredo Petroleum, Inc. and has since transferred to Bce-Mach II LLC on the wellbore schedule.

Completion filings report 2 formation tops, including Granite Wash, Atoka.

No lease production has been reported under this well’s leases.

Operator of record

Bce-Mach II LLC

Permitted by Laredo Petroleum, Inc.; the EWA schedule now lists a different operator.

Oklahoma City, OK · P-5 Y, filed Jun 4, 2026 · (833) 831-2164

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBce-Mach II LLC
Production reportsBce-Mach II LLCthrough Apr 2026
Latest permitLaredo Petroleum, Inc.Oct 20, 2010

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

13,840
total depth, ft
1
permits on file
Oct 20, 2010
last permit issued
Jan 26, 2011
completed
0
cumulative oil, bbl
619K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 2011 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jan 26, 2011
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
Washita River 39 G-14-265087Begert (10,200)Bce-Mach II LLC10619KJan 2011 – Jul 2026

Gas, mcf lease total

Last 12 months 14,535 · prior 12 15,684(-7%)

01K2K202420252026

Chain of custody

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

  1. 1Laredo Petroleum, Inc.Jan 2011 → Jul 2013
  2. 2Enervest Operating, L.L.C.Aug 2013 → Aug 2019
  3. 3Bce-Mach II LLCSep 2019 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
703785-99DrillLaredo Petroleum, Inc.Oct 13, 2010Oct 20, 2010Dec 11, 201013,840

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-14-265087————

Formation tops

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

FormationMD ftSubsea
Granite Wash11,315-8,957
AtokaATOKA WASH12,918-10,560

Perforations

Perforated and open-hole intervals.

FromToType
11,37411,836Perforated
11,88012,255Perforated
12,44812,987Perforated
13,08313,578Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,62512.25820 S
5.513,7307.875673 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 30, 2012Sep 14, 2011Yes

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