WELL · 42-003-31177 · DISTRICT 8

University 6-24 #1

Plugged

Andrews County · Block 6 NE (Silurian) field  · Vertical

University 6-24 #1 (API 42-003-31177) is a plugged well in Andrews County, plugged April 10, 1996, last operated by Westland Oil Development Corp..

The RRC has issued 2 drilling permits between 1977 and 1989, permitted to 13,000 ft.

Completion filings report 6 formation tops, including San Andres, Clear Fork, Spraberry, Strawn.

Its 2 leases have reported 1.42K barrels of oil and 1.95K mcf of gas since January 1993, last reporting in May 1996.

Operator of record

Westland Oil Development Corp.

Conroe, TX · P-5 Y, filed Sep 3, 1999 · 264 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleWestland Oil Development Corp.
Production reportsWestland Oil Development Corp.through Jan 1996
Latest permitWestland Oil Development Corp.Nov 29, 1989
13,000
total depth, ft
2
permits on file
Nov 29, 1989
last permit issued
Aug 13, 1977
completed
1.42K
cumulative oil, bbl
1.95K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH May 1996

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Aug 13, 1977
Shut in
—
Plugged
Apr 10, 1996

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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
University 6-24 O-10-32424Block 6 (Strawn)Westland Oil Development Corp.11.42K1.95KJan 1993 – May 1996
— O-10-24671——000—

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. 1Westland Oil Development Corp.Jan 1993 → Jan 1996

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
366819-99RecompletionWestland Oil Development Corp.Nov 22, 1989Nov 29, 1989—11,255
3870-99DrillWestland Oil Development Corp.Jul 25, 1977Jul 25, 1977—13,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-24671————
—— O-10-32424————

Formation tops

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

FormationMD ftSubsea
San Andres4,800-1,806
Clear ForkCLEARFORK6,470-3,476
SpraberryTOP SPRABERRY8,460-5,466
Strawn10,990-7,996
Mississippian12,010-9,016
Silurian (undifferentiated)SILURIAN-DEVONIAN12,496-9,502

Perforations

Perforated and open-hole intervals.

FromToType
11,04611,057Perforated
11,07511,076Perforated
11,08211,084Perforated
11,08811,091Perforated
12,49612,512Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37530717.5350 S
9.6254,80012.25900 S
5.512,6008.751,100 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
00Dec 28, 1989Nov 29, 1989Yes
00Dec 9, 1989——
00Jan 12, 1984Sep 8, 1977—

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