TEXAS · WELLS · ZAPATA COUNTY · VOLPE LEASE · API 42-505-35819 · DISTRICT 04

Volpe #4

Plugged

Zapata County · Wildcat field  · Vertical

Volpe #4 (API 42-505-35819) is a plugged well in Zapata County, plugged June 8, 2007, last operated by Chesapeake Operating Inc..

The RRC has issued one drilling permit, issued February 22, 2007, permitted to 15,000 ft.

Operator of record

Chesapeake Operating Inc.

Based in
Oklahoma City, OK
P-5 status
Delinquent (D)
P-5 last filed
Dec 10, 2024
Permits on file
13,061
Phone
(405) 935-3100

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleChesapeake Operating Inc.
Production reportsnone
Latest permitChesapeake Operating, Inc.Feb 22, 2007
15,000
total depth, ft
1
permits on file
Feb 22, 2007
last permit issued
Mar 31, 2007
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 2007 THROUGH —

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Mar 31, 2007
Shut in
—
Plugged
Jun 8, 2007

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
Volpe O-4-13430WildcatChesapeake Operating, Inc.100Mar 2007 – —

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

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
633688-99DrillChesapeake Operating, Inc.Feb 16, 2007Feb 22, 2007Feb 27, 200715,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Mar 31, 2007Volpe O-4-13430WildcatChesapeake Operating Inc.Plugged—

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,70712.25542 S
78,8688.75337 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
00Jun 12, 2007Jun 6, 2007—
00Jun 8, 2007Jun 1, 2007Yes
00Jun 6, 2007——

Well logs

1 log loaded from the RRC's log index, the latest received May 4, 2010. 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 POROSITYTIFF8,866 to 10,970May 4, 2010run Mar 28, 20070.55

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