TEXAS · WELLS · ZAPATA COUNTY · URIBE LEASE · API 42-505-35772 · DISTRICT 04

Uribe #1

Plugged

Zapata County · Wildcat field  · Vertical

Uribe #1 (API 42-505-35772) is a plugged well in Zapata County, plugged July 23, 2009, last operated by Eagle Oil & Gas CO..

The RRC has issued one drilling permit (amended once), issued December 22, 2006, permitted to 10,300 ft.

Operator of record

Eagle Oil & Gas Co.

Based in
Dallas, TX
P-5 status
Active – Extension (X)
P-5 last filed
Apr 22, 2026
Permits on file
347
Phone
(214) 369-1545

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleEagle Oil & Gas Co.
Production reportsnone
Latest permitEagle Oil & Gas Co.Dec 22, 2006
10,300
total depth, ft
2
permits on file
Dec 22, 2006
last permit issued
May 6, 2007
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · May 2007 THROUGH —

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
May 6, 2007
Shut in
—
Plugged
Jul 23, 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 lease this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Uribe G-4-228446WildcatEagle Oil & Gas Co.100May 2007 – —

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

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
630969-98DrillEagle Oil & Gas Co.Apr 4, 2007Dec 22, 2006Apr 15, 200710,300
630969-99DrillEagle Oil & Gas Co.Dec 21, 2006Dec 22, 2006—10,300

Completions

CompletedLeaseFieldOperatorStatusDepth
May 6, 2007Uribe G-4-228446WildcatEagle Oil & Gas Co.Plugged—

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,02012.25450 S
76,6688.751,200 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 30, 2007Jul 19, 2007Yes
00Jul 26, 2007——

Well logs

2 logs loaded from the RRC's log index, the latest received May 27, 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 POROSITYTIFF6,672 to 11,004May 27, 2010run May 2, 20072.87
COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF1,022 to 6,666May 27, 2010run Apr 24, 20073.44

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