WELL · 42-465-30826 · DISTRICT 1

Altizer 56 #2

Y

Val Verde County · Altizer (Canyon Lower) field · Producing  · Vertical

Altizer 56 #2 (API 42-465-30826) is a well in Val Verde County operated by Patno Oil & Gas Company, completed April 18, 2008 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued February 22, 2008, permitted to 14,750 ft.

It was permitted by Hughes, Dan A. Company, L.P. and has since transferred to Patno Oil & Gas Company on the wellbore schedule.

Completion filings report one formation top, including Perm/Penn.

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

Operator of record

Patno Oil & Gas Company

Permitted by Hughes, Dan A. Company, L.P.; the EWA schedule now lists a different operator.

Zapata, TX · P-5 Y, filed Apr 4, 2026 · (956) 849-5305

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePatno Oil & Gas Company
Production reportsPatno Oil & Gas Companythrough Jan 2017
Latest permitHughes, Dan A. Company, L.P.Feb 22, 2008

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

14,750
total depth, ft
1
permits on file
Feb 22, 2008
last permit issued
Apr 18, 2008
completed
0
cumulative oil, bbl
89.9K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2008 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 18, 2008
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Delinquent

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
Altizer "56" G-1-241706Altizer (Canyon Lower)Patno Oil & Gas Company1089.9KApr 2008 – Jul 2026

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. 1Hughes, Dan A. Company, L.P.Apr 2008 → Jun 2010
  2. 2Baker ResourcesJul 2010 → Jan 2012
  3. 3McGuffin, Joe Jr.Feb 2012 → Nov 2013
  4. 4Patno Oil & Gas CompanyApr 2015 → Jan 2017

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
655275-99DrillHughes, Dan A. Company, L.P.Feb 13, 2008Feb 22, 2008Mar 3, 200814,750

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-1-241706————

Formation tops

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

FormationMD ftSubsea
Perm/Penn2,505-406

Perforations

Perforated and open-hole intervals.

FromToType
13,36213,378Perforated
13,40813,414Perforated
13,44013,462Perforated
13,47813,484Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6252,52412.25830 S
4.513,5558.875700 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 18, 2008May 22, 2008Yes
00Nov 4, 2008——

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