WELL · 42-495-10807 · DISTRICT 8

University Sec. 30 #2

Plugged

Winkler County · War-Wink (Delaware 5085) field  · Vertical

University Sec. 30 #2 (API 42-495-10807) is a plugged well in Winkler County, plugged November 22, 2004, last operated by Passmore Mike F..

The RRC has issued one drilling permit, issued July 8, 1982, permitted to 5,500 ft.

It was permitted by MR Oil Company and has since transferred to Passmore Mike F. on the wellbore schedule.

Completion filings report 3 formation tops, including Rustler, Salado, Delaware.

Operator of record

Passmore Mike F.

Permitted by Mr Oil Company; the EWA schedule now lists a different operator.

Monahans, TX · P-5 Y, filed Mar 3, 2006

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePassmore Mike F.
Production reportsnone
Latest permitMr Oil CompanyJul 8, 1982

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

5,500
total depth, ft
1
permits on file
Jul 8, 1982
last permit issued
Sep 15, 1982
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Mar 2008

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Sep 15, 1982
Shut in
—
Plugged
Nov 22, 2004

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
University Sec. 30 O-10-27711War-Wink (Delaware 5085)Passmore, Mike F.100Jan 1993 – Mar 2008

No volumes reported on these leases in the last three years.

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
166376-99OtherMr Oil CompanyJul 8, 1982Jul 8, 1982Aug 24, 19825,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-27711————

Formation tops

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

FormationMD ftSubsea
Rustler7102,035
Salado1,0301,715
DelawareDELAWARE LIME4,950-2,205
DelawareDELAWARE SAND5,093-2,348

Perforations

Perforated and open-hole intervals.

FromToType
5,0935,099Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
71,0859.875—
71,085——
2.3755,043——
4.55,1746.25300 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
00Nov 13, 1986Oct 21, 1986—
00Nov 4, 1986Oct 13, 1982—
00Jan 12, 1984Oct 13, 1982—

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.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

342K
bbl, last 12 reported months
1.92M
bbl, all reported
Aug 2001
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000053049H-1 InjectionPlugged Jan 6, 20055,0001,2005,093–5,099

MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS

Last 12 months 342,099 · prior 12 243,204(+41%)

020K40K20002001

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