WELL · 42-163-32445 · DISTRICT 1

Panther Hollow #28

Plugged

Frio County · Pearsall (Austin Chalk) field  · Horizontal

Panther Hollow #28 (API 42-163-32445) is a plugged horizontal well in Frio County, plugged March 31, 1995, last operated by Oryx Energy Company.

The RRC has issued 2 drilling permits (amended once) between 1985 and 1991, permitted to 7,000 ft.

Completion filings report 4 formation tops, including Olmos, San Miguel, Anacacho, Austin Chalk.

Its lease has reported 628K barrels of oil and 856K mcf of gas since January 1993, last reporting in June 1997. The lease carries 44 wells, so these are lease totals, not this well alone.

Operator of record

Oryx Energy Company

Dallas, TX · P-5 Y, filed Feb 5, 1999 · 1,627 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleOryx Energy Company
Production reportsOryx Energy Companythrough Nov 1996
Latest permitOryx Energy CompanyNov 6, 1991
7,000
total depth, ft
3
permits on file
Nov 6, 1991
last permit issued
Dec 18, 1991
completed
628K
cumulative oil, bbl
856K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jun 1997

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Dec 18, 1991
Shut in
—
Plugged
Mar 31, 1995

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; they carry 44 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Panther Hollow O-1-4948Pearsall (Austin Chalk)Oryx Energy Company44628K856KJan 1993 – Jun 1997

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. 1Oryx Energy CompanyJan 1993 → Nov 1996

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
393709-98RecompletionOryx Energy CompanyJun 8, 1992Nov 6, 1991Nov 30, 19916,440
393709-99RecompletionOryx Energy CompanyNov 6, 1991Nov 6, 1991—6,414
287192-99DrillPanther Hollow Ranch, LtdOct 11, 1985Oct 11, 1985—7,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-1-4948————

Formation tops

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

FormationMD ftSubsea
OlmosOLMOS A4,460-3,921
OlmosOLMOS B4,778-4,239
San Miguel5,314-4,775
Anacacho5,468-4,929
Austin Chalk5,713-5,174
San Miguel5,736-5,197
Austin ChalkBASE AUSTIN CHALK6,115-5,576
Austin Chalk6,320-5,781

Perforations

Perforated and open-hole intervals.

FromToType
6,0208,166Perforated
6,2936,740Open hole

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,37312.25544 S
5.56,2937.875593 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 16, 1992Apr 17, 1992Yes
00Oct 10, 1989Jan 22, 1986Yes
00Sep 30, 1989Jan 22, 1986Yes
00Feb 13, 1986Jan 22, 1986Yes
00Feb 7, 1986——

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