WELL · 42-505-34624 · DISTRICT 4

Jennings Ranch AA #22

Y

Zapata County · Jennings Ranch (Lobo Cons.) field · Producing  · Vertical

Jennings Ranch AA #22 (API 42-505-34624) is a well in Zapata County operated by Hilcorp Energy Company, completed February 14, 2003 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued October 31, 2002, permitted to 13,600 ft.

It was permitted by Conoco Inc. and has since transferred to Hilcorp Energy Company on the wellbore schedule.

Completion filings report 2 formation tops, including Wilcox, Wills Point.

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

Operator of record

Hilcorp Energy Company

Permitted by Conoco Inc.; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Mar 26, 2026 · 3,454 permits on file · (713) 209-2411

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHilcorp Energy Company
Production reportsHilcorp Energy Companythrough Apr 2026
Latest permitConoco Inc.Oct 31, 2002

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

13,600
total depth, ft
1
permits on file
Oct 31, 2002
last permit issued
Feb 14, 2003
completed
0
cumulative oil, bbl
2.61M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 2003 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Feb 14, 2003
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
Jennings Ranch AA G-4-193833Jennings Ranch (Lobo Cons.)Hilcorp Energy Company102.61MFeb 2003 – Jul 2026

Gas, mcf lease total

Last 12 months 33,805 · prior 12 40,256(-16%)

02K4K6K202420252026

Chain of custody

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

  1. 1Conocophillips CompanyFeb 2003 → Dec 2015
  2. 2Hilcorp Energy CompanyJan 2016 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
525116-99DrillConoco Inc.Oct 31, 2002Oct 31, 2002Dec 25, 200213,600

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-193833————

Formation tops

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

FormationMD ftSubsea
WilcoxBASE LOWER WILCOX11,410-10,982
Wills Point12,790-12,362

Perforations

Perforated and open-hole intervals.

FromToType
11,43411,446Perforated
11,70411,908Perforated
12,43412,670Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62586612.25304 S
78,8748.75205 S
4.512,9786.25376 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
00May 5, 2003Mar 26, 2003Yes
00Apr 14, 2003——

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