WELL · 42-003-36297 · DISTRICT 8

McWhorter a 105 #1

Plugged

Andrews County  · Vertical

Mcwhorter A 105 #1 (API 42-003-36297) is a plugged well in Andrews County, plugged August 22, 2011, last operated by Saber Oil & Gas Ventures, LLC.

The RRC has issued 3 drilling permits between 1988 and 2010, permitted to 11,700 ft.

Completion filings report 9 formation tops, including Yates, San Andres, Glorieta, Clear Fork.

Its lease has reported 64.9K barrels of oil and 21 mcf of gas since January 1993, last reporting in March 1999.

Operator of record

Saber Oil & Gas Ventures, LLC

Based in
Midland, TX
P-5 status
Inactive (I)
P-5 last filed
Jun 1, 2017
Permits on file
17
Phone
(432) 685-0169

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsUniversal Resources Corp.through May 1998
Latest permitSaber Oil & Gas Ventures, LLCOct 5, 2010
11,700
total depth, ft
3
permits on file
Oct 5, 2010
last permit issued
—
completed
64.9K
cumulative oil, bbl
21
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Mar 1999

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
Aug 22, 2011

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
McWhorter -A- O-10-32270Mid-Max (Devonian)Smith Pipe of Abilene164.9K21Jan 1993 – Mar 1999

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. 1Dallas Production, Inc.Jan 1993 → Sep 1996
  2. 2Universal Resources Corp.Oct 1996 → May 1998

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
703141-99ReenterSaber Oil & Gas Ventures, LLCOct 1, 2010Oct 5, 2010—8,538
639853-99ReenterBrowning Oil Company, Inc.May 30, 2007Jun 7, 2007Jun 13, 20074,000
354478-99DrillMaxus Exploration CompanyDec 20, 1988Dec 21, 1988Feb 11, 198911,700

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-32270————

Formation tops

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

FormationMD ftSubsea
Yates2,884506
San Andres4,360-970
GlorietaGLORIETTA5,515-2,125
Clear ForkUPPER CLEARFORK6,090-2,700
Tubb6,648-3,258
Clear ForkLOWER CLEARFORK6,721-3,331
Wichita-AlbanyWICHITA ALBANY7,400-4,010
Wolfcamp7,970-4,580
Woodford8,322-4,932
Devonian8,432-5,042

Perforations

Perforated and open-hole intervals.

FromToType
8,4458,459Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37535717.5375 S
8.6254,448112,775 S
5.59,0627.875385 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 12, 1989Jun 19, 1989Yes
00Jun 22, 1989Jun 5, 1989Yes
00Jun 15, 1989——

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) and the University Lands library. 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/00336297, documented in the API reference.