TEXAS · WELLS · ZAPATA COUNTY · LAUREL, O. M. ESTATE LEASE · API 42-505-35609 · DISTRICT 04

Laurel O. M. Estate #12

Y

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

Fields on the latest permit · any of 4
Charco (9200) · Charco (9400) · 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.

Laurel O. M. Estate #12 (API 42-505-35609) is a well in Zapata County operated by Hilcorp Energy Company, completed July 22, 2006 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued June 7, 2006, permitted to 12,400 ft.

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

Completion filings report 4 formation tops, including Perdido Uncon, Perdido Unconformity, Lobo Unconf, Lobo Unconformity.

Its lease has reported 158 barrels of oil and 888K mcf of gas since July 2006, last reporting volume in April 2026.

Operator of record

Hilcorp Energy Company

Permitted by Chesapeake Operating, Inc.; the EWA schedule now lists a different operator.

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

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHilcorp Energy Company
Production reportsHilcorp Energy Companythrough Apr 2026
Latest permitChesapeake Operating, Inc.Jun 7, 2006

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

12,400
total depth, ft
1
permits on file
Jun 7, 2006
last permit issued
Jul 22, 2006
completed
158
cumulative oil, bbl
888K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 2006 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 22, 2006
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active (A)

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
Laurel, O. M. Estate G-4-222523Jennings Ranch (Lobo Cons.)Hilcorp Energy Company1158888KJul 2006 – Apr 2026

Gas, mcf lease total

Last 12 months 9,710 · prior 12 7,570(+28%)

05001K1.5K202420252026

Chain of custody

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

  1. 1Chesapeake Operating, Inc.Jul 2006 → Jul 2014
  2. 2Hilcorp Energy CompanySep 2014 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
620585-99DrillChesapeake Operating, Inc.Jun 7, 2006Jun 7, 2006Jun 13, 200615,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Jul 22, 2006Laurel O. M. Estate G-4-222523Jennings Ranch (Lobo Cons.)Hilcorp Energy CompanyProducing12,400

Formation tops

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

FormationMD ftSubsea
Perdido Uncon8,740-8,279
Perdido Unconformity8,740-8,279
Lobo Unconf10,950-10,489
Lobo Unconformity10,950-10,489

Perforations

Perforated and open-hole intervals.

FromToType
11,30412,226Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,04812.25342 S
78,3058.75292 S
4.512,3846.25410 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
00Jul 6, 2007Jun 25, 2007—
00Mar 22, 2007Sep 28, 2006Yes
00Dec 4, 2006——

Well logs

2 logs loaded from the RRC's log index, the latest received Jul 27, 2007. Density, Neutron, Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.

Open the RRC's log search for this well ↗
Logas describedFiles Intervalft, as filedDatereceivedSizeMB
Combination: Resistivity/Neutron Density PorosityHIGH RESOLUTION INDUCTION DUAL SPACED NEUTRON SPECTRAL DENSITYSpans Perdido Uncon, Perdido Unconformity, Lobo Unconformity, Lobo UnconfTIFF1,500 to 12,390Jul 27, 2007run Jul 3, 2006—
Combination: Resistivity/Neutron Density PorosityHIGH RESOLUTION INDUCTION DUAL SPACED NEUTRON SPECTRAL DENSITYSpans Perdido Uncon, Perdido Unconformity, Lobo Unconformity, Lobo UnconfTIFF1,500 to 12,390Apr 30, 2007run Jul 3, 2002—

"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.

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