TEXAS · WELLS · ZAPATA COUNTY · API 42-505-34870 · DISTRICT 04

Jennings Ranch C #52

Plugged

Zapata County · Jennings Ranch (Lobo Cons.) field  · Directional · Sidetrack

Fields on the latest permit · any of 2
Charco (9900) · Jennings Ranch (Lobo Cons.)
Not one formation; the well must be completed in one of them, and no target formation is stated. The district's wildcat field is also on the permit.

Jennings Ranch C #52 (API 42-505-34870) is a plugged well in Zapata County, plugged November 18, 2019, last operated by Hilcorp Energy Company.

The RRC has issued one drilling permit (amended once), issued December 15, 2003, permitted to 13,600 ft.

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

Completion filings report 3 formation tops, including Perdido, Wilcox, Wills Point.

Its 2 leases have reported 17 barrels of oil and 91.8K mcf of gas since March 2004, with no volume in the three years through August 2026. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Hilcorp Energy Company

Permitted by Conocophillips Company; the EWA schedule now lists a different operator.

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Mar 27, 2026
Permits on file
3,460
Phone
(713) 209-2400

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHilcorp Energy Company
Production reportsHilcorp Energy Companythrough Sep 2019
Latest permitConocophillips CompanyDec 15, 2003

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
2
permits on file
Dec 15, 2003
last permit issued
Mar 2, 2004
completed
17
cumulative oil, bbl
91.8K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · MAR 2004 THROUGH SEP 2019

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Mar 2, 2004
Shut in
—
Plugged
Nov 18, 2019

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.

Wells nearby

Every well with a location on file around this well, in any state, nearest first.

Loading the map…

Open the full map →

Texas locations come from drilling permits, so most older Texas wells have none and are not listed.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH AUG 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
Jennings Ranch C G-4-201679Jennings Ranch (Lobo Cons.)Hilcorp Energy Company11791.8KMar 2004 – Sep 2019
Jennings Ranch C G-4-201680Charco (9900)Hilcorp Energy Company100Mar 2004 – —

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

Wells named Jennings Ranch C

Hilcorp Energy Company's other wells filed under this lease name in Zapata County, newest permit first. The RRC gives a gas well its own lease number, so the name is what joins the wells of a unit.

Loading the lease's wells

Chain of custody

Operator on the lease's P-4

Each operator named on the P-4 filings for this well's lease (a gas well is its own lease), from the date its filing took effect. The P-4 is filed by lease, so a date before the well was drilled is the lease's.

OperatorFromTo
Hilcorp Energy CompanyJan 1, 2016today
Conocophillips CompanyMar 2, 2004Jan 1, 2016

Reporting production

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

  1. 1Conocophillips CompanyMar 2004 → Dec 2015
  2. 2Hilcorp Energy CompanyJan 2016 → Sep 2019

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
538661-98Drill · sidetrackConocophillips CompanyJan 14, 2004Dec 15, 2003Dec 16, 200313,600
538661-99DrillConocophillips CompanyNov 17, 2003Dec 15, 2003—13,600

Completions

CompletedLeaseFieldOperatorStatusDepth
Mar 2, 2004Jennings Ranch C G-4-201679Jennings Ranch (Lobo Cons.)Hilcorp Energy CompanyPlugged—
—Jennings Ranch C G-4-201680Charco (9900)Hilcorp Energy CompanyPlugged—

Formation tops

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

FormationMD ftSubsea
Perdido8,885-8,489
WilcoxBASE LOWER WILCOX11,485-11,089
Wills Point12,295-11,899

Perforations

Perforated and open-hole intervals.

FromToType
10,19010,202Perforated
11,83411,972Perforated
12,11612,248Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62586312.25305 S
78,8458.75150 S
4.512,5006.25392 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Aug 4, 2004May 21, 2004Yes
00Jun 24, 2004——

Well logs

The RRC's map lists this well among those with logs online. Its monthly inventories loaded here, which start in July 2006, list none for it, so none are itemized.

Open the RRC's log search for this well ↗

Find logs withinmiles of this well:List →Map →

Search the well logs loaded into Petrora →

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.

The logs loaded for this well are under Well logs, with the RRC's log search for it.

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