WELL · 42-323-32938 · DISTRICT 1

Briscoe-Saner #233

Y

Maverick County · M.F. Jake Lawless (Edwards Lime) field · Shut IN  · Directional

Briscoe-Saner #233 (API 42-323-32938) is a well in Maverick County operated by Patterson Energy Corporation, completed February 15, 2007 and listed as shut in on the RRC schedule.

The RRC has issued one drilling permit (amended twice), issued January 18, 2007, permitted to 5,900 ft.

It was permitted by Exploration Company, The and has since transferred to Patterson Energy Corporation on the wellbore schedule.

Completion filings report 6 formation tops, including Buda, Del Rio, Georgetown, McKnight.

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

Operator of record

Patterson Energy Corporation

Permitted by Exploration Company, The; the EWA schedule now lists a different operator.

Dallas, TX · P-5 Y, filed Jun 4, 2026 · 23 permits on file · (806) 790-5547

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePatterson Energy Corporation
Production reportsnone
Latest permitExploration Company, TheJan 18, 2007

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

5,900
total depth, ft
3
permits on file
Jan 18, 2007
last permit issued
Feb 15, 2007
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2007 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Feb 15, 2007
Shut in
—
Plugged
—

Operator's P-5 on the schedule: X

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
Briscoe-Saner O-1-14807M.F. Jake Lawless (Edwards Lime)Patterson Energy Corporation100Apr 2007 – Jul 2026

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

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
631909-97DrillExploration Company, TheMar 21, 2007Jan 18, 2007Jan 15, 20075,900
631909-98DrillExploration Company, TheFeb 7, 2007Jan 18, 2007Jan 15, 20075,900
631909-99DrillExploration Company, TheJan 12, 2007Jan 18, 2007Jan 15, 20075,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-1-14807————

Formation tops

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

FormationMD ftSubsea
Buda2,320-1,430
Del Rio2,450-1,560
Georgetown2,690-1,800
McKnight3,264-2,374
Edwards3,509-2,619
Glen Rose3,791-2,901

Perforations

Perforated and open-hole intervals.

FromToType
3,5823,590Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62524612.25200 S
5.55,2227.875615 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
00Jun 13, 2007Apr 17, 2007Yes
00May 31, 2007——

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