WELL · 42-427-00403 · DISTRICT 4

Villarreal #22

Plugged

Starr County · Kelsey (Frio Consol.) field  · Vertical

Villarreal #22 (API 42-427-00403) is a plugged well in Starr County, plugged October 11, 2011, last operated by Wagner Oil Company.

The RRC has issued one drilling permit, issued April 19, 1988, permitted to 6,480 ft.

It was permitted by Cabot Petroleum Corporation and has since transferred to Wagner Oil Company on the wellbore schedule.

Completion filings report one formation top, including Frio.

Operator of record

Wagner Oil Company

Permitted by Cabot Petroleum Corporation; the EWA schedule now lists a different operator.

Fort Worth, TX · P-5 Y, filed Sep 4, 2025 · 278 permits on file · (800) 457-5332

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleWagner Oil Company
Production reportsEnergy Development Corp.through Oct 1995
Latest permitCabot Petroleum CorporationApr 19, 1988

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

6,480
total depth, ft
1
permits on file
Apr 19, 1988
last permit issued
May 11, 1988
completed
0
cumulative oil, bbl
3.1K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Oct 2011

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
May 11, 1988
Shut in
—
Plugged
Oct 11, 2011

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
Villarreal G-4-127860Kelsey (Frio Consol.)Wagner Oil Company103.1KJan 1993 – Oct 2011

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. 1Energy Development Corp.Apr 1995 → Oct 1995

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
345349-99RecompletionCabot Petroleum CorporationApr 18, 1988Apr 19, 1988—6,480

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-127860————

Formation tops

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

FormationMD ftSubsea
FrioMIDDLE FRIO3,962-3,719
FrioLOWER FRIO5,413-5,170

Perforations

Perforated and open-hole intervals.

FromToType
5,7225,730Perforated
—5,998Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,013—375 S
26,021——
5.56,494—375 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
00Oct 14, 1988Jul 11, 1988Yes
00Aug 17, 1988——
00Jan 12, 1984Nov 4, 1964—

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.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

0
bbl, last 12 reported months
0
bbl, all reported
—
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000066350H-1 InjectionPlugged Oct 24, 2011006,000–6,008

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