WELL · 42-249-32538 · DISTRICT 4

Wright #1

Plugged

Jim Wells County · Falfurrias E. (Vicksburg 9100) field  · Vertical

Wright #1 (API 42-249-32538) is a plugged well in Jim Wells County, plugged April 10, 2015, last operated by Paladin Petroleum Iii L.L.C..

The RRC has issued one drilling permit, issued October 4, 2008, permitted to 11,500 ft.

It was permitted by United Resources LP and has since transferred to Paladin Petroleum Iii L.L.C. on the wellbore schedule.

Completion filings report 5 formation tops, including Frio, Nowacek, Vx Cip N Mkr., Vx Myrick.

Operator of record

Paladin Petroleum III L.L.C.

Permitted by United Resources LP; the EWA schedule now lists a different operator.

Based in
Austin, TX
P-5 status
Active – Extension (X)
P-5 last filed
Jul 20, 2026
Permits on file
42
Phone
(512) 327-6122

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePaladin Petroleum III L.L.C.
Production reportsPaladin Petroleum III, L.L.C.through Feb 2013
Latest permitUnited Resources LPOct 4, 2008

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

11,500
total depth, ft
1
permits on file
Oct 4, 2008
last permit issued
Jan 5, 2009
completed
0
cumulative oil, bbl
1.06M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 2009 THROUGH Mar 2017

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 5, 2009
Shut in
—
Plugged
Apr 10, 2015

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
Wright G-4-247398Falfurrias, E. (Vicksburg 9100)Paladin Petroleum III, L.L.C.101.06MJan 2009 – Mar 2017

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. 1United Resources LPJan 2009 → Sep 2011
  2. 2Paladin Petroleum III, L.L.C.Oct 2011 → Feb 2013

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
671465-99DrillUnited Resources LPSep 18, 2008Oct 4, 2008Oct 21, 200811,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-247398————

Formation tops

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

FormationMD ftSubsea
FrioLOWER FRIO7,478-7,375
Nowacek8,160-8,057
VX Cip N Mkr.8,185-8,082
VX Myrick8,460-8,357
VicksburgLOWER VICKSBURG9,125-9,022

Perforations

Perforated and open-hole intervals.

FromToType
9,2429,248Perforated
9,2569,274Perforated
9,2769,282Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6253,05512.25890 S
78,3728.75420 S
4.59,7526235 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
00Jun 15, 2009Feb 20, 2009Yes
00May 29, 2009——

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