TEXAS · WELLS · MAVERICK COUNTY · API 42-323-32605 · DISTRICT 01

Mancha #5

Plugged

Maverick County · El Indio N.(olmos) field  · Vertical

Mancha #5 (API 42-323-32605) is a plugged well in Maverick County, plugged March 5, 2009, last operated by Encana Oil & Gas(USA) Inc..

The RRC has issued 2 drilling permits between 2002 and 2004, permitted to 1,650 ft.

It was permitted by Hollimon Oil Corporation and has since transferred to Encana Oil & Gas(USA) Inc. on the wellbore schedule.

Operator of record

Encana Oil & Gas(usa) Inc.

Permitted by Hollimon Oil Corporation; the EWA schedule now lists a different operator.

Based in
Denver, CO
P-5 status
Inactive (I)
P-5 last filed
Dec 19, 2019
Permits on file
3,078
Phone
(303) 623-2300

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleEncana Oil & Gas(usa) Inc.
Production reportsEncana Oil & Gas(usa) Inc.through Oct 2005
Latest permitHollimon Oil CorporationJul 21, 2004

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

1,650
total depth, ft
2
permits on file
Jul 21, 2004
last permit issued
Nov 17, 2003
completed
0
cumulative oil, bbl
10.4K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2002 THROUGH Mar 2009

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Nov 17, 2003
Shut in
—
Plugged
Mar 5, 2009

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
Mancha G-1-205662El Indio, N.(olmos)Encana Oil & Gas(usa) Inc.1010.4KNov 2003 – Mar 2009
Mancha G-1-195826WildcatHollimon Oil Corporation100Apr 2002 – Nov 2003

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

Chain of custody

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

  1. 1Hollimon Oil CorporationMar 2004 → Jun 2004
  2. 2Exploration Company, TheDec 2004 → Aug 2005
  3. 3Encana Oil & Gas(usa) Inc.Sep 2005 → Oct 2005

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
547571-99RecompletionHollimon Oil CorporationJun 28, 2004Jul 21, 2004—1,650
518693-99DrillHollimon Oil CorporationMar 29, 2002Mar 29, 2002Apr 1, 20021,650

Completions

CompletedLeaseFieldOperatorStatusDepth
Nov 17, 2003Mancha G-1-205662El Indio N.(olmos)Encana Oil & Gas(usa) Inc.Plugged—
—Mancha G-1-195826WildcatHollimon Oil CorporationPlugged—

Perforations

Perforated and open-hole intervals.

FromToType
957962Perforated
1,1951,250Open hole

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62512512.2585 S
71,1288.75300 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 3, 2005Apr 5, 2004Yes
00Jan 27, 2005——
00Feb 13, 2004Apr 23, 2003Yes
00Aug 7, 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/32332605, documented in the API reference.