WELL · 42-461-34940 · DISTRICT 7

University 18 #1

Plugged

Upton County · Sheep Mountain (Consolidated) field  · Vertical

University 18 #1 (API 42-461-34940) is a plugged well in Upton County, plugged January 30, 2009, last operated by Exl Petroleum LP.

The RRC has issued 2 drilling permits between 2005 and 2007, permitted to 11,000 ft.

Completion filings report 5 formation tops, including Russler, Yates, San Andres, Wolfcamp.

Its 2 leases have reported 1.05K barrels of oil and 726 mcf of gas since December 2005, last reporting in April 2015. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

EXL Petroleum LP

Midland, TX · P-5 Y, filed Jul 6, 2018 · 252 permits on file · (432) 557-5977

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleEXL Petroleum LP
Production reportsEXL Petroleum, LPthrough Dec 2007
Latest permitEXL Petroleum, LPJan 19, 2007
11,000
total depth, ft
2
permits on file
Jan 19, 2007
last permit issued
Feb 7, 2007
completed
1.05K
cumulative oil, bbl
726
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Dec 2005 THROUGH Apr 2015

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Feb 7, 2007
Shut in
—
Plugged
Jan 30, 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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
University 18 O-9-15869Spraberry (Trend Area)EXL Petroleum, LP11.05K726Dec 2005 – Apr 2015
University 18 O-9-16855Sheep Mountain (Consolidated)EXL Petroleum, LP100Feb 2007 – Mar 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. 1Williams, Clayton Energy, Inc.Dec 2005 → Dec 2006
  2. 2EXL Petroleum, LPDec 2007 → Dec 2007

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
631991-99RecompletionEXL Petroleum, LPJan 16, 2007Jan 19, 2007Jan 20, 200711,000
608530-99DrillWilliams, Clayton Energy, Inc.Oct 26, 2005Oct 28, 2005Nov 15, 200510,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-9-15869————
—— O-9-16855————

Formation tops

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

FormationMD ftSubsea
Russler1,2361,422
Yates1,956702
San Andres3,386-728
Wolfcamp7,315-4,657
PennsylvanianPENN9,078-6,420

Perforations

Perforated and open-hole intervals.

FromToType
8,1718,528Perforated
9,3219,430Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37573317.51,410 S
8.6253,746111,290 S
5.59,2127.8751,230 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
00Apr 24, 2009Oct 29, 2008Yes
00Mar 12, 2009——
00May 24, 2006Jan 18, 2006Yes
00Feb 14, 2006——

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