WELL · 42-507-31183 · DISTRICT 1

Pryor Ranch #2

N

Zavala County · Ike Pryor (Olmos 2300) field  · Vertical

Pryor Ranch #2 (API 42-507-31183) is a well in Zavala County operated by Winn Exploration/Dulce Company, completed February 23, 1983.

The RRC has issued 2 drilling permits between 1979 and 1986, permitted to 3,500 ft.

Completion filings report 5 formation tops, including Escondido, Olmos, Del Monte, Bracero.

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

Operator of record

Winn Exploration/Dulce Company

Eagle Pass, TX · P-5 Y, filed Oct 9, 1991 · 293 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleWinn Exploration/Dulce Company
Production reportsMcDay Energy Corp.through Apr 2026
Latest permitWinn Exploration/Dulce CompanyJun 26, 1986

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

3,500
total depth, ft
2
permits on file
Jun 26, 1986
last permit issued
Feb 23, 1983
completed
0
cumulative oil, bbl
131K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Feb 23, 1983
Shut in
—
Plugged
—

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
Pryor Ranch G-1-90281Ike Pryor (Bracero)McDay Energy Corp.10131KJan 1993 – Jul 2026
Pryor Ranch G-1-121757Winn-Dulce (Escondido)McDay Energy Corp.100Jan 1993 – Jul 2026

Gas, mcf lease total

Last 12 months 216 · prior 12 269(-20%)

02040202420252026

Chain of custody

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

  1. 1Winn Exploration Co., Inc.Jan 1993 → Oct 1994
  2. 2McDay Energy Corp.Nov 1994 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
303607-99RecompletionWinn Exploration/Dulce CompanyJun 25, 1986Jun 26, 1986—2,724
52514-99DrillSundown Drilling Co.Jul 10, 1979Jul 10, 1979—3,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-1-90281————
—— G-1-121757————

Formation tops

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

FormationMD ftSubsea
Escondido1,618-912
Olmos2,208-1,502
Del Monte2,630-1,924
Bracero2,673-1,967
Elaine2,725-2,019

Perforations

Perforated and open-hole intervals.

FromToType
1,9711,978Perforated
2,2962,318Perforated
2,6762,715Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62520512.25150 S
2.3752,250——
2.3752,390——
4.52,8617.625595 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
00Aug 7, 1986Jul 23, 1986Yes
00Aug 5, 1986——
00Jan 12, 1984Jul 22, 1983—
00Jan 12, 1984May 1, 1980—

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