WELL · 42-131-37185 · DISTRICT 4

Hernandez #2

Plugged

Duval County  · Vertical

Hernandez #2 (API 42-131-37185) is a plugged well in Duval County, plugged January 29, 1989, last operated by Price Drilling & Exploration CO..

The RRC has issued 2 drilling permits (amended once) between 1989 and 1992, permitted to 8,000 ft.

Completion filings report 3 formation tops, including Catahoula, Frio, Jackson.

Its 2 leases have reported 90.3K barrels of oil and 212K mcf of gas since January 1993, last reporting in July 2026. The leases carry 4 wells, so these are lease totals, not this well alone.

Operator of record

Price Drilling & Exploration Co.

Benavides, TX · P-5 Y, filed Jun 7, 2013 · 56 permits on file · (361) 701-3551

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsCimarron Engineering, LLCthrough Apr 2026
Latest permitPrice Drilling & Exploration Co.Oct 20, 1992
8,000
total depth, ft
3
permits on file
Oct 20, 1992
last permit issued
—
completed
90.3K
cumulative oil, bbl
212K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
Jan 29, 1989

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 2 leases this well is completed on; they carry 4 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Hernandez O-4-13332Orcones (Frio-Vksbg Cons.)L.T.D. Explorations Inc.225.1K88.3KJan 2006 – Jul 2026
Hernandez O-4-7491Orcones (5200-Oil)Price Drilling & Exploration Co.265.2K124KJan 1993 – Apr 2006

Oil, barrels lease total

Last 12 months 787 · prior 12 665(+18%)

050100202420252026

Chain of custody

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

  1. 1Price Drilling & Exploration Co.Jan 1993 → Jul 2013
  2. 2Cimarron Engineering Corp.Aug 2013 → Nov 2014
  3. 3Cimarron Engineering, LLCDec 2014 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
404280-98ReenterPrice Drilling & Exploration Co.Dec 4, 1992Oct 20, 1992—7,810
404280-99ReenterPrice Drilling & Exploration Co.Oct 5, 1992Oct 20, 1992Sep 18, 19927,810
354986-99DrillForney & McCombsJan 9, 1989Jan 11, 1989—8,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-4-7491————
—— O-4-13332————

Formation tops

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

FormationMD ftSubsea
Catahoula1300
Frio3,000-2,699
Jackson5,200-4,899

Perforations

Perforated and open-hole intervals.

FromToType
5,2225,228Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.751,13914.75301 S
7.6256,3229.875490 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
00Feb 7, 2006Oct 12, 1992—
00Jan 25, 1993Oct 12, 1992—
00Dec 23, 1992——

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