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

Asche #98

Y

Zapata County · Charco (9900) field · Producing  · Vertical

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

Asche #98 (API 42-505-35227) is a well in Zapata County operated by Hilcorp Energy Company, completed July 12, 2005 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued February 24, 2005, permitted to 10,100 ft.

It was permitted by Houston Exploration Company, The and has since transferred to Hilcorp Energy Company on the wellbore schedule.

Completion filings report 3 formation tops, including Perdido Unconformity, Top Perdido A, Top Perdido B.

Its 2 leases have reported 300 barrels of oil and 418K mcf of gas since May 2005, last reporting volume in April 2026. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Hilcorp Energy Company

Permitted by Houston Exploration Company, The; 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 permitHouston Exploration Company, TheFeb 24, 2005

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

10,100
total depth, ft
1
permits on file
Feb 24, 2005
last permit issued
Jul 12, 2005
completed
300
cumulative oil, bbl
418K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · May 2005 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 12, 2005
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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Asche G-4-211337Charco (9900)Hilcorp Energy Company1300418KMay 2005 – Apr 2026
Asche G-4-211338Charco (9200)Hilcorp Energy Company100May 2005 – —

Gas, mcf lease total

Last 12 months 2,365 · prior 12 2,943(-20%)

0200400202420252026

Chain of custody

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

  1. 1Houston Exploration Company, TheMay 2005 → Jun 2007
  2. 2Forest Oil CorporationJul 2007 → Dec 2012
  3. 3Hilcorp Energy CompanyJan 2013 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
558125-99DrillHouston Exploration Company, TheFeb 23, 2005Feb 24, 2005May 2, 200510,600

Completions

CompletedLeaseFieldOperatorStatusDepth
Jul 12, 2005Asche G-4-211337Charco (9900)Hilcorp Energy CompanyProducing10,100
May 27, 2005Asche G-4-211338Charco (9200)Hilcorp Energy CompanySWR-10-Well · shut in May 1, 200510,100

Formation tops

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

FormationMD ftSubsea
Perdido Unconformity9,132-8,708
Top Perdido A9,181-8,757
Top Perdido B9,719-9,295

Perforations

Perforated and open-hole intervals.

FromToType
9,1849,188Perforated
9,2909,294Perforated
9,3289,332Perforated
9,3669,374Perforated
9,7229,726Perforated
9,7309,738Perforated
9,7409,747Perforated
9,7899,793Perforated
9,7969,806Perforated
9,8109,814Perforated
9,8249,836Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62575012.25350 S
78,3018.75300 S
3.510,0926.25350 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
00Dec 13, 2005Jul 29, 2005—
00Dec 9, 2005Jul 29, 2005Yes
00Oct 10, 2005——

Well logs

1 log loaded from the RRC's log index, the latest received Sep 15, 2008. 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
RESISTIVITYSpans Perdido Unconformity, Top Perdido A, Top Perdido BTIFF8,296 to 10,099Sep 15, 2008run May 17, 20050.37

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